$node.absurl

$node.contribution("Title")

$node.absurl


What Does Google Know That We Don’t?


Joseph Janes

By Joseph Janes
American Libraries Columnist 

Assistant Professor, Information School, University of Washington.
intlib@ischool.washington.edu

Column for September 2005


I’m not sure I’ve ever asked a question at a panel session that led to a 30-minute answer.

This is my ALA conference story for the year. Those of you who didn’t make the trek to Chicago missed out on the spectacle of 20,000 glistening librarians flinging themselves back and forth to Indiana, which is where I swear the convention center is located. Chicago is one of my favorite cities, though, and everybody I talked to had a great time. Here’s a suggestion for next year—how about a conflict-free time for the precision book cart drill team competition (AL, Aug., p. 63)? I missed it!

Anyway, I wasn’t making mischief with the question, I promise. It was at the Reference and User Services Association President’s Program, which had such an enticing panel—folks from Gale, LC, and Xrefer, as well as a VP from Google and Wikipedia founder Jimmy Wales. Quite the crowd.

Tiers of answers

The discussion centered on the future of reference publishing, access, and so on. It was going well when a question drifted across my consciousness: Google and Wikipedia are both so popular and so widely used, and they get so much buzz and attention, they must be on to something. So I asked: What do Google and Wikipedia know that we in the library world don’t?

It kinda silenced the room there for a second, then the answers came. First the ones you’d probably expect: Those tools are fast; they’re comprehensive (or at least seem to be); and they cover almost anything you want to ask for.

Then came somewhat deeper and more subtle answers as people gave this more thought. (I wouldn’t even dignify what follows by labeling them paraphrases; my apologies to everyone involved—I’m sure I only got a fraction of what was said and missed attributions, and thus I’m doing a disservice to some pretty keen people.)

Individuals are now able to switch gears and morph interests very quickly, and systems such as Google and Wikipedia permit, even foster, that kind of investigation. Want to search for Robespierre’s first name? Google it. Details on the Order of Canada? Wikipedia’s got it. Probably takes you 45 seconds for either of these, if that, and that kind of speed and flexibility feeds seamlessly into a more scattershot society and culture. And while the results of those efforts might be less authoritative than, say, equivalent uses of Britannica, for a lot of people in a lot of situations they’re just fine.

Then there’s the personal, affective side. Google’s just fun and easy; and since the Wikipedia is exclusively the product of the people who use and contribute to it, it also gives them the sense of ownership and perhaps even of belonging. Throw in a disregard for containers qua containers, so everything appears easy and simple and clean to use and understand.

It wasn’t until Amazon had offered book-cover images for a while that they started to appear in library catalogs; and our catalogs and finding tools are still unforgiving of spelling and typographical errors, for logical and sometimes reasonable reasons. I don’t mean to suggest that we have to ape the latest internet flavor of the month; to be honest, we couldn’t even if we wanted to.

Lessons learned

Google and Wikipedia, and their kin, have clearly learned valuable lessons from librarianship. The early search-engine developers did their homework in reading the research literature on information retrieval; and it is, after all, called the Wikipedia for a reason, deriving at least some of its interest and allure from the traditional notions of encyclopedias.

Now it’s our turn again. What can we learn from them? What features, ideas, and—perhaps more importantly—attitudes can we take and incorporate into librarianship to provide better and more valued services to our communities? Can we make our services and tools more flexible? More personable? More fun? And yet still make sure they are high quality services we’re proud to be associated with, beyond just “good enough”? I sure hope so, because that sounds like a winning combination to me.

The Wikipedia is emblematic of another interesting phenomenon: the seemingly familiar resource that holds with a very different notion of accuracy and authority than we’re accustomed to. What lessons lurk here that we should attend to and perhaps draw from? That’s another story . . . for next month!