Richard Akerman’s recent post highlighting SOA resources at Educause reminded me about the . I’m assuming significant number of those interested in applying SOA to library systems are at an institution of higher education or in some related organization, so I’m adding the RSS feed for that aggregation to Planet LibrarySOA. This will undoubtedly result in a large spike of “new” postings to the planet aggregator, but should settle down after that.
Back in June, Eric Schnell posted a five part introduction to applying Service-Oriented Architecture (SOA) concepts to library applications. Along with his comparison of the predominant ILS architecture with Henry Ford’s application of assembly line manufacturing this is a great non-techie introduction to SOA form a library application perspective. I had reason to run across these again earlier this month and remembered that I had not posted a summary and pointers here.
I am pleased to announce the formation of Planet Library SOA — an aggregation of blog postings and resources related to the application of the Service-Oriented Architecture (SOA) software paradigm to library systems. You can follow the topic by reading the aggregation website, but the best way to follow along is by subscribing to one of the feeds (atom, rss1.0 or rss2.0) in your favorite newsreader. Those in the conversation at the beginning are Eric Schnell, Lorcan Dempsey, Richard Akerman, Stephen Anthony, and the Talis corporate blog. If you are looking for an introduction to the SOA topic with a slant towards library services, I humbly suggest you read my series on DLTJ starting with Defining “Service Oriented Architecture” by Analogy.
This month I’ve come across one great article and one great report on Service Oriented Architectures. The first came from Sally Rogers at Ohio State University in the form of an article from CIO magazine last year:
Koch, Christopher. 2006. The Truth About SOA. CIO Magazine, June 15. http://www.cio.com/archive/061506/soa.html (accessed March 27, 2007).
This article does a great job at laying the groundwork for the broad “what” and “why” (as well as the “why not”) of SOA, and I agree with Sally that it makes a better introduction to the topic than most of the white paper that I presented at the meeting. The two best paragraphs out of the article come towards the very end:
This is part three of a continuing series on the application of the Service Oriented Architecture (SOA) design pattern to library systems. In the first part, the SOA concept was compared to a transportation network and the basic foundation for defining SOA was set down. The second part described what a “service” in SOA could be and proposed an example using OCLC’s WorldCat interface with item status information being pulled from a library catalog system. That part also left off with a teaser about the juxtaposition of “inventory control system” with “local catalog system” — a foreshadowing of the topic of this post: what to do about the Monolithic (er… “Integrated”) Library System.
This post is the second in a series about the application of the Service Oriented Architecture (SOA) system design pattern to library services. The first post in this series focused on defining “Service Oriented Architecture” using the analogy of a transportation network. This post goes into some detail about what makes a “service” in this architecture and offers an example using a hypothetical use case: a union library catalog (Open WorldCat) making a statement about the availability of a book.
This post is the first in a series over the next few days that in total will attempt to lay the groundwork for a discussion of applying the Service Oriented Architecture (or SOA) software design pattern to systems and solutions in the library space. It starts with comparing the SOA concept with a multi-modal transportation network. Subsequent posts will outline use cases and describe how SOA can be applied to libraries.
I’ve been tasked to write a whitepaper envisioning a Service Oriented Architecture for OhioLINK’s services and operations. I’ve found a bit of information through my own networking and searching, but in putting out this list and asking for additions I want to be sure that I’m not already missing the holy grail of documents that I could just rebrand as an OhioLINK document. (With appropriate permission, of course.) I’m looking for strategic/explanatory documents over technical documents, although the latter will undoubtedly be useful in later iterations and derivatives of the whitepaper.
CDL Common Framework
FEDORA Workflow Working Group Meeting
18-Jun-2006, University of Virginia
Attending: Grace Agnew, Rutgers U.; Chris Awre, U. of Hull; Dan Davis, Harris Corp.;, U. of Hull; , OhioLINK; , FIZ Karlsruhe; Bill Parod, Northwestern U; Adam Soroka, U. of Virginia; Thorny Staples, U. of Virginia; , U. of Virginia
While in UNC-CH for JCDL I’ve had occasion to rant with/at some people about the state of the integrated library system marketplace — including, of course, how we got into the spot we’re in and how we might get out of it (and those people were kind enough to engage in the rant). Along comes a series of posts from Casey Bisson and Nicole Engard ultimately pointing back to John Blyberg’s “ILS Customer Bill-of-Rights” that is singing the same tune. There still seems to be a desire for a solution from an existing vendor, and in fact that was part of counter-points brought up by some on the receiving end of the ILS-must-go rant. (Paraphrased: ‘No one can satisfy the need of a library like a library automation vendor’ and ‘As libraries we’re not strong enough to take on the task of building the next ILS ourselves.’) Yet there does seem to be this mounting pressure to get control again over our data and how we present it to patrons.