Schema

Schema

Schema are required for back-end development. Here are the Schema that needs to be implemented. There's enough information given with every Schema.

User Schema:

• name: {String} requires user's name
• email: {String} requires user's email
• password: {String} auto generate password for the user
• phone: {Number} requires user's phone number
• socialProfile: {String} requires user's social profile
• motivation: {String} requires user's motivation to join AltCampus
• stage: {Number} stages will be recorded for tracking the user application

Note: name, email, phone, socialProfile and motivation are required Schema fields. Those can't be blank in first post request to the Schema.

Task Schema

HTML Object :

• startTime: {Date} captures task start time
• projectUrl: {String} requires user's project completion url
• submitTime: {Date} captures task submit time.
• score: {Number} stores the score given by mentor

Note: startTime is a required Schema fields.

Codewars Object

• username: {String} requires user's username of codewars profile
• startTime: {Date} captures task start time
• kataSolved: {Number} fetches the completed kata by the user
• submitTime: {Date} captures task submit time or auto time limit
• score: {Number} stores the score given by mentor

Note: username and startTime is a required Schema fields.

Question Schema

• question: {String} stores the question
• type: {String} stores the type of question either MCQ or Descriptive answer
• option: {Object} stores the a, b, c and d option of the MCQ if applies
• answers: {String} stores the descriptive answer by user
• points: {Number} stores the point rewarded by mentor
• isActive: {Boolean} stores the current status of the user

Note: Question, type and startTime are required Schema fields.