Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Data base structure

Jump to bottom
Cristian Gonzalez edited this page Mar 16, 2018 · 1 revision

Data Base structure

Next list are the collections present in the DB:

  • aggregations: This collection stores the users and users' groups which are registered in a course.
  • fs.chunks: Collection that stores files (presumably the submissions) in binary format.
  • fs.files: Stores the metadata of the files (maybe submissions). This metadata includes md5sum, upload Date, etc.
  • sessions: this collection the data associated to sessions (tokens, username, IP, among others).
  • submissions: this collection stores the submissions (except the binaries), and information related to the submissions such as: who did the submission, time of the submission, given result by the grader, among others.
  • system.indexes: list all the indexes in the database. (See: MongoDB system collections).
  • user_tasks: it stores the relation between users and tasks (it is duplicated because of mongoDB scheme). Each entry represents a pair (user, task) and the stored information is: given result, number of submissions the user has made, whether the user has passed or not the task, score, number of tries, etc.
  • user: information related to the user, his/her name, email, encrypted password, etc.
Clone this wiki locally