No, I’m not talking about the interface our users see in the web browser — there’s enough argument about that — I’m talking about web services, the technologies that form much of the infrastructure for Web 2.0.

Once upon a time, the technology that displayed a set of data, let’s say catalog records, was inextricably linked to the technology that stored that set of data. As we started to fill our data repositories, we found it usefull to import (and export) the data so that we could benefit from the work others had done and share our contributions with others. These processes were manual, or at least actively managed, and they depended on the notion that we had to have that information in our servers to be used by and displayed for our users.

Then technology evolved. Many applications now separate the components that store and manage the information from the components that display and manipulate it, and a few applications open up their data stores to the public via web services-based APIs. This is the concept that makes HousingMaps, ChicagoCrime, and Flickr Colr Pickr, among so many others, work.

Think about this for a moment: Our ILSs are inventory management systems, but our OPACs are (supposed to be) search and retrieval systems. The difference is obvious from here, but our vendors continue to operate as though you can’t have one without the other.

It might be easier to illustrate this point with an example or two.

Amazon Light is one of hundreds of applications based on Amazon’s web services. It connects Amazon’s inventory system with a custom built search and retrieval system, and it works. The Amazon Lite developers at Kokogiak didn’t need to build the inventory system, they only needed to think about ways to make the Amazon inventory more useful to you. Try it out, you might like the ability to search your local library (via some real hacks) or bookmark things via del.icio.us.

Or, you might not. Because Amazon allows anybody to access their catalog data, everybody has the opportunity to build a better, more usable catalog — or any other application that can benefit from the bibliographic details in it.

Take LibraryThing for example. It’s hard to explain what it is about people who read books that makes them want to list the books they own or have read or are interested in reading, but LibraryThing doesn’t worry about the why. It just answers the need. And because listing books, at least making a detailed list of books, can be time consuming, LibraryThing makes it easier by fetching the full details and book jacket from Amazon’s catalog. LibraryThing doesn’t need to “own” that info, it just needs access to it.

And what’s interesting is that LibraryThing is only one of a number of similar applications. Take a look at AllConsuming, Technorati’s popular books, and listal. These services connect Amazon’s catalog data with other data gathered from users or from web crawls, then they share the results. Here’s Ryan Eby’s lists of owned and wanted books, and here they are in RSS. Why RSS? Take a look at how he’s using the listal feed for his current reading list in his blog (lower-right column).

These are not technology demos. These are real applications. They are examples of how the world changes when you open up access to your catalog data. It’s what happens when we realize that the tools that store and manage our information are separate from the tools that display and manipulate that information.

Obviously, I’m about to make the (now-old) argument that we need to open our OPACs like this, but we also need take the lesson that easy and loose is winning over detailed and difficult — even in XML representations of our catalog data. And after looking at all that’s been done so far, I want to ask: why not adopt Amazon’s web services XML schema?

Is it so bad that it was invented elsewhere? Is it a bad thing that there are perhaps hundreds of applications that are already using data in that format?

Maybe the answer to those questions is yes, but here’s where technology can serve us again: we don’t have to choose. We don’t need to bet on one technology while we watch others progress faster. Our systems can output the same catalog data in any number of different ways. RSS, OpenSearch, MARC-XML, ATOM, EAD, or DC are all possible, easy in fact — if the inventory server architecture is open enough to allow it.

What do I really mean when I say library web services should be like Amazon web services? I mean they should be that accessible, that usable, that hackable. I mean libraries will benefit when people we’ve never met are spending their evenings building new applications to use our data. People are wondering how to get more programmers in libraries (example one, two), but I’m wondering how to make library systems more programmer friendly.

Fired up? Read more with my library catalogs should be like WordPress post, John Blyberg’s ILS customer bill of rights, and Ryan Eby’s open vs. turnkey discussion.

tags: amazon, amazon api, amazon web services, api, dublin core, ead, libraries, library, library catalog, marc, marc-xml, opac data, opensearch, web 2.0, web service, web services, web20, webservice, webservices, xml, xml server

I can’t explain why, at least not yet, but I’m looking for a way to search the iTunes Music Store catalog outside of iTunes. Rumors of an iTunes-Google partnership have been flying lately, but what I really want is a webservice/API I can use. Yes, Apple offers an affiliate program that supports direct links, but again, they don’t offer an Amazon-style API to search their catalog.

All of this has me thinking about reverse-engineering the iTMS to build the webservice I’m looking for. DVD Jon made news not so long ago with PyMusique, now rewritten as SharpMusique, but even before that, Jason Rohrer released iTMS-4-all.

Rohrer’s work is more in line with what I’m trying to do, so I’m exploring that concept a little. iTMS-4-all is a simple web browsing interface to the store. Jean-Yves Stervinou explains:

iTunes 4 is a beautiful example of a “specialized browser”. It uses html to render pages with texts and pictures, but it also uses macosX standard GUI elements when appropriate. When you browse the albums/artists, iTunes in fact gets the contents of these lists from a Web server out there at Apple (phobos is its nickname). The format for these lists is XML [...]. iTunes reads this XML list then uses a standard list browser to show you the content.

Stervinou describes the entire iTunes store as a REST webservice, but one which Apple has chosen to keep private. Rohrer describes the problems of interacting with the ITMS encrypted content. He (and contributors) were successful, but Apple changed the encryption after iTunes 4.7 was released. It didn’t take long for DVD Jon to get around the change, but it (or something else, I haven’t looked yet) has disabled iTMS-4-all. Too bad, too, because there’s a lot we might be able to do with such a webservice. DownhillBattle.org contemplates some of these uses in their iTMS-4-all announcement (Jason Rohrer is somehow involved with Downhill Battle).

More reading: Free Software Magazine did some poking at iTunes, The g4tv Screensavers crew looks into iTunes Hackery, Apple does offer a very limited iTunes RSS feed generator, XMLHead looks at the structure of iTunes affiliate links, and (update) here’s some talk about the iTMS XML interface before they started encrypting it.

tags: itms, itms-4-all, itunes, itunes music store, itunes music store api, music store, music store api, pymuscique, webservice, webservices, xml

I want Wikipedia to have an API, but it doesn’t. Some web searching turned up Gina Trapani’s WikipedizeText, but that still wasn’t exactly what I wanted. A note in the source code, however, put me back on the trail to the Wikipedia database downloads, and while that’s not what I want, I did learn that they’ve got a table of just the article titles (over 1.2 million of them) in their downloads.

Some of this is related to my interest in making Wikipedia work better in an academic library context, but I’ve got other plans too. With luck, we’ll see a beta release this week.

tags: api, application programming interface, article titles, database download, free encyclopedia, hacking, rss, web services, webservices, wikipedia, xml