Having to hover over a symbol to see the cost while in borrowing trying to build a custom string takes extra time. It would be great if the cost could be displayed right next to the days to fill.

Please develop an ILLiad app for iOS on iPad. It would greatly ease some of the difficulties our workers have doing their job remotely.

In the Staff Manager, please adjust the granularity of the Copy Layout & Grid Settings by Borrowing, Doc Del, and Lending. If I make major changes to the Borrowing layout, I'd like to be able to copy those changes to the relevant student employees & staff, but not overwrite their layouts in DocDel and Lending. It would be very helpful if we could indicate which layouts to change and which to retain in these different areas of ILLiad.

Book chapter requests use the incorrect custom holdings path; they pull from OCLCILLLoanHoldingsPath instead of OCLCILLArticleHoldingsPath, but the latter is the correct path.

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

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.

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.

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

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

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

Customer requests more high contrast skin options for ILLiad. "in general if there is a dark background a light font is better. Dark on dark is difficult to read." More details and pictures in ticket 8724.