Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (9)
Similaire à Edu0442
Similaire à Edu0442 (20)
Plus de jiali zhang
Plus de jiali zhang (20)
Dernier
Dernier (20)
Edu0442
- 1. "Sakai: A Collaboration Between the University of Michigan, Indiana University, MIT, Stanford, OKI, and the uPortal Consortium“ Amitava ‘Babi’ Mitra Executive Director Academic Media Production Services MIT EDUCAUSE 2004 October 21, 2004 Denver
- 2. "Sakai: A Collaboration Between the University of Michigan, Indiana University, MIT, Stanford, OKI, and the uPortal Consortium“ * What is Sakai ? * Why now ? * Deliverables * Where have we reached ? * Sakai Educational Partners Program * Architecture and Framework * Features and Functionality * Lessons Learnt * Going Forward
- 10. Sakai project launched in Jan 04
- 12. Sakai Final 1.0 Release at Sakaiproject.org
- 13. Those who are making it happen And many many more…
- 18. Sakaiproject.org gateway to DGs
- 19. Discussion Groups, Open Forums
- 21. Abstract Sakai Architecture Aggregator Presentation Tools Services System Client Sakai will work with a variety clients, including browsers Aggregators typically mean portals. Presentation is separated from the tool for better control. Tools act as the glue between the UI and services. Services provide abstract, re-usable functionality. The system in most cases is a server or system cluster.
- 23. Sakai
- 24. The Sakai Architecture WSRP JavaServer Faces Sakai Tools App Services The goal is support any portal that supports standards. WSRP will be the primary output from Sakai tools. JavaSever faces allow UI descriptions using XML. Sakai tools manage JSF events using services. Sakai services are revealed via Sakai API’s. Common services will be based on OKI models. Portal Common Services
- 25. The Sakai User Interface
- 39. The Sakai Board Joseph Hardin University of Michigan Chair, Sakai [email_address] Brad Wheeler Indiana University Vice Chair, Sakai [email_address] Jeff Merriman OKI/MIT [email_address] Vivian Sinou Foothill-DeAnza [email_address] Lois Brooks Stanford University [email_address] Amitava ‘Babi’ Mitra MIT [email_address] Mara Hancock University of California, Berkeley [email_address] Carl Jacobson uPortal/University of Delaware [email_address]
Notes de l'éditeur
- This set of 10 slides provides a high level overview of the Sakai Project. It is designed to be used by anyone who wishes to brief others regarding Sakai. We recommend using the Sakai Project Prospectus as an additional handout (see www.sakaiproject.org). These slides are accurate as of 20 January 2004. Updates will be posted at the Sakai Project website along with additional FAQs.
- This set of 10 slides provides a high level overview of the Sakai Project. It is designed to be used by anyone who wishes to brief others regarding Sakai. We recommend using the Sakai Project Prospectus as an additional handout (see www.sakaiproject.org). These slides are accurate as of 20 January 2004. Updates will be posted at the Sakai Project website along with additional FAQs.
- 2003 was the year that data and technical standards matured sufficiently along with growing university engagement to set the stage for the Sakai Project. Many institutions recognize the success of Linux and Apache as infrastructure and believe that Application software for education is the next open source domain. Gartner 2003 also views education as a prime candidate for open source applications. 2004 will be the year when the standards take a big step forward and enterprise-scale, open source applications become more available. 2005 will be the year at many institutions for broader implementation of refined applications.
- Note: The Open Source Portfolio Initiative’s release 2.0 will be based on the Sakai Tool Portability Profile. It is a separate project based on a Mellon grant to Indiana University in partnership with rsmart and OSPI.
- This slide builds to show the IP contributions of the Sakai Core institutions and then the two years of the project towards the releases.
- Official launch date for SEPP services is 1 March 2004. The Core Sakai institutions will develop ensure the project deliverables are met during the 2 years of the Sakai Project. The SEPP is the long-term, self-funded community to ensure Sakai’s continuing evolution and value. 10K fee is per institution – other fees may be applicable for University Systems or National government-level participation. Over a dozen partner institution commitments already committed to SEPP as of January 2004 (announcements soon). Note that some estimate licensing costs of a course management system are approximately 20% of the total cost of ownership. The open source nature of Sakai means that any institution can use the Sakai software with no licensing costs or any fees whatsoever for the code. The Sakai Educational Partner’s Program provides a community to help address the other 80% of the cost of a CMS or other Sakai tool.
- Official launch date for SEPP services is 1 March 2004. The Core Sakai institutions will develop ensure the project deliverables are met during the 2 years of the Sakai Project. The SEPP is the long-term, self-funded community to ensure Sakai’s continuing evolution and value. 10K fee is per institution – other fees may be applicable for University Systems or National government-level participation. Over a dozen partner institution commitments already committed to SEPP as of January 2004 (announcements soon). Note that some estimate licensing costs of a course management system are approximately 20% of the total cost of ownership. The open source nature of Sakai means that any institution can use the Sakai software with no licensing costs or any fees whatsoever for the code. The Sakai Educational Partner’s Program provides a community to help address the other 80% of the cost of a CMS or other Sakai tool.