COmanage Developers List

[Benn Oshrin <>]

Sorry, forgot to cc the list.

-------- Original Message --------
Subject: Re: [comanage-dev] Re: (CO-89) Add sponsor to data model
Date: Tue, 15 Nov 2011 21:57:41 -0500
From: Benn Oshrin 
<>
To: Marie Huynh 
<>

I'm making some changes to this for CO-193, hopefully the merge works out :)

The actual implementation of any of these configurations is CO-182 (and
maybe CO-56).

-Benn-

On 11/15/11 5:48 PM, Marie Huynh wrote:
> Oh, I forgot this:
> https://spaces.internet2.edu/display/COmanage/cm_cmp_enrollment_configurations
>
> If that looks fine, I'll add it in before commiting co89.  We should
> discuss what effects checking the boxes off in the config should have.
>   Perhaps that should be a separate ticket so we can commit this one?
>
> On Mon, Nov 14, 2011 at 8:57 PM, Marie 
> Huynh<>
>   wrote:
> > Yes, they will be separate.
> >
> > On Mon, Nov 14, 2011 at 7:56 PM, Benn 
> > Oshrin<>
> >   wrote:
> > > I'll look at the diff tomorrow (hopefully), but just to be clear... you'll
> > > commit the changes separately for 89 from those for 94, right? (ie: not
> > > 89+partial94, then remainder94)
> > >
> > > On 11/14/11 9:27 PM, Marie Huynh wrote:
> > > > Some of the files modified for co89 also contain edits for 94.
> > > > Attached is the diff.  It there's no problem with the edits for 89,
> > > > I'll commit those.
> > > >
> > > > Scott, have you had a chance to take a look at the multiple checkboxes for
> > > > 94?
> > > >
> > > > --- Changelist 'co89':
> > > > M       trunk/app/models/co_person_role.php
> > > > M       trunk/app/models/co_person.php
> > > > M       trunk/app/config/schema/schema.xml
> > > > M       trunk/app/controllers/co_person_roles_controller.php
> > > > M       trunk/app/controllers/co_people_controller.php
> > > > M       trunk/app/libs/lang.php
> > > > M       trunk/app/views/co_person_roles/fields.inc
> > > > M       trunk/app/views/co_people/fields.inc
> > > >
> > > > --- Changelist 'co94':
> > > > A       trunk/app/models/demographic.php
> > > > M       trunk/app/controllers/pages_controller.php
> > > > A       trunk/app/controllers/demographics_controller.php
> > > > M       trunk/app/libs/enum.php
> > > > M       trunk/app/views/pages/menu.ctp
> > > > A       trunk/app/views/demographics/view.ctp
> > > > A       trunk/app/views/demographics/edit.ctp
> > > > A       trunk/app/views/demographics/index.ctp
> > > > A       trunk/app/views/demographics/add.ctp
> > > > A       trunk/app/views/demographics/fields.inc
> > > >
> > > > Marie
> > > > On Fri, Nov 11, 2011 at 8:46 PM, Scott 
> > > > Koranda<>
> > > >     wrote:
> > > > > Hi,
> > > > >
> > > > > > Where is the honorific for names displayed?  It's not in the title of
> > > > > > the page /co_people/edit.  What are the odds that it will make a
> > > > > > difference if it's not displayed for the dropdown for sponsor if we
> > > > > > display first, middle, family, and suffix?
> > > > >
> > > > > I think we should display it if available (I don't think it is
> > > > > a required field).
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Scott
> > > > >
> > > > > > On Sat, Nov 5, 2011 at 2:07 PM, Benn 
> > > > > > Oshrin<>
> > > > > >     wrote:
> > > > > > > On 11/2/11 10:15 PM, Marie Huynh wrote:
> > > > > > > > Assuming the petitions tables aren't temporary, we can go back to
> > > > > > > > cm_co_petitions to find the original sponsor and to cm_co_person_roles
> > > > > > > > for continued enrollment.  COUs are specified in both tables so we can
> > > > > > > > have per-COU sponsors.
> > > > > > >
> > > > > > > I don't think the petitions will be temporary.
> > > > > > >
> > > > > > > > A thought: how does this interact with the nested COUs?  If COUs A and
> > > > > > > > B are children of COU C, what does a sponsorship to A imply about C?
> > > > > > > > Permissions shouldn't cross to siblings, but what of parents/children?
> > > > > > >
> > > > > > > I don't think it does, but perhaps Scott will suggest otherwise.
> > > > > > >
> > > > > > > -Benn-