checksumpackage mismatch options for older packages

[dinahhandel]

As we prepare for data migration, checksumpackage will need to be able to handle older packages file paths, which will show a mismatch due to the filepath. Proposed change is to add option where if there is a mismatch, to print out the checksum and the filename.

[dinahhandel]

I forgot about this! But it's important! @dericed any thoughts about next steps?

[dericed]

Presently checksumpackage considers it an error when there is any mismatch between the previous checksum.md5 and the newly generated checksum.md5. I suggest dividing this into types of responses:

• The new checksum document includes references to new files in the package that weren't part of the original package (i.e. an scc file was added from a later workflow. This gets into the living-aip concept.)
• Error when the same relative filepath has a checksum mismatch between the old checksum.md5 and the newly generated checksum.md5

[dinahhandel]

@dericed is this still an issue to be resolved, and are these still the responses to focus on?