- Article Type: General
- Product: Rosetta
- Product Version: 2.2
Rosetta does fixity in the following instances:
• When the deposit server receives a deposit, fixity is done and compared with the value provided in the METS of the SIP (if provided). The “missing” fixity values (SHA1, MD5, CRC32) are filled in.
• As a part of the validation stack in the fixity task. The value is compared with the value filled in by the deposit server.
• When the file is moved to the permanent repository. That completes (from a Rosetta perspective) the chain of custody from the deposit all the way through to permanent.
- Article last edited: 10/8/2013