Thread: Touch I've bought my Kobo, now some setup questions please
View Single Post
Old 02-14-2012, 12:58 AM   #10
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,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by MacEachaidh View Post
Meantime, I've discovered the metadata editor in Sigil, and have confirmed that the metadata is what the KT is reading in the files to construct the Library menu, so it's easy enough to fix - though of course it means DRM has to go out the window. (I don't have any qualms about that; I don't distribute files, so I figure I'm still abiding by at least the principle of DRM.)
I've discovered a peculiarity in the KT's database, though. I tried amending the metadata in a few errant files and replacing the copies already on the KT with the updated ones, but even though the KT recognised the files had changed and went through the "updating content" process when I disconnected it, the subsequent menu still used the cached info of the previous copies of the files. I'm sure there's a database file I could have deleted that would force the KT to rebuild it with new data, but I wasn't sure which one that would be. (I suspect it would be the KoboReader.sqlite file in the kobo directory, but I hesitated at simply removing any of the OS files.)

The only way I found to force the menu to update was to remove the book files, then the USB connection, let the system rebuild the menu without those books, then reconnect it, copy the new files on and let it rebuild the menu again.

A bit of a shortcoming in the menuing system, I think. And yes, I'm using the latest firmware (.16).
I found this problem recently as well. The way I found it was when I replaced a book that was still being written. The new version had extra chapters. When I opened the book on the KT, and it opened correctly at the last place I had viewed. And I could read the new chapters. But, when I opened the contents for the book, it only had the chapters up to the previous update. Looking at the database on the KT (KoboReader.sqlite), I could look at the contents table and see an entry for each book, plus an entry for each chapter in the book.

What I believe is happening, is that when a new book is added to the KT, it reads the metadata and adds it the databases. It also adds an entry for each chapter. But, replacing the book does not trigger this. As an experiment, I inserted rows into the database to add the new chapters. This worked fine. The chapters appeared in the contents and I could navigate to them. I'm not sure how safe this is, but it worked. Maybe someone will write a plugin for Calibre to automate it. I might try it but I'm not sure when I will have time.
davidfor is offline   Reply With Quote