Follow-Up of #43 - the Abstract user model needs a simple way to retrieve user objects

Description / Overview

Users should not relate to multiple user models (Student, Reviewer, Tutor) and the user that is associated with a request.user should be retrieved easily and without pain (no userInGroup blabla).

It is up to the person who implements this if they propose a way that allows superusers to change their roles within the interface and thereby providing a simpler way for developers to test different users.

Links / references

• Django auth docs

Feature checklist

• The user object of HTTP requests in views can be easily distinguished. E.g. model contains info about group and associated pages.
• DB constraints for UserAccount and UserModel (one Model per User policy with exception of the superuser)

changed milestone to %Computer Science I & C programming exam (Mock exams)

added Needs assignment label

added priority:high label

The DB constraints are important and the implementation effort should not be too high. Would be nice to see this closed soon.

One way to resolve this would be to degrade the Student model to a StudentInformation model and only use it for that purpose.

The users groups could be distinguished by a choice field on the UserAccount model.

mentioned in issue #68 (closed)

marked the checklist item The user object of HTTP requests in views can be easily distinguished. E.g. model contains info about group and associated pages. as completed

marked the checklist item DB constraints for UserAccount and UserModel (one Model per User policy with exception of the superuser) as completed

closed