Libraryfind 0.8.5 rc1

By reeset / On / In LibraryFind

Since Code4Lib, we’ve made a few significant changes to the 0.8.5 alpha tag.  Many of these are related to issues due to migrating to Rails 2.0, including issues with some pagination, changes to how rails handles posted data and then my favorite, issues with Rails defaulting to ActiveRecord caching (something that’s generally desireable, but causes issues within a threaded environment).  These fixes have all been wrapped up and pushed out via the svn: Branch 0.8.5 RC1.

There are one or two odds and ends that I’m interested in tightening up before we set this loose, but should be soon.


MarcEdit 5.1 Update

By reeset / On / In MarcEdit

I’ve got a couple of MarcEdit updates for folks.  Most of these updates are related to the Z39.50 client.  Of course, a number of other features have been added as well.  Here are the highlights:

Z39.50 Changes

So a number of Z39.50 changes — some related to adding editing functionality to the MarcEditor, others to provide Unicode search support for Z39.50 queries.  Big changes are:

  1. Unicode searches are now supported.  One of the funny things about Z39.50 is that by default, it wants to perform searches in a Latin format.  While there is a characterset option that can be set — few places seem to implement it.  So, MarcEdit will now evaluate the search string and then translate it appropriately to allow for correct searching (at least, this has been the case with all the test servers that I’ve worked with so far).
  2. Auto Unicode transforms.  While you can specify a return characterset — most Z39.50 servers will not send Unicode data back to you even if you ask.  MarcEdit’s Z39.50 client will provide transparent character translation for you, allowing you to take data in the format returned by the server or specifying that unicode data is always returned.  The way that you implement this new option is in the search screen (see below).  Simply check the Unicode option and the program will ensure that the data returned to the user is UTF8 encoded.
  3. In addition to changes to the Z39.50 Client, I’ve also included a lite-weight Z39.50 client into the MarcEditor.  This has been included to allow users to edit metadata records directly against a Z39.50 Server.  The new functionality is an Import, Update and Delete function.  This allows you to import files or groups of files into the Editor for edit, update those files that are edited and then delete files loaded into the editor.  Here are some screen shots:

    (Import Function — Initializes the Lite-weight tool)

    Again, this is a lite-weight tool.  At this point, the Edit Settings link is disabled.  If you need to change a database’s settings, you will want to update the settings using the full-blown Z39.50 tool.  They pull from the same data sources.  These changes will allow folks with systems like Koha or Zebra edit records directly in the MarcEditor. 

Other changes

Few other changes.  In the MarcEditor, you will now see the filename in the header (see below):

Also made changes to the command-line MarcEdit tool.  Added a new switch, -character.  This allows you to do character conversions.  For example, this is how you would convert a utf8 MARC file to a MARC8 MARC file:

C:\net_marcedit\C#\MProgram\MarcEdit\bin\Debug>cmarcedit -s c:\export.mrc -d c:\export1.mrc -utf8 -character
Beginning Process…
Records have been processed.

Within the MarcEditor, also re-implemented the Select Individual Records to Make function (found in the file menu):

The last change of note is the Delimited Text Translator.  I’ve added the ability to import data directly from an MS Access database.  It works basically like Excel importing.  You select the database and then select the Table/Sheet that you want to pull data from.

Download files are found at:


IE 8 beta & compliance

By reeset / On / In Uncategorized

While the IE team had said IE 8 would pass the Acid 2 test, I was taking a bit of a wait and see because a lot can happen between concept and release.  But, I downloaded the beta and sure enough, there’s the smiley face.



So, how about the Acid 3 test — not so good.