A way to prevent (or at least limit the number of) users creating duplicate accounts by not allowing a user to use the same email address to create a new account, but then have them prompted to "Change Password" if they try to create a new account using the same email address.

The University of Baltimore also uses ILLiad and Ares. They import their affiliate user records into a validation table. When a new affiliate user logs into the web interface, their info from the validation table populates the registration form. They would like this functionality in Aeon.

This would allow Aeon sites to anonymize part of a users data/request history to protect their privacy while also maintaining statistics long term. For example: an active users request history may extend beyond the 5 year data collection period maintained for audit. The user would retain their access to Aeon, but all requests prior to the 5 year collection period could be anonymized. Allowing the site to maintain their statistics and ensure user privacy.

This should not be dependent on the AutoUpdateExpiration key. Many sites want users to expire yearly in order to reagree to reading room policies but do not want the user's expiration date to update anytime the user submits ChangeUserInformation, as that would bypass set user expiration.

Once a user is cleared, it is hard for other staff to know if it's that person's first time into the reading room and needs an orientation, etc. It would be great if it could be visually displayed somewhere in the user record or on the sign in table so that it's more obvious to staff.

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.

Most users that just make photoduplication requests never get cleared and so they never expire and get prompted to update their contact information. It would be helpful for all users to expire regardless of whether they have ever been cleared.

Would be very useful for class reserves to be able to put one request in multiple users account using "Request For"

Need a way to control if a patron has permission to view certain collections. Needs to be visible by researcher and staff.

We would like to keep the option of not clearing users when merging accounts. Clicking on "merge" on a user should go to that user in the merge list.

We would like the whole process of merging to be smoother -- it should be possible to start from any status and merge, and it should be easier to find related individuals. Also, if you click "merge" on a certain user, it should start with that user in the list of users.

The current merge workflow is incredibly confusing.