[Digikam-devel] [Bug 303690] New: hierarchical tags inconsistencies

[Patrick Scharrenberg]

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

            Bug ID: 303690
          Severity: normal
           Version: 2.7.0
          Priority: NOR
          Assignee: digikam-devel at kde.org
           Summary: hierarchical tags inconsistencies
    Classification: Unclassified
                OS: Linux
          Reporter: pittipatti at web.de
          Hardware: Other
            Status: UNCONFIRMED
         Component: Tags
           Product: digikam

When using hierarchical tags (which I think will always be the case) there are
some inconsistencies in digikam handling these tags.

Assuming we have the tag "People" with two subtags "Maria" and "George":
+People
   + Maria
   + George

After adding these subtags to a photo (right click photo -> Assign Tag -> Maria
(My Tags/People) (and the same with George) I can find these tags in multiple
places:

1. the "assign tag"/"remove tag" menu (after right clicking an image) shows the
full path of a subtag 
2. In the properties view under "digikam properties" I find:
   Tags: People / George, Maria
    suggesting that Maria is no more a subtag of People
3. in the database (sqlite in this case) only the child tags are stored (this
can be fine)
4. in the XMP section of the metadata view the full hierarchy is saved in
various keys of various namespaces e.g. "Xmp.digiKam.TagsList"
5. filtering for people in the left tag view returns all photos having either
the people parent tag or *just* any of the subtags
6. filtering for people in the right tags filter view only returns images
explicitly tagged with the parent tag people but *no* photos only tagged with
the subtag.

I am aware of the new feature to set the "auto toggle" for parents and/or
children in the right tags filter and tags "edit" view. For the filter this is
a really nice feature. For edit tags view I thing this option is superfluous.
In my opinion a subtag implies that the parent tag is set as well (if maria is
a subtag of people, than maria *is* a person) and should always be set either
explicitly (as a separate tag in the various places) or implicitly (handled by
the software) but always consistently.

Reproducible: Always

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