Your feedback matters to us. Help us improve RapidILL by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
20 results found
Electronic holdings should take priority over physical holdings
Currently, the format is not a parameter of the algorithm used to select the most appropriate partner. Electronic holdings should take priority over physical holdings: this would avoid institutions to digitize print materials (operations that take time and human resources) while others may have an electronic version that can more easily and quickly be provided.
If Partner A has an electronic access and Partner B has a physical holding (and things like time zones being equal), Partner A should receive the lending request in priority.157 votes
Defining Work Week permanently
It should be possible to define our work week permanently, and not via Lending Off every week. For example, our work week is Sundays-Thursdays 8:00-17:00 (not Monday-Fridays). Also, it should be possible to define Lending Off via Alma, and not just via the Rapid interface.79 votes
Alma/Rapido notes: Reason for rejection should be passed on through RapidILL
Currently, the only notes passed on in a RapidILL-Alma integration are notes given as part of the bad citation workflow.
However, as borrowing library, in order to reasonably notify the patron why a request is rejected, the note containing the reason for the rejection by the lending library also needs to be passed on into the borrower's Alma/Rapido.79 votes
Reducing turnaround times
Since each lending library can hold a request for 4 working days, sometimes files are received after a long time (for example: if there are many libraries and each one takes 4 days to Unfill, before one library eventually fills it).
A solution to this could be to treat requests with only one match differently than requests with many matches, e.g., reduce the holding time for requests to 2 days when more than 1 library holds the item.75 votes
updating Lending requests to Filled without sending the file
Sometimes libraries update Lending requests to Filled, but do not actually send the file via RapidX or any other way.
There should be a way to indicate that the file was not actually sent to the Borrowing library.57 votes2 comments · Other · Admin →
Show dates in a format suitable for global users
In the RapidILL interface dates are displayed in US format. With RapidILL now a global phenomenon this can be confusing for users in other regions which do not use M D Y.
A date like 10/06/2022 - could be interpreted either as 10 Jun 2022, or 6 Oct 2022.
Please use a format like 05 Sep YYYY - that should prevent confusion and make work more efficient outside of North America39 votes
Currently, when you submit a request with an ISBN, Rapid does not also search for the ISBN of the Ebook, or vice-versa. This is not the case with Journal requests, Rapid does search for alternative ISSNs of print journals and ejournals.24 votes
Submitting requests via Alma using DOI
Currently, Rapid accepts requests from Alma with ISSN / ISBN and OCLC number. It should also be possible to submit requests that only have a DOI.21 votes
Please allow sites to FTP holdings files to RapidILL. That way we could automate and do on a more frequent basis.
We have two ExLibris products: RapidILL and Summon. It it frustrating to have to use two completely different processes to send holdings records. RapidILL is especially frustrating because it's a web interface and files can't be sent with FTP. (We're a SirsiDynix site - we have a report that can automatically extract and FTP records to a third party site. It works beautifully for Summon.)20 votes
Support issue and article-level linking
Rapid should support issue-level requesting. We would love our lending requests to come in with accurate issue level data.
Related, when RAPID provides a link to owned/licensed material for a document delivery request, we get journal-level data. But, it would be ideal if the link generated were for article-level links through the link resolver. We use 360 Link, also owned by Ex Libris, so perhaps there is an opportunity for cross-walking these products?19 votes
Customising Reasons for Rejection
As it stands, we cannot customise the choice of reasons for rejection when we reject a lending request. It would be useful to be able to configure this to make them clearer, and have reasons that we find the most applicable to the type of requests we get. For example, having one that is more applicable to specific copyright restrictions, or when we have an access issue. As well as this, it would be useful to remove reasons we don't use.18 votes
Rapidill lending requests: Locate item on loan
We often get scan lending requests from Rapidill for items that are on loan. It seems that the Rapid locate mechanism should be improved.14 votes
Incorporating non-English phrases into holdings upload to Rapid
It should be possible to upload non-English phrases into the Rapid process for parsing years and coverage data.
Our description field is in Hebrew, which means that the data is ignored, when Rapid tries to upload it. As a result, requests are automatically sent to Rapid instead of being rejected as Locally-Owned. This causes unnecessary work for other libraries, and in many case, a delay in supply to the patron.14 votes
Problem with Hebrew Numerals in Publication Dates and Volumes / Issues numbers
When we submit requests to Rapid that have Publication Dates and / or Volume/Issue Numbers with Hebrew numerals and / or apostrophes, Rapid is not able to identify locally-owned items, or to accurately locate possible Partners.13 votes
Make Holdings Status Page & Upload Process More User-Friendly
Currently, the holdings upload process is a bit of a black box. There are no notifications to tell libraries that our holdings uploads have failed. So, we have to keep checking the Holdings Status page (https://rapid.exlibrisgroup.com/Holdings/Status) to see if our uploads went through, and submit a ticket if they don't. Failed uploads are still marked as “In Progress”. Because of this we have to wait 24-48 hours to establish that the process has stalled and requires intervention. If we notice a failure, Support cannot tell us what caused it because data from past uploads is not retained. A failure of one holdings upload in a particular file type causes all the others in that file type to fail, even if there’s nothing wrong with the other files. Since Support cannot tell us what caused the failure, we just have to check all the files for potential fail points.
To help libraries remedy holdings upload failures more promptly, so that we can ensure more accurate holdings and a better request experience for our users, I propose the following enhancements to the holdings upload process and Holdings Status page.
1.) Create notifications that will alert libraries when a holdings upload has failed and, ideally, why it has failed.
2.) Implement more granular batching of holdings uploads, so that a failure of one holdings file does not result in a failure of every other file of that type. As we understand it currently, a failure in the print books upload would also cause the electronic books upload to fail, even if there was nothing wrong with the electronic books holdings file.
3.) Provide granularity in the “Last Index Date” field for holdings format and type. Currently, that date only reflects the last index for the entire holdings type. In the current system, if we upload electronic journals on October 5 and print journals on November 9, the Last Index Date will read November 9 for both sets of holdings, even though the electronic journals really have not been indexed since October 5.
4.) Introduce more meaningful and specific status indicators. Mark a failed holdings upload as “Failed,” “Paused,” or the like, not “In Progress”.
5.) Provide more thorough documentation of how to interpret the Holdings Status page. The Knowledge Center documentation is very sparse. We only really understood what was happening behind the scenes after repeated questions to a patient Support rep. (Thanks, Neta!)
Currently, the holdings upload process is a bit of a black box. There are no notifications to tell libraries that our holdings uploads have failed. So, we have to keep checking the Holdings Status page (https://rapid.exlibrisgroup.com/Holdings/Status) to see if our uploads went through, and submit a ticket if they don't. Failed uploads are still marked as “In Progress”. Because of this we have to wait 24-48 hours to establish that the process has stalled and requires intervention. If we notice a failure, Support cannot tell us what caused it because data from past uploads is not retained. A…9 votes
Search Holdings in Rapid Interface
The Search Holdings feature for books is very limited, it doesn't include the Author or Publication Date. Conducting the same search under Borrowing>New Request is inconvenient as there are four required fields.9 votes
Ability to throttle the number of lending requests
We would like the ability to throttle the number of lending requests our institution gets. As a larger institution, we receive about 150 lending requests a day during the school year. We know RAPIDILL staff can do this for us, but we can occasionally have a student out sick and that dramatically decreases the amount we are able to scan. If we could cap our print holdings requests ourselves quickly, this would help us especially during the summer or holidays.4 votes0 comments · Lending · Admin →
Separate Mapping List into book chapter lending and whole book lending rules
Please consider adding could the ability to separate the mapping list between chapter lending and whole book lending. More of our collection is available for chapter scanning than whole book Rapid Returnables lending. For example, we could scan a chapter of a reference book but we would not provide the entire book via Rapid Returnables. We have put in place the more restrictive lending rules as there's no way to distinguish between chapter scanning and whole book lending in the mapping .3 votes
Require members to send OCR'd files
RapidILL members should be required to send OCR'd PDFs.3 votes0 comments · Lending · Admin →
Export monthly borrowing/lending summary reports
Under Tools > Statistics > Lending Summary/Borrowing Summary, the statistics shown on the screen can drill down to monthly level but when I clicked on Excel, the file does not breakdown to monthly level. We had to resort to copy and paste from the screen into an Excel file and format it. It would save staff time if the export includes the monthly statistics.2 votes0 comments · Other · Admin →
- Don't see your idea?