Skip to content

ILLiad Ideas

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

146 results found

  1. Track flag history along with status history of each request

    It would be really useful at our library to be able to track flag history in the Staff Client along with status/queue history of each request. We would love to see what flags have historically been added to a request, and when and by whom they were added and removed.

    There are several flags in our system that stay on requests indefinitely because that's the only way we can identify and run reports on those requests specifically. There are also many times it would be useful to see who applied a flag to a given request so that follow-up clarifying…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Staff client  ·  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 customization of shortcut actions

    Staff will perform the actions that produce "shortcut" actions in ILLiad accidentally. These should be able to be customized or turned off to prevent accidental prompting of processing steps. (https://support.atlas-sys.com/hc/en-us/articles/360011911733-Tips-and-Shortcuts-for-ILLiad

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Add ability to "pin" or "favorite" staff Note in ILLiad request

    In cases where staff have the need to re-use the text of a staff note in an ILLiad request, it would be helpful to enable functionality to "pin" or "favorite" a specific note at the top of that day's listing of notes so as to get there in a single click, without having to scroll down to it (or to have to type in the beginning text for that needed note in the Recent Notes field, in order to auto-suggest).

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Expand the group maintenance functionality to include settings that persist for specific groups such as if renewals are permitted and the le

    Expand the group maintenance functionality to include settings that persist for specific groups such as if renewals are permitted and the length of renewals for specific groups. One group we are a part of has expanded renewals to 17 weeks - we want this for that group but not for everyone so it would be nice to be able to customize more than just initial loan length based upon the borrowing library's group.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. renewal

    Add the ability to specify length of renewal to the groups management tab. Since we can set loan periods based upon group, renewal length should also be able to be specified for each group.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Connection Manager stops importing Lending when invalid unicode character in a lending request gets stuck

    Sometimes an OCLC lending request includes a unicode character that keeps it from being able to be imported into ILLiad. Right now sites just notice this is happening because Lending requests get stuck behind it. And until the OCLC request is cancelled via Worldshare, the Lending requests aren't able to be imported.

    Could there be a way for staff to see that this is the issue in the Connection Manager log in the client, or something else?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Allow ILLIAD staff to customize name of column labels.

    Hi,

    I'm having to do a lot of re-organization of my data after I've created a custom report from ILLIAD. I find myself renaming columns so I know what data I'm looking at. If there was a feature that allowed us to rename the columns in the backend, this would be great for resource sharing managers who have to report on this dataset!

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Additional request field auto-copying functionality (user-by-user basis)

    Currently, the CopyTitleToClipboard key in ILLiad Customization Manager allows for the auto-copying of the request title. However this setting is global for all users, and can only turned off or on by Process Type (Borrowing, Doc Del, Lending). It would be helpful to provide individual staff with the ability to override the auto-copy functionality, solely on their client, in order to either choose another field to auto-copy (e.g., Transaction Number), or alternately not to auto-copy any field when opening a request. The general setting (via the CopyTitleToClipboard key) would remain active for any staff members who did not "opt out"…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Make Illiad fields searchable regardless of including accent marks/special characters

    Allow the ability to do searches in ILLiad & pull up the correct results regardless of whether that field has a special characters or accent marks, etc. For instance, doing a patron last name search for Peña, should pull up with Pena or Peña (currently it has to be an exact match). Same thing with titles & authors, if the title has accent marks or special characters, we cannot pull up the request without also including the special characters/accent marks.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Lengthen conditional message

    The Lending Notes field in OCLC has a character limit of 500 characters, but ILLiad will only put through 255 characters. Would it be possible to increase this?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Have Lender Select box consider Odyssey and email addresses too

    Atlas support said recently that only the shipping and billing address fields are checked for incoming ILL requests. Libraries often change their contact info. and it would be best if the system is checking for that too in order to avoid outdated Lender records in the Client and misdeliveries

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Allow applying field/layout/grid customizations to all users in Staff Manager

    Please make it simpler to set customizations for all staff, including future ones. Currently, field customizations that are applicable to all users must be applied to new users one-by-one.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Add another note type

    We like to hide our staff notes (via customization manager), but it would be nice to have another option for adding notes viewable to the user. Perhaps a Staff-hidden and Staff - so we could hide some notes but make others visible to the user in their account/request.

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Clear OCLC search filters when a request is closed

    When searching for harder to find items in OCLC through ILLiad, we often use the custom search or set filters in the Limits box. The search terms and filters stick from request to request. The worst problem is that if I filter by year, this doesn't appear obviously in the limits, but when I search the next request by ISSN/ISBN nothing comes up. I have to remember to open Limits and clear the year from the filter.

    It would be so helpful if these fields would just reset with every request. There isn't any case where I want the same…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Support for Controlled Digital Lending Software and Workflows

    Ability to identify requests that will use the lend-like print method using an owned-to-loan ratio, manage due dates, etc. Details on CDL can be found here: https://controlleddigitallending.org/.

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Update Lender Billing Fields and Description on Transaction Form

    Adjust the availability of lender address fields in the transaction form.

    Remove Billing Notes from the Transaction view in the Client. Dev believes this is an artifact from before lending billing was split into 2 parts and we have been unable to populate it with data.

    Add LibBillingMethod as an option for addition to the layout. It's available in the LenderAddress record view, but not the transaction form view.

    Rename the "Billing Groups" label in the Transaction form's Library tab. These are just groups and should not be described as specifically related to billing.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Fulfillment Data should be included in Custom Search results

    Custom searching for transactions doesn't return information from the FulfillmentData table. We need to be able to calculate money spent through DSP addons like Reprints and Get It Now and there isn't any other way to gather that information out of ILLiad, other than using an ODBC link and an external program.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add User Expiration Date as an option for Customized Layout in 1-borrowing form, and 2-Check In From Lending Library batch screen.

    We'd like to be able to see the User Expiration Date in the client on the borrowing request form and the borrowing batch process "Check In From Lending Library." This would help us when assigning due dates and renewals (in case we need to truncate what the lending library offered), and may also determine where we send initial requests as well. At the moment, User Expiration Date is not in the list of fields to choose from when customizing layouts.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Increased Granularity in Web Circ Permissions by User

    I would like to be able to restrict available actions in Web Circ by user. I would like to restrict our circ desk account from being able to do anything other than check out items. I think essentially I'd like the customization keys to be available on a by-user basis.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Create a read-only/distributable form of dbc files or the SQL Alias Manager

    With SQL Alias Manager 1.3.2 staff with local admin privileges on their desktop or VM’s are no longer able to successfully Set Default (Local Machine) without also requiring Full Control privileges on the folder where the DBC’s reside.

    In a shared environment this is an issue because we wouldn't want everyone to have full read/write access to a shared folder where someone could potentially change a dbc file for every staff member. This wasn't an issue with SAM v1.2.2.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Feedback and Knowledge Base