## Please put instances of this page in the Actions/ subfolder
= Action Datamodel =
## The persons assigned to the action
 Assigned:: EAB, MAR, EK

## The persons that previously worked on this action
 Prev assigned::

## The tasks from the WBS that are adressed by this action
 Tasks adressed:: [[Tasks/1/1/1]], [[Tasks/1/1/2]], [[Tasks/1/2]], [[Tasks/1/3]], [[Tasks/1/4]], [[Tasks/1/5]], [[Tasks/7/2]], 

## Time remaining on this action. Use the format Xmd, to indicate the number of man-days estimated.
 Time remaining:: 2md

## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated
 Time estimated:: 11md 

## The time used for this action so far. Same format as Time estimated
## Time used:: PKO: 1        EK: 4     KFC: ½

## The priority of this action. 1-9. 1 is highest.
 Priority:: 8

## The status of this action, legal values are 'Not described', 'Not started', 'In progress' and 'Finished'
 Status:: In progress

## The iteration that this actions belongs to
 Iteration:: 23,24

## Notes about this action, that should be viewable on other pages
 Notes:: 

In this action, we intend to describe the DOMS datamodel.
This includes an evaluation of the use of FRBR for DOMS.

The outcome of the seven tasks will (hopefully) be a basic datamodel for all present and future digital collections in DOMS.

 * We describe FRBR and give examples of how the model may be used in general. See [[How to use FRBR]] 
 
 * We examine how we can modify the FRBR-datamodel to fit into Fedora - and how we can combine it with the Patterne Language-model. See Diagram shown (with comments) on [[DataModelWorkDiagram]]. Also see [[GuidelinesForNewDatamodel/PatternLanguage/FRBR Relations]]

 * We analyse the digitisation workflow in view of the datamodel and the GUI. See [[Analyse Workflow]]

 * We design the datamodel and comply with [[GuidelinesForNewDatamodel]].

 * We decide if we need to use the PREMIS semantic units. See [[PREMIS not in DOMS]]

 * We will test the datamodel in relation to Fedora and GUI.

 * The relevant documentation will be extracted and published
 

## Detailed description of wanted output from the work to be carried out.
## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written.


== Checklist For Working On An Action ==

The Life Cycle of an Action:
 * ''Assign people for action definition'': Done at start of iteration status meeting. Fill out '''Assigned'''
 * ''Define the action'': Describe information about what is to be done and how. Fill out '''Tasks Addressed''' and '''Time Estimated'''.
 * ''Review the definition'': Get another project group member to review the action definition, and update it.
 * ''Assign people for action implementation'': Done by project manager, usually the same persons who wrote the definition. Fill out '''Assigned''' and '''Prev assigned''' if new persons are assigned.
 * ''Implement the action'': See details below
 * ''Review the action'': Get another project group member to review what is implemented (code and documentation), and update it.
 * ''Finish the action'': Change the status to "Finished" and update the "time used" field on the action page.

Please make sure that you address the below issues, when working on an action:
 * Update the state of the action to "In Progress" when you start working on it.
 * Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.
 * Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. '''Hint:''' Continually updating the "Time used" field will make it easier for you.
 * Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.