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

CDRI Collections not using UV (not AV) #323

Open
ckarpinski opened this issue Aug 15, 2023 · 2 comments
Open

CDRI Collections not using UV (not AV) #323

ckarpinski opened this issue Aug 15, 2023 · 2 comments
Assignees

Comments

@ckarpinski
Copy link
Collaborator

ckarpinski commented Aug 15, 2023

These CDRI NON AV collections are not using the UV as they should. The records have the checkbox checked for "Use IIIF Viewer"

FIGURED THIS OUT - the works now using the UV are all PDF files. These should still use the UV but probably have to get processed right? (i think we have the print gem on the DL right?)

@aprilrieger
Copy link
Contributor

Developer notes for keeping track of where the issue is in the que:

I have investigated the issue on production. Since this application had it's dns configured in a state that we cannot force ssl to be true in the application, the links that the application is passing to the uv through the manifest is all http:// versus https://, which then creates a mixed media issue in the browser which then prohibits the uv from displaying the media.

I was able to implement a solution where we catch the base_url before the uv gets it and replace the http:// with https://. I was able to get this working locally. I was able to import the collection form a production import: https://dl.atla.com/importers/370. I was able to get into the r2-atla-dl cluster, under the production namespace, after connecting to the cluster via terminal I was able to kubectl cp production-hyrax-778969d74-gqxlg:/app/samvera/hyrax-webapp/tmp/imports/370_20230925190437/Archive.zip /Users/aprilrieger/softserv/atla_digitial_library/tmp/imports/370_20230925190437/Archive.zip the file locally and use it in my import testing.

When I deployed a test branch of this work to production, it appeared I broke production in some way. When I would go to click into the works I would get a rails standard error page, in the logs I would receive solr errors retrieving the works. I was able to jump into a rails console in the web container and see the work. Dumping the error and the logs in slack here (Sorry Christy I don't think you have access, let me know if you want to view these files and I can provide them, but I was thinking this is just my notes for someone to pick up where I left off troubleshooting or for me to find my way back as I search for answers).

@aprilrieger aprilrieger self-assigned this Sep 28, 2023
@orangewolf
Copy link
Contributor

this should be fixed now I believe.

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

No branches or pull requests

3 participants