-
Notifications
You must be signed in to change notification settings - Fork 51
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
Updating manifest generation to use IIIF 3.0 Presentation #4532
Comments
I used a IIIF manifest from MCO in the IIIF validator without
Manifest tested: https://gist.github.com/Dananji/ecd53e3a3d802e62b07c8c1c794a2210, to test this in the validator, I put this on maple here. |
Fix for number 2 above with |
@joncameron will break any remaining items here into separate issues. |
Description
Avalon generates IIIF manifest for each media object. This is performed on the fly when you visit
media_object_url/manifest
. And this manifest generation seems to be partially using the presentation API 2 (v 3.0 changelog).We also have the timeliner in avalon currently using a IIIF manifest for rendering of the component, but this might be different from what is mentioned above. As per the notes below there are 2 code segments in
media_objects_controller
andtimelines_controller
for handling manifests.IIIF manifests in avalon needs to be fully updated to use Presentation 3.0.
Validator for Prezi 3 compliance: https://iiif.io/api/presentation/validator/service/
Notes
The text was updated successfully, but these errors were encountered: