Topics for March 2012 Pasadena f2f

  1. (tick) Reconciliation workflow vs LIGO requirements (CO-186)
  2. (tick) Did we tag Registry v0.4? If not, when will we?
    1. (tick) What remaining tickets are blockers vs can waits?
  3. (tick) Demo of petitions controller
  4. (tick) Petition templates for common enrollment patterns (CO-273)
  5. (tick) 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.
  6. (tick) Mapping COmanage Registry v.5, v.6
  7. (tick) Sprint planning
  8. (tick) COmanage Directory v0.2
  9. (tick) Demo/presentation goals/plans for I2MM
    1. (tick) Review demo script - Postpone until a week before the member meeting
    2. (tick) What to announce to community list
  10. (tick) COmanage Demo 3 / demo.co.internet2.edu
  11. (tick) Vocabulary/Terminology
  12. (tick) GUI design
    1. (tick) Switching to div layouts from table layouts
  13. (tick) What goes in a URL? (See background, below)
  14. (tick) And, relatedly, CO-247 (CO selector - persistence of selected CO)
  15. (tick) Rationalization of the REST request and response structures
  16. (tick) CO-261 and strategy for fixing validation issues after CakePHP upgrade
  17. (tick) svn vs git, continued
  18. (tick) InCommon Silver out of the box support
  19. (tick) Grouper Integration (CO-268)
  20. (tick) When will the new enrollment code be committed? Not until after 0.4 is tagged
  21. (tick) Hooks for Notifications (CO-207) and Provisioning (CO-188, CO-55, CO-272)
  22. (tick) Enrollment Workflow REST API Revisions (CO-179)
    1. (tick) Authnz, Real time reconciliation, Notifications
  23. (tick) Design for "Manage My Identity" UI / Plug-ins (CO-184)
  24. (tick) 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.

  • No labels