COmanage Developers List

[Scott Koranda <>]

> > On Tue, Nov 15, 2011 at 7:00 PM, Benn Oshrin 
> > <>
> >  wrote:
> > > 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)?
> > 
> > Scott was looking into how CakePHP would render a multiple checkbox field.
> > https://bugs.internet2.edu/jira/browse/CO-94?focusedCommentId=15986&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15986
> 
> Hi,
> 
> On this question of multiple check boxes.
> 
> Is there a preference or strong feeling on how the underlying
> data should be handled?
> 
> For the sake of discussion, suppose we want to add 'race'
> with possible values of 'purple', 'green', and 'blue' or any
> combination of them to the OrgIdentity class.

I should have used 'cm_demographics' as detailed at

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

for the example.

I see from that page that right now we are storing race as a
VARCHAR(5).

Marie, can you send me what you have for that model right
now? Also the to generate the table?

Thanks,

Scott

> 
> A user wants to select 'purple' and 'green'.
> 
> Do we want 
> 
> a) to store 'green purple' as a string in a 'race' row for
> OrgIdentity 
> 
> or
> 
> b) do we want a separate model/table with a many-to-many
> relationship between the OrgIdentity and the values 'purple'
> and 'green'.
> 
> I think in the past I argued for (a) but I think there is
> more CakePHP magic available for (b).
> 
> Before I dig deeper and code up test code for both I wanted
> to know if we had a preference or already ruled something
> out, or if I am missing another good possibility?
> 
> I had hoped we could use a database column of type SET and
> get CakePHP automagic, but I do not see that available so
> far.
> 
> Thanks,
> 
> Scott
> 
> 
> > 
> > >
> > >>> - 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).
> > 
> > Not currently supported by us or cake?
> > 
> > >
> > > -Benn-
> > >