Skip to content
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.

IIIF compatability #5

Open
edsu opened this issue Dec 16, 2019 · 1 comment
Open

IIIF compatability #5

edsu opened this issue Dec 16, 2019 · 1 comment

Comments

@edsu
Copy link
Contributor

edsu commented Dec 16, 2019

On the subject of IIIF compatability I did try to create some IIIF manifests that referenced image tiles created with magick_tile. After much hand-wringing I couldn't seem to get them to display in MIrador. But I was rolling my own IIIF manifest JSON, so it's quite possible the problem was in there. Minting all the various URLs for things, that don't really need to resolve is quite complicated--I guess I've been spoiled by iiif-prezi...

I'll be leaving the result of the experiment online for a few weeks if you have any interest in taking a look. Here's an example manifest:

https://mith-lastclass.s3.amazonaws.com/iiif/manifests/items/98.json

You can load it up in the Mirador Demo

Screen Shot 2019-12-16 at 4 35 24 AM

@mdlincoln
Copy link
Collaborator

🤷‍♂ as far as I can tell, you're properly announcing in both the manifest as well as in the info.json document for specific images that you're complying with level 0 only, which should suggest that Mirador ought not try to request an image arbitrarily sized at width of 59 which I see it trying to do for one of your pics.

This issue comment intimates you may need to specify a thumbnail in your manifest - maybe that's a path to try? I haven't graduated to the IIIF presentation API yet :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants