Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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

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

Expand
titleExample

First name: bobcat
Last name: cataloging
Primary identifier: cataloger1
Password: trustnoone
Permissions: Cataloging Manager Profile
Issue: #27 (within alma-config repo)