RE: Connexion and exporting to Innopac

["Simpson, Sarah" <ssimpso at tulsalibrary dot org>]

We had the same exact problem and it is (mostly) fixed.  We had to set up a Gateway export instead of using the default export that was available when we got into Connexion the first time.  The message actually still says bib and item record created, though no item record is created BUT it does provide the Innovative bib number that is created in our local system (and tells us the title that was overlayed if we are overlaying a record).  If you haven't heard from someone else and want to talk about what we did, email me and I'll find the steps we took to get it going.
 
Sarah Simpson
Tulsa City-County Library

________________________________

From: innopac-bounces at innopacusers dot org on behalf of Catherine Cox
Sent: Tue 5/31/2005 4:20 PM
To: innopac at innopacusers dot org
Subject: Connexion and exporting to Innopac



We're just getting around to setting up Connexion for our staff - I know, I
know, we should have done it months ago, but life's like that
sometimes.  For the most part we seem to have things working fairly well,
but there's one problem I haven't managed to fix yet.

We import our bib records from OCLC prior to ordering.  In Passport, when
the record was exported to our Innopac, the message that showed up in
Passport confirmed that the export was successful - "BIBLIOGRAPHIC record
created" - and displayed the bib number.  In Connexion, on the same
computer, using the same gateway, the message that comes back says
"BIBLIOGRAPHIC and ITEM record created" and does not give the bib
number.  When we check the record in Innopac, the bib record displays
correctly, and there is no item record (which is the way it ought to be -
we create the item record later, when the item is received.)

We just upgraded to Silver and we're running the Connexion Client.   We're
not using MilCat yet - still on the character-based system for
cataloging.  The help desk says that the message sent back from the Innopac
when the record is received is the same no matter whether what utility
we're using, so the problem must be with Connexion.  I'm waiting to hear
back from OCLC, but I was wondering if anyone on the list has had a similar
problem and if so, what they did to fix it?

Catherine Cox
Collection Development & Electronics Librarian
Mission College Library
  

--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC at innopacusers dot org
Update your subscription options: http://innopacusers.org/mailman/listinfo/innopac




--- StripMime Report -- processed MIME parts ---
multipart/mixed
  text/plain (text body -- kept)
  application/ms-tnef
---