|
Size: 2774
Comment:
|
← Revision 3 as of 2010-03-17 13:12:48 ⇥
Size: 2775
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 39: | Line 39: |
| * [:TaskC.3AnalysisDocument:Analysis Document] | * [[TaskC.3AnalysisDocument|Analysis Document]] |
| Line 44: | Line 44: |
| * ["TaskC"] | * [[TaskC]] |
| Line 48: | Line 48: |
| [[PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskC.3)]] | <<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskC.3)>> |
C.3 Active logical Integrity Checking
State: Not started
Time used: 0 md.
Description
We need to write software to integrity check our repository. That is, ensure the DOMS system has an automated verification of its internal references, meta data and the audit trails of the content.
The integrity check must ensure that the repository has no broken references, that is, ensure no referenced content can disappear and no references can be made to content that does not exist in the repository. It must also ensure that all meta data conforms to the standard/format that it is supposed to, and that the audit trail has been properly updated with event information whenever any content has been migrated/transformed.
This check should run as a periodic test. The test is identical or similar to the test that should be done during ingest.
Documentation
Parent task
Progress history
| Iteration | Time used | Status | Notes | |
| ActionValidator | 14 | 0md | Description in progress |
2007-10-05
Created task from TDR identification work