[Zope-CMF] List of subject/metadata sets?

[Ken Manheimer]

I concur with this approach - i have used local roles in related ways in
both the tracker and my wiki work.  I think there's a pattern here to 
consolidate in mechanism - probably in the workgroup stuff...

Ken
klm@digicool.com

On Thu, 14 Jun 2001, Shane Hathaway wrote:

> "Meilicke, Scott" wrote:
> > The default CMF as I perceive it is geared around one person owning a chuck
> > of something, and not so much a team effort for that chunk.  For example, if
> > I publish a short manual on how to do something, no one else can later
> > modify/update the manual except for me.
> 
> I think we're much closer to workgroup functionality than we used to be.
> 
> On the security tab of your portal root, create a new role.  Call it
> "Workgroup Member".  Give the Workgroup Member role the "Add portal
> content" and "Modify portal content" permission.
> 
> Now, don't give your users the "Workgroup Member" role globally.  That
> would be pointless. :-)  Instead, in each of your workgroup folders
> assign local roles to individual users.  You can find local roles
> through a link on the security tab of all folders.
> 
> Now here's the cutting edge part: I think you'll need DCWorkflow (or
> your own workflow) to make this work.  You'll need to be able to assign
> the "Workgroup Member" role the "View" permission when objects are in
> the "private" state, or you'll need to use the "visible" state instead
> (which is probably better).
> 
> The thing I perceive to be missing is the fact that assigning local
> roles is tedious for large numbers of users and we don't have a
> mechanism yet for managing users through the portal UI.  But you can
> work around this.