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

--- Comment #9 from Steve Franks <steve...@gmail.com> ---
Digikam is correctly reading the tagtree (hierarchy) for a lot of images,
but not all.
It appears to import the tags and hierarchy from several places for an
image. e.g. .XMP sidecar, which may contain several sets of tags in
different sections and imbedded data in the image. My main problem is that
the formats of the xmp sections varies depending upon which software wrote
the data. Over the years I have used Microsoft Photo Gallery, Google
Picasa, Adobe Elements and Adobe Lightroom.
Each program has its own opinion so the same tagtree (e.g. Places|East
Kent|Deal) will appear several times, with various delimiters (i.e. | \ ,
.). Digikam seems to correctly parse Places|East Kent|Deal, but every time
it rescans files other variants reappear.
It would be nice if merging tags meant that the tags in the picture merged,
but it doesn't.
One solution would be software that would allow all not standard tags to be
deleted leaving only those written by digikam.

Changing whether digikam reads/writes sidecar files has had an unexpected
result. The number of images with no tags has increased from about 1200 to
6449.
Regards
Steve

On Sun, 13 Jan 2019 at 13:47, Sebas <bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=399596
>
> --- Comment #7 from Sebas <djse...@home.nl> ---
> Seems like I forgot to answer to Maik Qualmann's last reply.
>
> I did fix the issue manually so it is a bit hard for me to recall the whole
> thing, but let's try.
>
> Digikam saves individually in image metadata (if enabled) these things:
> 1. Tags
> 2. Tagtree
>
> I removed some tags and added new ones, or maybe renamed something. Then,
> after
> rescanning (because of some 'Collection disappearing if network share
> unavailable' bug) the old tagtree keeps appearing again and again.
>
> What I found when opening these images in a text editor is that when
> removing
> tags, Digikam does not (always?) also remove that tagtree from custom
> metadata.
> It should do so when the tagtree ceases to exist. Maybe a check for this
> is not
> coded.
>
> Steve Franks, I am not sure it is exactly the same problem. I don't know
> how
> Digikam will try to build a tagtree from tags set by other programs.
> Obviously
> those programs will not save the tagtree to custom metadata as Digikam
> does and
> if they save the tagtree to metadata at all, I have no idea if Digikam can
> read
> other tagtree metadata than its own.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to