Lois Brooks Stanford University 25 January 2005 A Higher Education Initiative

“The University of Michigan, Indiana University, MIT, Stanford, and the uPortal consortium are joining forces to integrate and synchronize their considerable educational software into a pre-integrated collection of open source tools.”

Converging Trends…why now… Institutional Partnering Data Standards Foundation $$ Investments Architecture Standards Institutional Mobilization Community Source Applications

Sakai is: A collaborative development effort A standards-based architecture A community “Best of Breed” software, synchronized development ~60 partner schools Emerging relationships with related efforts Tool Portability Profile provides a roadmap for other developers

The Tool Portability Profile: a roadmap for writing portable software A Pooled intellectual property…best of a portal, course and research collaboration tools, quizzing and assessment…modular and pre-integrated Synchronized adoptions at Michigan, Indiana, MIT, Stanford with open-open licensing Sakai Products

Commitments 5+ developers per institution under project leadership $4.4M in institutional staff (27 FTE) $2.4M Mellon Funding Additional investment through partners Sakai Project Core Universities

How is it working? After one year: Best ideas emerging Community is growing and changing rapidly: Berkeley and Foothill have joined core group, 60+ partners Software is shipping Synchronization of dependencies across six programming teams is challenging

Sakai Partners by Country

SEPP Objectives (1of 3) The objectives of the Educational Partner’s Program are to: actively develop a large, self-sustaining community of institutions that share the Sakai Project’s open source vision carry on a discussion of strategic directions for the Sakai Project as it emerges and evolves, provide a Sakai Project roadmap describing the timing and features for Sakai software releases,

SEPP Objectives (2 of 3) provide in depth developer and adopter training, develop a leveraged support infrastructure of a common (or locally implemented) knowledgebase, and helpdesk mobilize distributed resources for development and support of Sakai tools, provide a marketplace for the sharing and exchange of Sakai-based tools/components, facilitate purposeful interaction with the Sakai Core development team,

SEPP Objectives (3 of 3) coordinate activities with other organizations, such as, IMS or country-level agencies, build on the experiences of the JA-SIG, CHEF, and OKI training and conferences, facilitate Sakai community sharing of best practices in development, implementation, and support.

Why Sakai at Stanford? Economics Innovation and shared expertise Pedagogically rich experience for our community Integration of applications, functions and infrastructure

Integration With SIS With Libraries With portfolios With authorization/authentication structures

Bringing it all together Infrastructure networks and systems persistent access to content personal and institutional services intra-institutional identification enterprise system data Libraries owned and licensed content programs to gather, publish and preserve curatorial and interpretive services Teaching and Learning course management systems collaboration venues and tools content and metadata mgmt personal and group identities world-wide academic community formal / informal relationships institutional partnerships shared access to massive content stores