If a researcher requests something that is already on hold or in retrieval from a remote location, Aeon should alert staff to prevent duplicate paging or looking for things that are right behind them.

In the staff client, requests in the Item on Hold queue have no expiration, but most sites allow holds for 1-2 weeks. Create an addon that allows site to determine queue and number of days for requests to stay in that queue. When the number of days has elapsed, automatically route the request to another queue. EX: if a request is in Item on Hold and is allowed to be on hold for 2 weeks, set expiration for 14 days. When 14 days has passed, automatically route the request to Remove from Hold so staff can reshelve.

When you open an activity, and then open the request grid, I really want to be able to select multiple requests from this grid, and print those call slips.

And, I don't always necessarily want to print all call slips in an activity. Some might be offsite, others in the vault, others I just need to look at first in making decisions about a class...I don't always want to print them all.

Would it be possible to highlight a set of requests from one user, and send a single email to the user?

It would be great to highlight all the requests from each single user at once and then send one collective email to the user.

Seat Assignments: It is currently not possible to reassign users’ seats in the reading room without first checking them out of the room and then checking them back in. Patrons regularly change seats to view different size and formats of materials. Having a real-time view of seating, as well as a seat history, is vital from a security perspective. The need to check patrons out and then in again also potentially compromises security, as well as creating an inaccurate record of events, which be important in any (hopefully unlikely) security events.

Create one invoice for orders/one invoice for multiple copy requests from single user

This could be handled via addons currently but would it make sense to build it into the native system?

Used for reimbursement. Current option of just printing the table of requests does not look very official or sufficient.

Appointment fields are not currently available in the data source for PrintCallslips. Sites would like to add StartTime, StopTime, and ReadingRoom.

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.

It would be great if we had the option to set global request limits as well as appointment specific request limits. Ie, a user may be limited to 20 requests total, but only 5 of those could be for one appointment.

Certain fields would be restricted and not allow bulk editing.

Some staff rarely use the staff client and it would be good to get an alert to check out a request.

The two route buttons are identical and it makes them confusing.

Students may have come to view the items, but you don't want to add them as users for that activity because they shouldn't be able to create requests associated with it. But staff (and instructors) like to know who was in the room.

When an invoice is generated in Aeon, it's made visible for the patron to approve in the web. But there is no option for patrons to cancel that request if they do not wish to approve the invoice.

It would be really helpful to automatically generate appointment confirmation emails (when an appointment is made) & reminder emails (the day before an appointment)

All saved and scheduled requests are currently listed in Outstanding Requests, and there isn't a way for users to easily sort out just the requests for their upcoming appointment. There also isn't a good way for them to view when they have an appointment coming up, short of going into each request (and they may have requests scheduled for different days). It would be good if the patron could see the dates they have requests scheduled and the requests scheduled on those dates, as well as be able to sort Submitted vs Saved requests.

Add the ability to enter closure dates for a range of dates rather than just individual days.