Configuration
Introduction
Resource sharing using Rapido is based on several elements, including a Primo VE CDI enabled discovery and an active RAPID ILL account. This page focuses on the back-office elements that have to do with the resource sharing and fulfillment aspects of the workflow.
Library processing of Rapido requests, on both the borrower side and lender side, is based on standard resource sharing workflows and requires the resource sharing and fulfillment configurations that make the library processes possible. Working with Rapido enables you to maintain the local resource sharing configurations such as partner records and locate profiles that support managing a resource sharing process with a non-Rapido partner. If you expect to manage resource sharing transactions with non-Rapido partners, then the resource sharing configurations that are detailed in the Configuring Resource Sharing document are relevant. The following are exceptions:
- Sending Borrower Request rules (replaced by Rapido Mediation Rules)
- Additional Requested Media (Rapido uses different request forms)
- Configuring Primo Request Form Type by Genre (Rapido uses different request forms)
The following sections focus on specific configuration requirements for Rapido. More information may be found in the relevant sections of the Customer Knowledge Center.
Rapido Partners
- When joining Rapido PODs there is no need to create/add partners at the institution level.
- Once a request is created between two Rapido partners, the partner is added automatically to the partners' list for both institutions at the institutional level (no manual action is required).
- There are cases where you might want to allow resource sharing for a Rapido partner who is not part of a POD you belong to.
- In this case, you can use the Add Partner function to send the request. As a prerequisite, both sides need to download the partner record from the community tab to the institutional level and work at a peer-to-peer level.
Rapido Members and Resource Sharing Libraries
Use the Resource Sharing > Configuration > Members to configure Rapido members.
Adding a Resource Sharing Library
Rapido requires a minimum of one member to support borrower or lender requests. Multiple members are supported.
When adding From New Resource Sharing Library, ensure Is resource sharing library is selected. For more information on creating libraries, see Adding Libraries and Configuring Resource Sharing Libraries.
Editing an Existing Resource Sharing Library
More than one member is used when there are multiple campuses that manage their resource sharing operations separately from one another or libraries that run their resource sharing operations independently.
Like any library, the resource sharing library must also have a valid calendar. Note that:
- The ISO Symbol is only required if the resource sharing library is also used for resource sharing transactions with non-Rapido partners. It is not required if the resource sharing library only communicates (as a borrower or lender) with Rapido partners.
- The locate process related parameters are not required if the library only communicates (as a borrower or lender) with Rapido partners:
- Borrowing setup
- Cancel request on locate failure
- Automatic activate locate profile
- Lending setup
- Automatic location of resources
- Ignore electronic resources
- Automatic creation
- Locate by fields
- Borrowing setup
Borrowing Policies
Use the Borrowing Policies (Configuration > Resource Sharing > Members) to set the pod priorities. Use 
to drag and drop according to the order of priorities for borrowing requests.
Maximum Time to Delivery cannot be left blank. If left blank, no Rapido terms appear in Primo VE and the borrowing request is not sent to Rapido pod partner. There must always be a value, even if the value is 0.
Locally managed pods are checked when Locally Manage Rapido Pod is selected in Fulfillment > Resource Sharing > Rota Templates.
Configure the following fields to include these terms in all offers:
- Delivery Time
- Loan Period
- Check availability and only show terms for available resources
If Check availability and only show terms for available resources is selected, the terms only appear if the item is available.
This section is available for fulfillment network type pods.
Borrowing Exceptions
You can associate a pod with a Rapido member.
Add exceptions to override the default borrowing policies. Borrowing exceptions can be defined to allow for variation in working with pods that differ from and override your defined default borrowing policies. The borrowing exceptions do not apply to locally managed pods.
Assigning POD Priorities at the lZ Level
For some institutions, it might be relevant to set the POD priority at the IZ level rather than at the member level. To do so, from Resource Sharing > Configuration > Institutional Borrowing Policy, select Use Institutional Borrowing Policies. Define your Default Borrowing Policies and Save. Using this feature overrides the settings in the individual member's policies (Resource Sharing > Configuration > Members).
Maximum Time to Delivery cannot be left blank. If left blank, no Rapido terms appear in Primo VE and the borrowing request is not sent to Rapido pod partner. There must always be a value, even if the value is 0.
Configuring Borrowing Request Inactive Filters
- General System Administrator
- Fulfillment Administrator
Fulfillment Unit and Terms of Use
Borrowing resource sharing libraries must have a library Fulfillment Unit (Configuration > Fulfillment > Physical Fulfillment > Fulfillment Units).
Fulfillment libraries Resource Sharing Allowed must be enabled in the Fulfillment Unit Rules tab.
The rules determine:
- Resource sharing eligibility
- Request limits
- Allow pickup locations
- Fees
- Personal delivery
For more information, see Supporting Personal Delivery for Requests.
Participating Items
To manage resource sharing lending requests, you must have a Repository Manager role.
Use the Configuration > Resource Sharing > Members > Physical Items Lending Policies to edit the lending policies.
Add Participating Items to specify the terms for each type of item.
The Participating Items are sets of Physical Items used for fulfilling resource sharing requests. Participating Items must be defined for every member.
The Location is the current location of the item and not the permanent location.
Physical items are only available for lending when Supplies physical items is checked.
Participating Items sets must be linked to the pods that are assigned to a member.
Adding a Physical Lending Policy
Use the Add Physical Lending Policy to make lending terms available to other Rapido institutions that are not part of a pod. This information is available for other institutions when using the Find Partners action from borrowing requests if they have signed the resource sharing agreement.
After entering the lending policy terms, requests for physical items that meet your terms will be able for lending.
Lost Fees
New for June! When the parameter rs_use_tou_for_lost_item (Configuration > Resource Sharing > General > Other Settings) is set to true (default false), a Lost Item Fine is automatically added to the patron's account in addition to the Lost Item Replacement Fee when an item is marked as lost or when the number of lost profile days have passed, based on the borrowing library's settings in the library loan Terms of Use (TOU) (Configuration > Fulfillment > Physical Fulfillment > Terms of Use and Policies).
Excluding Non-Workdays Days from Expiry Period
The Expiry Time (days) can either be defined on a partner or on a lending policy. A job runs that deletes unhandled expired requests. To prevent lending requests from expiring during non-workdays, Rapido enables you to set days to exclude from the expiry period calculation (Configuration > Resource Sharing > Configuration > Resource Sharing Working Days).
Automatic Jobs for Renewals and Expired Requests
When the Expired Resource Sharing Requests job (Configuration > Fulfillment > General > Fulfillment Job Configuration) is set to Active, expired requests are automatically rejected. The default setting for this job is Inactive.
For pods that allow automatic renewals, when the Send Courtesy Notices and Handle Loan Renewals Job (Configuration > Fulfillment > General > Fulfillment Job Configuration) is set to Active and Allow Renew for Rapido Pods Requests is checked, expiring resource sharing requests are automatically renewed. The default setting for this job is Inactive.
AutoRenewal (Fulfillment > Auto Loan Renewal Rules) must be set to True. in the Automatic Loan Renewal Rule Editor.
Customizing Borrowing Cancellation Reasons
Each institution can customize the list of request-cancellation reasons that appear in the dropdown list of reasons when cancelling requests like holds or resource-sharing borrowing requests. The text available for each of the standard reasons can be modified, and reasons that are not relevant to the institution can be removed from the dropdown list. In addition, the institution can create up to ten new reasons to add to the dropdown list. These options enable the institution to create a list of options that only includes reasons that are actually in use in their libraries, thus preventing problems that arise when an inappropriate reason is selected. The list of cancellation reasons can be edited from Configuration > Fulfillment > Request Cancellation Reasons.
Copyright Rules
The copyright rules must be activated to activate copyright management on the borrower side of the request.
For more information, watch Copyright Management.
The rs_borrower_copyright_management parameter (Fulfillment > General > Other Settings) must be set to true for the copyright rules to work.
The Rule of Five is an out-of-the box rule and is disabled by default. When enabled, the rule causes the sixth digitally requested request that is placed within the same calendar year for the same material (that has been published within the last five years) to automatically be marked as copyright approved. The request is still sent, but the copyright status is reportable in Analytics.
Configure the copyright rules from Configuration > Resource Sharing > Rapido Rules > Borrowing Copyright Rules.
When adding a rule, the following parameters are available by default:
- Number of Requests in Calendar Year — How many times a resource can be requested in a given year.
- Request Type — Electronic or Digital.
- Total Copyright Work Percentage — Up to what percentage of a resource can be requested for Electronic and Digital.
- Years Since Publication Date — When a resource was published.
- Number of Requests Per User on Specific Resource — This parameter determines how many requests a user is allowed to make for a resource. For articles, this is determined by ISSN, volume, and issue (if any of these are empty the rule will be skipped). For books, this is determined by ISBN.
- Time Span (In Months) Since Request Date — The amount of time that needs to pass before a resource can be re-requested.
Rapido can only calculate the total work percentage if the total number of pages is known, and the page fields are populated. Without this information, the rule will be skipped. This case mostly occurs for requests placed via the blank form Resource Sharing requests and not from a Rapido offer, since the Rapido offer includes all the metadata.
You have the option to add a label to easily determine which copyright rule was applied to a request. When a request meets the rule, the label appears in the task list. Additionally, you can create a set based on the copyright label.
Select to enable Copyright Clearance to automatically approve or reject the copyright clearance request.
The Rapido rules only apply to borrowing requests. For Alma copyright rules, which apply to lending requests, see Configuring Digitization and Copyright Rules.
Copyright Declaration
Use the Configuration > Resource Sharing > Request Forms > Resource Sharing Copyright Declaration to create the copyright declaration that is attached to the Primo request form. No declaration is mandatory on the request form if the relevant text is not configured using this link.
The following HTML tags are supported:
-
Common Block Elements: <p>, <div>, <h1>, <h2>, <h3>, <h4>, <h5>, <h6>, <ul>, <ol>, <li>, <blockquote>,
-
Table elements: <tr>, <td>, <th>, <colgroup>, <caption>, <col>, <thead>, <tbody>, <tfoot>
-
LINKS: adding href to <a> elements
-
Common Inline Formatting Elements: <b>, <i>, <font>, <s>, <u>, <o>, <sup>, <sub>, <ins>, <del>, <strong>, <strike>, <tt>, <code>, <big>, <small>, <br>, <span>, <em>
-
IMAGES: <img>
Staff Accounts
Staff users that access resource sharing task lists must have the following roles:
- Fulfillment Administrator (institution scope). This role is required to access the Fulfillment and the Resource Sharing configuration menu.
- Fulfillment Services Manager/Operator (scope of the resource sharing library) This role is required to access the borrower and lender task lists.
- The role must be within the scope of the resource sharing library that the user requires access to. An institution-level scope does not affect this access.
- Only a Repository Manager role can delete a set of participating items.
Patron Accounts
To place requests, patrons must be assigned a patron role and have an assigned Resource sharing library or a default patron resource sharing library. If this is not defined in the patron's user information, Alma uses the ill_item_creation_lib_code customer parameter to choose the Resource sharing library.
Setting Librarian-assigned Blocks
From the user's Blocks section, you can define if a user is blocked from making loan requests, renewals, resource sharing requests, or hold requests. Each block may contain one or a combination of these blocks, together with a specific reason for the block, as configured by an administrator.
- From the User Block Descriptions table (Configuration > Fulfillment > Patron Configurations > User Block Description), define the reasons for blocking a user, for example, Disruptive behavior in the library. After enabling the relevant reasons, Save.
- From the User Block Definitions table (Configuration Menu > Fulfillment > Patron Configurations > User Block Definitions), assign a block to each reason you specified in the previous step.
- In the Type field, select the type of block: This is a descriptive field, except for Consortial blocks (that are used when copying a block to linked accounts in the network) and Demerits blocks (that are applied by accrued demerits on the user).
- In the Blocked Action field, select which actions to prevent:
- 01 – loan
- 02 – loan, renew
- 03 – loan, renew, hold
- Note: You can set up blocks for resource sharing and create other permutations of these block options (e.g., loan+hold). For these options, contact Ex Libris Support.
- In the Overridable field, select which circulation roles are required to override the block:
- ALL – Any circulation desk operator can override the block
- NONE – Users cannot override the block
- CIRCDESC – A circulation desk manager can override the block
- OPERATOR – A circulation desk manager or a circulation desk operator can override the block (and not a user with circulation desk operator – limited permissions)
- In the Network Block field, select False, as currently we are setting up an institution-only block. If you are part of a network, select True - this copies the block to linked accounts created for your users.
-
Select Save. The block is set. For details, see Configuring User Block Descriptions and Definitions.
-
To add the block to a specific user, find that user in the Manage Users screen (Admin > User Management > Manage Users). In the user's User Details screen, from the Blocks tab, add the Disruptive behavior in the library block to the user and select Save. For details, see Blocking and Unblocking Users.
You can also add an expiry date for the block to have it automatically lifted.
-
To test the block, try to loan the user an item. The following message appears:
As defined above, users with the Circulation Desk Manager or Circulation Desk Operator roles can override the block by selecting Override in the dialog box.
General Settings
Set the Configuration > Fulfillment > General > Other Settings menu as follows:
The ill_item_creation_lib_code parameter can be used to assign a default library. If this is configured, then the user record does not have to be updated with a resource sharing library.
- rs_disable_borrowing_auto_assign – default true. When set to false, this setting assigns borrowing requests to a specified staff member for updating.
- rs_disable_lending_auto_assign – default false. This auto-assigns lending requests to the staff member that updates them.
- rs_keep_rejected_request_active – This determines your policy regarding requests that have been rejected by the lender. Use this parameter to determine whether the borrowing or lending requests should remain active when rejected and should continue being processed as an active request, for example in order to process with a broker system.
- None — This is the default setting. The request is completed and is no longer included in the active requests queue.
- Borrowing, Lending, Both — The request remains in the active requests queue of the appropriate task list, so the staff has the option to work on the request.
- rs_default_digitization_department. This is the digitization department that is assigned automatically created digitization requests if the rs_auto_request_lending parameter is on.
- check_patron_duplicate_borrowing_requests – true. This prevents patrons from requesting a resource that they already have an active request for.
Locate Failed
When a locate process fails for technical reasons such as missing credentials or communication issues, set rapido_do_not_send_request_when_locate_fails (Configuration > Resource Sharing > General > Other Settings) parameter to true (default) to send the request to the next lender in the rota. Set the parameter to false to send the request to the lender whose locate request failed.
Self Owned Resources
To prevent Rapido offers for self-owned resources, add the below Display Logic Rules (Configuration > Fulfillment > Discovery Interface Display Logic > Display Logic Rules):
- Hide service Resource Sharing Request with Ownership by the institution = true — hides the Rapido offer when there is physical inventory
- Hide service Resource Sharing Request if exists service Full Text — hides the Rapido offer when there is electronic inventory
Setting check_self_ownership_serial to false enables request placement when the local resource is a serial but requires staff mediation. Mediation rules are used to ensure the exact issue that the patron is requesting is not held locally.
If check_self_ownership_serial is set to true, and one of the below Display Logic Rules is enabled, journal offers are not presented for journals you own or have available, and the request can only be placed by staff mediation, regardless of the coverage.
- Hide service Resource Sharing Request with Ownership by the institution = true
- Hide service Resource Sharing Request with Availability by the institution = true
Multi-Volume Settings
Rapido uses the summary holding delimiter set in Alma to read the summary holdings (currently only available for mediation rules).
For matches based on the summary holdings, Rapido uses a semicolon (;) as the default delimiter. To set the delimiter you want to use, you can use the new rapido_summary_holdings_delimiters (Configuration > Resource Sharing > General > Other Settings) parameter. The parameter value can be any delimiter that you use for your summary holdings.
If the summary holdings is empty, Rapido searches the item information.
Matches are made based on mediation rules such as for Fill Locally and the Self Owned and/or Available options.
This function is currently only available for mediation rules.
For more information, see Multi-Volume Resource Sharing Workflow.
Mediation Rules
Any borrowing request created in Rapido is automatically sent to a matching lender, either based on a Rapido offer or based on locally managed rota templates. Use the Configuration > Resource Sharing > Rapido Rules > Borrowing Mediation Rules to establish rules for when requests should not automatically be filled and require staff mediation to advance the request to the next step.
Mediation rules are created with a condition that enables the request to be sent to the lender if that criteria is met. For example, consider the below rule for managing requests that have been placed for resources that are owned by the library:
- Any request that meets the criteria of Self Ownership=True is stopped for mediation.
- An ‘exit criteria’ rule requires that there is no SELF_OWNED_APPROVED label.
The result of this rule is that requests are stopped for mediation (i.e. the status is Ready to be sent) even when there is a known potential lender. To enable the request to continue its lifecycle, the operator removes the SELF_OWNED label (that is automatically assigned by the rule) from the request and adds a SELF_OWNED_APPROVED label instead.
Use the Configuration > Resource Sharing > Rapido Rules > Borrowing Mediation Rules to add labels to control your mediation rules.
Labels are automatically created based on mediation rules. Each rule's Output Parameter determines when manual intervention is required for handling a request.
For mediation rules such as Missing article/book metadata there are two optional operators:
-
In List — requires all selected fields to be filled to send the request without mediation.
-
All In List — does not stop for mediation if at least one field is filled in so that the users can send requests to lenders even if only one field is populated.
For testing purposes, see Testing Your Workflow for Borrowing/Lending Requests for creating test mediation rules.
Available Mediation Input Parameters
Below are the various mediation rules available:
- Borrowing Owning Library
- Converted from hold request
- Excel with ISBN/ISSN — Upload a spreadsheet that contains ISBNs/ISSNs that the institution does not want to allow resource sharing for those resources
- Labels
- Missing article metadata fields
- Missing books metadata fields
- Needed by date
- Partner
- Pickup Location
- Price
- Rapido request
- Request with note
- Request status
- Requested format
- Requester (only for testing purposes. For more information, see Testing Your Workflow for Borrowing/Lending Requests.)
- Requests created from blank form
- Self Owned And Available
- Self ownership
- Statistical category of requester
- Supplying Pod
- User group
- Years since publication date
Available Mediation Actions
The following actions are available for mediation rules:
- Cancel Request - automatically cancels requests when the mediation rule applies to a request.
- Fill Locally - manually fill a digital request that is readily available. Also see Automating the Process.
- Test Locally - enables libraries to interact locally to create borrowing and lending requests at the local institution for both physical and digital requests. Also see Testing Your Workflow for Borrowing/Lending Requests.
Non-Signed in Users
Use fulfillment terms of use to prevent user types from receiving Rapido offers. For example, create the below Terms of Use rule on the Fulfillment Unit of the Resource Sharing Library.
This rule enables every user to receive an offer when not logged in. When clicking the offer, the login screen appears. The login action reloads the full view page with the Rapido offer. If the rule prevents the user from receiving this request, no offer is presented.
Discovery
Rapido holdings are included in any scope configured to query the Central Index and not filtered by availability.
Scopes
We recommend configuring Rapido scopes (Discovery > Display Configuration > Configure Views).
There are two options for how to configure your scopes to work with Rapido.
- Configure one scope with one search profile and slot that contains your local inventory as well as the unfiltered Central Index. In this configuration, all results are retrieved in one place. There is no navigation between the library results and the Central Index results (Expand your search and Back to library results are not relevant).
Currently, this configuration can result in duplicate results.
- Configure two separate search profiles, one for the local inventory which consists of the institutional repository, network repository (if relevant), and records from the central index that are available. Configure a second search profile to find everything else, i.e., records that need to be retrieved from a different institution. Configure this slot to access the Central index without filtering by availability. Rapido enables smooth navigation between the two slots with the Expand your search and Back to library links so that the patron does not need to understand what each slot really is.
This can be configured by having one slot and two different search profiles or having two separate slots each with its own search profile.
EasyActive and FullyFlexible
EasyActive – all collections are automatically searchable in discovery and does not require proactive search activation by the library staff.
FullyFlexible – beyond the activation of your own library holdings, the institution controls which collections are searchable in your discovery.
Either option can be used with Rapido.
EasyActive exposes more content beyond your library collections than FullyFlexible. This enables patrons to create resource sharing requests directly from their search results rather than needing to use the blank form for their request. This avoids unnecessary errors in their requests and provides patrons with clear visibility for the request such as delivery time for Rapido offers.
Displaying Rapido Offers in Primo
You can configure the location of the Rapido offer on the Primo full view record, for example, to set it to be right below the How to Get It section.
Set this in the Full Record Services section of Discovery > View Configuration, by changing the location of the rapidoOffer row from its out-of-the-box location at the end of the section.
Rapido Holdings Index Records
The Rapido Holding Index contains the index of all Rapido library holdings. The record displayed is a single anonymized record. The index does not include records suppressed by the institution and external data sources. Additionally, only records that are included in the inclusion criteria below are included in the index.
Records that are internal to your institution and do not provide benefit to another institution should be considered for suppression from external search.
Suppression from an external search affects the global index and potentially affects searches in the library catalog using Z39.50 and SRU based on your library’s configuration of those profiles.
Inclusion Criteria
Use at least one of the following criteria:
External system number (035)
LCCN + brief title + year
LCCN + fuzzy title + year
LCCN + full title + pagination
OCLC + brief title + year
OCLC + fuzzy title + year
OCLC + full title + pagination
ISBN + brief title + date
ISBN + fuzzy title + date
ISBN + full title + pagination
IncorrectISBN + full title + date
IncorrectISBN + full title + pagination
Full title + main entry + date + pagination
Full title + main entry + date + fuzzy pagination
Full title + date + publisher + pagination + [main entry]
Full title + date + publisher + fuzzy pagination + [main entry]
Full title + date + pagination + [main entry]
Full title + date + fuzzy pagination + [main entry]
Full title + date + publisher + [main entry]
LCCN + brief title
OCLC + brief title
ISSN + brief title
Full title (not in common serials list) + place of publication + country of publication + Main entry conditional
Full title (not in common serials list) + date + place of publication + main heading (conditional) + ISSN conditional
Full title (not in common serials list) + date + main entry
Full title (can be in list of common titles) + date + main entry + place of publication
Fuzzy title (not in list of common titles) + date + main entry + place of publication
Records in the Rapido Holding Index
Below is an example from a full record in the Rapido holdings index (including a Rapido offer). The Source of the record is Global Title Index, the owning library is not included, and the information is not available for the patrons.
Rapido Offers
Rapido Labels
You can configure Rapido labels (Discovery > Discovery Configuration > Labels > Rapido Labels). Each new tile begins with rapido.tiles.xxx.
Rapido Offer Fields
You can configure the Rapido form (Settings > Resource Sharing > Rapido Request Forms Customization) by enabling or disabling any of the fields.
Configuring Rapido Tiles and Resource Sharing Options
Rapido enables you to configure when to present resource sharing requests and when to hide them. This is done via the display logic rules under Configuration > Fulfillment > Discovery Interface Display Logic > Display Logic Rules. The display logic rules that influence the appearance of Rapido tiles are:
- Resource Sharing Request
- Rapido Digital Offer
- Rapido Journal Offer
- Rapido Physical Offer
No Rapido offers are shown for external resources. There is no need to configure this via the display logic rules.
Resource Sharing Request
This option is used to control the display of all Rapido tiles (physical, digital, and journal), such as in the following cases:
- For which users (user groups) to present resource sharing services
- Whether services should be presented if the library owns the resource
- Whether services should be presented if the library has the resource available
- Whether services should be presented if a full text service is available for the resource
- Whether services should be available when a purchase request exists for the resource
- Whether services should be presented when the representation exists in Alma
- Whether services should be presented for specific Resource types — The resource types correspond to the PrimoVE resources in the Facet Resource Type labels.
If a rule exists that hides offers for specific user groups, the tiles are also hidden for non-logged in users.
When the display logic rules restrict placing requests where no offers are available, the tile indicates that No offer available at this time.
Rapido Specific Offers
The following services are specific to the type of offer:
- Rapido Digital Offer
- Rapido Journal Offer
- Rapido Physical Offer
They enable you to manipulate the display of the Rapido tiles according to specific conditions and for specific users if defined.
For example, if your institution does not offer document delivery services, you can hide the Digital Offer completely by configuring the display logic rule as in the example below. With this configuration, only physical offers appear.
Another example would be to hide the physical resource sharing offer if no terms are available as in the following example.
For more information, watch Managing the Display of Rapido Offers.
Hiding Rapido Offers for Link in Resource Records
Rapido enables you to hide resource sharing requests so that Rapido offers are not shown when the record has a direct link to the resource (the Link in Record method). Select Configuration > Fulfillment > Discovery Interface Display Logic > Display Logic Rules > New > Add Rule and hide service Resource Sharing Request. when Full Text is selected in if exists service.
Hiding Sections
Hiding How to Get It
Rapido enables you to hide the HOW TO GET IT section so that if this feature is not used by your institution, you can remove it. To hide this section, from Configuration > Resource Sharing > General > Other Settings set rapido_hide_how_to_get_it_section to false. By default, this setting is set to true.
 |
 |
|
Show HOW TO GET IT
|
Hide HOW TO GET IT
|
Hiding How to Get it from Other Locations
Rapido enables you to hide the Get it from other locations section from specific user groups or when a user is not logged in. To hide this section, from Configuration > Resource Sharing > Request Forms > Hide Get It From Other Locations select the user group(s) or check Hide section when user is not logged in.
 |
 |
|
Show Get it from other locations
|
Hide Get it from other locations
|
This should only be used for user groups that never see an offer since it hides the section regardless of any display logic rules.
To hide the section when the display logic rules hide the service, this needs to be done using CSS customization in Primo.
Sending Notes
When request_note_to_lender (Configuration > Resource Sharing > General > Other Settings) is set to true (default), notes are sent to both the borrowing and lending institutions. When set to false, notes are only sent to the borrowing institution.
This parameter is not in use for RapidILL. The note will not be included with RapidILL requests.
Display Rapido Functionality
Your institution can determine which views and slots should include Rapido functionality such as the Rapido offers, the link to access resources beyond your library collection, etc.
To enable this option on a global level, select the Display Rapido Functionality (Configuration > Discovery > Display Configuration > Configure Views > General tab and select a view to edit) checkbox. This option is checked by default.
To hide the link to expand the central index scope from the library scope (Didn't find what you were looking for? Click here to expand your search), select the Hide Rapido External Link (Configuration > Discovery > Display Configuration > Configure Views > Search Profile Slots tab and select a profile to edit) checkbox.
Shelf Expiration
To prevent items from sitting on hold shelves for extended periods of time, Rapido enables you to configure if the Maximum time on hold shelf (Days) (Configuration > Fulfillment > Library Management > Circulation Desk > Hold Shelf Information) for an item to remain on a hold shelf before being returned to the lending library should be based on the request Due Date or the Circulation Desk Hold Shelf Expiration Time. Set the parameter rapido_hold_shelf_expiration Configuration > Resource Sharing > General > Other Settings) to either due_date (default) or circ_desk.
If Maximum time on hold shelf (Days) is not defined, Rapido uses the request Due Date
Offer Message
The No Rapido Offer Message appears every time the library decides that an offer tile should not appear. This is governed by the display logic rules.
Examples of cases where this might occur: specific user groups if the resource is available locally, and others.
Configure the offer message from Configuration > Resource Sharing > Configuration > No Rapido Offer Message.
Enter the text to alert users that an item is not available for borrowing.
Self Ownership Check
The check_self_ownership_serial parameter (Fulfillment > General > Other Settings) determines whether requesting is allowed for articles without checking local ownership.
Set this to false so that article requesting is always allowed without checking the local physical inventory first.
Alma cannot determine whether the exact coverage of the requested article is in your physical holdings. Therefore, setting this parameter to false allows the patron to request the article. We recommend mediating these requests in order to first verify local availability using the Self Ownership parameter of the mediation rules.
The Document Delivery Page
Document Delivery requires configuration for integration with RapidILL. See RapidILL Based Resource Sharing Workflow.
The document download page that Alma displays when a patron clicks an email link using your institution’s CNAME (e.g., instituitonA.alma.exlibrisgroup.com) and not the classic link (e.g., https://ap01-.alma.exlibrisgroup.com...TITUTIONA_INST) link. This requires intervention from your IT department if you have not authorized the CNAME URL before.
The document download page uses the logo that is defined in your General > Alma Logo and Color Scheme menu as the login page logo.
Note to Patron
Use the Configuration > Resource Sharing > Request Forms > Note to Patron to include notes to patrons when placing their requests in the request forms.
The following HTML tags are supported:
-
Common Block Elements: <p>, <div>, <h1>, <h2>, <h3>, <h4>, <h5>, <h6>, <ul>, <ol>, <li>, <blockquote>,
-
Table elements: <tr>, <td>, <th>, <colgroup>, <caption>, <col>, <thead>, <tbody>, <tfoot>
-
LINKS: adding href to <a> elements
-
Common Inline Formatting Elements: <b>, <i>, <font>, <s>, <u>, <o>, <sup>, <sub>, <ins>, <del>, <strong>, <strike>, <tt>, <code>, <big>, <small>, <br>, <span>, <em>
-
IMAGES: <img>
Configuring Patron Queries
- Old system: Patron query templates are a basic means of configuring patron letters. You can enter multiple letters and configure the fields in the letters. You cannot edit the initial structure of the letter, but – if configured – you can edit the letter before it is sent.
This system is deprecated and will be removed in an upcoming version.
- New system: Patron query types use Alma’s flexible XSL style sheet letter configuration system for each query, which is more flexible. You can define up to thirty types of letters that will be sent when a user selects to send a query to a patron, for example, a welcome letter, a response to a request, and so forth.
Configuring Patron Query Templates
- General System Administrator
- Fulfillment Administrator
- Add a patron query template (see Adding Patron Query Templates)
- Edit a patron query template (Modify the column values in the Mapping Table Rows section).
- Delete a patron query template (select Delete).
Adding Patron Query Templates
- Open the PatronQueryTemplates Mapping Table (Configuration Menu > Fulfillment > Resource Sharing > Patron Query Templates).
- Select Add Row. Enter a name for the template in the Name field.
- In the Subject field, enter a subject. You can use the variables %reqId% and %reqName%; these will be replaced with the borrowing or lending request’s external ID or the patron’s name, respectively.
- In the Header field, enter a header, such as “Dear Sir/Madam:”.
- Enter additional lines in Query Line 1, 2, and 3. These fields are substituted into the Query to Patron Letter. For more information, see Example Letter Customization: Query to Patron Letter.
- In the Edit if Single field, enter True if the message will be open for editing, or False if the message is sent directly to the patron without any opportunity for editing.
- Select Add Row. The template appears in the list of templates.
- Select Customize.
Configuring Patron Query Types
- General System Administrator
- Fulfillment Administrator
- Add a patron query type (see Adding Patron Query Type)
- Edit a patron query type (Modify the column values in the Mapping Table Rows section)
Adding Patron Query Type
- On the Patron Query Types Code Table Page (Configuration Menu > Fulfillment > Resource Sharing > Patron Query Types), enable the relevant patron query types.
Patron Query Types Code Table
- You can modify the enabled entries' descriptions. Note that the Description column's text appears in the drop-down of query types (after selecting Send Query to Patron for a Borrowing request), and the code enables you to map the exact text to be used for each query type.
- You can select enabled entries as templates for the Send Query to Patron email and can modify the entries on the Query to Patron Letter Code Table page.
- Select Save when you are done.
Cost to Patron
Configure the Cost to Patron (Configuration > Resource Sharing > Members) to charge a patron based on their user group and the material type requested (Physical/Digital). The cost associated with digital requests is only for requests that are handled by the Rapid network.
The cost is only effective once the borrowing library receives the item.
Expand the Cost to Patron section and select Add Cost to Patron.
Add a Cost Type.
Add the groups and their cost.
Assign the cost to a POD for a selected member.
Managing Borrowing Alerts
Alerts are added to requests when information about the request needs to be communicated to the borrower.
The following alerts are currently supported and can be configured from Configuration > Resource Sharing > Manage Lending Alerts:
- CANCELLED_BY_PATRON (enabled by default)
Managing Lending Alerts
Alerts can be attached to a lending request during the main steps of a request's workflow.
The alerts show the progress of the request (In Process, Canceled, or Completed). The following alerts are currently supported and can be configured from Configuration > Resource Sharing > Manage Lending Alerts:
- Move Request in Process
- Move Request Cancelled (enabled by default)
- Move Request Completed
- Digitization Request in Process
- Digitization Request Cancelled (enabled by default)
- Digitization Request Completed
- Resend Request Received
Downloading Electronic Resources
Rapido includes the ability to select the license fields to be added to the screen rather than using the Primo screen for this flow. (Resource Sharing > Configuration > Manage Download Electronic Resource)
The following are out-of-the-box and can be deleted if they are not needed:
- Interlibrary loan print or fax
- Interlibrary loan secure electronic transmission
- Interlibrary loan electronic
- Interlibrary loan record keeping required indicator
- Interlibrary loan note
Each license field that is enabled appears in the right pane.
Rapido Letters
To configure letters, you must have one of the following roles:
-
General System Administrator
-
Letter Administrator
The following letters (Configuration > General > Letters > Letters Configuration) are used by Rapido throughout the different flows.
For information on adding non-default fields to Rapido letters, see Letter documentation for adding new fields.
| Letter Name | Letter Description |
|---|---|
|
Patron Letters
|
|
|
Resource Sharing Request Confirmation Letter
|
Rapido automatically sends a confirmation email when a request is placed to confirm with the patron that their request has been placed.
|
|
Document Delivery Notification Letter
|
When a patron has requested digital material and the send method on the request is Attach Documents - Link, this notification is emailed to patrons to provide links to the file. See Attaching Digitized Items To Be Sent To a Patron.
This letter can be sent automatically once the lending partner provides the item or when the institution uploads the file manually and sends it to the patron.
|
|
Ful Borrowing Info Letter
|
|
|
Change Rapido Request Terms Letter
|
An automatically generated letter that notifies the patron if the terms that were defined by the previous lender were changed when the request is moved to a new lender.
|
|
Query To Patron Letter
|
|
|
Lending Workflow Letters
|
|
|
Ful Incoming Slip Letter
|
A slip that is printed by the library staff from the Resource Sharing Lending Requests task list when they need to retrieve an item from the shelf to be shipped to a borrower (see the print slip description in Receiving Physical Material). You can also include a printable barcode image in this letter.
For information on extracting metadata from a lending request, see How to add information from the resource sharing request to the lender.
A shipping label can also be added as a template.
|
|
Ful Resource Request Slip Letter
|
A slip that is printed out by library staff from the Pick Up Requested Resources page when they need to retrieve an item from the shelf. For details on pickup up items from the shelf, see Pickup at Shelf. You may include a printable barcode image on this letter. The barcode is populated for item-level requests, not title-level requests. For title-level requests, there could be multiple possible items, so the barcodes appear as optional barcodes, and not a specific barcode linked to the request. This letter is also printed when an item that had a hold request is returned. This letter does not include the borrowing institution field on the letter by default. To add this field, enable the supplied_to code (Configuration > General > Letters > Letters Configuration) and add <xsl:value-of select="notification_data/partner_name"/> |
|
Lending Requests Report Slip Letter
|
A slip that is printed out by library staff for the selected requests in the lending task list that lists the availability of the items so that they can be taken off the shelf and shipped to the requester.
|
|
Resource Sharing Shipping Slip Letter
|
A user selects the Ship Item link for a lending request and then selects Automatically Print Slip = Yes on the Shipping Items page. You can include a printable barcode image in this letter.
This letter does not include the Pod ID and Pod Name by default. To add these fields, enable pod_id and pod_name labels (Configuration > General > Letters > Letters Configuration).
|
|
Request New Resource Sharing Partnership Letter |
This letter is used to contact an identified partner within the directory from the Find Partner workflow, using the Send Rapido Request action, to begin the process of adding the potential partner as a new partner.
|
|
Borrowing Workflow Letters
|
|
|
Resource Sharing Receive Slip Letter
|
A slip that prints automatically when the Automatic Print Slip option is selected for Received Items. You can include a printable barcode image in this letter.
|
|
Resource Sharing Return Slip Letter
|
Printable when returning a borrowing item to the lender. You can include a printable barcode image on this letter. The letter prints if:
The letter is not relevant for NCIP transactions.
This letter does not include the Pod ID and Pod Name by default. To add these fields, enable pod_id and pod_name labels (Configuration > General > Letters > Letters Configuration).
|
|
Resource Sharing Email Workflow Letters
|
|
|
Ful Outgoing Email Letter
|
For borrowing requests sent to a partner with a profile type Email.
|
|
General Message Email Letter (only if working with email partners)
|
An email sent to the resource sharing partner to alert them of a new general message that has been entered on the request.
|
|
Lender Reject Email Letter (only if working with email partners)
|
Sent to the borrowing partner when the lending partner has rejected a lending request.
|
|
Lender Will Supply Email Letter (only if working with email partners)
|
When a letter wants to notify a borrowing partner that they are working on a request, this letter is sent to the borrowing partner when the status of a resource sharing request changes to Will Supply.
|
|
Lender Ship Email Letter
|
Sent to the borrowing partner to indicate that the requested item has been shipped.
|
|
Borrower Receive Email Letter (only if working with email partners)
|
Sent to the lending institution when the loaned item has been received at the borrowing institution.
|
|
Borrower Return Email Letter (only if working with email partners)
|
Sent to the lending institution when the borrowing institution has returned the loaned item.
|
|
Ful Renew Email Letter (only if working with email partners)
|
Indicates that a resource sharing request has been renewed. Sent to partners automatically when a resource sharing borrowing request is sent to a partner whose Type = Email.
|
|
Ful Damaged Email Letter
|
Sent to the lending partner to notify them that a resource sharing item has been damaged.
|
|
Ful Lost Email Letter
|
Sent to the lending partner to notify them that a resource sharing item has been lost.
|
|
Lending Recall Email Letter (only if working with email partners)
|
Sent to the borrowing partner when an item is recalled and must be returned. Not used in Rapido but is used in Peer to Peer. In Rapido a general message is being used for sending recall.
|
|
Lender Checked-In Email Letter (only if working with email partners)
|
Sent to the borrowing partner when an item was checked in at the lending institution.
|
|
Lender Renew Response Email Letter
|
Sent to the borrowing partner when the lending partner responds to a renewal request.
|
|
Borrower Overdue Email Letter
|
Sent by the lending institution to the borrowing partner when a resource is overdue. When sent using ISO protocol, the request on the borrowing side is automatically marked as overdue.
|
|
Other Letters
|
|
|
Externally Obtained Letter
|
Sent to patrons; contains a URL for a requested article obtained through the CCC GetItNow service.
|
|
ARTEmail message
|
For working with the British library.
|
|
Send Rapido Request Letter
|
Rapido sends a request to a potential lender for a new resource sharing partnership.
|
|
Borrower Claim Email Letter
|
For peer-to-peer partners, the letter is sent when the Automatic Claim field is enabled on the borrowing request and the value of the Time to Claim (days) is reached. See Resource Sharing Partners.
|
|
Interested In Letter
|
Informs someone who is registered as “interested in” about a change in a PO line status. For details on interested users, see the description in Find PO Lines for Receiving Fields in Receiving Physical Material.
|
Changing the From Email Address
You can set the default sent from email address to be different from the main library email address. When rs_use_addressfrom_letter_param (Configuration > Fulfillment > General > Other Settings) is set to true (default false), instead of letters being sent from the Preferred Email Address set in Fulfillment > Library Management > Contact Information, the email is sent from the letter configuration addressFrom (Configuration > General > Letters > Letters Configuration) on the following letters:
- Externally Obtained Letter
- Lending Recall Email Letter
- Borrower Claim Email Letter
- Ful Cancel Email Letter
- Ful Renew Email Letter
- Ful Incoming Slip Letter
- Ful Damaged Email Letter
- Ful Lost Email Letter
- Borrower Overdue Email Letter
- Fil Outgoing Email Letter
- Borrower Receive Email Letter
- Borrower Return Email Letter
- Lender Checked-in Email Letter
- Lender Reject Email Letter
- Lender Response Email Letter
- Lender Ship Email Letter
- Lender Will Supply Email Letter
- Query To Patron Letter
- Rapido member letter
- Resource Sharing Request Confirmation Letter
- Resource Sharing Return Slip Letter
- Resource Sharing Shipping Slip Letter
In addition, for the following three letters, signature_email needs to be replaced in the XSL with address_from in order to prevent the preferred email address from appearing at the bottom of the email:
- Externally Obtained Letter
- Query To Patron Letter
- Rapido member letter
For more information, see Configuring Alma Letters
Document Delivery Link for Multiple SAML Authentication Profiles
For cases where a user has more than one SAML IDP profile in their system should configure the Document Delivery Notification Letter so the SAML link includes the idpCode for the correct SAML profile.
<!-- Do not remove Ex Libris workaround created variable to alter current SAML delivery page -->
<xsl:variable name="SAML_URL">
<xsl:value-of select="notification_data/download_url_saml" />
</xsl:variable>
<xsl:variable name="DOCID">
<xsl:value-of select='substring-after($SAML_URL,"digitalDoc")'/>
</xsl:variable>
<xsl:variable name="GOOD_SAML_URL">
<xsl:value-of select='concat("https:/<Alma Host Name>/services/login?auth=SAML&idpCode=<SAML IDP Profile Code>&digitalDoc=",$DOCID)'/>
</xsl:variable>
</tr>
<tr>
<td><a>
<xsl:attribute name="href">
<xsl:value-of select="$GOOD_SAML_URL"/>
</xsl:attribute>@@for_saml_users@@@@click_here@@</a>
</td>
</tr>
<!-- GOOD_SAML_URL select ends -->
Setting Up Rapid
To enable Rapido document delivery setup, you need to define Rapid as a partner and load your holdings by using the Alma Holdings Harvest for RapidILL.
Configuring RapidILL as a Resource Sharing Partner
Configure RapidILL as a resource sharing partner from the Resource Sharing Partner page (Fulfillment > Resource Sharing > Partners > Add a Partner).
For the Profile Type and System Type, select RapidILL. Enter the form details as described at Resource Sharing Partners.
On the Parameters tab, for the Default Library Owner, select the library to be used when creating lending requests. Lending requests received from RapidILL are created in the Resource Sharing Library that you select. Enter the form details on the Parameters tab as described at RapidILL Parameters. 
If you are using the RapidR integration, select Enable Rapid Returnables Integration For Rapido. This enables you to manage borrowing and lending requests from your RapidoR network via Rapido. By selecting this checkbox, a Rapid Returnables pod is added to your list of participating Pods, and you need to define its priority on the Borrowing Policies tab of the resource sharing member.
Additional Parameters
Configure the following parameters located at Configuration > Fulfillment > General > Other Settings as follows:
| Parameter | Default Value | Description |
|---|---|---|
| rs_keep_rejected_request_active | Borrowing | Keep rejected resource sharing requests active as a borrowing request to keep it open if it is rejected by RapidILL |
| borrower_document_delivery_maximum_views | 2 | The maximum number of times patrons can access the link for RapidILL document delivery. |
| borrower_document_delivery_send_automatically | true | Whether the email to the patron is sent automatically when a document is received on the borrower side. |
| document_delivery_cleanup_days | Default: 30
Maximum: 90 |
The number of days after which the digital file is deleted. |
Resource Sharing Between Libraries in the Same Alma Institution
Rapido supports performing resource sharing between libraries in the same institution. This is not a common scenario, and you need to open a support ticket to enable it.
Below are the requirements for this to be enabled:
- The libraries in the institution (IZ) do not do a pick from shelf from other libraries. Each library serves its own patrons.
- Contact support to create the relevant POD to include the libraries in the institution and to enable this specific configuration (ngrs_allow_iz_rs parameter must be set to True).
- Each member in the library must associate participating items with the POD and the pod must be set in the correct pod priority order for borrowing priorities.
Associating Pickup Locations with Resource Sharing Members
This feature enables the borrowing experience for libraries with multiple resource sharing libraries to be more efficient. By selecting Add Definition (Configuration > Resource Sharing > Configuration > Associate Pickup Location with RS Member) and adding a Pickup Location and RS Member, borrowing requests are handled by the closest or most convenient library.
- If the pickup location does not belong to a library that serves as the resource sharing library, and the pickup location is not defined, the library is selected randomly.
- If the pickup location is attached to a member, but the member is not part of the pod or Rota from where the request received the offer, the owning library is not the member defined in the configuration. The owning library is the member that was assigned when getting the Rapido offer.
Enabling Branches to Ship Directly
This feature enables institutions to define which library can ship on its own, without needing to send the resource to the resource sharing library to ship the resource to the borrowing institution.
Check Ship resource sharing resources directly (Configuration > General > Libraries > Add a Library or Edit Library Information) to allow branches to ship resources directly to a borrowing institution instead of sending the request to the associated resource sharing library.
We recommend enabling the Move to Branch to Automatically create move or digitization request for incoming request, (see Create Move Request Configuration). This creates the fulfillment request for the staff at the branch to handle without needing to access the resource sharing requests task list.
If the above is configured and the staff has fulfillment privileges in the library defined as allowed to ship resources directly from the branch while at the scope of that library, the Shipping Items menu (Fulfillment > Resource Sharing > Shipping Items) and the Scan In Item page > Shipping Items button are visible. The user can use either one of them to ship the resource. The resource sharing request is then updated accordingly, for example, Shipped Physically.
Configuring Reshelve Without Transit Rules
To configure reshelve without transit rules, you must have one of the following roles:
- General System Administrator
- Fulfillment Administrator
You configure reshelve without transit rules from the Reshelve Without Transit Rules page (Configuration > Fulfillment > Library Management > Reshelve Without Transit Rules) to set relationship rules between libraries, departments, and circulation desks so that transit for reshelving is not required between certain libraries. This reduces redundant work effort by not automatically putting items in transit for reshelving when the libraries are close to each other. This does not affect other transit types, such as hold shelf, work orders, and processing.
The default input parameter rules are empty. The default output parameter is set to False, which means all items should be set into transit when reshelving.
Each rule can be either enabled or disabled. By default, both rules are enabled.
Configuring Lending Scanning Options
You can set a message to warn users that scanning in items will complete the lending process.
Configure the Complete lending request (Configuration > Fulfillment > Physical Fulfillment > Scan In Messages Configuration) parameter (default Show message None).
If Show message is set to Popup message and 'Cancel" available at popup is set to Yes, if an item is scanned in and is part of a Resource Sharing Request that is linked to a lending request with the status Shipped Physically, a warning message requires the user to Confirm or Cancel. This prevents users from unintentionally completing the lending request.
If Show message is set to Feedback message and 'Cancel" available at popup is set to Yes, the feedback notifies the user that the request will be completed, but the scan in action cannot be canceled.
Consortia Resource Sharing
For some institutions, in specific cases, if a resource exists, and you want to create a request for an unavailable resource, the request is still created under the pod that owns it and will be filled when the selected condition is fulfilled.
To create a hold request for unavailable resources, select:
- When Resource is Unavailable in the Current Pod — don't send the request to the next pod, keep the request with the current pod until the resource becomes available
- When Resource is Unavailable in Any of the Member Pods — check all pods to see if the resource is available at another pod
If one of the above options is selected, the request will not expire, and the library card Estimated pick up and Estimated due date are updated to: Cannot be determined.
The default setting is Never. These settings are defined at the pod level. Contact support for more information.
Integrating Rapido and ILLiad
Alma institutions that are “Lenders Only” can specify whether they are managing resource sharing from Alma or ILLiad. If ILLiad is selected (Configuration > Resource Sharing > Partners) the lending request for this institution is created and can be managed from ILLiad.
When a request status changes from being calculated to presenting the Lending library details, the Lending library information and contact details are also available in the right pane.
Use the parameters User identifier regex (Fulfillment > Resource Sharing > Partners > ILLiad partner) so that when requests are passed to ILLiad, ILLiad now recognizes the identifier. By default, this field is blank.
The User identifier regex field in the example below indicates that Alma should use the identifying information until the @ to match the User identifier type Primary Identifier in ILLiad.
Integrating Rapido and Reshare
Rapido enables you to push user borrowing requests to Reshare (Fulfillment > Resource Sharing > Partners). Rapido can check whether the resource is found in the ReShare network without your users needing to leave their known discovery system. Additionally, your users do not need to enable Rapido to search for the resource they need via the various resource sharing options that your institution supports.
Enter the ReShare credentials on the Parameters tab.
The RESHARE SHARED INVENTORY CONFIGURATION section is used for searching on the ReShare network. The RESHARE OPENURL CONFIGURATION section is used for pushing borrowing requests. The RESHARE API (MOD-RS) CONFIGURATION is used for syncing Rapido with the ReShare request. The ReShare Updates Job (Admin > Monitor Jobs > Fulfillment > Scheduled tab) runs every four hours and is enabled automatically upon configuring ReShare.
Add the ReShare partner as a locally managed Rapido pod (Fulfillment > Resource Sharing > Rota Templates).
Once the partner record is added to a rota, you can order the pod priority from the Borrowing Policies (Configuration > Resource Sharing > Members) tab.
Integrating Rapido and Tipasa
You can push borrowing requests from Rapido to Tipasa to further process requests. NCIP updates are also sent to Alma as required.
This option enables requests that have not been fulfilled by a local peer-to-peer rota to be automatically pushed into Tipasa, where they are further processed as a broker-managed request. This eliminates the need to manually transfer such requests to Tipasa.
Enter Tipasa in the Fulfillment > Resource Sharing > Partners > General tab. Configure the API settings in the Fulfillment > Resource Sharing > Partners > Parameters > EXPORT TO THIRD PARTY section.
For the Export to Third Party radio button, select Yes. Enter the URL and API key as supplied by Tipasa, and the Requesting agency ID that they expect to identify your library.
The Close request when exported defines whether the borrowing request is closed after export or is managed under the same borrowing request. Since these systems are not able to use the exported request’s ID to further send NCIP messages that hook up to the existing request, we recommend setting this parameter to true, resulting in the request being closed in Alma when it is exported. A new request with a different ID is created when the item is received in Tipasa, as it is with other NCIP broker systems.
Integrating Rapido and WorldShare
You can push borrowing requests from Rapido to WorldShare to further process requests.
This option enables requests that have not been fulfilled by a local peer-to-peer rota to be automatically pushed into WorldShare, where they are further processed as a broker-managed request. This eliminates the need to manually transfer such requests to WorldShare.
WorldShare ILL can be set up in a peer-to-peer rota as a supplier for last resort (see Peer-to-Peer Resource Sharing in the Resource Sharing Guide).
From the Fulfillment > Resource Sharing > Partners > General Information tab, select NCIP as the Profile Type and select WorldShare ILL as the System Type.
Configure the API settings in the Fulfillment > Resource Sharing > Partners > Parameters > EXPORT TO THIRD PARTY section.
For the Export to Third Party radio button, select Yes. Enter the API key and Server URL as supplied by WorldShare ILL, and the Requesting agency ID that they expect to identify your library (e.g., the institution's OCLC symbol in OCLC-XXX format).
The Close request when exported defines whether the borrowing request is closed after export or is managed under the same borrowing request. Since these systems are not able to use the exported request’s ID to further send NCIP messages that hook up to the existing request, we recommend enabling this parameter, resulting in the request being closed in Alma when it is exported. A new request with a different ID is created when the item is received in WorldShare, as it is with other NCIP broker systems.
Integrating Rapido and Relais
Relais can be configured in a resource sharing rota as a supplier of last resort (see Peer-to-Peer Resource Sharing in the Resource Sharing Guide).
From the Fulfillment > Resource Sharing > Partners > General Information tab, select NCIP as the Profile Type and select Relais ILL as the System Type.
Configure the API settings in the Fulfillment > Resource Sharing > Partners > Parameters > EXPORT TO THIRD PARTY section.
For the Export to Third Party radio button, select Yes. Enter the API key and Server URL as supplied by Relais ILL, and the Requesting agency ID that they expect to identify your library (e.g., the institution's OCLC symbol in OCLC-XXX format).
The Close request when exported defines whether the borrowing request is closed after export or is managed under the same borrowing request. Since these systems are not able to use the exported request’s ID to further send NCIP messages that hook up to the existing request, we recommend enabling this parameter, resulting in the request being closed in Alma when it is exported. A new request with a different ID is created when the item is received in Relais, as it is with other NCIP broker systems.
Configuring an ALA Profile Type
From the Fulfillment > Resource Sharing > Partners > General Information tab, select ALA Email as the Profile Type. The System Type defaults to Other.
From the Parameters tab, enter the email address that should receive the ALA form.
Data Sharing Profile
To enable resource sharing shareholding information, you must have a General System Administrator role.
The Data Sharing Profile (Configuration > General > General Configuration> Data Sharing Profile) option enables institutions to shareholding information for resource sharing purposes. When set to Yes, this indicates that the institution has agreed to share its information. The default setting for this option is No. We strongly recommend setting this option to Yes.
For more information, see Data Sharing FAQs.
Configuring Rapido Jobs
Rapido supports batch automatic delivery of digital lending requests from a configured folder. This functionality uses the Automatically Ship Rapido Digital Requests (default Inactive) (Configuration > Resource Sharing > General > Rapido Jobs Configuration) job to scan a configured folder to then attach files to the right request. The attached files are then automatically sent to fill the borrowing request. Configuring this job enables staff to skip manually attaching files to individual lending requests. To enable automatic processing for lending requests with scanned resources saved in a folder, use the Automatically Ship Rapido Digital Requests job.
The Automatically Ship Rapido Digital Requests job relies on the file names being saved with the internal identifier of the lending request.
Select Add Row and select the S/FTP Connection Type (as configured in Configuration > General > External Systems > S/FTP definitions) and Rapido Member. The job can be scheduled hourly, daily, weekly, or monthly, or you can Run Now.
When using this job, the lending files should be saved with the internal identifier name.
The Digitization Workflow Setup (Configuration > Fulfillment > Copyright Management > Digitization and Copyright Rules) determines what kind of output the borrowing institution receives, based on what output type (link or attachment) is selected in the Select digitization target drop down list. When the job is run, a folder AutoShipFileTmp is created in the institution's root directory folder with a folder for shipped files and a folder for failed deliveries.
Disabling Lending Hours in Rapido
To disable resource sharing lending hours, you must have a General System Administrator role.
- Select Configuration > General > Libraries > Add a Library or Edit Library Information.
- From the resource sharing library Summary tab, select Temporarily inactive for lending.
- If relevant, select the Inactive dates range.
Temporarily deactivate lendingThe date range does not determine when lending resumes. To resume lending, the library must manually deselect the Temporarily inactive for lending checkbox.
If there are active lending requests that cannot be filled due to the need to become temporarily inactive for lending, staff can reject these requests to move them to the next partner.