A.2.3. Meta Data Content

State: In progress

Time used: Not reported + 3/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.

Documentation

• [: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.