Add the ability to export of list of staff user from the staff manager similar to functionality available in Ares

It would be great if I could, through the Customization Manager or the client, set a Due Date Override so that I could make everything due before the end of the semester for specific patron groups (Undergraduates go far away over winter break and don't give their stuff back, but Staff are here year round)

ILLiad needs support for DKIM and to allow configuration to differentiate From addresses and Reply-To addresses to prevent ILLiad messages from going to SPAM.

Implement an option to make a shipping label for the patron send the item directly back to lending library and supporting workflows and updates in ILLiad.

When a user is disavowed, it makes sense to cancel all outstanding requests so that they are not processed. It does not make sense to move completed requests (in queues Request Finished or Delivered to Web) to Cancelled by ILL Staff. This skews statistics.

Currently ILLiad has Last Name and First Name fields in the patron record, but other databases on our campus, including our ILS, have the additional fields of Preferred First Name, Preferred Middle Name, and Preferred Last Name. It would be great if ILLiad would add these fields.

Add a field to the StaffPasswordComplexity field to allow a plain text description of the regular expression. A user should able to view what the password requirements for staff passwords are without having knowledge of regular expressions.

I realize that this could be very dangerous and should be locked down behind something like the database manager, but having the ability to batch update records (transaction, user, lender, etc) in ILLiad would be a huge time saver. There are times when local data or workflows change, and the ability to change more than one record at once would open up a lot of possibilities.

Could you provide a Web Circ option for checking-out and checking-in in-library use items multiple times for a patron? Currently, we don't have an electronic means of tracking when an in-library use item has been removed from our ILL pick up shelf or is being consulted by our patrons.

Our campus wants us to deliver accessible PDFs for faculty who post files online for classes. Many libraries scan as images and deliver via Odyssey as part of the scanning process. They don't have opportunity to OCR files before delivery.

In the lending scanning window, display the email address of the borrower. When sending via Article Exchange it isn't always known if the email address is filled out in the address book. If the email address is not in the address book, the article does not get delivered.

It would be good to have BI reporting for ILLiad like Aeon and Ares.

Auto update of Custom Group when using exact name of the OCLC Group Access Capability (GAC), such as ACOV. Manually adding individual codes for all of us seems redundant.

Enable a pop-up message that would indicate when a request is open by another user

When using User Expiration in 9.1, the only indication of a user's expired status on the User Record is the Expiration Date. All other indicators are the same as a New User :

User Record= no status button active
https://www.screencast.com/t/1xqQr0NbaIZ

Transaction Record=flag by username and "user not cleared" status warning
https://www.screencast.com/t/0DttY3BXKQkP

I would be helpful to be able to readily distinguish between users that are expired vs. users that are new.

Consider increasing the number of ItemInfo and UserInfo fields to more than 5 each. We have already used up all of the ItemInfo fields and have had to re-purpose existing fields to collect the additional information we need in our borrowing requests.

I would like to be able to control if a request will automatically open when searched or when a queue of one is displayed.

Primarily, I want to be able to STOP the request from opening automatically. Many times we search for an item to see info, or route to an active status, and auto opening just slows down our ability to do this as we wait for the request to render.

Several of our library's databases don't play nice with IE anymore, so when searching for an article while in ILLiad, we have to cut and paste the link into another browser before we can continue the search. This would (hopefully) be eliminated if IE were not the default browser.

Store demographics (ie, non personally identifying information, such as major or department) associated with a user request, to the request, not just the user.

This would allow us to know better understand ‘how many requests were submitted by BIOLOGY majors’ in a given period of time vs. having those BIOLOGY requests migrate to a new major when USERS change major or vice versa.