Integration of Heterogeneous Metadata in Europeana. Cesare Concordia Institute of Information Science and Technology-CNR

Transcription

1 Integration of Heterogeneous Metadata in Europeana Cesare Concordia Institute of Information Science and Technology-CNR

2 Outline What is Europeana The Europeana data model The Europeana Semantic Elements (ESE) Case study: the data ingestion in the Europeana prototype Conclusion and next steps

3 What is Europeana European Digital Library Open access to the digitized objects of European cultural institutions Cross multilingual search European cultural heritage at a single place Across cultural domains and across countries General public - User centered Digital Library technologies + Web 2.0

4 What is Europeana The Europeana Digital Library will be the result of a number of projects run by different cultural heritage institutions, among them there are: Athena an aggregator that helps museums bringing their content to Europeana APENet a BPN whose objective is to build an Internet Gateway for Documents and Archives in Europe EUROPEANAlocal that aims to improve the interoperability of the digital content held by regional and local institutions European Film Gateway: find solutions for providing integrated access to the Europe's cinematographic heritage All are part-funded by the European Commission s econtentplus programme.

5 What is Europeana The full implementation of the Europeana is the goal of the two core technology projects: EuropeanaConnect that will provide the technologies and resources to semantically enrich the digital content in Europeana. Europeana V1.0 that will implement the technology platform They are successors to the EDLNet thematic network which created the EDL Foundation and the Europeana prototype ( in short Europeana v1.0 and EuropeanaConnect will turn the prototype into an operational service

6 Europeana architecture Europeana is not a Web Portal Europeana is a services platform providing an Application Program Interface (API) enabling cultural institutions and users to Access Europeana content Provide content to Europeana Build applications using Europeana functionalities for their own use. According to DELOS classification Europeana is a Digital Library System (DLS) The Europeana Portal is a web application using the Europeana API to access the Europeana Digital Library

7 Europeana DLS functional architecture

8 Europeana data flow

9 Europeana data space Europeana will create a data space that is a representation of the content providers data spaces The Europeana data space will contain Digital Surrogate Objects (DSO) that are defined as follows: "the minimal significant documentary object unit a given content provider is able / willing to identify (in the case of textual object there thus can be surrogates on the level of the entire document, on chapter level or on page, paragraph, sentence or even word levels)" [ EDLNet Deliverable 2.5] Each DSO will be a web resource, it will be identified by a URI owned by Europeana.

10 Digital Surrogate Objects There are several kinds of DSO, depending on the kinds of objects to be represented: Real Physical Object (RPO): the physical object, for instance a painting, a building, a book Digital Representation Object (DRO): a digital object obtained by digitizing an RPO, usually created by the data provider Digital Primary Object (DPO), a "born digital" object, i.e. a digital object that is not a DRO

11 Digital Surrogate Objects Each DSO contains at least an identifier, a link to the Object in the content provider data space, the metadata record describing the object and some elementary technical and licensing information There should be a one-to-one correspondence between remote object entities and DSOs Surrogates can be linked each others

12 Digital Surrogate Objects On a very abstract level Europeana can be seen as a large collection of DSOs representing born digital or digitised cultural heritage objects Surrogates will be linked to semantic resources representing concepts as well as to reference entities such as persons, places and periods in time (contextualization)

13 Surrogate Object Data Model (EDLNet)

14 Europeana Semantic Elements In EDLNet the Surrogate Data Model has been implemented using the Europeana Semantic Elements (ESE) metadata format The ESE, consists of the Dublin Core (DC) metadata elements, a subset of the DC terms and a set of twelve elements which were created to meet Europeana s needs.

15 Source Element Refinement(s) Europeana Semantic Elements Source Element Refinement(s) DC title alternative DC coverage spatial; temporal DC creator DC rights DC subject DC terms provenance DC DC DC description tableofcontents publisher contributor DC date created; issued DC type DC format extent; medium DC DC identifier source DC relation isversionof; hasversion; isreplacedby; replaces; isrequiredby; Europeana relation isshownby; isshownat Europeana usertag Europeana unstored Europeana object Europeana language Europeana provider Europeana type Europeana uri Europeana year Europeana hasobject Europeana country

16 Europeana Semantic Elements (ESE) DSOs are created during the Europeana data ingestion process using the information provided by the content suppliers

17 EDLNet Data Ingestion Workflow Source collections are acquired via harvesting or received by content providers as XML files The mapper checks the source collections and creates the mapping rules XSLT is used to implement the mapping ESE collections are stored and indexed

18 Europeana prototype data space The first Europeana prototype has been presented in November 08 as result of the EDLNet project Next prototype will be released in September 09 As of April 09, it contains DSOs referring information objects provided by 54 cultural institutions from 24 European countries 4.5 milion of surrogate digital objects stored in the data space 15 different metadata formats

19 Heterogeneity: records by countries

20 Heterogeneity: records by languages

21 Heterogeneity: records by data providers

22 Heterogeneity: records grouped by metadata format

23 Source collection snippet: DC <ListRecords> <record> <dc:title>από τα γλυκοχαράµατα της ζωής µου: Σαλαµίς</dc:title> <dc:creator>κ. Ν. Κωνσταντινίδης</dc:creator> <dc:subject/> <dc:description/> <dc:publisher>νέα Ζωή</dc:publisher> <dc:contributor/> <dc:date> </dc:date> <dc:type>articles</dc:type> <dc:format>image/jpeg</dc:format> <dc:identifier> 313 <dc:identifier> <dc:source>νέα Ζωή; Vol 1, No 1 (1904); σελ </dc:source> <dc:language>gr</dc:language> <dc:coverage/> <dc:rights/> </record>

24 Example: DC mapping

25 Source collection snippet: MemoireSDAP <BASE> <NAME>Mémoire</NAME> <DOMAINE>SDAP</DOMAINE> <NOTICES> <NOTICE ID="AP "> <REF> AP </REF> <ADRESSE> rue Petit ; villa "Rosario", ilot A</ADRESSE> <AUTP>Richard, Fran ßoise</AUTP> <AUTOR>Delamotte, Patrick (architecte)</autor> <COM> Mers-les-Bains </COM> <MCL>Secteur sauvegardé</mcl> <LEG>cartouche céramique en relief façon "cuir" ; décor briques vernissées.</ LEG> <COULEUR>OUI</COULEUR> <LIB>Epoque 19ème</LIB> <PAYS>France</PAYS> <INSEE>80533</INSEE> <TYPEIMG>JPG ; oui</typeimg> <TYPSUPP>DS1</TYPSUPP> <REFIM>AP080_ NUCA_P.JPG,DS1,,</REFIM> <VIDEO>/Wave/image/memoire/1047/ap080_ nuca_p.jpg;/Wave/ image/memoire/1047/ap080_ nuca_v.jpg</video> </NOTICE>.

26 Analysis file of the MemoireSDAP collection

27 Example: MemoireSDAP mapping

28 <xsl:template match="base"> <metadata> <xsl:comment>europeana:type has 'image' value </xsl:comment> <xsl:apply-templates select="notices/notice"/> </metadata> </xsl:template> <xsl:template match="notices/notice"> <record> <xsl:apply-templates select="deno"/> <xsl:apply-templates select="idprod"/> <xsl:apply-templates select="adresse"/> <xsl:apply-templates select="autor"/> <xsl:apply-templates select="autti"/> <xsl:apply-templates select="com"/> <xsl:apply-templates select= VIDEO"/> XSLT snippet

29 XSLT Snippet <xsl:template match="video"> <europeana:isshownby > <xsl:text> select="substringbefore(.,'; )"/> </europeana:isshownby> <europeana:object > <xsl:text> select="substringbefore(.,';')"/> </europeana:object> </xsl:template>

30 Analysis file of the mapped ESE collection

31 Theory and Practice Lot of manual work for writing the mapping rules and implement them Often mapping files cannot be reused Same metadata element have different kind of values for different collections It is difficult distinguish metadata records describing DR, DP or RP objects Many content providers provide minimal metadata records, it is difficult to build significant DSOs Few relationships among digital objects in the metadata

32 Theory and Practice Surrogates contextualization is a complex task Implicit contextualization i.e. matching elements and attributes values with (few) classification schemes and/or authority files has been applied to several collections Explicit contextualization i.e. using elements values directly linking to semantic resources (ex. IsAbout) has been in practice never applied Need to adopt authority files

33 Data normalization problem: example

34 DSO Data Model (EDLNet): theory and practice

35 Ingestion: from EDLNet to Europeana The DSO data model is currently being reviewed, it should move from DC to CIDOC-CRM Extracting and adding snippets (research) Provenance Events Model adopted for Europeana will be released in September 09 More involvement of content providers in the ingestion workflow (EuropeanaConnect) Extracting knowledge from the data space to contextualize and create relationships among DSOs (research) Try to make the mapping a semi-automatic process (research) Going open source Europeana Labs

36 Acknowledgements The Digital Surrogate Object model has been defined by WP leaders of EDLNet Work Package 2: Makx Dekkers, Stefan Gradmann and Carlo Meghini and reviewed by EDLNet members The ESE model has been defined by Go Sugimoto (EDL Office) EDLNet Interoperability Manager and reviewed by EDLNet members. The xml-analyzer program has been developed by Gerald de Jong and Sjoerd Siebinga (EDL Office).

37 Thanks