Recently in WorldCat API Category
OK, so it isn't Rock 'n Roll. So sue me. But just as rockers can have fun doing what they love, so can library coders. And this Thursday and Friday, that's exactly what a bunch of us will be doing in Seattle -- having fun. We're sorry you couldn't make it, but we have done this kind of thing before and before, and will do so again (a VALA Bootcamp already scheduled and who knows where/when next).
It's two days of library mashup goodness, fueled by our suite of APIs as well as many others from libraryland and beyond. Out of the two days, we hope to do presentations of options for no more than a quarter of the time, then code like mad, and regroup toward the end to show-off what we've accomplished. Like I said, we're sorry you couldn't make it. But if you're nearby, come. We have slots left and we'd be happy to make your acquaintance. As for the rest of you, if you feel some serious mojo seeping out of Seattle, at least you'll know why.
New limit by holdings for WorldCat Search API
Good news for WorldCat Search API WSkey holders. The WorldCat Search API has been enhanced. You can now limit the results returned to an individual library's holding symbol, without authenticating the application's users, at all service levels. In lots of discussions with developers, people have asked for this feature. Yay, now it's here.
With this functionality update, the eligibility requirements for the WorldCat Search API have also been updated.
NB: ALL 200+ current WorldCat Search API WSKeys will remain active through at least Sept 1, 2010. This eligibility change should affect very few future requests for service. In addition, there is even more good news if your library doesn't currently qualify--or if you're a developer who is not connected to a library.
WorldCat Basic API planned
For a long time now, OCLC has wanted to provide a general Web service to WorldCat in addition to WorldCat.org. This wish is now becoming a reality. Later this year you'll have a simple API into WorldCat that anyone and everyone in the world can use, for noncommercial use. Called the WorldCat Basic API, it provides a mashable access point for lightweight apps built by developers who may or may not have ties to the library community.
The WorldCat Basic API is planned to use OpenSearch and return feeds in Atom and RSS. Results include OCLC number links to WorldCat.org, ISBNs and formatted citations.
We're excited to announce these improvements and updates, expanding the range of developers able to include WorldCat and library data in their apps. Sign up for the Developer Network listserv (WC-DEVNET-L) if you haven't already, to hear when the WorldCat Basic API is available.
I just finished reading the article "Using the OCLC WorldCat APIs" in Python Magazine by Mark Matienzo (fondly known as "anarchivist" in his online persona), and I have to say he did an excellent job of describing not only how to use our APIs effectively, but also providing a very accurate and thorough historical context. I really don't think even an OCLC employee could have done any better.
But of course the real value of his piece is his "worldcat" Python module and his explanation and demonstration on how to use it. If you have access to the issue (or buy it for $7), there is even a temporary, limited access key you can use to test his code against our services.
This piece is required reading for any Python programmers wishing to take advantage of our APIs, and highly recommended for anyone else wanting to use our APIs, given his straightforward descriptions of the services and his examples on how he mashed them up along with other APIs (such as Google Maps) to create a useful service. This is exactly why we are offering these services, so it warms the cockles of our CPU to see it happening.
