I created an ASC MHL History using the command line tool:
ascmhl create -h md5 16421225_Day001/
Afterwards, I manually changed the HashFormatType to 'failed' for first hash:
<md5 action="original" hashdate="2022-02-08T14:54:36.763024-08:00">9290a2ca3f586cb53da7cb516610fed2</md5>
I then ran the create command on the same directory. There was no error about the 'failed' HashFormatType. In the new 0002* MHL, the hash register for that file was kept, and the HashFormatType was changed to 'original':
Even though the md5 hash did not change and was technically accurate for the respective file, I expected this hash to be removed for the new MHL generation, due to the 'failed' HashFormatType.
I created an ASC MHL History using the command line tool:
ascmhl create -h md5 16421225_Day001/
Afterwards, I manually changed the HashFormatType to 'failed' for first hash:
<md5 action="original" hashdate="2022-02-08T14:54:36.763024-08:00">9290a2ca3f586cb53da7cb516610fed2</md5>
I then ran the create command on the same directory. There was no error about the 'failed' HashFormatType. In the new 0002* MHL, the hash register for that file was kept, and the HashFormatType was changed to 'original':
Even though the md5 hash did not change and was technically accurate for the respective file, I expected this hash to be removed for the new MHL generation, due to the 'failed' HashFormatType.
The data used for this is under /sources/104_verification_types/104f/ within the dataset on the G-Drive: https://drive.google.com/drive/folders/1PrAPczRFBQsVfjakbX-fqnDVHsAD-kd1