Child pages
  • 07_31_2008 EvalSys Team Meeting (Adobe Connect)
Skip to end of metadata
Go to start of metadata

Objective: Provide a communication opportunity for members of the Sakai community who are interested in the Course Evaluation tool

Agenda items:

0. Dinking around with audio, etc. til everyone can hear (5 minutes)

1. Update on previous action items (10 minutes)

  • Update on Aaron's conference presentation
    • Aaron not on call; don't see slides on site yet
    • Presentation is available online: rtsp://video.cpm.jussieu.fr/Archive/visio/sakai/st080703_4.rm
  • Contrib instance for testing?
    • rSmart has discontinued that hosting service; won't be able to have a shared experience of testing the core software; Sean will check with QC group and the larger Sakai community
  • Feedback to SWIFT documentation?
    • Harriet's document - Cambridge's instance is branded SWIFT; has not been posted to confluence site, but is in email
  • What's new page (http://confluence.sakaiproject.org/confluence/x/moB9AQ)

2. Progress update on development (20 minutes)

  • U-M: performance profiling and email generation; functional testing status
    • Some new development on the tool
    • Planning roll out university-wide
    • Ability to present multiple instructors in a single evaluation
    • Consolidated email approach - changed some of the logic in the core tool to handle email the way U-M would like
    • Functional testing starting this week; in general things are going okay
    • Still dealing with issues of exchanging data between PeopleSoft and Sakai
    • Decision to participate will be put on the departments; some departments will mandate that all faculty will be evaluated
    • Multiple evaluation windows - Pharmacy School evaluates classes every week (bad news is it is coming up in a few weeks, good news is use is low so they can find bugs before university-wide rollout); Engineering mid-term evaluations; full-campus roll-out at end of semester; Process needs to begin in October timeframe
    • Question about how data is used for faculty review: Depends on department and how they use the data; sensitive issue
    • Michigan's branch is CT-623
  • Open issues:
    • MyEvaluations screen performance (see prior meeting notes)
      • Aaron and Rick have looked at Maryland's solution and issue is resolved with Maryland's solution
    • Student login and response submissions
      • Aaron and Rick have looked at Maryland's solution and issue is resolved with Maryland's solution

3. Plans for the Fall (20 minutes)

  • U-M: Full campus rollout out
  • Maryland: Continued full university-wide deployment adding more colleges with college level items; possibly adding department level items with a few departments

4. Next Steps/Action Items (5 minutes)

  • process for handling new requirements (e.g. option to separate responses from responder immediately)?
  • Understanding all the new system settings and what they do
    • Harriet has recently added some notes on the new settings in the Administrator's Guide
  • Regional meeting opportunity (Virginia Tech)?
    • November 11 and 12, 2008
  • Next Sakai Evaluation Tool group meeting in October
  • No labels