Radio-TV collection
As seen a lot of places, the Radio TV collection should be ingested and made available through DOMS. This document describes the datamodel used for the objects in DOMS.
Is part of collection
Default is:
isPartOfCollection doms:Root_Collection
Contains, sub collections and objects
This can be whatever is contained within.
Pattern expression
Write your pattern expression here, it's the rationale behind the collections structure.
Let the expression be your dreams, ideas and thoughts for the collection.
Collection description
We chose to use a Program-Centric datamodel. So, the primary object is the Program object, corresponding to one TV show, radio program, movie. There is no higher structure encoded in the datamodel, about relations between programs. So, while the programs (of course) contain information about when they were aired, there will be no links to the previous or next program. This structure must be dynamically created from an index.
Beside the program, the datamodel consist of two other types of objects, Shard and File. File objects represent one of the recording files, which spans multiple programs and channels. Shard represent the exact recording of this specific program. The trick here is that the Shard objects do not refer to real files. The files they refer to are created dynamically when needed. One the File objects refer to real files.
Collection
All the objects are part of the "doms:RadioTV_Collection". There is currently no subdivision among digital tv recordings, analog recordings and radio recordings. All the objects have a policy specifying that they are only viewable by administrators and users sitting inhouse.
Workflow
This is the manual, if you want people to RTFM make a FM
Describe the intended usage of and content addition to this collection, use all available measures that help clarify on the subject. Consider images in addition to text.
Technical
Be concrete and go into detail of things that require it, especially parts of the collection that is complex or of a special nature.
Consider using a drawing to illustrate relations or for instance include code/XML snippets.
Presentation
When being used by Summa, the datamodel described above should be presented as one record. Every Program object denotes a Summa record, and every program object is presented in a bundle with it's corresponding Shard object. The File objects are not presented to Summa.