Grouper Users - Open Discussion List

[Jon Gorrono <>]

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
'0003482'

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


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
>
> thanks,
> Chris
> ________________________________________
> From: 
> 
>  
> []
>  on behalf of Jon Gorrono 
> []
> Sent: Friday, October 19, 2012 6:15 PM
> To: 
> 
> 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)
> hierarchy?
>
> example:
>
> http://server/grouper-ws/servicesRest/json/v2_1_001/groups/cms%3Acourse%3Asection%3AAHI%3A001B%3AA01%3A200501/members
>
> That returns a nice json list of members of a leaf node which is a
> group defined via the loader job as
> 'cms:course:section:AHI:001B:A01:200501'
> (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:
>
> http://server/grouper-ws/servicesRest/json/v2_1_001/groups/cms%3Acourse%3Asection%3AAHI%3A001B/members
>
> (actually expected 'members' to return 0 and 'memberships' to return a
> sum of the groups below as indirect members)
>
> Regards,
> Jp
>
> ...
>
>
> --
> Jon Gorrono
> PGP Key: 0x5434509D -
> http{pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
> http{middleware.ucdavis.edu}



-- 
Jon Gorrono
PGP Key: 0x5434509D -
http{pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
http{middleware.ucdavis.edu}