## page was renamed from A.2. Identify metadata to manage and structure for management
##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. Identify Meta Data to Manage and Structure for Management =

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

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

With basis in identified data from [[TaskA.1]], we need to define the model used for storage in DOMS.

Since Fedora is selected as metadata repository, this datamodel must be described in Fedora terms. Pre-analysis has given a promising datamodel that needs to be fleshed out and fully implemented.

In order to use this metadata model, we need to extend Fedora with the concept of types. This work has already been started with [[http://fedora.statsbiblioteket.dk/fedoraWiki/RIFF|RIFF]] for Fedora 2.x, but that work needs to be finished, and updated to Fedora 3.x

The actual types from our metadata model then needs to be implemented in that framework.

== Sub tasks ==

 . [[TaskA.2.1|A.2.1. Fedora-typesystem]]
 . [[TaskA.2.2|A.2.2. Define base types for DOMS]]
 . [[TaskA.2.3|A.2.3. Metadata content]]

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

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

== Progress history ==

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



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