Nov 20
So I've been asked by the Adult Services department head to come up with a means to retrieve and store statistics for "Questions Answered at the Public Service Desks". Currently, they're using a pen and paper approach from a template created in Microsoft Word. Each staff member (reference librarian) at the desks (currently using the paper document) has to print out one sheet per day (therefore, the Reference Desk has 2 sheets each day, Information Desk has one sheet) and will tally (slash slash slash slash, cross) the number of questions asked, separated by hour(s) (9-11, 11-1, 1-3, 3-5, 5-9). There's also a section for notes such as "We need the following items...", "Interesting Questions", and "Suggested books/items to order".

He mostly wanted a way to reduce the paper trail and become more "green". All those papers are then returned to his desk at the end of the day. He tallies the results at the end of the month. That's approximately 3*5*4 = 60 full pieces of paper to go through to count (by hand) all of the stats, as well as read (all at once) the comments and/or notes. Granted, I don't know if he keeps a running tally (one would hope), but either way, that's a lot of unnecessary work.

Since other desks/departments may find this useful, I've extended the schema in the database that will hold the information to account for that. Although it can all be managed via a web page (and is currently working as such in skeletal form -- thank you, CakePHP and 5 minutes of time), I've opted for a better solution. Since it'd be unruly to require a webpage to be open at all times, or dealing with load-times on a webpage from a favorite or desktop shortcut, I'll be developing a dynamically created UI using Adobe Air to allow for a desktop application. All it will require from the staff member is to either click on a button (and then verify -- requested from the department head), or fill in a text box. Upon installation the application will verify which public service desk it is at and use that information from then on.

The department heads in charge of each service desk (in case any other departments wish to use this) will then be able to view reports and statistical data from a staff intranet page, as the database will be maintained on our webserver. I'll probably integrate it with Open Flash Chart like I did on a personal project - it turned out really nice looking and was easily stylized (with a little understanding of its settings).

Hopefully when all done I can post some screenshots of the first draft of the final product. It's meant to be very simple, but nice with features...we'll have to see if I deal with connection issues to the database (as Adobe Air also has a local file store and can check on server responses). Either way, I have a lot of reading ahead of me on Adobe Air now that the database schema is complete. The statistics will come last...but we should have hourly, daily, weekly, monthly, and yearly break downs.

Posted by Brendon Kozlowski

0 Trackbacks

  1. No Trackbacks

2 Comments

Display comments as(Linear | Threaded)
  1. Mike says:

    Sounds good. We do stats one week per year and then extrapolate the numbers. Pen and paper is the method used. I guess if we were doing stats all the time, it might be worth going paperless but when it's one week a year, it hardly seems worth it! ;-)

    However, if your app is slick enough, maybe I will change my mind. :-P

  2. Brendon Kozlowski says:

    Apparently most other libraries do these type of stats the same way you do. Our new Director said his old libraries all did it the same way you do. The nice thing about doing it all the time is to realize what times of the day, and what days of the week, and what weeks/months of the year are our busy times. By using these metrics, we can also extrapolate better times to make sure we have only one, or more than one person on the service desk(s) (our Reference Desk supports 2 concurrent reference librarians assisting our patrons, Info Desk is 1 library, 1 volunteer)...thusly letting us properly utilize our staff hours. Whether it's to be used for that purpose or not I cannot say!

    ...that, and another nice thing is that Flash Charts are quite pretty. ;-) You'd be more than welcome to the codebase, although the backend code might not be as useful since I'll be using a PHP framework - the SQL schema and Air app code would work though.

Add Comment


Standard emoticons like :-) and ;-) are converted to images.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA

BBCode format allowed