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

HYKU: Configure iiif_print #184

Open
1 task
ShanaLMoore opened this issue Mar 15, 2023 · 0 comments
Open
1 task

HYKU: Configure iiif_print #184

ShanaLMoore opened this issue Mar 15, 2023 · 0 comments

Comments

@ShanaLMoore
Copy link
Contributor

ShanaLMoore commented Mar 15, 2023

Summary

Once IiifPrint is installed, we should communicate with the client (Rob?) to clarify which configurable features to enable.

Give the client the options or review their SOW (look in google drive or ask Jill), and update this ticket with what needs to be done.

Iiif_print configuration options:

Should we have everything turned off by default?

  • Currently pdf splitting is only set up for generic work, which might be confusing behavior as a new hyku user.
  • if so, this work will remove the existing configurations and add a note about iiif_print to hyku's readme.

if not...

  • PDF SPLITTING
    • Should all models get split?
    • What work types should they get split into?
  • DERIVATIVE TYPES
    • Tiff, Jpg, Png, or we can also turn this off.

Note: Text derivative (OCR) and parent only catalog search results are already enabled.

Acceptance Criteria

Implement the configurations once we get the answers to the above options.

  • The application should be configured as defined by the client.

Screenshots or Video

Testing Instructions

Once this ticket is done, it can be closed.

ref #185 for QA

Notes

ref playbook article for some configuration options:
https://playbook-staging.notch8.com/en/DEMOS/IiifPrint/i11-split-PDF-into-images-and-create-child-works

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

2 participants