This release includes upgrades to inQuiry building block to function with the QuML 1.1 format. The changes are detailed out in the link . The V2 version of the components as it is known from release 6.0.0 will start working with QuML 1.1 format and hence the questions that previously exist in the system has to be migrated from QuML 1.0 to QuML 1.1 format. A one time migration activity needs to be done on the existing question / questionsets.
Following are the Planned Tickets of R 6.0.0
Sl.no
JIRA Id
Issue Type
Description
1
IQ-480
Minor-Enhancement
Integrate V2 player and Editor in the inQuiry Portal
2
IQ-469
Bug
User is able to see all the fields editable in review mode
3
IQ-468
Minor-Enhancement
Remove hard coding in the QuML Player
4
IQ-443
Minor-Enhancement
inQuiry Documentation
5
IQ-442
Minor-Enhancement
Integrate latest common form library in editor
6
IQ-421
Minor-Enhancement
Remove hard coding of content organisation and target frameworks to point to a specific framework
7
IQ-414
Minor-Enhancement
Editor/Player: Update the Node version from 14 to 16
8
IQ-413
Minor-Enhancement
Mark it video, PDF, and EPUB player as optional in the resource library
9
IQ-412
Minor-Enhancement
Integration of Editor and Player web component into inQuiry portal
10
IQ-411
Minor-Enhancement
Integration of QuML player web component into the sunbird resource library
11
IQ-410
Minor-Enhancement
Integration of QuML player web component into the editor
12
IQ-393
Minor-Enhancement
Error standardisation
13
IQ-385
Minor-Enhancement
inQuiry V2 API Implementation
14
IQ-378
Bug
Zoom icon and show answer button are overlapping for the subjective question with image
15
IQ-337
Bug
User is not able to send for review when reset the set max and warning timer for question set
16
IQ-297
Minor-Enhancement
Player changes to ensure QuML compliance
17
IQ-296
Minor-Enhancement
Editor changes to ensure QuML compliance
18
IQ-272
Minor-Enhancement
Inquiry - QuML Design Changes to ensure QuML complaince
19
IQ-148
Bug
Footer is not aligned Properly when console is open.
Release Tags:
Question Set Editor:
Tag: v6.0.0
Install: npm i @project-sunbird/sunbird-questionset-editor@6.0.0
Question Set Editor Web Component:
Tag: v2.0.0
Install: npm i @project-sunbird/sunbird-questionset-editor-web-component@2.0.0
Data type of showTimer is changes from string to boolean so form Config change is required for this field.
showFeedback
{ "code": "showFeedback", "name": "Show Feedback", "label": "Show Question Feedback", "placeholder": "Select Option", "description": "If feedback is selected, users are informed whether they have correctly answered question or not", "dataType": "boolean", "inputType": "checkbox", "editable": true, "required": false, "visible": true, "renderingHints": { "class": "sb-g-col-lg-1" } }
Data type of showFeedback is changes from string to boolean, so form Config change is required for this field.
showSolutions
{ "code": "showSolutions", "name": "Show Solution", "label": "Show Solution", "placeholder": "Select Option", "description": "If show solution is selected then solutions for each question will be shown to the user", "dataType": "boolean", "inputType": "checkbox", "editable": true, "required": false, "visible": true, "renderingHints": { "class": "sb-g-col-lg-1" } }
Data type of showSolutions is changed from string to boolean, so form Config change is required for this field.
warningTime
No Config for warning time.
This field is not needed in QuML 1.1 .Warning time will be handled by playerConfig.
bloomsLevel property is changed to complexityLevel and it's datatype is also changed from string to array so the config change is required for this field
QuML Player:
Tag: v6.0.0
Install: npm i @project-sunbird/sunbird-quml-player@6.0.0
QuML Player Web Component:
Tag: v2.0.0
Install: npm i @project-sunbird/sunbird-quml-player-web-component@2.0.0
Resource Library:
Tag: v6.0.0
Install: npm i @project-sunbird/sunbird-resource-library@6.0.0
ALTER TABLE {{ question_keyspace_name }}.question_data ADD (outcomeDeclaration text, feedback text);
Jenkins Job Changes:
Note:
1. For V2 API's, compatibilityLevel increased by 1. So for Question object, value is 5 and for Questionset object, value is 6. If any application consume data based on compatibilityLevel, it should make the the changes accordingly.
URL:
URL:
URL:
URL:
URL:
New Configuration Added:
Please Refer to
Note: V2 API need to be onboarded.
Ref:
Schema Should be Uploaded For Question & QuestionSet using
A New Jenkins Job Created For Kafka Topic Management. The job can be imported using
For Build, Upload, and Deploy operation of data-pipeline jobs, jenkins jobs are available for import