[digiKam-users] Digikam puts its "signature" in metadata even when no other changes - why?

Remco Viƫtor remco.vietor at wanadoo.fr
Fri Sep 21 10:48:42 BST 2018

On vendredi 21 septembre 2018 10:22:54 CEST Jack Marxer wrote:
> I think that the option to update the timestamp (Settings, Configure
> > digikam, Metadata, "update filestamp when files are modified")
> I just saw this today and am very sorry that I didn't notice it before.

No need to yell, it won't replace factual arguments...

And i disagree, as a default, the "file modified" timestamp should be updated 
when files are, well, modified.

At least for me, the expected behaviour for the "modification" timestamp is to 
reflect the last time the file was modified, Anything else would be surprising.
And one of the principles of deciding what should be the default is that it 
should be the least surprising behaviour.

That modification timestamp helps when you want to collect a number of edits, 
or need to remove sidecars: just order by timestamp in a file manager, and 
you'll have all the original files together. That means there's less risk of 
deleting an original image file.

Don't forget that the image metadata contain the original date the image was 
created (i.e. the shutter was pressed). That one should never be touched 
automatically (and isn't, afaik), and manually only for a good reason (e.g. 
camera clock was wrong).


More information about the Digikam-users mailing list