Category: OCLC

  • Code4Lib Article: Opening the Door: A First Look at the OCLC WorldCat Metadata API

    For those interested in some code and feedback on experiences using the OCLC Metadata API, you can find my notes here: http://journal.code4lib.org/articles/9863   –TR

  • OCLC WorldCat Metadata API Ruby Gem

    Since last December, I’ve had the opportunity to spend a good deal of time working with the OCLC WorldCat Metadata API.  The focus was primarily around kicking the tires, and then eventually developing some integration components with MarcEdit, as well as a C# library (https://github.com/reeset/oclc_api) for those that may have use of such things. However,…

  • MarcEdit and the OCLC Metadata API: Introduction

    ******************************************************************************************************************************************************* I wanted to note that I’ve updated this post to correct/clarify two statements within this post.  The requirement of 2 wskeys Terms of use OCLC has two wskey structures.  For those developers that have been working with OCLC for a long time and have a wskey for their search services, OCLC can decommission your…

  • Can libraries really be effective advocates for open data?

    This is one of those questions that I ponder ever now and again, because I wonder how effective libraries really can be as open data advocates when our current practice demonstrates that we don’t fully believe in the concept.  Well, I should qualify that — we have no problem believing that other people have a…

  • OCLC’s Classify in C#

    During Code4Lib, I spent a little time playing with OCLC’s Classify service (http://oclc.org/developer/services/classify).  I’ve been working on adding a couple of functions into MarcEdit that will allow folks to leverage some of the OCLC web services.   Using OCLC’s Classify, I’ve been working on an experimental tool that would allow you to do batch classification of…

  • Thoughts about the SkyRiver/OCLC lawsuit

    So this is what it has come to…two iconic (III and OCLC that is) library software vendors wrestling in court.  Not that I think this is all that surprising…too bad…but not particularly surprising.  In fact, I think that many folks in the library community probably seen this coming.  For me, the canary in the mine,…

  • WorldCat Rights and Responsibilities for the OCLC Cooperative — initial thoughts

    So yesterday, a number of messages were sent out letting folks know that the OCLC Record Use Policy Council had completed their work and have provided a draft document to the OCLC member community for comment.  Sadly, I’m in the middle of doing other work (travelling mostly) — but I have had an opportunity to…

  • WorldCat API gem moved to rubyforge

    I had mentioned that I’d quickly developed a helper gem for simplifying using the WorldCat API in ruby (at least, it greatly simplifies using the API for my needs).  This was created in part for C4L and partly because I’m moving access from Z39.50 to the API when working with LF and I basically wanted…

  • WorldCat API: draft ruby gem

    Since the WorldCat Grid API became available, I’ve spent odd periods of time playing with the services to see what kinds of things I could do and not do with the information being made available.  This was partly due to a desire to create an open source version of WorldCat Local.  It wouldn’t have been…

  • OCLC to convene a Review Board of Shared Data Creation and Stewardship

    From the OCLC news release: http://www.oclc.org/us/en/news/releases/20092.htm First off, I think that this is a good thing for a couple of reasons. I take this development as a sign that OCLC has heard the membership, heard some of their concerns and has agreed to take some additional time to have further discussion with the membership.  For…