View Single Post
Old 12-10-2013, 03:53 AM   #4
aleyx
Addict
aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.aleyx can self-interpret dreams as they happen.
 
Posts: 250
Karma: 20386
Join Date: Sep 2010
Location: France
Device: Bookeen Diva, Kobo Clara BW
Quote:
Originally Posted by eschwartz View Post
The metadata is set in metadata.calibre, either when you send the book, or when the device is scanned for books not in the metadata.calibre, and once there, calibre doesn't assume a need to rescan for a changing size.

So calibre wouldn't know if the filesize changed, but only because it is populated from the book, at the time of indexing
Yet Calibre knows whether the book exists in the library (in Device view) or on the Device (in Library view). This implies a common ID field between the two DB. At least for those books Calibre sent, obviously.

So another question is: are there ways to add more comparisons between the two DB? For example, given a book sent by Calibre on the device, is there a way to know whether it is up-to-date, by adding a calculated column in the Library view?

Periodicals and the FFDL plugin (and maybe Quality Check) would greatly benefit from this kind of feature. Actually, if the necessary hooks already exist and nobody else's on it, I'd be interested in coding a plugin...
aleyx is offline   Reply With Quote