Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow customization of Aeon form defaults #240

Open
ctgraham opened this issue Sep 2, 2022 · 1 comment
Open

Allow customization of Aeon form defaults #240

ctgraham opened this issue Sep 2, 2022 · 1 comment
Assignees

Comments

@ctgraham
Copy link
Contributor

ctgraham commented Sep 2, 2022

Is your feature request related to a problem? Please describe.

Branching from #228, and pending any migration to using the Aeon API directly for requests, the Grouping / Concatenation / FirstValue settings, the Reading Room defaults, and the Duplication defaults are likely candidates for institutional customization.

Describe the solution you'd like

Either configuration variables to localize these settings, or settings editable in the Django application.

Describe alternatives you've considered

The alternate approach of using the Aeon API to directly write to Aeon seems like a subsequent effort to me, following a low-effort implementation of configuring the form-based interaction.

Additional context

n/a

@ctgraham
Copy link
Contributor Author

ctgraham commented Sep 7, 2022

We should also note in the configuration that the effective selection of Grouping / Concatenation / FirstValue settings is dependent on the Aeon GroupRequestsByLocation key:
https://support.atlas-sys.com/hc/en-us/articles/360011919533-Submitting-Requests-via-EAD-Finding-Aids

If this key is set to "No", the Grouping* fields are ineffective/irrelevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants