immich-app/immich

[Feature] Per user "minimum face count"

Geschlossen

#21.279 geöffnet am 26.08.2025

Auf GitHub ansehenContributor Guide
 (4 Kommentare) (2 Reaktionen) (0 zugewiesene Personen)TypeScript (5.601 Forks)batch import
good first issue

Repository-Metriken

Stars
 (100.600 Sterne)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

Each individual user should be able to specify a "minimum face count" that filters out people on the /people endpoint & associated page. This should be added as a user preference (probably at people.minimumFaces), and can be set to any number, with 0 implying that no people are filtered out of view.

Background

There is a server config option (machineLearning.facialRecognition.minFaces), that is used during the clustering process to determine at what threshold a Person is created. This same configuration setting is being used as a global cutoff for the /people endpoint, and has led to some confusion.

Contributor Guide

Research-Richtung
The issue requests a per user 'minimum face count' preference. First, examine how existing user preferences are stored and retrieved (likely in a user preferences service or similar). Then, locate the `/people` endpoint and its associated controller/service to understand how the global config `machineLearning.facialRecognition.minFaces` is currently applied. Implement a new preference field `people.minimumFaces` in the user preferences schema, defaulting to 0. Modify the endpoint to filter people based on the user's preference instead of the global config. Finally, add a UI component in the user settings page to allow users to set this value. Ensure backward compatibility for users without the preference set.
Tech Stack
typescript
Domain
full stack
Issue Type
Funktion
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
Halber Tag
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
Frisch
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
Klar
Voraussetzungen
Immich architecture overviewTypeScript/Node.js basicsREST API understanding
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
75