[Digikam-devel] [digikam] [Bug 337688] Reading/writing of keyword-tags to jpg and xmp corrupts tag hierarchy, duplicate root tag

[Christian]

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

--- Comment #11 from Christian <buitk14 at A1.net> ---
Created attachment 87882
  --> https://bugs.kde.org/attachment.cgi?id=87882&action=edit
Digikam 4.1  automatically created xmp with explicit root tag.

I found an older example in the backups - it was created with digikam
4.1.0-11.1
Unfortunately it is to big - I have no images below 4 MB. I added the xmp only
and will prepare an ftp download with more examples.

I used this jpg to store and import all tag keywords on other workstations. The
xmp file was created without asking - i guess because there are too many tags
selected to be embedded.

You can see the _Digikam_root_tag_ that caused me a lot of pain in the last
weeks. 

As I mentioned I could create my hierarchy without the root tag as well (I did
before), but then these tags are not joined with the tags digikam reads from
new images that have been tagged on another workstation.

In short:
I moved my tags below the root tag - this was a lot of work. There was no such
tag before. But when I imported metadata (in 3.5) this tag was inserted by
digikam - same behaviour in 4.1. For me the only way to join tagged images from
several workstations was to rearrange my tags this way. Is 4.1 going nuts
because of this tag? 

By the way, why does dk introduce this unwanted parent-tag when reading from an
image that was not tagged with this root-tag visible in the GUI (same in 3.5
and 4.1)? There was no such tag in the xmp metadata - I checked that - but
after importing metadata this root tag is shown in the GUI.

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