Skip to content

ILLiad Ideas

← Atlas Systems

How can we improve ILLiad?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

6 results found

  1. Fill in Lending DueDate field when TN is in other transactionstatus other than Awaiting Lending Request Processing

    If lending loan requests come in via Rapid and are routed to Awaiting Stacks Searching via a Routing Rule (because they already have the location and callnumber), the lending request never gets the DueDate assigned automatically because that only happens the first time a TN is opened from the Awaiting Lending Request Processing status. Could ILLiad somehow set that DueDate even though the Awaiting Lending Request Processing status is skipped?

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  RAPID  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Allow RapidR borrowing renewals to be sent in batch by the Send OCLC Renewal Requests button

    Currently, the Send OCLC Renewal Requests button will send out renewals for all requests in the status of "Renewed by Customer to MM/DD/YYYY", but it only works on requests with a SystemID of OCLC. Now that RapidR allows renewals within ILLiad, it would be helpful to be able to batch send requests to Rapid using the same button, so that renewals can be sent out regardless of the System ID.

    The query that populates the ESPUpdate table is currently:
    "SELECT t.TransactionNumber, t.ILLNumber, t.SystemID FROM Transactions t JOIN Users u ON (t.Username = u.Username) " +
    "WHERE ((t.TransactionStatus LIKE N'Renewed by…

    15 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  RAPID  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Cancel Rapid pre-shipment requests from within ILLiad Client

    Staff would like to use the ILLiad Client to cancel Rapid borrowing requests that have yet to be marked as Shipped by a Rapid lender.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  RAPID  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Incoming Lending RapidR to reflect default Renewal setting in Customization Manager

    Incoming Lending RapidR requests in ILLiad are set to be "No Renewal" by default. We wanted to change it since we now allow renewals, yet our Loan labels print as "No Renewal." A borrowing library pointed out that it is confusing when they process Receives.

    I was told by OCLC and Rapid (Exlibris) that RapidR requests do not reflect the "LendingRestrictDefault" keys for Renewals, Photocopying, and Library Use Only in Customization Manager.

    I wish Lending RapidR requests could reflect these default values the same as OCLC Loan requests in ILLiad.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  RAPID  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Ability to select which ILLiad field that RAPID call numbers and locations populate.

    We love the electronic links and holdings information that RAPID auto-populates in our ILLiad lending requests, but we currently use our call number and location fields differently in our ILLiad instance. It would be great to be able to decide which fields the links and holdings information from RAPID would populate.

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  RAPID  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Allow RAPID to match on a DOI number

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  RAPID  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

ILLiad Ideas

Categories

Feedback and Knowledge Base

(thinking…)