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.

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.

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.

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.

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.

Patron often add multiple citation entries into one field i.e. paste all of teh citation information into the journal title field. It would be helpful to have field note more obvious to users. Maybe something like this example
https://www.screencast.com/t/YDgAWZB4EE

-submitted on behalf of Cleveland Health Sciences Library

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

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.

It would be nice to have the patron's name, transaction number, part of the citation, and fee added to the cover sheet. This would useful for the people who are not part of the university to keep track of the fees.
I usually add the fee in the note section, but creating a separate field and allowing the user to have a PDF of the request with the fee on it would also be helpful.

I love the new webpages though we haven't made them public yet. One thing I'd like to see is the ability for the patron to see notifications that were sent that were associated with that request when viewing the request details. An example would be an email with the link we sent to an open-access resource via email.

It would be nice to see a User History tab on their User window. For example, what link did they come from to create an account, what time stamp they entered Users to Clear, transfer history, etc.

It would be nice to have the Reprints Desk automation add-on to be able to pull from unfilled and fill the requests without staff intervention. The issue is if the add-on is looking in the unfilled queue and the OCLC request is still active it makes a never ending loop.

In cases where SMTP authentication requires a single sending "From" address, it would be nice to allow a variable Reply-To address in email notification templates so that replies to particular notifications could arrive in distinct mailboxes.

It would be helpful if libraries could choose to suppress sending borrowing overdue notices to patrons on days when the library and/or ILL office is closed. We do not check for ILL returns on Saturdays or Sundays, and on Monday morning we backdate everything returned over the weekend to Friday. However, patrons are regularly annoyed/alarmed to receive an overdue notice on Saturday or Sunday when they've already returned the item. We do indicate that this is nothing to worry about in our email template, but not everyone reads the entire email, unfortunately.

Extend the max field length for the ISSN/ISBN field beyond 20 Characters. Users sometimes copy/paste an ISBN with a prefix (e.g. ISBN: 1234567891234). If they do that with a 13-digit ISBN, the last digits are cut off.

I noticed that Aeon can accommodate credit card payments. For our purposes it would be great if ILLiad do the same. We have a home grown tool that allows individuals and companies not affiliated with our institution or another academic institution to place requests for copies of articles or to borrow books. We facilitate these transactions via web forms and credit card payment through cybersource (a 3rd party secure payment system). Essentially, we would like to be able to manage these types of requests in ILLiad.

It would be nice if there were one or two more fields where data grabbed via Z39.50 could be imported into ILLiad. In particular, "Item Num" would be an ideal place to hold a barcode, rather than having to concatenate it to a different value (as described here: https://support.atlas-sys.com/hc/en-us/community/posts/360006750353-Finding-Importing-the-Barcode-Field).