You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
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.
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:
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.
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.
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!
The text was updated successfully, but these errors were encountered: