learning and research the next generation of on-line learning support systems at the university of...
Post on 20-Dec-2015
214 views
TRANSCRIPT
Learning and Research
The Next Generation of On-Line Learning Support
Systems at the University of Michigan
ACSF PresentationMay 28, 2002
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
FREE Kittens!!
8 weeks old, 1 female (black), 3 male1st shots given 5/20/02 (health records at Remrock Farms)
Call 734-424-9970 with questions
UM.CourseTools
UM.CT Business School Effort - Results
Over 80% of UM Business Courses now online
UM.WorkTools
SupportForResearchGroups
Support forWork Groups
UM.Worktools
Scientific ResearchGroups
Science ReviewTeams
TechnologyDesignTeams
Currently over3000 users
worktools.si.umich.edu
UM.WT
SupportFor Research
DistributedTeamsAnd Conferences
0
5000
10000
15000
20000
25000
30000UMCT Adoption at UM-AA - Update
Introduction Fall 1999
NowFall 2001
Fall 2000 Spring 2001
30,000
So, What’s Doubling Now?
Fall 2000 Winter 2001
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
10000
Peak UsersInSingle Day
InvariablyATuesday
NowFall 2001
10,000
WorkTools Growth
0
500
1000
1500
2000
2500
NowFall 2001Fall 2000 Spring 2001Spring 2000
3000
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
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/
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”
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
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
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 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
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
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)
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
Choices in Platform
Why adopt CHEF• open source – code,
tools, developer community
• configurability/customiz-ability - users, admin
• centralization/decentralization 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
CourseTools:Assignments Quizzes …
Worktools:ToDo listData Access…
Teleobservation – NEESInformatics/MetaData - CMCS
SharedCore Features:LogonFile uploadAnnouncementsDiscussionChatScheduleMail archive …
Gradebook CAPA Quizzes
DissertationTool
OKI APIs
CHEF Technology
Leveraging Education/Research Complementarities
Apache
Tomcat
Turbine Velocity
Jetspeed
CHEFGroups, Awareness, Tools
Portal EngineUI Templating EngineWeb Application Framework
Servlet and JSP
HTTP Server
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
CHEF: collaborative tools and services, enhancements to the Jetspeed Portal Engine
Jetspeed: Portal EngineAreas 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
CHEF
Apache
Tomcat
Turbine Velocity
Jetspeed
Teamlet-Based Ed/Research Apps
OKI/API’s Net-BasedServices(Grid)
OKI
Users Content
OKI “Core” Reference Architecture
ComponentSpecification
Quiz
White Board
Virtual Lab
Portfolio Management
Content Outline
User InterfaceSpecification
List Management
Enterprise Data Exchange
Specification
DigitalAsset Exchange
Specification
EnterpriseInformation
--Student
Information Systems
AssetManagement
--Digital
LibraryInitiatives
AuthenticationServices
Modular Authentication
Process
OKI “Core” Reference Architecture
Users Content
User InterfaceSpecification
CHEF and the Grid
CHEF node
CHEF node
CoGXML
CoGXML
Grid
… plus OKIAPIs to services…
CHEF
Apache
Tomcat
Turbine Velocity
Jetspeed
Portlet-Based Educational Apps
OKI/API’s Net-BasedServices(Grid)
…plus CHEF framework (groups, awareness, etc.)…
… with CHEF/Jetspeedportlets/teamlets for education and collaboration…
… Conneted to GRID network services …
UI Template engine
FREE Kittens!!
8 weeks old, 1 female (black), 3 male1st shots given 5/20/02 (health records at Remrock Farms)
Call 734-424-9970 with questions
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
Personal worksiteWT.NG
Group worksites (collaboration groups)
WT.NG
Announcement teamlet
Menu – access to tools (teamlets)
Discussion teamlet
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
Worktools Next Generation
Worktools Next Generation
For any ‘page’…
… teamlets (tools)can be added or subtracted(permission controlled)
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
Flexibility at the worksite level – control over users, roles, access privileges. For example…
…ability to add/change roles, and…
… allow/deny permissions for a role
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)
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
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
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
Integrating Your Own Tools: Advanced
• Utilize CHEF/ NEESgrid services
You do not have authorization to view this experiment.
AuthorizationService
DataDirectory
DataRepository
e.g., NEESData Viewer
YourToolHere
CHEF/NEESgri
d
CHEF/NEESgri
d
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., ExperimentControl Page
YourToolHere
e.g., Notification
Service
New Announcement…
New Email…
Alert to new data…
Integrating Your Own Tools: Advanced
• Develop tool using Portlet API– Currently using: Jetspeed-1.4 Portlet
API– Summer 2003: JAVA Portlet API 1.0
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
Data Viewer
Load vs time
Drift vs time
Load vs drift
Data Viewer
Data Viewer
Data Viewer
• 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)
Lab Notebook
Lab Notebook
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
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.
Early CT.NG Prototype
CHEF Info Site
http://intel.si.umich.edu/CHEF
FREE Kittens!!
8 weeks old, 1 female (black), 3 male1st shots given 5/20/02 (health records at Remrock Farms)
Call 734-424-9970 with questions
