This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Moving a hierarchy of tags (a tag with subtags) around?

Tags: None
(comma "," separated)
marcuschristopher
Registered Member
Posts
21
Karma
0
OS
Hi all,

I'm not sure, if this is the right place to ask... I'm hoping for some help regarding a long-standing problem that I'm having with Digikam. Now, I'm really not sure, if what I'm describing is a bug or if I'm asking Digikam to do something it wasn't designed for. Anyway, I'd be grateful for any help you can provide: If I find that Digikam is unsuitable for my needs, I will have to investigate other options.

Anyway: What I'm trying to do is the (to me) simple task of reorganizing my tag hierarchy. To give you a simple example, I do the following:

  • Open Digikam
  • Open the tag manager
  • Click any tag and drag-and-drop it to under another tag
  • Close the tag manager
  • Close Digikam

Upen re-opening Digikam the tag that I moved should still be under the new tag, shouldn't it? At least that's what I would expect. However, having read a few articles that dealt with how tags are stored in images, in sidecar files and in the database itself, I'm not so sure anymore...

Because, the things is: That is not at all what is happening. The procedure described above only seems to work for single tags without subtags. When I try to move a tree of tags (e.g. a tag with a subtag), however, nothing seems to change in the database at all: The tag-tree does appear to be filed under the new tag for the moment - upon re-opening Digikam, however, the changes are reverted and the tags are back where they were before.

By the way: I worked in version 4.12 before and lost (!) hundreds, if not thousands, of tags by this procedure, because I re-organized whole tag trees and then deleted the original root tags. Upon re-opening Digikam that root tags were gone, of course, but the trees that I had moved had disappeared as well. A frustrating experience to say the least. So, thinking that must be a bug, I updated to 5.1 recently. And realized that things are behaving exactly the same.

What am I missing here? Is this a bug? Or is this a request that simply won't work, because of... I don't know... the way hierarchies are stored maybe?

Any help would be much appreciated. Thanks in advance!
Marcus


Bookmarks



Who is online

Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]