|
Size: 3213
Comment:
|
← Revision 6 as of 2010-03-17 13:12:53 ⇥
Size: 3216
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| 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"]. | 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]]. |
| Line 49: | Line 49: |
| * [:TaskA.2.3AnalysisDocument:Analysis Document] * [:TaskA.2.3DesignDocument:Design Document] * [:TaskA.2.3SystemMaintenanceDocument:System Set-up and Maintenance Document] |
* [[TaskA.2.3AnalysisDocument|Analysis Document]] * [[TaskA.2.3DesignDocument|Design Document]] * [[TaskA.2.3SystemMaintenanceDocument|System Set-up and Maintenance Document]] |
| Line 54: | Line 54: |
| * ["TaskA.2"] | * [[TaskA.2]] |
| Line 58: | Line 58: |
| [[PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskA.2.3)]] | <<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskA.2.3)>> |
| Line 67: | Line 67: |
| In connection with [:ActionDataModelTDRRequirements:], we discovered a few TODOs for the data model. These have been added to the analysis document. | In connection with [[ActionDataModelTDRRequirements]], we discovered a few TODOs for the data model. These have been added to the analysis document. |
A.2.3. Meta Data Content
State: In progress
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.
Documentation
Parent task
Progress history
| Iteration | Time used | Status | Notes | |
| ActionDataModelTDRRequirements | 11 | 1.5md | Finished |
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.