You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the user changes an actress name or merges actress entries, automatically launch a background command to scan all movies and update names appropriately.
The actress database will always be considered the authority, so the names in movies will reflect whatever is listed there. The actor alias data will be changed to reflect the actress database as well. In the case of an actress entry merger, duplicate entries will be located and eliminated. It may be simplest if the command does not distinguish any particular actress entry and simply updates all movie entries, making note of which ones actually change so the .nfo files can be saved at the end of the command.
When should this occur? After the user finishes the edit? What if it's in multiple parts, like swapping main and alternate names? Maybe after closing the current detail view would be safer then? Maybe don't update if the change set the name to empty, as that's not considered valid. In the case of a name change -easy enough. Launch the update when you click Merge.
Alternatively, this could be manually triggered. Not sure I like that, as the least surprising thing would be for the actress names in movie listings to automatically sync up to what's listed in the detail pages, I think.
I think I like the idea of launching this process after you either explicitly trigger it with Merge, or when you navigate away from the current detail page. Will have to keep track of an edit flag specifically for names.
The text was updated successfully, but these errors were encountered:
If the user changes an actress name or merges actress entries, automatically launch a background command to scan all movies and update names appropriately.
The actress database will always be considered the authority, so the names in movies will reflect whatever is listed there. The actor alias data will be changed to reflect the actress database as well. In the case of an actress entry merger, duplicate entries will be located and eliminated. It may be simplest if the command does not distinguish any particular actress entry and simply updates all movie entries, making note of which ones actually change so the .nfo files can be saved at the end of the command.
When should this occur? After the user finishes the edit? What if it's in multiple parts, like swapping main and alternate names? Maybe after closing the current detail view would be safer then? Maybe don't update if the change set the name to empty, as that's not considered valid. In the case of a name change -easy enough. Launch the update when you click Merge.
Alternatively, this could be manually triggered. Not sure I like that, as the least surprising thing would be for the actress names in movie listings to automatically sync up to what's listed in the detail pages, I think.
I think I like the idea of launching this process after you either explicitly trigger it with Merge, or when you navigate away from the current detail page. Will have to keep track of an edit flag specifically for names.
The text was updated successfully, but these errors were encountered: