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.

When a user is associated with a proxy or an activity, they can see the associated requests but cannot manage them. The Actions menu will appear blank as no action can be taken. For clarity, a tooltip or other message should display here indicating the user cannot manage requests they did not create.

Currently, you can configure the "requestable archival record levels" setting in the plugin so that the Aeon request button is disabled at specified record levels in ArchivesSpace. It would be helpful to have the option to completely hide the button at those specified record levels where users cannot make requests.

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

Sites would like the option to initialize photoduplication for multiple transactions at once from the request grid ribbon.

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.

No tracking entry is added when files are downloaded from the user's account after photoduplication delivery. Add entry in tracking table to indicate file was downloaded and make visible in both web and staff client tracking tables for each transaction.

When a user wants a statement of paid invoices for reimbursement from their institution or other issues, there's no great way to get that for them once the orders are paid and delivered. We have to manually go in and resend each paid invoice, or they have to go into each separate transaction/order.

Aeon automatically generates an invoice number for each transaction when an invoice is generated. However, the InvoiceNumber is not visible in any grid in the client. The field can be added, but no data displays.

The field also should be able to be added to the Billing tab.

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,

We need the ability to POST requests to Aeon (after acquiring an authentication token). We do not want users to be sent to the Aeon site and leave our finding aids site when making a request, so we would prefer to submit the request in the background. This seems like the most basic integration one could want, yet it's missing from the current API.

Some libraries receive requests frequently by members of certain organizations like news media, law firms, etc. It would be useful to search by Organization and return results lists for users associated with that organization or requests made by users with that organization. This would help when staff know someone from an organization made a request but they aren't sure who the user is.

Allow staff users to adjust sign out time in the Aeon client. This will allow for accurate statistics and tracking.

If staff have a way to flag that an item is already digitized (perhaps import a field from ArchivesSpace), show container information that items are the same, but can be managed separately. Add logic to ask user if they want digitized or physical version. Auto-close digitized requests to finished queue and email patron to let them know that an alternate copy is available.

Ex: if a user places a request but includes a range of boxes, staff will need to clone the request and update the barcode (ItemNumber). If the barcode field is set not to clone, staff can add the correct barcode to each cloned request.

A library using the Aeon Fulfillment plugin in ArchivesSpace would like for checkboxes to appear at the requestable levels (e.g. file, Item) so that a patron may select more than one resource before using the plugin to log into the Aeon and submit the requests via Aeon. They are essentially looking for a "shopping cart" feature on the ArchivesSpace side.

Create a new database field for Preferred Name. This field should be searchable in the Name search on the Dashboard and added to the available display fields in the Signed In Users group. When used and data is present, the preferred name should supersede the First Name in all views/displays/print templates.