EDM mappings, refinements and extensions
Here is an overview of EDM mappings, refinements or extensions developed by Europeana and its data providers.
Disclaimer: The following profiles don’t provide guidelines for submitting data to Europeana and are not (all) supported by Europeana for data submission. They are nevertheless great assets for EDM implementers or communities working around the same topics.
As Europeana developes new data features, it refines and extends the Europeana Data Model (EDM) to accommodate new requirements.
Europeana’s data providers are doing a similar work by extending and refining EDM to minimise the loss of data from their original metadata format during the conversion to EDM.
This section provides an overview of all the EDM mappings, refinements or extensions developed by Europeana and its data providers:
- A mapping to EDM is any kind of specification (e.g., a concordance table) of relationships and equivalences between two metadata formats or models, e.g., between EDM and another metadata schema.
- A refinement of EDM or EDM Application Profile is any kind of specialisation of EDM to meet specific needs of the data provider.
- An extension to EDM is required when existing EDM classes and properties cannot represent the semantics of providers’ data with sufficient details.
Further details on the definitions of these are provided in the Report from the Task Force on EDM mappings, refinements and extensions.