Work with the IIIF Presentation API
Item manifests
The image example above also supports the IIIF Presentation API response. The IIIF Presentation API call which returns the JSON manifest is:
CONTENTdm's Presentation API request URL follows the pattern described in the IIIF Presentation API specification:
- yourCONTENTdmURL/iiif/info/{collection alias}/{record ID}/manifest.json
Collection manifests
For all CONTENTdm collections that contain images, a collection-level collection manifest is automatically created. This collection manifest data structure is part of the IIIF Presentation API specification and is a JSON file that lists each item manifest in the collection. For large collections, this collection manifest will be paginated into multiple files. Collection manifests are useful for any viewer or aggregator that needs to see a complete list of every item in the collection. Universal Viewer directly supports loading and parsing collection manifests.
For the example manifest above, see its parent collection manifest here:
These collection-level manifests in CONTENTdm will always follow the pattern described in the IIIF Presentation API specification:
- yourCONTENTdmURL/iiif/info/{collection alias}/manifest.json
Collection-of-collections manifest
Similar to the collection manifest data structure, CONTENTdm automatically creates a top-level manifest that links to each of the collection manifests. This repository-level JSON file can be considered as equivalent to a Sitemap.xml file, although it currently only includes references to image records in CONTENTdm. For the example item and collection listed above, the sitewide manifest is here:
The sitewide manifest follows this pattern:
- yourCONTENTdmURL/iiif/info/manifest.json
Note: For more information on these and other methods for calling the CONTENTdm IIIF Presentation API service, consult the IIIF Presentation API specification.