Grouper Users - Open Discussion List

[Loris Bennett <>]

On Mon, 2009-03-16 at 16:05 +0000, Richard James wrote:
> I would also express my interest in this feature. We now have a
>  hierarchy set up within Grouper for the University, the way we have
>  done it is by having a folder for each school/faculty, then within
>  this folder have an individual group for each of the departments
>  within the school, so for ISS it's similar to the below;
> 
> 
> Newcastle University (Parent Stem)
> >>>>>Central Services (Stem)
> >>>>>>>>>>ISS (Stem)
> >>>>>>>>>>>>>ISS All (Group, using grouperLoader)
> >>>>>>>>>>>>>Middleware Team (Group)
> >>>>>>>>>>>>>Unix Network Team (Group)
> >>>>>>>>>>>>>Information Delivery Team (Group)

Just my 2 eurocents on this set up: You might find certain things easier
if you make "Middleware", "Unix Network Team" and "Information Delivery
Teams" stems rather than groups. You can then define a group within each
folder like "sor" to contain the people in that org unit. The advantage
of this is that when you come to make roll-up groups with grouperloader
for "all" groups (i.e. a group containing everyone in a given org unit
and all its children), the SQL will be much simpler and quite generic
since you will be able to refer to all the groups in the same way, e.g.
"%:sor".

I found it helpful to make a clear distinction between the org
structure, which I represent purely with folders, and groups, which I
use to differentiate between different types people within the org unit.
This approach also corresponds well when you have an automatically
generated group plus black- and whitelists (see include/exclude groups
for more on this).

Cheers

Loris

> The initial set up of this was quite painful at times, so I think as
>  Loris has suggested, if you were able to give a table of the org_id
>  and parent_org_id to create the initial hierarchy of folders it would
>  be a very useful feature.
> 
> Regards
> 
> Richard
> 
> 
> >-----Original Message-----
> >From: Tom Barton 
> >[mailto:]
> >Sent: 16 March 2009 15:36
> >To: Chris Hyzer
> >Cc: 
> >;
> > Richard James; Grouper Users Mailing
> >List
> >Subject: Re: [grouper-users] Stems and Group Members
> >
> >Chris Hyzer wrote:
> >>> Isn't it that case that "grouperLoaderQuery" actually creates
> >multiple
> >>> groups, whereas "grouperLoaderGroupQuery" just allows the display
> >name
> >>> to be set?
> >>
> >> Ah yes, you are right.
> >>
> >>> At first reading I thought I should also try something like that,
> >since
> >>> being able to use a single select like that is quite elegant.
> >However,
> >>> I am also keen to keep the hierarchy, rather than having all the
> >groups
> >>> in one folder.
> >>>
> >>> Chris, would it be feasible to tweak Grouper so that it can make an
> >org
> >>> structure pop into existence as a hierarchy of folders, given a table
> >>> containing org_id and parent_org_id information? Looks like it might
> >be
> >>> a useful feature for Penn ;-)
> >>>
> >>
> >> We could consider that at some point...  so you would want an org to
> >> be a folder and a group inside right?  And if an org has a parent,
> >> put it in its folder...  hmmm
> >
> >+1 on that feature request. A "bushy" form in addition to the "flat"
> >form. Sometimes you want one, sometimes the other.
> >
> >Also, an org folder might contain two groups: the people at that node in
> >the org hierarchy, and a rollup group of all people at a subordinate
> >node in the hierarchy. That one probably just consists of subgroups, no
> >direct non-group Subjects.
> >
> >Tom
-- 
Dr. Loris Bennett (Mr.)
Freie Universität Berlin
ZEDAT - Zentraleinrichtung für Datenverarbeitung / Computer Center
Compute & Media Service
Fabeckstr. 32, Room 221
D-14195 Berlin
Tel ++49 30 838 51024
Fax ++49 30 838 56721
Email 

Web www.zedat.fu-berlin.de