When a Canvas course which is running te-canvas is duplicated, all its events will be copied over. But they will be unmanaged in the sense that there is no sync job keeping them up to date.
It is thus best to just delete all te-canvas events for copied courses.
This can be done manually right now by adding and deleting any TimeEdit object to the course via the te-canvas UI. We could add an explicit "Delete all" button, to make this easier.
Another approach (suggested by LU, this is how they solved it) would be to automate this – have a cronjob which e.g. once a day goes through all Canvas courses and looks for te-canvas events which do not have an associated "Connection" object in the database.
When a Canvas course which is running te-canvas is duplicated, all its events will be copied over. But they will be unmanaged in the sense that there is no sync job keeping them up to date.
It is thus best to just delete all te-canvas events for copied courses.
This can be done manually right now by adding and deleting any TimeEdit object to the course via the te-canvas UI. We could add an explicit "Delete all" button, to make this easier.
Another approach (suggested by LU, this is how they solved it) would be to automate this – have a cronjob which e.g. once a day goes through all Canvas courses and looks for te-canvas events which do not have an associated "Connection" object in the database.