COmanage Developers List

[Marie Huynh <>]

Oops, forgot to respond to the list.


---------- Forwarded message ----------
From: Marie Huynh 
<>
Date: Wed, Sep 7, 2011 at 2:45 PM
Subject: Re: [comanage-dev] Notes on CO-172
To: Benn Oshrin 
<>



>  [1] Update data model to add parent_cou_id column
>     - Update wiki

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

>     - Update schema.xml
snippet:

<table name="cous">
   <field name="id" type="I">
     <key />
     <autoincrement />
   </field>
   <field name="co_id" type="I">
     <notnull />
     <constraint>REFERENCES cm_cos(id)</constraint>
   </field>
   <field name="name" type="C" size="128" />
   <field name="description" type="C" size="128" />
   <field name="parent_cou_id" type="I">
     <constraint>REFERENCES cm_cous(id)</constraint>
   </field>
   <field name="created" type="T" />
   <field name="modified" type="T" />
   <index name="cous_i1">
     <col>co_id</col>
   </index>
   <index name="cous_i2">
     <col>name</col>
   </index>
   <index name="cous_i3">
     <col>co_id</col>
     <col>name</col>
     <unique />
   </index>
 </table>



>  [2] Update model (COU hasMany COU)

I'll come back to this after I read up on linking models.

>  [3] Update REST API documentation
>     - Update wiki schema definition to allow parent_cou_id attribute
>       in all appropriate operations

https://spaces.internet2.edu/display/COmanage/COU+Schema

Is this staying Version 1.0?

>     - Update error codes for scenarios described in [4], below

https://spaces.internet2.edu/display/COmanage/COU+API

There are two 403s.  Are we also filing these under 403?

Marie

>  [4] Update controller
>     - Add a write check that the parent cou is a member of the
>       same co as the target cou
>     - Add a delete check that a cou can't be deleted if it has
>       children
>  [5] Update web UI to allow Parent COU ID to be set as part of
>     editing a COU (probably via a drop-down)
>  [6] Update isAuthorized in all appropriate controllers (ie: anything
>     that currently allows authorization based on COU Admin status)
>     to properly account for child COUs in decision making. (This
>     probably just needs to be done in CalculateCMRoles.)
>
> -Benn-
>