...
As per the above diagram, End user will sync the assess events through api, which will update the database with computed values. The assessment data product which read data from the database and will generate the reports per batch and uploads to azure cloud storage.
API:
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
METHOD: POST
URI: /course/v1/assessment/update // End point
REQUEST: {
"id": "api.course.assessment.update",
"ver": "1.0",
"ets": 1566884714550, //Time stamp in ms
"request": [{
"batchId":"", // Batch Identifier - required
"courseId":"", // Course Identifier - required
"userId":"", // User Identifier - required
"attemptId":"", // Attempt Identifier - required
"contentId": "", // Content Identifier - required
"events": [{}] //ONLY ASSESS Events - required
},
...],
} |
Request Structure:
Events related to particular to batchId, courseId, userId, attemptId, contentId should be grouped together while calling this API.
attemptId: Should be generated from Hashing HASH(courseId, userId, contentId, batchId, ets)
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
{
"id":"api.course.assessment.update",
"ver":"1.0","ets":1566974765224,
"params":{err:err},
"responseCode":"SUCCESS"
} |
Disadvantages:
- Need to
validateandde-dupthe the events.
...