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.

Would love to print from different physical locations but need to be able to select which pull slips (or receives, or whatever!) should be pulled for printing, so that you do not disrupt work at another location.

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.

From user: New EFTS system automatically uploads all completed transactions into our account with our base fee but we can override with our own file. Currently ILLiad does not include $0 charges in the file for upload.

Expand the ItemNumber field in ILLiad to accommodate multiple barcodes for multi-volume sets. Add ItemNumber to the default Number search in the ILLiad ribbon for easy access. Add ItemNumber to fields searched by TN/ILL # search on Check Item In interface.

All of the above would allow more efficient handling of borrowing returns when paperwork with Transaction is missing.

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.

We can use flags and notes to ask other ILLiad staff users questions about a request, but it would be even simpler if we could include @PersonName in a staff note and notify them that they'd been tagged for review/response.

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.

I would like to send invoices via email, using billing manager

It would be great to have an Addon similar to the existing DOI Addon. If a user on the webform enters a PMID, ILLiad searches and fills in/adjust the rest of the request data.

Currently ILLiad will only track the first renewal for a request. However, many lending libraries allow for multiple renewals, and with current closures this is happening more frequently. It would be helpful to have ILLiad route and track renewals for requests beyond the first one so that the due date in borrowing requests match what the lender has determined.

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.

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.

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)

In the Staff Manager, please adjust the granularity of the Copy Layout & Grid Settings by Borrowing, Doc Del, and Lending. If I make major changes to the Borrowing layout, I'd like to be able to copy those changes to the relevant student employees & staff, but not overwrite their layouts in DocDel and Lending. It would be very helpful if we could indicate which layouts to change and which to retain in these different areas of ILLiad.

Remove step of manually checking for OCLC "Returned" status before generating overdues. it would be helpful if the automatic process included checking the OCLC status before sending it off and not sending for items in Returned status.

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