Reading Management consists of optional support for tracking how much you have read, when you read a particular book (or part of a book), and for planning future reading. This will probably take the form of a plugin (turned off by default, for simplicity) which makes storing the additional information possible through the main Alexandria interface.

The developers are not very familiar with Reading Management, so any further details as to what users actually require the software to do/store/produce would be helpful.

Ian Davey on the mailing list (http://rubyforge.org/pipermail/alexandria-list/2007-September/001318.html) suggested the following features:

Data Storage

• Dates relating to when a book was read
  • Start date (optional)
  • Finish date
• Optionally store page numbers for all books
  • How many pages were read during a particular interval
• Goal list for unread books, a list books to read

Scripting

• At the moment (0.6.2), users might wish to store finish-date information informally, perhaps in the Notes section of a book, perhaps as a tag e.g. [Finished:2008-01-29]. As an informal entry, this has no real function except as a place to note the information down. In the future, when Alexandria supports Reading Management, it should be possible to run a bespoke script over old book records and turn the informal note or tag into proper Reading Management data. (http://rubyforge.org/pipermail/alexandria-list/2007-November/001376.html)

Data retrieval

• A “statistics tool” [mentioned in #17563] It should be possible to produce a report of what books were read over a particular period. We need more details on what statistics users actually want to see, and what a user-interface might look like.