There has been quite a saga unfolding slowly over the last couple months in the #code4lib IRC channel regarding the use of Amazon’s OpenSearch technology and it’s use for searching across cooperating libraries’ catalogs. Everyone there seems to agree, on a basic level, that OpenSearch is a useful search interface and that it benefits everyone to expose our catalogs using it.
Evergreen Alpha Release
After approximately a year of software development, we are proud to announce the arrival of the Evergreen Alpha release! Programmers and other techies will probably want to go straight to the download area and grab a tarball. We’re very pleased with how this release turned out, and are looking forward to the comments and suggestions from the field.
A little history on JSON, etc.
I’m glad to see we’ve stirred the pot with our discussion of JSON. It’s driven us to stop and think about our decisions, their impact on our project, and how others may be able to interact with our system.
For the sake of those interested, I thought I might offer some clarity regarding our use of JSON. When OpenSRF (our core information passing framework, discussed here) was first designed, it was XML everywhere. As we were doing our benchmarking of the system, we thought things were good, but sluggish with large datasets. OpenSRF is designed as a set of independent applications which often must communicate with one or more other applications to accomplish any particular task. For example, to retrieve information on a patron, the system must verify the requesting party has such permission, then it must actually retrieve the information. With a lot of such conversation going on across the backbone, you can see there will be a great deal of data flying around the network.