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.

U Pitt has a remote storage location that shares an OCLC symbol but has its own NVTGC to allow for unique workflow requirements. We need the ability to process invoices for both sites at once, rather than duplicating the process, since the purpose of the remote storage facility is to support requests sent to the primary site, rather than function as its own entity.

University of Pittsburgh would like more control over access to the Electronic Delivery Utility, particularly in reference to billing features. Please consider tiered permissions that limit individual staff use and limit the ability to skip or adjust automatic billing totals.

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.

It would be helpful to be able to select multiple requests then click a button on the ribbon saying "Add Note," which would then open a field to add a note to all highlighted requests. Having to open each request to add the same note repeatedly is unwieldy.

It would be very helpful to have the Lending Overdues ribbon have the options that various queues have: Export, Add Flag, etc.

A customer asked for this during the #ILLiad24 event at roundtable. Have an options for settings per time period like semester table in Ares to specify dates until which items can be renewed automatically. After that date items could be renew denied or manually processed. It would be nice to set this by status so that faculty could request renewals across semesters but students would need to return items by end of semester etc. Decision Support Pipeline and Business Rules can probably already make this work when the new renewal features are released.

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.

Ability to create an individual invoice for lost items and have the Billing Manager handle billing for one-off invoices.

It would be incredibly helpful to be able to save grid layouts as .xml files in ILLiad to apply to other users or to other queues for the same user. It appears this is already supported in Aeon: https://support.atlas-sys.com/hc/en-us/articles/360011821354-Saving-and-Loading-Grid-Layouts
(I saw this suggested on the Ares Ideas area; this would be great for Ares as well.)

In a recent OCLC customer service webinar it was suggested that we notify patrons regularly as to the status of outstanding borrowing requests. This would not be possible for us to do manually due to our work load. If we could use ILLiad to send out a notice for borrowing requests to let patrons know we are still trying to fill their requests, that would be great.

To piggyback off of the case-insensitivity with queue names ideas: https://uservoice.atlas-sys.com/forums/581665-illiad-ideas/suggestions/42375580-case-insensitivity-for-queue-name-and-custom-field. Another option to avoid having errors if a queue name is typed in a routing rule without proper case sensitivity would be to have a way to select queues such as a drop-down menu when creating custom routing rules.