Skip to content

EDM: resolve vocabulary items by id or URI to value #3

Description

@twagoo

Europeana records from the newspapers collections (possibly also others) use various identifiers for e.g. subject or resource type values that could be resolved to make the metadata better suitable for indexing into the VLO.

  • IDs of the library of congress subject headers appear as subject values, e.g. <dc-subject>sh85091614</dc-subject> (full record), which is a reference to http://id.loc.gov/authorities/subjects/sh85091614 "Newspapers--Sections, columns, etc" (skos RDF)

    • These always take the form of /sh[0-9]+/ as text content within dc:subject elements. The concept URIs don't appear to be used, i.e. no @rdf:resource.
  • Resource types are often encoded with concepts from the Getty Art and Architecture Thesaurus, which are included in expanded form in the RDF/XML representations harvested. Rather than rendering the full content we could also detect these and do a lookup or trim down the provided values to only include the most relevant information.

    • Example from the RDF: <dc:type xmlns:dc="http://purl.org/dc/elements/1.1/" rdf:resource="http://vocab.getty.edu/aat/300026656"/>, which is expanded in the conversion to CMDI with all content found in the concept definition also included in the RDF/XML served by Europeana's OAI provider (in this case ten altLabels/prefLabels in different languages: Tageblätter, tidning, newspaper etc).

An example EDM record and its current CMDI conversion:
BibliographicResource_30001170701972017.xml (RDF/XML)
BibliographicResource_30001170701972017.cmdi (CMDI)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions