Topics for March 2012 Pasadena f2f
- Reconciliation workflow vs LIGO requirements (CO-186)
- Did we tag Registry v0.4? If not, when will we?
- What remaining tickets are blockers vs can waits?
- Demo of petitions controller
- Petition templates for common enrollment patterns (CO-273)
- Is adding an additional role just another petition? If so, how does it vary from the current model (if at all)? No, for now it's just adding another role.
- Mapping COmanage Registry v.5, v.6
- Sprint planning
- COmanage Directory v0.2
- Demo/presentation goals/plans for I2MM
- Review demo script - Postpone until a week before the member meeting
- What to announce to community list
- COmanage Demo 3 / demo.co.internet2.edu
- Vocabulary/Terminology
- GUI design
- Switching to div layouts from table layouts
- What goes in a URL? (See background, below)
- And, relatedly, CO-247 (CO selector - persistence of selected CO)
- Rationalization of the REST request and response structures
- CO-261 and strategy for fixing validation issues after CakePHP upgrade
- svn vs git, continued
- InCommon Silver out of the box support
- Grouper Integration (CO-268)
- When will the new enrollment code be committed? Not until after 0.4 is tagged
- Hooks for Notifications (CO-207) and Provisioning (CO-188, CO-55, CO-272)
- Enrollment Workflow REST API Revisions (CO-179)
- Authnz, Real time reconciliation, Notifications
- Design for "Manage My Identity" UI / Plug-ins (CO-184)
- Deprovisioning statuses and flows
What goes in a URL?
COmanage Registry is a bit inconsistent as to when things are attached to URLs and when they aren't. We should come up with a standard. eg:
/registry/co_people/index/co:2 GET /registry/co_people.json?coid=2 /registry/co_group_members/select/cogroup:9/co:2 GET /registry/co_group_members.json?cogroupid=9 /registry/co_nsf_demographics/add/co:2/co_person_id:21
Furthermore, these parameters are generally lost when a form errors out (on add or edit), and there is usually some code in fields.inc that needs to regenerate them.