hardin by wanghonghx

VIEWS: 6 PAGES: 45

									            CHEF
             CSG
          May 7, 2003
          Joseph Hardin
  Collaborative Technologies Lab
Media Union & School of Information
       University of Michigan
         University Missions
• CourseTools – a first-generation course
  management system
• WorkTools – part of a series of efforts in
  building systems for support of scientific
  research teams
  These two paths have a lot in common, as
  instances of collaboration support systems,
  and have led to:
• CHEF – A framework for building the next
  generation of both systems
UM.CT

Custom
course
page
presented
to
each
student
UM.CT

Help
for
Remote
Users




          Students working off campus
         often run into difficulty because
          their browser or dial-in service
            is not correctly configured.
Support for
Work Groups

UM.Worktools

Scientific
Research
Groups

Science
Review
Teams

Technology
Design
Teams

Currently over
5500 users




                 worktools.si.umich.edu
            Adoption of CT/WT
                                     Over 9,000
30000     Over 35,000        2500


                             2000
25000

                             1500
20000


15000                        1000

10000                         500

 5000
                               0


                                WT Users – Accelerating
    0



CT Users - Saturating
                             We see these as foundation
10000
9000
8000
7000
6000                         efforts in understanding and
                             building “Knowledge Work
5000
4000
3000


                             Support Systems” for UMich
2000
1000



                             faculty, students and staff,
   0




        CT Use - Deepening   and remote collaborators.
                     So, CHEF as Next Step(s)




http://chefproject.org
                          Shared
                          Core Features:
                          Logon
                          File upload
    CourseTools:                                 Worktools:
                          Announcements
    Assignments                                  ToDo list
                          Discussion
    Quizzes                                      Data Access
                          Chat
     …                                           …
                          Schedule
                          Mail archive
                               …


Gradebook
 CAPA Quizzes
                                                 DissertationTool
                   Teleobservation – NEES
                   Informatics/MetaData - CMCS   OKI APIs

                          CHEF Technology


            Leveraging Education/Research Complementarities
Network for
Earthquake
Engineering
Simulation
  CHEF and the Grid – Access to Globally
    Distributed Computing Resources
                                 Grid




                           CoG
                           XML
                                        CoG
                                        XML
                     CHEF node
Moving to GRID
services model (OGSA)                    CHEF node
as it develops. And it
did last Wednesday…
Home
Home
Resources
CMCS is enabled by broad
     collaboration
        • Development partnerships cut across offices and
          agencies

           SAM
        • Collaborations also include CCA, SDM ISICS.
        • A collaboration of eight national labs and
          universities span chemical scales
        • Collaboration opportunities for future
           – Xportlets work at Indiana University
           – Portal web Services
           – NeesGrid work at University of Michigan
                                     CMCS Explorer is a data
                                     management tool for accessing
                                     data across DAV resources.




                  The default address in CMCS Explorer for My
                  Workspace is the path to your personal data
                  folder. In a team workspace, the default address
                  points to the team’s data folder.

CMCS Explorer shows tree and file views, can spawn
viewers and tools for specific files, and has search,
notification and pedigree capabilities.
Current Implementation
Pedigree Browsing in CHEF



                       Data is linked to
                       projects, references,
                       inputs, and outputs




 The Browser enables
 metadata editing.
 Automatic Translation
and Metadata Extraction
                  Data translations provided
                  automatically by SAM using
                  previously registered XSLT’s
                  for this file type.
        Pedigree Graph in CMCS




Pedigree graph provides a two-dimensional visualization of a data
resource and all of its relationships. Users can easily see the
relationships without following all pedigree links.
              Data + Metadata
• Metadata allows the creation of revolutionary new types
  of collaborative chemical science projects, coordinating
  research efforts across chemical scales.
• Metadata dramatically increases accessibility of state-of-
  the-art research knowledge to industry and the public.
• CMCS data repository with pedigree tracking provides a
  new means for evaluating research claims.
• CMCS pedigree graphing provides a visual
  representation of data relationships.
• CMCS metadata supports allows scientific peer review of
  electronic data, which is important to groups like
  IUPAChem.
• CMCS metadata is extensible.
  Leveraging Research Support

• NSF National Middleware Initiative grant
  – U Michigan
  – U Texas-Austin
  – Indiana U
  – NCSA
  – Argonne National Lab
  3 year support for core GRID services
    integration; Jetspeed/CHEF as portal tech
             CHEF Summary
• CourseTools.NG – online support for learning; in
  pilot, fall rollout
• WorkTools.NG – online support for research,
  workgroups; in development for NEES, CMCS,
  NMI, rollout late summer; continuing development

• Goals – enhance online tools; make it easy to
  move between teaching and research; build
  standards efforts, collaborations so market of
  components develops
     Why Open Source CMS?
• University should not outsource a core
  competence – teaching
• It fits University value structures, we are
  an open community
• It can build the extended academic
  community through collaboration and
  shared effort
• It is a grand experiment, worthy of the
  University’s participation
                  CHEF Architecture
                                     Teamlets:
                                  Written in JAVA
                                  Responsible for      Portal
    Services                             GUI           Engine:
   Persistent                      Operate in the
  System-wide                       context of a      Jetspeed     Web
    Multiple                           session.        Velocity   Server:
                  Services API



implementations                   Rely on services      CHEF
   of services                   for any persistent               Tomcat
                                   or “cross-user”                Turbine
Configurable as                     information.
    to what
implementation                              Servlets:
 provides what                   Access services outside of the
    service                       portal engine: AccessServlet
                                      and WebDavServlet

                                   Non-HTTP Components (i.e. E-Mail)
       CHEF/OKI Relationship
                                     Teamlets:
                                  Written in JAVA
                                  Responsible for
    Services                                           Portal:
                                         GUI
   Persistent
                                   Operate in the
 System-wide                                           Tomcat
           O
     Multiple
implementation
                  Services API      context of a
                                       session.
                                                       Turbine
                                                      Jetspeed
                                  Rely on services
  s of services
           K
Configurable as
     to what
                                 for any persistent
                                   or “cross-user”
                                                          +
                                    information.
           I
implementation
 provides what
                                                        CHEF
                                                      extensions
     service                            ….                 to
                                                       Jetspeed

                                        ….
     OKI APIs – CHEF Implementation
•    Authentication                  •   Filing (*)
•    Authorization                   •   Hierarchy (*)
•    Local ID                        •   UserMessaging (*)
•    Logging                         •   WorkFlow (**)
•    DBC                             •   Scheduling (**)
•    Shared Objects             As OKI APIs become available
     (Agent, Group,             we either swap out CHEF APIs
     AgentIterator)             or build OKI translators –
                                ‘Innovate and Normalize’
    * unpublished but well enough along that we can do something
    ** unpublished, unspecified
                          localid and locallyuniqueidentifier
NSDL OAIster/CHEF Proposal
                                             User
                                             portals
                                                                          Tool          Tool
                                                                   Tool          Tool
     DLXS                                                   OAI           Tool
                                                                          Tool                 n
   Middleware                     OKI                      Records
                                                                   Tool
                                                                                         2
                                                            Tool
         • Transformation         DR                                  User 1
         • Indexing
         • Filtering                                                        Team-aware
                                • Query                                     Portlets
                                • Response

    OAIster                                                                        • Retrieving
    Topical                                        OKI APIs                        • Saving
                                                                                   • New Search
   Data Sets

                   DLXS
                                                       Web Services
                                                 Standard CHEF services
                                                 (e.g., Discussions, Schedule)
                                                 Added Value: Saving/retrieving
        Team aware portlets include              query/response sets
        Standard CHEF tools plus                 In team context
        Search (with search tracking)
                                                                            CHEF
         Current CHEF Environment
CHEF Uses Jetspeed as its                     A CHEF Application
tool coordination                          Jetspeed                  Turbine
framework, velocity as its
presentation language,
Portlet for its tool            Velocity                  Portlet
                                                                                  CHEF
specification, and Turbine
for its service broker.
                                XML/XSLT                  Portlet                  OKI
There is a wide range of
underlying services
including OKI, CHEF, and         HTML                     Portlet                 Grid
Grid Services.
                                     PERL, JSP, etc
CHEF/Jetspeed also
supports “simple”               Ideally, all of these interfaces would not be based on a
integration of tools using an   particular product (Jetspeed, uPortal, WebSphere, etc)
i-frame which are not           but instead would be based on a standard which was
                                supported across products. Then we could share
portlet-based.                  components.
                 Standards Efforts
• The full suite of standards is several years out
   – Some need our input now
       • OKI – we are working in this space
       • WSRP – Support WSDL (i.e. pre-presentation data) instead of
         HTML (post-presentation)
       • JSR-168 and WSIA – Service lifecycle, brokering, discovery
• We need to start a collaborative effort to bring order to
  this problem space
   – CHEF has one useful architecture to provide transition
       • In both the Educational and Research support areas
       • As standards evolve, we can quickly test and deploy them
       • Becoming “Jetspeed agnostic” by abstracting APIs
• If we can work together to solve the standards problems,
  organizations can maintain their existing portals and add
  support for these standards, upgrading as they go.
    Cross-Portal Development
• IMS at data level
• OKI at services level
• Building channel adapters for
  Jetspeed<->uPortal
• WSRP++ and display level ‘standards’
  and best practices
  – Setting up meeting with uPortal, CHEF, IU
    portal, Stellar MIT developers to discuss,
    figure out next steps

  Goal is, always, interoperable components
Component Interoperability




                             •Navigo project
                             Michigan,MIT,Stanford,Indiana
                             •Goal is real tool, module
                             interoperability
                             •On the way to standards
   Research, Teaching and Public
              Service
• Alliance for Community Technology
• African AIDs Project
• AIHEC – American Indian Higher Education
  Consortium
How do open source, collaborative efforts
 contribute to and help us understand
 the new information dynamics in all our
 domains of interest?
                         CHEF Project Site




http://chefproject.org
               stop

hardin@umich.edu

								
To top