Quick notes from the meeting
- some Jira issues can be closed (Cheryl)
- Peter using Scheduler (feature not in baseline Sakai 2.0.0 m2) to schedule within-Sakai job for populating Sakai from Banner data.
- Peter needs list of desired default tool list (from Gloria)
- Forums tool - IFrame? Simple tool to JavaScript to open a new window pointing at forums.
- Need a CVS for our work (Peter) (Drew will do).
- Need to discuss details of course id format (Peter, Gloria, Cheryl) (term needs to be in identifier or else collision of names so that users get confused).
Browsing syllabi: generic text, generic HTML page, for a generic Classes site for classes that are in Sakai. Then students going to classes can find the site's "new" location in Sakai.
Problem: how do we know when to populate Classes with instructions to go to Sakai, given that Sakai site might not yet be available.
Question: is syllabus available even when site is not published?
Blanket rename of courses at end of term? So during a term a course has a short name, and then later it has an archival name?
Drew's gritty idea:
Really this /access/f05/cs110 Use apache to map this during the term: /access/cs110 And drop that mapping, perhaps replacing with this, after the term. /access/cs110_f05
Peter points out the bookmark problem with this idea.
Cheryl: Mike, please look for piece of code in how it decides what to display in Membership as joinable. Is it published and joinable and current term? Or just published and joinable? I.e., do we need to unjoinable or unpublish at end of term?
CLASSES: as of now students can only see courses from 05/06.
Photo roster? May just be in classes. Like registrar's roster. etc.
Goal was: Friday done with customization work (delay to Tue for course provider).
2 weeks for QA, moving to production box. Completes aug 15.
Machine room. Call machine room in outage. "Classes v2 is down." (We should look at the call sheet.)