student data (eg, enrolment list) will be quite dynamic in the first few weeks of a course as students officially drop and add. As we are trying to communicate with identified students earlier in a semester and want to track that communication in preferably a single intervention log, how can we ensure that that intervention log persists while the "student data" changes?
We could use the "delete function" in the student view pane but this only allows for the removal of existing students within a unique Paper instance in SRES. It would be easiest to upload a new "student data" file but this would result in a new Paper and the intervention log for the overall course would be piecemeal because there are now multiple Paper instances for the same course.
student data (eg, enrolment list) will be quite dynamic in the first few weeks of a course as students officially drop and add. As we are trying to communicate with identified students earlier in a semester and want to track that communication in preferably a single intervention log, how can we ensure that that intervention log persists while the "student data" changes?
We could use the "delete function" in the student view pane but this only allows for the removal of existing students within a unique Paper instance in SRES. It would be easiest to upload a new "student data" file but this would result in a new Paper and the intervention log for the overall course would be piecemeal because there are now multiple Paper instances for the same course.
Any ideas?