Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Merging performers and scenes #1351

Open
DDC12 opened this issue Apr 28, 2021 · 4 comments
Open

[Feature] Merging performers and scenes #1351

DDC12 opened this issue Apr 28, 2021 · 4 comments
Labels
feature Pull requests that add a new feature
Milestone

Comments

@DDC12
Copy link

DDC12 commented Apr 28, 2021

Is your feature request related to a problem? Please describe.
It happens every so often that I apparently have duplicate performers in my list under different aliases. This usually happens because when adding one of them, they were not on Freeones yet and could not be scraped, or because over time their "primary" name has changed, which Stash then sees as a new user because the hash is based on the name.

When I realize this, I find the one that is "wrong", go through all the scenes they were in, remove them as a performer, and add the "right" performer instead and then delete the wrong performer, ending up with only the correct one with all the scenes that were linked to the wrong one merged into the new one. As a programmer I feel stupid doing this.

The same kind of goes for scenes, but with different qualities instead. If I have the same scene twice, but once in 720P, and once in 1080P, they are seen as 2 separate, unrelated scenes.

Describe the solution you'd like
A way to merge performers. Just reassigning the scenes to the new performer and deleting the old one would be fine. Getting a comparison with "old vs new" for the performer values, just like when scraping, would be nice, but not as required.

As for the scenes: Something similar as with the performer merging would be fine, allow me to compare the 2, chose which fields to keep from which version, and which file to keep.

You could also borrow some experience from media servers and separate scenes and files, this way a scene can have multiple files, and you can have different qualities for 1 scene at the time allowing you to choose which one to play. But this would probably require a huge change in the infrastructure for very little benefit.

@echo6ix
Copy link
Contributor

echo6ix commented Jul 14, 2021

+1 to adding a feature that merges performers.

UI/UX implementation could be exactly like the new tag merging feature. Have the merge button located in the performer's operation tab.

@kermieisinthehouse kermieisinthehouse added the feature Pull requests that add a new feature label Nov 3, 2021
@kermieisinthehouse kermieisinthehouse added this to the "Soon" milestone Jan 29, 2022
@ALonelyJuicebox
Copy link

ALonelyJuicebox commented Mar 12, 2022

+1 to allowing metadata (tags and performers) to be selectively copied from one scene to another. Super valuable for manual tagging. This would make going from scene to scene to add all relevant metadata significantly easier.

In fact, the issue I opened (#1542) is probably a dupe of this. Would definitely consider a bounty for this.

@Skier23
Copy link

Skier23 commented Sep 2, 2022

+1 to merging performers.

@myalow
Copy link
Contributor

myalow commented Jan 3, 2024

+1 to merging performers. scraping JAV is very annoying because JavLibrary (and other sources) tend to return in surname firstname order, leads to a lot of duplicates.

(I'm sure there is a more sophisticated way to resolve this specific issue of mine but this would also solve it and presumably a lot of other issues as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Pull requests that add a new feature
Projects
Status: No status
Development

No branches or pull requests

7 participants