Ability to filter notifications under the History > Notification’s page to limit only emails sent to the patron. Right now, this includes all emails sent from ILLiad related to that user's account such as emails that were sent to Acquisitions about purchasing a book.

If a user is on the Main Menu page and wants to renew a checked out item, clicking on the renew button directs the user to the transaction details. Instead, allow the user to remain on the Main Menu and display the success error so the patron doesn't have to navigate back to the main page.

It would enhance accessibility if each of the ILLiad 9.1 forms (request forms, search page, new user info, reset password, login, etc.) used the autofocus feature to activate the cursor in the first blank field. See: https://www.w3schools.com/tags/att_input_autofocus.asp We're working on adding this manually to our pages, but having it in the pages by default would be better!

The NotWantedAfter field was removed as a default from the 9.1 ILLiad web pages. This should be be replaced, with the corresponding hidden field removed, and a dropdown calendar should appear when clicking in the field box, as in previous versions of ILLiad. This feature was appreciated by our patrons and desired for the 9.1 pages. (write up by Kerry).

Ability to choose the order in which the alerts appear on the web pages. This includes the #SYSTEMALERTS, #USERALERTS,#STATUSALERTS alerts.

When you click the Renewal button on the ILLiadMainMenu.html page, it takes you to the page that shows all the information about the transaction but even though the status line tells the patron they have placed a renewal, the TransactionStatus still shows Checked Out to Customer, and the Renew button still seems to be active. If you refresh the page, then those update, but it's confusing to the patron.

On the All Requests page in ILLiad patron web interface, make the display in the “Request Finished” (or similar) status appear without the due date, while the others retain them.

This way the request form automatically appears and the users don't have to go back through the navigation menu.

Ability to collapse the listings under a link for each of under the categories of Electronically Received, Checked Out Items, and Outstanding Requests on the main page rather than listing all possible requests under each category. This would match the style for "Cancelled" and "Completed Requests" and also take up less room on the main page if the patron has a lot of requests in one or both categories. Otherwise, the patron needs to scroll through all three (3) category listings to get to the bottom of the listing.

We'd like to be able to hide the AccountNo field in the Transaction request forms on the web. Right now, if we want Borrowing billing active with each patron being assigned a Default Account, the transactions created do not have an account selected unless we include this code:
<select id="AccountNo" name="AccountNo" size="1" class="f-name"><#OPTION name="ValidAccounts">

But we don't want the patrons to see that account at all. They don't need to know they even have an AccountNo. Right now there is no way to pass it through as a hidden value though.

Please provide multi-language support for ILLiad web pages or a Spanish language web interface option.

The old GIST webpages for ILLiad had a function that allowed a patron to enter an ISBN into a search box on the webrequest form, search for the item, and have it populate the title, author, etc.

I would like more customizable display options for transaction statuses in the patron interface. For example, once a patron clicks the "Renew" button, the request disappears from their checked out items list until the renewal is processed and routed back to checked out to customer. I would like items in the Renewed by patron status to also appear under the checked out heading.

We use a lot of custom queues and would like to be able to manage where requests display in the patron interface.

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.

If a user registers to ILLiad (specifically via the NewAuthRegistration.html) in the wrong nvtgc site's pages, during the dll redirect to the right nvtgc pages the UserNotifications entries are not added for the user. The dll log does show that entries are being added but it appears this is written to the log even when the entries have been skipped over.

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.

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.