Skip to content

RapidILL

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.


6 results found

  1. 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…

    17 votes
    0 comments  ·  Holdings  ·  Admin →
    How important is this to you?
  2. 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 .

    7 votes
    1 comment  ·  Holdings  ·  Admin →
    How important is this to you?
  3. 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.

    17 votes
    0 comments  ·  Holdings  ·  Admin →
    How important is this to you?
  4. 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.

    11 votes
    0 comments  ·  Holdings  ·  Admin →
    How important is this to you?
  5. 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?

    32 votes
    0 comments  ·  Holdings  ·  Admin →
    How important is this to you?
  6. 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.)

    21 votes
    Under Review  ·  0 comments  ·  Holdings  ·  Admin →
    How important is this to you?
  • Don't see your idea?

Feedback and Knowledge Base