Proposed public statement (ala previous such in August and October) about what OSIdM4HE has been up to and where we're headed.
Summary
The work of the initiative continues, including technical analysis, organization and planning, and outreach. New participants have joined the discussion. The group is working hard to "make it real" by developing concrete proposals that can generate real resource commitments in 2012.
General
- The OSIdM4HE joint effort proposal was presented to the Kuali community at Kuali Days 2011 and was well attended and received. Several additional institutions expressed interest in contributing. To see notes of the meeting including responses to the IdM survey conducted in advance of the meeting refer to the following links. Kuali Days IdM BoF Presentation and Notes from Kuali Days IdM BoF
- While there was much interest in contributing to focused efforts, many mentioned they would need more of a concrete plan that they could "sell" to the appropriate decision makers at their institution in order to be able to participate in a material fashion. Work to create this plan is underway.
- The OSIdM4HE joint effort was discussed at the Kuali Rice Board meeting at Kuali Days and the board continues to express strong interest. They endorsed a recommendation to speed up our overall initiative by exploring potential consulting services to create an overall development plan with enough details so that interested parties can have confidence in formally contributing resources. The OSIdM4HE Strategy and Organization team is working to solicit consulting proposals and will present back to the Rice Board for consideration of seed funding.
- A face-to-face meeting will happen in early January to move forward on the elements needed for the development plan, including resource and scheduling estimates.
- UCB/UCSF engagement: The UC schools are doing joint work on IAM requirements to meet near-term needs. They are trying to align this work, and likely design resources in 2012, with the needs and goals of OSIdM4HE.
- Participation from people from Rutgers University, the University of Arizona, and the OpenRegistry project.
- better name still TBD ...
- ...
Subteams:
Strategy and Organization
- refined Team Charge
- proposed new deliverable of Development Investment Plan, possibly using consultant help, see SoW
- continued work on other top-level documents
Registries
- focus on matching component, likely development opportunity via UC as example/pilot
- participation from Rutgers / OpenRegistry, Arizona
- beginning of analysis and gap-fit of Penn State Central Person Registry against UCB/UCSF registry requirements
- discussion of and general agreement on API format standards using RESTful methods
Provisioning
- looking at both path from SoRs to Registries and from Registries to downstream systems
- looking at provisioning as an aspect of general-purpose enterprise data integration, and existing software packages/patterns that do this
Access Management
- gap analysis performed against requirements from Kuali community and Penn State, both KIM and Grouper matched up well
- importance of coordination on capabilities and APIs for (at least) the two useful systems
- access request/approval workflow as potential new functional area