COmanage Developers List

[Benn Oshrin <>]

Primarily for Scott...

You added a comment to CO-760: "The LIGO use cases would prefer that the 
NSF demographics link is configurable at the COU level."

The problem with this is that NSF Demographics attach to the CO Person, 
not a Person Role (which is where the COU is significant), so doing this 
would be inconsistent.

As an example, imagine COU-1 and COU-2, where COU-1 wants NSF 
demographics and COU-2 does not.

 Person 1 = COU-1 = Enabled
 Person 2 = COU-1+COU-2 = Enabled
 Person 3 = COU-2 = Disabled

From the perspective of COU-2, Person 2 and Person 3 have different 
behaviors, which will lead to confusion. That is, if I am viewing the CO 
Person record for Person 2, do I render the link or not? That view does 
not vary according to COU (there's no concept of "current COU"), so we'd 
have to render the link. So even though COU-2 wants it disabled, in some 
cases it won't be.

Our options here are to make it configurable at the CO level, or 
refactor NSF demographics to attach to a Role instead of a Person, which 
doesn't really make sense to me either. (Why would you have a different 
ethnicity depending on your role?)

Thoughts?

Thanks,

-Benn-