Meeting Notes January 18, 2008- 1:30 P.M.

Next Meeting:

Wednesday, January 23 at 10:30 AM in 113 Seaton Hall

Attending:

Mike Crow (iSIS), Jennifer Gehrt (iSIS), Donnelly (AG), Tilford (AG), Pumphrey (AS), Cunningham (BA), Niedfeldt (BA), Murphy (ED), Larry Satzler (EN), Karen Pence (HE), David Delker (TC), Scott Schlender (GR), Linda Morse (DCE), Monty Nielsen (REG), Doris Carroll (FS/AAC), Al Cochran (PROV)

Meeting with Provost’s Staff (Jennifer Gehrt)

(See agenda from David Delker and the handout titled “iSIS – Dean’s Council – Jan 14, 2008)
Questions raised by Provost’s staff were brought to the Task Force for clarification.

• Why purge the waitlist after Day 7 of semester?
• Auto-enrollment from waitlist after Day 7 could ambush students, especially since there is no enrollment notification to students. They might not know they have been added to a class. They might no longer want the class and not realize they were still on the waitlist. Trying to catch up after being added late might jeopardize their academic performance.
• Current policy is that late enrollment in a course after Day 7 requires instructor’s permission.
• What will happen to those on the waitlist?
• A report listing class waitlist will be run before the purge. Departments and Dean’s Office can print the report for faculty who wish to use it to grant permission to enroll if space becomes available after Day 7.
• Since requisite enforcement in iSIS will vary by college and/or department, should a list of courses for which requisites are (or are not) enforced be published?
• How would this list be maintained and where would it be displayed?
• The Undergraduate Catalog lists REQ. REQ can be enforced electronically or by instructor. If REQ is not checked electronically, it may be enforced by the instructor, or not, as is current practice.
• If REQ is enforced electronically and student is denied enrollment, student can click “details” to determine why denied enrollment.
• If there is an error and student believes REQ has been completed or is in progress at a transfer school, who should the student contact? (Will be on website.)
• A student who does NOT have the REQ completed or in progress and wants an exception to allow enrollment would consult the instructor for consent/permission.

Shannon Pumphrey will distribute a list of AS departments with status of REQ enforcement.

iSIS Orientation Session at Teaching Retreat

Kudos to Jennifer and Brian Arthaud-Day for their presentation and Q&A session at the January 15 retreat. Following are some of the questions raised.

• Will the system help police student “no shows” to be administratively dropped for non-attendance?
• Can current practice be continued? (Send Enrollment Services a class roster with those to be dropped lined out.)
• What about students enrolled in distance learning classes?
• This issue needs further discussion.

Here is the policy from the University Handbook, section F64.
If an instructor recommends a reassignment, the student should confer with his/her advisor. An instructor may drop a student from any or all components (e.g., lecture, recitation, lab, etc.) of a course if the student is absent at the beginning of the first class period of any component of the course. Students who cannot be in attendance should arrange prior permission from the instructor in order to avoid being dropped. For purposes of this procedure, enrollment in and payment of fees for a course do not constitute sufficient notification of intent to take a course. No student may add a course after the first week of classes without the permission of the instructor.

• Where are all the “SRDI” screen items? Why can’t they be all in one place?
• Maybe there can be a one-page report. In the interim, use hot links, or put screens in “My Favorites.
• Access to ACT information is part of advisor role.
• Will transfer grades be on the KSU transcript? No.
• Will student’s subplan appear on the class roster? No, not yet.
• How will DARS “exceptions” (e.g., application of “unknown” courses) feed back into the iSIS requisite system? They won’t. Student will have to get permission every time an “unknown” course is used for the requisite.
• Will waitlisted courses block enrollment when there are time conflicts between waitlisted course and enrolled course? Yes, waitlisted course WILL block enrollment in conflicting course. What about associated classes? If student wants to keep LEC but change LAB, what happens? This needs to be tested. Currently, students are advised to add before dropping, but iSIS will require the opposite – drop before adding. If the course is closed with a waitlist, will dropping to change LAB time result in a waitlisted student moving into the course and blocking out the (formerly) enrolled student?

Jennifer has a list of about forty questions generated at the retreat and will post responses.

iSIS Help

Mike Crow will provide a contact list of iSIS, Registrar and technical staff.

Mike Crow’s List

• DeptViewSchedule will be posted February 22.
• REQ Enforcement. Shannon will provide list of AS departments enforcing REQ electronically and those enforcing REQ by hand.
• Instructor/Advisor Table needs to be kept updated. Will migrate report and attach to role. Everyone who has a department will have instructor role.
• Advisor Role. Only those who have advisor role will do advisor security form. Be sure to check the Advisor box in order to assign advisees. Checking this box does NOT give advisor access, but allows assignment of advisees. The advisor security form has to be completed for advisor access.
• Dept Head Schedule View/Dean roles also will have advisor role.
• Class Schedule. A “post-op” review will be held at the end of the month. Sharon Hauck will notify departments when room assignments have been made.
• Enrollment Requisites.
• Everything approved has been moved out of CS1 to iSIS, then to CS2.
• REQ are not yet attached to courses – will be done March 2.
• Approvals now need to be done in CS2. Mike will send out link for CS2 (7042) testing for F08.
• 1000 students will be available for DARS/REQ testing. We can see transfer work in iSIS but cannot run audits.
• Program/Plan Changes.
• Some errors are coming up on the “compare” report (iSIS compared to SIS). A graduate student is identifying which are conversion errors and which are operator errors.
• New form was distributed. Discard old “Curriculum Change” forms and use new ones. More are available from Registrar’s Office.
• iSIS Student Schedule Request form was distributed. Review and send feedback to gunile@ksu.edu
• Backdated drops: cannot drop with effective date before actual date of enrollment. Who will identify date of enrollment? This may cause problems with error corrections. More research is needed. Withdrawal from the university is “different.”
• Load Testing. First run – no assessment yet – just getting started. Problems occurred at 1250 concurrent enrollments, however, typically no more than 250 concurrent enrollments occur.
• Slow Search Problem for plan changes – they’re working on a fix.
• Reserve Capacities – contact Mike if you have questions.
• Requisite Edit Check List is on SAMBA. An update will be posted, and also posted on iSIS help site.
• Grades will be discussed in detail in upcoming two weeks.
• A/Pass/F. The problem of A/Pass/F grading option being identified on the grade roster will be fixed.
• Annual Advising Survey will be available in October with S09 enrollment.
• Academic Forgiveness Policy. Steve the consultant will work on implementing this new policy.
• Drop/Adds. Adds through Day 21? Drops through Day 68? (Clarification needed.)
• Pilot Enrollment. Be sure to distribute plan to advisers. Question: can pilot be expanded to include student workers in college offices? Yes. Mike will send out form to identify participants. N = 10 per college.

Date and Time for Next Meeting.

Wednesday, January 23, 2008, 10:30 a.m., Seaton 113.