Fondly Collisions: Archival hierarchy and the Europeana Data Model
0 likes1,254 views
This document discusses representing archival hierarchies in Europeana using the Europeana Data Model (EDM). It provides an example of converting a finding aid encoded in EAD to EDM to represent the hierarchical structure. Remaining challenges include representing hierarchies when metadata or digital representations are missing for certain levels. Publishing hierarchical data for both developers and end users is discussed.
Fondly Collisions: Archival hierarchy and the Europeana Data Model
- 1. Fondly Collisions: Archival hierarchy and the Europeana Data Model Valentine Charles and Kerstin Arnold 8th October 2014, DCMI2014, Austin
- 2. Overview The Archives Portal Europe - Introduction • Projects and content • Standards and tools Europeana - Introduction • Content and ecosystem Europeana - Data models • From Europeana Semantic Elements (ESE) to the Europeana Data Model (EDM) • Semantic layer • Representing hierarchies
- 3. Overview An example • Representation in EDM • How to get there - conversion in the Archives Portal Europe’s dashboard • From apeEAD to EDM - a comparison Remaining challenges Preview
- 4. The Archives Portal Europe The projects behind ● APEnet (2009-2012) with 13 partners (incl. Europeana), extended to 19 partners until the end of the project ● APEx (2012-2015) with 29 partners, extended to currently 33 partners After the projects: Archives Portal Europe Foundation to maintain and enhance the portal, its network and its position within the European (digital) cultural heritage environment
- 5. The Archives Portal Europe The current status ● 30 countries represented, 27 providing content ● 683 institutions, 435 providing content ● more than 50M descriptive units in 335K+ EAD files, 2M linked with digital archival objects ● 1044 descriptions of records creators
- 6. The Archives Portal Europe The use of standards - profiles for central use ● apeEAD for finding aids, holdings guides and source guides ● apeEAC-CPF (Encoded Archival Context - Corporate Bodies, Persons, and Families) for descriptions of records creators ● EAG 2012 (Encoded Archival Guide) - for descriptions of archival institutions and their services ● future addition: apeMETS (Metadata Encoding and Transmission Standard) and apeMETSRights for structured information on digital archival objects
- 7. The Archives Portal Europe The use of standards - decentralised responsibility ● local and central tools for conversion and validation of data ● local and central tools for creation/edition of data (especially EAG 2012 and apeEAC-CPF) ● central tool for delivery and processing within the Archives Portal Europe ● central tool for conversion and delivery to Europeana
- 8. Europeana.eu, Europe’s cultural heritage portal 32M objects from 2,200 galleries, museums, archives and libraries Text Image Video Sound 3D CC
- 9. Europeana and its ecosystem Audiovisual collections National Aggregators Regional Aggregators Archives Thematic collections Libraries
- 10. Represent complex data structure: the challenge Initial data model: Europeana Semantic Elements (ESE) and its difficult integration with EAD ESE • flat model based on Dublin Core • item-centric model • no links between cultural heritage objects (CHO) or between objects and contextual entities EAD • highly structured model • hierarchy containing descriptions of digital and non-digital items/objects • nested items/objects with references to contextual entities
- 11. A new data framework: Europeana Data Model (EDM) A data model that re-uses several existing Semantic Web-based models Adopt Semantic Web representation principles (RDF) • Re-use and mix different vocabularies together • Preserve original data and still allow for interoperability
- 12. EDM basic pattern A data provider submits to Europeana a “bundle” of an object and its digital representation(s)
- 13. Connect Archives to the other domains Create a “semantic layer” on top of cultural heritage objects
- 14. Representing hierarchies in EDM Hierarchies in EDM can be built at the level of • ProvidedCHO • the hierarchy focuses on the description of the semantic structure of the object (fonds, series, subseries, file, item) • WebResources (images, scans) • hierarchies of the digitised representations of a ProvidedCHO • Contextual resources • hierarchies of “non-information resources” or contextual resources such as edm:Agent, edm:Place, edm:TimeSpan, edm:Concept, edm:Event
- 15. An example
- 16. An example - representation in EDM
- 17. An example - representation in EDM
- 20. An example - Converting a finding aid to EDM
- 21. An example - Converting a finding aid to EDM
- 22. An example - Converting a finding aid to EDM
- 23. An example - Converting a finding aid to EDM
- 24. An example - Converting a finding aid to EDM
- 25. An example - Converting a finding aid to EDM
- 26. An example - Converting a finding aid to EDM
- 27. An example - Converting a finding aid to EDM
- 28. An example - Converting a finding aid to EDM quick note on future extensions ● include apeEAC-CPF for conversion to edm:Agent ● use apeMETS/apeMETSRights for more detailed input on digital archival objects, their relations and their rights status
- 29. An example - Converting a finding aid to EDM
- 30. An example - apeEAD / fonds
- 31. An example - EDM / fonds
- 32. An example - EDM / fonds
- 33. An example - apeEAD / hierarchy
- 34. An example - EDM / hierarchy (I)
- 35. An example - EDM / hierarchy (II)
- 37. Some challenges remain Representing hierarchies with one level missing metadata • when a missing ProvidedCHO is an inner node (i.e. it has children) it could imply losing information about the context of the children CHOs.
- 38. Some challenges remain Representing hierarchies with one level missing a digital representation
- 39. Publishing data: for data consumers Hierarchical data are available via • data.europeana.eu, Europeana Linked Data pilot • Europeana API • Structured data for search engines (Schema.org markups) • One of the challenges is to make developers understand a specific structure of the data.
- 40. Publishing data: for end-users Displaying hierarchical objects has been Europeana’s biggest challenge! • Searching hierarchical objects • It should be possible • to make search queries on the objects contained in a hierarchy • to make search queries in all the levels of descriptions of an object • to search an object via information on its context • to allow a user to find the different objects of a hierarchy
- 41. Publishing data: for end-users Presentation of the hierarchies • A user should be able to grasp a complex object as a whole and understand the relationships between the different objects, of which the hierarchy is composed. • An object should be always presented in context (digital representation and descriptive metadata if possible).
- 42. Preview!
- 43. Preview!
- 44. Thank you ! valentine.charles@europeana.eu k.arnold@bundesarchiv.de www.europeana.eu www. pro.europeana.eu www.archivesportaleurope.net www.apex-project.eu 8th October 2014, DCMI2014, Austin