[Feature] duplicate detection blacklist

[spawnpeekboi]

I have searched the existing feature requests to make sure this is not a duplicate request.

• Yes

The feature

duplicated detect blacklist on criteria, like in a certain album, or being selected to kept before.
sometimes I just want every photo in a certain album. like moments in wedding photo. I do not want them to be stacked. However, each time I run duplicate detect, they just being select out again and as me to keep or not.
So if there is a option that i could blacklist a certain selection of image being pick to be deduplicated that will be very nice
thankyou

Platform

• Server
• Web
• Mobile

[maicss]

#17566

[orrd]

This same feature has been requested several times, but I think this one is the oldest request for it? (But someone should probably fix the spelling/wording of the title of it.)

There does need to be some mechanism to remember when the user wants duplicates to be ignored so they don't keep on re-appearing in the duplicates utility. The way I implemented this on a project I worked on was to have a "nonduplicates" table that records sets of photos that have already been reviewed. So for Immich, each time the user reviews a set of duplicates and chooses to keep more than one, it would add a row to the nonduplicates table. Then that set of nonduplicates would be ignored on future duplicate searches.

If a new photo is added that matches past photos that were nonduplicates, it's ok for it to show the group of photos again with the new photo added. Using the "all" button on the duplicate detection item on the Job Status page should also delete all rows of the nonduplicates table, since that is a way to make it reconsider all duplicates again.

I don't have experience with this code base, so I'm not sure if it makes sense for me to try to tackle this or not. I also don't know if anyone is already working on a solution for this.

[orrd]

This appears to have been fixed in 1.133 or 1.133.1. I don't see any mention of anything like this in the release notes, but it appears to work now!