View Single Post
Old 02-16-2019, 11:38 AM   #381
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
As the examples show, it matches on the RE and then replaces whatever Tag is matched with the "new tag" value. Or, purges it if that is what you set.

"/.*Buffy.*Vampire.*Slay.*/","Buffy The Vampire Slayer",False

So, "/.*Game[ ]of[ ]Thrones.*/" would not match Buffy, and Buffy would not match Game of Thrones.

Your .csv files show way too many needless rules because they do not use REs at all.

You need to be developing your .csv files using a TEST Library that is a copy of your "real" Library. You just need the metadata.db, not all of the books underneath it. That way, you could refresh your TEST Library's metadata.db easily and quickly to test again. Or, create some custom columns to hold your test data column, and refresh your active custom columns from that using Bulk Edit S&R. That is what I did to develop the Tag Scrubbing tool.

Remember to compress your "real" metadata.db using Check Library after you run your rules "for real".

DaltonST

Last edited by DaltonST; 02-16-2019 at 11:45 AM.
DaltonST is offline   Reply With Quote