Grouper Developers Forum

[Chris Hyzer <>]

If it is only the naming people want to customize, then we can make config 
params for it easily...  I think this will end up being a relatively simple 
hook, and if people want to customize the logic, they can get the source, 
change it, install as new hook, and use that one... and I will help them of 
course.

I agree with your way of naming / organizing, it is just a little complicated 
for the loader (since in that case, it focuses around the system of record 
group, but in the UI, it focuses around the overall group).  How about if a 
group is marked as "grouperIncludeExclude", the following occurs:

If the group name ends in _systemOfRecord [this might be only applicable for 
loader... kind of obscure], e.g. org123_systemOfRecord, then the following 
groups are created if they don't already exist:

a. create group of org123_include
b. create group of org123_sorAndIncludes (have two members: 
org123_systemOfRecord, and org123_include)
c. create group of org123_exclude
d. create group of org123 (composite of sorAndIncludes minus org123_exclude)

If the group name does not end in _systemOfRecord, e.g. org123, then the 
following groups are created if they don't already exist:

a. create group of org123_include
b. create group of org123_systemOfRecord
c. create group of org123_sorAndIncludes (have two members: org123, and 
org123_include)
d. create group of org123_exclude
e. change the group org123 to be a composite of sorAndIncludes minus 
org123_exclude

Thanks!
Chris


> -----Original Message-----
> From: Tom Barton 
> [mailto:]
> Sent: Wednesday, October 22, 2008 9:51 AM
> To: Chris Hyzer
> Cc: Loris Bennett; Grouper Dev
> Subject: Re: [grouper-dev] auto-creating "include" and "exclude" groups
> based on group type hook
>
> I think that https://bugs.internet2.edu/jira/browse/GRP-151 would
> create the proper set of groups, but I have two questions.
>
> In addition to removing the manual steps to create the necessary
> include and exclude groups, it may be that sites will only wish to
> provision the resultant _overall group. Should the other _ groups be
> marked with an attribute that can be used to deselect them for
> provisioning (or perhaps it should be the other way around)?
>
> Will the substrings following the _ be configurable? Eg, in your
> example with org21, perhaps we'd rather see the resulting included and
> excluded group be named org21, and would choose to apply suffixes along
> these
> lines: org21_from_sor (ie, as determined from its System of Record),
> org21_include, org21_sorandinclude, and org21_exclude.
>
> Chris Hyzer wrote:
> > Hey,
> >
> >
> >
> > Loris and I were discussing this enhancement which would be
> especially
> > useful to how Loris and I will the loader, but will also be valuable
> > for manually created groups as well...
> >
> >
> >
> > https://bugs.internet2.edu/jira/browse/GRP-178
> >
> >
> >
> > I think if this is a decent generic implementation, then it will not
> > be customizable, and you can take the hook source code for this, and
> > duplicate or subclass, and put your own customizations in there.
> This
> > is probably better than making this hook customizable... since there
> > probably wont be much code there anyways.
> >
> >
> >
> > Still need to make sure it is all feasible...
> >
> >
> >
> > Thoughts?  Let me know sooner than later... J
> >
> >
> >
> > Thanks,
> >
> > Chris
> >