Skip to content

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.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

65 results found

  1. Limits for RapidILL scan from print requests

    Since all Rapido scan requests are converted to RapidILL requests and thus have a 24-hour service commitment, we’ve been noticing an unmanageable workload on Mondays with requests coming in over the weekends. Prior to dropping OCLC we could balance our workload by doing the urgent requests first and the less urgent requests another day, but now all of our most time-consuming requests are also urgent.
    Possible solution: Limiting the number of scan from print requests that can be assigned to one library at one time.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Allow patron to delete pdf from Primo after downloading locally

    Allow patron to delete pdf from Primo after downloading. This helps patrons manage very large lists of received pdfs. Some of our patrons are used to being able to delete received pdfs after downloading them locally, since this functionality was available in Illiad.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Discovery  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Stacking requests functionality for scanning items

    We will occasionally receive multiple digitization requests from the same item from the same school or from different schools. The issue is that Alma only writes one request to the pick from shelf at a time. This would work for physical requests, but for digital scan requests, its not the most efficient workflow.

    For example we receive two requests, one for chapter 2 and one for chapter 3 - whether they go to the same or different schools is not relevant.

    The current workflow is:
    a. request writes to pick from shelf
    b. staff retrieves item from the shelf
    c.…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Convert to Resource Sharing should not be an option on the pick from shelf, when the item is a lending request from another school.

    Convert to Resource Sharing should not be an option on the pick from shelf, when the item is a lending request from another school.

    As we understand it, "Ship Digitally" requests should be Cancelled and "Patron digitization requests" should be Converted. However, requests in the pick from shelf lists don't show this distinction and both "Cancel" and "Convert" are options in the row action. To minimize confusion, we would prefer to gray out or hide the "Convert" option for a Ship Digitally? request.

    We've been telling staff to try to Convert first, and if they get an error, then go…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Field on Borrowing Request form for non-Rapido lending library's identifier (TN number ILL number, etc.)

    Idea: Create a field on the borrowing request form for the "Lender's Identifier". This field would either map from an ISO Illiad request (or other request), or be keyed in by the borrower when receiving or externally ordering a physical item. The lender's identifier in these cases would be the "Illiad TN number" or "OCLC Request ID" as a couple of examples. This field would also appear in the receive workflow.
    It would also be beneficial to have this field included on the Resource Sharing Return Slip Letter in case the lender's paperwork goes missing. This will help facilitate a…

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 4 Next →
  • Don't see your idea?