ESciDoc Component Checksum Calculation
Checksum calculation of eSciDoc component is important from several aspects:
- Long-term preservation aspects
- to ensure that users will get exactly the content that is stored in a eSciDoc repository instance
eSciDoc Object manager core service must make sure that the checksum is calculated for each internally managed content of an eSciDoc component.
Scenarios[edit]
- A checksum is always calculated for the newly created files
- A checksum is always calculated when file content is newly uploaded thus replacing previous content
Post-condition[edit]
- A checksum for internally managed content is available latest before an item is released
- The internally managed content checksum and the algorithm used is delivered with the component properties, or within the content properties
eSciDoc and Fedora checksum built-in functionality[edit]
Fedora enables calculation of the checksum for each Fedora datastream in the repository. The default configuration of Fedora does not perform the checksum calculation of Fedora object datastreams.
For more details see Fedora checksum calculation
However, there are two options:
- overwrite default Fedora checksum operation (as described in Fedora documentation)
- provide separate checksum operation from within internal logic of the Object manager component
Checksum Algorithms[edit]
- see Checksum@Wikipedia
- see Hash functions overview
- see MD5 algorithm