|
⇤ ← Revision 1 as of 2010-09-30 08:35:22
Size: 368
Comment:
|
Size: 1633
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| = Name and grade ** = grade is 0-2 stars ()or(*)or(**) |
= DOMS Collection Access Control ** = |
| Line 8: | Line 7: |
| When creating a data-model where the objects are all of the same work, | The implementation of access control in the DOMS. This pattern builds upon the [[../../Access_Control_Planning|Access Control Planning]] pattern, and is a more concrete version of these principles. |
| Line 12: | Line 11: |
'''In bold font''' |
''' DOMS can ensure Access Control (AC) on a "object" level of granularity, thus objects pointing to files containing multiple "streams" of content, will need a system , that varies in AC rights will need. This pattern describes that system. ''' |
| Line 17: | Line 16: |
| Many collections will contain a lot of split up data, imagine for instance a Newspaper collection, each page will have its own document as part of a section again a part of a newspaper, which is part of a newspapers accumulated editions. | |
| Line 18: | Line 18: |
| Likewise many born-digital formats contain a lot of layered data in the files, one example is the MPEG-4 format used in the televised materials collection, each file is 3hours long and contain several streams of video as well as textual information about the programs. | |
| Line 21: | Line 22: |
| '''In bold font''' |
''' The data model should accommodate the restrictions of the access control system, this is done using [[../data shards|shards]], the shards describes the parts that make up the object on which access is being controlled. ''' |
| Line 24: | Line 26: |
| The creation and splitting of data is of importance, is it possible to split the data in such a way that it can be presented without modification? If not what can be done to make the re-assembly of shards easier? |
DOMS Collection Access Control **
Context
The implementation of access control in the DOMS. This pattern builds upon the Access Control Planning pattern, and is a more concrete version of these principles.
Description of pattern
DOMS can ensure Access Control (AC) on a "object" level of granularity, thus objects pointing to files containing multiple "streams" of content, will need a system , that varies in AC rights will need. This pattern describes that system.
Problem description
Many collections will contain a lot of split up data, imagine for instance a Newspaper collection, each page will have its own document as part of a section again a part of a newspaper, which is part of a newspapers accumulated editions.
Likewise many born-digital formats contain a lot of layered data in the files, one example is the MPEG-4 format used in the televised materials collection, each file is 3hours long and contain several streams of video as well as textual information about the programs.
Solution
The data model should accommodate the restrictions of the access control system, this is done using shards, the shards describes the parts that make up the object on which access is being controlled.
Consider next
The creation and splitting of data is of importance, is it possible to split the data in such a way that it can be presented without modification? If not what can be done to make the re-assembly of shards easier?