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.

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

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.

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

The ability to increase the font.

To help with the increase in ILL hacking attempts.

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.

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.

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.

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.

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.

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.

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

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.

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.

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?

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

This makes the navigation easier to navigate to and clearer that it is a navigation when using a screen reader.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/nav

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.