- How do library staff record system failures and request support?
- Notify LTS so that LTS has a complete record of system failures and resolutions
- LTS/HUIT submits requests for technical support to Atlas and monitors time to resolutions
- How are patrons and staff notified of system down-time?
- LTS/HUIT is responsible for evaluating whether Atlas is meeting its support obligations, based on Harvard/Atlas SLA.
...
Administrative Access Policy
As of 8/25/2017, the following administrative access policies apply to both the Aeon test environment and production environment:
- Customization Manager: Only one primary contact for the system and one backup contact for the system have access to the Customization Manager. The current primary contact is Marilyn Rackley and the backup contact is Spruill Harder. The primary and backup contacts can be reviewed and modified as needed.
- Staff Manager: Only LTS staff have access to the Staff Manager; LTS is responsible for creating staff accounts and updating staff permissions.
- Web Directory (system web pages): Harvard staff do not have direct access to modify the system web pages. All changes must be made by Atlas Systems staff.
All Harvard administrative users with access to the Customization Manager or the Staff Manager must have a unique ID and password that meets the Harvardstrong password requirement. No system user may use a group, shared, or generic account.
Access for any terminated administrative users must be deactivated as soon as the user is terminated.
Requesting New Staff Accounts and System Changes
New staff client accounts or client account changes should be requested through LTS following these instructions.
System configuration changes should be submitted to
Modifications of Harvard Aeon web pages will be drafted and submitted to Atlas Systems staff by the primary or backup contact for the system, and Atlas staff will modify the pages as requested, provided the modifications do not violate PCI security standard requirements.