ILLiad Ideas

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add the ability to increase font size in the staff view for older folks or the visually impaired.

    The current font size in the staff interface is not adjustable within the application. It would be useful and decrease eye strain is the font could be adjusted to user preferences, Regular, Large or Extra Large maybe?

    47 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Staff client  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  User management  ·  Flag idea as inappropriate…  ·  Admin →

    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

  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    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.

  6. The ability to increase the font

    The ability to increase the font.

    11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  8. Update lending pages to same style as the other Updated Default Pages

    This is necessary because there are multiple ILLiad lending pages that need to be completed for new web tune ups. The changes between the default pages and the updated defaults are different enough that it would be difficult to repeat the changes for each customization as they come in. It will be much easier to have the same starting point for lending pages as we do for borrowing pages.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base