Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 03-28-2022, 07:28 PM   #2438
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 NiLuJe View Post
That smells like PEBCAK (and/or a bug somewhere that caused a reading state to be flagged as changed), as the plugin only cares about the reading state in the *nickel* DB, and KOReader doesn't touch that, ever (never ever ever!).
Definitely a PEBCAK issue. There is no way there would be any bugs in my code. How dare you suggest such a thing!

@Uncle Robin: As the others have said, the Kobo Utilities plugin reads the database that is maintained by nickel. If the reading status has not changed in that, then the plugin won't find any changes. I can only assume that you had done some updates that you forgot about.

If you aren't using nickel, there is a KOReader Sync plugin that, I think, fetches the reading status from wherever KOReader stores it. I haven't really looked at it, so I don't know what it's dependencies are.

Quote:
I should know, I wrote a script to do the KOReader -> Nickel reading status update just so that I could keep using that feature of the Calibre plugin .

(Said script requires my Python distro; after which you can just 'right click > run python script' it in KOReader. I fav'ed it for ease of access on my devices).
I hadn't seen that before. Good to know about it. Have you considered running it from the connected PC? It would stilll need a Python install, but, some people might be more comfortable with that.

Quote:
Originally Posted by NiLuJe View Post
The lack on "on device" checkmark is more troubling though, but might be explained because of reasons (possibly related to a stale on-device calibre metadata cache), depending on exactly what you did.

(See the rest of that thread for context, although most of my answers were geared towards what happens if you *add* new books behind nickel's back; not the state of already-imported-by-nickel books).
A missing "metadata.calibre" is mainly an issue when matching books. And that is largely with books that have multiple authors. Calibre uses the title and author and that might not be handled correctly for multiple authors. And for books not sideloaded through calibre, there can be title issues. You can manually match these books and that is stored in metadata.calibre. It also helps with performance as the matching has already been done.
davidfor is offline