1. EDI from Blackwells Collection Manager to Voyager: Issues and Solutions Carol MacDonald University of Regina Library Issues/Solutions Objectives Contact We were early adopters of the new Collection Manager EDI export process and overlay of full records from OCLC so had many issues establishing efficient workflows for our needs. Blackwell’s documentation was not always accurate and the workarounds they suggested often did not work with Voyager. Each phase of the project required extensive testing.  Bulk import profile recommended by Blackwell didn’t work so delayed start; bug in Sysadmin which Ex Libris confirmed with Blackwell and gave us workaround to use  Collection Manager did not set their profiles to output minimum records with 024 field so dupe detection did not work on overlay of OCLC records; staff had to manually load each record cutting and pasting 020 fields to match until Blackwell began to output records with 024 fields  Collection Manager EDI Files with multiple orders could not create one PO per title as their docs indicated; had to educate them on Voyager capabilities with Ex Libris supporting documentation and advice to Blackwells  Staff used Webadmin to load files with 10 or less titles/line items to avoid accounting & FYC problems; this created many log.imp and webadmin files on server  Staff made mistakes in naming files for preparation for FTP to Blackwells. Filenames not following naming conventions aren’t accepted by the Blackwells server; therefore Systems intervention is required to rename files on server before they can FTPed; if we automate the process it will require more error checks  EDI files from Blackwell had taxes at invoice level rather than line level; we can’t use this  Blackwells reluctant to change EDI file to include taxes in line level segments of invoice lines but followed Ex Libris advice how to output a proper EDI file for Voyager  Librarians select from Collection Manager; Acq staff export files from CM by subject  Bulkimport must create one PO per title from each CM file loaded with taxes in each line item not total of invoice; line item totals must match requirements of Banner Financial System funds  Acq staff import CM files to create minimal bib records, MFHDS, POs, & invoice in Voyager without Systems intervention  Acq staff prepare file of approved orders to FTP to Blackwell using Blackwell file naming conventions; Blackwell sends to OCLC for full record creation  No direct access to server by staff so need staff to use Webadmin to bulkimport records  Cat staff FTP full record from OCLC and load using Webadmin with bulk import based on 024 match and dupe detection Replace  Automate as much of process as possible so Technical Services staff can control workflow ELUNA 2009 Annual Conference May 6-8, 2009. Richmond, Virginia Bulk Import Workflow Carol MacDonald Head, Systems Development and Implementation University of Regina Library Email: carol.macdonald@uregina.cacarol.macdonald@uregina.ca Phone: (306) 585-4015