[Design] QuestionSet/Assessment score report
Introduction:
The user’s assessment is taken a score report for a question-set. The scores were calculated for question set/s and the latest attempted score was displayed as part of the report.
Overview:
However now that, a new content type called "Self-Assess” has been introduced, there are some minor changes to do as part of the report. The scores of “Question set” will no more be included as part of the Score report. Instead, the scores of content-type “Self-Assess” alone will be included as part of the Score report
As a State Admin, I would want to have access to scores of self-assessment/s of all users within a batch of a course, So that I can get some insights on the quality of the contents within a course.
Solution I:
Every question units having evaluation logic and plugin knows the question attempted or not. This data we are not sending as part of Telemetry.
After evaluation, there is a callback to the question-set plugin. so while returning data from question unit plugins will send attempted: true/false and questionId:"do_id" as part of the result. This data will carry to question-set and dispatch event to org.ekstep.questionset:summary.
So it will help to know the score report of the assessment.
Example:
Solution II:
As part of the question-set/assessment, we are generating the "ASSESS" telemetry event for all questions during the evaluation of the question. So each ASSESS event contains question params and resValues.
So looking into telemetry Assess event resValues empty or contains data in an array based on this data will consider Question attempted or skipped.
FTB | MCQ | MTF | Sequence | Reorder | |
---|---|---|---|---|---|
ASSESS Event resvalues | |||||
Solution III:
Based on Telemetry Response event. Currently, MCQ type of questions only generating a Response event.
If the response event generates so it is considered as an attempted question.
MCQ | FTB | MTF | Sequence | Reorder | |
---|---|---|---|---|---|
Response event |
Solution IV:
In questionSet when the user selects or filled the answer, we are preserving the answers for state management. So this data will store in evaluated result we call state data.
For example: MCQ: result:state:value => if attempted => selected option index
result:state:value=> if skipped => result:state:value: undefined
FTB: result:state:value => if attempted => array of answers (result:state:value['apple','mango'])
result:state:value=> if skipped => result:state:value:[]
reorder: result:state:value => if attempted => array of selected answers (result:state:value['apple','mango'])
result:state:value=> if skipped => result:state:value:[]
Evaluated result state object
MCQ | FTB | Reorder | Sequence | MTF | |
---|---|---|---|---|---|
Attempted | |||||
Skipped |