nextcloud / nextcloud/recognize
Support for `--folder` and `--user` parameters in `occ recognize:classify`
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 699
- Forks
- 68
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Describe the feature you'd like to request
I use nextcloud together with memories to browse my pictures. It integrates Recognize as part of its features to tag the content of the pictures themselves.
I have a collection of hundreds of thousands of pictures on network drives, which are accessed via nextcloud's external storage. Moreover, I have several test users that have access to those files, but don't use them actively, so the whole picture library is actually duplicated several times in nextcloud database.
So, when running a full indexing of my library, something I'm aware it can take several days, I'd like to skip those users and folders that I know don't contain any pictures or won't be used at all.
Describe the solution you'd like
I would love if there was some parameter in the occ recognize:classify to specify for which user I'd like to run the classificator, or limit it to a specific folder subtree. For instance:
occ recognize:classify --user myuser --folder "Media/Pictures"
This would limit the classification to my user, and circumscribed to my picture folder only (I don't need recognize to scan all my documents or work files). And would save me several days of processing time.
Describe alternatives you've considered
The only alternative would be to set up a separate nextcloud installation with only that user and an external storage pointing to the specific path of the picture library. But it's not realistic.
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 at the occ recognize:classify command entry point and trace how users and folders are currently selected for classification. Define how --user and --folder should combine, then verify that the example command limits processing to the requested user and folder subtree without affecting unrestricted classification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100