Rapido
Your feedback matters to us. Help us improve Rapido 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.
8 results found
-
Due dates synchronized with the calendars of libraries
We noticed that Rapido does not consider closing periods entered in the calendar of the library. The due dates of Rapido requests are therefore not based on that calendar, while the due date of the loaned temporary item is. Consequently, a mismatch occurs, which in addition interferes with the renewals.
We would like:
1. Rapido considers the closing periods entered in the library calendar in Alma.
2. Rapido synchronises the borrowing and lending requests due dates.188 votesCurrently this is not planned. Thank you for this submission.
-
Renewal options
With Rapido, renewals are restricted to five times. With Fulfillment, renewals are based on a maximum number of days (and are not limited on x-times). We would like to have a parameterization option that allows the following: Renewals in Rapido should also work according to the logic with the maximum number of days (and not limited on x-times)
115 votesHello,
Thank you for this idea. After thorugh discussion and consideration we need to update you that this functionality will not be pursued. We are updating the status to closed in order to release the associated votes to continue and encourage further engagement with ideas from the Rapido community.
-
Place reservations on title level instead of item level
When a user creates in Rapido a reservation on a copy that is not available, the reservation should be created at the title level. Because, if there are multiple items not unavailable, the reservation is placed on a specific item. If another item becomes available sooner, the reservation is not moved to that item. The patron has to wait for the item that was reserved when the reservation was placed, even if another item might be available sooner. For this reason, a reservation should be created at the title level instead of the item level.
75 votesThank you for this submission. We will not be pursuing this development at this time.
-
Prioritization of reservations
In a system, where users can create a reservation either via the get-it section or via the Rapido-Tile, the reservation from the get-it section currently have priority over reservations made via the Rapido-Tile. Our wish is, that the reservations are fulfilled in the order of their creation date, regardless of how they were created.
104 votesThank you for this idea. We have reviewed and will not be adding this functionality at this time.
-
Prioritization of the libraries in a given pod
The Rapido lending request distribution algorithm does not allow the different libraries in a pod to be prioritised. This would be useful to ensure that in case of multiple items the most staffed libraries are given priority in the attribution of requests, and to prevent small libraries from being overwhelmed by lending requests.
84 votesHello,
Thank you for this idea.
We have reviewed and determined that this functionality will not be added to the roadmap at this time. Current functionality support ordering pod priorities, load balancing within each pod, and additional pods can be created as needed by the community. I am closing this idea to release the votes back to the community.
-
Configurable lending request reject reasons
There are currently 25 lending request reject reasons in Rapido. That is too many, many that don't make sense for our institution and workflow. We would like to be able to configure the lending request reject reasons - add some, remove some, and rename some. There is currently no table in Alma to do this and Ex Libris cannot update this through a service request either.
The 25 lending request reject reasons as of March 2, 2023 are listed in the file included in this Idea Exchange.73 votesThank you for this submission, this idea will not be implemented at this time.
-
Expected arrival date
Instead of telling the patron a specific length of time, it will take to get an item, or a specific date when it is expected it would be better to have a range of time e.g. instead of 7 days, 7-10 days, and instead of 11/02/22, 11/02/22-11/04/22. This would help account for business days and delays in shipping.
41 votesHello,
Thank you for this idea submission. Pod terms are a set number and the visibility of these terms are what shows to end users. Pod terms as ranges are not under discussion at this time. A configuration option is to customize the text in the labels on the offers. Some examples we have seen are to customize the language to align with campus tone and messaging, sometimes this looks like estimated delivery or business days.
-
Exclude Rapido temporary bibs from Alma's Authority Control Task List
Currently, when a patron places a borrowing request through Rapido, a temporary bib. is created and appears on the Authority Control Task List in Alma. This is problematic for the Cataloging staff who rely on the Authority Control Task List to identify authority updates needed on local records.
As a Cataloger, it is hard to identify these Rapido temporary bibs. even if they are suppressed since institutions may have other suppressed records. It is also currently not possible to exclude them from the Task List.
We would like a way to filter the Authority Control Task List to exclude Rapido…
40 votesThank you for this idea. This will not be implemented at this time. The facet of Suppressed from Discovery within the Authority Control Task List may be useful.
- Don't see your idea?