Quote:
Originally Posted by JimmXinu
I'd also change the first #multiseries in custom_columns_settings to 'r' mode to clear the pre-existing value on update. Otherwise, since it's a text column, you might end up with duplicates. (Depending on the custom column type. A 'tags' type text column could mask that.)
Code:
custom_columns_settings:
series00=>#multiseries,r
series01=>#multiseries,a
series02=>#multiseries,a
series03=>#multiseries,a
series04=>#multiseries,a
|
this worked like a charm, thank you so much!!! i didn't realize i'd need to specify series00,series01,etc. instead of just using a generic "series" for replace_metadata lines...but in retrospect, duh. i knew it was something simple i just wasn't seeing. it always is, lol. clearing include_in_series also made things stop being wonky--i'm not sure where i even got that line from, but thank you for pointing that out.
noted, about the =~ for exclude_metadata_pre! i did not realize that was the prefered seperator, but i've fixed it for all of the other exclude_metadata_pre lines i have now.
i removed the Recommended Reading Order line from this section anyway, since i think your renaming convention under replace_metadata is a great idea. if i run into another series with a recommended reading order series tag and it does somehow manage to interfere/cause issues in the multiseries column, i'm sure i'll be circling back here anyway for assistance.
as for your final comment about the custom_columns_settings--this multiseries column i made is actually set up as a comma seperated text column, like tags, shown in the tag browser. i haven't seen duplicates like you're describing to date, even after fixing my ini and updating everything; i assume that's because i have it set up as a tags-type column. but do you think i should just keep it as "series00=>#multiseries,r" anyway? since clearing out pre-existing values on update is likely a good move regardless?? if you think so, i'll just keep it as ,r. let me know.
you're the best!! as always, thanks for the help!