Library and Information Show 2007
There’s a few photos from the event on Flickr…
I think the previous post will be the last batch of graphs unless I uncover something new in the data. Instead, many thanks to my colleague Lisa (Senior Assistant Librarian for Applied Sciences and Computing & Engineering) for sifting through the respondent comments for the common themes. The full figures will be in the report, but here’s a snifter of the “feature comments”…
The most common wanted feature was federated searching (both electronic resources and other libraries’ holdings), with over 30 responses.
Next up, being able to customise the OPAC (look & feel and adding new features), with over 15 comments.
Relevancy ranking was specifically mentioned by at least 10 respondents, with 9 wanting personal borrowing histories, Amazon style wish lists, and saved session results.
1 respondent wanted to be able to search by colour of cover and another wanted wiki style functionality adding to the OPAC.
For the “final comments” section, here’s a sample…
10 respondents felt that “2.0” style features could be a distraction and that the OPAC should be kept simple. Another 10 said that lack of staff expertise or money was stopping them from being able to make the changes they would like to their OPACs.
However, the most common theme was laying the blame squarely at the feet of the vendors — broken promises, slowness of feature delivery, etc.
Lisa also picked out a handful of the comments that she felt stood out and here’s just 3 of them…
It seems that OPACs are too busy trying to please every customer. They spend too much time developing and not nearly enough time releasing software. The ability of the library to customize the OPAC should be the primary feature. Developing extensive APIs and building in flexibility should be at the top of the list for development. Let librarians develop the specific tools they want or need. Allow librarians to create add-ons and templates and distribute them to other libraries. OPAC vendors need to concentrate on search technology and not the next great feature.
I think we should always keep in mind the key aim of the OPAC is so users can locate/access resources. These new web 2.0 type enhancements can be fantastic, but there is a danger in using them just because we think we should.
We took a risk in 2002 and extensively customized our OPAC outside the confines of vendor support. Our efforts have been extremely successful and it has essentially become our new model for the direction we’re heading in the future. We’ll be doing MORE customization and application development in the future, rather than less. We’re much more likely now to move away from traditional library automation vendors as we consider what comes next.
(Phil Feilmeyer, Hennepin County Library)