1. UM/MU Futures – Building Knowledge Networks The Next Generation of On-Line Learning and Research Support Systems Duderstadt Presentation June 14, 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, GRID, …), CHEF Technology, open source, support for transition Consortium ideas

3. UM.CourseTools Built on tests UM-AA, Dearborn, Ford/UAW Released Fall, 1999 - over 6,000 users Growth exceeds expectations – 11,000 in Winter 2000 Then over 16,000 users – Fall, 2000 Currently, over 30,000 users – Winter 2002 Rapid adoption continuing, and deepening

4. UM.CourseTools

5. UM.CT – Current Sites

6. UM.CT Custom course page presented to each student

7. UM.CT Announcements Everyone sees this.

8. UM.CT Course Schedule Link items to a description, assignment, or resource like lecture notes.

9. UM.CT Course Schedule User-configured choices for Course Schedule presentation

10. UM.CT Discussions

11. UM.CT Discussions Used for assignments Use discussion topics to present assignments when you want students to view each other’s work. Work originally submitted as an assignment can later be uploaded to the Discussions area for general review.

12. Here, each Resource links to a web page outside of CourseTools, creating a portable bookmark page. Using CourseTools doesn’t mean giving up current web presence. CourseTools is designed to maximize flexibility while maintaining continuity within University divisions. UM.CT

13. While new CourseTools users often limit resources to text files and links… …more advanced user often include a variety of visual and audio files to support and enhance student learning. A resource document can be attached to a discussion topic to Stimulate responses. UM.CT Resources And Discussions

14. UM.CT Resources

15. UM.CT Resources Only a Browser Needed

16. Students working off campus often run into difficulty because their browser or dial-in service is not correctly configured. UM.CT Help for Remote Users

17. UM.CT Business School Effort - Results Over 80% of UM Business Courses online after first year

18. Other UM.Tools Applications Support for testing, surveys – UM.Lessons Support for lecture capture, replay – UM.Lectures Support for research side of learning – UM.WorkTools

19. UM.Lectures Capturing Lectures For The Web And UM.CT

20. UM.Lessons

21. Easy to Build Quizes, Drills, Exams, Surveys Tests And Results Available Through UM.CT

22. UM.WorkTools

23. UM.WT Built on past Experiences With Distributed Research Groups – SPARC Support For Research Distributed Teams And Conferences

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

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

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

27. WorkTools Growth Fall 2001 Fall 2000Spring 2001Spring 2000 3000+ Starting its exponential climb… Now

28. Why Build CHEF Here? UM history of leadership in: –collaborative projects –on-line educational projects –combining technical and socio-technical knowledge in software development Provost LT Initiative NSF, NIH support – Collaboratories ITR, NEES, CFAR,… Time is right – UM.tools lifecycle, OKI, market experiences, net development

33. SPARC and WorkTools Collaboration Framework Targeted at real-time activities  Support for post-event collaboration, “electronic workshops” Collaboration focus on data viz  Support for collaboration throughout “scientific lifecycle” Lotus Domino-based [CourseTools]

35. Multi-Platform Collaboration

36. Great Lakes Regional CFAR

37. Network for Earthquake Engineering Simulation

38. Instrument Room Instrument Room Instrument Status Instrument Status Experimental Data Experimental Data On-Line Control On-Line Control Video Conferencing Video Conferencing Electronic Notebooks Electronic Notebooks Provides Access to: Materials Microcharacterization Collaboratory MMC Slide: Nestor Zaluzec, Argonne National Lab

39. http://tpm.amc.anl.gov/TPMLVideo17.html

40. Distributed PowerPoint Co-presence with remote groups Highest quality but affordable audio and video Multi-mode operation AG at the Chautauquas – A Panel Session

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

42. PIRC (President’s Information Revolution Committee) – Info Rev 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/

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

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

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

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

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

48. 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 Experimenting at low cost –Supporting early adopters Encouraging everyone – raising all boats, as CT has Leading –we discover we are already with CT/WT and enterprise integration –will further with OKI, JetSpeed, IMS/SCORM (RDF, runtime teamlets), GRID…

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

50. Next Generation Built on CHEF technology CT.NG the next generation CourseTools WT.NG the next generation WorkTools CHEF an open source software framework to construct CT.NG and WT.NG

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

52. 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, it has been good to us

53. Apache Tomcat Turbine Velocity Jetspeed CHEF Groups, Awareness, Tools, Administration Portal Engine UI Templating Engine Web Application Framework Servlet and JSP HTTP Server

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

55. CHEF Apache Tomcat Turbine Velocity Jetspeed Teamlet-Based Ed/Research Apps OKI/API’s Net-Based Services (Grid) Teamlets are tools built for the portal environment We are building the OKI APIs And GRID services into the portal environment

56. 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 OKI – Standards for LMS APIs

57. CHEF node CoG XML CoG XML Grid CHEF and the Grid – Access to Nationally Distributed Computing Resources

59. … 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 … So, we have a team portal …

60. Collaboration Tools built using CHEF CourseTools/WorkTools Next Generation –Existing collaboration tools –Additional capabilities & collaboration tools Presence, Synopsis, Notification, Personal worksite, Web Site, LabNotebook, DataViewer, etc… –Customizable Administrators End users –OKI built in –Grid enabled

61. Personal worksite WT.NG

62. Group worksites (collaboration groups) WT.NG

63. Announcement teamlet

64. Menu – access to tools (teamlets)

65. Discussion teamlet

66. CourseTools/Worktools Next Generation Built on a portal model Extended to support teams, not just individuals A portal aggregates Teamlets (tools) –A teamlet is a tool that displays in the portal –Teamlets can be mixed/matched on a page –Combine or not according to a Team’s/User’s needs

67. Worktools Next Generation

69. For any ‘page’…

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

74. Collaboration Tools – CT/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

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

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

77. … allow/deny permissions for a role

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

79. 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 Appears as menu element

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

81. 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…

82. Integrating Your Own Tools: Advanced Develop tool using Portlet API –Currently using: Jetspeed-1.4 Portlet API –Summer 2003: JAVA Portlet API 1.0 This is part of a Java Community process that will result in an open standard and an open source reference implementation Brings another level of standardization to portal environments So, CHEF could run on top of another compliant portal engine, eg, WebSphere, not just Jetspeed – IBM, Sun, Apache participants

83. Support for Transition Continuing support for CT/WT, 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

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

85. Early CT.NG Prototype

86. CHEF Info Site http://chefproject.org

87. stop hardin@umich.edu