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).
Sandbox URL (requires credentials provided by system administrators, see below): URLs:
- For everyone: https://princeton-psb.alma.exlibrisgroup.com/SAML
- For generic users (e.g. catbasic1): https://princeton-psb.alma.exlibrisgroup.com
Sandbox development workflow (DRAFT):
- 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: A system admin will deliver credentials with appropriate permissions.s 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 reviews them.
- Communication: Upcoming changes to production are communicated to affected stakeholders (e.g., periodic during departmental check-ins with departments and open in issues on the alma-config repo).
- Implementation: System admins implement the change in production.
Sandbox credentials template (note: the following process will not be needed after the next sandbox refresh in Feb 2022; it's only necessary if users are anonymized)
First name: netid of tester
Last name: functional area
Primary identifier: functional area+sequential number
User Group: P Faculty & Professional
Password: one-time password
Force password change on next login: yes
Permissions: as appropriate to task
...
| title | Example (as sent by EUS in email) |
|---|
...
- approved changes in production
...