COmanage Developers List

[Benn Oshrin <>]

On 11/15/11 8:53 PM, Marie Huynh wrote:
> > - edu_person_affiliation can be multi-valued, but data model doesn't allow 
> > this.
> > - org_people:edu_person_affiliation and co_people:e_p_a should probably 
> > become org_people:affiliation co_people:affiliation
>
> edu_person_affiliation is in cm_co_person_roles and cm_org_identities,
> both as varchar(32).  According to the link in the definition, the
> permissible values are:
>
> faculty, student, staff, alum, member, affiliate, employee, library-walk-in
>
> I propose we treat this in the same way as the multiple checkboxes for
> demographics(CO-94).

I forget, what did we say on that? Make the field VARCHAR(n)?

> > - affiliation field should be customizable
> How so?  During setup via enum?  As part of the enrollment config so
> it can be done via the UI?

Open for discussion. It could just become an Extended Attribute that 
gets tied to an Enum (not currently supported).

-Benn-