Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] automagically creating group from stem node

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] automagically creating group from stem node

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Nathan Weyenberg <>
  • Cc: "" <>
  • Subject: RE: [grouper-users] automagically creating group from stem node
  • Date: Mon, 22 Oct 2012 15:32:07 +0000
  • Accept-language: en-US

Do you have a database table which has your org chart relationships in it?  If so, send me the rows for the groups you want an example for, and I will send you an example.





From: Nathan Weyenberg [mailto:]
Sent: Monday, October 22, 2012 11:30 AM
To: Chris Hyzer
Subject: Re: [grouper-users] automagically creating group from stem node


Hi Chris,


Here at the University of Wisconsin we have tried to implement Organization Hierarchies using the grouper loader, using the example you linked as a model. While we have been able to implement the proof of concept using the configurable items, we were not able to successfully modify the example to have it do what we want. Could you provide a very simple example in the documentation? 


What I am looking for is stem:grpA to be a group that contains stem:sub_stem:grpA1 and stem:sub_stem:grpA2 groups as members all loaded via the grouper loader. 






On Oct 21, 2012, at 7:42 PM, Chris Hyzer wrote:

Ok, got it.  Penn does this for orgs.  Maybe this will help you with an example:

I believe we have one query as you have which has the people in the leaf nodes, then we have another query which link up all containers into one another...  that query is best performing if it can use the col as the subject_id to put in the group.  I think we have a DB link from our warehouse to your grouper database to make this happen (make sure the join happens on the correct side of the db link (e.g. with oracle hint) or you will be sending many rows across the link instead of a few).  Otherwise you can use the group name which might be fine since the number of groups in groups is a lot less than the number of people in groups.


-----Original Message-----
From: Jon Gorrono []
Sent: Sunday, October 21, 2012 8:00 PM
To: Chris Hyzer
Subject: Re: [grouper-users] automagically creating group from stem node

ok, I was trying to pack as much into the smallest question possible I guess :)

The simple view I have returns something like:

group_name, subject_id, subject_source_id
'cms:course:section:AHI:001B:A01:200501', '0003482', 'ss_cms'
'cms:course:section:AHI:001B:A02:200501', '0008892', 'ss_cms'

So this creates a group '200501' nested in the folder structure
'cms:course:section:AHI:001B:A01' with the member with subject_id

...and a group '200501' nested in the folder structure
'cms:course:section:AHI:001B:A02' with the member with subject_id

Logically this folder structure could be construed to indicate that
the folder 'cms:course:section:AHI' contains both '0003482' and
'0008892' as indirect members... I can see that you might not want
that to be true as a general steadfast rule, but I thought that there
might be a way get folders to inherit subfolder memberships with out a
specific assignment buy the loader.

So you're saying that in order to do that I should have another row in
the result (or a different query) to accomplish that? ... a query row
that ties both id's with the shorter stem?

On Sat, Oct 20, 2012 at 5:30 AM, Chris Hyzer <> wrote:

I dont know exactly what you are asking, but I think the answer is yes :)


Your query results can be groups as members... you could have multiple queries running after one another to cascade correctly.  We do this at Penn.   If you want to give a more detailed example I could explain a little better





From: [] on behalf of Jon Gorrono []

Sent: Friday, October 19, 2012 6:15 PM


Subject: [grouper-users] automagically creating group from stem node


I probably have all the terminology wrong here but...


my question, put right up front, is .... when provisioning a bunch of

stems+groups and members(hips) with the loader is there a way to make

the stem-nodes (folders?) be groups with indirect members made from

the groups' members below that node in the (folder/group/stem)







That returns a nice json list of members of a leaf node which is a

group defined via the loader job as


(that is Section A01 of the Courseoffering AHI 001B for the first term of 2005)


But I assumed that the intermediate folders would also be addressable

and members(hips) inherited, maybe by throwing some switch somewhere


So logically 'cms:course:section:AHI:001B' might contain all the

members of all the sections in all a terms for AHI 001B ... instead

this returns a groupNotFound... the intermediate 'folder' doesn't seem

to be addressable:




(actually expected 'members' to return 0 and 'memberships' to return a

sum of the groups below as indirect members)









Jon Gorrono

PGP Key: 0x5434509D -



Jon Gorrono
PGP Key: 0x5434509D -


Nathan Weyenberg

UW-Madison DoIT - Middleware


Archive powered by MHonArc 2.6.16.

Top of Page