Summary: | DigiKam does not save tags as hierarchical tags in Extended Attributes | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | tagwerk19 |
Component: | Database-Baloo | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | KDE |
Priority: | NOR | ||
Version: | 7.2.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/graphics/digikam/commit/7e9deba251739bcd3b2786e7c63eb8ad1556a24f | Version Fixed In: | 7.2.0 |
Description
tagwerk19
2021-03-05 08:08:55 UTC
Git commit 7e9deba251739bcd3b2786e7c63eb8ad1556a24f by Maik Qualmann. Committed on 05/03/2021 at 11:45. Pushed by mqualmann into branch 'master'. write hierarchical tags to Baloo FIXED-IN: 7.2.0 M +2 -1 NEWS M +5 -5 core/libs/fileactionmanager/metadatahub.cpp M +3 -10 core/utilities/extrasupport/filesindexer/baloowrap.cpp https://invent.kde.org/graphics/digikam/commit/7e9deba251739bcd3b2786e7c63eb8ad1556a24f Checked with build 2021-03-06 That works so much better. I can see two changes, hierarchical tags I create within digiKam are written as hierarchical tags to the extended attributes - so I see: # file: testfile.jpg user.xdg.tags="Parenttag/Mytag" I can set these tags in Dolphin/Gwenview, read them into digiKam and write them out and it works. A "full circle" test works. I also notice that when digiKam reads the Extended Attribute Tags, they appear 'as given' in the Tag view, not prefixed by /BalooTags. I also do not need to create a new Tag under /BalooTags in order for it to be exported to the xattrs. For me, that is a real improvement. Many thanks! There might be an edge case when someone deletes tags within digiKam and expects the tags to be cleared when written to the xattr. Can check and log this as a separate issue (In reply to tagwerk19 from comment #2) > There might be an edge case when someone deletes tags within digiKam and > expects the tags to be cleared when written to the xattr. Can check and log > this as a separate issue See bug 434060 |