Skip to content
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

Design for judge/supervisor case #197

Open
Huy-Ngo opened this issue Jan 30, 2021 · 0 comments
Open

Design for judge/supervisor case #197

Huy-Ngo opened this issue Jan 30, 2021 · 0 comments

Comments

@Huy-Ngo
Copy link
Owner

Huy-Ngo commented Jan 30, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant