The Europeana Natural History Aggregator OpenUp! has published an online tool that supports the automated creation of IIIF manifests out of uploaded EDM metadata.
This guide describes in detail how to use the tool and how your EDM metadata is transformedwhat it delivers.
The tool is currently available in version 1, i.e. it supports the conversion of EDM metadata for digital images hosted in IIIF compliant image servers. Subsequent versions will integrate the creation of IIIF manifests for audio and video data.
The tool is realised in co-operation with Europeana and uses the same IIIF mapping as Europeana. For more information on the mapping see chapter 9 of this guide.
| Table of Contents | ||
|---|---|---|
|
...
After downloading your created manifests, there is one last step to make them accessible: You have to make sure that you unzip the manifests in the correct folder on your server. In our case we would have to store the IIIF manifests in the folder "manifests" on the server "my.IPADDRESS". The storage place must match the path in the service base URL for manifests that you had entered in the upload form.
9 Manifest Creation
| Anchor | ||||
|---|---|---|---|---|
|
For each EDM record, a corresponding IIIF manifest is created and saved as an xml file. For example, if the user provides ten valid EDM records and enters the correct IIIF service base URL for those records, ten manifest xml files are created. The name of each manifest xml file is derived from the name of the corresponding tif image on the image server and looks like this: “manifest_ID.json”
...
The following IIIF manifest fields are created with the EDM2IIIF Manifest Creation tool:
IIIF Manifest field | EDM field |
@context | [ "http://www.w3.org/ns/anno.jsonld", "http://iiif.io/api/presentation/3/context.json" ] |
id | Manifest path for image |
type | „Manifest“ |
label | dc:title or dc:description if dc:title not present |
summary | dc:description, but only if dc:title exists |
metadata | all descriptive elements from edm:ProvidedCHO class like dc:identifier, dc:relation, dc:type etc. |
thumbnail | edm:objects from ore:Aggregation |
homepage | edm:isShownAt from ore:Aggregation |
requiredStatement | dc:rights from edm:WebResource of corresponding edm:isShownBy |
rights | edm:rights from ore:Aggregation |
provider | edm:dataProvider from ore:Aggregation |
seeAlso | dc:source from edm:ProvidedCHO |
service | svcs:has_service from edm:WebResource |
start | edm:isShownBy if at least one edm:hasView exists |
items | edm:isShownBy and all corresponding edm:hasView |
10 EDM enrichment
EDM enrichment in our case is the process of updating the EDM metadata records by providing appropriate descriptions of IIIF resources. Such updating involves the following steps:
...
Goal: You can use the delivered IIIF-enriched EDM metadata records for your further processing as required. In particular, they also serve as templates for describing IIIF resources in exactly your EDM metadata records.
11 Troubleshooting
“name does not exist”:
After a week the EDM Manifest Creation tool deletes a submitted dataset. It is highly possible that the dataset has been removed because of this. Or it is possible that a dataset with this name does not exist at all.
How error is produced: Writing project name in Name input field -> Choosing Track/download harvested dataset as Harvest Protocol -> Submit button
...
“OAI-PMH upload failed”:
This window occurs shows if the OAI-PMH link was not correct or one of the two URL input fields could not be processed correctly.
...
Samples
Original EDM (from OAI provider)
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:edm="http://www.europeana.eu/schemas/edm/" xmlns:dc="http://purl.org/dc/elements/1.1/ " xmlns:dcterms="http://purl.org/dc/terms/ " xmlns:wgs84_pos="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:ore="http://www.openarchives.org/ore/terms/">
...
</ore:Aggregation>
</rdf:RDF>
.json Manifest
{
"@context": [
"http://www.w3.org/ns/anno.jsonld",
...
}
]
}
]
}
Enriched EDM
Please see IIIF&EDM classes and properties for detailed information on how to express IIIF in EDM classes and properties.
<rdf:RDF xmlns:dc="http://purl.org/dc/elements/1.1/ " xmlns:dcterms="http://purl.org/dc/terms/ " xmlns:doap="http://usefulinc.com/ns/doap#" xmlns:edm="http://www.europeana.eu/schemas/edm/" xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:svcs="http://rdfs.org/sioc/services#" xmlns:wgs84_pos="http://www.w3.org/2003/01/geo/wgs84_pos#">
...