Sakai Futures… Sakai Presents Uppsala, Sweden Nov 2005 Joseph Hardin School of Information University of Michigan Sakai Project/Foundation Board KYOU / sakai Boundary, Situation

2 To Hope to Predict the Future… We must understand the past a bit.. What is Sakai? When? Who? Why Sakai? How? What is coming now…

3 So, What is Sakai? Sakai is a project – an initial grant for two years Sakai is an extensible framework - provides basic capabilities to support a wide range of tools and services – teaching and research Sakai is a set of tools - written and supported by various groups and individuals Sakai is a product - a released bundle of the framework and a set of tools which have been tested and released as a unit Sakai is a community – an emerging group of people and resources supporting the code and each other, and learning how as we go. Now, Sakai is a Foundation too.

4 The Sakai Project “The University of Michigan, Indiana University, MIT, Stanford, the uPortal Consortium, and the Open Knowledge Initiative (OKI) are joining forces to integrate and synchronize their considerable educational software into a pre-integrated collection of open source tools.” Sakai Project receives $2.4 million grant from Mellon

5 Sakai Funding Each of the 4 Core Universities Commits –5+ developers/architects, etc. under Sakai Board project direction for 2 years –Public commitment to implement Sakai –Open/Open licensing – “Community Source” So, overall project levels –$4.4M in institutional staff (27 FTE) –$2.4M Mellon, $300K Hewlett (first year) –Additional investment through partners

6 Sakai Project Deliverables Sakai Community – Committed and active Working Code – CMS/CLE- Collaboration and Learning Environment – Sakai 1.0 Course management system – core tools plus Quizzing and assessment tools, [ePortfolio from OSPI], etc Research collaboration system Portal (uPortal 2.3, 3.x) Modular tools - also pre-integrated to work out of the box Tool Portability Profile Specifications for writing portable software to achieve application ‘code mobility’ among institutions – modular tools and services Synchronized development, adoptions at Michigan, Indiana, MIT, Stanford – Sakai 1.0 is the next generation for CourseWork, CHEF, Oncourse, Stellar

7 Why: All the simple reasons These are core infrastructures at our Universities Economic advantages to core schools, partners Higher ed values – open, sharing, building the commons – core support for collaboration tech We should be good at this – teaching, research are our core competencies; collab essential Maintains institutional capacity, independence Ability to rapidly innovate – move our tools within/among HE institutions rapidly Based on goals of interoperability - Desire to harvest research advances and faculty innovation in teaching quickly

8 Sakai in Context – Open Source This is part of a rapidly emerging mode of constructing software – Open Source Open Source is more than a license - Indeed, there are multiple types of OS licensing – Sakai uses an Apache style Open Source is a way of doing business, a method and set of practices, loosely defined, but different from traditional methods, that emphasizes openness and meritocracy Born in educational institutions, now coming back to educational institutions

9 Economics - Emerging Models of Open Source Development Institutions as OS Developers –Traditional – consortia –Hybrid – dual centers of power –OS like – adopt social structures, practices All answering multiple questions –User facing dev – higher on app stack –Balance various stakeholders –How to do complex integration of UI We’ll come back to some of this…

10 Breaking Some LMS Boundaries Sakai is a Collaboration and Learning Environment – not only a LMS/CMS/VLE It is intended to be a framework to support a variety of types of “collaboration” of which teaching and learning is just one eResearch, Virtual Research Environments are another Support for online “work groups” in general yet another

11 Support Teaching and Learning

12 Support Distributed Research

13 Placing the Sakai Product Collaboration and eResearch Teaching and Learning

14 Requirements Overlap Physics Research Collaboration Earthquake Research Collaboration Teaching and Learning Grid Computing Visualization Data Repository Large Data Libraries Quizzes Grading Tools Syllabus SCORM Chat Discussion Resources

15 Tests & Quizzes Tool Discussion Tool Research Team Support OnLine Class Support

16 NMI / OGCE NSF National Middleware Initiative Indiana, UTexas, ANL, UM, NCSA

17 Bringing the lab to the classroom Bringing the lab to the classroom

18 Support Online Collaboration Sakai ≠ Course Management System Sakai = Collaboration & Learning Environment Use for teaching/learning/research and many other online group activities. Portal Staff 1Student Discussion Forum Middle East News Feed Discussion Forum Resource Management Collaborative Project Portlet ASUC Middle East Discussion Portlet Staff 2Staff 3Student

19 Additional General Collaboration Tools Under Development Wiki based on Radeox Blog Shared Display Shared Whiteboard Multicast Audio Multicast Video These are works-in-progress by members of the Sakai eResearch community. There are no dates for release.

20 Ctools – Production Sakai at University of Michigan

21 Ctools – List of Worksites – Classes, Projects

22 Site/class home page

23 Site Resources area

24 Discussion tool – Forums

25 Archive

26 Site Info – class list

27 Software Progress to date –Releases on time 1.0 (June2004), 1.5 (Dec2004), 2.0 (June 2005), 2.1 (coming Nov2005) – on track; final tag set made –Production and pilots underway, in pipeline; –Processes being developed - organizational methods evolving rapidly; release engineering, distributed QA, contributions acceptance models, definition of enterprise bundle, methods for OS Core… This “Community Source” stuff is a learning process

28 In full production With >35,000 users at University of Michigan Indiana University production transition started in Fall 2005 On to Stanford, UC-Berkeley, Foothill, MIT in 2005

29 So, some Sakai components Most of these are built _not_ as part of the core effort, but rather by those who felt strongly enough to go do it. Think about this. It is the way Sakai will grow and incorporate innovation.

30 Open Source Portfolio Initiative (OSPI) OSPI is a community of individuals and organizations collaborating on the development of the leading open source electronic portfolio software. The Open Source Portfolio software is individual-centered, enabling users to gather work products and other artifacts to be stored and shared with others, and used for personal growth and development. The ePortfolio toolset is being developed on the Sakai infrastructure providing a stand alone application as well as an integration of rich portfolio tools in the full suite of Sakai applications. See Tracking Sakai releases

31 Open Portfolio - Sakai Tool

32

33 Flexible Skinning at Portal Level

34 Skins at Course Site Level

35 Melete – Lesson Builder

36 Linking to websites to supplement or support the content of a lesson Composing content online using a WYSIWYG Editor Uploading all types of documents for lesson components/content This is MELETE

37 Accessibility metadata Ability to check for lack of compliance with Section 508 accessibility guidelines Will plug in to TILE from U Toronto.

38 Student View – Navigation & Licensing Navigation is created automatically content Authors can license their content

39 The Twin Peaks Project Sun Microsystems, Inc. funded deployment of a citation/link authoring tool by Indiana University. The Twin Peaks project is an experiment in providing a search and one click selection of library electronic resources from within the Sakai authoring tool. The interim tool demonstrated at the December 2005 SEPP Conference provided searching of EBSCO Academic Preimer, ERIC, or the IU Libaries SFX enhanced online catalog's electronic holdings.

40 Search as part of WYSIWYG Editor

41 Twin Peaks - access to library resources from within editing environment(s) in Sakai

42

43 New Discussion Tool – Quick Response to Users Demands

44 Online Presence and Messaging within forum

45 The Berkeley Grade Book University of California, Berkeley funded development of an on-line grade book. The UC Berkeley grade book is now in pilot on the Berkeley campus as a stand alone tool, and moving into pilot at IU. It is part of the 2.0 release.

46 Grad Tools The University of Michigan’s Grad Tools provides doctoral students a way of tracking their degree progress from the point of choosing an advisor to degree conferral. Doctoral students create their own site, which contains an automatically personalized dissertation checklist based on data from their department and from the graduate school. Students control access to their Grad Tools site, and use collaboration features common to CTools, including file storage, group , notification, structured discussion, and more.

47

48 Samigo – Testing and Assessment Part of 1.5 release

49 All these are examples of distributed development of innovation – Sakai Partners building new tools, and sharing them immediately with the community, through the Sakai platform. We are also doing the same with research tools – here’s some examples:

50 Open Grid Computing Environment Example: Submitting a job to the GRID. Note research computing tools added on left.

51 NEESgrid interface

52 NEESgird interface

53 NEESgrid interface

54 NEESgrid: Data viewer

55 NEESgrid: LabNotebook

56 NEESgrid: Simulation

57 Remember: Sakai Concepts It is both research and teaching - it is all “collaboration” - many tools in common –Teaching: Courses, tools, drop-boxes –Research: Building user interface and services on the Grid and Virtual Organizations Teaching and Learning Collaborative Research Collaboration and Learning Environment

58 Modular Tools - SOA Sakai Need to capture innovation led to Services Oriented Architecture (SOA) approach for Sakai Framework – this is evolving and stabilizing as we speak – 2.1 release SOA allows anyone to build tools without need to also build many “services” – like authn/z, file management, messaging, etc. – these are available from the framework Speeds interesting tool development and encourages integration, sharing of results

59 The Sakai Framework The need to satisfy the often conflicting goals of ease of use, ease of expansion, configuration flexibility, environmental portability and rock-solid production reliability suitable for enterprise deployment.

60 Sakai Foundational Technologies Java 1.4 Oracle Apache - SSL, mod_jk, WEBISO, virtual hosting MySql 4.1 Sakai consists of technologies chosen to be common in Java Enterprise Environments. Sakai Tomcat 5.5 Spring Hibernate Java Server Faces Velocity (legacy)

Service Oriented Architecture My Monolithic Code Persistence Browser Presentation Code Persistence Browser Service Code Service Interface (i.e. API)

Sakai Applications and Framework Framework Application SAF—Kernel SAF—Common Services Application Services Tool Code (Java) Tool Layout (JSP) SAF—Presentation Services Service Interface (i.e. API)

Sakai Web Services Framework Application SAF—Kernel SAF—Common Services Application Services Web Services Client (PHP,.NET, Java, VB, etc...) Jakarta Axis Web Services End Point Web Svcs Service Interface (i.e. API)

Web Services and Web Applications Framework Application SAF—Kernel SAF—Common Services Application Services Tool Code Tool Layout Presentation Service Interface (i.e. API) WS Client Axis WS End Point Web Svcs

65 Architecture Goals Provide solid, robust framework Support native tool development in Java Ease integration of ‘3Ps’ tools (Perl, Python, PHP) – capture local innovation Allow for locally-chosen levels of integration and use of new tools Encourage distributed support, development – open source community

66 Sakai Partner’s Program Developing the Community that’s Directing the Source. Membership Fee: US$10K per year ($5K for smaller schools), 3 years Access to SEPP staff –Community development liaison –SEPP developers, documentation writers Invitation to Sakai Partners Conferences –Developer training for the TPP, tool development –Strategy and implementation workshops –Software exchange for partner-developed tools Seat at the Table as Sakai Develops The success of this effort will determine The long term success of the project.

67 Arizona State University Boston University School of Management Brown University Carleton College Carnegie Foundation for Advancement of Teaching Carnegie Mellon University Coastline Community College Columbia University Community College of Southern Nevada Cornell University Dartmouth College Florida Community College/Jacksonville Foothill-De Anza Community College Franklin University Georgetown University Hosei University Harvard University Johns Hopkins University Lubeck University of Applied Sciences Maricopa County Community College Monash University Nagoya University New York University Northeastern University North-West University (SA) Northwestern University Ohio State University Portland State University Princeton University Roskilde University (Denmark) Rutgers University Simon Fraser University State University of New York Sakai Educational Partners - Feb 1, 2004 Stockholm University SURF/University of Amsterdam Tufts University Universidad Politecnica de Valencia (Spain) Universitat de Lleida (Spain) University of Arizona University of California Berkeley University of California, Davis University of California, Los Angeles University of California, Merced University of California, Santa Barbara University of Cambridge, CARET University of Cape Town, SA University of Colorado at Boulder University of Delaware University of Hawaii University of Hull University of Illinois at Urbana-Champaign University of Minnesota University of Missouri University of Nebraska University of Oklahoma University of Texas at Austin University of Virginia University of Washington University of Wisconsin, Madison Virginia Polytechnic Institute/University Whitman College Yale University University of Melbourne, Australia University of Toronto, Knowledge Media Design Institute 20% non-US

Known Pilots and Production Boston University School of ManagementBoston University School of Management Carleton College Foothill-De Anza Community College DistrictFoothill-De Anza Community College District Indiana University Johns Hopkins University Lübeck University of Applied Sciences, GermanyLübeck University of Applied Sciences, Germany Massachusetts Institute of TechnologyMassachusetts Institute of Technology Northwestern University Rutgers Stanford University University of California, Berkeley University of California, Berkeley University of California, Merced University of California, Merced University of Cape Town, SA University Fernando Pessoa, Portugal University Fernando Pessoa, Portugal University of Lleida, Spain University of Michigan University of Missouri University of Virginia Whitman College Yale University

69 Sakai in Production

70 Current Stats - CTools Current Fall 05 class sites Total project sites (note) GradTools student sites ~20,000 unique users on a busy day

71 The University of South Africa (UNISA) will be going into full production on Sakai in January It will be fully integrated with our student information system Projected student user base: Projected staff user base: 3000 Technical contact: Shaun Donovan

72 Sakai Community Activities Developer and Adopter Support SPP - Sakai Partner’s Program Community for ongoing dev, adoption, support Commercial Support – SCA, IMS, maybe SPA Based on open-open licensing – open source, open for commercialization- see ECL at sakaiproject.org SCA – Fee-based services from vendors include… Installation/integration, on-going support, training Think of as “Sakai Red Hats” IMS – working with other CLE/CMS vendors on interoperability between frameworks

73 SCA – Sakai Commercial Affiliates First Generation – Open Source Software Support Support for the Sakai codebase = SCA Member

74 Second Generation SCA Partners

75 Reference Architecture: Working with a group of higher education leaders and partners, IBM intends to publish a reference architecture for the higher education industry and to create an integration stack (…) SW Stack and Offering: With the Sakai application as the core, IBM plans to build an end-to-end software stack(…) HW Stack and Offering: Building on the software stack, the next logical step is to build a combined software/hardware stack and provide clients with what we are calling a “Sakai-in-a-Box” offering that enables them to order a Sakai installed server that they simply plug in and configure to their specific institution’s needs. This will be a significant factor in enabling a fast adoption rate for Sakai. Hosting Stack and Offering: Examining the successful business models of commercially successfully Course Management Systems highlights the fact that being able to provide a web-accessible ‘hosted’ offering is a key factor in fast commercial adoption(…) Code Donations: IBM is well known for our significant contributions of source code to the open source community, and we are open to considering the donation of IBM owned assets to the Sakai community. What we plan to do…

76 “Commercial” SW expertise: As one of the world’s largest software companies,IBM Software Group can offer the Sakai Project significant experience across the full spectrum of code development, packaging, testing and commercialization. Global Sales and Marketing Channel: IBM manages the single largest Education Industry channel in the world, combining the most experienced team of IBM Education Industry sales experts in the world with the most extensive Business Partner channel in the world. With the key to Sakai’s success being quick, broad commercial adoption, having an experienced, global channel will be a significant contributor. What we plan to do… 2

77 And, interestingly… Sun Unisys Apple … Are also joining the Sakai Commercial Affiliates, and proposing to do similar things with the Sakai Community

78 New Models of Production OS is giving us new models of working together, of collaborating Sakai is bringing these models to attention of universities’ administrations Meritocratic, collaborative, ‘participatory democracy’ as a way of meeting needs Requires, often, change of thinking to realize economic and organizational benefits

79 Institutional ‘readiness’ Virtual organizations – the surprise of open source – Weber – constructing complex artifacts VO’s match with educational organizations New cost evaluations – building together –All isolated efforts are now suspect; you will be asked: why aren’t you collaborating with other OS efforts? –This helps drive standards; it is in open environments that they can thrive, freed of the inherent structural stumbling blocks of purely proprietary commercial dynamics (the need for differentiation)

80 “Community source describes a model for the purposeful coordinating of work in a community. It is based on many of the principles of open source development efforts, but community source efforts rely more explicitly on defined roles, responsibilities, and funded commitments by community members than some open source development models.” Community Source Projects “Community Investments for ICommunity Outcomes” Thanks to Brad Wheeler

81 Reflecting on Our Efforts Open Source Projects are crucial to supporting innovation in higher ed We have some examples now of ‘for higher ed, by higher ed’ OS efforts A literature is developing around the dynamics of open source communities What can we learn from experience and add to our common stock of knowledge; we are learning institutions, after all

82 Open Source Changing Us Moving across communities Questioning value of hierarchy Accepting, requiring responsibility Adjusting stance to risk Driving innovation from end-user through their participation Moving action to the edges – like the net Is OS changing us, and will we let it? Universities good place to try these experiments And good economics are emerging to support this

83 Sakai Foundation Formed as a non-profit corporation to support, sustain, and promote Sakai. Initial foundation board is the current Sakai project board, with open nominations (right now), elections next month for three retiring Sakai board members. Ten on Board. Annual budget of $1M from member contributions – Will have 4-6 staff positions funded by the Foundation Support staff, core architecture and framework, release process – Two conferences per year, no cost to members Membership fee is $10,000 per year for educational institutions, non-profits, or commercial partners ($5,000 for smaller schools).

84 Sakaiproject.org

85 Sakai: More Information Main site: – Bugs: bugs.sakaiproject.org Sakai-wide collaboration area – collab.sakaiproject.org – –

86 Winter Conference 2005 Technical Description of Dev & Contrib Processes OSP Sessions Pedagogy, eScience Sessions Sakai Foundation Update Election Results Line Dancing/Salsa Deep In The Heart of Sakai Austin, Texas - December 7-9

87 Tak

88 Sakai UM OCW Web Site or other Institutional Repository Publication Pipeline Digital Course Materials: (1) Exporting from CTools (2) Matching OCW Categories (3) Increasing Production Values (4) Standardizing (5) IP Management Raw Course Content Vetted OCW Content Teaching Research What Student Sees – Really, a Bunch of Stuff What World Sees – Targeted Re-use Publishing from Sakai – An OER/OCW Pipeline MIT OCW process doesn’t scale. How automated can we make this process?