Awesome

Semester Statistics

Check the documentation for detailed Information.

The API is Live!

This is a project designed to give all the required details of a given VTU-College.

Assumptions:

These are some of the assumptions I will work with. They are not Subject to change much in the future. I may add some more Assumptions at a later date, but the current core assumptions will remain the same, Nothing will change, only added to.

• 2015 (CBCS) Onward Only. Anything before 2015 is automatically treated as Invalid.
  • While the database will accept the USN, note that undefined Behaviour might occur if wrong usns are Provided.
• Subject Details are Provided. This is Publically Provided. (Credits, (Minimum and Maximum) Internal Marks, etc) By the User of this API.
• Any Score Pertaining to a Subject not in the Database will be REJECTED.
• Any Score Pertaining to a Student not in the Database will be REJECTED
• Any Department Pertaining to a Score OR Student not in the Database will be REJECTED
• Any Student OR Subject Pertaining not pertaining to a Scheme will be REJECTED

Permanent API Routes:

New Routes will Be added as necessary, however, these are some of the permanent API Routes Available.

Their Internal Workings are Subject to Change and the Output to Each May Also change from Version to Version, but they remain of the same functionality.

• /batch/
  • GET​ /batch​/{batch}
  • GET /batch​/{batch}​/scores
  • GET /batch​/{batch}​/detained
  • GET /batch​/{batch}​/backlogs
  • GET /batch​/{batch}​/aggregate
• /dept/
  • GET /dept​/{dept}
  • PUT ​/dept​/{dept}
  • POST ​/dept​/
• /student/
  • GET /student​/{usn}
  • GET /student​/{usn}​/scores
  • GET /student​/{usn}​/backlogs
  • GET /student​/{usn}​/subject​/{subcode}
  • PUT /student​/{usn}
  • POST /student​/
• /bulk/
  • POST /bulk​/scores
  • POST /bulk​/dept
  • POST /bulk​/student
  • POST /bulk​/subject

Please take a look at the documentation for the same for detailed Information on how these routes work. (Do note that the documentation is not available for now, due to development reasons.)

Reports vs Reciepts:

• Reports: Stritly for Input and Internal Generation.

  • Internal Generation Models Only.
  • They are also Inputs for the API.

• Reciepts: Stricly for Output and Display.

  • Why? Simpler, Easier to Manage.
  • Conversion costs but Data Transmission is Easier.

There are Converters that translate from Report to Reciept.