[ARCHIVED] SIS Rostering-How do you handle teachers leaving?

[bob_thomas]

This is our first year of rostering via Clever and our SIS (Aspen) in our K-12 district. Things have gone very well, but we've had issues when a teacher leaves. This fall we've had several teachers go on leave, or resign. Canvas admins are not always notified, and the change in the SIS leads to the teacher and the course being deleted. We can resurrect the course, retrieve grades and and cross list with the new course attached to the new teacher, but it's a tremendous amount of work. 

How do other schools deal with syncing-teacher-leaving issue? All suggestions are appreciated. 

[robotcars]

We do not use Clever, and just pull data from our SIS via SQL.

Our SIS endpoints are not constrained. Ie... if a teacher leaves, the course title which includes their name will change to include STAFF instead and their course enrollment is removed. The course is still active, and students are unaffected, and the teacher enrollment is 'vacant', waiting for a sub or staff to manage.

I think some real time/API happy Integrations like Clever move a little too fast and trying to make changes 'snappy'.

Because our Integration only pushes hourly, daily, and weekly, changing a teacher out would most likely be done in a few steps/minutes and the entire switch would be complete before the next set of queries and SIS Import. Thus, changing the teacher out or removing one does nothing.

Logically, it doesn't make sense to constrain a course to a teacher, enrollments are not permanent... but a course can survive multiple enrollment changes throughout a term.