General EDM template
Table of Contents
1. Europeana Data Model (EDM) Template for use with University of Chicago Library Digital Collections
2. Triple Types
All triples should be typed. Choose from among these types.
a ore:ResourceMap
a ore:Aggregation
a edm:ProvidedCHO
a ore:Proxy # optional
a edm:WebResource
a rdfs:Resource # This is the default type. Use it when
none of the preceding apply.
Of the above, the ore:Resource Map and ore:Proxy are optional.
3. Required Elements
In this section, mandatory Europeana elements are indicated by boldface. Mandatory Europeana elements governed by either/or or if/then statements are indicated by italics. Mandatory elements required by local usage are underlined.
The following is with reference to Definition of the Europeana Data Model v5.2.8 06/10/2017 and the EDM Mapping Guidelines.
3.1. ore:ResourceMap
The following are required for an ore:ResourceMap, which is optional. The requirements are indicated by example.
<b20x2w73r321/rem>
dcterms:creator "https://node.uchicago.edu/" ;
dcterms:created "2022-02-09T11:21:52-06:00"^^xsd:dateTime ;
dcterms:modified "2022-02-09T11:21:52-06:00"^^xsd:dateTime ;
ore:describes <b20x2w73r321/aggregation> ;
a ore:ResourceMap .
Note that when an ore:ResourceMap is being created, the values of dcterms:created and dcterms:modified are the same.
3.2. ore:Aggregation
The following are mandatory Europeana elements for the ore:Aggregation.
- Either edm:isShownAt "The URL of a web view of the object in full information context. If there is no edm:isShownAt for an object, there must be a edm:isShownBy. If both are available, provide both. The use of edm:isShownBy is preferred." (EDM Mapping Guidelines) The example given in the EDM documentation is <edm:isShownAt rdf:resource="http://www.mimo-‐db.eu/UEDIN/214%22/>. This is clearly a website.
- edm:isShownBy "The URL of a web view of the object. An edm:isShownBy must be provided. If there is no edm:isShownBy for an object, there must be a edm:isShownAt. The use of edm:isShownBy is preferred." (EDM Mapping Guidelines) The example given in the EDM documentation is <edm:isShownBy rdf:resource="
>. This is clearly something of a type which we might provide out of the Library Digital Repository via IIIF, e.g., edm:isShownBy <b20b66b16m9w/file.pdf>. - edm:rights
By convention, we indicate edm:isShownAt by the URL of the mapping ARK identifier (for this terminology, see https://datatracker.ietf.org/doc/html/draft-kunze-ark-28#name-ark-anatomy), and edm:isShownBy by appending ``/pres'' to the mapping ARK identifier if the file is going to be retrieved from the OCFL disk hierarchy; otherwise, it should have its own mapping ARK identifier, e.g., if it is going to be served by an external system such as Panopto.
Local usage specifies the following:
uchicago:inCollection <http://lib.uchicago.edu/uchicagonode>
In addition to uchicago:inCollection <http://lib.uchicago.edu/uchicagonode>, which local usage requires for the edm:ProvidedCHO, one or more additional uchicago:inCollection predicates should be specified, for example, <http://lib.uchicago.edu/chopin-early-editions> in the case of Chopin Early Editions.
The following is an example of an ore:Aggregation. The order is specified by Europeana's documentation.
<b20x2w73r321/aggregation>
edm:aggregatedCHO <b20x2w73r321> ;
edm:dataProvider "University of Chicago Library" ;
edm:isShownAt <b20x2w73r321> ;
edm:isShownBy <b20x2w73r321/pres> ;
edm:object "https://www.lib.uchicago.edu/dl/images/audio.jpg" ;[1]
edm:provider "University of Chicago Library" ;
edm:rights "https://rightsstatements.org/vocab/NoC-US/1.0/" ;[2]
uchicago:inCollection <lib.uchicago.edu/uchicagonode>, <lib.uchicago.edu/mesoamerican-languages-collection>, <lib.uchicago.edu/online-language-archive> ;
ore:isDescribedBy <b9m865s34c01/rem> ;
a ore:Aggregation .
See also https://github.com/uchicago-library/UChicagoNode/wiki/Notes for collections which may belong to more than one collection other than <lib.uchicago.edu/uchicagonode>.
The ore:Aggregation may contain edm:hasView (the value is a link to edm:WebResource). See https://europeana.atlassian.net/wiki/spaces/EF/pages/2106032160/ore+Aggregation#edm%3AhasView for usage.
[1] The URL of a representation of the CHO which will be used for generating previews for use in the Europeana portal. This may be the same URL as edm:isShownBy. … This must be an image, even if it is for a sound object. https://europeana.atlassian.net/wiki/spaces/EF/pages/2106032160/ore+Aggregation#edm%3Aobject
[2] Copyright metadata needs to be provided for every digital object submitted to Europeana and has to be mapped either to edm:rights … For additional copyright information dc:rights may be used. https://europeana.atlassian.net/wiki/spaces/EF/pages/1503756289/Providing+copyright+metadata+to+Europeana#Available-values Ideally [dc:rights] should be applied to the edm:WebResource or the edm:ProvidedCHO. https://europeana.atlassian.net/wiki/spaces/EF/pages/2106032160/ore+Aggregation#dc%3Arights
3.3. edm:ProvidedCHO
The following are mandatory Europeana elements for the edm:ProvidedCHO. For local usage see also Required Elements, which should be in agreement with what is stated here.
- Either dc:description or dc:title or both.
- One or more the following: dc:subject, dc:type, dc:coverage, dcterms:spatial, dcterms:temporal. "… if more than one of these properties is available, please provide them all."
Local usage requires dc:type. Values should be drawn from the DCMI Type Vocabulary. These are Collection, Dataset, Event, Image, InteractiveResource, MovingImage, PhysicalObject, Service, Software, Sound, StillImage, Text. ``Note that digital representations of, or surrogates for, [PhysicalObject] should use Image, Text or one of the other types.''
- dc:language for TEXT objects. It is strongly recommended for other object types if there is a language aspect. Language codes conforming to ISO 639 are used as values.
- edm:type must occur and must use one of the following values (in upper case): TEXT, IMAGE, SOUND, VIDEO or 3D. Map DCMI types to EDM types as follows:
Image : IMAGE MovingImage : VIDEO Sound : SOUND StillImage : IMAGE Text : TEXT
In addition to what is specified above, the following is also required by local usage for the edm:ProvidedCHO.
- dc:identifier. String-literal values for locally-created ARK identifiers are used, e.g., "https://ark.lib.uchicago.edu/ark:61001/z9m865s34c01".
- uchicago:identifier. String-literal values assigned by the Digitization Unit are used, e.g., "G4104-C6-1933-U5-a".
For the following, see ``DCMI Kernel Metadata Community: Kernel Metadata and Electronic Resource Citations (ERCs)'', Section 3, Kernel Stories. (https://www.dublincore.org/groups/kernel/spec/#anchor3) They will support responses to queries about the metadata when the appropriate syntax is provided to an ARK resolver: ``ARK resolvers must support the `?info' inflection for requesting metadata.'' (https://datatracker.ietf.org/doc/html/draft-kunze-ark-28#section-1.2) See further in that document for the ?info inflection and the use of Electronic Resource Citations [ERCs].)
- erc:who The value is drawn from dc(terms):creator, dc(terms):contributor, or dc(terms):publisher, in that order. If none of those have values, then use erc:who ``(:unkn) unknown''.
- erc:what The value is drawn from dc:title or dc:description, in that order.
- erc:when String-literal values conforming to ISO 8601 or the Extended Date/Time Format Specification (EDTF) are used in that order. If a date is not supplied, then use erc:when ``(:unkn) unknown''.
- erc:where The value is drawn from dc:identifier, which must be present.
Any values which cannot be assigned should be drawn from ``DCMI Kernel Metadata Community: Kernel Metadata and Electronic Resource Citations (ERCs)'', Section 9.3, Special Kernel Standardized Value Codes.
The following is an example of an edm:ProvidedCHO. This example does not include any elements specific to a particular digital collection which may also be included in the edm:ProvidedCHO, for example, from BIBFRAME, VRA Core, etc. It includes only those elements discussed in this section.
<b20x2w73r321>
dc:contributor "Hanks, William F." , "Unnamed contributor (male)" ;
dc:date "1979" ;
dc:description "Contents: \"History of Cooperativa\"" ;
dc:language "spa" , "yua";
dc:title "Yucatec Maya field recordings (Hanks, 1979-1987) Yucatán Maya" ;
dc:identifier "https://ark.lib.uchicago.edu/ark:61001/b20x2w73r321" ;
dc:rights "https://rightsstatements.org/vocab/NoC-US/1.0/" ;
dcterms:spatial "7005600" ;
dcterms:type dcmi:Sound ;
dc:type "Sound";
edm:type "SOUND" ;
uchicago:identifier "G4104-C6-1933-U5-a";
erc:who "Hanks, William F., interviewer; Unnamed contributor (male), consultant" ;
erc:what "Yucatec Maya field recordings (Hanks, 1979-1987) Yucatán Maya" ;
erc:when "1979" ;
erc:where "https://ark.lib.uchicago.edu/ark:61001/b20x2w73r321" ;
a edm:ProvidedCHO .
3.4. ore:Proxy
The following are required for an ore:Proxy, which is optional; it is used only if one is associating a file of original descriptive metadata, e.g., MARCXML or Dublin Core, with the aggregation. The requirements are indicated by example.
<b9m865s34c01/file.dc.xml>
dc:format "application/xml" ;
ore:proxyFor <b2nw3wm8552h> ;
ore:proxyIn <b2nw3wm8552h/aggregation> ;
a ore:Proxy .
Note that when an ore:ResourceMap is being created, the values of dcterms:created and dcterms:modified are the same.
3.5. edm:WebResource
The following are required for an edm:WebResource. The requirements are indicated by example.
<b20x2w73r321/file.wav>
ebucore:hasMimeType "audio/x-wav" ;
dcterms:identifier "https://ark.lib.uchicago.edu/ark:61001/b20x2w73r321/file.wav" ;
premis:fixity [
rdf:type <https://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions/sha512> ;
rdf:value "10b1a2959f2229ab52e3873651c1d99036caa1e5d641e0bf257"] ;
premis:originalName "FieldRecording1996-2.wav" ;
premis:size 44694436 ;
a edm:WebResource .
3.6. rdfs:Resource
If rdfs:Resource is used, the following indicates its format. The example is for OCR data for a page object in Campus Publications.
<b2nw3wm8552h/00000001/file.xml>
dc:format "application/xml" ;
a rdfs:Resource . # This is the default type.
Namespaces used in this document:
@base <https://ark.lib.uchicago.edu/ark:61001/> .
@prefix bf: <http://id.loc.gov/ontologies/bibframe/> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix ebucore: <http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#> .
@prefix edm: <http://www.europeana.eu/schemas/edm/> .
@prefix erc: <http://purl.org/kernel/elements/1.1/> .
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix premis: <http://www.loc.gov/premis/rdf/v3/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix uchicago: <http://lib.uchicago.edu/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .