backend
backend copied to clipboard
Backend of Source Academy @ NUS, LMS extension of Source Academy (Elixir, Ecto, Phoenix, PostgreSQL)
## Unattempted questions in submissions should be marked graded Request to update existing auto-submission feature. ### Current behaviour When an assessment closes, the backend auto-submits all student submissions, and inserts...
Where models have foreign keys that cannot be null, the tables should have appropriate constraints and changesets should also validate this with `Ecto.Changeset.foreign_key_constraint/3`. See [here](https://elixirforum.com/t/ecto-association-vs-foreign-key-constraints/2387/2) for difference with `Ecto.Changeset.assoc_constraint/3`. Todo:...
To properly decouple cadet from the grader I propose moving to a managed queue on AWS.
Refactor to use `on_refresh` callback in the authentication code as well
Just to log the issue down first. The current pipeline: - Submission does not exist - Student submits at least 1 answer, submission is created, marked as `attempting` - Student...
Some simple validation on the import script especially on the nusnetid would be super useful and nice!
Current: A grading job takes in a student's submission, and for each answer forks a task to AWS Lambda for grading. Does not return any status. Proposed: A grading job...
Currently, features such as grading and chatkit need a student/group assignment, which is uploaded as part of the deployment process. Ideally, the only place where groups are needed is for...
For a student, if an assessment has answers that are null (i.e., nothing saved for these answers), `POST /assessment/{id}/submit` responds with status code 400. I think this is good behaviour,...