OCLC

SYMPTOMS

When clicking either the OCLC button on the search form, or the OCLC Live Link menu option from the General Update form, ILLiad stops responding and you have to use the task manager to kill the session.

CAUSE

This is caused by an incorrect OCLC Authorization or Password entered in the Customization Manager.

RESOLUTION

Verify the Authorization and Password for your site entered in the Customization Manager.

SUMMARY

You may notice the following error on your ILLiad server in the Windows System Event Log each night between midnight and 3am:

The ILLiad Connection Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This is normal as the service resets itself. The ILLiad Connection Manager Service is set to restart automatically after stopping. As long as you use the ILLiad Auto Updater or the InstallConnectionManager.bat file provided with it to install the service, it will be set to restart automatically.

SUMMARY

You will need to make several changes to your constant data settings within OCLC in order for your Connection Manager to function properly. You can edit these through the OCLC .. Resource Sharing Settings option within the ILLiad Client. These changes are necessary for any constant data used by a site for updating within the Connection Manager. In shared server installations, each site can designate a constant data to use for sending and receiving requests from within the Customization Manager under System .. OCLC.

Please note that a DEFAULT Constant Data set is required by the ILLiad Connection Manager unless your OCLCILLConnectorCDBorrowing and/or OCLCILLConnectorCDLending keys are set to some other Constant Data set.

Check the following values in your constant data. These are the ones needed for ILLiad. Others may be recommended or necessary for OCLC sending to function but are not specific to ILLiad.

Required Changes

Shipped - The value should be "-0" so that when responding Yes to requests, the status changes to Will Ship instead of Will Supply. ILLiad does not use Will Supply for updating filled requests.

Return To - This should be the full return address for your institution. If this value is missing and ILLiad attempts to update Yes for a Loan, you may get an error about the request missing a required field. You can not update Loans to Yes without supplying a Return To field in OCLC.

Optional Changes

Patron fields - These should be blank. ILLiad will fill out the Patron field with the customer's name by default and append it to whatever is in the field already. You can edit what is put in that OCLC field by editing the WorkFormMapping table.

Due Date - This value should be blank. If you put in a default value such as +30, the date created will be overwritten by the due date from ILLiad or N/A for articles.

Lending Charges - This value should be blank. ILLiad will enter any charges and add IFM tags for those items billed via IFM.

All other borrowing fields for the OCLC workform will be filled out using the WorkFormMapping table or the Connection Manager when performing the updates.

SUMMARY

The following OCLC fields are recognized by the ILLiad WorkFormMapping table as potential OCLCFieldName values. These fields can be used to map ILLiad field values to the specified OCLC fields in the OCLC work form upon creation of the work form during processing. These fields are not case-sensitive.

affiliation
article
author
billto
billingnotes
borrowingnotes
callnumber
copyrightcompliance
dissertation
edition
email
fax
imprint
insurance
isbn
issn
issuedate
issuenumber
locations
maxcostamount
maxcosttype
needbeforedate
pages
patron
patronaddress
patrondepartment
patronemail
patronfax
patronid
patronnotes
patronphone
patronpickuplocation
patronstatus
series
shipto
shipvia
title
uniformtitle
verified
volume

MORE INFORMATION

Please note that the former OCLC MaxCost field has been split into two distinct fields in the new OCLC system. These are MaxCostAmount and MaxCostType.MaxCostAmount should contain only a dollar amount, such as $15. No additional text will be accepted in this field. MaxCostType should contain only text. Recognized values for this field are IFM or Other. Any other text which may have populated your MaxCost field in the past should be moved elsewhere, such as to the borrowingnotes field.

SUMMARY

The process for borrowing renewal requests has changed slightly in order to accomodate the ILLiad Connector.

If customers request renewals automatically, those items go to Renewed by Customer to XX/XX/XXXX. Those requests can be sent to the Connector from the Main Menu under Process .. Write Renewal File/Send to OCLC. This will move the items back to Checked Out to Customer and send the requests for the next Connector update.

If customers request a renewal that goes to Renewal Requested or if a staff member wants to place a renewal request for a customer, the staff can place the renewal request from the General Update form. First change the due date to the new one desired. Then under Process choose Renew Request. The request will be sent to OCLC with the next Connector update. Be sure to change the status back to Checked Out to Customer after requesting the renewal.

SUMMARY

The ILLiad Connector automatically downloads and updates requests and statuses in OCLC. Here is a list of statuses updated and downloaded by the ILLiad Connector.

BORROWING

* Connector Version 6.3.0.0 and higher.

LENDING

SUMMARY

There are two keys, OCLCILLConnectorCDBorrowing and OCLCILLConnectorCDLending, that set the constant data when the ILLiad Connector runs to perform updates and downloads. These keys are located in the Customization Manager under System - OCLC.

These keys are used ONLY by Shared Server institutions when multiple libraries that are otherwise separate entities share an OCLC symbol. They specify which set of constant data the ILLiad Connector should use for sites that share OCLC symbols. This information is used for updating Lending (for Return To fields etc.) and for sending out on Borrowing (Ship To fields etc.).

There is no need to set these keys for Single Server ILLiad institutions. Nor is there any need to set these keys for Shared Server ILLiad institutions that do not share OCLC symbols, as in most cases there is no constant data choice to be made.

SYMPTOMS

When exporting items to the OCLC MicroEnhancer from ILLiad, an error will appear. The error varies depending on the problem.

ERROR MESSAGES

Permission denied.

File not found.

CAUSE

Permission denied: If the ILLiad share is set to read only, and there is no MEDatPath key directing ILLiad to another folder location for the files it needs, ILLiad can not gain the necessary access to send the updates to the MicroEnhancer.

File not found: The four dat files necessary for updating are not in the ILLiad share or the path that MEDatPath points to if that key exists.

RESOLUTION

The four dat files - EvenReceived.dat, EvenReturned.dat, OddReceived.dat and OddReturned.dat - need to be copied to the local machines in the c:\illiad folder.

Next set your MEDatPath to point to c:\illiad\ (be sure to include the last \ in the path). The key should be under Borrowing .. OCLC Microenhancer. If the key does not exist, you can either add it by entering it in the Customization table (under System .. General in the Customization Manager) with these values or by running the script below that on the ILLData database:

CustKey: MEDatPath
Value: c:\illiad\
NVTGC: ILL
Description: Directory location for the four dat files for Borrowing updating OCLC
AdminCat: Borrowing
AdminKey: OCLC Microenhancer
AdminType: StringValue

<begin script>

use ILLData
go
insert into Customization
(CustKey, Value, NVTGC, Description, AdminCat, AdminKey, AdminType)
values
('MEDatPath','c:\illiad\','ILL','Directory location for the four dat files for Borrowing updating OCLC', 'Borrowing','OCLC Microenhancer','StringValue')
go

<end script>

SYMPTOMS

The borrowing items that import to Awaiting Unfilled Request Processing (Unfilleds in OCLC) no longer show the history from the OCLC record that includes the "reasons for no" from each potential lender.

CAUSE

This feature was in version 6.0.0.3 - 6.0.0.8 of the Connector but was found to be causing problems at some sites (the imports would fail at this point occasionally).

RESOLUTION

This feature will be put back in the Connector an upcoming Connector release after verifying that it no longer causes imports to cease mid-stream.

SUMMARY

When processing both Borrowing and Lending OCLC requests, records that are in the queue for updating (either via the Connector or through MicroEnhancer or Passport) can be removed from that table so that a different update can be sent to OCLC.

The most common need for this is Lending requests that are mistakenly cancelled, conditionalized or marked as "yes" and that status needs to be changed later. ILLiad allows you to remove the old pending update from the table within the client so that staff can then update the request to the new status/process for updating on OCLC.

EXAMPLES

To change a Lending request that was originally answered as "yes" to a conditional, do the following steps:

1. From the Update Stacks Search form, click the Mark Item as Found button (this will most likely already have been done earlier, hence the need to change the update).
2. Search the request in ILLiad and go to the General Update Form.
3. If there are any pending updates to be sent to OCLC, a tab will appear on the right side of the form next to the Resubmission tab marked Pending Updates.
4. Click on the Pending Updates tab and right-click on the update you wish to remove.
5. Choose Remove Selected Pending Update from the pop up menu.
6. The selected update will be removed from the list and the update table. If the list is now empty, closing and reopening the General Update form will remove the Pending Updates tab. The Pending Updates tab only shows if there are updates in the table to be sent to OCLC.
7. Process the request again with the new status. In this example, you would conditionalize the request from the General Update form to send a Conditional message on OCLC at the next update.