Closed amhanson9 closed 2 months ago
I'm not able to replicate the error in my new dev environment. My best guess is it happened from bags that could not be validated with bagit, since validate_bag() and validate_bag_manifest() both update the preservation log, only in my new dev environment the bags are validating with bagit fine.
Collections that originally printed double: ms3770, ua12-022, and ua0138.
@emkaser Since it just prints twice for an accession, is it ok to leave it as is? Or if hat is confusing (e.g., looks like the script is malfunctioning), we might be able to get validate_bag_manifest() to not print the error from update_preservation_Log().
The print statements for a preservation log is missing or has nonstandard columns are sometimes printed twice for an accession. The print statements are generated in update_preservation_log().
These accessions have _bag and _FITS folders, but there are other accessions that only print once and also have _bag and _FITS folders, so that does not appear to be the issue this time.