Examples of permission limitations that sites need are necessary. Are staff limited from editing or viewing? Would a web interface with only certain available tasks fix the issue?

Data repository for user information so researchers could have a single Aeon profile and suport collection usage across institutions

If the original request says 1-25 for the box value, it would be great if Aeon knew to convert that one to 1 and then make 24 more each saying 2,3,4,5,6 etc. Also it would be good if it understood 1-4,7,10-12.

The interface should provide a grid of the resulting requests with an opportunity for staff to edit/correct any of them before they are created.

Would be great to have an additional level of sign in for users above the room level so that we could sign out lockers to users before they are assigned a seat.

If a user chooses a country, have the web form change the options for possible states. This could also include other dynamic drop down options if there are other suggestions.

would like to be able to select more than one item to print at a time on additional queues and also requests that Call Slip Printing be available on all queues.

This seems to have been possible before and is missing now.

When opening a user to clear them, the form defaults to the default ribbon and you have to click the process ribbon. For users that need to be cleared, it should default to the Process ribbon.

I was thinking something like the Approve Orders table where patrons could click one or multiple checkboxes from the table (the one they view when they click the tag link from the main menu) and click a "remove tag" button.

Make the rule field like an email template where you can right click to choose a table and field to prevent typos etc.