Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] auto-creating "include" and "exclude" groups based on group type hook

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] auto-creating "include" and "exclude" groups based on group type hook

Chronological Thread 
  • From: Tom Barton <>
  • To: Chris Hyzer <>
  • Cc: Loris Bennett <>, Grouper Dev <>
  • Subject: Re: [grouper-dev] auto-creating "include" and "exclude" groups based on group type hook
  • Date: Wed, 22 Oct 2008 08:50:44 -0500

I think that 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:

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…

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



fn:Tom Barton
org:University of Chicago;Networking Services & Information Technologies
title:Sr. Director for Integration
tel;work:+1 773 834 1700

Archive powered by MHonArc 2.6.16.

Top of Page