hydrusnetwork / hydrusnetwork/hydrus
Additional Option for the API Settings to not Allow Overwriting Previosly Deleted Tags
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
A API Setting like "api parsed tags won´t overwrite previosly deleted tags" would be a great addition for a specific repo or api option.
When using for example a tool that generates tags automatically like hydrus-dd it would be interest to be able "clean" up those generated tags by deleting false positives. The issue is that even if you have created a separate repo just for generated tags than any attempt by cleaning the results will be wiped the next time the tool processes the files and send the tags to hydrus.
In order to create a progressive workflow where generated tags can be deleted AND stay deleted a option to enforce it would be necessary.
edit: because it´s maybe difficult to read here is a tl:dr "to have a parameter in the api to set that "do not add deleted tags" option from the tag import options"
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
No file or test is named. Start by tracing the API entry point for tag imports and the existing tag-import option that prevents re-adding deleted tags; define how the setting should apply per repository or API option, then verify that deleted generated tags remain absent on later imports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100