Subject: Grouper Developers Forum
- From: Peter DiCamillo <>
- To: Grouper Dev <>
- Subject: [grouper-dev] Brown's course group use case
- Date: Tue, 28 Sep 2010 22:57:27 -0400
- Authentication-results: cox.net; none
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:
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.
- [grouper-dev] Brown's course group use case, Peter DiCamillo, 09/28/2010
Archive powered by MHonArc 2.6.16.