|
The only thing it has over the standard cloud connection is that is has values for composite columns (computed columns). But to get these values the user must manually export their library (making a copy of all books),
Manually export? Well, if setting up Calibre to connect to a folder device on startup, and configuring the Reading List plugin to automatically send all their books to there is 'manual', okay, it's manual?
sync that exported copy with the device, then import that copy into CC.
I was also suggesting using it over the cloud. I.e., CC checks for a metadata.db *or* metadata.calibre file upon cloud connection. (Either using the real cloud connection, or a fake local cloud.)
On the other hand, several people have asked that we support importing books sent over a cabled connection, which is a use case similar to what you are describing. I have had this on my "look at" list for some time. Perhaps the right time is approaching.
You mean, reading new or changed metadata.calibre in the existing CC Default folder, and picking up new books from it? (And *possible* picking up metadata changes in other books, but maybe not?)
That would be great. I'd actually much rather have CC do that than deal with any 'cloud connection' stuff.
People who use USB connections and point CC at the same directory would have that working for them.
And it also allows people to set up a cloud 'Folder device' in Calibre and sync *that* to CC's Default folder. (Which could even, awesomely, be synced back, unlike my fear of syncing the actual Calibre library back. Calibre notices, upon device connection, when a device has added books that aren't in metadata.calibre, or when books are deleted.)
Incidentally, any thoughts on compressing metadata.calibre? It's really really large per book, and very compressible. Completely outside of any of this, reading and writing that compressed would almost certainly be faster, even if it was just over USB. Or should I take that idea to some other forum?
|