meghini - europeana data model @euscreen mykonos

A look at the Europeana Data Model

Carlo Meghini, Stefan Gradmann, Antoine Isaac

EUScreen Workshop on Metadata

Mykonos, June 24, 2010

Rationale

• Rich functionality (semantic search) requires rich representations

• Rich representations exists: collect them (1) • Interoperability is the problem:

• models: connect (2) •  values: normalize (3)

• Multilingualism cuts across • Need a lot of knowledge: link (4)

Mykonos, June 24, 2010 2 EUScreen Workshop on Metadata

Tools

• Collect existing metadata as they are: OAI ORE • Connect classes and properties: basic ontology

(CIDOC CRM, DC, SKOS, VRA) + mappings • Web architecture, in particular URIs • Link metadata to existing resources

•  Linked Open Data


History

• ESE •  quickly set up prototypes •  keep barriers low •  build on Dublin Core •  Rhine based on ESE V3.2


EDM development

•  version 1: initial surrogate model with rich set of contextualization properties

•  version 2: OAI-ORE aggregations and SKOS concepts

•  release 2: 1st Europeana plenary •  version 3 •  version 4: IRW ontology

•  release 1: December 2009 •  release 2: February 2009

•  version 5: integration of ESE, evaluation through domain meetings

•  release 1: April 2010 •  release 2: next week

5 EUScreen Workshop on Metadata Mykonos, June 24, 2010

The general picture

6 Mykonos, June 24, 2010 6 EUScreen Workshop on Metadata

The class taxonomy


Property taxonomy (without ESE properties)


The Example - 1


The Example - 2


Providing an aggregation of digital resources for a cultural object

RDF graph with specific conventions for resource types and sub-properties


Has View


Modeling Mona Lisa

•  There’s a resource that stands for Mona Lisa as an object in Museum

•  Ideally identified by a URI assigned by Direction des musées de France •  classified using a DMF ontology • But DMF has a specific description for that object

• Other institutions might have a different one!


So we create Proxies


Becomes really handy when there are several records for a same object

Berlin, Jan. 25-26, 2010

15 Europeana Librarian Community Meeting20100324


And there are always several information providers: think of Europeana!

Berlin, Jan. 25-26, 2010


Landing Page


Back to proxies: don’t look at that!

Berlin, Jan. 25-26, 2010


Remember: one provider may not need to submit data for everything

Europeana should take care of maintaining the whole structure


Now for metadata describing the object

• EDM is flexible • Common, simple object-centric approaches • More sophisticated event-aware approaches •  In fact, any approach?

• Crucial principle: mapping • Keep original metadata • Map to more general interoperability level


Contextualization property taxonomy


hasMet/isAbout with simple values


hasMet/isAbout & fully-fledged contextualization


Reminder: classes for context entities

Who, what, when, where


Enabling event-aware descriptions: Was Present At, Happened At, Occurred At


Amphora of Tuthmosis III


Advanced EDM

• Relations between “provided” objects •  Part-whole links for complex objects •  Derivation and versioning relations


Has Part


Properties for Versioning & Derivating


Is Representation Of


More information

32

•  EDM Specification •  EDM Primer


Thank you!

• Questions


meghini - europeana data model @euscreen mykonos

Technology