Difference between revisions of "AIP integrity checking"
m (Move to feature requirements category) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
[[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > AIP integrity checking | [[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > AIP integrity checking | ||
| − | + | This is critical requirement because it is required by OAIS, page 4-8, section 4.1.1.3: "The '''Error Checking''' function provides statistically acceptable assurance that no components of the AIP are corrupted during any internal Archival Storage data transfer. This function requires that all hardware and software within the archive provide notification of potential errors and that these errors are routed to standard error logs that are checked by the Archival Storage staff. The PDI Fixity Information provides some assurance that the Content Information has not been altered as the AIP is moved and accessed. Similar information is needed to protect the PDI itself...The storage facility procedures should provide for random verification of the integrity of data objects using CRCs or some other error checking mechanism." | |
| + | |||
| + | From [[Development_roadmap#AIP_storage|0.8 Development roadmap]]: | ||
* AIP storage integrity checking and logging to confirm that: | * AIP storage integrity checking and logging to confirm that: | ||
** write to storage was successful (completed) | ** write to storage was successful (completed) | ||
| − | ** | + | ** ongoing integrity of the AIP is maintained and can be demonstrated. ([https://wiki.umiacs.umd.edu/adapt/index.php/Ace ACE]?) |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | See also [[Fixity checking and reporting]] | ||
| − | [[Category: | + | [[Category:Feature requirements]] |
Latest revision as of 13:46, 23 March 2017
Main Page > Development > Development documentation > AIP integrity checking
This is critical requirement because it is required by OAIS, page 4-8, section 4.1.1.3: "The Error Checking function provides statistically acceptable assurance that no components of the AIP are corrupted during any internal Archival Storage data transfer. This function requires that all hardware and software within the archive provide notification of potential errors and that these errors are routed to standard error logs that are checked by the Archival Storage staff. The PDI Fixity Information provides some assurance that the Content Information has not been altered as the AIP is moved and accessed. Similar information is needed to protect the PDI itself...The storage facility procedures should provide for random verification of the integrity of data objects using CRCs or some other error checking mechanism."
From 0.8 Development roadmap:
- AIP storage integrity checking and logging to confirm that:
- write to storage was successful (completed)
- ongoing integrity of the AIP is maintained and can be demonstrated. (ACE?)
See also Fixity checking and reporting