Media Watermarking

monica

Watermarks are added at time of upload and processing. You need this configuration added to your providence install and reprocess your media to show the watermark.

darrigan

... and to reprocess media, with a terminal, go to /ca/support/bin and, with root or sudo access:
./caUtils reprocess-media
For help, use:
./caUtils help reprocess-media
I suggest you to try this reprocess-media only for one object in your collection, in order to see if your watermark is as you expected. To do so:
./caUtils reprocess-media -o 934
(934 is an example of CollectiveAccess number of an object)

carlosTF

Thank you, will try as suggested.

carlosTF

I just can't figure this out.

In /ca/app/media_processing.png, "MEDIA_TRANSFORMATION_RULES" appears 8 times for up to 53 lines where SCALE is defined for an image. It seems there are many rules repeated, such as

		rule_preview_image = {
			SCALE = {
				width = 180, mode = width, antialiasing = 0.5
			},
			SET = {quality = 75, format = image/jpeg, background = "#ffffff" }
		},

repeated up to 4 times. I really don't know which "VERSIONS" or rules to look after in media_processing.conf.

In https://manual.collectiveaccess.org/providence/user/media/media_watermarking.html it says:

Note that this must be the absolute path to the watermark image. If placed in ‘app’ directory, the pre-existing macros set in global.conf (such as <ca_ap_dir>) can be used to avoid hardcoding path information. E.g., if the watermark image is at web/ca/app/watermarks/mymark.png, you can configure it here as <ca_app_dir>/watermarks.mymark.png

I've tried:

			WATERMARK = {
        		image = <ca_app_dir>/watermarks/mymark.png,
         		width = 72, height = 85, position = south_east, opacity = 0.8
    		},

and trying different paths to call the watermark image:

image = ca/app/watermarks/mymark.png,
image = www/ca/app/watermarks/mymark.png,

I will very much appreciate some guidance here.

Thank you.

darrigan

If ca_app_dir is not defined in global.conf, you can define it.
In global.conf, you should have:

ca_base_dir = __CA_BASE_DIR__
ca_conf_dir = __CA_CONF_DIR__
ca_app_dir =  __CA_APP_DIR__
ca_lib_dir =  __CA_LIB_DIR__
ca_models_dir = __CA_MODELS_DIR__

where __CA_APP_DIR__ should be defined in setup.php.
But you can also write ca_app_dir in hard as:
ca_app_dir = /www/mfa/app

Or if you want to precise the absolute path directly in media_processing.conf, try:
image = /www/mfa/app/watermarks/mymark.png,
(assuming /www is at your root directory)

darrigan

Each of MEDIA_TRANSFORMATION_RULES you find refers to different kinds of images used in CA, that you may treat differently: (in my version, they are 7)

ca_object_representations
ca_object_representation_multifiles
ca_attribute_value_multifiles
ca_icons
floorplans
ca_item_comments_media
ca_representation_annotation_previews

Most people use ca_object_representation and ca_object_representation_multifiles. (You should consider them.)
The ca_icons is used is for icons in the user interface of providence.
The floorplans is used if you need to add floor plans of storage locations or places.

And for SCALE, if you see multiple references to this, it's because you may treat different sizes of images (used in different view of providence or pawtucket) with different settings.
For example:

rule_icon_image is for small "icon", 72x72 pixels.
rule_thumbnail_image is used for thumbnail images, 120x120 pixel.
etc.
rule_original_image is the original file. Theoretically, if you want to preserve somewhere the untouched original file, you should not apply any SCALE settings here.

The media_processing.conf seems very big and confusing at beginning, but it describes all the transformations you want to apply in all kinds of media files you need in different parts of providence and pawtucket... Everything is customizable.

Let's take an example. On this page https://collections.univ-pau.fr/pub/index.php/Detail/objects/1179 you see a big image on the left, and small images behind.
If you right-click on the big image to open it in a new window, you see its path: ......./7/55046_ca_object_representations_media_2785_large.jpg
If you right-click on a small image to open it in a new window, you see its path: ......../7/26491_ca_object_representations_media_2785_icon.jpg
So, the big one corresponds to the rule_large_image, and you should apply a watermark on it.
The small one corresponds to rule_icon_image, and you should decide to not apply a watermark on it because of its size.

carlosTF

@darrigan thank you for your detailed explanation. Unfortunately, I'm still not capable to place a watermark on an image. I didn't want to mess around with global.conf and setup.php and focused in setting the exact path in media_processing.conf.

Under ca_object_representations:

	rule_large_image = {
		SCALE = {
			width = 700, mode = width, antialiasing = 0.5
		},
		WATERMARK = {
    		image = /www/ca/app/watermarks/mymark.png,
     		width = 72, height = 85, position = center, opacity = 0.8
		},
		SET = {quality = 75, format = image/jpeg, background = "#ffffff" }
	},

Opening an uploaded image on separate tab I see: http://mfa.localhost/media/collectiveaccess/images/0/27080_ca_object_representations_media_62_large.jpg, which corresponds to the above rule. However, no watermark is shown.

In case you wonder, yes, I have a mymark.png image in /ca/app/watermarks.

monica

Most Linux installs wouldn’t have /www at the root. It is more likely /var/www if Ubuntu and Apache.

Check log files (ca’s app/log and the web servers /var/log
Run the command: ls /www/ca/app/watermarks if the path is right or should output your png file

If the logs or ls show the path is wrong, update to correct and try again (restart web service and reprocess media file)

darrigan

@carlosTF Right now, I tested with your file mymark.png and exactly like your settings as above (except I changed the path, of course!).
It works!😁 The proof:

So I think Monica is right: you have to put the absolute path of your image, something like:
image = /home/blablabla/ca/app/watermarks/mymark.png,
(To know the absolute path, use a terminal, go to the directory containing your file, and type "pwd" command.)

carlosTF

@darrigan so cool to see my grandfather signature in your photo! And @monica thank you to you too for your time and advise.

I'm running Providence and Pawtucket in an iMac using Apache server. Everything works as expected, but watermarking is showing resistance.

The real path is /usr/local/var/www/ca/app/watermarks

27723_ca_object_representations_media_65_large.jpg is the output file name that should had been waterkarked by the above settings as @darrigan showed. But it doesn't.

ca's app/log does not contain anything related to file uploading, let alone watermarking. var/log either.

With the aforementioned setup with the watermark image path hard coded, do setup.php or global.conf enter into play in any way?

Does the object (image) need some specific metadata for the watermak to be applied?

We plan to release the digital raisonné catalogue of my grandfather, a Catalan painter, and we definitely need watermarking in place.

Sorry for abusing your time, thank you.

darrigan

With the aforementioned setup with the watermark image path hard coded, do setup.php or global.conf enter into play in any way?

No.

Does the object (image) need some specific metadata for the watermak to be applied?

I think no.

There must be something really stupid that is blocking it somewhere.🤔
Some ideas just in case:

Is your modified media_processing.conf file in ca/app/conf or in ca/app/conf/local? Do you use the local directory? (I use the local directory.)
When you launch caUtils script to reprocess representations_media, you have no error message?
When you display the image supposed to be watermarked, do you check there is no cache joke with you navigator, nor a cache elsewhere? (The best is to check directly in the media directory to see if the image file had been really touched or not.)
The original file you upload is a .jpg or something else?
In which parent { } of the media_processing.conf file do you change the rule_large_image? (Should be in the ca_object_representations = {...})
🤔🤕

(If you want, I can have a look on your media_processing.conf file... send it by email... my surname at univ-pau.fr )

carlosTF

darrigan

In reply to your check list:

ca/app/conf/local (although the original media_processing.conf file is kept untouched in ca/app/conf
Running caUtils causes some fatal errors.
I'm uploading a new image on every new test, so no cache is in play here. I also review the media file and there are no watermarked images.
.jpg
It is.

I've emailed the media_processing.conf file to you as you kindly offered, as well as the caUtils errors. Hope you can put some light on this.

Thanks.

carlosTF

With the assistance of @darrigan I've looked at several causes to this, but I couldn't find out what the reason was for the watermark not being applied.

I ended reinstalling Providence running git pull origin master, which did the trick.

In order for the git pull to work I have had to correct some file and folder permissions. I'm positive I had made no changes to any Providence files other than those in /ca/app/conf/local, so I figure out that whatever was causing the watermak problem had to do with server user permissions.

As for the image path /usr/local/var/www/ca/app/watermarks/mymark.png works as <ca_app_dir>/watermarks/mymark.png does, so I've opt for the second.

Hope this helps anyone encountering a similar problem.

Again, my gratitude to @darrigan and @monica .