Reading Pages

[pommernMeg]

Statistics are currently displayed for weekdays, days of the week and months, each in time.

But it would also be interesting to see how many pages that would be. Because an eBook is not always the same and some days you read more but also fewer pages because the layout only allows it.

[extra-jalapenos]

I think I've seen some hint that pages are logged in the database by KOReader depending on actually rendered pages -- which depends heavily on the user's display settings. As in -- if we both read the very same book, but your eyes are better, you'll have read less pages than me (or: if you get older, you'll "read more pages" in timeframe, because font gets increased).

Are you ok with that / still see the value in this?

[GeorgeSG]

@extra-jalapenos that's what the reference page count is for. KOReader is logging page and total page count. If you enter reference page count, the page counts from KOReader would be normalized for that value.

For example, if KOReader is logging that you read 10 pages out of 200 (this takes rendered page size into account) and you enter reference page count 100, each of the 10 pages will be counted for 2, so KoInsight will show 20 pages read.

At least that's how it's supposed to work, I think I covered it pretty well with tests 😅

[extra-jalapenos]

Hey @GeorgeSG , sorry, forgot to mention that I'm aware of that, I just thought that this has the same hurdles as the covers in terms of usability, or even more tedious as your cover adding workflow is very agreeable with pre-filled title and only having to click a cover that one likes. For reference pages users would have to scour the web for the hardcopy page count. I intend to look into the matter over the weekend (both raw data structures and e.g. external databases for suggestions of page counts). :)

[GeorgeSG]

Yeah, the UX is not great, and it's hard to even explain what the "reference page count" is 😁

The best thing to do IMO is find a way to link the book to some specific edition in an external API (I used to work with Goodreads API way back, but I think this is no longer available). The API should give us cover, reference page count, tags, etc, anything we may need for additional metadata. But the user should be able to pick the specific edition, and this is non-trivial in my experience.. since some books have like 900 editions in different languages :D

Another option is to have a "setup book info" guided wizard for newly imported book. Just ask the user step by step to provide book cover, reference page count, etc.

For reference pages users would have to scour the web for the hardcopy page count.

That's a fair point too, I'm not sure how to resolve that, open to ideas :)

[extra-jalapenos]

Thanks for your insight, I had intended the very same way to go about retrieving additional information about books (external API), I'll see what's out there. The wizard idea is neat, too!! Hadn't thought about this.

(On a personal note, the statistic nerd in me is bugged about the different layouts of books, so a page is not the same as a page in a different book, so I'd actually prefer to go by word count because that's pretty solid as measure and if you know that one pocketbook page has roughly 250 words or something like "Harry Potter 1 is roughly 70,000 words", you have a pretty good idea about the real-life equivalent. I pay way more attention to the word count than the page count when in Calibre.
I can imagine though that I'm very much alone in this preference though)