The 2.0 world -- in libraries in particular, or the web in general -- is helping to address the information management problem of ambiguity. In his inaugural column in the May issue of KMWorld," Now, everything is fragmented," David Snowden notes: "The more you structure material, the more you summarize (either as an editor or using technology), the more you make material specific to a context or time, the less utility that material has as things change..."

Much of what the knowledge management world, and, for that matter, librarians more broadly, seek to accomplish is to get the right bit of information to the person who is looking for it at the right time. However, as we build systems to accomplish that task, we often run counter to both the defining characteristic of our age and what he describes as one of the defining characteristics of our species. Snowden writes:

First, we live in a world subject to constant change, and it’s better to blend fragments at the time of need than attempt to anticipate all needs. We are moving from attempting to anticipate the future to creating an attitude and capability of anticipatory awareness. Second, we are homo sapiens at least in part because we were first homo narrans: the storytelling ape. Dealing with anecdotal material from multiple sources and creating our own stories in turn has been a critical part of our evolutionary development.

Information systems are typically built to remove ambiguity. They are tailored to the specific need at hand. Snowden notes that there is a risk to building systems that remove ambiguity by "chunking" information into discrete elements. This risk is shown through research (in national security, in particular) that indicates raw intelligence is more useful over longer periods of time than the reports based on that raw data. 2.0 environments, in which users of information build on the raw materials, mixing and matching sources in novel ways, are more flexible, allowing for changing needs to reflect themselves over time.

A mentor and twice-supervisor of mine described someone's ability to survive in an organization by saying that the individual either had or lacked a "high tolerance for ambiguity." Having a high tolerance was a good thing: if you could keep your relative sanity as organizational priorities and day-to-day exigencies changed, you were in good shape. As librarians, we need to develop a high tolerance for ambiguity in the information systems we design and provide. By this, I don't mean developing to wishy-washy specifications. I do mean that we need to build systems that enable our users to pursue information-seeking paths we don't, or can't, anticipate. Systems must be built to allow others to get to the raw data, manipulate it, and do what they will. As we today's information needs, we must also allow for flexible interpretation and serendipity of discovery.

Melissa Cheater at the Academica blog compiled a survey of institutions of higher education with a presence Facebook and published a post titled "How higher ed is using Facebook Pages."

She found more than 420 IHE-related Facebook Pages. It is interesting to note that Facebook does not provide a standard way to identify authorship -- so she was unable to determine who published the page: the school, a staff or faculty member, or someone who thought there should be one? This poses an interesting question of "authority" -- how reliable are Facebook Pages as sites of valid and trusted information?

The full post is worth a read.

Tagging systems offer a fascinating opportunity to study how people tag and what collective wisdom can be generated from the masses. Tim Spalding, in his a recent post at Thingology, The Long Tail of Ann Coulter, observes that tag use in LibraryThing resembles the Long Tail principle. That is, a few tags are used a great deal to describe a given item, while other tags are used just once. These singleton tags reflect the idiosyncratic nature of individual taggers.

I've been thinking about the value of these singleton tags, without conclusive results, in connection with MTagger, the tagging application we built at the University of Michigan library. With the 8.5 million items in the library catalog, or even the 55,000 web pages on our site, will enough tags ever be applied to enough items to make it a useful mode for a newcomer to find an individual item, or are they just an aide-memoire for the person who applied them? In other words, do tags way off in the Long Tail matter?

The more I've pondered this, the more I realize that it's not an either-or question. Tagging, at least in the library environment, is most valuable as a personal collection tool. It offers a way for library users to bring together things that seem similar to them for their own purposes. The real value of tagging is like that of a library: it's the collections, the constructed universe of things that someone (a librarian, a subject expert, a user) brought together. While my tags may prove of no value to anyone else in finding a particular item, the mass of items I've used that idiosyncratic tag on may very well guide a future user in resource discovery.

Copyright and fair use are poorly understood in the population at large (just ask high school teachers or college professors how much time they spend vetting submitted papers for flagrant -- let alone subtle -- plagiarism). However, syndication technologies such as RSS and Atom make it so easy to repurpose works that what's proper -- morally or legally -- is often overlooked. After all, feeds are purpose built to make content portable. If the author did not want others to copy the content, the author would not send it out in a format designed for its simple syndication.

The Australian magazine PC World runs an interesting article by Larry Borsato: "Who owns 'public' content? RSS feed ownership brought into question." In the article, Borsato recounts a recent incident in which a commercial entity reproduced, in toto, his blog posts via RSS on its web site. While Borsato has a Creative Commons non-commercial attribution license, he felt the commercial entity had violated it; they were, after all, a commercial entity. While the question was resolved amicably, it highlights, once again, the difference between how copyright is frequently viewed in the syndicated environment from how it is often seen in the print world. Borsato concludes:

Like many other facets of life in the Internet age, technological possibility is outstripping common practice -- and often outstripping common sense. Some of this particular misconception, about what can legitimately be done with online content, can be cleared up through experience and training. Some of it will inevitably be resolved through better technological solutions. But when it comes down to it, we as bloggers must take greater responsibility for tracking how our content is used.

Apple's iPhone and iPod Touch allow users to save "web clips" -- favorite web pages -- directly to the device's home screen -- so one tap of the finger on the icon takes you directly to that site. By default, the iPhone or iPod Touch use a nearly-impossible-to-read screen shot to represent the web clip; few web sites end up being visually identifiable on the home screen.

There's a great opportunity for branding here. Apple has made it very easy to create custom icons for your web site. There are 2 steps:

1. Make a graphic that is 57 x 57 pixels and save it in PNG format.


2. Name this file apple-touch-icon.png and save it to the main ("root") level of your web server.

(Credit to The Primary Vivid Weblog for documenting the process in plain English.)

When you add a web clip to your iPhone or iPod Touch's home screen, it automatically (and unavoidably) adds a glow effect and rounded corners to the graphic you provide. To compensate for this, use this web clip Photoshop template (from iPhoneMinds) that shows just where the usable space in that 57 x 57 pixel square is and how it will look with the glow effect.

How easy is it? It took me (a truly novice Photoshop user) about 5 minutes to make an icon for RSS4Lib -- if you're using an iPhone or iPod Touch, save this page to your home screen to see it, or just view http://www.rss4lib.com/apple-touch-icon.png.

If your library has iPhone or iPod Touch users, why not extend your brand to their mobile desktop?