Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 10-08-2017, 08:45 PM   #1739
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 compurandom View Post
Right now, metadata can't be updated until the second time the device connects after a new book is added.
That is correct.
Quote:
If you automatically update subtitle and comment in the driver, how would you handle this? Scan the entire library for books not updated? Keep a list of new books that need an update? Something else?

Right now, I have a tag on books that have already had their metadata updated and a saved search that both finds books that need to be updated, and books deleted that use to have metadata.
And this is one of the reasons I've never implemented the metadata update in the driver; it could take to long.

For the series info, the driver is already looking at each book on the device, comparing the series info to the calibre library and updating the device if there is a difference. If I change the driver to update the rest of the metadata, it will be done in the same way: compare the values and only update if there is a difference. There shouldn't be many changes with each connection, but there is a lot of work to do to find them.

There are things that could be done to speed things up. Like, only look at books that have changed since they were put on the device. Or the last time the device was connected (I can't remember if there is a way to determine this). Doing this should improve things, but there are issues such as what happens if you log out of the device and the books get reloaded. Then, the metadata for all the books need to be updated.

But, the biggest reason for not doing this in the driver is that I have already implemented it in the Kobo Utilities plugin. As there is already a way to update the metadata on the device, I haven't felt a great need to add the same function to the driver. And I haven't had felt a great need to have the update run automatically, as I personally don't want it run all the time. I usually make sure the metadata is correct before sending the book to the device. If I feel the need to update it, I sort by modified in the library, select books back to whatever date I think is appropriate and do the update for those books.

I will look at automating the update in the utilities plugin. Maybe I'll add a control for how often to run it. For my purposes, running it once a week is probably enough. Then I'll revisit the driver and see how it fits there. But, if I do it there, I will not put all the function the plugin has. It will be all-or-nothing and no options for non-standard metadata.
davidfor is offline   Reply With Quote