sakai 3 at csu

19
Sakai 3 at CSU Matt Morton-Allen - L&T Liaison Enterprise Architecture and Liaison Division of Information Technology

Post on 22-Oct-2014

1.065 views

Category:

Education


1 download

DESCRIPTION

Sakai 3 at CSU Matt Morton-Allen, Charles Sturt University

TRANSCRIPT

Page 1: Sakai 3 at CSU

Sakai 3 at CSU

Matt Morton-Allen - L&T LiaisonEnterprise Architecture and Liaison

Division of Information Technology

Page 2: Sakai 3 at CSU

Agenda

• Historical overview

• Sakai 3 and CSU Interact– Why?– What?– How?

Page 3: Sakai 3 at CSU

1. Historical Overview

Page 4: Sakai 3 at CSU

CSU Interact Timeline

Page 5: Sakai 3 at CSU

CSU Interact Vision

• Consistent and integrated

• Scalable

• Flexible

• Reliable

• Agile

Page 6: Sakai 3 at CSU

Release Timelines

Page 7: Sakai 3 at CSU

Discussions• Nov 2008 - AuSakai @ Monash• Dec 2008 - Internal discussions with Sponsor et al• Mar 2009 - OLE Steering Committee approved initiative• Apr 2009 - ILSCOSC endorsed initiative• May 2009 - ILSC endorsed initiative• May 2009 - Sakai 3 IHP proposal lodged• Jul 2009 - T&S closed off• Jul 2009 - Boston Sakai conference• Aug 2009 - Sakai 3 Impact Assessment completed• Sep 2009 - SEC approval of initiative and funding

Page 8: Sakai 3 at CSU

2. Sakai 3 and Interact

Why?

Page 9: Sakai 3 at CSU

Why?

• Ease of use

• Improved scalability

• Reduced development costs

• Architectural alignment

• Interoperability

• Vast improvement in user functionality!

Page 10: Sakai 3 at CSU

2. Sakai 3 and CSU Interact

What?

Page 11: Sakai 3 at CSU
Page 12: Sakai 3 at CSU
Page 13: Sakai 3 at CSU

Previously Identified Needs

• Course sites

• Subject Entry Point

• Contact Tool

• Sub-sites

• Restricted joinable sites

• Full site merging

Page 14: Sakai 3 at CSU

New Opportunities

• Sakai based tools for:– online assignment submission (i.e. EASTS)– Gradebook?– Forums software?

• Seamless DOMS integration?• Public facing pages?• Integration with Web 2.0 services?• Improved collaboration with external people?

Page 15: Sakai 3 at CSU

2. Sakai 3 and CSU Interact

How?

Page 16: Sakai 3 at CSU

How?

• Multi-pronged approach:

1. Sakai 3 “Preparatory Work”

2. Sakai 3 “Implementation project”

Page 17: Sakai 3 at CSU

Sakai 3 – Preparatory Work

• Paul Bristow – CSU Applications Architect– 2 days week– Focus on CSU specific technologies:

• Integration with CSU middleware• Linkages to CSU authentication

• Ian Boston – CARET CTO– 1 day / week– Integration of CSU needs in “kernel”:

• CSU grouping• Site provisioning

Page 18: Sakai 3 at CSU

Sakai 3 – Implementation

• Two phase project:1. Conceptual phase

• Philip Uys and Matt Morton-Allen• Stakeholder reference group• Scoping and analysis• August 2009 – December 2009

2. Implementation phase• Full project team• Design and implementation• Early 2010 - 2011?

Page 19: Sakai 3 at CSU

Questions?