Doorgaan naar de website
OCLC Support

Set up RapidILL

Learn how to set up RapidILL in Tipasa using OCLC Service Configuration and your RapidILL account and find information about disabling RapidILL.

Set up RapidILL as a service

To turn on RapidILL in your Tipasa interface:

  1. Sign in to OCLC Service Configuration.
    1. Navigate to WorldShare ILL and select External System Settings.
    2. Click on the check box next to "Turn this feature on to enable RapidILL processing."
    3. Enter your institution's RapidILL information (provided by RapidILL), including:
      • User Name
      • Password
      • Rapid Branch
      • Rapid Code

 Note:  If you need help determining any of this information, contact Rapid staff.

  1. Under Local Holdings Optionsselect where to route items held by your institution in RapidILL:
  • Route to ILL Review
  • Route to Document Delivery
  1. Click Save.
  1. Configure your RapidILL account settings.
  1. Sign into your RapidILL account.
  2. Navigate to Rapid Tools > My Profile and select the branch you want to edit from Edit Associated Branches.
  3. Select your preferences:
  • E-delivery Borrowing (Receiving)
    • Preferred Delivery Method set to Article Exchange
    • Alternate Delivery Method set to RapidX
  • E-delivery Lending (Sending)
    • Preferred Delivery Method set to Article Exchange

    • Alternate Delivery Method set to RapidX

 Note: Odyssey and Ariel are not supported in the integration between RapidILL and Tipasa.

  1. Set up automations to route patron requests directly to RapidILL. In OCLC Service Configuration:
    1. Create a new custom holdings group containing the RAPID symbol and your preferred fast turnaround copy suppliers. If you are a member of Express, add the Express symbols to this group.
    2. Add the custom holdings group to a custom holdings path. The custom holdings path can contain additional custom holdings groups, but the newly created group must be the first holdings group in the path.
      1. Create or modify an automation that will match all copy requests, apply copy-related constant data, and send the request directly to lenders in your newly created custom holdings path. This will enable a smart lender string, sorted by the turnaround time of all potential lenders. In some cases, RAPID may not be the fastest supplier.  Your request will be routed to the fastest suppliers first, ensuring your patrons receive requested articles as quickly as possible. See Automated Request Manager for more information.

 Note:  When setting up an automation for RapidILL, consider the following:

  • If you have Copyright turned on for copies and an automation in place for copies, requests that are within your copyright timeframe (5 or 6 years) and have more than 5 uses in the current year will not be automatically produced.
  • Any existing automations may need to be updated.  Review your existing automations to be sure that all desired requests are going through the RAPID automation. 
  • RapidILL processing will not apply to loan requests.  If an automation tries to assign RAPID to a loan request, RAPID will not be added to the lender string and the request will not be produced.
  1. (Optional) Add the RAPID symbol to any custom holdings group included for proven senders so that requests fulfilled with this service are automatically updated to Received status and routed to patrons.
  1. Add a lending priorities group based on the custom holdings group used for borrowing requests in order to reciprocate a fast turnaround time when supplying copies. The lending priority group will aggregate requests in a separate queue in order to give priority. 

Disable RapidILL

To turn off RapidILL integration:

In OCLC Service Configuration > External Service Providers deselect the box "Turn this feature on to enable RapidILL processing." Do not remove your institution's information from the credential fields.

Borrowing and lending requests that are pending with RapidILL will complete processing, however the RapidILL configuration data must remain in place in order to update the requests. New copy requests will not be routed to RapidILL.