Open tomcramer opened 10 years ago
Use case?
Some thoughts in the meantime:
The logic for when to apply a watermark would have to be entirely server-side, because if the URI for the derivative was, say:
http://{server}/loris/{id}/full/full/0/native.jpg?watermark=true
then it wouldn't be tough to figure out what
http://{server}/loris/{id}/full/full/0/native.jpg?watermark=false
is likely to do. Sure there could be something more opaque baked into the identifier, but that would be ugly.
watermark_id
or something like that as an optional parameter that the resolver can return, and when it's present, get that overlay (from the app? from the repository?) and revise the transformation scenario to take an optional path to the overlay to apply.So, the devil is in the details...let me know more.
Amendment I'd forgotten about the Djatoka watermark plugin. Is this anything like what you're after? We never used it here, but it looks like it makes the assumption that all (or none) of the images from the server will be watermarked; I'd want to be more flexible.
As an image repository, I'm interested in giving donors a sense of control of their images once posted on the website. For downloading or printing any image above a certain resolution, I'd like to add a watermark that provides attribution and/or discourages unlicensed exploitation of the image.