##Analysis Documentation

## Headline such as "Analysis of Backup Requirements"

= Analysis of Build Systems to Extract/Build/Generate/Ingest Fedora Digital Objects =

## Add detailed explanation/analysis of the task(problem)/action.

## This may include use-case diagrams etc. attached like this:
## attachment:MyUseCase.png

When addressing this task, we should consult the following TDR requirements:

 * Collection specific requirements we should consider to some degree in DOMS B1.3, B1.4, B1.6, B2.3, C2.1, R72
 * File integrity checking during ingest, fail on errors: B1.6, B1.8, B2.6, R48
 * Proper reporting required from ingest module, ensure only complete objects are ingested and reported ok, report indicates preservation status B1.7, B1.8, B1.9, R48-49, R63
 * Ensure received data cannot be modified during ingest: R50
 * Format definitions required, note that the intended usage of the format is relevant as well, use standard format registries: B2.1, B2.2, B3.3, R48, R62, R73
 * Must be able to document the data we have in the repository is derived from the data we received, and how: B2.3, R51, R54-56, R59, R68
 * Referential integrity required between file storage and metadata (creation and validation): B4.2, B4.3, D1.5, D1.6, R64, R69


See [[TaskC.1AnalysisDocumentDetails#CollSpec]] 

See [[TaskC.1AnalysisDocumentDetails#FileIntegrity]] 

See [[TaskC.1AnalysisDocumentDetails#ReportingFromIngestModule]] 

See [[TaskC.1AnalysisDocumentDetails#NoModificationDuringIngest]] 

See [[TaskC.1AnalysisDocumentDetails#FormatDefinitions]] 

See [[TaskC.1AnalysisDocumentDetails#Derivation]] 

See [[TaskC.1AnalysisDocumentDetails#ReferntialIntegrity]] 


##== Prerequisites and Assumptions ==
## Describe any prerequisites and assumptions that are important for this analysis, e.g.:
## What can we rely on?
## Which assumptions must hold in order to solve the problem described in this document?

##== Risks and Potential Problems ==
## Describe anything that may cause problems when solving this task.

##== Stakeholders ==
## List of links to any relevant stakeholders. That is, people who has knowledge about this task or in any other way are relevant to contact for input.

##||<tablewidth="98%" tablestyle="text-align: left;"30% bgcolor="#cccccc" style="text-align: left;">Stakeholder ||<bgcolor="#cccccc" style="text-align: left;">Knowledge||
##||["Link to stakeholder"] ||Usability expert. ||
##||["Link to Bart Ender"] ||Expert on mixing margaritas ||
##||["Link to out esteemed customer"] ||The guy with the money who actually may know what he wants. ||

##== Resources ==
## List links to documents, wiki pages etc. that are relevant to this analysis.
## * [:LinkToMyRessource:Use case diagram xx]
## * [:LinkToMyVersionControlledDocument:Link to document on user studies e.g. stored in SVN]