View Single Post
Old 11-01-2012, 12:08 AM   #22
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,906
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by StevenP94 View Post
I have a similar problem, and discovered that some ePub has an UUID inside that is different from the library one, so you upload a book and all seems ok, but at the next sync, calibre get the ePub uuid and use it to update metadata.calibre on the device: the book is no more recognized from calibre. It is on the device but having another id is not recognized.
That is correct and is happening it at least one case reported to me. But, when the UUID match fails, calibre also tries other things. These include using the author and title. This test is failing here.

Also, the circumstances under which the epub is read for metadata is limited. It only happens if the path for the file stored in the devices database does not match one in the metadata.calibre. Deleting the file or adding a book outside of calibre are the main reasons.
davidfor is offline   Reply With Quote