darktable-org / darktable-org/darktable

tagging module discrepancy with collection module in showing current collection of tags

Open
#19,762 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

This occurs in both the lighttable and darkroom views of dt.

The tagging module and collection module have a discrepancy in showing current collection tags when there are free nodes.

Steps to reproduce

Assume there is a tag "plant" applied to 8 images; a tag "plant|tulip" applied to 2 images (both of those images also have the "plant" tag); and 4 images with "plant|rose" (none tagged with just the "plant" tag).

When in the tagging module, right-clicking "plant", then choosing "go to tag collection" the current view shows 10 images: just the 10 tagged with the "plant" tag, not the 4 with the "plant|rose" tag.

In the collections module, when choosing the "plant" tag it shows 14 images in the current view: the 10 with the "plant" tag and the 4 with the "tag|plant".

There is no indication from the manual that the_tagging_ module's "got to collections" should work differently than the collections module.

Expected behavior

the two options listed above should behave the same, or the manual should be updated to reflect the exact behavior of each and why they are different

Logfile | Screenshot | Screencast
Image Image
Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.3.0+882~g916b7e4c99

What OS are you using?

Windows

What is the version of your OS?

Windows 11 Pro

Describe your system

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the stated plant, plant|tulip, and plant|rose setup in darktable, then compare the tagging module's “go to tag collection” action with the collections module's plant selection. Read the relevant tagging and collections module behavior and the manual; done means both actions agree or the manual clearly documents the difference.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.