-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create process for creating IIIF manifests in python #3
Comments
Looks like there are multiple Python IIIF manifest libraries, and I'm not sure which one is more active/up to date:
There are also multiple versions of the IIIF presentation spec. I assume we should use 3.0. |
I planned on this being in Python, as the Processing app will eventually create manifests from a form. But the first manifests will have to be created during the Hyrax migration. It might be best to migrate everything to SPE_DAO from within Rails since the structure is in Hyrax. So we could create manifests during that step, but my though was to right the structure to disk in some way, that way we can use the same IIIF manifest Python process as we'll eventually use by reading that file structure from disk. We could also write the manifests in ruby from within rails if we think that's a better approach too. |
Basic framework is here: https://github.com/UAlbanyArchives/arclight_integration_project/blob/main/scripts/manifest.py Still have to incorporate A/V materials, sort out transcriptions, and generalize it for use as a local library. |
This is pretty much done, we just need to test with Universal Viewer once SSL is set up. There is just some minor issues like audio not playing on mobile, and audio captions not working that I don't know if are manifest issues or viewer issues. |
This is higher up the to-do list than dockerizing, as once the spec is done, this is the main blocker for the migration.
The text was updated successfully, but these errors were encountered: