Quote:
Originally Posted by aleyx
Not really. Calibre's whole point is book management; it's therefore meant to be a main repo (database + filesystem), accessed through its various interfaces (GUI, CLI, content server).
Once you include Calibre into your process, your previous repo's books should be discarded once imported in Calibre (that's a manual operation, Calibre won't do it for you).
You can, of course, keep your current directory structure. Once your scripts populate them again, you can rerun the import and Calibre will update itself with the new files, adding or updating the books when needed. Then you can clear up your repo again.
|
Ok, understood.
I've been reading about the Calibre library structure, as well as the calibredb CLI.
Sounds like I may have to install Calibre Gui to get my inital library created. But once I have it created I should be able to add a section to my "postprocess.py" script that will run a "calibredb --recurse /my/processed/folder/path --library-path=/my/library/path".
That should add new books to my library.
Also, I may be able to generate an initial library through the CLI by running "calibredb restore_database --really-do-it".
This should "restore" (create in my case) a database from the metadata stored in my OPF files.
I'll give this a shot.