COmanage Developers List

[Benn Oshrin <>]

On 4/12/12 8:11 AM, Scott Koranda wrote:

> I propose that I do the following:
>
> - use the co_person_id to find all org_identity_id via the
>    co_org_identity_links table that the CoPerson might have
>
> - use the org_identity_id to find all identifiers associated
>    with the org_identity_id
>
> - also use the co_person_id to find all identifiers that might
>    be associated with CoPerson directly

I think we may need to discuss this further. My initial reaction is that 
org identity data shouldn't be exported by the registry, but I may not 
be understanding Grouper's needs and how we should be modeling this data.

> - make sure the list of identifiers does not contain
>    duplicates, and then add those identifiers to the
>    represenative Grouper group (and attach the co_group_id,
>    co_person_id, member, and owner attributes to each of those
>    memberships)

There are currently no uniqueness constraints in the datamodel for 
identifier, although I vaguely remember that some controller somewhere 
may enforce some constraint. Even then, it's possible for two different 
people to have the same identifier -- but of different identifier type 
-- so you may want to consider that as well.

-Benn-