"When CC connects as a wireless device, it asks calibre for any updated metadata for books already on the device. In this context, I am not sure why - for the purpose of sync'ing back data of individual books from the device to Calibre - it matters how large the Calibre database is (but I am dense). CC has its own management system of grouping & sorting the books (based on the Calibre/books metadata). My usage model is, to send books to be read over the wireless connection to CC. However, I do not have the impression that CC (Calibre Companion) loads all Calibre metadata. Once some hardcore calibre user does that sending the info back to calibre shouldn't be a Due to my limited knowledge on how the Calibre plugin operates, I am hesitant to muddle the discussion. The most difficult part is figuring out a way to store the relevant data of fields that are, in most cases, mutable. I think it is not a good idea to store the whole userdata, just the bits we might want. AFAICT the userdata field can grow a lot, it would be a good idea to test the implementation on a big library (1000-10000+ books) with a big userdata for each entry.we load the whole JSON metadata file in memory, so we strip the things we don't use, which are almost all of them (except the things used to navigate/search metadata).If somebody wants to contribute keep in mind: I think it is doable and certainly can assist (a bit) on the smart device app interface, but have no interest in doing this. Most of my documents are managed outside calibre. I don't keep any specific metadata beyond series & tags or use calibre as a book manager. I just use calibre to strip DRM of the books I buy online and to remove some corporative BS. The main limitation I reached with the current implementation is the lack of usage/understanding of calibre.
0 kommentar(er)
