Access Policies via Models
Title (Goal) | Support Fedora 3-style object classes (content models) - Access Policies via Models |
---|---|
Primary Actor | Repository architect & implementer |
Scope | Data architecture and access |
Level | High |
Story (A paragraph or two describing what happens) | As a repository manager,
|
Examples
- Given the myns:image object, I want to create some access policies that allow only users in imaging group to view and update that object.
- If a user adds the mymix:published_web mixin, access to that object, some of its properties, and the web_thumbnail, web_small and web_large datastreams is granted to web users.
- If a user removes the mymix:published_web mixin, access to the object, all its properties and children is revoked for all web users.