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 transformed.
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.
1 Goal of the EDM2IIIF Manifest Creation tool v01
This guide introduces you to the EDM2IIIF Manifest Creation Tool. It was initially created as a successor of the Image Conversion Guide to facilitate the workflow towards making your digital images IIIF compliant.
IIIF stands for International Image Interoperability Framework (spoken Triple-Eye-F). The framework was created to offer the scientific community a way to productively interact with their digital objects (visual or audio/visual) and use them across different platforms. Here you can learn about the benefits of IIIF.
If you are looking for a general introduction to the IIIF framework, please check out the What is IIIF? training resources for aggregators.
When deciding to use the IIIF standard for publishing your images on the internet there are a few obstacles to take, because: the more images you want to convert and equip with the Image API and the Presentation API, the more time you will have to invest to create IIIF compliant images and manifests. (A IIIF manifest is the package that contains all the information related to a particular digital object, including the image itself as well as the metadata.) The manifest creation tool aims to make this process less time-consuming by automating the creation of IIIF manifests for your images.
With this tool you can:
use EDM metadata (of IMAGE type - cultural heritage objects) to automatically create IIIF manifests for images and enrich the EDM metadata with IIIF descriptions
download the IIIF manifests that were created based on your EDM metadata (about manifest creation details see chapter 9)
download the enriched EDM metadata with IIIF descriptions (about enrichment of EDM details see chapter 10)
2 Where to find the EDM2IIIF Manifest Creation tool
The EDM2IIIF Manifest Creation Tool can be accessed through https://openup.ait.co.at/edm2manifest/ .
This tool was developed in the Python programming language, using the Flask framework. To use this tool, the user only needs Internet connection and a browser.
3 How to prepare your dataset
In order to use the EDM2IIIF Manifest Creation tool you have to prepare your data appropriately. You need to verify that your dataset can be used with the tool before proceeding. Several considerations must be made:
Your IIIF images should be stored in the correct location on the image server, because you need to enter your IIIF service base URL as input to the tool. (N.B. The process of generating the IIIF service URL is described in the IIIF Image Conversion Guide.) “Correct location” in this context means: a folder with your IIIF images which the web server makes accessible through the URL address.
Your EDM metadata records must to follow the Europeana Data Model specifications. You can find more information about EDM in the Documentation.
Your dataset must be uploaded using the OAI-PMH protocol or a zip file.
4 General interface elements
Below is a list of the general interface elements and their uses.
4.1 The Welcome screen
The default screen, the screen you land on when navigating to the tool is the Welcome screen.
You can click ‘Start’ to navigate to the Home screen (see section below).
4.2 The Home screen
This screen allows you to start accessing the EDM2IIIF Manifest Creation tool. Here you can track existing data or initiate a new upload. It looks like this:
4.2.1 Input fields
The input fields are the white boxes where information must be entered by you. The description above the input field states what information should be entered. Every input field comes with a possible input example. Each field is mandatory.
0 Comments