[Digikam-devel] [Bug 220545] Cannot write XMP sidecar files

[Jakob Malm]

https://bugs.kde.org/show_bug.cgi?id=220545





--- Comment #18 from Jakob Malm <jakob malm gmail com>  2010-05-05 20:46:17 ---
(In reply to comment #17)
> Allowing to use XMP sidecar file and to not touch the original files will also
> improve backups: for now, each time I change any metadata (usually tags), the
> file is backuped again and again. My backup program (backuppc) must store a
> full new version of the image instead of using (hard)links to the previous
> 'version'. If XMP sidecar were used, the original image would not change,
> avoiding similar but not exact copy in each backup. XMP files would be
> duplicated but their size is a lot smaller than the original image.

Yes, this will indeed be a very nice effect. Thanks for your encouragement!

> A second thought: I see that you will use the same basename with the .xmp
> extension. How will you deal with 'foo.jpg' and 'foo.avi' when both present ?
> (ignore one ? which one in this case ?) Won't 'foo.jpg.xmp' and 'foo.avi.xmp'
> be a better choice ?

For me, personally, foo.xmp is necessary. Perhaps it should be configurable? Is
foo.xmp a convention?

> A third thought: some other software (geeqie) allow to read/write xmp files in
> another directory. This way, photos can be on a read-only medium (CD or ro NFS)
> and xmp files (and so metadata) can still be edited and saved on the hard-disk.

Hmm... Interesting idea. In principle, this should be quite easy to implement.
But I would eventually like digikam to be able to reread the XMP sidecar when
it changes, and for this, it would need to be situated in a directory which
belongs to an album, so that digikam will notice the change. This might
complicate things a little bit.

Jakob

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.