Quote:
Originally Posted by sealbeater
I think I already answered this.
All of my books have this format:
Anja Jonuleit/Anja Jonuleit - Novemberasche - Kriminalroman (2010)[9783423405638].epub
If it's a series:
Gav Thorpe - [Time of Legends - The Sundering #1] - Malekith (2008) [9788448038373].epub
so I can just go, as stated "cd library ; find . -name "Time of Legends*epub" | parallel cp -rv {} /mnt/bookreader.
...
Of course, small libraries will load calibre quickly but I find command line operations to be faster in general.
|
+1 on command line being faster, but calibre and the command line do work well together. Your approach has advantages and disadvantages (e.g. your substring/filename approach can fail when a series name is short; you can easily get false matches on a series name like "Foundation"—you can come up with specific naming schemes that allow unambiguous searches, but at some point you're basically reinventing your own YAML or JSON).
I'd typically use something like:
Code:
cd dest; calibredb export --single-dir $(calibre-id series:Foundation)
where calibre-id is a utility script I have that just does:
Code:
calibredb list -s "$*" -f id|grep "[0-9]" | tr '\n' ,|sed -e 's/,$//'
Well, in reality I have another calibre-export script so I can just run
Code:
calibre-export "series:Foundation"
or whatever search I want, but it's largely equivalent to the above behind the scenes (plus my favorite tweaks on preferred formats and the like).
For a while I played around with a shadow directory of symlinks so I could arrange things how I wanted, but I found that once I made a couple of simple scripts to integrate calibre-db with the Unix command-line infrastructure I really didn't need that anymore.
Different strokes for different folks, obviously you've found something that works well for you.