ILLiad Ideas

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Integrated OpenAthens Support

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

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

    We’ll send you updates on this idea

    2 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  2. Have Chrome (or FireFox) be the ILLiad default browser

    Several of our library's databases don't play nice with IE anymore, so when searching for an article while in ILLiad, we have to cut and paste the link into another browser before we can continue the search. This would (hopefully) be eliminated if IE were not the default browser.

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

    We’ll send you updates on this idea

    10 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  3. Remove trim function from ILLiad web password login

    When users log into ILLiad web form to make requests or manage their Illiad account, the ILLiad.dll is trimming spaces from the beginning and end of the password entered. Through LDAP we use our campus Active Directory credentials to let users log into ILLiad. Our campus now has active directory password requirements of including a space (to create a pass phrase). Some users are choosing to put the space at the beginning or end of their password, and because ILLiad is trimming spaces, they cannot log into ILLiad. I don't think ILLiad should be altering passwords entered by the patrons…

    3 votes
    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 →
  4. 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. 

    32 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 →
  5. Enable auto-population of citation information thru the users' Lending login

    To better serve former Loansome Doc users (as well as others), it would be helpful to have the ability to auto-populate the citation information thru the lending login. This feature exists in the borrowing login. It's easier for our patrons and more accurate for our staff than having patrons fill in the information manually or email it to staff.

    2 votes
    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 →
  6. Default setting for Accept non-English Set on User Record

    Add a setting to the user records that would apply their selection of Accept Non-English field as the default on all requests from that user

    via Site Visit with WVU

    2 votes
    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 →
  7. The ability to increase the font

    The ability to increase the font.

    9 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 →
  8. 2 votes
    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 →
  9. Include Display Status in any call to the API that returns a Transaction Status

    Currently, Display Statuses are not returned with Transaction Status information when using the API.

    Our library is using the API to integrate ILLiad into the patron account interface; it would be very helpful to be able to use the Display Status table to mask the queue names.

    2 votes
    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 →
  10. 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.

    3 votes
    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 →
  11. Ability to upload request from Reference Citation service

    Our researchers often use Reference Citation services such as RefWorks, EndNote or Zotero to create bibliographies. We would like for them to have the ability to upload a batch/list of items from a service like this or from an excel spreadsheet.

    6 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 →
  12. Make "terminal" statuses customizable

    We have some statuses that are effectively terminal (eg "Supplied via consortial system"). However, these will remain in patrons' Active Requests in the web interface forever, unless they are moved to Request Finished or Cancelled by ILL Staff. It would be great to be able to add to what statuses are considered no-longer-active.

    8 votes
    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 →
  13. Allow FORMSTATE tag to persist through webpage workarounds.

    When a workaround is used on the webpages to display something outside of the usual ILLiad workflow, it breaks the tag and doesn't allow OpenURL to route the user back to their request. Ideally, the formstate would persist through the workaround, and the user would be routed back to their request instead of dropped onto the main menu.

    2 votes
    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 →
  14. 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 →
  15. Add Captcha challenge to login and password reset pages

    Captcha might prevent the recent scripted logins which are resulting in fraudulent lending requests.

    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 →
  16. Expand the borrowing statuses in which patron cannot cancel.

    Not sure if this goes in the web interface. We have some custom queues we use for items that we've already ordered and do not want to have the ability for a patron to cancel. Right now can only specify cannot cancel if item is in the "Request Sent" status.

    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 →
  17. Ability to remove loan information from web pages.

    Many libraries take advantage of NCIP integration with their ILS and thus manage loans (due dates and renewals) directly with their ILS, thus patrons are encouraged not to log into ILLiad web pages to perform those tasks. However, there is no easy way to remove or hide that from the web 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 →
  18. Set web session timeout by patron type/status

    From customer: We have a faculty member complaining about the web session. We have it set at 10 minutes since so many of our patrons use shared/pubic workstations. Is there any way to individualize web session times by patron type?

    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 →
  19. Allow the document type to be set on default ILLiad web forms

    Use case: A library would like to offer the option for patrons to request a loan in ebook format and process through the Occam's Reader addon. We have set this up as an option with an Item Info field currently, but it would be helpful to be able to use Document Type where this info seems to live more naturally. The other workaround considered was changing the default loan form for GenericRequestLoan but this seemed like a lot of extra work (include_menus, OpenURL Mapping, Validation, etc.) just to add a new value. So if we ever get to make changes…

    2 votes
    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 →
  20. Default setting for Accept non-English Set on User Record

    Add a setting to the user records that would apply their selection of Accept Non-English field as the default on all requests from that user

    via Site Visit with WVU

    0 votes
    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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base