There are very few of my files where the tree structure is not read by digikam. There are 3 tags on one file. The structure is right with two of them but not with the 3rd. I checked, that the right data is saved in the files with exiftools. It happens with a tag which looks like this: Last Keyword XMP: Tätigkeit/Feierlichkeiten/Weihnachten/1. Weihnachtsfeiertag Categories: <Category Assigned="0">Tätigkeit<Category Assigned="0">Feierlichkeiten<Category Assigned="1">Weihnachten<Category Assigned="1">1. Weihnachtsfeiertag</Category></Category></Category></Category></Categories> Tags List: Tätigkeit/Feierlichkeiten/Weihnachten/1. Weihnachtsfeiertag Hierarchical Subject: Tätigkeit|Feierlichkeiten|Weihnachten|1. Weihnachtsfeiertag Catalog Sets: Tätigkeit|Feierlichkeiten|Weihnachten|1. Weihnachtsfeiertag Subject: 1. Weihnachtsfeiertag Keywords: 1. Weihnachtsfeiertag In DIgikam it's just shown as: Tags/1/Weihnachtsfeiertag Can reproduce it with DIgikam 4.12 and digikam 5.0 beta 6. Reproducible: Always Steps to Reproduce: 1. Read the image file... 2. 3. Actual Results: Tags/1/Weihnachtsfeiertag Expected Results: Tags/ Tätigkeit/Feierlichkeiten/Weihnachten/1. Weihnachtsfeiertag
I have created your tree hierarchy. The problem is not to reproduce here. Can you provide a test image? Maik
Sure, I send you the link to the picture via mail, because there are people on all of them...
Created attachment 99221 [details] tags.png The problem is not to reproduce with the image here. See the screenshot. Maik
You're right. I just checked and the picture I sent you was not only the one with the least faces on it but also one which didn't show this problem (though being in the same album with the same tag...) Gonna send you another one.
Created attachment 99223 [details] It looks like this
The last test image has no XMP tags. The keywords coming from "Iptc.Application2.Keywords". Here we can actually have a point as separator. I will look which applications uses points as separators. I would disable "Iptc.Application2.Keywords" in the metadata settings and add new keywords to the image. Maik
I only use digikam for tagging and Nikon Capture-D for developing the raws.
Ok, so the problem is that the XMP-Keywords which contains the trees have not been saved somehow?
frank, yes certainly. Did you check your metadata settings in digiKam ? Gilles Caulier
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last bundle is available at this url: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier
See related bug 421464
See also related bug #421464 about EXIF:XP* tags
Git commit be46e3d31bff4ad7581adf6f242a65991fc5bb14 by Maik Qualmann. Committed on 25/12/2021 at 18:23. Pushed by mqualmann into branch 'master'. fix read Iptc.Application2.Keywords FIXED-IN: 7.5.0 M +1 -1 NEWS M +5 -12 core/libs/metadataengine/dmetadata/dmetadata_tags.cpp M +0 -1 core/libs/metadataengine/dmetadata/dmetadatasettingscontainer.cpp https://invent.kde.org/graphics/digikam/commit/be46e3d31bff4ad7581adf6f242a65991fc5bb14