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

[Elle Stone]

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

--- Comment #10 from Elle Stone <l.elle.stone at gmail.com> ---
> --- Comment #9 from Marcel Wiesweg <marcel.wiesweg at gmx.de> ---
> There's a problem in digikam that Exif takes precedence over XMP regarding
> the
> orientation. For all other fields, XMP takes precedence.

Is there a "use case" reason why exif takes precedence over XMP for
orientation?

Tangentially related - digiKam writes the tiff:orientation tag to the
xmp sidecar for jpeg image files. But it won't write the
tiff:orientation tag to the xmp sidecar for Canon cr2 raw files. Is
this a feature or a known bug? It throws a wrench in my on-going
effort to work around digiKam as it now handles XMP sidecars.

> If there are keywords, rating etc. defined in XMP, these entries always
> take
> precedence over entries in Exif and IPTC. The problem comes when e.g. all
> keywords are removed from the image and thus the sidecar, but IPTC in the
> file
> remains unedited. When not finding an entry in XMP, there will be a fallback
> to
> IPTC. During the step of reading file and sidecar metadata, we thus need to
> cancel from the read Exif and IPTC those fields which would be copied to
> the
> sidecar.
> This is possible. I'm not quite sure if there are implications and cases
> where
> this construct brings other problems.

When writing to the image file (instead of the sidecar), doesn't
digiKam write dc:subject to dc:subject and also to iptc:keywords (and
possibly other places)? And also for rating-related tags, etc? Just as
it writes the orientation information to exif as well as to
xmp-tiff:orientaion? If so, then telling digiKam to ignore iptc/exif
**in the specific cases where writing to the image would change the
iptc/exif equivalents as well as the xmp tags** would seem to just
make writing to a sidecar equivalent to writing to the image.

I would like to see digiKam ignore the iptc/exif as above when the xmp
is different in the sidecar, but I wouldn't want to see a change in
the current digiKam behavior mess up someone else's workflow. Perhaps
a question should be posted on the user forum to ask for input from
other people who use sidecars?

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