As I try to create a presentation that I hope will explain to my colleagues why we're moving onto a Drupal-based site, one of the things that I keep envisioning is the ways in which it can help us to (if we implement it as successfully as I hope we will) integrate our online environment. We no longer want the end-user to make their way through the fragmented, incoherent experience that our disparate online systems create. We want our users to have a sense of our library (which they arrive at via our organization's website) as the place where they can find x, y, and z. We don't want them to have to think about the fact that x came from our catalog, y came from our digital collections, and z came from a database that we'd created. Yes, we want them to be able to track down items in our physical collection, to link to images and documents from our collection that have been digitized, and to find information from that database. But no, we don't want them to have to know what the back-end looks like in order to get what they want.
Library WebHead is the blog of one librarian who focuses on web technologies (per a former colleague - a library "webhead"). In it, our webhead talks about the work she's doing with that library's website, which is, inevitably, a work in process! She also highlights some of the latest trends in web development and libraries. The views expressed here are the library webhead's only and do not necessarily represent those of her employer (or of any other organization or person).
Monday, October 26, 2009
What a tangled web we weave: integrating the web presence
As I try to create a presentation that I hope will explain to my colleagues why we're moving onto a Drupal-based site, one of the things that I keep envisioning is the ways in which it can help us to (if we implement it as successfully as I hope we will) integrate our online environment. We no longer want the end-user to make their way through the fragmented, incoherent experience that our disparate online systems create. We want our users to have a sense of our library (which they arrive at via our organization's website) as the place where they can find x, y, and z. We don't want them to have to think about the fact that x came from our catalog, y came from our digital collections, and z came from a database that we'd created. Yes, we want them to be able to track down items in our physical collection, to link to images and documents from our collection that have been digitized, and to find information from that database. But no, we don't want them to have to know what the back-end looks like in order to get what they want.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment