1. Supporting the Complete Learning LifeCycle The Next Generation of On-Line Learning Support Systems at the University of Michigan Future Learning Environments Presentation April 10, 2002

2. The Next Generation What we’ve done – the success of CT, WT What’s the context – increasing adoption, PIRC Where we’re going – what an NG system would look like, what vision it entails How will we get there – standards (OKI, Apache, …), CHEF Technology, open source, support for transition

3. UM.CourseTools

4. UM.CT Business School Effort - Results Over 80% of UM Business Courses now online

5. UM.WorkTools Support For Research Groups

6. Support for Work Groups UM.Worktools Scientific Research Groups Science Review Teams Technology Design Teams Currently over 3000 users worktools.si.umich.edu

7. UM.WT Support For Research Distributed Teams And Conferences

8. UMCT Adoption at UM-AA - Update Introduction Fall 1999 Now Fall 2001 Fall 2000Spring 2001 30,000

9. So, What’s Doubling Now? Fall 2000Winter 2001 Peak Users In Single Day Invariably A Tuesday Now Fall 2001 10,000

10. WorkTools Growth Now Fall 2001 Fall 2000Spring 2001Spring 2000 3000

11. The Next Generation What we’ve done – the success of CT, WT What’s the context –increasing adoption, success, PIRC –President’s Info Revolution Commission Where we’re going – what an NG system would look like, what vision it entails How will we get there – standards (OKI, Apache, …), CHEF Technology, open source

12. PIRC – Information Revolution at UM The University in a Changing Information Environment Never has the need been more pressing for the University of Michigan to examine its relationship to information and communication technologies. The information revolution that is radically altering our whole world at an ever- accelerating pace touches every aspect of university life. http://www.umich.edu/pres/inforev/

13. PIRC – Encourage Experimentation The key is to experiment in a systematic fashion, coordinating and exchanging information across the institution, and in the process transforming the University into a living laboratory. An “Ecology of Experimentation”

14. PIRC - Raise all boats A university-wide, across-the-curriculum approach is needed, providing faculty with the support they need and offering all students opportunities to use the state-of-the-art technology in education enhancing ways while at the same time learning to think critically about the implications of the information revolution… University-wide Approach

15. PIRC – Knowledge Networks Research and scholarship are increasingly interdisciplinary, collaborative efforts. The Internet and new information and communication technologies are enhancing — and transforming — research and scholarship, enabling users scattered throughout the world to share facilities, instruments, immense collections of multimedia information, and tools for analysis and synthesis. Knowledge Networks

16. PIRC – Knowledge Networks, Build and study them here Over the past decade, the University of Michigan has played a key role in designing, developing, and applying knowledge networks. The University should continue to pioneer by further developing knowledge networking technology, exploring innovative uses for it, and studying its impact on the way we work and learn. Building Knowledge Networks

17. The Next Generation What we’ve done – the success of CT, WT What’s the context –increasing adoption, PIRC Where we’re going – what an NG system would look like, what vision it entails How will we get there – standards (OKI, Apache, …), CHEF Technology, open source

18. Support for Learning Lifecycle Teaching, Learning Research, collaboration with colleagues Making it easy to move from one to the other Goal: Integration of research, the practice of knowledge work, within education

19. Enhancing Distributed Learning – Continuing to move forward Building on current functionality – CT, WT, Lessons Support for what users need –Group support –E-portfolio –Case-based tools –Grading, reporting Integration –Library resources –printing

20. Knowledge Networks Vision Open systems – in all senses –Open source, build community of support –Open to custom components, cots, fots –Open to all users Enabling core competency at University –Teaching/learning, research Supporting early adopters Experimenting at low cost Encouraging everyone – raising all boats Leading – we discover we are already – CT/WT –OKI, JetSpeed, IMS/SCORM (RDF, runtime teamlets)

21. The Next Generation What we’ve done – the success of CT, WT What’s the context – increasing adoption, PIRC Where we’re going – what an NG system would look like, what vision it entails How will we get there – standards (OKI, Apache, …), CHEF Technology, open source, support for transition

22. Choices in Platform Why adopt CHEF open source – code, tools, developer community configurability/customiz- ability - users, admin centralization/decentrali zation of services as appropriate aggregation - rss, html, xml - syndication prototype rapidly Why retire Domino proprietary rather closed not as easy adding features no community of developers finding expertise hard but, has been good to us

23. CourseTools: Assignments Quizzes … Worktools: ToDo list Data Access … Teleobservation – NEES Informatics/MetaData - CMCS Shared Core Features: Logon File upload Announcements Discussion Chat Schedule Mail archive … Gradebook CAPA Quizzes DissertationTool OKI APIs CHEF Technology Leveraging Education/Research Complementarities

24. OKI Users Content OKI “Core” Reference Architecture Component Specification Quiz White Board Virtual Lab Portfolio Management Content Outline User Interface Specification List Management Enterprise Data Exchange Specification Digital Asset Exchange Specification Enterprise Information -- Student Information Systems Asset Management -- Digital Library Initiatives Authentication Services Modular Authentication Process OKI “Core” Reference Architecture Users Content User Interface Specification

25. CHEF and the Grid CHEF node CoG XML CoG XML Grid

26. Support for Transition Continuing support for CT, natch Advance notice of timelines Input from users - faculty, students, staff, and other developers - as we go along Transition support as we go along, –Media Union staff –Online info, notices of NG development

27. Transition - CT.NG looks like CT Design criteria: A user familiar with CT should be able to easily use CT.NG. Interfaces should be recognizable. Actions should be similar. New features should be integrated into familiar frameworks.

28. Early CT.NG Prototype

29. CHEF Info Site http://intel.si.umich.edu/CHEF

30. Questions, comments, suggestions hardin@umich.edu