I would like the ability to print an invoice right away for the libraries that email their request and ask that we attach an invoice to the request. Most of the time these are specialty or international libraries that rarely or don't use OCLC or Docline. This would also be good for individual users ( former Lomsone Doc Users) who are not part of our university or our medical association.

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.

Attempting to Check In from Lending Library will cause a Connection Manager error if an item is returned to the lender but the borrowing library has not performed the OCLC Received or Returned update.While the Connection Manager error can be cleared, the system flag will remain unless the borrowing library updates the request.

It would be helpful to have a way to override these flags, particularly if the item is considerably overdue.

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

It isn't currently possible to add the CreationDate field to the loan and article pull slip templates because that field is not included in the xlsx datasource columns. Can this be fixed? Having the CreationDate field on pullslips would make it easier to know which printed requests are close to expiring and need immediate attention.

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.

When creating routing rules or addons that route to queues, allow for case-insensitivity. For example, normal behavior would prevent the renewal button from showing in the default 9.1 web pages if a routing rule includes "Checked Out To Customer" instead of "Checked Out to Customer" since this isn't the correct name case sensitivity in ILLiad. Allowing for case insensitivity could open the door to allowing for custom field names.

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.

The transaction purge tab in Database Manager only has transaction date as a criteria. The Patrons tab allows for a very fine grain approach for deciding which users to purge. It would be nice to have a similar or expanded group of options for transaction purging.

For example, it would be nice to be able to delete test users that have test transactions, which we cannot currently do effectively now.

We would like the patron to be able to answer a satisfaction survey when they receive their document or response. it would be valuable to identify transactions that were challenging (from the patron's perspective) and have front-line staff followup with them. a 1-5 star rating would be sufficient along with a comment box.

When a library uses the following deflection:

Requests: Loan
Deflection Type: Enable Real Time Deflection - except when I am last in the lender string

OCLC should bump past them in the string, but AUTOMATICALLY add them back to the end of the string of potential lenders.

Change (or change back) ILLiad Lua scripts to automatically stop on the screen that has the duplicate request alert. It flashes past so quickly now, it's easy to miss and then we have to pay for article twice. The way the scripts run now, you've lost us a great Docline feature.

Book chapter requests use the incorrect custom holdings path; they pull from OCLCILLLoanHoldingsPath instead of OCLCILLArticleHoldingsPath, but the latter is the correct path.

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.

We have some files that get quite large when delivering PDFs. We would like to parse these out - call them chapters or parts. unfortunately, Illiad has the restriction of a single file per TN. We would like the option of being able to upload multiple files per TN, so that when batch loading, all files with the same TN would be attached to the transaction (think TN018765a,TN018765b,TN018765c all being attached to transaction TN018765)

Enhance EDU to allow multiple copies (using Automode) to process files from the same scanned file folder for different nvtgc sites. Currently the EDU reads through all scanned files in a folder and when more than one EDU is running it can lock the file causing errors for the other EDUs trying to process that file.

Most other ILLiad screens allow exporting data to Excel. Adding the option to the Submit Copyright Orders screen so we could more easily investigate titles we're borrowing high amounts of, along with the actual current publisher fees in CCC prior to submitting the order would be very helpful

Recent issues with COVID 19 are increasing use of the "mail to address" workflow for home delivery. It would be helpful for users to be able to view their address and other user information from the request form should it need to be updated.

Ability to control user expiration based on User status i.e. I don't want Faculty accounts to expire. Or only expire undergraduate accounts.