July 12, 2006

VetMed 07/12/06

Missed 1st half of meeting - beer truck overturned on I80/I5 interchange!

Scheduler - Ilios/CERE

Discussion of designations for managing level-based groups.
Working on Student Group linked to user object concepts for shared levels of information/material,e.g.
1) all students access lectures on top shared-level
2) students access labs on a group-level beneath the top shared-level
3) some students may be in a sub-group beneath the group-level (e.g., discussion groups within the lab group)
4) possibly continuing tree up to five levels in depth

Evaluations

Interaction with Sakai will be fairly complex. While it is desirable to release to all courses in fall, Scott is concerned about testing adequately, and prefers pilot testing prior to full release. He expressed concern over the higher risk for data loss issues and stated that solid user testing is needed. Ray noted that only core features are required for initial release.

Jira management of bug fixes w/in group, backporting and organization issues

Discussion of roster tool fix for 2.1.2: access to viewing roster data limited to instructors, department proxies, and administrators. Will need to assign permissions to appropriate roles. Need to review code to add permission on VetMed roster display level.

Beau spoke of his discussion with Thomas on backporting 2.2 patches for Message Center to 2.1.x instances. May get patches from Seth Theriault/Columbia. Note: Lydia/Stanford pointed out code location for question pool performance issues to Thomas. Thomas or Jon may work on the Samigo patches.

Beau organising tool list in Confluence, required vs. want, for roll out determination and determination of what optional tools will be released for fall; requested contribution/feedback from rest of group. If tools are not mature enough, more damage possible with release of ineffective or poorly performing tools.