Different cases of IIIF in EDM
Case 1: You provide IIIF images and a manifest
What you need to do when a manifest is available:
Follow all steps on the EDM_IIIF Pattern page:
provide the IIIF image in the correct field (
edm:isShownBy
oredm:hasView
), and as a WebResource, making sure the Request URI Syntax matches the requirementsflag the WebResource as IIIF-compliant
indicate a level of IIIF implementation
provide access to a IIIF manifest (within
dcterms:isReferencedBy
)
What we do when you provide both IIIF images and a manifest:
we support both IIIF Presentation API v2 and v3
we use Mirador v3.0.0 (latest version) since the new portal went live April 2020
has custom plugins to handle search & fulltext
view is configured for one window
Examples on the Europeana website & EDM xml:
Leiden University Libraries (See a summary of the EDM xml in the grey box below)
Example of EDM record implementing all steps:
<ore:Aggregation rdf:about="[...]">
[...]
<edm:isShownBy rdf:resource="https://iiif.universiteitleiden.nl/iiif/2/hdl%3A1887.1%2Fitem%3A3280522/full/full/0/default.jpg">
[...]
</ore:Aggregation>
<edm:WebResource rdf:about="https://iiif.universiteitleiden.nl/iiif/2/hdl%3A1887.1%2Fitem%3A3280522/full/full/0/default.jpg">
<dcterms:isReferencedBy rdf:resource="https://digitalcollections.universiteitleiden.nl/iiif_manifest/item:3280522/manifest"/>
<svcs:has_service rdf:resource="https://iiif.universiteitleiden.nl/iiif/2/hdl%3A1887.1%2Fitem%3A3280522"/>
</edm:WebResource>
<svcs:Service rdf:about="https://iiif.universiteitleiden.nl/iiif/2/hdl%3A1887.1%2Fitem%3A3280522">
<dcterms:conformsTo rdf:resource="http://iiif.io/api/image"/>
<doap:implements rdf:resource="http://iiif.io/api/image/2/level2.json"/>
</svcs:Service>
Case 2: You provide IIIF images but no manifest
What you need to do when a manifest is not available:
Follow step 1, 2 and 3 on the EDM_IIIF Pattern page:
provide the IIIF image in the correct field (
edm:isShownBy
oredm:hasView
), and as a WebResource, making sure the Request URI Syntax matches the requirementsflag the WebResource as IIIF-compliant
indicate a level of IIIF implementation
Step 4, providing a manifest, can be left out. (See the grey text box below)
What we do when a manifest is not available:
we generate one automatically and on demand out of EDM
we support both IIIF Presentation API v2 and v3
we use Mirador v3.0.0 (latest version) since the new portal went live April 2020
has custom plugins to handle search & fulltext
view is configured for one window
Examples on the Europeana website & EDM xml:
Example Graz The value of
dcterms:isReferencedBy
is not provided by the institution, but generated by Europeana. This generated manifest can now be used anywhere as a reference to this IIIF resource.
Example of EDM record implementing all steps EXCEPT the definition of the IIIF manifest (for IIIF service supporting only image request calls)
<ore:Aggregation rdf:about="[...]">
[...]
<edm:isShownBy rdf:resource="http://iiif.europeana.eu/AZ_1927_01_04_0001/full/full/0/default.jpg">
[...]
</ore:Aggregation>
<edm:WebResource rdf:about="http://iiif.europeana.eu/AZ_1927_01_04_0001/full/full/0/default.jpg">
<svcs:has_service rdf:resource="http://iiif.europeana.eu/AZ_1927_01_04_0001"/>
</edm:WebResource>
<svcs:Service rdf:about="http://iiif.europeana.eu/AZ_1927_01_04_0001">
<dcterms:conformsTo rdf:resource="http://iiif.io/api/image"/>
<doap:implements rdf:resource="http://iiif.io/api/image/2/level1.json"/>
</svcs:Service>
Note that the set of parameters available as part of the image URI in <edm:isShownBy rdf:resource="http://iiif.europeana.eu/AZ_1927_01_04_0001/full/full/0/default.jpg">
will vary depending on the image the data provider wants to make available.