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.


3 results found

  1. Resupplying a Request - be made avaliable for non - rapido requests

    "Resupplying a Request"

    Currently "resupply" a document on the Lending side is possible only for Rapido/RapidILL requests and not other Alma Resource Sharing Partner requests such as requests from ISO LADD partners.

    However most Alma libraries have requests coming from difference sources and now this feature is creating different workflows, making it too hard to use, i.e. Rapiod request can use "resupply", Non Rapid requests via ISO partners cannot, staff will have to use email to resupply.

    We'd like to see all requests coming into Alma can be resupply using this feature.

    Case #07262909


    Currently "Resupplying a Request" works if…

    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  ·  Integrations  ·  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. Use of RFID in "Shipping Items"

    The button "Read RFID" should also be available in "Shipping Items" (Fulfillment --> Resource Sharing: Shipping Items) to scan in items.

    8 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)
  3. Enable back-and-forth of requests between Resource Sharing and Purchase Request

    Request Description: Often we’ll send requests that are difficult to get via resource sharing to acquisitions by creating a purchase request from Rapido. However, in doing so create a separate request and never find out whether the patron actually got their item. This means that if a patron comes with us with questions, we can’t answer them. (Is acquisitions working on it? Did they cancel it? Who knows!) It also means that if acquisitions can’t purchase the item for some reason, they have no way to send the request back to us so we can try again with those more…

    9 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)
  • Don't see your idea?

Feedback and Knowledge Base
https://ideas.exlibrisgroup.com/forums/935112-rapido?category_id=403746
ideas.exlibrisgroup.com
CC-MAIN-2024-38
149701
application/http; msgtype=response
sha1:ERZH5KHXZFU5HZ7C2R4LUJ4DZ3O6IBP3
<urn:uuid:f69c8bb7-0aa4-4bc9-80a2-610c6375f3b2>
2024-09-20T03:51:48Z
104.17.29.92
text/html
sha1:SNRASBRNX3CXQQIGF6JUDBPOOFUZYZHL
<urn:uuid:6072d111-1399-4c5d-80c7-f12a2e36ecb9>
https://ideas.exlibrisgroup.com/forums/935112-rapido?category_id=403746
response
<urn:uuid:cbd657ec-eaa2-4c3f-9103-5b4f4aaaaf8a>
isPartOf: CC-MAIN-2024-38
publisher: Common Crawl
description: Wide crawl of the web for September 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-217
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/