The Europeana Data Model (EDM) is the metadata framework that underpins Europeana, Europe's digital platform for cultural heritage. It provides a shared data model for aggregating metadata from thousands of libraries, museums, archives, and audiovisual collections across Europe, enabling unified discovery of tens of millions of cultural objects through the Europeana portal. EDM replaced an earlier metadata model based on Dublin Core (Europeana Semantic Elements) and represented a significant shift toward a richer, more expressive Linked Data approach to cultural heritage aggregation.
Background
Europeana launched in 2008 as a single access point for digital cultural heritage across European institutions. The initial metadata approach, based on a flat Dublin Core profile, quickly proved inadequate for representing the complex relationships inherent in cultural heritage data. Development of EDM began around 2010 under the leadership of the Europeana Foundation, with input from the library, museum, and archive communities. The model was designed to accommodate the diverse descriptive traditions of these sectors while enabling meaningful cross-domain search and browsing.
EDM was shaped by several EU-funded projects, including Europeana v2.0 and EuropeanaConnect, which brought together metadata experts from across the cultural heritage sector. The result was a model that could accept data described according to very different conventions and standards while maintaining semantic coherence at the aggregation level.
Purpose and Scope
EDM provides a framework for representing digital cultural heritage objects and their contextual information. It is not a replacement for domain-specific standards but rather an integration layer that enables interoperability across different metadata traditions. Providers map their native metadata (in MARC, LIDO, EAD, Dublin Core, or other formats) into EDM for ingest by the Europeana aggregation infrastructure.
The model centers on several key concepts: a Provided Cultural Heritage Object (the thing being described), one or more Web Resources (digital representations), and an Aggregation that binds them together with information about the providing institution. EDM also represents contextual entities such as Agents (people and organizations), Places, Time Spans, and Concepts (subject terms), enabling enrichment and linking beyond what providers supply.
Key Classes and Properties
EDM builds on and extends several established vocabularies:
| Class / Pattern | Origin | Role in EDM |
|---|---|---|
| ore:Aggregation | OAI-ORE | Groups a cultural object with its digital representations and provider |
| edm:ProvidedCHO | EDM | The cultural heritage object being described |
| edm:WebResource | EDM | A specific digital representation (image, video, text) |
| edm:Agent | EDM (modeled on FOAF) | A person or organization related to the object |
| edm:Place | EDM | A geographic location |
| edm:TimeSpan | EDM | A date or date range |
| skos:Concept | SKOS | A subject term or thematic concept |
Properties are drawn from Dublin Core Terms, SKOS, OAI-ORE, and EDM's own namespace, with the mapping guidelines specifying which properties apply to which classes and their obligation levels (mandatory, recommended, or optional).
Serializations and Technical Formats
EDM data is expressed primarily in RDF/XML for ingest into the Europeana infrastructure. An XML Schema (XSD) defines the structure for validation, and Schematron rules provide additional constraints. The schema files are maintained on GitHub in the metis-schema repository. Although the underlying model is RDF-based, most providers interact with EDM through the XML serialization rather than producing arbitrary RDF.
The EDM namespace URI is http://www.europeana.eu/schemas/edm/.
Governance and Maintenance
EDM is maintained by the Europeana Foundation, based in The Hague, Netherlands. The Europeana R&D team publishes an EDM roadmap outlining short- and long-term development plans. Changes to EDM are implemented incrementally; not all classes and properties defined in the formal specification are necessarily available in the production system at any given time. The mapping guidelines document the currently active subset.
The current formal specification is the EDM Definition v5.2.8 (October 2017), while mapping guidelines continue to be updated through the Europeana Confluence wiki.
Notable Implementations
EDM is used by the Europeana aggregation infrastructure, which as of 2025 provides access to over 50 million items from more than 3,000 cultural heritage institutions. National and thematic aggregators across Europe produce EDM-formatted metadata as part of the ingest pipeline. The model has also influenced other cultural heritage aggregation efforts and has been adopted or adapted by projects beyond the Europeana ecosystem.
EDM profiles and extensions have been developed for specific domains, including natural history, newspapers, and 3D cultural heritage objects.
Related Standards
- Dublin Core -- EDM reuses many Dublin Core Terms properties for basic descriptive metadata.
- SKOS -- Used for representing concepts and controlled vocabularies in EDM.
- OAI-ORE -- Provides the aggregation pattern that is central to EDM's architecture.
- CIDOC-CRM -- EDM's event-based modeling of contextual entities draws on CIDOC-CRM concepts.
Europeana Foundation