-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to Drop Students who drop via bCourses #58
Comments
Need to do import strategy feature When importing, allow user to specify different import strategies. mainly, two points of ambiguity:
I must have seen a well-defined set of importing strategies somewhere (like "overwrite", "integrate" etc). I shouldn't come up with this myself, which will probably turn out inferior. |
I think what probably makes sense if that if there are no prefs, we just update the student attributes. I don't know about righty specifically what makes sense.
This depends. For gradescope, Canvas sync removes people who came over via Canvas -- e.g. we track if they have a valid canvas ID. Largely this sounds like we might need to improve the import students follow:
These could apply whether canvas or CSV imports. The last two options should probably require the user approving a warning... There is a bonus here -- which I don't know how useful it is, but we can maybe consider only removing seats if the added constrains result in a guaranteed failed match. (e.g. you add a 'lefty' constraint to a student assigned in a righty seat...) |
Yes I am working on something like that |
if a student is removed from the bCourses roster, they should be removed from the seating tool
The text was updated successfully, but these errors were encountered: