nextcloud / nextcloud/recognize

Include a Process to Review or Approve Newly Categorized Faces to an Existing Named Person/Cluster

Open
#607 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
PHP
Stars
699
Forks
68
Avg merge
1d 4h
Merged PRs (30d)
5

Description

Describe the feature you'd like to request

Due to the complexity of AI Facial Recognition, and understanding that it will never be perfect, it would be beneficial to have a Review or Approval process when newly categorized faces are added to an existing Named Person/Cluster.

For example. I have a Person that I have edited and renamed as "Brian" instead of the default Cluster ID # 123. This means I know and care about the Person. I have 3,000 images in the Person Cluster named Brian. When faces are detected, categorized as Brian, and added to the Brian cluster (ID # 123), it's very cumbersome and nearly impossible to find this image in the Brian cluster to be sure it was properly categorized. This is especially true if adding older images to Nextcloud, as verifying newer images would be a bit easier but still quite cumbersome.

This type of feature could also be beneficial to https://github.com/nextcloud/recognize/issues/606

Describe the solution you'd like

I want the option to enable a review and/or approval process when new faces are categorized into an already-established Person/Cluster.

Even something as simple as some type of report showing which images were added to which clusters would be helpful so they can be reviewed for accuracy.

Describe alternatives you've considered

Click on the Person I expect an image to be categorized as and carefully review the images to be sure they were categorized properly. If they're not found in the expected cluster, perform the manual review of other existing clusters. Honestly, there is no good alternative for this that I can think of.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by tracing how newly recognized faces are assigned to named clusters and identify where a review workflow or additions report would fit. Done would mean users can review newly added faces for an established person or cluster before accepting them.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
computer-vision
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.