Custom Column side-effects
I really like custom columns, but I'm not too keen on their side-effects. The side effect i'm referring to is that when the custom column data changes, then the book metadata.opf gets updated and the book is considered "dirty" (changed) for the sake of synchronisation.
For example, let's take one a lot of people have, author_book_count. When the book count is updated, all the books in the library will be updated. When I next synchronize with a device, all the books will need to be resent (as then have changed since the last sync).
Aside being a problem with syncs, is that some of those columns can contain private information that needs to be scrubbed if the file is ever to be shared (web content epubs for example).
I was wondering if there was any way (hidden tweak?) I could mark some columns as being "database only", i.e. that medatadata field wont be updated in the book files (and metadata.opf).
(not sure i'm being clear so this is another way to ask exactly the same thing) -> Is there a column filter setting that can be used to identify columns that are not to be written in the book's metadata?
Last edited by botmtl; 04-02-2017 at 09:31 PM.
|