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

Could there be a way to see a list of the last 5 or so requests that a staff person opened? We sometimes forget to place notes or verify a piece of information before it gets routed to the next step. Titles or usernames are not always remembered correctly to find the request again. Even just the last request opened would be helpful.

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.

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

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

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: 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).

In Doc Del, have a dropdown choice of printing either articles or loans instead of all. We process these on different floors and it's really handy in Lending.

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.

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.

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.

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.

Integrate the ability to send NCIP messages for both borrowing and lending including support for renewals and recalls into the standard workflow rather than requiring an addon to do so. Settings could be part of the customization manager.

Include the option for html email

Add the ability to apply a coversheet on the lending side which would allow lenders to include copyright information as required by the CONTU guidelines.

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.

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.

When you submit a request through OCLC there is a field in Borrowing Information for the patron name. We have been deleting the patron name from this field for some time because we've found that it is sent to the lending library. If the library has a newer version of ILLiad, the patron name isn't sent, but if the lending library is on another system, it is. Removing this field would be an easy fix for patron privacy.

The ability to increase the font.