View Single Post
Old 04-11-2015, 08:03 AM   #20
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by DoctorOhh View Post
Nevermind, I changed the setting to mark book as read when opened. I never set this before because I didn't want a book marked as read until after I finished the book. But I see it doesn't mark the book as read only sets the date. This works for me.
You raise an interesting question. I chose to use Date Read because it is there, is automatically maintained, and I thought semantically what was wanted. However, given that a user can apply alternate semantics to the date as well as turn it off, perhaps I should add another date to keep track of when a reader is launched on a book.

Adding this date would be very straightforward. One downside: it would require a "short" database upgrade (one that touches the main table but does not look at every book). Another downside (and perhaps an upside) is that the user cannot change/erase the date to make a book disappear from the widgets. Syncing with calibre would/could not change this date.

Thoughts?
chaley is offline   Reply With Quote