WorldCat API gem moved to rubyforge

By reeset / On / In OCLC, rails, ruby

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 a be able to do the search and interact with the results as a set of objects (rather and XML). 

Anyway, the first version of the gem (which is slightly different from the code first posted prior to C4L) can be found at the project page, here:


oai and sru gems updated

By reeset / On / In rails, ruby

In wrapping up the Libraryfind update, I’ve had to make some modifications to a few gem packages.  These are the ones updated:

  1. oai:
    Prior versions of the oai component only supported the ruby libxml gem 0.3.8-.  In order to support the newer versions of the ruby-libxml (which does better memory management), I’ve updated the oai gem that will support both the older and new ruby-libxml apis.  The primary changes are related to how it handles properties/attributes and the way that the oai provider class handles dates (to support OAI 2.0 validation).
  2. sru-ruby:
    Added libxml support.  For queries that return one or two records, the different between using REXML or Libxml as your parser will be hardly noticable.  However, when queries result in larger datasets, the difference will be measured in terms of seconds.  For example, in some tests, recordsets returning 50 records in MARCXML format could run close to 10 seconds using REXML.  On the other hand, the same search using libxml processes in 0.8 seconds.  For tools, like LibraryFind, which deal with larger datasets, this is a welcome change.



Rails SVN question

By reeset / On / In rails

For a rails project, when I want to update the vendor/rails it appears that the easiest way to update this in svn is to delete the directory, refresh the gems and then re-add the directory to the svn.  Does this sound right?  Seems like it should be easier.  This has been the process that we have used for about a year and after going through it again (to update to the 2.0.2 framework), I’m just thinking that its got to be easier.