VetMed Developers Meeting
Scott - Boot camp update and interaction with other Sakai personnel. New team member Philip attended BC.
Chris - Will finalize schedule info w/Scott and confirm Ilios curriculum content with Jan
Talked to Walter Boyce (participant in spring pilot) about possible concerns about online tools changing the teaching process, e.g., verbal announcements in class vs in Announcements. Some faculty may feel pressured to use Sakai rather than continuing with their existing teaching methods.
CALF and VM staff to continue to assure faculty that the intent is not "force" but to provide tools if desired.
Keith/Chris - Talked about supplemental db tables in Ilios for additional course information including syllabus info like maps, etc. Worst case scenario would be to convert to pdf and put in Resources so the information is available.
Beau - Troubleshooting VM implementation on new box - possibly available to team this afternoon as issues are resolved.
MyVM is unavailable - "page not found" experienced by other team members. Beau would like to be informed asap about outages to diagnose problems w/this server/app. Possible firewall issue?
Production for Spring 2006 will be on the new server - for Fall 2006 on multiple servers.
Keith - Working on session topics match up to offerings in Ilios. Figuring out the table structure for the 4 joins required.
Rick/Dave - Captivate & content migration: most is new content; re: Captivate N.O.
determined that MW will not meet VM deadline - Phase 1 involves having scripts drafted &
edited by April, so Rick/Dave will do it themselves 10-12 Captivate - spec'd for
podcasting, scripting and will record next week. Done in 2 weeks.
Movies will seat from media server and be linked, will migrate later to planned common
document location. Will note duration of each clip for faculty info.
Beau - content migration files stored in memory (system RAM) until actually completed
(during the upload) This an issue that needs to be solved due to file size issues of VM
content. 20 MB limit.
Model of students (student committee?) entering content for faculty on regular basis as
well, for quick materials uploads of individual courses. Faculty drop box with students
(premitted to do the work) will have access to - with auto-notification of students when
faculty upload content. Need to examine this concept in depth to determine best flow (i.e.,
global shared location, per course tool?)
Beau to provide options/scenarios to discuss w/Rick and Dave
*************************************************************************************
CERE Mtg
Beau getting new production machine configured
Keith extending Ilios to contain add'l course info like meeting times, etc.
Jan add'l content included (consistent) core class or not, clothing,
Chris - essential vs. required vs. optional db storage need
In 2 weeks will have 10-12 sakai help video files. as brief as possible for dwload purposes
and to minimize impact on faculty time noting length of video
IT timeline not compatible w/VM deadline, so Rick & Dave will do
Jan - upfront requirements for 2 pilot courses and student needs for spring qtr. Links from
course to point to CERE rather than iWeb. Email out to class to notify re: pilot and CERE.
W/ new system trying out Announcements tool will send email notification via this process
since students will be accessing CERE only for these classes. Limiting course home page in
iWeb to single link to sakai and other links in iWeb to course directly to sakai.
Erin, and other dept admins, will be part of the pilot as well since they also email
students via a class.
Sites up for spring and bulk enrollment is done.
Has data for email been entered? Erin has needs for early notification for course
information changes, e.g., location, schedule changes. Signing up for electives, other
things affected by changes. Issue is notifying the correct group of students.
Jan - what are the essential things students need to know?
Urgent current issues notification by email, but other information will be noted in
Announcements for the course.
Students can audit all courses - should they be able to self-join?
Discussions of multi-term displays for students and faculty (auto-joined courses)
How do you distinguish btwn Fall --> Winter esp. for multi-qtr courses
Term indicators? By color, by text designation? Uncouple once student has completed the
course, but allow student to be able to rejoin.
Instructor can override for their TA's, etc.
How far in advance do you set up future courses for joining for schedule changes, prior to
their actual enrollment in the course? Inform students that changes are possible to courses
prior to their enrollment (flux)
Potential issue for unjoining students - gradebook issues?
Global hide when course is over?
This is a good opportunity for faculty to sort through their content and limit what content
they want on their new sakai sites. Significant, but small percentage of faculty who go to
their online sites... send printed website snapshot and request designation of what
material they want on their new site. Default is no content.
Email notification (for fall) of faculty (cc: course leader) with deadline for response re:
course materials.
Notifications to instructors outside the school? Notify them as well (cross-listed?)
Course worksites generated require enrollment prior to being displayed (current business
rule) to avoid mass generation of sites; may need to change to allow early release and
allow students to join. Need for project sites outside the automated load, e.g., residency
courses.
Migrating content from the current system to the new system. Faculty to copy within sakai
for future site updates. May require simple training session.