Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Designing Groups

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Designing Groups

Chronological Thread 
  • From: "Bryan E. Wooten" <>
  • To: Chris Hyzer <>, David Langenberg <>
  • Cc: "" <>
  • Subject: RE: [grouper-users] Designing Groups
  • Date: Wed, 12 Feb 2014 15:15:38 +0000
  • Accept-language: en-US

I think I get it.


Instead of have the SQL return all course sections and their students or instructors have the sql just return all the course sections and two rows as subjectID. These being “students” and “instruction” since we know that each section has groups by these names. These groups then become the members of the ‘all’ group.


I also need to change the subject source in the Loader query to ‘GSA’ since that is where subjectID lives (ie the group students or instructors)?


I think I am getting this right?




From: Chris Hyzer [mailto:]
Sent: Tuesday, February 11, 2014 1:23 PM
To: David Langenberg; Bryan E. Wooten
Subject: RE: [grouper-users] Designing Groups



I would not make a duplicate group that has all the members of students and instructors.

I think you can do what dave is saying, though it should be a loader job, so it will change dynamically as the groups are added/deleted (with “like” string).


So you can create a query against peoplesoft that returns group_name (the overall group), and subject_identifier (the group name of the member which is the students group or instructors group).  So basically this will return twice the number of rows as courses that you have.  If you have a dblink and can join to the grouper groups table and get the uuid of the group in a subject_id col that would be quicker, though it is not a requirement.








From: [] On Behalf Of David Langenberg
Sent: Tuesday, February 11, 2014 1:01 PM
To: Bryan E. Wooten
Subject: Re: [grouper-users] Designing Groups


Use GSH to create a :all group with the :students and :instructors groups as members?




On Tue, Feb 11, 2014 at 10:51 AM, Bryan E. Wooten <> wrote:

I’ve run into a mental block in designing my groups.


I have created 2 Grouper Loader jobs using SQL_GROUP_LIST. One creates groups for each course section with students as members. The other creates groups for each course section with instructors as members. Both run SQL against our PeopleSoft SIS.


I need a group for each course section that includes both instructors and students. I see 2 ways to accomplish this, one I know I can make work.


The easiest thing to do would be create a third  SQL_GROUP_LIST using SQL that returns both instructors and students in one query.


But I was wondering if I might be better of creating  Grouper Loader job that executes a query against the Grouper DB (GSA) the returns the members of the groups I created above.


I didn’t see any way to leverage composite groups to achieve my goal. And I didn’t see a way to leverage include groups either.


Any thoughts or opinions invited.




David Langenberg

Identity & Access Management

The University of Chicago

Archive powered by MHonArc 2.6.16.

Top of Page