Bug 499740 - It would be nice to have a way to review recently tagged faces
Summary: It would be nice to have a way to review recently tagged faces
Status: RESOLVED DUPLICATE of bug 298160
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Workflow (other bugs)
Version First Reported In: 8.6.0
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-10 08:34 UTC by Michael Moore
Modified: 2025-12-03 04:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Moore 2025-02-10 08:34:02 UTC
In the current workflow, if you tag some faces incorrectly it is very difficult to find the photo which you just tagged a face in. 

WISH: I wish there were a way to review recently tagged faces

USE CASES: 

* You know you made a mistake, but you can't find the photo you just tagged. This is especially problematic if you are confirming suggestions for a single person. 
* Multi-user review - One person can do an initial pass, and a second user could review the tagging
* Review in case of digiKam bugs (eg. https://bugs.kde.org/show_bug.cgi?id=499739) 

MODES: 

I would suggest that a tool be added to select all Images which have been tagged with at least two modes: 

1. Show the last N faces which have been tagged (eg. show the last 1000 faces I tagged, etc.
2. Show all faces tagged in the last N minutes/hours/days

The results should be able to have the usual filters from the Filter pane apply. 

SUGGESTION: 

I would suggest adding a new created_ts column to the ImagesTags table, with a default value of CURRENT_TIMESTAMP. Queries could then leverage this timestamp for the "last N minutes" mode of filtering, or to sort for selecting the "last N tagged" mode.
Comment 1 robinedgar 2025-12-03 04:39:36 UTC
Agreed!
See also https://bugs.kde.org/show_bug.cgi?id=298160

*** This bug has been marked as a duplicate of bug 298160 ***