Access Policies via Models

Title (Goal)Support Fedora 3-style object classes (content models) - Access Policies via Models
Primary ActorRepository architect & implementer 
ScopeData architecture and access
LevelHigh 
Story (A paragraph or two describing what happens)

As a repository manager,

  1. I can associate access policies to "content models"

Examples

  1. 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.
  2. 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. 
  3. If a user removes the mymix:published_web mixin, access to the object, all its properties and children is revoked for all web users.