Monday, November 12, 2007

Never did talk to anyone about Google Books, but I did get a tour of the campus and ate some of the free food. A big thank-you to my sister, who works there and set up the tour for two out-of-town librarians. We were there when a bigwig guest came in and said, "I've heard about all the good work you do." to her. I was impressed.

I described some specifics of what we saw in my other blog. I've had some time to reflect on it some and will include the professional reflections here.

Everything that I saw seemed designed to address the individual needs of engineers and the company's need for collaborative work. People there use the adjective "Googly" to describe the creative, collaborative feel of the place. All the famous amenities and the flexibility of the work schedules allow people to be comfortable in their work, but they also keep people on campus, never too far from their work. When we were there, a trailer had been parked within the grounds offering "worksite haircuts". Eating, grooming, fitness, laundry services, self-improvement, even napping are all possible on site.

The work space - at least as I glimpsed it - seemed geared for collaboration. A recent New York Times article described the way ideas in this organization percolate upwards from formulation by individuals to elboration in "grouplets" to implementation. I could picture this taking place in an environment with few doors and lots of whiteboards and reminders above the urinals about transposing code from 32- to 64-bit environments.

"Does Google have a librarian?" I asked, and the answer was - not that either of the two employees I was with knew of. If there really is no such position, I told mayself, that's a hole in the organization. The more I tried to define the role of a librarian in such an environment, the more I puzzled at it, though.

I began with the visual image of all those thick code manuals. Surely, they aren't all online, are they? They should be maintained as a collection! But on the other hand, why would Google care about saving money that way? If an engineer needed a code manual he could just order it, right? Maybe if he or she had to go the library, check it out, and feel responsible for depriving others of it while he or she has it, that engineer would hesitate before using the reource and exploring the paths where it lead. Circulation controls are necessary in environments where physical items are scarce and relatively expensive.

OK, OK, maybe Google doesn't need a librarian for outside technical resources. Wouldn't they need a librarian to do knowledge management in-house? What happens to all the notes on projects in alpha or beta stages? Who keeps them, who has access to them? What keeps engineers on a new project from getting stumped on a problem engineers on a different problem have already solved? The record of the company's own efforts is a resource in itself. For all I know, however, Google has solved that problem by dumping all those records into one big data warehouse and making them searchable. It would be like a Google Desktop for internal use.

So I'm left with the idea that the support services - legal, financial, PR, etc might need librarians to research questions or check facts. Periodical and reference work collections would all be online. I don't know. I wonder how I would research this question.

Thursday, November 01, 2007

Day Three of Internet Librarian 2007

This final day of the convention was a less intense day for speeches and sessions. I spent more time talking with other librarians.

I did attend two sessions and enjoyed both. Darlene Fichter led off with a talk about mashups and data visualizations. In short, some wonderful graphic tools are at the disposal of librarians. Maps have lent themselves to use in mashups most of all so far, because the map data is freely available and the resulting information is so handy.

Steven Cohen followed with a tour of RSS-related tools. He demonstrated Google reader most of all, persuading me that I should give it a try again. Among other revelations was Tumblr, which brings together all your personal uploads and posts into one spot, and page2rss, which can make an rss feed out of a page that doesn't have one.

Lunch with librarians (mostly public) from Massachusetts, Kansas and Alabama. Dominant topic at my end of the table was reimagining the OPAC, followed by the need to keep pushing for change. Encouragement in that area came from the most experienced librarian at the table, who said that what one is told is possible will change if one can demonstrate sufficient need or opportunity, though it may take repeated demonstrations.

Off to Google on Nov. 1. I will have a chance to meet with an officer of Google Books. That service has more frustrations than rewards for me right now. Even as the database grows and results improve, I think it still needs improvements in the search engine. Maybe, on the other hand, I am expecting it to look too much like the OPAC I am familiar with and that the public loathe. Maybe keyword searching is enough just to get snippets of info out of a book whose formal subject heading may be about different matters altogether. But the weird thing is, they've started adding subject headings and acting in that respect like an OPAC. By that standard, Google Books is a poor OPAC.

Labels: ,