Bug 415777

Summary:	Add a tool to remove duplicate faces.
Product:	[Applications] digikam	Reporter:	Andrius <aegoreev>
Component:	Faces-Workflow	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	benjcmin, caulier.gilles, craigfryer.au, jamie+bugskdeorg, maeseee, michael_miller
Priority:	NOR
Version:	7.0.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:	8.6.0
Sentry Crash Report:

Description Andrius 2020-01-01 22:49:31 UTC

Hello,

I have noticed that if you don't select "skip images already scanned" when scanning for faces digiKam might create duplicate entries on a single image.
Here is a screenshot of an example:
https://drive.google.com/open?id=1UqT26vs-mQEDVPwUOAoJtcB39BiHdpYc
I was wondering if there could be added a functionality to get rid of these, for example: IF an image has two face tags assigned with the same name THEN do something about it. I would suggest two actions: 1. Just filter all the images with the duplicate face tags 2. Delete one of the duplicate tags automatically.
Just an idea.

Comment 1 Maik Qualmann 2020-11-10 19:28:33 UTC

*** Bug 428941 has been marked as a duplicate of this bug. ***

Comment 2 Jamie 2021-08-04 10:42:17 UTC

Confirming that I am also experiencing this issue with the following details.
DigiKam 7.3.0 upgraded from 7.2.0 on July 15 2021

+Issue was NOT experienced prior to the July 15 upgrade. 
+The computer running DigiKam at the time of upgrade was NOT on its usual home network and some albums were not available.  Specifically a V: mapping to a local NAS.
+The issue has effected many but not all photos.  Unless there is a log, I cannot attest to the settings for an scans after the upgrade.  But I believe this may have been the first time in many months to scan to detect faces and "merge results".

OS Name	Microsoft Windows 10 Enterprise
Version	10.0.19043 Build 19043
Processor	Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2496 Mhz, 2 Core(s), 4 digikam version 7.3.0
Solid framework version 5.80.0

Comment 3 Maik Qualmann 2021-09-26 15:59:50 UTC

Git commit 7253440154529ab5d986c2869b08b5281639028e by Maik Qualmann.
Committed on 26/09/2021 at 15:57.
Pushed by mqualmann into branch 'master'.

check for existing faces in the database
when reading face metadata.
Related: bug 440773, bug 441378
FIXED-IN: 7.4.0

M  +2    -2    NEWS
M  +37   -11   core/libs/database/item/scanner/itemscanner_photo.cpp

https://invent.kde.org/graphics/digikam/commit/7253440154529ab5d986c2869b08b5281639028e

Comment 4 Craig 2023-07-20 02:33:49 UTC

(In reply to Maik Qualmann from comment #3)
> Git commit 7253440154529ab5d986c2869b08b5281639028e by Maik Qualmann.
> Committed on 26/09/2021 at 15:57.
> Pushed by mqualmann into branch 'master'.
> 
> check for existing faces in the database
> when reading face metadata.
> Related: bug 440773, bug 441378
> FIXED-IN: 7.4.0
> 
> M  +2    -2    NEWS
> M  +37   -11   core/libs/database/item/scanner/itemscanner_photo.cpp
> 
> https://invent.kde.org/graphics/digikam/commit/
> 7253440154529ab5d986c2869b08b5281639028e

I am still seeing this problem in version 8.0.0 (may be 8.0.1) on Windows 10.

Comment 5 Michael Miller 2025-02-02 13:13:16 UTC

Closing because the face pipeline was completely rewritten for 8.6.0.  The repro steps are no longer valid.

Cheers,
Mike