Frequently Asked Questions (FAQ)

Traditionally libraries have used paper systems to track Summer Reading Program participants. While this method works, we wanted a system that could:

• Provide better tracking of participants & completed levels.
• Reduce the number of duplicate registrations.
• Provide statistics without manually counting paper records.
• Allow patrons to register themselves.
• Be used by many staff & volunteers simultaneously, preferably from a web browser.
• Fit within our limited (read: non-existent) budget.

ReadingRecord doesn't replace paper reading records, but rather uses the information collected to track Summer Reading Program participants & generate statistics. It is a hosted application, meaning that no additional equipment is required to use ReadingRecord - just a web browser. Although aimed primarily at reading programs for Children and Young Adults, it can be used for Adult programs as well.

• Participants can register online, reducing staff time.
• The library can allow patrons to register before the program starts, alleviating some of the “first day” rush.
• Reduces the number of duplicate registrations.
• Tracking of participants & completed levels.
• Online access for patrons & staff using a web browser.
• Tracks any number of levels & prizes.

For a detailed list of features, including fields tracked, see the features page.

ReadingRecord is a free, hosted service. As such, no server hardware/software, technical knowledge or IT support staff are required.

ReadingRecord runs on the LAMP open-source web platform. LAMP is an acronym for:

• Linux: The server's operating system.
• Apache: The web server.
• MySQL: The database engine.
• PHP: The scripting language.

Furthermore, ReadingRecord runs on a virtual server using VMware software. Using virtual servers makes it easy to:

• Create additional ReadingRecord servers should load demand it.
• Move ReadingRecord to another server in the event of hardware failure.
• “Upgrade” the ReadingRecord server by moving it to newer/faster hardware.

If your library has an Internet connection and a computer with a web browser, you can probably run ReadingRecord. Some basic requrements include:

• An Internet connection. ReadingRecord is not graphic or page intensive, so even a slow connection should be adequate.
• A reasonably current web browser. The developers try to avoid “browser-specific” code at all times. If you come across a page that doesn't work with your browser, please let us know!
• A small amount of JavaScript is used on some of the pages. They should still work with JavaScript disabled, but extensive testing has not been done.
• Cookies are required for the staff module. ReadingRecord uses a small cookie to track staff logins.

The Westminster Public Library is the primary sponsor of ReadingRecord. WPL has used Linux & open-source software for over 10 years to provide a wide range of services to staff and the public. Part of the open-source philosophy involves giving back to the community, and we felt this was a good opportunity to do so. Rather than create another in-house only system, we wanted something that could be used by other libraries as well.

Douglas County Libraries is also a sponsor of ReadingRecord. Without their willingness to expand their in-house system, including letting WPL “try it before buying it” the first year, ReadingRecord would never have been born.

For more information, see the Team Members page.

ReadingRecord is available as a free, hosted service to libraries in the State of Colorado:

• Contact Eric Sisler to make sure we are still accepting new members. Including the word “ReadingRecord” in the subject will help expedite your application.
• Stay current with ReadingRecord announcements & discussions by joining the ReadingRecord Google Group.
• Fill out the Forms required for setup & customization.
• Provide feedback & report any problems encountered.

Last update: 2010-04-14

I and other library & city staff have been working to make this happen since June of 2009. Thus far everyone has been in favor of and enthusiastic about making it happen. That said, there are still a number of obstacles to overcome and while I am confident that it will happen, unfortunately it won't happen in time for the 2010 Summer reading season. My goal is to ensure that RR is available without any restrictions or encumbrances, it is simply taking much longer than anticipated and I want to make sure it gets done right the first time. I hope to have final approval by Fall or Winter of 2010, so stay tuned. In the meantime:

• Contact Eric Sisler to let us know you're interested! This will help us gauge the amount of interest and (hopefully) expedite the approval process.
• Stay current with ReadingRecord announcements & discussions by joining the ReadingRecord Google Group. Any announcements about availability outside Colorado will be sent to the group.
• Play with the demo sites if interested.
• Keep your fingers crossed that approval is given!

ReadingRecord is designed for libraries of all sizes. It has been used for single branch libraries registering less than 200 readers to a 13 branch district registering over 23,000 readers. To get an idea of what size libraries are using ReadingRecord, see the statistics page. That said, if your library is larger than anything you see listed on the statistics page, please let us know so we can discuss any potential issues.

Yes! If your library is interested in access to the RR demo sites, please contact Eric Sisler.

ReadingRecord provides the following standard statistical reports. The database can also be exported to a CSV file, suitable for importing into a spreadsheet program.

Individual book titles and/or book reviews/ratings cannot be tracked at this time. If there's enough interest in these features they may be added in the future. That said, “book”, “pages”, “hours read” or just about anything else you can think of can be substituted for “levels”.

Q: What happens to the patron's information once the reading clubs are over? Is their information wiped out or is it stored somewhere permanently?

A: That's mostly up to the participating library. Westminster Public Library has a 4-week rolling tape backup of all library servers, which includes the Summer Reading Program databases. That said, there's no reason for us to keep the data from your program, so the databases will be deleted at some point after the program ends. The databases will remain archived on older tapes until overwritten by the 4-week cycle, but after that they will be gone. If you want to keep the data, a database dump or export to CSV format is an option.

Q: Patron's information isn't used for anything other than reading club business, is it? (e.g. they won't get email blasts about programs or fund raising).

A: Yikes! The Westminster Public Library may elect to send an e-mail to our patrons about next year's program, but there's no way we'd use your data to SPAM people. Data from each program lives in a separate database - there isn't one central DB containing data from all participating libraries. Your data is your data, you can do what you want with it once the program ends.

Q: Oops! I forgot to include a city / zipcode / level / whatever. Can it be added later?

A: In most cases, yes.

By default, the maximum number of records supported by ReadingRecord is:

• 6 programs per library. This can be any combination of toddlers, kids, tweens, teens, adults and just about any other group of readers you can think of.
• 65.5 thousand readers per program.
• 16.7 million completed levels per program.

If you feel this may not be adequate for your library, please let us know before you begin using ReadingRecord. Not to mention: Wow! You're really busy!