Digirati manifest editor manifest not loading due to "Could not parse resource"

[glenrobson]

Do you know why the following URL:

https://iiif-test.github.io/testing-v3/manifests/manifest.json

Is generating

I wondered if it was something to do with the Github hosting but the original manifest from Digiarti also doesn't seem to work:

https://manifest-editor.digirati.services/api/iiif/p3/68f92487ee841bc894e8fe5ed1b379ab/1775150356671

I can't see anything in the console on why its not working.

[rsimon]

Hi @glenrobson, thanks for reporting!

Looks like it's a small bug in our parser library. It relies on the type property of the image service block to determine if an image is delivered via a service, and whether it's IIIF Image API v3 or v2. It looks like in your case, only the first image has a type (ImageService3), but the second doesn't. So I guess we should fall back on the context URL instead to identify the Image API version?

[rsimon]

Hi @glenrobson,

the bug is now fixed and deployed on our test instance: https://immarkus.rainersimon.io – will be available on the main instance with the next release.

[glenrobson]

Thats great thank you @rsimon! For planning purposes when do you expect the new release to be? Thanks

[rsimon]

Hi @glenrobson, I just published a new release and asked the InfraLives team to update the production server. I'll ping you when I hear back – they are usually super quick in making the server updates.

[rsimon]

Done - latest version is now live on https://xmarkus.immarkus.org

[glenrobson]

Great thank you!

Just tested and its working great.