Quote:
Originally Posted by Starson17
Calibre currently remembers searches, and the save search feature will be a great improvement. As a matter of interest, that work's being done by Chaley. IIRC, he keeps his author in reverse name order and he wrote a tweak to allow others to do that.
|
Yes, I am, and yes, I do.
Of course, you are right to point out that calibre is not designed to manage automatic workflow chaining along a multi-step process. I also think that such functionality will not arrive soon, given the amount of other stuff to do that seems to be higher on the priority list.
What works for me for workflow is to use a set of tags with a common prefix to organize what I am doing. For example, I use the tags T:inprogress, T:done, T:waiting, and T:a few others. The advantage for me is that I can query about the state of books by asking for 'tag:T:', query about specific states by asking for the exact tag such as 'tag:=T:done', or find books that have been forgotten by asking for 'not tag:T:'.
I agree with starson17: tags help organize much more than is (usually) apparent when starting using calibre. That being said, as time goes on, I am finding that I also want tags with testable values. For example, I would like to have READ:xx/yy/zz, and then be able to ask for books READ before/after some date. I am considering playing with adding columns to the GUI that show the value of some tag, a poor-man's custom column implementation that would facilitate sorting and selecting on tag values. I can see reasons not to do this, so I am still thinking about it. In addition, Kovid might have alternatives in mind that would obviate the benefits. We will see...