In addition to our production environment, we have a sandbox environment which we will use for targeted development and experimentation. The sandbox is a copy of our production environment, refreshed biannually (in Feb and Aug).
Logging In
- Regular staff login (CAS): https://princeton-psb.alma.exlibrisgroup.com/SAML
- For generic users (e.g. catbasic1): https://princeton-psb.alma.exlibrisgroup.com
Sandbox development workflow
- Proposal: Create a ticket proposing a development need on the alma-config repo (requires a free GitHub account and inclusion into the PUL GitHub organization)
Access: system admins will assign additional permissions as needed
- Development: Experiment and test in the sandbox
- Review: After the proposed changes have been made in the sandbox, they are reviewed with the system admin group
- Communication: Upcoming changes to production are communicated to affected stakeholders (e.g., during departmental check-ins and in issues on the alma-config repo)
- Implementation: System admins implement the approved changes in production
Refresh System Administrator Tasks
Twice yearly (in Aug and Feb) the sandbox is refreshed. The following tasks need to be done by the system administrators:
Before refresh
- Export lists of roles for users with roles differing from their prod roles
- Export S/FTP connections
- Export allowed emails
- Note webhook integration profile settings
After refresh
- Allowed S/FTP connections needs to be updated (config > Allowed S/FTP connections)
- Allowed Emails need to be restored (config > Allowed Emails)
- Webhook integration profile needs to updated (config > Integration Profiles)
- lib-sftp connection needs to have the Sub-Directory changed /alma/sandbox
- Alma color scheme needs to be changed to orange (prod is black) (config >
- Sandbox banner needs to be recreated (config > institution notifications)
- Elevated Permissions need to be updated