-
Notifications
You must be signed in to change notification settings - Fork 11
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
Sign up wizard for staff #55
Conversation
Nice - I want to eventually "break-up" unit offerings by teaching period too (if applicable to a unit..). See: #20 - basically, if a staff user created a unit for Semester 1 2015, they would need to create another module for Semester 1 2016 (since the data is linked to the same unit code). I still haven't thought of the best way to implement this given our current data model, but this is moving some way towards that :) |
… into registration-flow
@zwaters That makes sense. I think that in line with issues #31 and #51, all references to units should be done via the ID of the unit instead of the course code which would then allow multiple units with the same course code to work. Also, I think that non auto incrementing IDs could be a good thing to investigate so that the URIs for things are less predictable. |
Changes: