1. Learning and Research The Next Generation of On-Line Learning Support Systems at the University of Michigan ACSF Presentation May 28, 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. FREE Kittens!! 8 weeks old, 1 female (black), 3 male 1st shots given 5/20/02 (health records at Remrock Farms) Call 734-424-9970 with questions

4. UM.CourseTools

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

6. UM.WorkTools Support For Research Groups

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

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

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

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

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

12. 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

13. 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/

14. 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”

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. Apache Tomcat Turbine Velocity Jetspeed CHEF Groups, Awareness, Tools Portal Engine UI Templating Engine Web Application Framework Servlet and JSP HTTP Server

25. CHEF Jetspeed Velocity (and some other Apache Jakarta technologies) Turbine Tomcat (this is the servlet/jsp/http engine) (possibly, but not at present) Apache HTTP (also will do HTTPS) We are contributing to the top two layers, CHEF (tools and services) and Jetspeed. Areas of Jetspeed contribution: - general features / bug fixes / stability – Portlet API, Java Community Process (JCP) definition and implementation – multi-user / collaborative / groups support - automatic updating / independent updating technologies - integration of OKI layers in the Jetspeed framework

26. CHEF: collaborative tools and services, enhancements to the Jetspeed Portal Engine Jetspeed: Portal Engine Areas of Jetspeed contribution: - general features / bug fixes / stability – Portlet API, Java Community Process (JCP) definition and implementation – multi-user / collaborative / groups support automatic updating / independent updating technologies integration of OKI layers in the Jetspeed framework Velocity: user interface template technology for web page construction Turbine: Web Application Framework Tomcat: Web server with Servlet support Apache: Web server

27. CHEF Apache Tomcat Turbine Velocity Jetspeed Teamlet-Based Ed/Research Apps OKI/API’s Net-Based Services (Grid)

28. 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

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

30. … plus OKI APIs to services… CHEF Apache Tomcat Turbine Velocity Jetspeed Portlet-Based Educational Apps OKI/API’s Net-Based Services (Grid) …plus CHEF framework (groups, awareness, etc.)… … with CHEF/Jetspeed portlets/teamlets for education and collaboration… … Conneted to GRID network services … UI Template engine

31. FREE Kittens!! 8 weeks old, 1 female (black), 3 male 1st shots given 5/20/02 (health records at Remrock Farms) Call 734-424-9970 with questions

32. Collaboration Tools built using CHEF Worktools Next Generation –Grid enabled –Existing collaboration tools –Additional capabilities & collaboration tools LabNotebook, Presence, Synopsis, Notification, Personal worksite, –Customizable Administrators End users –Data viewer

33. Personal worksite WT.NG

34. Group worksites (collaboration groups) WT.NG

35. Announcement teamlet

36. Menu – access to tools (teamlets)

37. Discussion teamlet

38. Worktools Next Generation Built on a portal model A portal aggregates Teamlets (tools) –A teamlet is a tool –Teamlets can be mixed/matched on a page –Combine or not according to a user’s needs

39. Worktools Next Generation

41. For any ‘page’…

42. … teamlets (tools) can be added or subtracted (permission controlled)

46. Collaboration Tools – WT.NG CHEF framework provides added configuration –Installation level –Worksite level –User level Administrator’s control over user’s role, privileges User’s personal preferences

47. Flexibility at the worksite level – control over users, roles, access privileges. For example…

48. …ability to add/change roles, and…

49. … allow/deny permissions for a role

50. Collaboration Tools – WT.NG NEES specific deliverables to be embedded in WT.NG –Data Viewer –Lab Notebook Other possibilities –Other NEES tools Interface to Data Repository (metadata tools) Interface to the Tele-presence tools (use CHEF as the universal interface environment)

51. Outline The UM contribution to NEES Collaboration tools – Worktools Collaboration tools – CHEF Collaboration tools – Worktools Next Generation (WT.NG) Integrating your own tools –Basic –Advanced Data viewer LabNotebook Timeline

52. Integrating Your Own Tools Basic Integration –Existing tools –Puts tool immediately into NEES context with minimal effort Advanced Integration –New tools –Develop using Portlet API –Tool can utilize NEES services and interact with other NEES tools

53. Integrating Your Own Web Tools: Basic Easy way to integrate existing tools Requires URL Accessible, iFrame compliant tool (e.g., web page, web app) Create simple teamlet definition for tool

54. Integrating Your Own Tools: Advanced Utilize CHEF/ NEESgrid services You do not have authorization to view this experiment. Authorization Service Data Directory Data Repository e.g., NEES Data Viewer Your Tool Here CHEF/ NEESgri d CHEF/ NEESgri d

55. Integrating Your Own Tools: Advanced Interact with other tools (e.g., notify) Experiment Control Page Start Experiment Configure Experiment Stop Experiment CHEF/ NEESgri d CHEF/ NEESgri d e.g., Experiment Control Page Your Tool Here e.g., Notification Service New Announcement… New Email… Alert to new data…

56. Integrating Your Own Tools: Advanced Develop tool using Portlet API –Currently using: Jetspeed-1.4 Portlet API –Summer 2003: JAVA Portlet API 1.0

57. Data Viewer Inputs – repository data User selects experiment, channels (data and/or video) Choose plot types Results: tiled, time synchronized plots of selected channels Through EA, will accept a limited, early spec data type with minimal user interface

58. Data Viewer Load vs time Drift vs time Load vs drift

59. Data Viewer

62. EA – prototype available Will be demo’d at the June 21 NEES Awardees meeting Post EA –convert to Chef teamlet –Discussions with Nestor (e.g., Tele-presence integration) –Add functionality (plots, UI control as indicated from EA usage)

63. Lab Notebook

66. 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

67. 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.

68. Early CT.NG Prototype

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

70. FREE Kittens!! 8 weeks old, 1 female (black), 3 male 1st shots given 5/20/02 (health records at Remrock Farms) Call 734-424-9970 with questions

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