Generate IIIF Collection Manifests and deploying all manifests to static site

[sammeltassen]

Current IIIF Collection Manifests consist of two types:

• Skeleton manifests such as lib-tresor-universiteitsgeschiedenis.json which do not contain any items. The static site generates the collection by looking for the Object Manifests in the corresponding subfolder (in this case /content/collections/lib-library/lib-tresor-universiteitsgeschiedenis), but does not generate a complete collection json.
• Complete manifests from Collective Access such as 64c2d30b-1002-4063-a4d0-299cb10c507e.json. For these manifests, the objects can be found in the /content/objects folder and are matched by the corresponding IDs.

On the static website, the IIIF icons link to the manifests in the GitHub repository.

Proposed improvement:

• As part of the built process, the static site generator creates IIIF Collections for the skeleton collections. The resulting jsons are deployed to the static site, e.g. heritage.tudelft.nl/iiif/collections/lib-tresor-universiteitsgeschiedenis.json
• All other Collection and Object Manifests are deployed to the static site, e.g. heritage.tudelft.nl/iiif/collections/64c2d30b-1002-4063-a4d0-299cb10c507e.json and heritage.tudelft.nl/iiif/objects/009d29e8-e196-451f-8422-265b6ff27fb1.json (with the correct CORS headers). Exhibition manifests are included and could form a separate sub-collection.
• An additional collection json is created that points to all available collections. This can be used as an API entry point.
• During the built process, the manifest IDs are altered to the URLs of the deployed manifests.

This setup offers a more stable implementation of the IIIF Presentation API and could be used for other apps that work with our collection data.

[sammeltassen]

Potential addition:

• Being able to automatically add metadata properties to the deployed Object and Collections Manifests, for example a link to the collection's or object's landing page (which is not in the original manifest, and does not necessarily need to be rendered on the object/collection page).

[sammeltassen]

Should be possible to set the correct CORS headers on Netlify:

• https://stackoverflow.com/questions/62507022/how-to-enable-cors-on-a-netlify-deployment