COmanage Developers List

[Scott Koranda <>]

Hi,

> Broadly, there are three types of attributes we might be interested
> in collecting: Organizational, CO Person, and CO Person Role. Here's
> how I think we want to handle them during the enrollment/petition
> process:
> 
> - Org attributes are collect as configured by the CMP (ideally via
>   SAML or LDAP, but in practice via form for now).

Understood.

> 
> - CO Person Role attributes are collected via form... these include
>   telephone numbers and extended attributes. 

Consider an attribute like telephone number. A person my have
an Org attribute called telephone number and may also have a
CO Person Role attribute called telephone number.

We might want a known value for one, say Org attribute
telephone number, to be the default for the other.

Or we may not.

Should it be configurable as part of the enrollment flow
whether or not an Org attribute "flows down"?

>   Each enrollment petition
>   generates a new CO Person Role.
> 
> - CO Person attributes are treated as follows:
>   - Populate once: eg previous LIGO ID
>   - Populate once but allow change: eg preferred or author name
>   - Do not populate via form: eg: LIGO ID, @ligo.org email address
>     (these would get populated by some other process later)

Understood.

Thanks,

Scott

> 
> Thoughts?
> 
> -Benn-