I've been busy this summer engineering two online moves and launching a new blog. For four and a half years, our library's reference wiki and reference staff blog have been at hosted services (PBworks, formerly PBwiki, and Blogspot, respectively). Having witnessed a number of free online services go belly up over the few years (e.g.,
Yahoo! Photos,
Google Video, Google Notebook, Jaiku, etc.), I decided that it would be best to run these essential communication services on servers we fully control. We're nearly done moving our password-protected reference staff wiki (which is essential a policy and procedures manual, as well as a repository of inside dope) from PBworks to Confluence. This week, we officially relaunched the staff blog,
Reference at Newman Library, on WordPress MU, which is
locally installed and administered here on the Baruch campus by the cracker-jack team at the Schwartz Communication Institute.
Moving the wiki from
PBworks proved particularly hard. Because of the lack of interoperability among many wiki platforms, there was no easy way to import the 500 pages from the PBwiki version of the wiki to the new
Confluence one. Instead, a dedicated and detail-oriented student employee copied and pasted text and recreated links. The version of Confluence that we have installed here does not offer all the bells and whistles that PBworks does, but when we get the new version set up and add in a few plugins, it should be as rich an environment for the user as what we had in PBwiki.
Later this week, we'll officialy launch another new staff blog that is intended to highlight issues and news of interest to all library staff in our library. Called the
Newman Library Idea Lab, this blog written by and for the folks who work here. Feel free to subscribe, though, as the content should be of interest to anyone who works in most any outpost in libraryland.
A post on the iNODE blog,
"OA Begins at Home," struck a chord with me. We should be doing more to ensure that open access content is findable in our discovery systems (link resolvers, A-Z journal lists, even the databases we subscribe to).
I recently discovered that the
San Jose State University School of Library and Information Science has a podcast series from its colloquia (here's the
feed URL) that includes a nice presentation by
Lili Luo from 2007 about chat reference skills and chat reference training. There are number of ways to access the recording of her presentation:
As part of her doctoral work at UNC Chapel hill, she surveyed nearly six hundred librarians about what they felt were the essential chat reference skills. Then she held another survey that close to three hundred librarians responded to in which respondents noted which training techniques they had encountered when being shown how to do chat reference.
Of the thirty compentencies listed in the first survey, twenty-one were deemed essential. As noted on Luo's slides from her presentation, the top five were:
- Refererring users to appropriate/services when necessary
- Skills in selecting and searching databases and internet resources
- Familiarity with subscribed library databases
- Ability to think quickly and deal flexibly with unexpected situations
- Using open probes to clarify questions
The survey on chat reference training techniques asked respondents to rate twenty-three different approaches for teaching. The top ones that Luo listed on her slides were:
- Trainees pair up as patron and librarian to gains hands-on experience on using the software
- Trainees review selected chat transcripts to learn more about the transation
- Trainees ask questions to real chat reference services as users and evaluate their experiences - the secret shopper approach
- Librarians pair up to practice chat reference skills on a regular basis for a certain period of time
- Cheat sheet containing vital information librarians might need to access quickly and often while covering the service
There is tons of great stuff here that should help anyone who has to train colleagues in how to do chat reference. The only quibble I have is Luo's description of a competency that is unique to chat reference: the knowledge of library services and resources of other libraries in a chat reference consortium. She suggests that to provide effective service in a cooperative service, librarians must have a basic level of familiarity with the services and resources provided at each member library. I don't think that quite gets to the real skill that librarians who do chat in a cooperative environment have to master.
What is essential is that librarians are familiar enough with the wide range of services (and ways of offering those services) that a library elsewhere in the cooperative might offer. As a librarian at Baruch College helping students at UC San Diego in the QuestionPoint 24/7 Reference Academic Cooperative, I don't need to have memorized all the services at UC San Diego. I just need to know how to navigate the library's web site to see if such a service that the student is asking about is offered and how it is offered. In QuestionPoint, we also have online "cheat sheets" on each library in the cooperative that give you a quick overview of that library and its services and resources (as well as the relevant links to the library's many web pages). If UC San Diego happens to loan digital cameras to students, I am not expected to have memorized that fact; but I should know how to find out if the UC San Diego library does so if I am ever asked about.
As far as familiarity with resources at member libraries go, again, I don't need to have memorized what libraries have which databases. But I must know how to locate any library's list of databases. I should also know how to recommend databases that I am unfamiliar with based on subject guides, etc., that a library has put up. At no point, though, am I expected to have the ability to list from memory what resoruces each library has. With hundreds of libraries in the academic cooperative, it just isn't possible to memorize like that even if you wanted to.
Dont' let this very minor quibble, though, deter you from checking out what is a wonderful presentation.
My colleague here at the
Newman Library at Baruch College,
Frank Donnelly, writes a really interesting blog that focuses on issues and technologies for GIS. Launched in March 2008,
Gothos features coverage of new GIS resources and detailed step-by-step instructions for various projects using GIS software.
After having
PBwiki host the wiki for our reference staff for the past four and a half years, I'm finally taking the plunge to move to whole thing (499 pages!) over to a locally installed version of
Confluence. The college where I work got Confluence to use for various intranets needed around campus. Worried that some day PBwiki might just plain disappear, I decided to move the reference wiki over to something that is on our own servers and more under our control. It will take a chunk of the summer to laboriously recreate the wiki via copy and paste (wiki software from different vendors don't seem to make it easy to do import/exports). So much for that long week at the beach...