[digiKam-users] Possible bug in Digikam? Inconsistent behavior when adding new hierarchical tags in Digikam

[Sebastian Bayer]

Hi everyone,

some days ago I've posted a question concerning hierarchical tags in Digikam at stackexchange: 
https://photo.stackexchange.com/questions/108739/inconsistent-behavior-when-adding-new-hierarchical-tags-in-digikam

One comment suggested that I could try to post this in the mailing list as he suspected this to be a bug. 

Here's the text of the original questions for completeness:

 

Whenever I create a new hierarchical tag in Digikam (right-mouse click on image -> Assign Tag -> Add New Tag) then all hierarchy levels are applied to the image. For instance, if I have the hierarchy Tag 1 / Tag 2 and add a new tag Tag 1 / Tag 2 / Tag 3 to an image, then all tags Tag 1 / Tag 2 / Tag 3 are applied to the image.
In contrast, when I add an existing hierarchical tag to an image, then only the bottom level is applied. Picking the example from above up, when I add Tag 3 to an existing image, then only Tag 3 is applied but not Tag 1 / Tag 2.
I find this a bit inconsistent, as I now have some images with the full hierarchy and some with the bottom level only.
Is there some way to standardize the behavior of Digikam?

Does anyone of you have an idea what could be the problem and have a remedy?

Thanks in advance and regards 

Sebastian

[woenx]

Hi Sebastian,

If Tag3 is placed at Tag1/Tag2/Tag3, and you only use the Tag3, the picture
will still contain the whole hierarchy internally (you can look it up at the
XMP metadata), but only Tag3 will be "checked". I personally, sometimes only
check the higher level of the hierarchy in order to avoid lots of tags in
the picture, because I feel they are redundant.

I just checked, and adding a new tag using the right-click, Assign Tag, Add
new Tag, adds all the tags of the hierarchy if these tags are new, but if it
is using an existing hierarchy, will only add the tag that you just added
within the hierarchy.

e.g. if Tag1 and Tag1/Tag2 do not exist, and you assign them, the new
picture will have: Tag1(✓)/Tag2(✓). If Tag1 already exists in the database,
and you assign Tag1/Tag2, the picture will have: Tag1( )/Tag2(✓). Of course,
you can just click on Tag1 afterwards and assign it manually.

I personally think it's intuitive this way. If you are adding new tags to
the database that do not previously exist, it assumes you want to assign all
of them. If you are adding a new tag inside an existing tag tree, only the
new tag is added (but within the hierarchy).



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[woenx]

By the way, if you want all the pictures to have the full tree, just select that Tag in the Tag panel, and check all the lower tags in the hierarchy. They will be written in all the files (or in sidecars if you configured it that way). And don't worry, that metadata should be compatible with other picture managers that can read XMP.

---

Sent from the digikam-users mailing list archive at Nabble.com.

[Sebastian Bayer]

Hi woenx,

many thanks for your explanations. Good to know that the whole hierarchy is actually stored in the xmp tag, that helps.

Thanks

Sebastian

Am Mo., 17. Juni 2019 um 21:43 Uhr schrieb woenx <[hidden email]>:

By the way, if you want all the pictures to have the full tree, just select that Tag in the Tag panel, and check all the lower tags in the hierarchy. They will be written in all the files (or in sidecars if you configured it that way). And don't worry, that metadata should be compatible with other picture managers that can read XMP.

---

Sent from the digikam-users mailing list archive at Nabble.com.