Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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): https://princeton-psb.alma.exlibrisgroup.com

Sandbox development workflow (DRAFT):

  1. Proposal: Create a ticket proposing a development need on the alma-config repo (requires a GitHub account and inclusion into the PUL GitHub organization)
  2. Access: A system admin will deliver credentials with appropriate permissions.

  3. Development: Experiment and test in the sandbox.
  4. Review: After the proposed changes have been made in the sandbox, the system admin group reviews them.
  5. Communication: Upcoming changes to production are communicated to affected stakeholders (e.g., periodic check-ins with departments and open issues on the alma-config repo).
  6. 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

 Example (as sent by EUS in email)

First name: bobcat
Last name: cataloging
Primary identifier: cataloger1
Password: trustnoone (you'll need to change this immediately on login)
Permissions: Cataloging Manager Profile
Issue: #27 (within alma-config repo)






  • No labels