Evolving Europeana’s Metadata: from ESE to EDM

Evolving Europeana’s Metadata: from ESE to EDM
Boyan Bontchev Faculty of Mathematics and Informatics, Sofia University Sofia, Bulgaria DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

September 18, Veliko Tarnovo, Bulgaria
DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Faculty of Mathematics and Informatics (FMI) BSc, MSc, PhD programs in: Mathematics Applied Mathematics Mathematics and Informatics Statistics Informatics Computer Science Software Engineering Information Systems Mathematics and Computer Science DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Technology enhanced learning: models, adaptability, authoring/instructional/delivery platforms and interoperability – experience gained within ARCADE: Architecture for Reusable Courseware Authoring and Delivery (CIST project), FP6 NoE IST Project KALEIDOSCOPE: “Concepts and methods for exploring the future of learning with digital technologies”, FP5 (IST ) Project DIOGENE: A Training Web Broker for ICT Professionals, and FP6 IST IP Project TENCompetence: Building the European Network for Lifelong Competence Development; Serious games - creating virtual business models, tools and environments within FP IST-NMP-2 Project PRIME: Providing Real Integration in Multi-disciplinary Environments, role-based Web/WAP/SMS games (SHIVER project of MyAlert S.L.); models of board games for education for D002/155 Bulgarian NSF project ADOPTA: ADaptive technOlogy-enhanced eduTainment platform for building edutainment (education plus entertainment); mobile games Content collaboration and access to cultural heritage - within FP5 IST Project MECITV: Media Collaboration for Interactive TV; using semantic technologies for construction of an ontology-driven community-oriented map-based portal for cultural heritage (internal project) Software services - software service design by contract and service discovery (FP7-REGPOT Project SISTER: Strengthening the IST Research Capacity of SU DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Agenda Introduction Europeana Content providers and aggregators Direct and indirect contributions to Europeana Contribution workflow Importance of metadata Metadata types Europeana Semantic Elements (ESE) Europeana Data Model (EDM) Conclusions DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Introduction Importance of integrated multilingual Web access to locally developed multimedia content Modern content tends to be more heterogeneous and distributed It is produced using collaborative processes in various forms, formats, and languages Worldwide content access services like semantic and optimized search and browsing Increase of traffic of content providers and aggregators at national and regional level DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

EC Digital Libraries Initiative (2005)
Three main issues of pan-European activity: Digitisation Avoid duplication / create synergies Strategic and financial planning Promoting mass digitisation facilities and programmes Digital preservation Strategies and standards Digitised from analogue Born digital: legal deposit; web harvesting Online accessibility Intellectual property rights Integrated access Digital Libraries initiative was inaugurated by the Commission in 2005 as part of the Commission's i2010 strategy to boost the digital economy. It was the culmination of over a decade’s work the Commission had supported, and also a response to Google’s book digitisation programme. It was a way of enabling the broad cutural heritage of Europe to be seen alongside primarily text-based, anglophone material - coming out the Google work Its intention was to harmonise digitisation initiatives going on across Europe. Random digitisation going on in libraries, museums, archives, audio-visual collections – duplication, different standards, methods and terms of accessibility, Programme needed to harmonise standards, establish best practice, minimise duplication, select related and complementary collections, Need to create national strategies and identify synergies Setting up large scale digitisation programmes Pres Systematic approach to digital preservation - Different approaches; all re-inventing the wheel - starting from beginning, no knowledge exchange, or best practice methodology Finally, the third strand was to enable public access to the digitised material Source: Jon Purday, Senior Communications Advisor, Europeana DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Europeana (foundation/service/network) Europeana is “a digital library that is a single, direct and multilingual access point to the European cultural heritage” (European Parliament) “A unique resource for Europe's distributed cultural heritage… ensuring a common access to Europe's libraries, archives and museums.” (Horst Forster, Digital Content & Cognitive Systems Information Society Directorate, European Commission) Aims at building an open services platform providing facilities for management of large collections of surrogate objects representing digital content DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Source: Meghini, Isaac, Gradmann, Schreiber. The Europeana Data Model (2010) Objectives of Europeana To create a multilingual access point to Europe’s cultural and scientific heritage (public-domain) To develop a wide range of information products and services making use of digitized cultural heritage resources To play a key role in expected future growth of important and promising industrial sectors such as technology based learning and tourism To inspire new creative enterprise and business innovation To promote understanding of a common European background and European identity DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Strategy (2011-2015) Engage Aggregate Facilitate Distribute
to build the open trusted source for European cultural and scientific heritage content Aggregate to support the cultural and scientific heritage sector through knowledge transfer, innovation and advocacy to make heritage available to users wherever they are, whenever they want it Engage Distribute Facilitate to cultivate new ways for users to participate in their cultural and scientific heritage

The Europeana foundation DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Europeana’s content providers and aggregators A content provider for Europeana may be any organization (and even individuals, in the future) that provides digital cultural heritage content accessible on the Web via Europeana An Europeana aggregator is a business entity that: collects descriptive metadata from a group of content providers and transmits them to Europeana standardizes file and metadata formats provides help to the providers regarding conformance with metadata standards and process workflows of Europeana DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Metadata harvesting Europeana stores only the institution’s metadata and indexes it, however, digital objects remain stored at the content provider site (library) The provider/aggregator prepares the data sets to be submitted using the Europeana Semantic Elements (ESE) specification or Europeana Data Model (EDM) The aggregator aggregates descriptive metadata from content (data) providers, usually through metadata harvesting using the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Types of aggregators Public versus non-public Digital repository aggregators (storing digital items to a repository) versus intermediary aggregators (only collect metadata with a link to digital item) Single sector aggregator (collects data from a single sector such as a local/regional/national museum, archive, library or audio-visual collection) vs cross sector aggregator (data from several sectors) Horizontal aggregators (aggregate content across several domains) vs vertical (aggregate content from single domain - at international, national or regional level, like Judaica) DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Direct and indirect contributions to Europeana The Europeana Group projects are: APEnet – Archives Portal Europe ASSETS aims to improve the usability of Europeana. ATHENA aggregates museum content and promotes standards for museum digitisation and metadata. Biodiversity Heritage Library - Europe CARARE aggregates content for the archaeology and architectural heritage. Digitising Contemporary Art (DCA)[10] ECLAP will build a large digital library of performing arts and UGC.[11] European Film Gateway (EFG) Europeana Connect adds sound material to Europeana. Europeana Fashion will bring more than 700,000 items of fashion-related content into Europeana. Europeana Libraries will add over 5 million digital objects to Europeana from 19 of Europe’s leading research and university libraries. Europeana Local brings content from regional and local content holders. Europeana Regia is digitising royal manuscripts from Medieval and Renaissance Europe. Europeana Travel will bring material associated with travel, trade, tourism and migration into Europeana. Europeana v1.0 is developing a fully functional Europeana website. EURO-Photo digitises photographs from news agencies. EUscreen contributes television material to Europeana.[12] Heritage of People’s Europe (HOPE) aims to improve access to digital social history collections. JUDAICA Europeana looks at the Jewish contribution to Europe's cultural heritage. Linked Heritage aims to add substantial new content from commercial and public sectors, and enrich Europeana's metadata with a "linked data" approach. Musical Instrument Museums Online (MIMO) Natural Europe connects the digital collections of natural history museums. OpenUp! brings Europe's natural history heritage to Europeana PATHS[13] Personalised Access To cultural Heritage Spaces The European Library aggregates the content of national libraries. thinkMOTION gathers content from the field of motion systems. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Europeana projects Athena (3,964,858) The European Library (3,499,524) moteur Collections / France (2,205,082) Hispana (1,762,759) Norsk Kulturråd (1,352,518) Swedish Open Cultural Heritage (1,262,773) Saxon State & Univ. Lib., Dresden/Deutsche Fotothek (1,104,117) Irish Manuscripts Commission (907,837) CARARE (824,882) Federacja Bibliotek Cyfrowych (783,275) CultureGrid (696,036) OpenUp! (585,662) Archives Portal Europe (555,370) EFG - The European Film Gateway (546,352) Bayerische Staatsbibliothek (465,614) Judaica Europeana (460,883) DISMARC - EuropeanaConnect (347,929) Hope - Heritage of the People Europe (180,548) ASSETS (128,887) Bernstein project: (119,961) Rijksmuseum (112,590) Erfgoed Brabant (111,664) EuropeanaLocal Deutschland (109,609) dLib.si - Digital Library of Slovenia (104,584) Hellenic Aggregator at Veria Public Library (102,705) Institut National de l'Audiovisuel (101,356) BHL Europe (100,561) DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Workflow for contributions 1/2 The provider/aggregator has to a Data Provider/Aggregator Agreement with Europeana Office The organization send to Europeana Operations a Data Submission Form with description of type of submission (new/update), licensing and metadata information The Europeana Office reviews the submission request and sends feedback and plans for the submission DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Workflow for contributions 2/2 The provider/aggregator prepares the data sets to be submitted using ESE or EDM. Mapping and Normalisation Guidelines Web Content Checker - intended for validation of mapping against the XML Schema, and for local testing of ingestion operations such search, browse and display of the data in a copy of the Europeana portal. The Europeana Office validates the transfer with the organization. After successful validation, the Europeana Operations ingest submission data into the Europeana production environment and notifies the organization. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Europeana’s technical implementation steps 1. Constitution of digital collection(s) 2. Repository installation 3. Metadata transformation – includes: a. Metadata Extraction b. Metadata Normalization c. Metadata Enrichment 4. Repository Population 5. Metadata Harvesting 6. Usage of aggregator repositories 7. Starting end-user services DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Metadata transformation 1/2 Metadata extraction from the collection management system to populate the local repository Metadata normalization - represents a process of harmonizing metadata in order to match a specific format or notations (i.e., given date format) DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Metadata transformation 2/2 Metadata enrichment - stays for a manual or semi-automatic process of improving the metadata quality such as: multi-lingual content (e.g. by using Google Translate), temporal and/or spatial references (e.g. by using date and location extraction software services), mapping to common vocabularies such as that of Simple Knowledge Organization System (SKOS). Many automated techniques may be faulty and could incur some errors. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Digital cultural heritage objects The data model of Europeana enables integrated multi-lingual search and discovery of digital cultural heritage objects (CHOs) distributed at local European collections. These services are available thanks to a common central index of CHOs metadata maintained by Europeana. As far as Europeana does not store provided CHOs but their metadata, there is generated a description and a thumbnail (preview) of any found CHO with a link to the content provider or aggregator Web side. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Three types of data A content provider or an aggregator is supposed do provide to Europeana three types of data: Metadata describing given provided CHO (using ESE or EDM notation) A preview (thumbnail) of the provided CHO - a thumbnail image or audio/moving image previews. Audio/moving image preview usually is a short extract of audio/video content with lower resolution Active and stable links to the provided CHO on the provider/aggregator Web site DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Europeana Semantic Elements (ESE) was developed specially for the first prototype of Europeana in 2008 as a Dublin Core (DC) application profile incorporates 37 DC terms from both the dc and dcterms namespaces as well, there are defined 12 ESE-specific terms using the Europeana namespace, specially purposed for supporting portal functionality. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Elements supplied by Europeana
ESE V3.4 Mandatory elements Recommended elements Additional elements Elements supplied by Europeana dc:title or dc:description dc:language europeana:dataProvider europeana:isShownAt or europeana:isShownBy europeana:provider dc:subject or dc:type or dc:coverage or dcterms:spatial europeana:rights europeana:type dcterms:alternative dc:creator dc:contributor dc:date dcterms:created dcterms:issued dcterms:temporal dc:publisher dc:source dcterms:isPartOf dc:format dcterms:extent dcterms:medium dc:identifier dc:rights dcterms:provenance dc:relation dcterms:conformsTo dcterms:hasFormat dcterms:isFormatOf dcterms:hasVersion dcterms:isVersionOf dcterms:hasPart dcterms:isReferencedBy dcterms:references dcterms:isReplacedBy dcterms:replaces dcterms:isRequiredBy dcterms:requires dcterms:tableOfContents europeana:unstored europeana:country europeana:language europeana:uri europeana:usertag europeana:year DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

ESE mapping guidelines
Answer questions about provided CHOs such as “who, what, where and when?” Thus, the organisation should provide names, types, places and dates relevant to the provided CHOs by mapping as many as possible of original source metadata to the specified ESE elements As far as many of the elements are refinements of other elements, the provider must always use the more specific dcterms refinements when possible dcterms:created and dcterms:issued are refinements of dc:date dcterms:spatial or dcterms:temporal instead of dc:coverage DIPP'2012

Shortcomings of ESE ESE supports interoperability but it supposes a loss of original metadata. The ESE model is “flat” using only simple string values and preventing linking items ingested by Europeana to other CHOs such as contextual entities (e.g., naming variations of the CHO's creator) or more specific concepts. As well, ESE aggregates in one record metadata fields applying to different entities like providers' use rights. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Europeana Data Model (EDM) 1/2 aims at replacement the old the ESE schema focused at enabling data integration and interoperability by means of semantic linking between objects, while preserving original metadata (unlike ESE) based on RDF graphs RDF graphs have been created to provide the reader with a more intuitive view of examples. The reader should however be aware that these graphs are meant to represent data expressed in RDF, adapting the conventions used, e.g., by the RDF Primer [RDF-Primer]. This implies that they correspond exactly to a set of RDF “statements” (or “assertions”), using the following rules: - a circled URI in normal font denotes a standard RDF resource. Two URIs’ being in a single circle indicates that one resource has been given two identifiers. Such situation may typically result from asserting an owl:sameAs statement between the two URIs.3 - a string enclosed with quotes denotes an RDF literal. It can carry a language tag, as for - an arrow between two resources (or between a resource and a literal) indicates an RDF statement ("triple") between these two resources. The object of the statement is 3 Cf. Europeana Data Model Primer 7 the origin of the arrow; its subject is the target of the arrow. The predicate of the statement is the property indicated by the URI in normal font next to the arrow - a URI in italic font denotes: o a type for the resource, if appearing in a "resource circle". o a super-property of the property, if appearing next to an "property arrow" DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Europeana Data Model (EDM) 2/2 supports an enriched functionality based on semantics (like semantic search). makes use of fundamentally new principles for ingesting/managing/publishing metadata about CHOs accommodates: LIDO (Lightweight Information Describing Objects) for museums EAD (Encoded Archival Description) - finding aids for archival and manuscript collections METS (Metadata Encoding and Transmission Standard) – descriptive/administrative/structural metadata of digital library CIDOC CRM (Conceptual Reference Model) LIDO is a schema intended for delivering metadata, for use in a variety of online services, from an organization’s online collections database to portals of aggregated resources, as well as exposing, sharing and connecting data on the web. LIDO is not intended to be used as a basis for a collection management system or to support loan and acquisition activities. Its strength lies in its ability to support the full range of descriptive information about museum objects. It can be used for all kinds of object, e.g. art, cultural, technology and natural science. It supports multilingual portal environments. LIDO defines 14 groups of information of which only three are mandatory. This allows for as large a variety of completeness of information as possible. Organizations can decide which data they want provide to a portal and publish online. It is made up of a nested set of ‘wrapper’ and ‘set’ elements which structure records in culturally significant ways. An important part of its design is the concept of events taken from the CIDOC CRM. For example the creation, collection, and use of an object are defined as events that have associated entities such as dates, places and actors. These can all be represented in a consistent way. LIDO also allows an organization to provide (in different parts of the schema): ● Indexing information – optimized for searching and retrieval; ● Display information – optimized for presenting information online to the user of the portal. The structural elements of LIDO contain ‘data elements’ which hold the in EAD: standard for electronic encoding of finding aids for archival and manuscript collections implementation of Extensible Markup Language (XML) maintained in the Network Development and MARC Standards Office of the Library of Congress (LC) in partnership with the Society of American Archivists 1993: initiated by the University of California, Berkeley Library under direction of Daniel Pitti August 1998: version 1.0 Document Type Definition (SGML DTD) December 2002: version 2002 SGML/XML DTD EAD: on-line publication of guides and inventories to archival and manuscript collections facilitate searching and browsing content of collections may provide access to digital images and/or transcriptions of items in a collection EAD is used in: Indiana University Finding Aids Five College Archives & Manuscripts Collection Washington Research Libraries Consortium Kentuckiana Digital Library The Metadata Encoding and Transmission Standard (METS) is a metadata standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium. The standard is maintained in the Network Development and MARC Standards Office of the Library of Congress, and is being developed as an initiative of the Digital Library Federation. The 7 sections of a METS document METS header metsHdr: Contains metadata describing the METS document itself, such as its creator, editor, etc. Descriptive Metadata dmdSec: May contain internally embedded metadata or point to metadata external to the METS document. Multiple instances of both internal and external descriptive metadata may be included. Administrative Metadata amdSec: Provides information regarding how files were created and stored, intellectual property rights, metadata regarding the original source object from which the digital library object derives, and information regarding the provenance of files comprising the digital library object (such as master/derivative relationships, migrations, and transformations). As with descriptive metadata, administrative metadata may be internally encoded or external to the METS document. File Section fileSec: Lists all files containing content which comprise the electronic versions of the digital object. file elements may be grouped within fileGrp elements to subdivide files by object version. Structural Map structMap: Outlines a hierarchical structure for the digital library object, and links the elements of that structure to associated content files and metadata. Structural Links structLink: Allows METS creators to record the existence of hyperlinks between nodes in the Structural Map. This is of particular value in using METS to archive Websites. Behavioral behaviorSec: Used to associate executable behaviors with content in the METS object. Each behavior has a mechanism element identifying a module of executable code that implements behaviors defined abstractly by its interface definition. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria 30

EDM features data integration in an open environment (because it is feasible to anticipate all submitted metadata) rich & extendible functionality + reuse of existing models distinguishes any provided CHO (e.g., a painting, book, video, etc.) from its digital representation and, on the other side, from its metadata record allows co-existing of several possible (even contra-dictionary) descriptions of the same CHO, because different org’s may submit different metadata sequence or partitioning needed to support representation of complex items and compositions. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

EDM classes The EDM Class hierarchy. The classes introduced by EDM are shown is light blue rectangles. The classes in the white rectangles are re-used from other schemas; the schema is indicated before the colon - EDM re-uses from the following namespaces: • The Resource Description Framework (RDF) and the RDF Schema (RDFS) namespaces ( • The OAI Object Reuse and Exchange (ORE) namespace ( • The Simple Knowledge Organization System (SKOS) namespace ( • The Dublin Core namespaces for elements ( abbreviated as DC), terms ( abbreviated as DCTERMS) and types ( abbreviated as DCMITYPE) DIPP'2012 September 18, Veliko Tarnovo, Bulgaria 32

Europeana Linked Open Data Pilot the first Europeana EDM pilot system includes three core classes: a provided cultural heritage object (edm:ProvidedCHO) such as a painting, book, movie, music record, etc.) one or more digital representations of this object accessible via Web including its previews (edm:WebResource) an aggregation (ore:Aggregation) aggregating ore:ProvidedCHO and one or several edm:WebResource via two sub-properties of ore:aggregates - edm:aggregatedCHO and edm:hasView DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

edm:WebResource ore:Aggregation edm:ProvidedCHO
“Художествена галерия edm:WebResource Museum_Kazanlak/0083.html edm:dataProvider ore:Aggregation ex1:Aggregation/000TL042792 ore:aggregates edm:hasView “The Old Plovdiv ore:aggregates edm:aggregatedCHO dcterm:title edm:ProvidedCHO ex1:object/000TL042792 “Цанко dc:creator DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Object- or event-centric approach? 1/2 Aggregations capture digital environment of given provided CHO by attaching descriptive and contextual information about different features of the resource via: the object-centric approach - focused to the object metadata like dc:format, dcterm:title, edm:hasMet, edm:currentLocation and edm:hasType DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

“The old Plovdiv” by Tsanko Lavrenov – an object-centric description
edm:hasType cd:format “The Old edm:hasMet dcterm:created dcterm:title edm:ProvidedCHO ex1:object/000TL042792 “Цанко edm:hasMet dc:creator dcterm:subject edm:hasMet edm:currenLocation “Sofia,

Object- or event-centric approach? 2/2 Instead/together with object-centric descriptions - the more complex event-centric approach - enriches this data with contextual classes like: edm:Agent (representing persons or organizations), edm:Event (with edm:wasPresentAt property), edm:Place (with edm:happenedAt property), edm:TimeSpan (with edm:occurredAt property) skos:Concept (for SKOS entities thesauri and classification schemes) DIPP'2012 September 18, Veliko Tarnovo, Bulgaria 37

“The old Plovdiv” by Tsanko Lavrenov – an event-centric description
edm:Place ex1:place/Plovdiv “The Old edm:happenedAt edm:hasType cd:format dcterm:title edm:Event ex1:event/000TL a edm:ProvidedCHO ex1:object/000TL042792 edm:wasPresentAt ex1:schema/CreationEvent edm:occuredAt edm:wasPresentAt ex1:schema/AuthorAt dcterm:subject edm:TimeSpan ex1:time/1940 edm:Agent viaf:

Proxies As far as Europeana receives data from many providers, some data may represent multiple views on the same CHO. In order not to merge these different metadata records about the same object, Europeana supports provider’s proxy of this CHO, modeled using the ore:Proxy resource. A proxy is specific to given aggregation and represents description of the provided CHO specific for the provider and therefore for that aggregation. Thus, Europeana may support different, even conflicting metadata about any CHO, received by different providers about that CHO Digital Natives and Academics Do you know what a digital native or a digital immigrant is? A digital native is basically someone who grows up immersed in digital technology. It is the norm for them. A digital immigrant has to play catch-up with technology because it came along much later in life for them. DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

ore:Proxy “платно”@bg “canvas”@en “Художествена галерия Казанлък”@bg
skos:prefLabel skos:prefLabel edm:WebResource Museum_Kazanlak/0083.html skos:Concept ex1:concept/canvas edm:dataProvider “The Old edm:hasView ore:Aggregation ex1:Aggregation/000TL042792 dcterm:format dcterm:title edm:Event ex1:event/000TL a ore:proxyIn ore:Proxy ex1:Proxy/000TL042792 edm:wasPresentAt ex1:schema/CreationEvent edm:aggregatedCHO edm:occuredAt ore:proxyFor edm:happenedAt dcterm:creator edm:TimeSpan ex1:time/1940 edm:ProvidedCHO ex1:object/000TL042792 edm:Agent viaf: edm:Place ex1:place/Plovdiv “Tsanko “Цанко

Conclusions – ESE vs EDM 1/2
ESE metadata format supposes flat lists of property-value pairs while EDM specifies how the resources as networked => One-to-one mapping from ESE to EDM is not possible EDM structure leads to complex network of aggregations, proxies and other resources, which makes the RDF graphs rather complex. Tracking object data provenance without using proxies will be expected after starting applying RDF named graphs DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Conclusions – ESE vs EDM 2/2
Though the complexities which EDM does incur, it allows flexible metadata modeling with valuable semantic issues EDM preserves original metadata of the providers while facilitating data interoperability EDM does support effectively both object-centric and event-centric advanced metadata modeling, allowing property relations between provided objects, aggregation structures for hierarchical objects, versioning relations and compatibility with descriptions and conceptual schemas. The launch of data.europeana.eu has set the first trial of making the Europeana metadata set available as Linked Open Data. a smooth transition from ESE to EDM DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Thank you for you attention!
For contacts: Questions? DIPP'2012 September 18, Veliko Tarnovo, Bulgaria

Evolving Europeana’s Metadata: from ESE to EDM

Similar presentations

Presentation on theme: "Evolving Europeana’s Metadata: from ESE to EDM"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Evolving Europeana’s Metadata: from ESE to EDM

Similar presentations

Presentation on theme: "Evolving Europeana’s Metadata: from ESE to EDM"— Presentation transcript:

Similar presentations

About project

Feedback