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.

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

Add ability for the Symphony API add-on to complete an additional transaction upon check-in, (checking the item in within Symphony, which would push it into transit to the hold location).

Please give libraries the ability to re-order the CustomDropdown Table in the Customization Manager - there are cases when an order other than alphabetical is what makes most sense to the user.

I often need to delete notes I have just added to a request because I realize that there is a typo or I want to add to the note. It would be very helpful to be able to just edit the existing note rather than having to delete it and add a new note.

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.

I would love to be able to revert to a previous version of a request after saving (similar to how Google Suite does so). There have been a few times we have saved over the request information in ILLiad and had to log in to WorldShare in order to see what was originally requested.

I'd like to see an addition to the database manager where we can run a search against the transactions, users or lending library tables and from those results, batch update fields in that table for those results. An example would be if we have a campus that changes names (which we've had a couple times) We could run a query on all users with that pickup site and batch update them to the new name. I see this as an addition to the database manager since that is able to be restricted to a VERY limited number of staff.

Given that the corresponding event hook for Doc Del is triggered for article requests, this may be a longstanding bug. As of 9.1.1 the LendingRequestCheckOut event hook isn't triggered for article requests when they are marked found. I've been working around it by using the Route event hook.

Add a way to reveal what you type in the password change box so staff can make sure they have typed in what they think they've typed in.