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

Evaluate options for IIIF deep viewer component #24

Closed
garrettdashnelson opened this issue Jan 3, 2024 · 0 comments · Fixed by #28
Closed

Evaluate options for IIIF deep viewer component #24

garrettdashnelson opened this issue Jan 3, 2024 · 0 comments · Fixed by #28
Assignees
Milestone

Comments

@garrettdashnelson
Copy link
Member

The collection record page ( /src/pages/maps/[identifier].astro ) should have a large deep-zoomable viewer as its primary component. Ideally this is a reusable component which takes a IIIF Manifest or IIIF Image as its prop and which could also be used in other parts of the site (e.g., to create a zoomable collection viewer within an article page type).

Some options:

  1. Use the @samvera/clover-iiif React component. This would be my first choice, but as of Issue #141 in that repo, there was a problem loading our Manifests, probably due to identifier mismatches or 300 redirects. I haven't checked yet to see if the recently-released v2.3.0 fixes this bug.

  2. Use Tify. This is what the old ARGO does. Tify is not componentized so it has to be included on the client side. It also doesn't yet support Presentation 3.0 Manifests, which isn't currently an issue, but it would be nice to future-proof for when we do eventually need to handle Presentation 3.0.

  3. Build something custom based on OpenSeadragon ... similar to what we did in Walk to the Sea. Note that OSD can only take in IIIF Images, not Manifests, so we would need to write a shim that first pulls the Manifest and passes its constituent Images to OSD.

@alexandergknoll very much open to your opinions on this!

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 a pull request may close this issue.

2 participants