#25 Improve checksum handling post manifest creation

[John]

This probably is not a manifest maker issue, but I have no other place to put it...

Currently, one of the barriers to agency transfers is requiring the use of manifest maker. The hardest part about it is making sure that the barcode numbers for the files match up with the barcode numbers in the item list.

Sometimes, it is better all round if an agency does not have to worry about doing this. An example we have at the moment is a quite important agency who refuses to do much in the way of transfer documentation for paper records and have no desire to do much in the way of manifests. In the paper world, we would normally accept the transfer of their paper records, then arrange and describe them so that they can be used by researchers. For the digital records, it is likely that we will accept a bunch of files, then spend time arranging them into a reasonable order before ingest to the digital archive

What would be useful is for a tool that can confirm a file's integrity, by reference to a manifest, no matter what the pathname, etc is.

This would enable an agency just to provide checksums for every data object, the NAA to rearrange those data object into different items and then confirm that the files have not been changed in any way in the meantime