Calibre Kobo Utilities - Wishlist!!

[JSWolf]

Would these breezy feature not be better off in the Reading List plugin?

[davidfor]

Originally Posted by JSWolf

Would these breezy feature not be better off in the Reading List plugin?

Not at all.

[davidfor]

Originally Posted by Terisa de morgan

Thoughts from a programmer trying to add "automatic update metadata on connection depending on the device" to the plugin

What exactly have you been up to?????

[Terisa de morgan]

Originally Posted by davidfor

What exactly have you been up to?????

I'm now exactly at what I'm telling you: in the same way that you get the reading position when you connect the device, you update metadata (plugboard included) for some marked books.

[davidfor]

Originally Posted by Terisa de morgan

I'm now exactly at what I'm telling you: in the same way that you get the reading position when you connect the device, you update metadata (plugboard included) for some marked books.

That's another thing I've been thinking about for ages. Or putting it in the driver. I've tended towards the plugin for flexibility. It shouldn't be too hard. Unless the issue is collecting the metadata before passing it to the job?

[Terisa de morgan]

Originally Posted by davidfor

That's another thing I've been thinking about for ages. Or putting it in the driver. I've tended towards the plugin for flexibility. It shouldn't be too hard. Unless the issue is collecting the metadata before passing it to the job?

I'll tell you in a couple of days... But my approach is less automatic, not ckecking device but marking books.

[davidfor]

Originally Posted by Terisa de morgan

I'll tell you in a couple of days... But my approach is less automatic, not ckecking device but marking books.

You are looking for the mismatches in metadata, marking them so that you can fix things later?

[milady133]

Originally Posted by davidfor

And while I said I am not interested in doing this, for a while I have had in my mind to do something to check reading status between calibre and the device. I've been thinking about this more since getting the Aura ONE and populating it (and yes, I'm one of those strange people who like to keep a lot of books on their devices). If I do that, extending it to compare some other attribute would be "a breeze".

Note: "a breeze" is used here as a programmers term to describe a small feature we think will be easy to add, but will probably end up taking more time than the rest of the project.

As someone who has been doing something similar "manually" for my sideloaded kepubs to return the reading status after the last firmware update, the OCD in me would appreciate it for when my Aura HD suffers a fatal accident and I have an excuse to replace it with an Aura One (although it seems the HD is not as fragile as people here complain eReaders are, it has survived some accidental falls)

Note: By manual I mean that some steps are manual, I don't know anything about python, but I'm good with databases, so working with a backup database and creating excel batches of updates I've been able to return that information to my two working Kobos.

[Terisa de morgan]

Originally Posted by davidfor

You are looking for the mismatches in metadata, marking them so that you can fix things later?

I'm changing metadata and marking the changes. There's no usually metadata mismatch aside of that.

[davidfor]

Originally Posted by milady133

As someone who has been doing something similar "manually" for my sideloaded kepubs to return the reading status after the last firmware update, the OCD in me would appreciate it for when my Aura HD suffers a fatal accident and I have an excuse to replace it with an Aura One (although it seems the HD is not as fragile as people here complain eReaders are, it has survived some accidental falls)

Note: By manual I mean that some steps are manual, I don't know anything about python, but I'm good with databases, so working with a backup database and creating excel batches of updates I've been able to return that information to my two working Kobos.

I'm not quite sure what you are saying, but...

If you are using the plugin to store the reading status of the books, the plugin can be used to restore them. If you do a factory reset or get a new device, you send the books to the device and then disconnect and let the device process the books. Then connect again, select the books you want to restore the reading status for and use the "Store/Restore current bookmark" function. Choose the appropriate options and press the OK button. That should do it.

If you are talking about restoring the database and other files, I won't be automating that. If you need to do it, find the backup, unpack it and copy the files over.

Or are you doing something else?

[Terisa de morgan]

Originally Posted by milady133

As someone who has been doing something similar "manually" for my sideloaded kepubs to return the reading status after the last firmware update, the OCD in me would appreciate it for when my Aura HD suffers a fatal accident and I have an excuse to replace it with an Aura One (although it seems the HD is not as fragile as people here complain eReaders are, it has survived some accidental falls)

Note: By manual I mean that some steps are manual, I don't know anything about python, but I'm good with databases, so working with a backup database and creating excel batches of updates I've been able to return that information to my two working Kobos.

I'm with David, I don't understand the need of manual tools. When I purchased the Kobo Aura One, I sent all my books and later, with Kobo Utilities, I updated all the reading status (position, finished/ongoing....). Of course, I have a specific library which contains all the book I have in any ereader/phone/tablet, and I store status when I connect my ereader to calibre.

Metadata in existing books (really comments in my case with associated plugboard) is a totally different matter, and it happens more frequently than a change of ereader.

[Terisa de morgan]

Originally Posted by Terisa de morgan

I'm changing metadata and marking the changes. There's no usually metadata mismatch aside of that.

Ditto, the plugin update automatically the metadata in the device if the tag for the device is in an specific column (all of them configurable). And it works like a job too, so no conflict in time (code duplicity but...)

[JSWolf]

Originally Posted by Terisa de morgan

Ditto, the plugin update automatically the metadata in the device if the tag for the device is in an specific column (all of them configurable). And it works like a job too, so no conflict in time (code duplicity but...)

I still think adding metadata updating to the Reading List plugin would be best. It already handles adding books very easily.

[Terisa de morgan]

Well, then you are not thinking it well, sorry. Updating Metadata means to update the database device, so device specific, while Reading List is mainly device agnostic.

Anyway, you are entitled to your opinion but I'm developing the code, so...

[JSWolf]

Originally Posted by Terisa de morgan

Well, then you are not thinking it well, sorry. Updating Metadata means to update the database device, so device specific, while Reading List is mainly device agnostic.

Anyway, you are entitled to your opinion but I'm developing the code, so...

Good point. I didn't think about having to update the database.

It is possible for one plugin to pass data to another plugin?