nextcloud / nextcloud/recognize
Recognize results are lost when transferring files to other user
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 699
- Forks
- 68
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Which version of recognize are you using?
6.1.1
Enabled Modes
Object recognition, Face recognition
TensorFlow mode
Normal mode
Downstream App
Files App
Which Nextcloud version do you have installed?
28.0.4
Which Operating system do you have installed?
Debian 12
Which database are you running Nextcloud on?
MariaDB 10.11.6
Which Docker container are you using to run Nextcloud? (if applicable)
No response
How much RAM does your server have?
16GB
What processor Architecture does your CPU have?
x86_64
Describe the Bug
When files are transferred from one user to another user via transfer ownership, only the classification results are transferred, face detections are lost. Also, the transferred files are not added to the face detection queue for detecting the faces again.
Expected Behavior
Either keep the face recognition and run the clustering for the new user or re-run both face recognition and clustering after moving the files.
To Reproduce
- Upload images to one user
- let recognize do its thing
- transfer ownership of these images to another user
- see that face detections are lost and files are not added to face detection queue
Debug log
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how transfer ownership moves files between users and how face detections and the face-detection queue are handled afterward. Reproduce the transfer with recognized images, then verify that face detections are preserved or that both face recognition and clustering are queued for the new owner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100