Checksum Mismatch Reporting

[photomedia]

Hi @jb4, thanks, this is coming along nicely! Tomasz and I just had a chat about what we'd want to happen when the mismatch is noted and here's what we're thinking:

By default:

• Stop the export for the EPrint where an md5 mismatch was noted
• Note issue in log
• Send an email to configurable email address to notify of issue
  (This will give the notified person a heads up to try to find an uncorrupted version of the file from backups to restore from)

If "force" flag is enabled:

• Calculate new md5 from file on disk and use that in manifest
• Write note to a preservation_note field in metadata.json indicating details about the mismatch, using the following template:

"preservation_note": "Checksum mismatch in EPrints on filename [filename], detected on [date]. Original md5 value [(md5 value stored in database]) overwritten with new value calculated from file on disk ([new md5 value calculated from file on disk])"

Does that seem feasible to you?

Originally posted by @tw4l in #14 (comment)