echo6ix

+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.

This is an excellent idea. I would find it useful if it could also implement regex to match parts of the original filename and add them to the output of...

> Just noting that this seems related to your prior request #2984 Yes it does. They are very similar, but #2984 seems like an inferior implementation. I am going to...

Two things. I. **Sorting**. It's easier to parse aliases when they're case insensitive alphanumerically sorted. After each save of the performer profile automatically sort the list of aliases. This would...

> There should be a way to do this extremely efficiently using semantic relationships to constrain and order the potential results. Like this? #422

In your concept showing a match-as-you-type query, I presume an alias is being queried, and your concept has the matches displaying the primary performer name with the matched alias in...

Would implementing something like this require require a new table, such as `performers_aliases`, in the database? ``` performers_aliases table id integer alias_name varchar(255) performer_id integer studio_id integer ``` To reference...

@hyde231 > Two (or more) performers can have the same alias with a given studio Definitely. Not sure there's any way around that though. > One performer can have two...

Performers are typically associated with multiple sites though, displaying their primary name with one seems kind of arbitrary imo. Most people are probably only going to add the alias-studio connection...

 ### Toggle Autotag toggle button to denote if the entry should be ignored by autotagging. - Toggle enabled: Entry is available for autotagging - Toggle disabled: Ignore entry when...