Grouper Developers Forum

[Jim Fox <>]

Just curious, do you have use for this complexity?  We get by pretty well 
with one group per course, with members (students plus instructors) and 
instructors (just the instructors).  This is in the grouper registry, and 
translates directly to ldap.  All our course information come from 
institutional data, so we have no admins of any sort for courses.

Jim

On Sep 28, 2010, at 7:57 PM, Peter DiCamillo wrote:

> I noticed that Tom put this on the agenda for Wednesday's call, so I 
> want to describe in more detail what we would like to able to do.  It's 
> more complex then just setting an ACL for all the groups under a stem.
> 
> The names we have for course groups are, for example, 
> COURSE:CSCI:1230:2010-Fall:S01:id, and for each of those we have 12 
> groups in a tree structure of indirect memberships like this:
> 
> id:
> 
> All
>   Administrator
>     Instructor
>     Manager
>     TeachingAssistant
>   Contributor
>     ContentDeveloper
>     Mentor
>   Learner
>     Auditor
>     Student
>     Vagabond
> 
> The leaf groups (Instructor, Manager, etc) with people as members are 
> the ones which may need to be modified by staff.  The other groups 
> should not be modified, but need an ACL to allow staff to view the 
> membership.  So for a rules-based solution, we would want to be able to 
> grant a privilege to all the groups under the COURSE stem which have 
> certain IDs, and specify a different privilege for groups under the 
> COURSE stem with other IDs.  I'm not very concerned about the time 
> needed to delete 475K group membership if I know we'll be able to 
> upgrade to a rules-based solution that meets our needs.
> 
> Peter
>