Grouper Users - Open Discussion List

["Dr. Loris Bennett" <>]

Hi Richard and everyone else,

Here are some details about how I have gone about things ...

1. I have written a client which reads the org structure out of our HR
database
   and creates a folder for each unit in the hiearchy. Additionally it
fills a
   table I have added to the Grouper database which just constains
subject ID
   and the name of the groups that the subject belongs to, e.g.

       ncl:cs:auto                 123456
       ncl:cs:iss:auto             123457
       ncl:cs:iss:middleware:auto  123458
       ncl:cs:iss:middleware:auto  123459
       ncl:cs:iss:middleware:auto  123460

   (I call my SOR groups 'auto')

2. I then set up a grouper loader group at the top of my hierarchy to
create these groups
   automatically by setting the following attributes

      grouperLoaderQuery: select group_name, subject_id from
my_auto_groups

      grouperLoaderGroupQuery: select name as group_name, display_name
      as group_display_name, description as group_description from
      grouper_groups_v

   The first query determines the members of the groups. The second
   sets the display name for the group, but will only work if the
   groups have already been created with the corresponding display
   name information (my client does this).

3. To create the 'all' groups is set up another loader group and set
grouperLoaderQuery to

      select gs.name || ':all' as group_name, ggv.group_id as
      subject_id, ggv.group_name as sub_group_name from grouper_stems
      gs, grouper_groups_v ggv where gs.name like
      'my:toplevel:stem:%' and ggv.group_name like gs.name || '%auto'
      and exists (select 1 from grouper_stems gs2 where gs2.name like
      gs.name|| ':%')

   where 'my:toplevel:stem' could be just 'ncl'. In my case is something
like

      sources:source1

   The display name can be set as in step 3 (I still need to tweak my
client to do this).

4. To get the groups filled you have to run the loader like this:

      bin/gsh.sh -loader

I would be interested if anyone has any comments on this approach.

Cheers

Loris

On Thu, 2009-03-05 at 10:19 -0500, 

 wrote:
> Hi Loris, 
> 
> The structure you have suggested looks like it could be a very effective 
> solution to what I am aiming for. Having the all-groups and the sor-groups 
> will allow for better control on the members being assigned to certain 
> groups, especially as the University departmental structure does go quite 
> deep!
> 
> Any input or advice on using the grouperLoader custom types would be 
> greatly appreciated, I've only been using Grouper for a few weeks so it's 
> been quite a quick learning curve at the moment. If you are able to provide 
> any snippets of a working sample to get me started would be a great help.
> 
> Many thanks for taking the time to respond to me in so much detail,
> 
> Richard
> 
-- 
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