The Aeon system is made up of 4 separate applications: a client that manages reading room activity, a staff manager that manages permissions, a configuration manager that manages Aeon configurations, and a set of front end webpages used by patrons. Most staff will only engage with the client. Managers will have permissions to make changes in the staff manager and the configuration manager.
For help with Aeon, please send tickets to the following:
For client setup and printing support: LTDS Service desk (78888@emory.edu)
For client configuration support and error messages: Core Services Application Support Team (coreserviceshelp@emory.edu)
For changes/additions to Aeon webpagesArchivesSpace application has an interface for staff and one for public discovery. The staff interface requires an Emory account. A breakdown of the different roles and responsibilities associated with ArchivesSpace is available in the Operations section of this Wiki.
For help with ArchivesSpace, please send tickets through the Aeon and ArchivesSpace Issue form
For permissions to log into the staff interface, contact your local repository manager. Staff not a part of one of the units below should contact the Rose representative for help.
- Rose: Gabrielle Dudley
- Pitts: Brandon Wason
- Health: Ashley Stevens
- Law: Anna Sturgill
- Oxford: Kerry Bowden
Documentation for managers setting permissions is available in the Permissions and User categories section of this wiki.
For changes/additions to the ArchivesSpace public interface, configuration needs, training needs, and enhancement requests: contact the Aeon product owner (currently Elizabeth Roke: erussey@emory.edu)
Training documentationArchivesSpace upgrades:
Documentation for Aeon is available on the Aeon website: https://support.atlas-sys.com/hc/en-us/categories/360000720853-Aeon . Of particular interest is:
- calendaring/appointment scheduling: https://support.atlas-sys.com/hc/en-us/articles/1500006225481-Managing-Appointments-in-the-Client
- SQL alias manager (for those who need to see more than one Emory repository in Aeon): https://support.atlas-sys.com/hc/en-us/articles/360011921593-Atlas-SQL-Alias-Manager
Emory maintains a few documentation sources for local issues and configuration:
...
ArchivesSpace is periodically upgraded. All upgrades are initiated by the product owner and do not require any actions by staff. Any questions related to new functionality should be directed to the product owner, not Core Systems or desktop support.
ArchivesSpace test environment:
The ArchivesSpace test environment is available for staff to test imports, try out functionality, and conduct training. Login credentials match those for production. The test environment is updated periodically without notice. The testing environment will also be used for testing upgrades so may not be in sync with production.
Local documentation:
Local documentation about specific data usage policies and best practices for Emory's instance of ArchivesSpace will be added here as developed.