Bug 208553

Summary: wrong number of images in a closed recursive tag
Product: [Applications] digikam Reporter: noeck <noeck.marburg>
Component: Tags-EngineAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: caulier.gilles
Priority: NOR    
Version First Reported In: 0.10.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 1.0.0
Sentry Crash Report:

Description noeck 2009-09-25 21:40:27 UTC 
Version:           0.10.0 (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

Situation: I have 10 fotos and all have a tag "ExampleTag" and a tag "SubTag" that is a child of the ExampleTag:

- ExampleTag (10)
  |
  '-SubTag (10)

Now, if I close the entry ExampleTag the count of images of all children of ExampleTag are added to the image-count behind ExampleTag:

+ ExampleTag (20)

Which is wrong because there are only 10 images behind ExampleTag which are all tagged twice.

I couldn't find that bug in the existing ones yet.
Comment 1 Andi Clemens 2009-10-25 02:35:07 UTC 
Well it isn't actually a bug, but another way of interpretation :)
We could add an option to either display the real amount of images or the recursive amount (although I'm not a fan of adding more and more options to setup, it is already too big).

Any other suggestions?
Comment 2 noeck 2009-10-30 13:37:16 UTC 
Ok, now I see the interpretation you meant. You're right, you can count images or tags (but subsubtags are not counted neither).
I use those numbers to check if every picture has a tag of a category, therefore it would be useful.

EXAMPLE:
(20 pictures are tagged and should have at least one of the following tags, but can have more)

 - quality (0)
    '-nice (10)
    '-important (8)   <- e.g. 6 of the nice ones and 2 of the bad ones
    '-bad (10)

gets

 + quality (28)

I would expect 

 + quality (20)

then I could easily check if every picture has at least one tag.

END OF EXAMPLE

I would like the feature, but I think it's up to the developers to decide if adding an option is a good idea.
Comment 3 Marcel Wiesweg 2009-10-30 16:33:41 UTC 
It's not too easy to implement. To get the number "20" in the above example, you must find all subtags for "quality", and make a query for unique image ids tagged with any out of this group of tags.
Comment 4 caulier.gilles 2009-10-30 19:38:33 UTC 
For me the current behavior is enough. No need to make a big puzzle...

Gilles
Comment 5 noeck 2009-11-07 15:27:20 UTC 
I can't estimate the effort that is needed in this case. But according to what Marcel wrote I think it's not worth it. There are so great features already there and to come, so don't waste time on this one.

So as I opened this report, I change the status to resolved and I suppose "wontfix" is the right option.