|
Size: 1750
Comment:
|
← Revision 16 as of 2010-05-25 12:41:56 ⇥
Size: 1483
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| ---- /!\ '''Edit conflict - other version:''' ---- description of datastructure moved to: [GuidelinesForNewDatamodel/Collections/Anker%20Kirkeby|Anker Kirkeby Collection] |
description of datastructure moved to: [[GuidelinesForNewDatamodel/Collections/Anker Kirkeby|Anker Kirkeby Collection]] |
| Line 24: | Line 23: |
| ---- /!\ '''Edit conflict - your version:''' ---- description of datastructure moved to: [GuidelinesForNewDatamodel/Collections/Anker Kirkeby|Anker Kirkeby Collection] ---- /!\ '''End of edit conflict''' ---- |
The Anker Kirkeby Collection **
Context
The Anker Kirkeby collection is a historical collection comprised of recordings of cultural value, these are from the first half of the 20th century and are digitized from 78rpm records.
It contains voice recordings of important Danish figures, sound clips from the 1930's, Danish journalism from London during the 1940-1945 occupation, etc.
The collection is already digitized and the data originates from a relational database, thus it heavily influenced by the Old Collections pattern
Description of pattern
description of datastructure moved to: Anker Kirkeby Collection
Problem description
To a great extend the problem consists of being able to migrate the original database to the DOMS, this is a technically trivial task since the ECMs facilitate this quite well. The main difference is that the DOMS solution will combine all the data about a given recording into one document, fields which have multiple field-entries can be represented in the Datamodel format.
Solution
The structure of the pattern will be a replication of table 1. This is due to the static nature of the collection, being a previously digitized.