Bug 497567

Summary:	Feature Request: "No New Images for Deceased Persons"
Product:	[Applications] digikam	Reporter:	tab
Component:	Faces-Workflow	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	caulier.gilles, john.kizer, metzpinguin, michael_miller
Priority:	NOR
Version First Reported In:	8.5.0
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed/Implemented In:	8.6.0
Sentry Crash Report:

Description tab 2024-12-16 16:43:23 UTC

I would like to suggest a feature that allows marking a person as "deceased," preventing new images from being assigned to them.  

**Background:**  
When a person is deceased, they can only appear in photos taken before their date of death. Images taken after this date cannot possibly include this person.  

To make this functionality flexible, it should be possible to enable or disable this restriction. This is necessary in cases where the image capture date may not accurately reflect when the photo was taken (e.g., when scanning old slides that are newly digitized but were originally taken before the person's death).  

**How it could work:**  
- If a date of death is set for a person and this feature is enabled, face detection or person suggestions for this individual should only occur for photos with a capture date earlier than the date of death.  

This feature would improve the accuracy and logic of person assignments in photo libraries, especially for large archives.

Comment 1 Maik Qualmann 2024-12-17 07:44:36 UTC

This wish has already been submitted once. We have already discussed it and rejected it.
Our goal is to further improve face recognition so that such "crutches" are not necessary.

Maik

Comment 2 John Kizer 2024-12-29 00:39:07 UTC

(In reply to Maik Qualmann from comment #1)
> This wish has already been submitted once. We have already discussed it and
> rejected it.
> Our goal is to further improve face recognition so that such "crutches" are
> not necessary.

Hi - from a bug triage perspective, this one looks like a duplicate of https://bugs.kde.org/show_bug.cgi?id=459499 - however, you mentioned that the concept in this request has been rejected. Should both this and 459499 then be in RESOLVED/INTENTIONAL status or something like that (or are they actually different issues and I just misunderstood)?

Comment 3 Michael Miller 2024-12-29 13:54:07 UTC

(In reply to John Kizer from comment #2)
> (In reply to Maik Qualmann from comment #1)
> > This wish has already been submitted once. We have already discussed it and
> > rejected it.
> > Our goal is to further improve face recognition so that such "crutches" are
> > not necessary.
> 
> Hi - from a bug triage perspective, this one looks like a duplicate of
> https://bugs.kde.org/show_bug.cgi?id=459499 - however, you mentioned that
> the concept in this request has been rejected. Should both this and 459499
> then be in RESOLVED/INTENTIONAL status or something like that (or are they
> actually different issues and I just misunderstood)?

Hi John,
You are correct.  I'll close both issues in BugZilla.

I hope you like the improvements to the face engine coming 8.6.0.  We're always working to make face recognition more accurate.


Cheers,
Mike

Comment 4 tab 2025-01-05 09:55:03 UTC

"I will wait for 8.6.0. Thanks a lot for the help and your engagement with the product."