When I type a custom email to a patron from within the client, I'd like spell check.

Allow ILLiad to merge data not only with Microsoft Word but also Google Docs because many organizations are migrating from Microsoft Office to G Suite

We would like to be able to run Database Manager tasks on a schedule. For example, we would like to flip expired patrons to blocked on a nightly basis instead of requiring interaction from staff.

Web Circ should throw an error message when attempting to check out an item that is in transit but not at Customer Notified via E-Mail or Customer Notified via Phone.

When sending a borrowing request in ILLiad, have ILLiad bring the ISBN/ISSN from the record selected over from the work form to the main request page, as it does with OCLC numbers/titles. This would help ensure accuracy with the standard number and assist with collecting stats.

From customer: If we could automatically/programmatically create Staff User accounts in ILLiad and have the option for them to authenticate via LDAP to the ILLiad client, that would be really convenient. (Or if there was a Single Sign-On option that used the computer's Windows credentials to authenticate staff users).

We have three pickup locations and are becoming increasingly reliant on Web Circ. Recently, we figured out that "Billed & Blocked" isn't considered an "Active Status", so when a patron tries to return a long overdue book at the desk, it can't be checked in (but something that hasn't been checked out yet can!). Could you add "Billed & Blocked" as a status Web Circ can check in? Additionally, are you planning any usability updates? It would be great if "Check in" and "Check Out" weren't right next to each other.

Purdue University needs to break down IFM charges by RequesType for internal reporting. Having this in the default reports would be very helpful. We'd like to see it for both Lending and Borrowing.

Having a new document type of E-Book would help when doing custom reports.

To better serve former Loansome Doc users (as well as others), it would be helpful to have the ability to auto-populate the citation information thru the lending login. This feature exists in the borrowing login. It's easier for our patrons and more accurate for our staff than having patrons fill in the information manually or email it to staff.

All patron accounts are given expiration dates but the account remains active beyond this date until something occurs and the account is investigated and then manually blocked.
It would be great to have the system automatically block users when the expiration date is reached. This would help prevent graduated students and people no longer with our library from requesting materials through our services.

From customer regarding patron notification email templates used for the cancellation of borrowing transactions. : It would be helpful if I had a template for each reason and if ILLiad would automatically select the right one for each specific reason.

example: Our Political Science department changed their name. I want to be able to make this change to all the existing patrons it would apply to.

Include the option for html email

When an ILLiad stub account gets made due to incomplete registration it should not be assigned to a site not in use like "ILL." Allow users to configure what site/NVTGC those stub accounts should be assigned to.

Currently, if you use the Cancel option to Cancel a lending request when the OCLC status is Cancelled or Record not Found, it will cause a Connection Manager error. While staff can avoid the error by using the routing option to move the request to Cancelled by ILL Staff, it would be helpful if the Connection Manager or the Cancel option could be updated to avoid generating an error so that all Cancellation transactions can be handled in the same manner.

Stanford U is locally hosted and has a custom job that imports users directly into the Users table. This job will update users based on any change event triggered in the Registrar's database. It creates many users that never end up using ILLiad. We would like a standard method of creating a process that pushes users into the UserValidation table and can update users, regardless of their being in the Validation table or in the Users table.

It'd be great to replicate the great ILLiad on the web so that staff can work remotely.

When creating a holdings list, currently borrowers can see the institution name, days to respond, and fees for lending institutions. It would be nice to see the library's loan period for items in this area.