These scripts are commonly run on accessions in the backlog, and if they are changing the bag, the preservation_log.txt must get updated as well. We could automatically do this as part of the script. See the validate_fixity.py in the hub-monitoring repo for how this is handled.
However, to keep the scripts flexible for use in other contexts, it should be an optional step. It could be a script argument, or it could just do nothing if there is no preservation_log.txt in the expected location.
These scripts are commonly run on accessions in the backlog, and if they are changing the bag, the preservation_log.txt must get updated as well. We could automatically do this as part of the script. See the validate_fixity.py in the hub-monitoring repo for how this is handled.
However, to keep the scripts flexible for use in other contexts, it should be an optional step. It could be a script argument, or it could just do nothing if there is no preservation_log.txt in the expected location.