Meeting Notes November 29, 2006
Attending:
Donnelly, Herspring, Pumphrey, Jackson, Niedfeldt, Perl, Hightower, Schlender, Pence, Delker, Nielsen, DeVault, Morse, Crow
Mike Crow provided an update.
- Testing is proceeding, learning HOW system will work instead of worrying about will it work!
 - System has great flexibility, which is both good and bad. Although there is lots of documentation, there are not templates. We can do more ourselves – also good and bad news.
 - Probably will not be a lot of policy changes, but lots of process changes.
 - Prerequisites: entry will be “different” but seems to be more intuitive than OSS.
 - Demonstrations are planned for December 14 or 21, 10:00-11:15 am at Union to introduce how prerequisite entry will go, followed by “hands-on” training in late January in Fairchild Hall computer lab.
 - Course schedule development will be different, with direct entry (by DO? Depts?) instead of passing green bar sheets back and forth.
 - Communication continues to be essential and challenging.
 - Issues:
 - Conversion
 - Resources
 - Technical modifications. “DARS is a big challenge,” especially related to use of transfer courses to meet prerequisites.
 - Timeline:
 - Late January: re-acclimate; systems installed on office computers
 - Start entering prerequisites late Jan and Feb
 - When satisfied, tell tech people to “freeze” the group to go to production
 - Push hard to complete in February (delay can be accommodated, but results in pile-up as work continues to move on)
 - March – April: begin discussion of processes (see handout)
 - Glossary (a work in progress) is on SAMBA drive or laser.ksu.edu>project team site>studentfunctional>glossary
 - INTENSE work March to June (includes dept level training)
 - 4-5 volunteers will be needed in mid-spring to provide DO view of processes
 
- Concerns
 - Adding courses not currently in F/S/U course schedules (CS-1?)
 - Visibility of course location in course schedule as students schedule courses
 - Using consistent terminology for tools (catalog, course schedule) and processes – which may be different from current usage.
 - Scheduling graduate credit and undergraduate credit courses for an individual student – will require student to have both “Graduate Career” and “Undergraduate Career”
 - Who will update DCE courses? (Currently done by DCE, not Colleges.)
 - Access questions yet to be answered (e.g, exceptions to prerequisites, additions to closed classes, backdates – what will be accessible at faculty, department, dean’s office levels?) Clarifying impact of exceptions (e.g., exception to allow student to enroll without PR may result in overenrollment in a closed section)