Bulk Changes Testing Workflow for ArchivesSpace API Projects - smith-special-collections/sc-documentation GitHub Wiki

Overview

In order to reduce the chance of error, the following steps must be followed before running new or modified scripts on the production ArchivesSpace server. This process is in addition to QC done as part of script development.

Note: Running scripts using the API is currently the only way we make bulk changes (beyond one resource record) to ArchivesSpace. This policy should be used (with appropriate changes) for any future tool used for bulk changes.

Steps

• Prior to running the script on the test server, the reviewer will review the logic used in the code with the developer (required for new scripts, optional for modified scripts).
• Prior to running the script on the production server, the reviewer and (when appropriate) other stakeholders will check a sample of modified or newly created records on the test server.
• As a final step before running the script, the person running the script will submit a ticket to Lyrasis requesting the server be backed up.
• The reviewer and (when appropriate) other stakeholders will check a sample of modified or newly created records on the production server.