library20

In recognition of the divisive and increasingly meaningless nature of x.0 monikers — think library 2.0 and the web 2.0 that inspired it — I’m doing away with them.

When Jeffrey Zeldman speaks with disdain about the AJAX happy nouveaux web application designers and the second internet bubble (and he’s not entirely off-base) and starts claiming he’s moving to Web 3.0, then it’s a pretty clear sign that we should give up on trying to version all this.

Don’t get me wrong, there’s something big going on, but it doesn’t respect version numbers and it isn’t about AJAX or social software. And as much as designers and developers want to take credit, we cant. I’m not the first to say it, but let me repeat it without the baggage of these x.0 monikers: people are making the internet a part of their daily lives and in doing so it is changing us. With or without a label, that’s what we need to talk about.

You don’t like the “2.0” moniker? So what. John Blyberg reminds us that “if we’re arguing over semantics, we’ve been derailed.” And Stephen Abram is said to have cautioned us: “when librarians study something to death, we forget that death was not the original goal.”

I hadn’t seen Ryan Eby’s post at LibDev that connected ILSs with WordPress before I posted that library catalogs should be like WordPress here. It connects with a my comment on a post at Meredith Farkas’ Information Wants To Be Free. My comment there goes in two directions, but I’d like to focus on the technology side now.

Our vendors will inevitably bend to our demands and add small features here and there, but even after that, we’ll still be stuck paying enormous amounts of money for systems that remain fundamentally flawed. Technology marches on, and inevitably we’ll find some new way to use our catalog data. John Blyberg is talking about this in his ILS customer bill of rights post, and that’s what I was getting at when I say the catalog should be like WordPress.

Meredith asks for more programmers, but as a programmer, I’m asking for her help in demanding smart software design from our vendors.

Library catalogs should be be like WordPress. That is, every entry should support comments, trackbacks, and pingbacks. Every record should have a permalink. Content should be tag-able. The look should be easily customizable with themes. Everything should be available via RSS or Atom. It should be extendable with a rich plugin API. And when that fails, it would be nice if it were all written in a convenient language like PHP so we can hack it ourselves.