Page Comparison

Step 1

...

Tip
Data provider fills out the request form: https://europeana.atlassian.net/servicedesk/customer/portal/5/group/11/create/96

Step 2

...

Metadata coordinator reviews the vocabulary based on the information provided in the request form.

...

Tip

Vocabulary must content negotiate to RDF/XML  It must be openly licensed (CC BY, or CC BY-SA by exception) or dedicated to the public domain  It has to follow the recommendations for structure and representation of values and languages described in 2.4.4. sub-section about quality High level of semantic relationships, especially incoming and outgoing links with other vocabularies like, for example, Wikidata is a crucial criteria. Equivalence can be expressed using, for example, owl:sameAs or skos:exactMatch. Priority is given to vocabularies with multilingual coverage of metadata as they improve language accessibility of information published in Europeana

Step 3

...

After the initial review, Europeana Operations team is consulted.

Europeana reserves the right to turn down the request if the vocabulary is not fulfilling the specified criteria and is not suitable for Europeana dereferencing efforts. Data provider is informed about the decision and reasoning behind it.

Step 4

...

If vocabulary is fulfilling the criteria, metadata coordinator checks which RDF/XML data profile the vocabulary content negotiates to - we make a request to URI with the Accept header “application/rdf+xml.” xml” - and creates a crosswalk between the format and EDM. It is possible that the vocabulary supports more than one data profile (preferably, vocabulary is based on standard data models, like, for example, SKOS). Library of Congress Subject Headings (LCSH), for example, supports SKOS as well as MADS, as is evident from this response. It is under the discretion of the Metadata Coordinator to select the data format that is most suitable for transformation.

Step 5

...

Metadata coordinator creates the contextual mapping (i.e. crosswalk) that focuses on overlaps between selected data profile and EDM contextual class. This can be done in partnership with the data provider who submitted the request.

Step 6

...

Metadata coordinator uses the contextual mapping as a general guidance for creating XSL stylesheet with a template for transforming vocabulary to EDM.

...

If language coverage of the vocabulary goes beyond the languages supported by Europeana, the XSL stylesheet will leave out any unsupported values.

Step 7

...

The Manager of Aggregation Systems team adds the XSL stylesheet to Metis and publishes it on GitHub. All supported vocabularies are also listed in this spreadsheet.

Example

...

- Dereferencing of LCSH vocabulary

Because LCSH vocabulary is in line with Europeana’s criteria for supported vocabularies, contextual mapping between SKOS and EDM contextual class skos:Concept was created.

Based on the crosswalk, XSL stylesheet was written and it is now used for LCSH dereferencing.

For example, when you run the XSLT process on this record this is the output:

<?xml version="1.0" encoding="UTF-8"?>
<skos:Concept xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
              xmlns:skos="http://www.w3.org/2004/02/skos/core#"
              xmlns:skosxl="http://www.w3.org/2008/05/skos-xl#"
              rdf:about="http://id.loc.gov/authorities/subjects/sh85085171">
   <skos:prefLabel xml:lang="en">Military ceremonies, honors, and salutes</skos:prefLabel>
   <skos:altLabel xml:lang="en">Military courtesy</skos:altLabel>
   <skos:altLabel xml:lang="en">Military honors</skos:altLabel>
   <skos:altLabel xml:lang="en">Military salutes</skos:altLabel>
   <skos:altLabel xml:lang="en">Salutes, Military</skos:altLabel>
   <skos:broader rdf:resource="http://id.loc.gov/authorities/subjects/sh85045446"/>
   <skos:narrower rdf:resource="http://id.loc.gov/authorities/subjects/sh85090372"/>
   <skos:narrower rdf:resource="http://id.loc.gov/authorities/subjects/sh2012001521"/>
   <skos:narrower rdf:resource="http://id.loc.gov/authorities/subjects/sh2003009031"/>
   <skos:narrower rdf:resource="http://id.loc.gov/authorities/subjects/sh85145907"/>
   <skos:narrower rdf:resource="http://id.loc.gov/authorities/subjects/sh85085200"/>
   <skos:narrower rdf:resource="http://id.loc.gov/authorities/subjects/sh2018002201"/>
   <skos:closeMatch rdf:resource="http://id.worldcat.org/fast/1021060"/>
   <skos:closeMatch rdf:resource="http://data.bnf.fr/ark:/12148/cb12129082c"/>
   <skos:closeMatch rdf:resource="http://data.bnf.fr/ark:/12148/cb12129082c"/>
   <skos:closeMatch rdf:resource="http://id.worldcat.org/fast/1021060"/>
   <skos:inScheme rdf:resource="http://id.loc.gov/authorities/subjects"/>
</skos:Concept>

Once XSL stylesheet is added to Metis, the following happens during Enrichment step:

Metis finds dereferenceable URI in the data:

<ore:Proxy rdf:about="/proxy/provider/14/UEDIN_214">

  <dc:subject rdf:resource="http://id.loc.gov/authorities/subjects/sh85085171"/>

  [ OTHER PROVIDER PROXY DATA ]

</ore:Proxy>

2. Using XSL stylesheet Metis converts entity to EDM structure and adds it to the record. The link now resolves within the record:

<ore:Proxy rdf:about="/proxy/provider/14/UEDIN_214">
   <dc:subject rdf:resource="http://id.loc.gov/authorities/subjects/sh85085171"/>

  [ OTHER PROVIDER PROXY DATA ]

</ore:Proxy>


<skos:Concept rdf:about="http://id.loc.gov/authorities/subjects/sh85085171">
   <skos:prefLabel xml:lang="en">Military ceremonies, honors, and salutes</skos:prefLabel>
   <skos:altLabel xml:lang="en">Military courtesy</skos:altLabel>
   <skos:altLabel xml:lang="en">Military honors</skos:altLabel>
   <skos:altLabel xml:lang="en">Military salutes</skos:altLabel>
   <skos:altLabel xml:lang="en">Salutes, Military</skos:altLabel>
   <skos:broader rdf:resource="http://id.loc.gov/authorities/subjects/sh85045446"/>

  [ OTHER PROPERTIES OF CONTEXTUAL OBJECT ]

</skos:Concept>

...