Meghini - Europeana Data Model @EUscreen Mykonos

1,382 views
1,254 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,382
On SlideShare
0
From Embeds
0
Number of Embeds
64
Actions
Shares
0
Downloads
20
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Meghini - Europeana Data Model @EUscreen Mykonos

  1. 1. A look at the Europeana Data Model Carlo Meghini, Stefan Gradmann, Antoine Isaac EUScreen Workshop on Metadata Mykonos, June 24, 2010
  2. 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. 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. 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. 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. 6. The general picture Mykonos, June 24, 2010 EUScreen Workshop on Metadata 6 6
  7. 7. The class taxonomy Mykonos, June 24, 2010 EUScreen Workshop on Metadata 7 7
  8. 8. Property taxonomy (without ESE properties) Mykonos, June 24, 2010 EUScreen Workshop on Metadata 8
  9. 9. The Example - 1 Mykonos, June 24, 2010 EUScreen Workshop on Metadata 9 9
  10. 10. The Example - 2 Mykonos, June 24, 2010 EUScreen Workshop on Metadata 10
  11. 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. 12. Has View Mykonos, June 24, 2010 EUScreen Workshop on Metadata 12
  13. 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. 14. So we create Proxies Mykonos, June 24, 2010 EUScreen Workshop on Metadata 14
  15. 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. 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. 17. Landing Page Mykonos, June 24, 2010 EUScreen Workshop on Metadata 17
  18. 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. 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. 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. 21. Contextualization property taxonomy Mykonos, June 24, 2010 EUScreen Workshop on Metadata 21
  22. 22. hasMet/isAbout with simple values Mykonos, June 24, 2010 EUScreen Workshop on Metadata 22 22
  23. 23. hasMet/isAbout & fully-fledged contextualization Mykonos, June 24, 2010 EUScreen Workshop on Metadata 23
  24. 24. Reminder: classes for context entities Who, what, when, where Mykonos, June 24, 2010 EUScreen Workshop on Metadata 24
  25. 25. Enabling event-aware descriptions: Was Present At, Happened At, Occurred At Mykonos, June 24, 2010 EUScreen Workshop on Metadata 25
  26. 26. Mykonos, June 24, 2010 EUScreen Workshop on Metadata 26
  27. 27. Amphora of Tuthmosis III Mykonos, June 24, 2010 EUScreen Workshop on Metadata 27 27
  28. 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. 29. Has Part Mykonos, June 24, 2010 EUScreen Workshop on Metadata 29
  30. 30. Properties for Versioning & Derivating Mykonos, June 24, 2010 EUScreen Workshop on Metadata 30
  31. 31. Is Representation Of Mykonos, June 24, 2010 EUScreen Workshop on Metadata 31 31
  32. 32. More information •  EDM Specification •  EDM Primer Mykonos, June 24, 2010 EUScreen Workshop on Metadata 32 32
  33. 33. Thank you! • Questions Mykonos, June 24, 2010 EUScreen Workshop on Metadata 33

×