Quote:
Originally Posted by jackie_w
@davidfor,
Ooh! This sounds promising. Paraphrasing, I think chaley just said it would be easy for a man of your exceptional talents. Maybe you were looking for a little project to while away those long, dark Aussie winter nights  |
I'm not sure whether
or
is the proper response
Quote:
|
Seriously, though, having a 'resend-if-newer' option (for books and/or metadata) available on Kobos would be brilliant. I love it on CC.
|
The biggest issue I have with this is if the changes affect the structure of the file. As the firmware processes the book the first time to extract the ToC and metadata, and I have the driver updating the device database to prevent this, automatically sending changed books might be a bad idea. At the moment, I have to remember to delete books I change to much before resending.
If I do this, there are two timestamps on the device. One is the file timestamp, which will be when the book was put on the device. The other is the "Last Synced" timestamp in the database. This is when the book was seen and added to the database. Which should be used? I tend towards the last synced, but if it is used, I need to update it. This is used by the "Recent" sort in the library. Updating it means the book will be pushed to the top of the list (if it is unread).
For the resend, I am planning to add an option to let the device process the books as new. This is what would happen if you manually sideload the books in the recent firmware. Now that I can change the configuration easily, adding an option to do this will be a lot simpler.