-
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
Allow tenant configuration to ignore showing PDFs in universal viewer #659
Labels
Needs Rework
ReShare
https://docs.google.com/document/d/1vcA7NNNHuQMn6ocg2LvSNQpcXGzua3cEGyswKQvjEIc/edit#
Comments
3 tasks
This was referenced Aug 8, 2023
jeremyf
added a commit
that referenced
this issue
Aug 10, 2023
The current (as of <2023-08-10 Thu>) implementation of IIIF Print assumes that we generate derivatives at the application level. However, we want options for generating at the tenant level. As noted, I have chosen to default using IIIF print to `true` because that was the behavior before this commit. In other words, this commit is functionally a non-change to the production code-base (assuming no one goes and flips some switches). Related to: - #656 - #657 - #658 - #659
This fails SoftServ QA:
Screenshot: |
jeremyf
added a commit
that referenced
this issue
Aug 11, 2023
There is a conflict between the `IiifPrint` and `Hyrax::IiifAv` gems; namely they both have strong opinions about how to sniff out if we should use the `iiif_viewer?`. Compounding this, is that IiifPrint decorates `Hyrax::WorkShowPresenter` and Hyku extends `Hyrax::WorkShowPresenter` then includes `Hyrax::IiifAv::DisplaysIiifAv`. The end result is that the logic to determine if we should show pages split from the PDF is never called. Yet, if we were to solely use IiifPrint we'd ignore rendering audio and vidoe in the iiif viewer. So this commit peels that back so that we're using the logic (brought forward by IiifPrint) but ensuring our Hyku presenters are using that logic. Why move the logic out of the Hyku instance and into a module? Because that module contains the per-tenant antics of IiifPrint and its PDF relationship. There is larger work to do in regards to incorporating this logic into IiifPrint and the Hyrax::IiifAv gem. Does this work? Please pull down a branch and check. I'm at the end of my day (and then some). Related to: - #659
crisr15
added
the
ReShare
https://docs.google.com/document/d/1vcA7NNNHuQMn6ocg2LvSNQpcXGzua3cEGyswKQvjEIc/edit#
label
Aug 14, 2023
1 task
jeremyf
added a commit
that referenced
this issue
Aug 15, 2023
There is a conflict between the `IiifPrint` and `Hyrax::IiifAv` gems; namely they both have strong opinions about how to sniff out if we should use the `iiif_viewer?`. Compounding this, is that IiifPrint decorates `Hyrax::WorkShowPresenter` and Hyku extends `Hyrax::WorkShowPresenter` then includes `Hyrax::IiifAv::DisplaysIiifAv`. The end result is that the logic to determine if we should show pages split from the PDF is never called. Yet, if we were to solely use IiifPrint we'd ignore rendering audio and vidoe in the iiif viewer. So this commit peels that back so that we're using the logic (brought forward by IiifPrint) but ensuring our Hyku presenters are using that logic. Why move the logic out of the Hyku instance and into a module? Because that module contains the per-tenant antics of IiifPrint and its PDF relationship. There is larger work to do in regards to incorporating this logic into IiifPrint and the Hyrax::IiifAv gem. Does this work? Please pull down a branch and check. I'm at the end of my day (and then some). Related to: - #659
jeremyf
added a commit
that referenced
this issue
Aug 15, 2023
There is a conflict between the `IiifPrint` and `Hyrax::IiifAv` gems; namely they both have strong opinions about how to sniff out if we should use the `iiif_viewer?`. Compounding this, is that IiifPrint decorates `Hyrax::WorkShowPresenter` and Hyku extends `Hyrax::WorkShowPresenter` then includes `Hyrax::IiifAv::DisplaysIiifAv`. The end result is that the logic to determine if we should show pages split from the PDF is never called. Yet, if we were to solely use IiifPrint we'd ignore rendering audio and vidoe in the iiif viewer. So this commit peels that back so that we're using the logic (brought forward by IiifPrint) but ensuring our Hyku presenters are using that logic. Why move the logic out of the Hyku instance and into a module? Because that module contains the per-tenant antics of IiifPrint and its PDF relationship. There is larger work to do in regards to incorporating this logic into IiifPrint and the Hyrax::IiifAv gem. Does this work? Please pull down a branch and check. I'm at the end of my day (and then some). Related to: - #659
jeremyf
added a commit
that referenced
this issue
Aug 15, 2023
There is a conflict between the `IiifPrint` and `Hyrax::IiifAv` gems; namely they both have strong opinions about how to sniff out if we should use the `iiif_viewer?`. Compounding this, is that IiifPrint decorates `Hyrax::WorkShowPresenter` and Hyku extends `Hyrax::WorkShowPresenter` then includes `Hyrax::IiifAv::DisplaysIiifAv`. The end result is that the logic to determine if we should show pages split from the PDF is never called. Yet, if we were to solely use IiifPrint we'd ignore rendering audio and vidoe in the iiif viewer. So this commit peels that back so that we're using the logic (brought forward by IiifPrint) but ensuring our Hyku presenters are using that logic. Why move the logic out of the Hyku instance and into a module? Because that module contains the per-tenant antics of IiifPrint and its PDF relationship. There is larger work to do in regards to incorporating this logic into IiifPrint and the Hyrax::IiifAv gem. Does this work? Please pull down a branch and check. I'm at the end of my day (and then some). Related to: - #659
Here's a thread reporting that this has been returned to SoftServ for further fixes: https://assaydepot.slack.com/archives/C0313NKC08L/p1692255870043969 Looking at the logs I'm seeing:
And here's the exception : https://scientist-inc.sentry.io/issues/4368889816/?environment=production&project=6707374&referrer=project-issue-stream |
jeremyf
added a commit
that referenced
this issue
Aug 17, 2023
Prior to this commit, we had a private `#solr_document` method. This resulted in an error in the `Hyrax::Ability` as follows: ``` NoMethodError private method `solr_document' called for #<Hyrax::IiifAv::IiifFileSetPresenter:0x00007ff118124808> Did you mean? solr_document= ``` With this commit, I'm making public two methods that might cause issues being private. (And adding a test verifying the interface) Oh dear reviewer, were that I were able to duplicate the bug locally. I tried toggling on and off the feature flag. I also tried toggling the allow downloads. But to no avail. Alas, I cannot replicate but must instead rely on addressing the specific error. Related to: - #659 - https://scientist-inc.sentry.io/issues/4368889816/?environment=production&project=6707374&referrer=project-issue-stream
jeremyf
added a commit
that referenced
this issue
Aug 17, 2023
Prior to this commit, we had a private `#solr_document` method. This resulted in an error in the `Hyrax::Ability` as follows: ``` NoMethodError private method `solr_document' called for #<Hyrax::IiifAv::IiifFileSetPresenter:0x00007ff118124808> Did you mean? solr_document= ``` With this commit, I'm making public two methods that might cause issues being private. (And adding a test verifying the interface) Oh dear reviewer, were that I were able to duplicate the bug locally. I tried toggling on and off the feature flag. I also tried toggling the allow downloads. But to no avail. Alas, I cannot replicate but must instead rely on addressing the specific error. Related to: - #659 - https://scientist-inc.sentry.io/issues/4368889816/?environment=production&project=6707374&referrer=project-issue-stream
jeremyf
added a commit
to samvera/hyku
that referenced
this issue
Dec 15, 2023
The current (as of <2023-08-10 Thu>) implementation of IIIF Print assumes that we generate derivatives at the application level. However, we want options for generating at the tenant level. As noted, I have chosen to default using IIIF print to `true` because that was the behavior before this commit. In other words, this commit is functionally a non-change to the production code-base (assuming no one goes and flips some switches). Related to: - scientist-softserv/palni-palci#656 - scientist-softserv/palni-palci#657 - scientist-softserv/palni-palci#658 - scientist-softserv/palni-palci#659
jeremyf
added a commit
to samvera/hyku
that referenced
this issue
Dec 18, 2023
From scientist-softserv/palni-palci#675 > 🐛 Ensure consistent logic path for when iiif viewer > > There is a conflict between the `IiifPrint` and `Hyrax::IiifAv` gems; > namely they both have strong opinions about how to sniff out if we > should use the `iiif_viewer?`. Compounding this, is that IiifPrint > decorates `Hyrax::WorkShowPresenter` and Hyku extends > `Hyrax::WorkShowPresenter` then includes > `Hyrax::IiifAv::DisplaysIiifAv`. > > The end result is that the logic to determine if we should show pages > split from the PDF is never called. Yet, if we were to solely use > IiifPrint we'd ignore rendering audio and vidoe in the iiif viewer. > > So this commit peels that back so that we're using the logic (brought > forward by IiifPrint) but ensuring our Hyku presenters are using that > logic. > > Why move the logic out of the Hyku instance and into a module? Because > that module contains the per-tenant antics of IiifPrint and its PDF > relationship. > > There is larger work to do in regards to incorporating this logic into > IiifPrint and the Hyrax::IiifAv gem. > > Does this work? Please pull down a branch and check. I'm at the end of > my day (and then some). > > Related to: > > - scientist-softserv/palni-palci#659 Related to: - scientist-softserv/palni-palci#659 - scientist-softserv/palni-palci#675
jeremyf
added a commit
to samvera/hyku
that referenced
this issue
Dec 19, 2023
Contribute back the following features: - scientist-softserv/palni-palci#445 - scientist-softserv/palni-palci#659 - scientist-softserv/palni-palci#740 - scientist-softserv/palni-palci#748 - scientist-softserv/palni-palci#823 - scientist-softserv/palni-palci#843 - scientist-softserv/palni-palci#844 - scientist-softserv/palni-palci#911 Which were resolved via the following PRs: - scientist-softserv/palni-palci#920 - scientist-softserv/palni-palci#704 - scientist-softserv/palni-palci#706 - scientist-softserv/palni-palci#790 - scientist-softserv/palni-palci#867 - scientist-softserv/palni-palci#874 - scientist-softserv/palni-palci#893 - scientist-softserv/palni-palci#898 - scientist-softserv/palni-palci#824 - scientist-softserv/palni-palci#923 - scientist-softserv/palni-palci#939 - scientist-softserv/palni-palci#922 - scientist-softserv/palni-palci#926 - scientist-softserv/palni-palci#927 - scientist-softserv/palni-palci#928 - scientist-softserv/palni-palci#929 - scientist-softserv/palni-palci#930 - scientist-softserv/palni-palci#931 - scientist-softserv/palni-palci#943 - scientist-softserv/palni-palci#945 - scientist-softserv/palni-palci#954 Co-authored-by: Lea Ann Bradford <[email protected]> Co-authored-by: LaRita Robinson <[email protected]> Co-authored-by: Kirk Wang <[email protected]> Co-authored-by: Shana Moore <[email protected]>
jeremyf
added a commit
to samvera/hyku
that referenced
this issue
Dec 19, 2023
Contribute back the following features: - scientist-softserv/palni-palci#445 - scientist-softserv/palni-palci#659 - scientist-softserv/palni-palci#740 - scientist-softserv/palni-palci#748 - scientist-softserv/palni-palci#823 - scientist-softserv/palni-palci#843 - scientist-softserv/palni-palci#844 - scientist-softserv/palni-palci#911 Which were resolved via the following PRs: - scientist-softserv/palni-palci#920 - scientist-softserv/palni-palci#704 - scientist-softserv/palni-palci#706 - scientist-softserv/palni-palci#790 - scientist-softserv/palni-palci#867 - scientist-softserv/palni-palci#874 - scientist-softserv/palni-palci#893 - scientist-softserv/palni-palci#898 - scientist-softserv/palni-palci#824 - scientist-softserv/palni-palci#923 - scientist-softserv/palni-palci#939 - scientist-softserv/palni-palci#922 - scientist-softserv/palni-palci#926 - scientist-softserv/palni-palci#927 - scientist-softserv/palni-palci#928 - scientist-softserv/palni-palci#929 - scientist-softserv/palni-palci#930 - scientist-softserv/palni-palci#931 - scientist-softserv/palni-palci#943 - scientist-softserv/palni-palci#945 - scientist-softserv/palni-palci#954 Co-authored-by: Lea Ann Bradford <[email protected]> Co-authored-by: LaRita Robinson <[email protected]> Co-authored-by: Kirk Wang <[email protected]> Co-authored-by: Shana Moore <[email protected]>
jeremyf
added a commit
to samvera/hyku
that referenced
this issue
Dec 19, 2023
Contribute back the following features: - scientist-softserv/palni-palci#445 - scientist-softserv/palni-palci#659 - scientist-softserv/palni-palci#740 - scientist-softserv/palni-palci#748 - scientist-softserv/palni-palci#823 - scientist-softserv/palni-palci#843 - scientist-softserv/palni-palci#844 - scientist-softserv/palni-palci#911 Which were resolved via the following PRs: - scientist-softserv/palni-palci#920 - scientist-softserv/palni-palci#704 - scientist-softserv/palni-palci#706 - scientist-softserv/palni-palci#790 - scientist-softserv/palni-palci#867 - scientist-softserv/palni-palci#874 - scientist-softserv/palni-palci#893 - scientist-softserv/palni-palci#898 - scientist-softserv/palni-palci#824 - scientist-softserv/palni-palci#923 - scientist-softserv/palni-palci#939 - scientist-softserv/palni-palci#922 - scientist-softserv/palni-palci#926 - scientist-softserv/palni-palci#927 - scientist-softserv/palni-palci#928 - scientist-softserv/palni-palci#929 - scientist-softserv/palni-palci#930 - scientist-softserv/palni-palci#931 - scientist-softserv/palni-palci#943 - scientist-softserv/palni-palci#945 - scientist-softserv/palni-palci#954 Co-authored-by: Lea Ann Bradford <[email protected]> Co-authored-by: LaRita Robinson <[email protected]> Co-authored-by: Kirk Wang <[email protected]> Co-authored-by: Shana Moore <[email protected]>
jeremyf
added a commit
to samvera/hyku
that referenced
this issue
Dec 19, 2023
Contribute back the following features: - scientist-softserv/palni-palci#445 - scientist-softserv/palni-palci#659 - scientist-softserv/palni-palci#740 - scientist-softserv/palni-palci#748 - scientist-softserv/palni-palci#823 - scientist-softserv/palni-palci#843 - scientist-softserv/palni-palci#844 - scientist-softserv/palni-palci#911 Which were resolved via the following PRs: - scientist-softserv/palni-palci#920 - scientist-softserv/palni-palci#704 - scientist-softserv/palni-palci#706 - scientist-softserv/palni-palci#790 - scientist-softserv/palni-palci#867 - scientist-softserv/palni-palci#874 - scientist-softserv/palni-palci#893 - scientist-softserv/palni-palci#898 - scientist-softserv/palni-palci#824 - scientist-softserv/palni-palci#923 - scientist-softserv/palni-palci#939 - scientist-softserv/palni-palci#922 - scientist-softserv/palni-palci#926 - scientist-softserv/palni-palci#927 - scientist-softserv/palni-palci#928 - scientist-softserv/palni-palci#929 - scientist-softserv/palni-palci#930 - scientist-softserv/palni-palci#931 - scientist-softserv/palni-palci#943 - scientist-softserv/palni-palci#945 - scientist-softserv/palni-palci#954 Co-authored-by: Lea Ann Bradford <[email protected]> Co-authored-by: LaRita Robinson <[email protected]> Co-authored-by: Kirk Wang <[email protected]> Co-authored-by: Shana Moore <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Needs Rework
ReShare
https://docs.google.com/document/d/1vcA7NNNHuQMn6ocg2LvSNQpcXGzua3cEGyswKQvjEIc/edit#
Summary
We want a feature flipper that turns on and off the PDF processing for iiif print. This means a tenant can decide if they want PDFs showing in the viewer or not.
Testing instructions
Create a PDF work. Go view it to see that it creates with a thumbnail.
Go to the Settings, Features, and toggle the use iiif print feature.
Upload a PDF and allow it to process.
View the work and confirm you can see the PDF in the viewer.
Notes
There should be one single
flipflop
feature for the following tickets:Testing Instructions can be found here:
The three tickets can all be tested in one swoop.
The text was updated successfully, but these errors were encountered: