Aside from paying very little attention to visual design and not caring about the impact of horrible typography, the big problem with library catalogs is that they are not designed to help people accomplish library tasks. Instead, they’re designed to expose catalog records.
I’m not even talking about lofty library tasks like learning, creating, and connecting. I’m not referring to semi-interesting library tasks like discovering exciting content. I’m talking about very basic library tasks: finding items in a specific location, reserving items, and renewing items. Of course, people can do these tasks with our catalogs but only because the functionality has been clumsily bolted onto catalog records.
Correct me if I’m wrong, but this is totally backward—prioritizing the collection, not people, results in a user-hostile interaction design and a poor user experience. Imagine the reverse: a tool that prioritizes helping people accomplish their tasks, whereby bibliographic data exists quietly in the background and is exposed only when useful.
Starting from Design
I wondered what this would look like, so I sketched out some examples. I’m certainly not the first to complain about OPAC functionality, but taking this as an explicit design challenge rather than as a software architecture or cataloging challenge led me to emphasize readability and ease of use.
Beyond that, there isn’t too much to explain about these designs. Here’s a very plain bibliographic record and illustrates how simplifying them would make them easier to use.
The following hints at eliminating the need for a dedicated view of a single bibliographic record; in this mock-up, nearly everything a member needs to do with an item is available without it.
The ability to link directly to a single record is missing from this example, but that would be easy enough to sort out. This one is similar but uses a swipe-friendly layout that could be effective on mobile devices.
An effective catalog design would obviate the need for how-to screencasts and handouts. Designs like this would not only make our libraries easier to use, but, by freeing up the time we spend helping people with our catalogs, they would make librarians’ lives easier, too.
While these examples aren’t fully featured, they illustrate how focusing on people and tasks would change our catalog. When bibliographic data plays second fiddle, the page calms down and is easier to understand and use. What’s more, by employing some basic principles of graphic design, these creations instill more confidence in library services than our current catalogs.
Members in Mind
This is just one example of how focusing on our members’ motivations and goals can transform what we do. Members will be better served if all of our services are designed as responses to their motivations and goals. With regard to catalogs, this focal point leads to improvements in usability. For library services, this emphasis makes libraries more worthwhile.
The deeper libraries dive into the lives of their members and explore opportunities for improving their lives, the more impact we can make and the more valuable libraries will become. This sort of listening, not shouting, is the best form of library advocacy.
This first appeared in “The User Experience,” a column I write for LJ.
To my knowledge, this is the first iPhone application put out by a library. A big congrats to DCPL CIO Chris Tonjes who assembled a great team, and a big thanks to Brian Farmer for his coding skills, Bill McClendon for his knowledge of the SirsiDynix backend and Gilbert Luwaile for testing. You can read more about all of them at the 