Bug 423387

Summary:	Add Button to instanlty set face tag as Unknown
Product:	[Applications] digikam	Reporter:	Pedja <pedja>
Component:	Faces-Workflow	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, kartikx2000, metzpinguin, pedja
Priority:	NOR
Version:	6.4.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:	7.2.0
Sentry Crash Report:

Description Pedja 2020-06-23 08:12:12 UTC

SUMMARY

When Scan for faces is done, number of photos with Unconfirmed tag are created. That is OK.

When user lists photograph with Unconfirmed tag he has only two options: to confirm tag (after optional editing) and to remove tag.

Problem is that face detection creates lots of false detection - it finds out face but it assignes wrong person. Person is actually unkown or not important for photo or at that moment he cannot remember persons name so he wants to leave it for later. 

User cannot leave it with wrong assigned person tag as those images do show elsewhere as assigned to that person which is plainly wrong.

If user removes that tag it just means it will pop up in another scan and again with wrong face recognition. 

There is an option for user to assign Unknown person tag which is most logical. But, each time user has to search for that tag which means loosing to much time, especially as unknown persons are quite often.

It would be great to have third button besides Confirm and Remove: Unknown. That would allow user to quickly mark face as unknown in single click.

Comment 1 Maik Qualmann 2020-06-23 10:00:36 UTC

A student is currently working on this problem as part of GSoC 2020.

https://bugs.kde.org/show_bug.cgi?id=423114#c1

Maik

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

Comment 2 Pedja 2020-06-23 10:37:16 UTC

(In reply to Maik Qualmann from comment #1)
> A student is currently working on this problem as part of GSoC 2020.
> 
> https://bugs.kde.org/show_bug.cgi?id=423114#c1
> 
> Maik
> 
> *** This bug has been marked as a duplicate of bug 423114 ***

I do not see that bug report is similar to this I posted.

Comment 3 Maik Qualmann 2020-06-23 11:08:57 UTC

Your bug report is already included in various bug reports. The desire to make a wrongly unconfirmed face unknown again already exists. I moved it to this bug report so that our student reads your bug report.

Maik

Comment 4 Maik Qualmann 2020-06-23 11:57:11 UTC

It would be nice if you would test the current digiKam-7.0.0-RC version. Compared to digiKam-6.4.0, more than 740 bugs were closed and a new face engine was introduced.

It is important to build up the training database for the new engine.
Tools-> Maintenance Tool-> Face detection [x] training database
The database is now created based on the faces already confirmed.

https://files.kde.org/digikam/

Maik

Comment 5 Kartik 2020-06-23 18:11:09 UTC

(In reply to Pedja from comment #0)
Hi, I did include this bug as part of my project, and I fixed it last month. The fix should be present in the post-September release of DigiKam. 

Have a look at this for a demo of the Feature : https://imgur.com/a/eaFFDG4

The Red Minus button performs the "Unknown" operation you mentioned. Pressing the cross button performs the remove operation as earlier.

Kartik

Comment 6 caulier.gilles 2020-09-12 05:39:31 UTC

Fixed with #423114