Skip to content

ILLiad Ideas

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

23 results found

  1. Update WorldCat Local Addon to support Chromium Browser

    The WorldCat Local addon is not working in ILLiad v9.2 (and probably other versions too). On display under the tab was an error message saying Internet Explorer browser is not supported. The addon needs to be updated to use the Chromium browser since Internet Explorer is deprecated.

    9 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

    3 comments  ·  Addons  ·  Admin →
  2. Include $0 charges for EFTS libraries in Billing Manager EFTS file for Upload to MLA EFTS

    From user: New EFTS system automatically uploads all completed transactions into our account with our base fee but we can override with our own file. Currently ILLiad does not include $0 charges in the file for upload.

    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

    2 comments  ·  Billing  ·  Admin →
  3. SLPasswordChanged does not appear on page

    When a patron signs in and attempts to change their password, they do not receive the "success" message even through the system has accepted their change after submission. They then attempt to change what they entered or resubmit what they do not realize they have already submitted.

    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

  4. Integrated OpenAthens Support

    Build in support for OpenAthens without the use of Shibboleth or EZProxy.

    43 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

    Released in ILLiad v9.2 on 3/22/22.


    Prior to v9.2, ILLiad only supported OpenAthens as an IDP using third-party SAML SP software, such as EZProxy or the well-known Shibboleth SP software. The native SAML Module included with ILLiad v9.2 integrates support for SAML authentication directly into ILLiad so that using OpenAthens no longer requires EZ Proxy or other third-party software. It isn't a full OpenAthens integration, but it should allow institutions using OpenAthens as an IDP to lay much of the groundwork that we need in place to have tighter integration later on.

  5. Easy Article Request Submitting for Users using DOI or PMID in ILLiad Web Client

    If a user has a PMID or DOI they could insert that number or URL into a field when requesting an article. Once the number/URL is in the correct field it would automatically fill in all the needed citation information so they do not have to. A users that may not know how to use the automated database search and fill ILLiad request may like this feature. Also the user that has many request that need to be placed.

    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

  6. Maintain updates with Rapid and update to current Rapid API

    Continue to work with Rapid and keep API up to date to allow Rapid & RapidR enhancements to work with ILLiad.

    55 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

    4 comments  ·  RAPID  ·  Admin →
  7. Provide automated reminder notice when borrowed item is not picked up

    We would like to send an automated email to patrons an email reminder to pick up borrowed material if they have not checked out the material a few days after getting initial notification.

    27 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

  8. Update patron web pages and the ILLiad web DLL to comply with Section 508 and WCAG 2.0 (level AA) guidelines for accessibility. 

    Update patron web pages and the ILLiad web DLL to comply with Section 508 and WCAG 2.0 (level AA) guidelines for accessibility. 

    34 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

  9. 18 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

  10. Add password reset error message when username is incorrect

    Current if a user enters an invalid username on the password reset page no error message is presented.

    Common functionality in other environments would present an error message directing users to contact staff to obtain the username.

    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

  11. Automatically block patron accounts when the expiration date is reached

    All patron accounts are given expiration dates but the account remains active beyond this date until something occurs and the account is investigated and then manually blocked.
    It would be great to have the system automatically block users when the expiration date is reached. This would help prevent graduated students and people no longer with our library from requesting materials through our services.

    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

    As a part of the Automatic User Expiration feature, 4 new Customization Keys were added to the Customization Manager in v9.1 under System | User Expiration including AutoExpireUsers which determines if the System should automatically expire users. If set to yes, the system will set the cleared value of expired users to the value specified by the ‘AutoExpireUsersClearedValue’ key.

  12. Include the Renewal button for each request on the ILLiad Main Menu by default

    Renewing is more streamlined if you can see the Renewal button for each request on ILLiad Main Menu. Please include in the next batch of default web pages to be released, or as an easy alternative.

    Currently possible with additional web work.

    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

    released  ·  1 comment  ·  Web Interface  ·  Admin →
  13. The ability to increase the font

    The ability to increase the font.

    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

  14. 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

  15. DOI - improve DOI searching options

    Instructor wants to just put in a DOI for an article request and feels that since that is a unique identifier for an article that it should be all he needs to enter. Make this work unmediated, either via an enhancement or via an addon, that would be really great! Ticket 5983

    21 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

  16. Streamlined patron load/registration functionality and updating of records

    Add functionality to reduce the amount of information a patron has to enter upon registration if the institution already has that info via some other authentication system or other service/database while still getting it into the patron record. Also update patron records if the data in the primary source changes.

    18 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

    As of ILLiad 9.1, authentication enhancements have been added that allow ILLiad to map user attribute fields from external authentication systems into the ILLiad User table fields. Staff is able to select which fields can be passed through to update the user record. Users can now be automatically created, pre-cleared, and skip the NewAuthRegistration and Billing pages for user clearance into ILLiad.

    https://support.atlas-sys.com/hc/en-us/articles/360037463394

    https://support.atlas-sys.com/hc/en-us/articles/360037962733

  17. 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

  18. Allow API to truncate field lengths needed for acceptance

    The way the API currently functions is that if an entry in a field is too long for the database to receive the call falls. It would be nice if the API was able to truncate the field to the appropriate length so the call would still go through but the offending field would be automatically trimmed to the needed length.

    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

  19. Support automatic / silent installation of the ILLiad client

    Please provide a .msi installer to allow modest customization and easy silent installation via different system management systems e.g. AD, SCCM, KACE, 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

    Atlas Systems’ doesn’t currently provide MSI files for our ILLiad installers and doesn’t support remote installations. ILLiad installers are created using Installshield, which wraps the Microsoft MSI functionality and requires the use of an answer file to silently answer any questions asked during deployment. You can create recordings of the options chosen in the UI to be used for silent installations/uninstallations by running the installer at least once to record your answers. For details see: https://support.atlas-sys.com/hc/en-us/articles/360058986953.

  20. Allow shared server installations to share a RAPID account (similar to sharing OCLC account)

    When downloading new requests, a certain site code would need to be designated as the primary site for receiving those requests. The requests could then be doled out to other ILLiad sites on the server for fulfillment and all would update that same RAPID account.

    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

    0 comments  ·  RAPID  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base