Differences between revisions 4 and 5
Revision 4 as of 2010-10-14 13:00:11
Size: 2071
Editor: eab
Comment:
Revision 5 as of 2010-10-20 10:57:51
Size: 3174
Editor: eab
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
The Television Programs collection uses the [[Shards]] and [[DOMS_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. 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 23: Line 23:



{{attachment:radioTVCollections.png}}
||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}}||

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, <!> add stuff ...

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

  • <!> <!> 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.

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