Bug 366556

Summary: Add possibility to exclude an album (and possibily its children) from face detection
Product: [Applications] digikam Reporter: Stefano <rs4000>
Component: Faces-DetectionAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: wishlist CC: caulier.gilles, laurakittyinka, mario.frank
Priority: NOR    
Version: 5.0.0   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Stefano 2016-08-09 16:40:49 UTC
It would be desirable to avoid face-detection on album trees and subtrees where you don't care about face tagging: for example if you routinely shoot crowded public events you'd likely avoid to have those albums scanned for faces, having thousands of data to manually discard.

Reproducible: Always
Comment 1 Mario Frank 2017-01-17 10:12:29 UTC
It is already possible to select specific albums to scan. You can first select all albums and then unselect complete subtrees with context menu.

Is this what you expect?
Comment 2 Stefano 2017-01-17 10:19:14 UTC
Yes, but it would be convenient to have a persistent per-album choice, so it wouldn't be needed to unflag them every time.
Comment 3 Mario Frank 2017-01-17 11:01:14 UTC
(In reply to Stefano from comment #2)
> Yes, but it would be convenient to have a persistent per-album choice, so it
> wouldn't be needed to unflag them every time.

Okay, I see. You would like to have the opportunity to mark albums explicitely as don't-cares. And those should be ignored in face detection and recognition. Do I get this right?

If yes, this could be desirable for tags, too, since face detection and recognition can also be done on tags.

This would make the task far more complex. Marking tags as don't care is not this complex since we can use tag properties. But we currently do not have album properties - at least I did not find them.
Comment 4 caulier.gilles 2017-01-17 11:13:02 UTC
Mario,

Yes, Album properties do not exist yet, as i know. There are an old album categories but not in database. There is another report to implement album properties in DB as well, and to remove legacy album categories.

Gilles
Comment 5 Stefano 2017-01-17 11:16:21 UTC
If I understand correctly, the tag exclusion is a different matter though, because it's a "dont detect this automatically whithin the whole collection". May be useful too, though I don't see any practical case myself.

The album "blacklisting" would instead just avoid the need to unselect albums every time you run a face detection/scanning.
Comment 6 Barbara Scheffner 2017-01-17 19:22:19 UTC
(In reply to caulier.gilles from comment #4)
> Mario,
> 
> Yes, Album properties do not exist yet, as i know. There are an old album
> categories but not in database. There is another report to implement album
> properties in DB as well, and to remove legacy album categories.
> 
> Gilles

Probably I get something wrong here but just to make sure I would like to mention that Album Properties are descripted in the doc (Album View in digiKam Main Window). So there must be at least something somewhere, or not?
Comment 7 caulier.gilles 2017-01-17 21:44:01 UTC
Wolfgang,

By album properties, Mario want said extra properties to album from database, as keywords. Currently DB is able to store comment and date for album. Album categories are stored in text file, and must be store in DB as well.

In documentation, "Album Properties" is a dialog to edit Album features.

Gilles
Comment 8 caulier.gilles 2024-10-07 17:09:01 UTC
Maik,

I tested the face scan settings parameters restoration between sessions and the albums/tags works as expected.

But the "All Albums" and "Recursive" selection is not saved/restored at all in AlbumSelector widget. 

Best 

Gilles