Wednesday, January 21, 2009

Evaluating quality of answers in consortial chat reference

The latest issue of College and Research Libraries (January 2009, volume 70, number 1) has an interesting article by Deborah L. Meert and Lisa M. Given ("Measuring Quality in Chat Reference Consortia: A Comparative Analysis of Responses to Users' Queries") reporting on a study that attempted to measure the quality of answers provided in a consortial chat reference service to one member library's patrons. The final version of the article isn't available online yet but you can read the preprint here (PDF). 

The library where the chat service was studied is at the University of Alberta, which until a few years ago used 24/7 Reference and then QuestionPoint to provide a chat reference service available around the clock (they now use LiveHelp and staff the service themselves for limited hours each week). By looking closely at chat reference transcripts from sessions where University of Alberta patrons were helped, the authors of the article wanted to compare the quality of answers given by University of Alberta staff to the answers given by staff of other libraries in the chat reference consortia (i.e., non-University of Alberta staff).

The basic methodology of the authors was as follows:
  • select a representative pool of chat transcripts from the University of Alberta service
  • code each chat session as either answered or not answered
  • code the question type in each session (library user information; request for instruction; request for academic information; miscellaneous or non-library)
  • code each chat session as being handled by either U of A staff or non-U of A staff
  • for the subset of chat sessions that were coded as "not answered," code to indicate the reason why the questions weren't answered in real time (some were adequately answered after email followup with the patron)
I'll pass over detailing how the chat transcripts were selected and representative samples found. Instead, I want to offer some comments on the undiscussed historical context of the service studied, the sample set used, the coding methodology, the findings, and the implications. The authors say that they used transcripts from October 1 to April 30, but they don't mention what years that covers; they do say that the sessions used are from the first year of service but no launch dates for the service are provided. It would be useful to know exactly when the sessions took place, as there are some historical events that might help place the findings in notable context. I am pretty sure that the chat sessions took place when the University of Alberta was just using 24/7 Reference for its software; my college, too, was also a subscriber at the time, and I know that the number of other libraries in the academic consortial service grew rapidly. For the purposes of this article, it would be helpful for readers to know more about the consortia that was helping to provide answers to University of Albert patrons; specifically, how many other libraries were members of the consortia during the time period that the transcripts came from. How busy was the consortial service at the time? (The busier the service, the less likely that consortial librarians would be willing to expend a lot of time with any one patron and the more likely they would be to refer a question for e-mail follow up by the patron's home library).

Another notable detail is that during the time period that the Unversity of Alberta was in the 24/7 Reference academic cooperative service, they were the only library not in the United States. In their analysis of why non-answered questions weren't actually answered, the authors mention one possible reason as being a "cultural barrier" between librarian and patron, such as "not understanding the Canadian educational context" (80). It seems to me that the authors should have noted more explicity the reality that all the librarians from other libraries in the consortia worked at American colleges and universities and most if not all of the backup librarians employed by 24/7 Reference were also American.

Given that the University of Alberta, then, was the only Canadian institution in the consortia, I wonder just how representative these chat sessions are. I wish I could recall how many academic libraries were in 24/7 Reference when the University of Alberta was; if I had to guess, I would say at least fifty, maybe one hundred.

I did not see any mention of inter-rater reliability in the article. A note one way or the other ("yes, we did it" or "no, we didn't") would have helped me assess the validity of the coding of transcripts.

Another question that came to mind as I read this was whether assessing "answers" is the best way to evaluate a service. It is worth remembering that the study could have looked at how users perceived the quality of the service (do you feel like your question was answered? would you use the service again? would you recommend the service to someone? etc.)  or how they acted in response to the service (how many repeat users were there). I'm not sure I know the answer, but it is a question to keep in mind as you read this article.

The authors found that U of A staff met the library's own reference standards 94% of time; non- U of A staff 82% of the time. They also discovered that  U of A staff answered 89% of the questions in real-time (no followup or referrals were needed), while non-U of A did so only 69% of the time. Meert and Given say that for the consortial service to work at the U of A, the library there must:
provide adquate and easily accessible information to non-UofA staff (assuming that non-UofA staff use this information) that allowed them to answer most questions regarding library user information correctly, and in real time, this would decrease the number of questions not meeting the UofA reference management standards and would increase the number of questions anwered in real time by non-UofA staff. (82)
They go to say that this study "should provide further assurance that high standards of quality can be achieved by nonlocal staff in a chat reference consortium" (83) as long as "consortium staff...have the information they need to answer the most commonly asked types of questions, particularly the kind described in the 'Library User' question category" (82).

It's a shame that the University of Alberta no longer uses a consortial service, because I think it would really great to do this study again. Since the university stopped being in the consortia, it has undergone a number of notable changes. First, 24/7 Reference got acquired by OCLC and merged into its already existing QuestionPoint service. Second, QuestionPoint then built an all new chat software based on the 24/7 Reference software. Third, the consortia has grown considerably since the days that the University of Alberta was in it. I would love to know if service is better or worse now.

A factor that isn't addressed in this article is that while the staffing of chat reference at the University of Alberta may have been relatively stable, the consortia itself was constantly adding new libraries. With each new library in the consortia comes a bunch of librarians brand new to consortial chat reference; it takes quite a bit of experience to be able to provide reference in the consortial environment. Also, experienced staff already in the consortia may retire or take other jobs. It can be quite a challenge to make sure that everybody monitoring a consortial chat service is well-prepared to help patrons a libraries flung across the continent.

I must say that despite my comments, I think this is a good article and well-worth reading. As the authors point out, there has not been much work done yet in looking at how well patrons are helped in consortial chat reference services. This article offers an interesting methodology that I hope others will replicate.

Tuesday, January 20, 2009

Correction to earlier post about busiest day of the week

I just realized that I made an error in the way I did computed averages in my post a few weeks ago detailing what was the busiest day of the week for my college's chat reference service. It looks like Tuesdays are actually the busiest day of the week for us, not Saturdays (just barely). The original post now contains a correction at the end with the revised statistics.

Thursday, January 15, 2009

Widgets and chat reference discussion at ALA Midwinter

If were going to ALA Midwinter this month, I would definitely check this discussion group's event out:

RUSA MARS Virtual Reference Discussion Group (VRDG)
Saturday, January 24, 2009, 4:00pm - 5:30pm
Hilton Garden Inn, Element Ballroom

Do You Fidget with a Widget?

Join your colleagues in learning how widgets are being used for virtual reference chat and IM-based reference services.  What widget features are helpful? What improvements are needed? Thinking about adding a widget to your library’s Web pages?

Kathleen Kern and David Ward will present an introduction to the University of Illinois at Urbana-Champaign’s IM Collaborator software. Discussion of widgetry and all things virtual reference will follow.

Come and participate in a lively discussion. Hope to see you there!

The Virtual Reference Discussion Group is sponsored by the Reference and User Services Association [RUSA] Machine-Assisted Reference Section [MARS].

Monday, January 12, 2009

Most popular times of day for chat reference at Baruch

In my last post, a commenter asked for details on what hours of the day were most popular for chat. Here is a list of the hours of the day showing the changes by hour of the for all 1,890 chat sessions requested in 2008 on the Baruch College service:
12 am - 1 am, 52
1 am - 2 am, 32
2 am - 3 am, 25
3 am - 4 am, 9
4 am - 5 am, 4
5 am - 6 am, 2
6 am - 7 am, 1
7 am - 8 am, 9
8 am - 9 am, 40
9 am - 10 am, 68
10 am - 11 am, 124
11 am - 12 pm, 128
12 pm - 1 pm, 143
1 pm - 2 pm, 148
2 pm - 3 pm, 148
3 pm - 4 pm, 128
4 pm - 5 pm' 128
5 pm - 6 pm, 130
6 pm - 7 pm, 109
7 pm - 8 pm, 98
8 pm - 9 pm, 117
9 pm - 10 pm, 95
10 pm - 11 pm, 91
11 pm - 12 am, 61
Here is that same list sorted to show hours from busiest to slowest:
1 pm - 2 pm, 148
2 pm - 3 pm, 148
12 pm - 1 pm, 143
5 pm - 6 pm, 130
11 am - 12 pm, 128
3 pm - 4 pm, 128
4 pm - 5 pm, 128
10 am - 11 am, 124
8 pm - 9 pm, 117
6 pm - 7 pm, 109
7 pm - 8 pm, 98
9 pm - 10 pm, 95
10 pm - 11 pm, 91
9 am - 10 am, 68
11 pm - 12 am, 61
12 am - 1 am, 52
8 am - 9 am, 40
1 am - 2 am, 32
2 am - 3 am, 25
3 am - 4 am, 9
7 am - 8 am, 9
4 am - 5 am, 4
5 am - 6 am, 2
6 am - 7 am, 1
I also took those numbers and aggregated them into four six-hour blocks to see what part of the day generally is busiest:
Morning (6 am - 12 pm), 370 chats requested, 20% of total
Afternoon (12 pm - 6 pm), 825 chats requested, 44% of total
Evening (6 pm - 12 am), 571 chats requested, 30% of total
Late Night/Early Morning (12 am - 6 am), 124 chats requested, 7% of total
It is worth keeping in mind that Baruch College is a commuter school. Most of our students work part- or full-time, which may make our numbers different from what you might see for a chat service at residential college.

Chat service at Baruch College shows increasing use

As I continue to crunch last year's numbers from my college's chat reference service, I thought I would note here that the number of chat sessions requested has gone up slowly over the past three years (which is when we started using the flash-based QuestionPoint software and had access to new data points like "chat sessions requested" and "chat sessions accepted."). Here are the statistics:

2006: Number of chat sessions requested = 1722
2007: Number of chat sessions requested = 1757 (a 2% increase from previous year)
2008: Number of chat sessions requested = 1890 (an 8% increase from previous year)

I don't have any theories about why the numbers have been going up. I'm digging through old spreadsheets I made from years ago to see if any can find the comparable data from the earlier years of our chat service (2001-2006). The older software we used to use (first HumanClick, then 24/7 Reference) did not tell us how many sessions were requested; instead, they only offered how many sessions were answered, which is a different number. With HumanClick (which we used from 2001-2002), we only offered the service ten hours a week. Comparing annual data from recent years with this older data does not really make sense, as the current service allows patrons to chat around the clock.

With 24/7 Reference and QuestionPoint, the data about the number of sessions answered does not jibe with the HumanClick-era data, as the latter was used for a chat service that just covered our college alone. Once we started using 24/7 Reference and then QuestionPoint software, we found ourselves answering chat sessions not just on the Baruch College queues but also a growing cooperative of academic libraries that used the same software. Our librarians found themselves busier than ever on their two-hour shifts answering questions from Baruch patrons and those at other colleges. One thing is certain though about data from those early years; going from a service of ten hours a week to an around-the-clock cooperative chat service dramatically boosted the number of chat sessions requested on the Baruch service; suddenly our service, backed up by an army of capable librarians at colleges across the country, was able to help all those students with questions on weekends and weekday evenings, times that we never could have staffed a chat service on our own.

Friday, January 09, 2009

Thursdays are slow for chat?

I've been doing a lot of number crunching for the chat reference service here at Baruch College and for the five other colleges in CUNY that share a QuestionPoint subscription with us (Borough of Manhattan Community College, Brooklyn College, CUNY Graduate Center, Hunter College, and John Jay College). I was just looking over numbers for Baruch's service and discovered that Thursdays, of all days, are the slowest days for our service.

Here's the data with the day of the week, followed by the number of chat sessions requested on just the Baruch College service, the percent of all requests for the month (215 for all of November), and the rank of that day of the week:

Monday: 32 chats, 15%, 3
Tuesday: 40 chats, 19%, 2
Wednesday: 28 chats, 13%, 5
Thursday: 18 chats, 8%, 7
Friday: 25 chats, 12%, 6
Saturday: 42 chats, 20%, 1
Sunday: 30 chats, 14%, 4

I realize that at least one Thursday was Thanksgiving, but before doing the analysis I didn't expect that Thursday would be our slowest day of the week. Our reference desk is busiest on Tuesdays and Thursdays, so I figured that would hold true for chat reference. I would pull a larger data set to see if this finding holds true across a longer time span if it wasn't so difficult to do this kind of analysis. The QuestionPoint reporting tools don't record what day of the week a chat took place on. I had to export the daily chat session activity into a spreadsheet and manually type in the day of the week for all 215 sessions. (I assume that those with fancier spreadsheet/database skills could make this work of assigning days to dates automated in some way.)

CORRECTION (20 January 2009): Whoops! I recently realized that I didn't use an equal number of days of the week when running my report. The month I analyzed (November 2008) has four Mondays, Tuesdays, Wednesdays, Thursdays, and Fridays and five Saturdays and Sundays. By taking the average number of chats per weekday, I made the mistake of taking the average of five Saturdays and five Sundays. If I drop the numbers for one Saturday and one Sunday, then it turns out that Tuesday is the busiest day of week, not Saturday, which makes a bit more sense to me. Here is the corrected breakdown:

Monday: 32 chats, 15% of total, 3rd busiest day

Tuesday: 40 chats, 19% of total, 1st busiest day

Wednesday: 28 chats, 28, 13% of total, 4th busiest day

Thursday: 18 chats, 9% of total, 7th busiest day

Friday: 25 chats, 12% of total, 6th busiest day

Saturday: 39 chats, 19% of total, 2nd busiest day

Sunday: 26 chats, 13% of total, 5th busiest day

Thursday, January 08, 2009

The Free Rider Problem and Chat Cooperatives

As an experiment, I decided to try doing a video post. The subject is equity among member libraries in chat reference cooperatives.