The document discusses the Europeana Data Model (EDM), which provides a framework for representing digital cultural heritage resources and their metadata. EDM aims to enable rich search functionality through standardized representations and connections between different metadata schemas. It pursues interoperability by mapping metadata values and linking to external knowledge sources. EDM has evolved over multiple versions to increasingly integrate metadata from different cultural heritage institutions and domains. Key aspects of EDM include representing objects and their related resources, contextualizing objects, and modeling versioning and derivation relationships between resources.

1. A look at the Europeana
Data Model
Carlo Meghini, Stefan Gradmann, Antoine Isaac
EUScreen Workshop on Metadata
Mykonos, June 24, 2010

2. 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 EUScreen Workshop on Metadata 2

3. 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
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 3

4. History
• ESE
• quickly set up prototypes
• keep barriers low
• build on Dublin Core
• Rhine based on ESE V3.2
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 4

5. 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
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 5

6. The general picture
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 6 6

7. The class taxonomy
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 7 7

8. Property taxonomy (without ESE properties)
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 8

9. The Example - 1
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 9 9

10. The Example - 2
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 10

11. Providing an aggregation of digital resources for
a cultural object
RDF graph with specific conventions for resource types and sub-properties
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 11

12. Has View
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 12

13. 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!
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 13

14. So we create Proxies
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 14

15. Becomes really handy when there are several
records for a same object
Berlin, June 24, 2010
Mykonos, Jan. Europeana Librarian
EUScreen Workshop on Metadata 15 15
25-26, 2010 Community
Meeting20100324

16. And there are always several information
providers: think of Europeana!
Berlin, June 24, 2010
Mykonos, Jan. EUScreen Workshop on Metadata 16 16
25-26, 2010

17. Landing Page
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 17

18. Back to proxies: don’t look at that!
Berlin, June 24, 2010
Mykonos, Jan. EUScreen Workshop on Metadata 18 18
25-26, 2010

19. Remember: one provider may not need to submit
data for everything
Europeana should take care of maintaining the whole structure
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 19

20. 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
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 20

21. Contextualization property taxonomy
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 21

22. hasMet/isAbout with simple values
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 22 22

23. hasMet/isAbout & fully-fledged contextualization
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 23

24. Reminder: classes for context entities
Who, what, when, where
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 24

25. Enabling event-aware descriptions:
Was Present At, Happened At, Occurred At
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 25

26. Mykonos, June 24, 2010 EUScreen Workshop on Metadata 26

27. Amphora of Tuthmosis III
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 27 27

28. Advanced EDM
• Relations between “provided” objects
• Part-whole links for complex objects
• Derivation and versioning relations
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 28

29. Has Part
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 29

30. Properties for Versioning & Derivating
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 30

31. Is Representation Of
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 31 31

32. More information
• EDM Specification
• EDM Primer
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 32 32

33. Thank you!
• Questions
Mykonos, June 24, 2010 EUScreen Workshop on Metadata 33