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

Updating manifest generation to use IIIF 3.0 Presentation #4532

Closed
Dananji opened this issue Sep 3, 2021 · 4 comments
Closed

Updating manifest generation to use IIIF 3.0 Presentation #4532

Dananji opened this issue Sep 3, 2021 · 4 comments

Comments

@Dananji
Copy link
Contributor

Dananji commented Sep 3, 2021

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 and timelines_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

I looked at the rest of one of the manifests and think that the "service" is probably the problem for validators to accept our manifests. If you have a way to try one of MCO's manifests excluding the service elements and the @ from @none, we may actually find that this is all...

@Dananji
Copy link
Contributor Author

Dananji commented Sep 10, 2021

I used a IIIF manifest from MCO in the IIIF validator without service and @ from @none tags as @mcwhitaker suggested. And found the following issues that needs to be fixed;

  1. Annotation requires an id property
  2. Cannot have null values for properties. Ones that I came across when testing are, label, value in metadata, height, width. Instead of null values use { "none": [] }.
  3. homepage property accepts an array
  4. for UV support add format property for resources

Manifest tested: https://gist.github.com/Dananji/ecd53e3a3d802e62b07c8c1c794a2210, to test this in the validator, I put this on maple here.
Changes from above made to make it valid: https://gist.github.com/Dananji/ecd53e3a3d802e62b07c8c1c794a2210/revisions?diff=unified

@cjcolvar
Copy link
Member

cjcolvar commented Sep 15, 2021

Fix for number 2 above with height and width submitted to iiif_manifest: samvera/iiif_manifest#59
Fix for number 3 above: #4536

@joncameron
Copy link
Contributor

@joncameron will break any remaining items here into separate issues.

@joncameron
Copy link
Contributor

#4596 and #4597 are broken from this ticket as the remaining pieces of work identified.

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

No branches or pull requests

3 participants