Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Mirador for images when IIIF bridge is unset #8

Merged
merged 1 commit into from
Oct 18, 2018

Conversation

jaguillette
Copy link
Contributor

If an Item has files, but there is no IIIF bridge set up, there shouldn't be a IIIF viewer displayed unless the Item has IIIF JSON data associated with it.

Previously, if there were no bridge set up, Items without manifests would display an empty Mirador viewer as long as they had IIIF-compatible files associated with them.

I found this out on a site where we don't have a IIIF server set up, but we still want to take advantage of externally hosted IIIF-compatible images and annotate those, while also having images that we had uploaded ourselves.

If an Item has files, but there is no IIIF bridge set up, there shouldn't be a IIIF viewer displayed unless the Item has IIIF JSON data associated with it.

Previously, if there were no bridge set up, Items without manifests would display an empty Mirador viewer as long as they had IIIF-compatible files associated with them.

I found this out on a site where we don't have a IIIF server set up, but we still want to take advantage of externally hosted IIIF-compatible images and annotate those, while also having images that we had uploaded ourselves.
@dicksonlaw583
Copy link
Collaborator

Thank you for your suggestion. The external-only use case should look a lot better with this modification in.

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

Successfully merging this pull request may close these issues.

2 participants