ITAG Status Report

1. David Walker Information & Educational Technology University of California, Davis DHWalker@ucdavis.edu ITAG Status Report

2. Surya Narayana, UC San Francisco Arlene Allen, UC Santa Barbara Lisa Gardner, UC Santa Cruz Greg Bell, Lawrence Berkeley National Lab Steve Hunter, UC Office of the President Pete Siegel, UC Davis (ITLC Liaison)‏ ITAG Membership • (To be determined), UC Berkeley • David Walker, UC Davis (co-chair)‏ • Marina Arseniev, UC Irvine (co-chair)‏ • Nick Reddingius, UC Los Angeles • Faust Gorham, UC Merced • Russ Harvey, UC Riverside • Emily Deere, UC San Diego (co-chair)‏

3. Kuali Rice Assessment • A definition of the scope of middleware for the purpose of this assessment, including at least the scope provided by Rice • A survey of needs for middleware at UC's locations • How Rice meets (or does not meet) those needs • Alternative solutions and whether they should be investigated further, either as alternatives to Rice, or for incorporation as components within the Rice framework • Opportunities for interoperation among UC locations that adopt Rice

4. Rice Assessment Activities • Campus middleware survey • Issue papers for each Rice component • Recommendations to the ITLC • Work materials are available under the Kuali Rice Assessment project on the ITAG wiki: https://spaces.ais.ucla.edu/display/ucitag/Home • Completion in February

5. Middleware Survey • Detailed results are available on the ITAG wiki. • https://spaces.ais.ucla.edu//x/iQA3AQ • Caveats • UCB and UCSF not reported. • Kuali applications section added later – UCB, UCR, UCSF, UCSB, and UCSC not reported.

6. Survey - Middleware Components

7. Survey – Middleware Suite

8. Survey – Kuali Applications

9. Significant Issues Identified • We need to consider UC's unique organizational structure, allowing appropriate campus options. • There will be a time dimension to our assessment, as Rice is still evolving. We will likely be sending recommendations back to the broader Kuali community. • We are addressing middleware technology that enables interoperation and sharing, when it makes business sense. We will not address business models (right now, anyway). • Sharing / federation of components and applications will be an interesting challenge.

10. Draft Report Outline • Context and background • Definition of middleware for this assessment • Issues related to UC's organizational structure • Needs for common middleware within UC • How Kuali Rice addresses those needs • Alternatives • Conclusions and recommendations

11. Work Plan for 2009 • Projects that address strategic issues like the Kuali Rice assessment • Projects that prepare the ITAG to address future strategic issues

12. Proposed ITAG Work Plan for 2009 • Assess Kuali Rice for use within UC. • Develop an initial statement of principles and standards for UC architecture. • Create a repository of UC standards, guidelines, etc. that foster interoperability, federation, and re-use of IT resources. This work will include the process for submission and approval of new and updated items for the repository, either from within ITAG or by other IT groups within UC. • Adopt existing standards where appropriate. • Create a clearinghouse for software and services that are available for sharing within UC. Maintenance might be moved to the ITLC's planned project management office at a later date, if that were deemed appropriate.

13. Potential Additions to the Work Plan • Establish browser standards for multi-campus applications. • Coordinate best practices for campus standards processes and repositories.