Skip to content

ILLiad Ideas

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

29 results found

  1. Ability to suspend patron from loans while still allowing requests for article copies.

    We have users who cannot be trusted with book loans, but I still want them to be able to request articles. I'd like a way to block loans but not articles.

    44 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)
  2. I'd like to have the power to make mass changes such as changing Department Names.

    example: Our Political Science department changed their name. I want to be able to make this change to all the existing patrons it would apply to.

    20 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. Fix the "Illiad Authentication" Checkbox so it Does not Automatically Enable itself when Saving a New User Record

    Leaving the ILLiad Authentication checkbox unchecked/unchanged when creating a new user will default the user to ILLiad Authentication type.
    Leaving the "ILLiad Authentication" checkbox unchecked/unchanged while creating a user in the Client still defaults to ILLiad Authentication when the user is created, even though the option is not checked when saving. This bug has been around for awhile with no fix in sight. Can this please be addressed in a future Illiad release? No one can remember to go back and uncheck that box constantly.

    This is currently logged as Bug# 12841

    15 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. Transfer User Notes when merging users

    When an existing user account is merged with an new one, in addition to moving the open requests, we would like any User Notes to be moved as well. We use these notes to track various issues with patron accounts and right now staff are manually copying each note.

    15 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. Add the ability to anonymize ILLiad transactions

    There have been requests for a tool to allow sites to anonymize ILLiad transactions similar to the old break the user link scripts. Would like to be able to preserve stats while maintaining confidentiality for patrons.

    11 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. Proxy User Functionality

    We have teaching assistants/administrative assistants/research assistants who are asked to request materials on behalf of an other ILLiad user. It would be helpful if a proxy account could be created for these assistants to create the request, but for the primary user to be responsible for the item (loan) and notified of delivery (article).

    10 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 API to Add, Remove, and Update records in the UserValidation table

    Stanford U is locally hosted and has a custom job that imports users directly into the Users table. This job will update users based on any change event triggered in the Registrar's database. It creates many users that never end up using ILLiad. We would like a standard method of creating a process that pushes users into the UserValidation table and can update users, regardless of their being in the Validation table or in the Users table.

    8 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. ILLiad stub accounts made when users fail to complete the registration process should be assigned to an NVTGC in use.

    When an ILLiad stub account gets made due to incomplete registration it should not be assigned to a site not in use like "ILL." Allow users to configure what site/NVTGC those stub accounts should be assigned to.

    8 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. Allow API to update existing users

    This is similar to the request to "update user account by pulling user data from org directories via Single Sign on"

    7 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. When non-OCLC library creates an LWeb account, have a registration workflow built in to check legitimacy before they can submit requests

    We want non-OCLC libraries to be able to create their own accounts, and to be able to make that process more transparent. However, right now, anyone can create an account and immediately place requests.

    After catching some illegitimate requests entered in this way we made a routing rule to review LWeb requests, but it would be better to have the workflow built into the system, so we can better manage approving, expiring, blocking, and communicating with non-OCLC libraries.

    7 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. User expiration by status

    Ability to control user expiration based on User status i.e. I don't want Faculty accounts to expire. Or only expire undergraduate accounts.

    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)
  12. When creating new users in the staff client, default to electronic notification options

    Currently, none of the notification check boxes are checked by default on the new user form. Staff have to remember which of the check boxes to check to set a new user to receive all electronic notifications. It would be good to have a setting that made those check boxes checked by default.

    5 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 a way to reveal what you type in the password change box

    Add a way to reveal what you type in the password change box so staff can make sure they have typed in what they think they've typed in.

    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)
  14. Encrypt Passwords in Customization Manager

    Having an email password in plain text available to anyone with Customization Manager rights is a security risk.

    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)
  15. Account History Details

    It would be nice to see a User History tab on their User window. For example, what link did they come from to create an account, what time stamp they entered Users to Clear, transfer history, etc.

    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)
  16. SAML multiple attributes (allow for multiple and to list those which are allowed)

    We have come to understand that ILLiad's SAML module does not support SAML2 attributes sent by the Identity Provider with multiple values. These would take the basic form in the SAML assertion XML like:

    <saml:Attribute Name="multiAttributeName">
    <saml:AttributeValue>Value 1/saml:AttributeValue
    <saml:AttributeValue>Value 2/saml:AttributeValue
    <saml:AttributeValue>Value 3/saml:AttributeValue
    /saml:Attribute

    It is described on pg 31 of the spec https://www.oasis-open.org/committees/download.php/56776/sstc-saml-core-errata-2.0-wd-07.pdf#page=31

    As this is a common method of delivering data structures inside of SAML attributes especially when specifying items like user affiliations or group memberships, we request that support be added in the future to read and operate on multi-value/list attributes within the RemoteAuthValidation table.

    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)
  17. Make sure all accounts that log in with past Expiration Dates must go through the Expired Users page and update their information

    Users with old expired stub accounts are not prompted to update their information when logging into their ILLiad accounts again. The account status goes from Cleared=NEW to Cleared=NO, and ExpirationDate isn't checked/updated because the account was technically already created.

    We need ILLiad to check whether an account is expired or overwriting an existing expiration date. Having a patron from 2012 able to submit requests without updating their contact information or preferences is a real problem for us -- patrons can and do change their email addresses, and we allow patrons to choose to have loans delivered to their home if…

    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. 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)
  19. Allow Database Manager To Run on a Schedule

    We would like to be able to run Database Manager tasks on a schedule. For example, we would like to flip expired patrons to blocked on a nightly basis instead of requiring interaction from staff.

    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)
  20. Ability to COPY and PASTE in User notes field

    This will allow us to copy and paste notes when we are merging accounts or when we need to copy and paste notes to multiple accounts (within families, etc.)

    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  ·  User management  ·  Admin →
    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
  • Don't see your idea?

Feedback and Knowledge Base