If you would like to allow researchers the option to place Aeon requests for archival objects directly from the ArchivesSpace Public User Interface (PUI), you can enable this functionality by installing the ArchivesSpace Request Fulfillment via Aeon plugin on your ArchivesSpace server. Once configured, this plugin will add a new Aeon request button to archival objects in the PUI, allowing users to easily submit a pre-populated Aeon request form for the item from ArchivesSpace. In order to use the plugin, settings will have to be configured both in ArchivesSpace and in your instance of Aeon. This article will note a few recommendations for configuring the plugin on the Aeon side.
Configuring the Atlas Dual Authentication Portal
This plugin is designed to send as much data from ArchivesSpace as possible to allow users to easily map fields on the Aeon side of the integration. As such, it uses POST data rather than GET parameters so that data does not get truncated. If you are using the Atlas Dual Auth Portal, please ensure that you have configured it to support POST data handling according to the instructions in the Using an Authentication Portal Landing Page article. If this is not properly configured, data will not persist from ArchivesSpace to Aeon via the plugin.
Configuring the OpenURLMapping Table
The Aeon OpenURLMapping table must be configured in the Customization Manager under Web Interface | OpenURL | OpenURLMapping before the plugin can be used. Below is an example configuration for an ArchivesSpace repository with a system ID of "ArchivesSpace" as indicated in the rfr_id column:
Example Configuration
| URL_Ver | rfr_id | Aeon Action | Aeon Field Name | Open URL Field Name | Aeon Value |
|---|---|---|---|---|---|
| Default | ArchivesSpace | Replace | ItemAuthor | <#creators> | |
| Default | ArchivesSpace | Replace | ItemDate | <#creation_date> | |
| Default | ArchivesSpace | Replace | ItemTitle | <#collection_title> | |
| Default | ArchivesSpace | Replace | ItemSubTitle | <#title> | |
| Default | ArchivesSpace | Replace | CallNumber | <#collection_id> | |
| Default | ArchivesSpace | Replace | ItemVolume | <#instance_top_container_display_string> | |
| Default | ArchivesSpace | Replace | ItemIssue | <#instance_container_child_type> </#instance_container_child_indicator> | |
| Default | ArchivesSpace | Replace | ItemInfo1 | <#accessrestrict> | |
| Default | ArchivesSpace | Replace | DocumentType | manuscript | Loan:Manuscript:GenericRequestManuscript |
| Default | ArchivesSpace | Replace | ItemNumber | <#instance_top_container_barcode> |
Configuring the Aeon Fields Used by the Plugin
Each row in the OpenURLMapping table configuration shown above contains a different Aeon field that will be populated with the value from ArchivesSpace field indicated in the Open URL Field Name column, with the exception of the row for the Aeon DocumentType field, which uses the Open URL Field Name column to indicate the document type that should be used when creating the Aeon request. You can add or remove additional mappings to the table if you would like to populate different fields on the Aeon request.
Configuring the Aeon Request Form Used by the Plugin
The specific Aeon request form that ArchivesSpace should use to create the request should be indicated in the Aeon Value column for the DocumentType row using the format <RequestType>:<DocumentType>:<AeonForm>. In the example above, the DocumentType row indicates that ArchivesSpace will use the GenericRequestManuscript request form to create a Loan request of the Manuscript document type. If you are unsure about which AeonForm value to use for a specific request form, you can find this value by opening the HTML file for the request form and looking at the value in the hidden input for the AeonForm field on the page. For example:
<input type="hidden" name="AeonForm" value="GenericRequestManuscript">