Sirsi/SOPAC Part 9

It’s been a couple of weeks since I have had a chance to code on this project. Over the last day and a half I have managed to beat my head against the brick wall of renewals and holds but these two pieces are now working. I have made some other changes. The most important I guess is how to harvest the data off the Sirsi Unicorn system. Tim and I had gone back and forth on cat key vs item key. When we both stepped away from it for a couple of days and looked at what we were trying to do it made sense to use the cat key. I have rewritten the code to extract the data using the cat key and have it now importing correctly. There was some additional clean up work with the author and title field that I have fixed. The code that allows you to place a hold basically takes a look to see if that item is available at your location and if it is then it is placed on hold and if not it then gets it from the next available location. I have not gone so far to check to see if it available at Main and then pull it from that location but it is a logical step to take in the future. There is some status information that is not showing up on the hold field and I think this is probably the next thing I am going to tackle.

Comments 2

  • Hi Sean,

    I’m implementing SOPAC on a Sirsi system. I’m wondering about your comment above that you settled on having use the cat key. The version of your connector which I have uses the following api call:

    echo $item | selitem -iB -oC | catalogdump -om

    According to Sirsi’s documentation for selitem’s -i option:

    B considers items with item IDs.
    C considers items with catalog keys.

    I see two possibilities:

    1) I’m using an outdated version, and the api call should look more like

    echo $cat_key | catalogdump -om

    2) You mean that SOPAC submits the item key, but that the perl uses selitem to convert that to the cat key (-oC) which is then submitted to catalogdump.

    Please clarify which it is, and if it’s #1, it would be very much appreciated if you could update the public svn repository.


  • Hi Sid,
    It is version 2. I am talking the item key as input and then getting the catkey as output and then catalogdump takes that as a native input.

    The svn is uptodate. I have not had a chance to do any development as I swamped at work.



Leave a Reply

Your email address will not be published.