… meanwhile, the Code4Lib Journal has published its second issue and boy is it packed with articles; Eric Lease Morgan, Coordinating Editor of the issue, does a bang-up job on the introduction (though the title has effectively Bostonroll‘d me).

Each article in this issue has a little bit of something for all who call themselves a librarian or work in a library. Each identifies some sort of library problem to be addressed, and offers one or more solutions. Many are complete with code snippets. After all, this is Code4Lib.

For example, people in public service may be interested in Edward M. Corrado and Kathryn A. Frederick’s review of database-driven subject guide applications. Kenneth Furuta and Michele Potter describe a simple help system that brings librarians running to the reference desk. Margaret Mellinger and Kim Griggs explain how library resources can be organized into course pages without the need of HTML knowledge and yet sport Web 2.0 features. Nancy Fried Foster, Nora Dimmock, and Alison Bersani shed light on participatory design.

For those of us who enjoy cataloging and metadata issues, Jonathan Gorman outlines how he modified VUFind to exploit Wikipedia and cataloging authority records to enhance information about authors in a library catalog. Chris Freeland, Martin Kalfatovic, Jay Paige, and Marc Crozier illustrate a different use of Library of Congress Subject Headings by integrating place names with Google Maps. Carol Jean Godby, Devon Smith and Eric Childress describe a technique for crosswalking just about any metadata format into just about any other metadata format.

For the systems librarian in you, Dan Scott and Kevin Beswick share how they used Linux live CDs customized as kiosk browsers to provide laptops as ‘quick lookup’ stations at their library. Andrew Darby takes advantage of the Google Calendar API to easily manage the display of library hours. Jody DeRidder exploits Google sitemap technology and static HTML pages to make content in the “deep Web” more accessible. We hope you find these articles useful, stimulating, and relevant to your daily working lives.

I am ashamed to admit that I have not yet finished the first issue, so I now have pages upon pages to read. Ordinarily when I am behind on my reading I wind up letting bits fall by the wayside but the material largely looks too good to ignore.

Congratulations to Editorial Committees past and present and to the community on the whole!

Dorothea left a comment on a post announcing the publication of a little conference review some colleagues and I splurted out. In the announcement I lamented a bit about impact and she wisely suggested I consider depositing the review in a subject repository such as E-LIS.

We looked into our agreement with the publisher and it was actually quite permissive. (Way to go, Emerald.) And here’s the review in all its open access glory.

Thanks, Dorothea!

Antonio reports that our review of the 2007 Code4Lib conference has been published in volume 27, issue 6 of Library Hi Tech News.

Though these articles have very low impact, the more press code4lib gets, the better.

I proposed an NJ Library BarCamp some months ago, not realizing that efforts were already under way to do the same in NYC. In retrospect, I’m glad I didn’t do anything to get things moving; I wouldn’t have pulled things together nearly as well as the NYC folks did. The event was excellent. It was my first camp, and I’d definitely try another. A big thanks to Stephen Francoeur et al.

Here are the three sessions I attended, with links to the “official” wiki pages for summaries:

• Solr and Lucene (session moderated by AIP’s Mark Matienzo and NYU’s Jason Casden) seem to be gaining momentum in the library world. Having gone to the last Code4Lib conference, my head was already chock full of relevant tidbits, but the moderators did a great job of showing examples, evangelizing, and keeping the discussion going.
• Grid Services (session moderated by OCLC Openly Informatics’ Eric Hellman) might have been very interesting if I hadn’t kept receiving phone calls from an insurance company. I had to take the calls, and so this session was difficult to follow. The basic idea was to think of networked library services like the power grid. What would libraries want from the grid? What would they be willing to contribute back?
• Semantic Web (session moderated by NYU’s Corey Harper and CUNY’s Sunny Yoon) was the most widely attended session I went to: standing room only! When I first added the topic to the wiki, I had no idea it would draw this many people. Odd that I would suggest this topic since I had little to offer on the topic, so I gleaned an awful lot. The discussion was spirited and, as you might expect, the RDF vs. microformats arguments flew fast and furious across the room. I’m left wondering if the RDFa/GRRDL approach might not be a good middle-road between the “everything must be represented as RDF in a triplestore” camp and the “just embed microformats in xhtml” people.

And now, the requisite name-dropping. I got to reconnect with a bunch of people I hadn’t seen in a while, like Terry Catapano, Jay Datema, Nicole Engard, Valerie Forrestal, Kevin Reiss, and Sunny Yoon. And I got to meet LibLime’s Chris Cormack, NYPL’s Josh Greenberg, Corey Harper, Mark Matienzo, Jenkins Law’s RayAna Min Park, and Steven’s Tech’s Linda Scanlon, among other people.

It was about as good as any camp without kayaks and archery can be. Check out some more summaries.

1. Ruby

I gave a little talk on Ruby at today’s VALE-NJ Technology Awareness Group meeting, and so I’m using my slides to finally kick off this vaporseries.

[Slides are embedded as Flash here if you're reading in an aggregator.]

It seemed to be taken pretty well, though it could easily have been dismissed as the fanboyish ravings of a neophyte Rubyist. The folks from Rutgers were interested in having me come talk to their software architecture group, so it couldn’t have gone too badly, I suppose.

I need to stop cramming so much into presentations. Rambling about reflection and OO at a speed the Micro-Machines Guy would envy isn’t the best way to share enthusiasm about Ruby.

The rest of the meeting was interesting: Ron Jantz, the Digital Library Architect at Rutgers, posed a number of challenging questions about trust, authenticity, and reliability in the digital realm; Terry Catapano, Special Collections Analyst at Columbia, exposed the lack of data model inherent in many current metadata schemas and suggested ontologies as a potential direction; and Jeffery Triggs, Applications Programmer at Rutgers, demonstrated the Java DjVu Viewer Applet for displaying DjVu-based images outside the DjVu browser plug-in. Many good questions were asked, and new faces were in the crowd, so the future of TAG seems to be bright.

I’m hoping to follow up my Ruby talk with another on Rails. That was my initial goal for today, but there was far too much to cover, knowing the audience was relatively new to both technologies.

This is a slightly modified (read: rough) transcription of the talk I gave at this year’s NJLA conference, called “Library Revolution.”

The abstract described an idealistic scenario:

Imagine, if you will, a world where library services are automatically discovered; Library users retrieve information objects and metadata with a single click, never having to navigate the dark alleys of dead-ends that are full-text resolvers; Information sources and services are connected and remixed according to user preferences and needs, where and when they wish. What if we could leverage existing library and industry standards, applications, and protocols to make this a reality? And soon?

In this scenario, a potential library revolution could be fomented — in which the goal would be to return the means of production to users, to hand over the reins, to re-envision ourselves as tool- and service-building artisans, as Karen G. Schneider described in her keynote at the Code4Lib 2007 conference, rather than gatekeepers and information proxies — and I’m going to suggest some ways this might be achieved. For now I’ll assume it’s self-evident why it is desirable to, generally speaking, get “our stuff” “out there” and meet users at their points of need.

Rather than get into nitty-gritty details, I’d like to describe a higher-level vision which has been put forward by a host of library technologists that have come before me (especially Daniel Chudnov). Some aspects of my vision may indeed be pie-in-the-sky, but consider this:

1. Isn’t pie delicious?
2. Shouldn’t we reach for it?

So, what’s the problem? Why a revolution? Here are some (arguably trite) observations:

1. Full-text resolvers do not work well. You should not have to click through two, three, or four windows to get at full-text — assuming it’s actually there and not a complete dead end! Don’t get me wrong — it’s better to have access to full-text through a resolver than not to. I’d like to see more resolver systems that implement look-ahead resolution like Oregon State University’s new, and freely available, metasearch tool, LibraryFind. LF uses what Jeremy Frumkin, the Chair of Innovative Library Services at OSU, likes to call “two-click workflow”: one click to find, one click to get.
2. Information splatter. We’ve accumulated too many silos and need to figure out better ways to access all of that information via a single interface, whether the method is federation, aggregation, or something else. Users should not have to go to multiple sites to search our collections for resources of interest.
3. Sandboxing. Our content and services are, generally speaking, tightly coupled to our websites, so we are generally unable to meet users at their points of need.
4. Service usage — reference desk visits, OPAC searches — appears to be dwindling.
5. Growing popularity of Google, Amazon, and “web 2.0″ or social networking sites — del.icio.us, flickr, twitter, myspace, facebook, ning, librarything. These sites are great — especially MySpace, where I get all sorts of offers for new prescription drugs and live adult webcams. But these sites really -are- great. They empower users to connect with one another, to describe their own resources, to share with others, to remix information. And most of all? They’re incredibly easy to use. Are our tools as easy to use? Are we similarly empowering users?

An aside on “2.0″: Although I cringe at the viral “2.0″ meme — web 2.0, library 2.0, business 2.0, identity 2.0, enterprise 2.0, learning 2.0, travel 2.0… — it is interesting to note that there is something to “2.0″. Something revolutionary. And it’s not folksonomies, it’s not tagging, it’s not tag clouds, it’s not sharing, it’s not any particular site or idea. It is the very fabric of “2.0″, and that is a re-envisioning of the web from connecting people with data to connecting people with people. The web has evolved from a network of interlinked documents to an extension of the social fabric connecting us all.

As you can see, a revolution of sorts has already begun. Time magazine selected “You” as their 2006 person of the year. When MSNBC covered the story, the headline read “From blogs to YouTube, user-generated content transforms the Internet”. I’m personally not that interested in the social networking aspect, and it already receives a lot of coverage from the library 2.0 gang. Library 2.0 is a popular topic now, and much has been said of wikis, blogs, and RSS. These are important topics but others are already covering them quite well. The point to take away from 2.0, in my view, is that it’s empowering and inspiring users to do things with information they previously were not able or willing to do. Ask tens of millions of people to help us catalog MARC records? Right. But ask them to tag videos on YouTube, bands on Last.FM, images on Flickr, links on del.icio.us, and so forth? There you go. My areas of interest with regard to library revolution are unifying our content and services, getting them outside the library sandbox, and returning the means of production in this very “2.0″ way.

Let’s step through some technologies and technological concepts that may play a role in reaching this outcome.

• Systems integration: We have accumulated a wealth of resources over the years and have purchased, or built, or licensed, numerous systems to access these resources that have traditionally been disparate. This is a great accomplishment; the more information we can get into the hands of our users, the better. The process doesn’t scale, though, and has resulted in a proliferation of information silos. Because of thorny issues of interoperability, not to mention licensing issues, technological incompatibilities, and lack of resources, we have thus far struggled to bridge the gaps between these silos. The result? A number of different search interfaces, with different result sets, in different formats, supporting different depths of coverage.
   
   How can we reconcile in our users’ minds this information environment with the “simple, single search box” mentality of the Google age? What if we built bridges between our systems? Pull together metasearch with the link resolver, the link resolver with the catalog, the catalog with institutional repositories. Easy, right? Well, no. But at the very least, if you can get XML out of these systems — whether through OAI-PMH, or SRU, or a database export — you can bring it together. Index it with a tool like Solr, and you’ve got your Google-ish library search tool.
• Auto-discovery: Auto-discovery is used by a number of technologies, though perhaps its usage to announce syndication (RSS) feeds is the most well-known. The mechanism for syndication auto-discovery is actually quite simple. Got a feed for your site? Add a single line of HTML code to any page you’d like to announce it on, and modern web browsers will pick it up and clue you in.
   
   In HTML, there is a LINK tag, not to be confused with the A tag (which stands for anchor) commonly used for hyperlinks. The anchor and link tags differ in the following ways:
  • Anchor tags may have text content and show up as labels for links. For instance, you might link to FoxNews.com and label it “Fair and balanced? Yeah right.” LINK tags do not have text content.
  • Actionability: Anchor tags are clickable. They take you someplace. LINK tags are not clickable.
  • Context: Anchor tags appear in the body of a document. LINK tags appear in the HEAD.
  • Semantics: Anchor tags may represent any number of things. It might be a link to content further down in the current page, it might link to another page entirely, or it might even be used to activate some javascript or launch a popup window. LINK tags are used solely to describe document relationships, more semantic information. For instance, a LINK tag might describe a link to the next and previous chapters in an e-book, a LINK tag might be used to link to alternative representations of a document, such as versions in other languages, or versions formatted in RSS or the Atom syndication format. The LINK tag is a great way to leverage the existing web architecture to handle the problem of “one resource, many representations”, and I wouldn’t be surprised if the OAI-Object Reuse and Exchange initiative took a hard look at it.

  The LINK tag sort of auto-discovery, such as for syndication feeds, is common, but is not the only implementation of auto-discovery. There are more sophisticated ways, such as Zero Configuration Networking.

• Syndication: You’ve probably heard a lot about RSS, or Really Simple Syndication, and I wouldn’t be surprised if most of you are already using it. It’s a great technology, simple to use and implement, and I know it saves me a great deal of time on a daily basis. Instead of having to click through and browse the 50 or so websites I track regularly, I read updated content from each site in my feed aggregator in a unified interface. A lot of attention is already paid to RSS, especially in library 2.0 circles, so I won’t say much more about it. Syndication allows content to be syndicated into feeds that folks can subscribe to and unsubscribe from willy-nilly.
   
   But I thought it was important to include an explicit mention of syndication since a couple of the other topics relate to it, and since it is a great example of getting stuff out there. Rather than requiring your audience to come to your website, syndication enables them to read your content in an environment of their choosing. It’s worth noting that my wife is not a fan of syndication. She likes the experience of going to different websites, enjoying their different takes on web design, and compartmentalizing her web surfing. And that’s great; no one, to the best of my knowledge, has advocated an “RSS-only” interface. Content available in the RSS format is also available otherwise, so it is a convenient option for people like myself.
   
   One more point about RSS, despite saying I wouldn’t talk much about it. It’s kind of an academic point, but I feel it warrants some clarification. The term RSS has quickly become the Band-Aid, or the Kleenex, of syndication feeds. RSS is one of a number of formats used for marking up syndication feeds. Another is the Atom Syndication Format. Most browser and feed aggregators are fully aware of both feed types — for instance, Bloglines has supported both formats since June of 2006 — and they generally should render the same, and that’s why you don’t hear about Atom much; it’s a detail that is, for the most part, behind the scenes.
• OpenSearch: Does anyone here have a website or a catalog? Do they have search interfaces? Perfect, you’re about a third of the way there. OpenSearch is a specification for some simple formats that allow you to share search results. Just as syndication allows you to decouple your content from your website, OpenSearch allows you to decouple your search engines from your websites. Here’s how it works:
  1. Go to your search page and look at the URL after you run a search
  2. Write an OpenSearch description document
  3. Embed a LINK tag linking to the OpenSearch description document, for auto-discovery
  4. Return search results in RSS or Atom

  You might ask “why bother?” Firstly, the newest browsers — FF2 and IE7, among others — support auto-discovery of OpenSearch targets. So folks can search Google, Wikipedia, Amazon, eBay … and your websites or catalogs directly from their browser. Secondly, it allows for fairly simple federation of searches across OpenSearch targets. Since each target contains a description document that is machine-readable, I can point my OpenSearch client at a number of targets, find their descriptions, and learn how to search them. Results are, by convention, returned in RSS or Atom, which are easily crosswalkable, so aggregating result sets is fairly trivial (though how to sort or rank them is tricky). Thirdly, since results are returned as RSS or Atom, one can in effect subscribe to search results. For example, you could subscribe to a search on Wikipedia for “Anarcho-Syndicalism”, and your feed aggregator will be alerted whenever that search returns new results. Or, a Linguistics professor could subscribe to your catalog’s OpenSearch target, hoping to be alerted when new materials about Germanic syntax are cataloged — and it’s worth noting, this is as easy as just two or three clicks in a web browser.

• unAPI: Numerous tools and protocols exist for integrating library resources into other information systems, library or otherwise. OAI-PMH and OpenURL are two great examples of successful and widely deployed technologies. Unfortunately, few developers outside the relatively small world of library technology know anything about library standards, and this is seen as a significant integration barrier. Dan Chudnov, a librarian programmer at LC, reflected on this: ‘we librarians and those of us librarians who write standards tend, in writing our standards, to “make complex things possible, and make simple things complex.”‘
   
   To address this issue, a number of librarians and technologists came together to develop a new standard called unAPI. unAPI is a tiny web-based specification designed to solve the problem of identifying, copying, and pasting discrete content objects to and from web applications (including catalogs, bibliographic databases, repositories, link resolvers, and so forth), making it simpler for developers outside the library world to get at our vast intellectual resources. The objective of unAPI, then, is to enable web sites with HTML interfaces to information-rich objects to simultaneously publish richly structured metadata for those objects, or those objects themselves, in a predictable and consistent way for machine processing.
   
   unAPI consists of three parts: A microformat for embedding object identifiers in HTML, an HTML LINK tag for unAPI service auto-discovery (as used for RSS, Atom, and OpenSearch), and a web service consisting of three functions–get formats , get formats for x identifier , get format y of identifier x — two of which have a standardized response format, returning XML.
• ZeroConf: I want to acknowledge Dan Chudnov again, for suggesting that Zero Configuration Networking might have a place in library services. The general question here is “why can’t library tools be as cool as iTunes is?” Just waltz into Starbucks, connect to the wi-fi, and you can see everyone else’s playlist. You can listen to their music, even. What sort of magic made this sort of auto-discovery “just work?”
   
   The technology is called Zero Configuration Networking, or ZeroConf, though you may see older mentions under the names Rendezvous and Bonjour. Without getting into the hairy details, ZeroConf is a small stack of fairly low-level technologies that piggy-back on the ubiquitous domain name system (or DNS), which enables us to type identifiers like “google.com” and “nytimes.com” into a web browser and rest assured that our computers will take care of the rest for us — looking up the domain name, finding the network address of the server, connecting to the server on an appropriate port, and so forth. ZeroConf allows machines to connect to networks without any knowledge of what’s already on the network, without regard for the type of network topology or infrastructure, and both register the services it provides and query the services already provided by other nodes on the network. It sounds complicated, but everytime you walk into Starbucks and start up iTunes, it seems pretty trivial. It “just works.”
   
   Wouldn’t it be great if users could discover our services and resources that easily? What if we went through with systems integration and announced that unified service via ZeroConf? A visiting scholar could enter our library, connect her machine to the network — and let’s forget about authentication and authorization for now — and immediately find our new service, from which she could run a simple search against all of our bibliographic databases, all of our catalog records, all of our full-text holdings, and all of our repository objects. What if library services “just worked”?Significant work needs to be done in this area before it becomes viable as I’ve just described, but I find it to be a compelling vision.

The technology as is widely acknowledged is the easy part. So how do we get there? How do we re-envision ourselves as library artisans? How do we craft services that “just work?” How can we investigate all these technologies that let us unleash our considerable assets?

1. Commitment to innovation. If you can afford to have skunkworks in your organization, even if it’s only one employee, or allowing a couple of creative individuals to devote 10% of their time to innovative pursuits, it’s worth it.
2. Bold direction.
3. Think outside the orgchart — leverage collaborative development, forge communities, make the most of your consortial ties.
4. … You tell me.

We can yield revolutionary results via small steps and a bold, forward-thinking direction. Pie in the sky? Maybe, but isn’t pie delicious? (Yes, that was a glib and abrupt ending, but I’m tired of editing.)

Maybe I’m late to the party — nods to John Blyberg and Rob Styles — but damn(!), does Microsoft have some exciting visualization projects or what?

John and Rob wrote about Microsoft Surface, a hardware/software combination that allows for tactile manipulation of data. In Microsoft’s own words:

Microsoft Surface represents a fundamental change in the way we interact with digital content.

With Surface, we can actually grab data with our hands, and move information between objects with natural gestures and touch.

Surface features a 30-inch tabletop display whose unique abilities allow for several people to work independently or simultaneously. All with out using a mouse or a keyboard.

Don’t take my word for it; go watch a demonstration video and be amazed.

But wait, open the video in another window, and keep reading before you lose interest in my uninteresting prose.

I noticed among the recently released TED talks a brilliant short presentation by Microsoft’s Blaise Aguera y Arcas on their Photosynth project. My first impression was just the visual joy of the photo browse / pan / zoom interface. It’s impressive in its own right. But what really tickles me about Photosynth is that it “takes a large collection of photos of a place or an object, analyzes them for similarities, and displays them in a reconstructed three-dimensional space.”

For example, throw it at http://www.flickr.com/photos/tags/seattlepubliclibrary/ and it will construct a collage-like view of the Seattle Public Library. Zoom in and you’ll see images at that level of zoom. Pan in three dimensions and (assuming there are enough photos to support the various views) you can virtually be in front of SPL. See for yourself:

Imagine browsing the stacks with this thing. Imagine finding a book on the stacks and being able to hook directly into its full-text. Super cool!

Microsoft Surface is tentatively planned for a November release, which will be targeted for “retail and entertainment settings”. It could be available to the public in a few years’ time though it will likely cost a few times more than an average PC. [Gleaned from a Seattle PI article.] Photosynth is also not available yet, but you can track its progress on the Photosynth team blog. (Yes, there’s a feed.)

[Disclosure: I lived in the shadow of Redmond not long ago, though I was not employed by Microsoft. I probably invest in Microsoft indirectly, but I haven't scoured my portfolio distributions in a while.]

I kicked around the idea of having a Library Camp NJ a few months ago. Response wasn’t fantastic but, then again, I didn’t try very hard to spread the word, and perhaps I am not the best champion for the cause. In the meantime, Baruch College in Manhattan will be sponsoring Library Camp NYC this August.

I certainly plan on attending if I can get approval to take that day off and may even be talking about this or that if I can come up with an appropriate topic — Ruby on Rails might be too narrow or technical. Those of you who are relatively local to NYC should read more about it and consider coming.

What is a “Library Camp?”

The first Library Camp was held at the Ann Arbor District Library in Ann Arbor, Michigan in April 2006 as an “unconference” to talk about opportunities and challenges regarding Library 2.0. It was organized by John Blyberg, and went over so well a Library Camp East was held in September 2006 at the Darien Public Library (CT) with about 50 attendees (organized by Alan Gray).

So what’s an unconference? Unlike a traditional conference, where people have to pay registration fees to sit in an auditorium and listen to someone read off PowerPoint slides, there are no registration fees and everyone is a active participant. Whoever shows up are the right people for an unconference. The discussion topics are decided by the participants when they arrive, as well as topics that are brought to the forefront during discussions that are deemed as particularly important and are thought to be worthy enough by members of the discussion groups to have these topics break off into their own core discussion groups. The format has gained popularity in the technology field in recent years, because it promotes collaboration and engagement.

I’m at the NJLA 2007 conference today talking about technology. I’m using this post to demonstrate RSS, OpenSearch, unAPI, and auto-discovery.

I usually travel by ground-based transportation — train when I can, bus when I must — because I hate flying. There is something about this sort of travel that makes folks more sociable in my experience. Frequently a question that I have come to dread is asked: “So, what do you do?”

Mumbling about libraries and technology is typically enough to bring about the initial stages of Ophthalmus Vitriatus: yes, the dreaded eye glaze (in faux Latin for pretentiousness points). The best reaction I can hope for is “oh, yeah, seems like a really useful job nowadays what with all that information going online.” Not a bad reaction, all in all. True for sure. But I wish I could succinctly express what I do without sounding overly general (”I’m a programmer and librarian”), or grandiose (”I am attempting to organize, disseminate, and preserve all the information in the world”).

I’m sure this is a problem with my own attempts at expression rather than a problem with our vocation. So I’m putting this question out there:

Assume you’re talking to someone who knows almost nothing of libraries and technology, how do you explain, in a quick-and-appropriate-on-a-bus-or-train sort of way, what you do for a living?

I’m guessing that snappy Rails app I’ve been working on for management of persistent identifiers is not very interesting to these folks.

What brought this about was my recent trek down to the Code4Lib conference in Athens, GA, which I must say is beautiful this time of year. Now if I can only convince myself that there won’t be snow to shovel at home, maybe I’ll work up the courage to step back on the train. By any road, I’m really looking forward to the next three days. The conference program looks awesome, and last year’s really set the bar high.

Oh yes, Anjanette Young (Systems Librarian at the University of Washington) and I found a cafe/pub in the College Ave. / Broad St. area that has happy hour from 4pm-9pm. This may very well be the death of me.

The title of this post has been brought to you by the Society for Meatwad Quotations™. Those of you who get the reference may be mildly amused. Those who don’t, clearly lead sad and empty lives.