[pdurrant]

Originally Posted by pdurrant

Custom Columns:
I have the following custom columns:

1. #parts - Comma separate text, giving the individual names for omnibus editions
2. #sub - like series, but indicates a sub-series within a series.
3. #read - Yes if I've read it, No if I intend to read it.
4. #dateread - the date I finished reading it
5. #price - floating point, what I paid for it
6. #orig - the original format downloaded (like tags)
7. #shops - where I got the book (like tags)

I forgot to say that I actually use the tri-state of a calibre Boolean column. That is, it can be yes, no or not set.

I use yes for "I have finished reading this"
I use no for "I want to read this in the future"
I use not set for "I don't want to read this, but I want to keep it around for reference"

That way, I can pick a random book from the read==no section, and not get books I don't want to read as books (e.g. cookbooks).

So it would be really nice if justRead handled the "not set" state of my #read column too. But that may require a bit more reworking than it deserves. In which case, I'l like the sync back to calibre for the read state to only ever change the state to read==yes, and never set a state to read==no (As it doesn't really make sense for that to happen in a reading app.) That way, my calibre tri-state won't get overwritten with lots of read==no states.