COmanage Developers List

[Marie Huynh <>]

There's a sponsor_co_person_id in the table cm_co_petitions and also
in  cm_co_person_roles now:

https://spaces.internet2.edu/display/COmanage/cm_co_person_roles

Assuming the petitions tables aren't temporary, we can go back to
cm_co_petitions to find the original sponsor and to cm_co_person_roles
for continued enrollment.  COUs are specified in both tables so we can
have per-COU sponsors.

A thought: how does this interact with the nested COUs?  If COUs A and
B are children of COU C, what does a sponsorship to A imply about C?
Permissions shouldn't cross to siblings, but what of parents/children?

On Fri, Oct 28, 2011 at 3:21 PM, Marie Huynh 
<>
 wrote:
>> There may be two use cases here: sponsor to get enrolled and sponsor to 
>> stay
>> enrolled. Regardless of LIGO requirements, COmanage should probably support
>> both.
>
> Would that sponsor to stay enrolled be the same one that would keep
> you enrolled by default?  If not, how long before someone gets booted
> for not having a valid sponsor to stay in?
>
>>>> How many levels of sponsorship do we need?  I added a sponsor for
>>>> membership into a group in cm_co_group_members here:
>>>> https://spaces.internet2.edu/display/COmanage/cm_co_group_members
>
> Reverted so I don't forget to do it later.
>
>>>>
>>>> Is that level sufficient or will there ever be a need for sponsors
>>>> into the CO or CMP level?
>>
>> I think sponsor gets attached to co_person_role. Alternately, if there are
>> multiple sponsors per person (which I hope there aren't), we need a
>> co_sponsors table (but let's try not to go this route).
>
> Since people can join more than one COU, we will need sponsors for
> each.  If each row of co_person_role corresponds to one COU and one
> person, we can still add the sponsor to that and not need a
> co_sponsors table.
>
> Scott, do we need more than one sponsor?
>
> Marie
>
>>
>> I hadn't thought about sponsors as part of group memberships... I wonder if
>> CORE (COmanage REgistry) should do this or if we should rely on Grouper (or
>> the GMS) to worry about it. The CORE design for groups was always intended
>> to be pretty minimal. (Can Grouper track sponsors for group memberships? Is
>> there even a LIGO requirement around this?)
>>
>> -Benn-
>>
>