Duplicate processing tags: copy/move from one service to another

Open
#796 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
desktop

Research direction

Start by reading issue #795 and tracing the existing processing-tag actions for copying or moving tags between services. Confirm how PTR tags and an inferior duplicate's tag service are represented, then define completion as applying the selected source tags to the destination service without staging unwanted mappings.

Written by the indexing model from the issue text.

Description

feature-request system:duplicates

While this is definitely distinct behavior from #795, it would be very useful to use in conjunction with it.

For example, I could take the PTR's tags and apply them to the my tags service on the inferior dupe, so that way I don't stage tags for an inferior file and thus add mappings people are unlikely to find useful.

Dominant language
Python
Stars
3.2k
Forks
207
No merged PRs in 30d

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.

More from hydrusnetwork/hydrus

All issues in hydrusnetwork/hydrus

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.