The future of Web Services isn’t the Library website
The last three weeks I’ve been thinking a great deal about the role of my department in fulfilling the Libraries mission and where the department needs to go in the next 3 years. Part of getting where we want to go has been this whole site redesign process. But not in the way most of the library thinks. Most of the library sees the redesign process as about “fixing” the current website so that it is more usable, up-to-date, and attractive. For me this isn’t really what the redesign is about. In my mind, the redesign is about defining the types of content the library has to offer its users and getting that content into pieces that can be reused and repurposed elsewhere. Whether this be the university website, school or college websites, or on the Internet at large.
Why is this more important to me than the end product of the new site the public sees? Because meeting your users where they are isn’t about making them come to the library website. In considering our long term virtual presence plans, the library website is a given. People who come to the site know we exist and want to use our services. To truly be successful we have to get our content into the path of the people who wouldn’t walk through our door (physical or virtual).
We couldn’t possibly begin to do this with our old site because of its static architecture. Long term I’d like a site which has a series of web services that can be exploited by my developers but also my the university web developers and who knows who else.
In the meantime, I’m dealing with fall out from the new site because it doesn’t look exactly the same to everyone. I’m not from the graphic design side of the fence of the web design world so I think that such expectations are unrealistic and ill advised. We can’t control what technology our users have. Trying to make a site that works equally well for everyone has two consequences:
- Huge amounts of resources are devoted to crafting multiple permutations that have to be maintained
- You end up with a mediocre site that no one hates or loves.
This isn’t saying you want a site that isn’t functional. However, if you have a site that is designed for 1024×768 it isn’t going to look “right” at 800×600. Issues of screen resolution are ones that drive me the most crazy because they can’t be scripted on the server side and you have to make a choice about what resolution you are designing for. With dynamic layouts sometimes things rescale nice and sometimes they don’t.
But let’s be honest some of these issues would be resolved if users had alternate ways of accessing our data. Does the typical mobile user want the library website or a specific piece of information or tool from the library site? If faculty could do their searches without coming to the library site would they? I think the answer is yes. Focusing on content rather than look and feel will allow us to provide these different types of services. It will also allow different types of users to potentially selectively access content.
For faculty and grad students who want to do known item searching in our catalog, maybe something like LibX is the way to go. Or maybe allowing users to create their own search interface to a set of particular resources that they can embed in their browsers search bar or on their desktop as a search widget.
Ultimately, I feel like it is these kinds of services that will make of break a library’s virtual presence not the library website. And with a limited staff, this means I like to choose carefully how much time I have my small staff spend on the tradition site. Otherwise, we could spend all our time caught up in look and not enough time working to make the library meet users where they are and be a seamless part of their work processes.