COmanage Developers List

[Benn Oshrin <>]

Not quite.

CO Person attributes are those that are intrinsic to the person (eg: my 
name), while CO Person Role attributes are those that are intrinsic to 
the role (eg: my title for my job).

-Benn-

On 10/18/11 12:12 PM, Warren Anderson wrote:
> Just to clarify, CO Person attributes are things that are single-valued 
> attributes of a CO person, and CO Person Role attributes are things that 
> allow multi-values?
>
> Warren
>
> On Oct 17, 2011, at 16:53 , Benn Oshrin wrote:
>
> > 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).
> >
> > - CO Person Role attributes are collected via form... these include
> >   telephone numbers and extended attributes. 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)
> >
> > Thoughts?
> >
> > -Benn-