You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are many faces found in "Unassigned faces" that I do not want to move to a person. It would be nice if there was a way to remove them from the "Unassigned faces" list so that I could more clearly see the ones I do want to move to a person. I have at least hundreds of photos with unassigned faces.
Describe the solution you'd like
In the "Unassigned faces" page, select a photo or photos and click a new icon in the "# selected" popup menu to remove them the list. A confirmation dialog would be a good idea.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
So I checked on this and it seems to be an upstream limitation. DELETE calls on unassigned faces return a 403. So this will need fixing in recognize first.
Is your feature request related to a problem? Please describe.
There are many faces found in "Unassigned faces" that I do not want to move to a person. It would be nice if there was a way to remove them from the "Unassigned faces" list so that I could more clearly see the ones I do want to move to a person. I have at least hundreds of photos with unassigned faces.
Describe the solution you'd like
In the "Unassigned faces" page, select a photo or photos and click a new icon in the "# selected" popup menu to remove them the list. A confirmation dialog would be a good idea.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: