35st adlug oli suite_new_ils

Copyright 2016 @CULT. All rights reserved

Tiziana Possemato (@Cult)

OliSuite/WeCat: an evolution in RDA, linked open data, SBN scenarios. How manage the 'transition'

period from old to new perspectives


Towards the BIBFRAME/Linked Data environment

2

In order to be ready with the concept of evolution from a web of documents (the traditional web) to a web of data (the semantic web) and with the started transition from MARC formats to Linked Open Data, we studied and developed a projects that go in this direction, more recently with emphasis on the model proposed by the Bibliographic Framework Initiative (BIBFRAME) following RDA guidelines. To this aim, we focus on the following three areas of activities.


The three areas of activities towards the BIBFRAME/Linked Data environment

3

1.The enrichment of MARC records to simplify BIBFRAME conversion

2.The use of a framework to automate the conversion from MARC to RDF, using BIBFRAME rda and other vocabulary

3.The creation of a FRBR/BIBFRAME layer starting from bibliographic and authority records, to help librarians and end users in LOD fruition


1. Enrichment of MARC records to simplify BIBFRAME conversion

4

Additional MARC tag fulfilment and treatment in order to simplify the conversion into BIBFRAME without losing content: the MARC record is enriched (through manual and automatic processes) with tags and subfields, in particular with the addition of a certain number of local and global identifiers. This builds the precondition to allow the conversion of MARC into Linked Open Data by any party.


URI Management System

5

We are improving in the WeCat cataloguing module of OLISuite a «URI Management System», to manage identifiers for each access point or heading. See as an example in the following slides the authorized access point for Franz Kafka and, in the first column (URI), the number of URIs associated to the heading.


URI Management System (WeCat screen)

6


URI Management System (WeCat screen)

7

The cataloguer can check, modify, delete or add other identifiers to the same heading


Validate an URI

8


Uri verification on VIAF web site

9

Click on the URI validated to verify directly it on VIAF web site


Creation of a new URI

10

Select source to search URI


URI’s result search for VIAF

11

Select the URI desired and SAVE


URI’s list

12


Cross references creation using external sources

13

To create the cross references desired, select the headings from the results ISNI list and SAVE


The cross references on our Name index

14

The cross references, coming from ISNI web services and previously saved, now are linked to the author «Kafka, Franz, 1883-1924» on our Name index


Access points and URIs

15

The URIs associated to a heading can be used in varying and useful ways. In the data export/conversion process we can choose how many URIs to make available for each heading, how to associate them to the heading, how to show them in relation to data use and formats.


Access point and URIs (example 1)

16

As $0 associated to access point in the MARC bibliographic record: =LDR 00560nam a2200181 4500 =001 000000127573 =003 CaOOAMICUS =005 20160108094931.0 =008 160107s\\\\\\\\it\\\\\\\\\\\\000\u\ita\r =040 \\$aAtCult$bita =100 1\$aKafka, Franz,$d1883-1924$0(isni) 0000 0001 2280 370X. =245 03$aLa metamorfosi /$cFranz Kafka. =260 \\$aMilano :$bLa spiga,$c2002. =300 \\$a61 p.; $c18 cm =336 \\$atext$2rdacontent =337 \\$aunmediated$2rdamedia =338 \\$avolume$2rdacarrier =997 \\$aPS



17

As specific tag in the MARC authority record: =LDR 00698nz 2200145 4500 =001 000000000617 =005 20160108125155.0 =008 751003s1974\\\\enk\\\\\\\\\\\000\1\eng\\ =024 7\$a56611857$2viaf =024 7\$a000000012280370X$2isni =040 \\$aPS$bita =100 1\$aKafka, Franz$d1883-1924 =400 1\$aKafka, F.$q(Franz)$d1883-1924 =670 \\$aWikipedia, Oct. 25, 2012$bFranz Kafka; born 3 July 1883 in Prague; died 3 June 1924 Kierling near Vienna; an influential German-language writer of novels and short stories, regarded by critics as one of the most influential authors of the 20th century. Kafka was a Modernist and heavily influenced other genres, including existentialism)



18

As RDF property in the triples produced in the conversion process:

001 000000000617

024 7 $a56611857$2viaf

024 7 $a000000012280370$2isni

100 1 $aKafka, Franz

<atcult:eb-617> <rdf:type> <bf:Identifier> <atcult:eb-617> <bf:local> <atcult:617-kafka-franz> <atcult:eb-617> <bf:identifierValue> “617” <atcult:eb-617> <owl:sameAs> “http://viaf.org/viaf/56611857” <atcult:eb-617> <owl:sameAs> “http://isni-url.oclc.nl/isni/ 000000012280370



19

Another example of identifiers used

as RDF property of an entity type

Person:

001 000000000617

024 7 $a56611857$2viaf

024 7

$a000000012280370$2isni

100 1 $aKafka, Franz

<atcult:617-kafka-franz>

<rdf:type>

<bf:Person>

<atcult:eb-617>

<rdf:type>

<bf:Identifier>

<atcult:eb-617>

<bf:local>


<atcult:eb-617>

<bf:identifierValue>

“617”


<bf:hasAuthority>

<rdf:resource=

“http://viaf.org/viaf/56611857”>


<bf:hasAuthority>

<rdf:resource=

“http://isni-url.oclc.nl/isni/

000000012280370”


2. Use of a framework to automate the conversion from MARC to RDF

20

The conversion from different formats to RDF is realized within the WeCat cataloguing module, that embeds micro-agents software, each one mapped on a specific MARC tag/subfield in order to convert and export it as Linked Open Data.

The same conversion process can be activated independently from an ILS, using data in different formats (MARC, xml, Lido, etc.).

Automatic conversion in RDF is realized through the ALIADA framework, applying the BIBFRAME vocabulary.


OliSuite/WeCat: from MARC 21 to RDF

21

Example of the

conversion process

activated in the ILS:

at the end of the

cataloguing workflow,

the user can click on the

RDF button to

convert/publish the

record as RDF triples,

using the ALIADA

framework


The conversion process from any format to RDF

22

IT COMPANIES

LINKED DATA CLOUD http://lod-cloud.net/

Library Management System (ILS)

Museum Collection Management System (MMS)

Content Management System (CMS)

RESOURCES METADATA CREATORS (Librarians, curators)

ALIADA

BROWSERS (GOOGLE)

OTHER PUBLIC AND CULTURAL INSTITUTIONS

http://lod-cloud.net/




Ontologies used in the framework

23

Additional ontologies used

in the ALIADA framework:

• FRBRoo (part of the first

release)

• BIBFRAME

• DCMI Metadata Terms

• RDF Schema

• RDA elements


3. The creation of a FRBR/BIBFRAME layer from bibliographic and authority records

24

The existent catalogues are description, above all, of manifestations/instances. We tried to give an answer to the requirement to re-design the data model with a system that derives data from existent records to produce a new Person/Work layer. The process creates for each Person entity a ‘cluster’ of possible variant forms, and does the same for associated Works.

• Person cluster: creation of a unique name access point for Person names.

• Work cluster: each Person is associated to his Work.

Each Work cluster is linked to Instance titles.


The loading process and creation of clusters

25


Cluster makers – Person (example 1)

26

001 00001

200 \1 $aEco,$bUmberto$f<1932- >.

400 \0 $aDedalus

997 \\ $aAUTHORITY

001 27283

700 \1 $aEco,$bUmberto$f<1932- >.

997 \\ $aUNINA

001 7258

700 \1 $aECO,$bUmberto

997 \\ $aUNISA

001 7258

700 \1 $aEco,$bUmberto

997 \\ $aUNIBAS

API VIAF

Similarity Score

Calculator

100%

ID cluster: 1281829

Author : Eco, Umberto, 1932-

...

VIAF ID: 108299403

Other forms:

ECO, Umberto

Eco, Umberto

Dedalus

اكو، أمبيرتو -1932

،إكو، أمبرتو

Eco, Umberto (Italian writer,

architect, and critic, born

1932)

Umberto Eco semiologo,

filosofo e scrittore italiano

1932, אומברטו, אקו -

This chart and the following example show the mechanism for associating names from different records in a single Person cluster



27

001 00002

200 \1 $aVan Ness,$bHendrick C.

997 \\ $aAUTHORITY

001 8379

701 \1 $aVan_Ness,$bHendrick C.

997 \\ $aUNIBAS

001 173506

701 \1 $aVan Ness,$bHendrick C.

997 \\ $aUNINA

001 1317

701 \1 $aVan Néss$b, Hendrick C.

997 \\ $aUNISANNIO

001 56522

701 \1 $aVAN NESS,$bHendrick C

997 \\ $aUNISA

API VIAF

Similarity Score

Calculator

100%

ID cluster: 1425297

Author : Van_Ness, Hendrick C.

Other forms:

Van_Ness, Hendrick C.

ID cluster: 965648

Author : Van Ness, Hendrick C.

VIAF ID: 32564481

ID LOC : n81035735

ISNI: 0000000116167284

Other forms:

VAN NESS, Hendrick C .

Van Ness, H. C.

Van Néss, Hendrick C.

Van Ness, H. C. (Hendrick C.)

Van Ness, Hendrick Charles



28

001 00003

200 \1 $aMiseska Tomic,$bOlga

997 \\ $aAUTHORITY

001 380992

700 \1 $aTOMIC$b, Olga Miseska

997 \\ $aUNIOR

API VIAF

Similarity Score

Calculator

100%

ID cluster: 1140364

Author : Tomić, Olga Mišeska

VIAF ID: 17255268

Other forms:

Miseska Tomic, Olga

TOMIC, Olga Miseska

Mišeska-Tomik, Olga.

Mišeska Tomik, Olga, 19..-....

Tomić, Olga Mišeska 1935-...

Mišeska Tomić, Olga


BibliotecheIndividuazione

Raccolta

Selezione

Elaborazione

Search Engine RDF Store

LOD Cloud

Linked Open Services Platform

(Elaborazione dati in RDF)

Bib1 Bib2

Bib3

Bib4

Bib5

Bib6

BIBFRAME-UP

30


Contra academicos

The BIBFRAME-UP: a three layer architecture

De Beatâ Vitâ De civitate Dei contra paganos

Person/Works

Instances

Item


The BIBFRAME-UP Portal: synthesis

31

1st layer - Person/Work: the set of data related to Person and Work, in RDF, saved in a SPARQL endpoint and made available by specific search and presentation functions. 2nd layer - Instance: bibliographic data indexed in SOLR search engine, that is able to produce new different data aggregations in facets (such as publication date, language, publisher, edition, etc.). This layer provides users with a wide range of search and navigation functions. 3rd layer - Item: holdings data, related to copy information, coming from the local OPAC or local system of each specific library.


The centrality of authority

32

The enhanced function for controlling authority expresses the need, common to RDA

and the principles of linked open data, to describe and identify the entity that is

being analyzed with a high number of attributes, thus creating an object perfectly

identifiable and reusable in many areas .


Creation of an authority record from VIAF

33


VIAF’s search result

34


Selection of headings desired

35


Message for successfully loading

36


VIAF authority record saved in our database

37


OliSuite and SBN Index

38


Results search window SBN BID

39


Browsing the Name index SBN VID

40


Searching in SBN index

41


Creation in SBN index (bibliographic and authority records)

42


Bibliographic record creation in SBN index

43


Demo: http://olisuite.casalini.it/olisuite/pages/weloan/core/home.faces

Tiziana Possemato – @CULT

Thank you

http://olisuite.casalini.it/olisuite/pages/weloan/core/home.faces

35st adlug oli suite_new_ils

Technology