Observations on Batch Update Performers

I’m relatively new to Stash and have been blown away (pun not intended, haha) by the exquisite quality and thoughtfulness of the software. I wish more apps and services were made with the high standards and attention to detail that are so evident in Stash.

I have been playing around with the performers in my database; choosing the image I like, adding missing Stash IDs, custom tags etc., and have a few observations/queries:

  1. I’ve been manually adding missing Stash IDs (by missing I’m referring to those performers that don’t have both StashDB and PornDB Stash IDs.) This is a bit tedious, to put it mildly, and so I was hoping to automate it by batch updating performers. This works fine for performers with unique names but is quite hit or miss for those with single or non-unique names. Is there an option to have Batch Update Performers only work for those performers that don’t have a name conflict? If not then this might be very useful to others too. I can discard single name performers manually with filters and/or custom tags for this exercise.
  2. When manually/batch update scraping a performer, aliases get replaced if the new scraper has one. However, if the previous scraper has aliases and the newer one doesn’t then these don’t get replaced. I’d like to replace information for all performers created by PornDB with StashDB, as the latter seems to be more accurate, and am able to do so but for aliases, where the PornDB ones remain for performers for whom the field is blank on StashDB.