• Introduction
• Content Strategy
• Aggregators' Role
• Providing Content
• Technical Requirements
• Case Study
• FAQ

Whether your data comes to Europeana directly or via an aggregator, it must fulfil certain basic requirements:

Your metadata must conform to the Europeana Semantic Elements, a Dublin Core-based set of fields with 12 additional elements necessary for records to display correctly in Europeana. Aggregators are developing tools to help their providers map their data to the Europeana Semantic Elements.

 

Persistent identifier: Because Europeana links from the metadata in our index to the digital object in your site, you must provide a persistent URL: a web location that never changes, so that users of Europeana can always link to the object on your website.

OAI-PMH: The Protocol for Metadata Harvesting is our preferred method of capturing your metadata, so you will need to have implemented OAI-PMH in your system. The alternative is for you to put your data on an FTP server from which we can pick it up.

ESE3.4 documentation

Europeana Semantic Elements specifications v3.4
Metadata mapping and normalisation Guidelines v2.1
Europeana Semantic Elements v3.4 XML Schema | About the Europeana Semantic Elements v3.4 XML Schema

Useful resources

Europeana Rights Guidelines
Technical Report: Archival Digital Object Ingestion into Europeana (ESE-EAD harmonisation) v1.0
Europeana Portal Image policy

ESE3.3 documentation

Europeana Semantic Elements specifications v3.3.1
Metadata mapping and normalisation Guidelines v2.0.1
Europeana Semantic Elements v3.3 XML Schema | About the Europeana Semantic Elements v3.3 XML Schema
Content Checker Guide v3.3