Routing Direct OCLC Requests with a Predefined Lending String

Print Friendly and PDF Follow

The Awaiting OCLC Sending Queue

Routing Requests to the Awaiting OCLC Sending Queue

Requests that come into ILLiad with a value already in the Lending String field (via OpenURL for example) and requests that have had the lending string manually added to them by your staff, can be routed, using a custom routing rule, to a special queue where they will be automatically sent to OCLC. The Connection Manager monitors the queue, Awaiting OCLC Sending, and creates a new OCLC request for each transaction it finds there. The Connection Manager applies a new Constant Data profile specified by one of two customization keys, OCLCAutomaticSendingArticleCD and OCLCAutomaticSendingLoanCD, and creates an OCLC Work Form based on the Constant Data profile and values in the WorkForm Mapping table. When a request is routed to Awaiting OCLC Sending, the Connection Manager sends the request to OCLC, assigns an ILL Number and moves the request to Request Sent. Requests you have automatically routed to the Awaiting OCLC Sending queue are processed during existing direct request processing.

The Predefined Lending String

The predefined lending string field should appear in your custom routing rule in the following format:

ISNULL(t.LendingString,'') not in ('Direct Request','RAPID','Manual Request','')

Troubleshooting Changes to the Lending String

As of ILLiad Connection Manager v9.2.2.0, a note will be added to the ILLiad request if the Lending String on the ILLiad request is modified when sending the request to OCLC (e.g., in the case that a symbol was removed because the lender is a non-supplier or because the symbol is invalid). The note will state "Original lending string does not match OCLC lending string" and will include detailed information about which lending symbols were modified/removed for troubleshooting purposes.

When a Request Fails

If the direct request process fails for any reason, the Lending String value will be moved into a Transaction Note along with an error message. The Lending String field will be changed to "Manual Request", and the request will then be moved to Awaiting Request Processing. RAPID requests that arrive in the Awaiting Request Processing queue with a Lending String of "RAPID" behave in a similar manner: the Lending String is set to "Manual Request" and the request is returned to Awaiting Request Processing. This is done so that routing rules created to automatically move requests into Awaiting OCLC Sending have an indicator to check to assure that failed requests are not getting put back into the Awaiting OCLC Sending queue when they fail.

Setting Constant Data Profile and Customization Keys for the Awaiting OCLC Sending Queue

Keys in the Customization Manager define which constant data record to use. There is one for loans and one for articles:

  • OCLCAutomaticSendingArticleCD: The default constant data value used for all article requests sent automatically to OCLC.
  • OCLCAutomaticSendingLoanCD: The default constant data value used for all loan requests sent automatically to OCLC.

Setting WorkForm Mapping Table Values for the Awaiting OCLC Sending Queue

You will need to add new workform mapping entries, one for articles and one for loans, into the WorkFormMapping table in the Customization Manager. The easiest way to do this is to copy each of the Blank Loan entries and Blank Article entries in your table, change the Work Form Type to OCLC Loan and OCLC Article as appropriate and save the new entries.



If this article didn’t resolve your issue, please contact Atlas Support for assistance:

Contact Support