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).
...
- 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
...
- Allowed S/FTP connections needs to be updated (config > Allowed S/FTP connections > import)
- Allowed Emails need to be restored (config > Allowed Emails > import)
- Ensure that lib-sftp-staging connection has been copied over from production (or recreate it using credentials in LastPass) (config > General > S/FTP Definitions)
- Publishing profiles need to be pointed to lib-sftp-staging for the "Incremental Publishing" and "General Publishing" profiles (Resources > Publishing Profiles)
- Webhook integration profile needs to updated be activated and saved. (config > Integration Profiles)
- 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 (from list exported above in 'Before refresh' steps and saved to MEO Team Drive)
...