We’re trying to create manifests for images that are held on an external Cantaloupe image server, using metadata from items in Omeka S. To start with, is this possible, or can manifests only be generated for items uploaded to Omeka?
Our main problem is that the manifest isn’t generating items for API version 3 images. I’ve set up a test item with a mix of attached media - some uploaded to Omeka, some IIIF v3 images linked from our Cantaloupe server, a IIIF image from the Bodleian library, and a v2 API image from our image server. None of the IIIF v3 images are displaying in Universal Viewer, and the ones from our image server aren’t listed under “items” in the manifest, but under rendering:
I’m not sure what you want to do. Do you use module IIIF server or not? This one creates iiif manifests from the items. If you don’t use it but have your own manifests created by another tools, you have to add them in a property of an item to display them.
Many thanks for your reply, and apologies for not explaining clearly. We really appreciate all the work you’ve put into your modules, as they’ve been incredibly useful to us.
We are using the IIIF server module, and we are trying to use it to create manifests for items created in Omeka S, which link to media on a separate Cantaloupe image server. However, when we do this, we just get an error for the manifest.
Thanks, Daniel. We are using Omeka S version 3.0.2 and IIIFServer 3.6.5.3, and also have ImageServer 3.6.8.3 (but in this instance, are serving the image from a Cantaloupe image server, v. 5.0.3).
I just did another test, switching our Omeka default back to v3, and loading the media using the v2 json, and the manifest works and the image displays in Mirador (except there’s no thumbnail in Omeka). So this suggests there’s an issue with the info.json file from our Cantaloupe server, or at least a compatibility problem? These are the info.json files for my test item:
.