Verifying IIIF manifests

[ChristieHurrell]

Hello, is there any documentation that goes along with this project on how to verify that the Image API for your chosen IIIF manifests is compliant with the IIIF plugin? I am working with a faculty member who is trying to import manifests from this site (http://kotenseki.nijl.ac.jp/) and although the manifests do import, we are noticing a few problems with the way they display:

• annotations are not appearing on the public site (although they display on the admin side)

• item level images (e.g. the single pages of the manuscripts) are not converted or displayed as jpegs

To test these issues, I uploaded a manifest from a different image server, and these problems did not replicate, so I am assuming that there is an issue with the manifests referenced above. But I'm not sure how to verify that. Thanks!

[dicksonlaw583]

I have taken a look at some manifests from the site, and it seems that the image API and annotation list URLs look like this:

//kotenseki.nijl.ac.jp/api/iiif/200021974/v2/NIIP/049-0081/049-0081-00003.tif
//kotenseki.nijl.ac.jp/biblio/200021974/list/2

The plugin looks for http:// or https:// to determine how to start the download (which are present in all compliant manifests we have seen thus far), but the ones in the manifest don't start with either. As a result, the plugin couldn't act on these URLs, so they are left out of the import.

[ChristieHurrell]

Dickson, thanks for letting me know that this is the problem. Much appreciated. Would a future update to the plugin consider addressing this issue?

[dicksonlaw583]

@ChristieHurrell

My apologies for the delay in responding. Can you try this branch and see if you can import? https://github.com/utlib/IiifItems/tree/patch-kotenseki

[drbauder]

@dicksonlaw583, I'm working with @ChristieHurrell on this project, as the server administrator. I've pulled this branch and I'm currently running the import on the manifest at http://kotenseki.nijl.ac.jp/biblio/200021974/manifest. Is this the manifest you referenced in your above comment? So far the import looks fine, but searching through the JSON manually, the URLs all appear to use https, in addition to having all forward slashes escaped (e.g., https:\/\/kotenseki.nijl.ac.jp\/api\/iiif\/200021974\/v2\/NIIP\/049-0081\/049-0081-00003.tif). Perhaps this manifest has been updated since you tested?

[dicksonlaw583]

@drbauder:

Yes, the manifest has changed since the previous test, it looks standards-compliant now. The back-then-forward slashes are fine, the JSON parser will turn those back into single forward slashes.

Are the imports working properly with the unpatched plugin? If it is back in order, we can safely close this ticket.

[drbauder]

@dicksonlaw583,

Yep, I switched back to the main branch and the import seems to be running fine now.

Thanks for your time!

[dicksonlaw583]

You're welcome. Closing.