Currently the Status field is the only option for creating unique request forms. It would be nice to be able to have more information to customize request forms. Some of the user information, such as Status or User Info # would be valuable to work with on request forms. If could be queried to hide/add fields based on unique statuses. The data could be in a query parameter or hidden input field on the page.

This option exists for Ares but is not available in ILLiad 9.1
The currently available webpages allow users to update address information and other personal account details, but there is no mechanism for letting a user know that their update has been successfully submitted-- i.e. the page reloads, displaying the information a user has just entered into the available fields, so from the user perspective there has not been any apparent change.

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

We would like the ability to customize what elements/fields display to the user on the Request Detail page. We use custom queues for certain requests and do not want the Due Date to display in the detail view for requests in those queues.

The OpenURL generated by Pubmed has the PMID field sent as:
&rft_id=info%3Apmid%2F26824237
which puts extra info in front of the PMID value. This means staff have to touch each request and clean it up before searching it. It would be great if the OpenURLMapping table could have an option to strip characters from a value or some other means to clean up that field when it carries over.

some users do not recall their username, so we are wondering if the Forgot Password feature would ever upgrade and offer other options such as allowing input of email address or alternative options between forgot password vs. forgot username and etc.

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.

Extend the Web API to include methods that will return data of requests made on parameter like RequestType and RequestDate. This would enable the interfacing of ILLiad data with other database systems.

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.

Patron often add multiple citation entries into one field i.e. paste all of teh citation information into the journal title field. It would be helpful to have field note more obvious to users. Maybe something like this example
https://www.screencast.com/t/YDgAWZB4EE

-submitted on behalf of Cleveland Health Sciences Library

I love the new webpages though we haven't made them public yet. One thing I'd like to see is the ability for the patron to see notifications that were sent that were associated with that request when viewing the request details. An example would be an email with the link we sent to an open-access resource via email.

Please give libraries the ability to re-order the CustomDropdown Table in the Customization Manager - there are cases when an order other than alphabetical is what makes most sense to the user.

Add ability to customize which statuses from the tracking table display to the user on the ViewDefaultDetailed.html page

on behalf of New Mexico State Library: We would like the ability to have a status-specific ChangeUserInformation form validation. As a referral center for our state, small libraries throughout the state have ILLiad user records to place requests that we process on their behalf. We would like to require different user information on those user records than we require for our other patrons who are individuals working in state government.

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

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.