By thinguy on

Working on internal site that will have about 15 groups. Each group will need a member role and a moderator role. So 30 roles total. Using Workflow, OG, and TAC-Lite (2-4 schemes) to setup Members with the ability to create content and moderators publish it.

Is this too complicated, too much overhead for performance, etc.

⋅ Categories: Drupal 6.x

Comments

adam_b’s picture

adam_b commented

I don't know if performance would be an issue, but it definitely looks too complicated - Organic Groups membership should cross-reference the two roles without you needing to replicate them for each group.

WorldFallz’s picture

WorldFallz commented

Maybe I don't understand-- but why 30 roles? Why not 2 roles (member and moderator) for each group? You should not have to create a 'group1 member' and 'group1 moderator' for each group. Moreover, depending on what functionality you want for your moderators, the built-in group admin might be all you need.

thinguy’s picture

thinguy commented

Using the individual roles with TAC-Lite is the only way I've found to meet my goals.

I'd like members of a group to be able to create content and a moderator publish the content.
Member or moderator should be able to pick if the content should be seen by public, any-authenticated, or just their group.
And content that isn't published(draft) should not be seen by anyone but author and moderator of their group.
Moderator should only have access to their groups content.

Even with OGUR, workflow, and TAC-Lite or TAC using just a member and/or moderator I've not been able to accomplish all these goals.
I looked revisioning and module_grants they seemed to complicated for my audience and backend needs.

Anyone have any tips to simplify this?

WorldFallz’s picture

WorldFallz commented

The only thing I see there that can't be done with just og and ogur is the anonymous ('public') vs authenticated access control. Ideally it would be nice if anonymous showed up in the group fieldset, but since it doesn't adding something like http://drupal.org/project/simple_access to the mix should work. You might also have to add something like http://drupal.org/project/private to deal with the 'unpublished' state.