In our development process for the Merritt repository, we first create a detailed specification for each micro-service and then develop software based upon the specification. Having a specification helps us think through issues and work out problems before we start to write code. It's always helpful to have people reviewing our specifications, to notice issues or implications we may have missed or not fully understoodUC3 staff presented a webinar on the Merritt Fixity service on Thursday, March 7, 2011. The presentation slides and a recording of the voice/web stream are available.
Fixity is a method to test for file integrity and corruption. The Fixity service will verify the bit-level integrity of files managed in the Merritt Repository with a two-part test: Is the filesize of each file unchanged? Is the message digest value of each file unchanged?