tags make me crazy

Frédéric Da Vitoria davito9w at free.fr
Mon Mar 3 10:25:39 GMT 2025


Hello Maik,

Sorry it took me so long to answer, but I needed all this time to 
understand the implications of your question and to find possible 
solutions. Not that it was very complicated but lots of other matters 
took the precedence.

First, tell me if I am right with the following guess:

 1. dK reads the tags from an photo P, with "A/A1/X"
 2. in the tags database, dK finds two "X": "A/A1/X" or to "B/B1/X".
 3. dK correctly writes "A/A1/X" in P, but because dK handles also DC,
    which does not support hierarchical tags, dK writes also "x" .
 4. dK re-reads the tags in the photo, finds the "x" tag and adds "x" to
    the tags database.

Up to step 3, I don't think anything is wrong. Step 4 creates the 
duplicate in the database.

In a way, dK is correct, the tag "X" is at root level in the DC, 
non-hierarchical system. But storing tags in a non-hierarchical way is 
only there to allow tags to be read by software which don't understand 
hierarchical tags.

Would disabling any non-hierarchical system be a workaround? I unchecked 
Xmp.dc.subject, Iptc.Application2.Keywords and Exif.Image.XPKeywords and 
checked all other tags systems, and indeed I can now have duplicates.

I can see several ways to improve things, but none would be complete. So 
maybe stating that users should either uncheck those three systems or 
avoid duplicates is the best. I suggest that the tags system check list 
should indicate whether each tag system is hierarchical or not, this 
would make configuration more clear, and few users are aware of those 
subtleties.

-- 

Frédéric Da Vitoria

On 11/12/2024 21:08, Maik Qualmann wrote:
> Another explanation of the tags: digiKam finds a tag X without a hierarchy in
> the uncleaned metadata of an image.
> Where should digiKam assign it now, to A/A1/X or to B/B1/X. digiKam can't
> decide, so it creates the tag X in the root.
> What would be the right solution for you?
>
> Maik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20250303/92f85779/attachment.htm>


More information about the Digikam-users mailing list