projectblacklight / spotlight

Spotlight enables librarians, curators, and others who are responsible for digital collections to create attractive, feature-rich websites that highlight these collections.
Other
161 stars 65 forks source link

Spotlight application access to download restricted images #1161

Open snydman opened 9 years ago

snydman commented 9 years ago

When creating a Spotlight exhibit using images that have a world no-download rule, the Spotlight app cannot use images to produce default or customized Browse category thumbnail images, or fetch high resolution images for cropping of mastheads.

Is it possible to give the Spotlight app access to higher res images in stacks even if their "read" rights are restricted by the no-download rule.

For example, is agent-auth a possibility?

blalbrit commented 9 years ago

agent-auth, as it is currently implemented, would require adding an agent stanza to rightsMD for every item with the no-download rule. that seems like a blunt-force approach to the problem that would require fairly extensive content remediation to get right.

are there other approaches we could explore?

jkeck commented 9 years ago

I'm not sure if this ultimately solves this problem but the way we would really like to handle cropping in the future is to NOT require the browser to download a high-res image for cropping purposes. Instead we would like to use the IIIF response to provide the user w/ a scaled image that they can zoom in/out and select a crop from that. I don't know what Spotlight would ultimately store (I think just a IIIF url and potentially additional coordinates) but assuming that URL would still be accessible for objects that have no-download then it could potentially solve this issue.

Unfortunately there are some complications around adding this functionality to Spotlight, but I think we've all resolved that it is ultimately the path that we should be taking.

cbeer commented 9 years ago

@snydman how should we handle masthead cropping for images tagged no-download? I imagine we should just stitch it up client side, but maybe there are rights issues that we need to inform the curator about?

cbeer commented 8 years ago

I'm not sure how this relates to #1184. It seems like it may make matters worse, even, if we're hotlinking directly to stacks IIIF urls.