| Summary: | Extending single tag to a group of tags | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | bugs bunny <drch> |
| Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | caulier.gilles, reiner.nix |
| Priority: | NOR | ||
| Version: | 3.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
*** Bug 225562 has been marked as a duplicate of this bug. *** Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. *** This bug has been marked as a duplicate of bug 463343 *** |
Motivation: Currently, tags are organized as "single tag hierarchies". This makes the tagging of images with multiple tags rather tedious - especially if images are tagged ("later on") Example: An event may be described as a tuple (event_type, organizer, date, location, topic, participants), whereby each component may be elements in different branches of the tag hierarchy. If, later on, additional images are imported which belong to the same event, all single components have to be tagged again Proposal: The concept of "named tag groups" is introduced as follows: 1. the user can define a named tag group "CeBIT 2013" as (fair, Hannover, 2013, IT). If later on, new images are imported, they can easily be tagged with "CeBIT 2013". 2. new "fair-events" can be generated by generation a copy of "CeBIT 2013", and then modifying the components with sibling tags. GUI: 1. right pane / tag section: the tag group can be generated by identifying the corrensponding component tags (as is) and storing the group under a group name (new) 2. right pane / filter section: tag groups can be selected/deselected, "must have", "must not have" in the same way as single tags 3. left pane / my Tags: to by extended by "tag groups" 4. left pane / search: search groups to be extended by "tag groups" (Remark: tag groups can already be defined by set of search groups with single tags each)