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] Selecting Aliases of performers with multiple names. #1724

Closed
monketybot opened this issue Sep 12, 2021 · 2 comments · Fixed by #3113
Closed

[Feature] Selecting Aliases of performers with multiple names. #1724

monketybot opened this issue Sep 12, 2021 · 2 comments · Fixed by #3113

Comments

@monketybot
Copy link

Is your feature request related to a problem? Please describe.
It is annoying when a performer goes by multiple names, which can cause multiple entries in the Database.

Describe the solution you'd like
I see there is already an Aliases section. If it could just have this section be used in the same way that the usual name is. Perhaps even with a checkbox which means you choose which aliases can be used in this way (may prevent aliases getting too many false hits)

Describe alternatives you've considered
You could also have a merge button where if you have found a performer with more than one entry you can merge them both together.

Or, Much like Studios can have Parent Studios, there could be Parent Performers (Sounds a bit weird but hopefully makes sense). where you can have multiple sub entries connect to the Main Performer. (This sounds like the easiest to do but could cause alot of duplicate data)

@echo6ix
Copy link
Contributor

echo6ix commented Sep 13, 2021

#422 (comment)

@monketybot
Copy link
Author

#422 (comment)

This looks good. It is a lot more detailed than my idea.

What do you imagine for the search names. Would it just use the main name as the search name or would you have multiple search names? (By search names, I mean the name you type into the performer text box to select the Performer)

Would you have to make a name for each studio or would I use the main name for all the unused studios

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants