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.

A web interface that combines the features of the Customization Manager and Staff Manager in one place.

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

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.

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.

Having to hover over a symbol to see the cost while in borrowing trying to build a custom string takes extra time. It would be great if the cost could be displayed right next to the days to fill.

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.

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.

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.

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.

With libraries closed indefinitley all over the world, we have to push due dates out, possibly multiple times. This is easy enough to do in an ILS, but ILLiad does not allow me, as the Borrowing Coordinator, to push out a renewal request for one new due date for all items currently due before that date. That would save me hours, possibly days of work!

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)

Sometimes when I check in an item from a lending library, I receive an NCIP error that causes a loan to not be automatically imported into Alma. After I fix whatever caused the error, I currently have to check the item in again. This messes up the tracking and can cause an OCLC error. It would be nice if there was an option to only import the request without updating the status in ILLiad and OCLC.

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

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.