You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When at an authorized location, location-restricted PDFs do not open in the viewer. It is possible to download the PDFs from direct links to the Stacks URL but the viewer presentation looks the same as when you are not in an authorized location.
I tested this while on campus visiting the Special Collections reading room. Geoff Willard (@oceanofsound ) also verified this from his workstation that is authorized to view location-restricted materials.
Expected behavior
When at an authorized location, the viewer should present PDFs as if the user has logged in. This is what happens with location-restricted media and images.
Additional information
I'm not sure how we can test this remotely. Whoever picks up the ticket may need to coordinate with Geoff if they need to see what the browser is doing when visiting PDF.
Embed::Purl::ResourceFile#downloadable? requires either world downloadable or stanford only downloadable.
It seems like the PdfComponent is using a completely different auth protocol from the media viewer. Currently it doesn't look like the PDF can handle embargo either. I wonder if switching to the media protocol could fix this?
Describe the bug
When at an authorized location, location-restricted PDFs do not open in the viewer. It is possible to download the PDFs from direct links to the Stacks URL but the viewer presentation looks the same as when you are not in an authorized location.
I tested this while on campus visiting the Special Collections reading room. Geoff Willard (@oceanofsound ) also verified this from his workstation that is authorized to view location-restricted materials.
Expected behavior
When at an authorized location, the viewer should present PDFs as if the user has logged in. This is what happens with location-restricted media and images.
Additional information
I'm not sure how we can test this remotely. Whoever picks up the ticket may need to coordinate with Geoff if they need to see what the browser is doing when visiting PDF.
To reproduce
From an authorized location:
From outside an authorized location:
Follow the steps above and see that neither the PDF viewer nor the Stacks link will allow access to the PDF.
The text was updated successfully, but these errors were encountered: