[Digikam-devel] [Bug 309058] The digiKam database can't be synchronized with XMP sidecars.

[Marcel Wiesweg]

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

--- Comment #6 from Marcel Wiesweg <marcel.wiesweg at gmx.de> ---
The "More->" actions essentially do the same but are old code, not
multithreaded, I should remove them or rather replace them with the "Image->"
actions.
Everything honors the settings regarding XMP sidecar reading or writing.

Your observation regarding the orientation is true: Here the Exif value is
given priority over the corresponding XMP value. This is a bug for your
scenario.
In the old days, we had IPTC and Exif; then came XMP, and the question was how
to detect conflicts if only IPTC or Exif was edited by an older program and the
change not updated into XMP.

With XMP sidecar files, relevant Exif and IPTC fields are copied into
corresponding XMP fields in the sidecar file. This is a quite different
situation. I tend to define that if a sidecar exists, sidecar information
always takes precedence over file information, not only for XMP, but also for
Exif and IPTC. This is done by simple merging.

The situation is unclear when a tag does not exist in the sidecar, but in the
file. Assuming we have "write only to sidecars", removing properties will only
happen in the sidecar. If all no keywords or rating are found the sidecar but
in the file, this can be because
a) These fields are stored in the file and were not copied to the sidecar. They
are valid.
b) These fields were removed, changes applied to the sidecar, but not to the
file. They are invalid.
Ideas for a clean solution?

-- 
You are receiving this mail because:
You are the assignee for the bug.