If your SIS is connected to your LMS/CMS, you expect your enrollments to synchronize, right?
Student drops Section 1, Student adds Section 2, expected behavior is clear: Student disappears from Gradebook in Section 1 as noted by Instructor, the Admin view of their enrollments updates to exclude Section 1 and include Section 2; Student no longer sees link to Section 1, but sees and able to access Section 2.
And this is by and large what we’ve seen this Fall semester. Except.
Except for Cross-lists.
(Who out there is really surprised? Plug for Product NG: We need cross-lists and we need them to work!)
If student drops out of a cross-listed section only to add its sister section, then what happens? Well, it should be the same thing, but it’s not.
Instead, the Admin View demonstrates that the student is no longer enrolled in the Crosslisted parent but STILL enrolled in the original child section. And therefore, because the enrollments ‘roll up,’ the student is ineligible for enrollment in the sister section (the system believes them to already be enrolled). The Instructor, who views the Parent Gradebook, doesn’t see the student enrolled in anything. The Student no longer has access to either section. Yuck.
And to make matters worse here at ND, where cross-lists are already everywhere, we also ‘supersection’ upon request and those teaching many sections of labs frequently supersection up to 40 sections! You can imagine what that crosslist looks like after add/drop!
To clean up, I’m wondering if I DARE rely on the underlying database structure which they claim (since Vista 3) reconnects a student’s data with the student if they re-enroll. In other words, can I delete all parent crosslist and child crosslist enrollments through the GUI, then resynchronize the enrollments from our SIS and have the students, their correct sections, AND all the work they’ve already done, be happily re-united?
Anyone care to offer an opinion?