Grouper Users - Open Discussion List

["Dr. Loris Bennett" <>]

Hi Chris,

Maybe I am missing something, but GRP-178 seems to be just about
include/exclude. I was thinking more along the lines of the following:

A group can be defined as the union of all the groups whose names match
a given pattern. So if I have 

        uni:computer_centre:sor
        uni:computer_centre:admin:sor
        uni:computer_centre:hpc:sor
        uni:computer_centre:identity_management:sor
        
I would then have

        uni:all defined by uni:%sor
        uni:computer_centre: all defined by uni:computer_centre:%sor

I have tried to do something similar with requireInGroups, e.g.

        grouperIncludeExclude.requireGroup.name.0 =
        testRequireInGroupAttribute
        grouperIncludeExclude.requireGroup.attributeOrType.0 = type
        grouperIncludeExclude.requireGroup.group.0 = sources:fub:%sor
        grouperIncludeExclude.requireGroup.description.0 = If value is
        true, members of the overall group must be in SAPHR (in the
        sources:fubb:%sor group).  Otherwise leave this value not filled
        in.

but the pattern functionality doesn't seem to be there.

Regards

Loris

On Mon, 2009-01-19 at 09:53 -0500, Chris Hyzer wrote:
> I believe everything requested is done in 1.4.  Please try it out and let 
> me know what you think.
> 
> https://bugs.internet2.edu/jira/browse/GRP-178
> 
> https://wiki.internet2.edu/confluence/display/GrouperWG/Include+exclude+and+require+groups
> 
> Note, due to the nature of include/exclude, custom types/attributes, and 
> how configurable it is, it is a bit complicated... feel free to edit this 
> wiki page or give any suggestions on how to make it easier to use 
> (including changes to documentation grouper.properties file).  Let me know 
> if you have questions/issues
> 
> Chris
> 
> 
> > -----Original Message-----
> > From: Loris Bennett 
> > [mailto:]
> > Sent: Monday, January 19, 2009 9:41 AM
> > To: Tom Barton
> > Cc: Chris Hyzer; Grouper Dev
> > Subject: Re: [grouper-dev] auto-creating "include" and "exclude" groups
> > based on group type hook
> >
> > Hi,
> >
> > Did the feature below make it into Jira? I'd would be interested on the
> > timeline for any implementation, so that I know whether to just wait or
> > come up with a workaround.
> >
> > Regards
> >
> > Loris
> >
> > On Fri, 2008-10-24 at 09:41 -0500, Tom Barton wrote:
> > > Loris Bennett wrote:
> > > > I mentioned the idea of having a "orgAll" and "orgRecursiveAll" to
> > > > distinguish between the group all the members associated with a
> > > > particular org unit and the group of members associated with a
> > > > particular org unit or one of its descendants.
> > > >
> > > > Could this also be realized in this context.
> > >
> > > Good point. In fact, U Chicago wrote a java util to create an org
> > > hierarchy in grouper from an SoR source with include, exclude, and
> > > rollup groups, exactly as you describe. So "+1" to your feature
> > request.
> > >
> > > 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