Would a Calibre plugin to extract reading progress from the kindle be useful?

[tpb]

I've built some scripts to automatically extract metadata from the Kindle and sync it to user defined custom columns in Calibre. This lets me sort my book collection by read/unread, date last read, number of reads, etc.

The data is provided by KRDS:info like position, completion status, hours read, etc.

If there is interest, I could clean this up and publish it as a calibre plugin. Years ago I saw quite a few threads about this, but I'm not sure if amazon has ever added this ability to newer kindles as mine is quite old now.

For me, my kindle only shows 0-100%, and that percent is reset if you ever open the book to a different page so your progress is lost. There's also no way to see if you read a book more than once, or sort by progress/last read.

This could also be easy to expand to other devices if extractors like KRDS exist on those platforms, but I haven't looked into that yet.

[Defenderland]

This sounds fantastic.
I personally would be most interested (besides the hours spent on a book being displayed in a column) in the calculation of the reading speed (WPM - words per minute).

Reading without any thoughts on measurement and afterwards checking it, could give interesting insights and comparisons (progress when learning a language, light literature vs heavy, speed variying with author, genre, ...).

[JSWolf]

Can the reading position be put back on the Kindle?

I don't know why there is an option for a different device as Kobo Utilities can already get reading positions and put them on the Kobo. This is a plugin for calibre. So we already have a different device able to do this.

And @tpb, if you want this to be a plugin, just make it so. That's how most plugins came to be. Someone wanted it and was able to make it.

[tomsem]

Originally Posted by tpb

For me, my kindle only shows 0-100%, and that percent is reset if you ever open the book to a different page so your progress is lost. There's also no way to see if you read a book more than once, or sort by progress/last read.

(for current Kindle) Percent reflects reading location in the book, if you change the location, it changes the percent complete. Amazon also tracks 'furthest page read' FWIW, I don't know if that's available for extraction (probably not).

Of course end of book may be well before the last location in the book, if there are footnotes and other end matter that are there just for reference purposes. There is metadata (ToC entry) that defines End of reading as set by publisher.

Newer Kindles (2024 models and Scribe) use MTP so if you want to read it directly you'll need to figure out how to use calibre's MTP device interface, probably would need to extend it.

I personally don't have any interest in tracking reading at such a granular level but didn't want to vote 'No' as I would not want to discourage the effort to create a plugin that could do these things.

[j.p.s]

Originally Posted by tomsem

(for current Kindle) Percent reflects reading location in the book, if you change the location, it changes the percent complete. Amazon also tracks 'furthest page read' FWIW, I don't know if that's available for extraction (probably not).

azw3f files in the .sdr directory for KF8/azw3 books have "fpr" and "lpr" fields each of which has a "position" subfield, where the numerical position is the byte number of that location in the uncompressed marked up book text. The values stored in those fields can be extracted with the (partially yours) utility krds.py
https://www.mobileread.com/forums/sh...d.php?t=322172
https://github.com/K-R-D-S/KRDS

I think that "fpr" is furthest position read and "lpr" is last position read, at least the numbers make sense for the books that I spot checked. (Well, I guess the "p" in fpr and lpr could still be "page" since the subfield is "position".)

KFX has a more complicated position structure, but it probably has a similar file amenable extraction by krds.py

[tomsem]

Good to know.

I suppose we need to check to see if any more changes are needed to krds.py (e.g. for active canvas location, underline type, etc.). I'll try to get to this.

[Drybonz]

I had actually just come to the forum to find out if there was a way to do this... so, yes!

[John F]

Originally Posted by JSWolf

...

I don't know why there is an option for a different device as Kobo Utilities can already get reading positions and put them on the Kobo. This is a plugin for calibre. So we already have a different device able to do this.

There are other devices besides Kindle and Kobo? Or am I missing something?

[tpb]

Originally Posted by tomsem

(for current Kindle) Percent reflects reading location in the book, if you change the location, it changes the percent complete. Amazon also tracks 'furthest page read' FWIW, I don't know if that's available for extraction (probably not).
...
Newer Kindles (2024 models and Scribe) use MTP so if you want to read it directly you'll need to figure out how to use calibre's MTP device interface, probably would need to extend it.

Thanks for this info. So it seems Amazon has still not included the ability to preserve reading progress/read indicators if you ever re-open the book to a different page, which was my main motivation behind this.

I'm really not sure about the MTP issue as a don't have a newer device to test on. Currently I'm just walking through the device path Calibre provides and using KRDS to read contents of the .sdr dirs.

Originally Posted by Defenderland

This sounds fantastic.
I personally would be most interested (besides the hours spent on a book being displayed in a column) in the calculation of the reading speed (WPM - words per minute).
.

Good idea. I've added this already and it will be in the initial release.

Originally Posted by JSWolf

Can the reading position be put back on the Kindle?.

Yes, I tested this with my kindle using .mobi files and writing the reading position seems to work. Replacing the first two numbers in the lpr struct in the .mbs file makes the kindle open to that new position on the device.

I do not know if this works on other kindles/firmware versions, and I also don't know what risks there may be if the .mbs file is corrupted (e.g. writing a value that is greater than the total positions in the book.). This could be really useful if people have multiple devices though, so I'm open to looking into it.