...
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:
As part of 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 /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.
...
Expand | ||
---|---|---|
| ||
"edata": { |
...
title | Skipped question |
---|
...
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:
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
...
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 II:
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.
title | Attempted question |
---|
"eid": "RESPONSE",
"ets": 1571385741820,
"ver": "3.0",
"mid": "RESPONSE:c35bb556e3920e6a5b287ac699d96448",
"actor": {
"id": "874ed8a5-782e-4f6c-8f36-e0288455901e",
"type": "User"
},
"context": {
"channel": "b00bc992ef25f1a9a8d63291e20efc8d",
"pdata": {
"id": "dev.sunbird.portal",
"ver": "2.4.0",
"pid": "sunbird-portal.contenteditor.contentplayer"
},
"env": "contentplayer",
"sid": "nm-dQSSXROxfJpbONAmdXSmY_2ttSA6C",
"did": "d1b3344d6b8d8b5441c3b47842b61abd",
"cdata": [
{
"id": "f799686c9c913589cf270153edf8dbf6",
"type": "ContentSession
|
|
|
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 III:
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:[]
...
|
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 => array of selected answers 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:[]
Evaluated result state object
...
Solution IV:
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:
...
title | MCQ state data |
---|
...
language | js |
---|
...
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 |