Quote:
Originally Posted by kjdavies
The change I really want is to be able to specify my own tag and hierarchy delimiters (comma and period both happen in real strings!) but that's a much scarier change.
|
Yes it is and that's why it isn't going to happen, at least by me.
Quote:
|
(Another one I'd like, also intended for use with tags and hierarchies, is the option in the bulk regex editor to say "if the tag doesn't match the RE, remove it"... AKA "if you find a tag like this, change it in this way, else remove it". It would be very useful when the tags contain metadata I want in another field, but it might be entirely a 'me' problem.)
|
Building this in is more than I want to do. It would be difficult to get "right" and cover all the corner cases.
You can do it yourself today with templates, either in bulk edit or action chains single field edit. In bulk edit you would use "template" as the source. In action chains you would use a template to compute the resulting value.
The template would fetch all the tags for a book, filter and modifiy them as desired using regexp or whatever, then return that result. Bulk edit would have the search regexp '^(.*)$', replace regexp '\1', and the destination field of tags. Action chains would be operating on tags.
A third way is to use action chains "python code" and write what you want directly against calibre's db. In this case you would fetch the tags from the db, filter and modify them as needed, then store them back into the db. This process processes tag-by-tag not book-by-book, which may or may not be what you want to do.