Bug 263400 - Newly detected faces should be stored in a dedicated virtual album for checking
Summary: Newly detected faces should be stored in a dedicated virtual album for checking
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Workflow (show other bugs)
Version: 2.0.0
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-17 11:49 UTC by unapiedra
Modified: 2017-08-15 18:21 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.5.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description unapiedra 2011-01-17 11:49:59 UTC
Version:           2.0.0 (using KDE 4.5.1) 
OS:                Linux

When running face detection on my collection detected faces are sorted into the already existing "folders"/"tags". This is good. 

However, I need something that lets me see which faces are new. 
This could be done like it's done in email with a small number behind the folder (3) indicating 3 new messages or 3 new photos. 
It could also be done in a "newly detected photos" tag or the like. 

Reproducible: Always
Comment 1 SB 2011-10-18 18:38:43 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 caulier.gilles 2011-12-14 13:59:28 UTC
unapiedra,

It still valid using digiKam 2.4 ?

Gilles Caulier
Comment 3 caulier.gilles 2014-08-24 17:32:57 UTC

*** This bug has been marked as a duplicate of bug 336253 ***
Comment 4 caulier.gilles 2017-01-16 19:02:01 UTC
Git commit 7a7c29c0b8b36bd30a190a6cb4dc5f43960034a8 by Mario Frank.
Committed on 16/01/2017 at 18:24.
Pushed by mfrank into branch 'master'.

I introduced the new special tag Unconfirmed which is automatically created if not present. In detection phase, faces are marked as unknown as usual.
In recognition phase, the faces are marked with the recognised face tag, as usual. But additionally, they are connected as autodetected person to the Unconfirmed tag. In this property, I store the id of the person as which the face was recognised and also the
face region.

With small adoptions in the image lister all recognised faces are now shown both in the face tag which was recognised (person A) and the Unconfirmed tag (with the suggested tag being person A).

Confirming the person can now be done in both tags. And the confirmed identity is set as expected. Confirming the face also removes the face from unconfirmed tag.
Rejecting the face also removes the face from both the recognised tag and also from the Unconfirmed tag. Rescanning for faces (detection) also removes the connection
to the Unconfirmed tag if unconfirmed results should be thrown away.
FIXED-IN: 5.5.0

M  +3    -1    NEWS
M  +10   -0    libs/database/coredb/coredbconstants.cpp
M  +2    -0    libs/database/coredb/coredbconstants.h
M  +21   -3    libs/database/item/imagelister.cpp
M  +25   -0    libs/database/tags/facetags.cpp
M  +3    -0    libs/database/tags/facetags.h
M  +15   -1    libs/database/tags/facetagseditor.cpp
M  +12   -0    libs/database/tags/facetagsiface.cpp
M  +5    -0    libs/database/tags/facetagsiface.h

https://commits.kde.org/digikam/7a7c29c0b8b36bd30a190a6cb4dc5f43960034a8