##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.2.3. Meta Data Content =

## 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 + 3/4 md...; iteration 11: 4½ md

== Description ==

We need to find out exactly what metadata we need to be able to represent in DOMS objects.

Note that this is not the metadata specific to collections, but rather the metadata that should be present in all DOMS objects, or at least in all DOMS objects of one of the base types identified in [[TaskA.2.2]].

We should identify all these metadata and decide the format we wish to save them in.

Thus this defines a framework for describing stored metadata and mandatory content in that framework.

The considerations about metadata needed includes, but may not be limited to:
 * IDs, 
 * administrative metadata/audit-trail req., 
 * Language (internationalisation),
 * Rights (Coordinate with DK-AAI)

Note that the analysis document contains a long list of TDR requirements that identify some properties we should consider when identifying metadata requirements.

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

 * [[TaskA.2.3AnalysisDocument|Analysis Document]]
 * [[TaskA.2.3DesignDocument|Design Document]]
 * [[TaskA.2.3SystemMaintenanceDocument|System Set-up and Maintenance Document]]

== Parent task ==
 * [[TaskA.2]]

== Progress history ==

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

Done for MiniDOMS, according the DataModel. Many requirements have been ignored, which must be adressed for DOMS

=== 2007-11-22 ===
 * Completed ActionSalvageDataModel

=== 2008-08-28 ===

In connection with [[ActionDataModelTDRRequirements]], we discovered a few TODOs for the data model. These have been added to the analysis document. 

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