Metadata Tier B

Metadata Tier B (Europeana website as an exploration platform)

If you want to increase the visibility of your content through our thematic collections and other browse entry points, at least 50% of the provided metadata elements that are relevant need to have at least one language tag. The metadata should now include at least three enabling elements covering at least two distinct discovery and user scenarios and one contextual class with all minimum required elements or link to LOD vocabulary (also with all minimum required elements).


At least 50% of the metadata elements from ProvidedCHO that are relevant have at least one language qualified value.

Metadata elements in ProvidedCHO

  • dc:coverage

  • dc:description

  • dc:format

  • dc:relation

  • dc:rights

  • dc:source

  • dc:subject

  • dc:title

  • dc:type

  • dcterms:alternative

  • dcterms:hasPart

  • dcterms:isPartOf

  • dcterms:isReferencedBy

  • dcterms:medium

  • dcterms:provenance

  • dcterms:references

  • dcterms:spatial

  • dcterms:tableOfContents

  • dcterms:temporal

  • edm:currentLocation

  • edm:hasType

  • edm:isRelatedTo

Enabling elements

At least three distinct metadata elements taken from two distinct ‘Discovery scenario’ groups present in the edm:ProvidedCHO class

Discovery scenarios

Enabling elements

Browse by date or time-span

dcterms:issued, dcterms:created, dcterms:temporal, edm:hasMet (with a link to an edm:TimeSpan that is present in the record)

Browse by subjects and types

dc:subject (with a link to a skos:Concept), dc:format, dc:type, dcterms:medium

Browse by agents

dc:creator, dc:contributor, dc:publisher, dc:subject (with a link to a edm:Agent that is present in the record), edm:hasMet (with a link to a edm:Agent that is present in the record)

Browse by places

dc:subject (with a link to a edm:Place that is present in the record), dcterms:spatial, edm:currentLocation

Contextual classess

At least one contextual class with all minimum required elements, OR link to a LOD vocabulary we support.

Contextual resource referred by the ProvidedCHO: A contextual entity (an instance of a contextual class such as edm:Agent, skos:Concept, edm:Place, edm:TimeSpan) that is linked directly from edm:ProvidedCHO (ie. Provider's ore:Proxy) and therefore ignoring contextual resources that are only linked from other contextual resources via e.g. placeOfBirth.


Example record

<rdf:RDF> ... <edm:ProvidedCHO rdf:about="#exampleMetB"> <dc:title xml:lang="en">Metadata Example Record Tier B</dc:title> <dc:subject rdf:resource=""/> <dc:type>Bound item</dc:type> <dcterms:created>1951</dcterms:created> <dcterms:isPartOf>Europeana Foundation Example Records</dcterms:isPartOf> <edm:type>IMAGE</edm:type> </edm:ProvidedCHO> <ore:Aggregation rdf:about="#exampleMetB_AGG"> <edm:aggregatedCHO rdf:resource="#exampleMetB"/> <edm:dataProvider>Europeana Foundation</edm:dataProvider> <edm:isShownBy rdf:resource=""/> <edm:provider>Europeana Foundation</edm:provider> <edm:rights rdf:resource=""/> </ore:Aggregation> </rdf:RDF>


For more details, see page .