Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Math in visualizer

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Math in visualizer

Chronological Thread 
  • From: Jeffrey Williams <>
  • To: "Redman, Chad" <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] Math in visualizer
  • Date: Thu, 27 Jun 2019 10:16:08 -0400

On Thu, Jun 27, 2019 at 9:21 AM Redman, Chad <> wrote:

Hmm, sounds like it would be useful to add a feature to show which members are actually excluded by the complement.

That sounds very Jira-worthy. 😊

And maybe another one to show which users are excluded because they aren't in the second factor of an intersect?

Do you envision the information being displayed in the composite or the factor objects?  On the one hand, putting it in the composite for the complement makes sense, but it'd be messy for the intersect.  Maybe display it in the factors e.g.

..._deny  2 users (excludes 1 in the composite)

..._intersct0, 4 members(excludes 2 in the composite)
..._intersct1, 6 memers (excludes 4 in the composite)

_intersect, 2 members



From: [mailto:] On Behalf Of Jeffrey Williams
Sent: Thursday, June 27, 2019 9:10 AM
To: Robert Bradley <>
Cc: Grouper-Users <>
Subject: Re: [grouper-users] Math in visualizer




| Maybe one of you deny’s are not in the allow’s?  So only one is
| subtracted?  Compare the subjectId of owner, and each factor to
| see for sure 😊

That was my guess as well, but Jason will have to comment on that
himself. :)


Correct me if I'm wrong, but I think the quickest way to find out is to change NextGenerationUsers' type of composite to an intersect(AND) and see how many members are both in allow and deny.  That will be your true operand to subtract from the NextGeneration_Users_allow.





Jeffrey Williams 

Identity Engineer
Identity & Access Services


Image removed by sender.

Jeffrey Williams 
Identity Engineer
Identity & Access Services

Archive powered by MHonArc 2.6.19.

Top of Page