You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Judges and supervisors can be the same person though they must have different roles for different projects. They can be either internal lecturers or external to the school.
Consider this example:
Lecturer A is supervisor for project 1and judge for project 2 and 3.
Professor B (external) is supervisor for project 3 and judge for project 2.
Lecturer C is judge for project 1, but wasn't invited as supervisor.
Employer D (external) is supervisor for project 3 but wasn't invited as judge.
Current design didn't even take into account for the judges.
I am thinking of a different registration scheme:
The admin is responsible for creating accounts, not users
Upon creation, an account should have roles as a list.
The academic assistants (or admin?) will assign these roles to respective persons only if they assume it.
In projects there is a field judge
In the example above: A and B both have roles ['supervisor', 'judge'] while C and D have only either of them.
The text was updated successfully, but these errors were encountered:
Judges and supervisors can be the same person though they must have different roles for different projects. They can be either internal lecturers or external to the school.
Consider this example:
Current design didn't even take into account for the judges.
I am thinking of a different registration scheme:
judge
In the example above: A and B both have roles
['supervisor', 'judge']
while C and D have only either of them.The text was updated successfully, but these errors were encountered: