##Task
## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting
## as they may become relevant later on.

= C.3 Active logical Integrity Checking =

## Valid states: "Not started", "In progress" and "Finished"
'''State:''' Not started

## The time used is measured in man days and does not include the time spent on any sub-tasks.
'''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.

## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions.
## Any available (technical) details goes into the below documentation pages.

## == Sub tasks ==
##  . [:TaskX.Y.Z:Add sub task link 1 here]
##  . [:TaskX.Y.Z:Add sub task link 2 here]
##  . ..[[BR]]
##  . ..[[BR]]
##  . ..
##  . [:TaskX.Y.Z:Add sub task link N here]

== Documentation ==

## The documentation section links to the documentation relevant to this task and its sub-tasks (if any).
##
## The below links will automatically be expanded to page names like "MyTaskPageNameAnalysisDocument" in your created page.
## This should be a proper default, however, it may be changed.

 * [[TaskC.3AnalysisDocument|Analysis Document]]
## * [:TaskC.3DesignDocument:Design Document]
## * [:TaskC.3SystemMaintenanceDocument:System Set-up and Maintenance Document]

== Parent task ==
 * [[TaskC]]

== Progress history ==

<<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskC.3)>>

## Add information about about the current state of the task here. That is, information about what has been completed so far and
## what outstanding issues that are left. Example:
##
##=== 2007-09-13 ===
##Finished the design documentation. A review is needed before this task can is completed.
##
##=== 2007-08-25 ===
##Completed requirement specification. We are now ready for writing the design document.

=== 2007-10-05 ===
Created task from TDR identification work