Difference between revisions of "Fixity checking and reporting"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
* Fixity Date, showing the date and time that the fixity check was run | * Fixity Date, showing the date and time that the fixity check was run | ||
* Fixity Result, showing the outcome (Succeeded or Failed) with links to tool output in cases of failures or errors (successful fixity scan reports are empty) | * Fixity Result, showing the outcome (Succeeded or Failed) with links to tool output in cases of failures or errors (successful fixity scan reports are empty) | ||
| − | |||
===Fixity Results: Failed=== | ===Fixity Results: Failed=== | ||
Failures should be reported as such if they are actual fixity failures, or if there were errors in the tool. | Failures should be reported as such if they are actual fixity failures, or if there were errors in the tool. | ||
Revision as of 16:40, 14 August 2015
Main Page > Documentation > Requirements > Fixity checking and reporting
This wiki page describes requirements for gathering fixity check information from the | Fixity app and reporting through the Archivematica Storage Service.
Requirements
- Modify Storage Service to record time and results of fixity checks by adding columns to packages tab
- Add script to send email alerts to administrator(s) when a fixity check fails
Mockups
Storage Service packages tab
Two columns are added to the Storage Service packages tab:
- Fixity Date, showing the date and time that the fixity check was run
- Fixity Result, showing the outcome (Succeeded or Failed) with links to tool output in cases of failures or errors (successful fixity scan reports are empty)
Fixity Results: Failed
Failures should be reported as such if they are actual fixity failures, or if there were errors in the tool.