Skip to main content
OCLC Support

Insert IIIF manifest link as metadata

 

 

We introduced Mirador viewer integration recipe which is welcomed by the CONTENTdm community. And we start to hear more and more about “IIIF manifests.” For those who are unfamiliar with IIIF manifest, below is an example.

This is an image item in a CONTENTdm collection: https://cdmdemo.contentdm.oclc.org/digital/collection/oclcsample/id/64/rec/6.

And this is the IIIF Presentation manifest for the image. The link is formed with the collection alias, and item ID: https://cdmdemo.contentdm.oclc.org/iiif/info/oclcsample/64/manifest.json

How would the manifest links be used? For example, if you want to load an item into a Mirador viewer, whether by itself or to compare it with another object, you need to feed the manifest link to the “Add new object from URL” box:

Load-item-into-Mirador-viewer.png

 

To fully utilize the power of Mirador viewer and potentially other IIIF-compliant agents, it would be nice to have the link to the manifest readily available on the website. This recipe will do just that – inserting the manifest link as metadata. Download the .js file from the demo site download portal, and upload it through your site’s Website Configuration Tool, Save & Publish. Now when an item page is loaded, the link to the IIIF Presentation manifest of the item is inserted dynamically after the other metadata fields. It comes with an IIIF logo to draw attention to the link. Another link to the IIIF Image API is inserted after that.

Insert image here

IIIF-Presentation-manifest-link.png

In compound objects (including monographs) the IIIF Presentation manifest link will be inserted into the Object Description accordion. The IIIF Image API links will be inserted into the Item Description for the individual pages as they differ from page to page.

For non-image items, this recipe will detect no associated manifest file, thus won’t add anything.

Make sure your manifests are all in place before testing this recipe, because you must run indexing for your collection to generate the manifests.

(An added fun benefit: you can drag the IIIF manifest link into a Mirador viewer and directly load it.)

We are also considering making this function a standard feature for all CONTENTdm users in the future. We will need your feedback to determine if it is a worthy idea. Contact OCLC Support or sign in the CONTENTdm Community to let us know if this should be a standard feature.

 
https://help-nl.oclc.org/Metadata_Services/CONTENTdm/Advanced_website_customization/Customization_cookbook/insert_iiif_manifest_link_as_metadata
help-nl.oclc.org
crawl=CC-MAIN-2022-21
56237
application/http; msgtype=response
sha1:HJD7SHFQFGOLOW7ME4G2TTSQ4IXNMRGX
<urn:uuid:ded51228-273e-4f2c-94ea-d317de266cbb>
2022-05-26T08:34:51Z
52.206.246.12
text/html
sha1:CJTQ2PF5ZFJXGRE7HIPDZN7O5XFPJSHI
<urn:uuid:7508ddd8-8e9f-42a2-8640-5205f71b6389>
https://help-nl.oclc.org/Metadata_Services/CONTENTdm/Advanced_website_customization/Customization_cookbook/insert_iiif_manifest_link_as_metadata
response
<urn:uuid:9018334e-4565-48e9-98e9-39a0126408f7>
isPartOf: CC-MAIN-2022-21
publisher: Common Crawl
description: Wide crawl of the web for May 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-206
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/