##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.

= A.3. Setup or coordinate the setup of Fedora and BitFinder with IT maintenance =

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

## The time used is measured in man days and does not include the time spent on any sub-tasks.
'''Time used:''' Not reported; Iteration 11: 6 md

== Description ==

## 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.

The DOMS repository (ie. the system that actually stores the data/metadata) consist of the major components. It is the purpose of this task to 
construct these components. The first component is Fedora (LINK), which is used to store the metadata. The second is the BitFinder service, provided
by the inhouse IT Maintenance department. Both of these must be configured for the specific demands of the DOMS and the MiniDOMS.
In addition, we would like Application Support/Maintenance to handle the daily running of the end systems. This form of this support must be agreed upon.

So, the tasks are at least:
 * The MiniDOMS BitFinder service
 * Config of the MiniDOMS fedora
 * Support agreement for the MiniDOMS
 * The DOMS BitFinder service
 * Config of the DOMS fedora
 * Support agreement for the DOMS

We have decided to use Fedora 2.2.1 for the MiniDOMS, and Fedora 3.x for DOMS.


## == 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.
 
 * [[TaskA.3AnalysisDocument| Analysis Document]]
## * [:TaskA.3AnalysisDocument: Analysis Document]
## * [:TaskA.3DesignDocument: Design Document]
## * [:TaskA.3SystemMaintenanceDocument: System Set-up and Maintenance Document]

== Parent task ==
 * [[TaskA]]

== Progress history ==

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

=== Minutes and documents produced ===

==== BitFinder ====
 * [[Bitstorage|Our requirements]]
 * [[Minutes/2007-12-20| Referat 2007-12-20]]
 * [[Minutes/2008-01-10| Referat 2008-01-10]]
 * [[Minutes/2008-01-28| Referat 2008-01-28]]
 * BitstorageAgreement
 * [[MaintenanceAgreementMiniDOMS| Production Agreement]]

==== Fedora ====



## 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-10 ===
##Met with JHLJ and discussed bit storage.