Quote:
Originally Posted by greene48
Well, by "manually" I mean opening up the Calibre GUI to update the .db.
|
That's a relief ^^
Quote:
Originally Posted by greene48
I can't do this since ChromeOS is basically just the chrome browser. So I can't install calibre on it. But I could install linux on my Chrombook to install Calibre if I need to run the Calibre GUI.
But this wouldn't be my ideal solution.
Do you need to open up the Calibre GUI everytime you want to add a new book to your .db?
|
No, you can use
calibredb, which is a CLI tool.
Quote:
Originally Posted by greene48
I oversimplified the way I'm processing my books. The "script" I'm using is actually a python program I have installed on my server called LazyLibrarian: https://github.com/herman-rogers/LazyLibrarian-1
This can be used to downloads books from nzb sites, (by passing them to Sabnzbd+), store them in the correct location, and then process them with cover pictures and metadata.
At the moment, I am only using the "postprocessing.py" script that comes with the program. I used it to process my current book collection, and have it setup to process any new book I move into my processing folder.
That script is located here: https://github.com/herman-rogers/Laz...postprocess.py
If this could be adapted to update the metadata.db file as well it would be ideal. Can you update the metadata.db file from the CLI? |
So after your postprocessing, what you have is a hierarchy of directories, anf the leaf directories have an ebook, a cover.jpg and an .opf. Is that right? If so, I don't think there's ll be any difficulty in using calibredb to import your books into the Calibre library, and thus the content server.
Be careful not to use the same hierarchy of folders for your Calibre library and your postprocessed repo, tho. In fact, the whole Calibre library should never be directly accessed by anything but Calibre (except for backups, of course. Backups are Good(tm)).