Differences between revisions 1 and 9 (spanning 8 versions)
⇤ ← Revision 1 as of 2010-10-14 09:37:51 →
Size: 1576
Editor: eab
Comment:
← Revision 9 as of 2010-11-25 08:07:38 → ⇥
Size: 3026
Editor: eab
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
The purpose of the collection document is two-fold it is a documentation of the This collection contains the combined on-demand and continuously catalogued television programs from public Danish broadcasters.
Line 4: Line 4:
In general use references to patterns and other collections to allow new collection authors to be "standing on the shoulders of giants"~-[[http://en.wikipedia.org/wiki/Bernard_of_Chartres|[quote]]]-~. The continuously catalogued programs pose specific problems in relation to the structure of the collection.

The meta-data is in three formats, RITZAU_ORIGINAL_SCHEMA, GALLUP_ORIGINAL_SCHEMA and PBCORE_SCHEMA, these combine to provide the needed meta-data to describe the data.
Line 7: Line 9:
'''<doms:isPartOfCollection rdf:resource="info:fedora/doms:RadioTV_Collection"/>'''
Line 8: Line 11:
Default is:

isPartOfCollection doms:Root_Collection		 The TV_programs are part of the [[../RadioTV_Collection]]
Line 13: Line 14:
The Television Programs collection uses the [[../../../GuidelinesForNewDatamodel/PatternLanguage/Data_Shards|Data Shards]] and [[../../../GuidelinesForNewDatamodel/PatternLanguage/Access_Control_Planning/DOMS_Collection_Access_Control| DOMS Collection Access Control]] patterns. The shards help make more complex object structures into a unified object that, when included in a TV-Program allow [[DOMS_Access_Control]] to exert Authentication and Authorization checks to allow data access.
Line 14: Line 16:
This can be whatever is contained within.
Line 17: Line 19:
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.
 This collection is based on the patterns [[DOMS_Access_Control]] and [[Shards]] the rationale behind this is to facilitate the use of granulated data in a way that hides the granularity from this collection, and the DOMS system in general, thus allowing the [[DOMS_Access_Control]] pattern to maintain access control to a number of shards as if these where one.
Line 23: Line 22:
Sum up the elements in the collection here, if you feel that you need to justify parts of your collection, and have asserted that your plan is sound. Include the rationale here, if possible back it up with new patterns describing your special collection.
Line 25: Line 23:
== Workflow ==
This is the manual, if you want people to [[http://en.wikipedia.org/wiki/RTFM|RTFM]] make a [[http://en.wikipedia.org/wiki/Technical_writing#Example|FM]]		 ||For the description of this collection we will first describe a plausible document, then how it fits into the collection.<<BR>>A Document is an singular-entity in the DOMS, however a Television Program can consist of multiple parts in a file and of multiple files.( this is described in [[../../../GuidelinesForNewDatamodel/PatternLanguage/Data_Shards|Data Shards]]). We often want a single layer in multiple files, i.e. we have a program spanning multiple files, each file containing several layers of TV Stations.<<BR>>In this context the Shard concept should make more sense, each program contains shards, the access control authorization can now be effected on the program although the actual files may have many different access control settings. <<BR>><<BR>>[[https://doms.svn.sourceforge.net/svnroot/doms/testbed/trunk/modules/testbed_implementation/data/objects/radio%20tv%20collection/| Technical documents]]||{{attachment:radioTVCollections.png}}||
Line 28: Line 25:
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. == Work flow ==
Here is shown the work flow of manual digitalization.

{{attachment:ManuelTVDigitalisering.png}}

Here is shown the process of storing digital tv, dotted lines represent references

{{attachment:DigitalRadioTVModtagelse.png}}
Line 31: Line 35:
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.		 Attaqched is a description of the Public Broadcast Core v1.1 (PBCore) scheme used in the TV-Programs collection. This forms the mapping from Ritzaus to PBCore.
[[attachment:PBCore_1 1 map Ritzau.pdf]]
 

Television Programs

This collection contains the combined on-demand and continuously catalogued television programs from public Danish broadcasters.

The continuously catalogued programs pose specific problems in relation to the structure of the collection.

The meta-data is in three formats, RITZAU_ORIGINAL_SCHEMA, GALLUP_ORIGINAL_SCHEMA and PBCORE_SCHEMA, these combine to provide the needed meta-data to describe the data.

Is part of collection

<doms:isPartOfCollection rdf:resource="info:fedora/doms:RadioTV_Collection"/>

The TV_programs are part of the ../RadioTV_Collection

Contains, sub collections and objects

The Television Programs collection uses the Data Shards and DOMS Collection Access Control patterns. The shards help make more complex object structures into a unified object that, when included in a TV-Program allow DOMS_Access_Control to exert Authentication and Authorization checks to allow data access.

Pattern expression

This collection is based on the patterns DOMS_Access_Control and Shards the rationale behind this is to facilitate the use of granulated data in a way that hides the granularity from this collection, and the DOMS system in general, thus allowing the DOMS_Access_Control pattern to maintain access control to a number of shards as if these where one.

Collection description

For the description of this collection we will first describe a plausible document, then how it fits into the collection.
A Document is an singular-entity in the DOMS, however a Television Program can consist of multiple parts in a file and of multiple files.( this is described in Data Shards). We often want a single layer in multiple files, i.e. we have a program spanning multiple files, each file containing several layers of TV Stations.
In this context the Shard concept should make more sense, each program contains shards, the access control authorization can now be effected on the program although the actual files may have many different access control settings.

Technical documents

radioTVCollections.png

Work flow

Here is shown the work flow of manual digitalization.

ManuelTVDigitalisering.png

Here is shown the process of storing digital tv, dotted lines represent references

DigitalRadioTVModtagelse.png

Technical

Attaqched is a description of the Public Broadcast Core v1.1 (PBCore) scheme used in the TV-Programs collection. This forms the mapping from Ritzaus to PBCore. PBCore_1 1 map Ritzau.pdf

GuidelinesForNewDatamodel/Collections/Television_Programs (last edited 2010-12-07 12:36:08 by eab)