Quote:
Originally Posted by cybmole
OK - well I decided to consistently re-title the PDF guide books , in calibre, so that they'd all appear in one place on the shelf.
I thought that all I'd need need to do was connect to content server & CC would then automatically pick up the updated titles - but that did not seem to work. even when I told it to download books it already had, I was still seeing some old titles.
so I went for the quick fix of nuking them all & re-downloading - that fixed it!
but what's my wrong assumption here - when /how does CC update its copy of something like a book title, if it has the book but the title is then altered within calibre on PC.
From somewhere, I picked up the ( maybe wrong ) idea that whenever CC connects to content server it compares it's records to those in calibre & updates as needed ?
|
Yes, you did get the wrong idea. Metadata for books on the device is updated automatically when you connect as a wireless device, not when you connect to the content server.
Quote:
|
To be specific, I edited the displayed title of some PDF books within calibre via the main window, by double tapping the title field & then editing its content.. then I got CC running on the Kindle & had it connect, then disconnect. Was I just too impatient or am I missing something ? there's less that 20 books on the tablet, so a metadata check should not take a long time, surely ?
|
That process should work if you connect as a wireless device. For 20 books it should take very little time, a small number of seconds.
When you connect as a wireless device you see several progress dialogs related to updating metadata. First CC asks calibre what metadata it needs, if any, then sends it to calibre. Next CC waits for calibre to do its analysis, then receives metadata from calibre. Only when after those progress dialogs are gone has the process finished.
Perhaps confusing things, there are several reasons why connecting to the content server does not update all metadata on the device. The major one is capability: the content server offers no way to ask if the metadata on the client is the same as the metadata on the server. It also has no memory of what interactions it has previously had with a client. Of course, I could add all that to the content server, but then we get to the second reason: purpose. The content server connection is meant to be a convenient way to do get books onto the device. Connect, transfer, disconnect. It would be extremely annoying if it spent many seconds when it connected checking metadata.