Right now it looks as if a user logged in through the web will see their own appointments displayed in order from earliest (including past appointments) to latest. I imagine that as our frequent users return, this might get annoying for them - since they'd have to scroll and scroll to reach more recent/upcoming appointments.

Is there a way to let patrons change the order in which they display, or to toggle on/off "active" (current and upcoming?) appointments the way you can for "active" requests?

An option to show patrons which requests they have linked to an appointment in the "Outstanding Requests," "All Requests" etc. lists would be great.

It would be great if researchers could cancel their own appointments within the minimum lead timeframe.

Need the ability to create appointments in the API so that we can leverage that when using external requesting.

Hide section for scheduling appointments on the User Review page if there are no requests to submit.

Once you require appointments, it is applicable to everyone including staff. This is okay for Public Services staff who can navigate the client but not for everyone else who submits through the web interface. We have a workaround but it would be nice to allow staff to submit without an appointment.

Create a "toggle" for viewing "All Activities" and "Active Activities Only" on ViewActivities in the web

It would be great if calendar could show both morning and afternoon appointments. It is very confusing for researchers who are scheduling multiple appointments.

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.

The University of Baltimore would like for ASpace to indicate when the Restrictions Apply? checkbox is checked in the collection record in ArchivesSpace, as opposed to importing the Access Restrictions note, as the plugin currently does. This is because restrictions note isn't always used because it doesn't always apply; a clearer indication for them is if the checkbox is checked.

Add a customization key to let sites determine if users associated with activities should be allowed to clone requests they do not own.

Many sites create requests on behalf of faculty or other users for the activity. If the request is in the staff person's account rather than the faculty person's account, the faculty person cannot easily re-request that item.

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

When performing a search using the web search, if a user selects the radio option to Search All, it automatically resets to Active after the search results display. Should be set to retain selection.

The University of Arkansas would like for patrons to be able export citations as a plain text file, besides as an .ris file, for patrons who don't use citation software.

The cancel statuses that display if a payment has been cancelled are not always clear to the patron. Sites would like to be able to edit these message, but they are currently controlled by the DLL. It would be helpful to move these to the HTML code so they can be customized as needed,

Add the functionality to have the electronically delivered file(s) open in a separate tab or window in the web browser. This way the user can still have their Aeon account viewable.

Add the ability to schedule partial closures within the customization manager. Because of instruction held frequently in the reading room, I would like to be able to block requesting for specific blocks of time within a day, for example, from 1:00-2:30.

Requests placed via external requesting (especially from ArchivesSpace) are unable to be turned into photoduplication orders. Patrons or staff must clone the request to a copy order, which creates confusion with duplicate requests.