This page contains details for the following EPICs
...
https://project-sunbird.atlassian.net/browse/SB-22717
Table of Contents |
---|
Question set details form driven by category configuration
Status | |
---|---|
colour | Green |
DONE |
Question Set details should be configurable such that it allows for flexibility yet does not burden the creator with plethora of details to be filled.
Each primary category form would define which of the behaviour configuration settings it wants to expose to the creators. For example, Practice would allow creators to modify only Shuffle, Show/hide Feedback, and Show x/y questions.
A primary category form would also define default values for the configuration settings. For example, Submit required = true for Assessment.
A primary category form would also dictate whether certain attribute is editable or viewable or hidden. For example,
Shuffle (default false, editable) for Practice,
Submit required (default true, viewable) for Assessment,
Scoring mode (default = no scoring, hidden) for Survey
So, a sample primary category form would be as follows:
Code Block |
---|
Practice
Shuffle: default false, editable
Submit required: hidden, no default (not applicable)
Show feedback: default true, viewable
Show solution: default true, hidden
... |
...
Question Set Creation Capabilities
Question details form driven by category configuration
...
→ Adding Images
→ Adding Audio
...
Create
...
Status | ||||
---|---|---|---|---|
|
Adding or Creating New question should allow creating question categories as specified in the category definition. For example, Assessment will not require Subjective Reference Questions
Conclusion: Editor allows configuring a list of allowed object types & primary categories for a collection / question set category.
Create hierarchy (Creating Sections)
...
case insensitive,
ignores more than one space,
allows all characters,
..
...
Tip |
---|
Completed in 3.6, 3.7 |
Question set details form driven by category configuration
Status | ||||
---|---|---|---|---|
|
Question Set details should be configurable such that it allows for flexibility yet does not burden the creator with plethora of details to be filled.
Each primary category form would define which of the behaviour configuration settings it wants to expose to the creators. For example, Practice would allow creators to modify only Shuffle, Show/hide Feedback, and Show x/y questions.
A primary category form would also define default values for the configuration settings. For example, Submit required = true for Assessment.
A primary category form would also dictate whether certain attribute is editable or viewable or hidden. For example,
Shuffle (default false, editable) for Practice,
Submit required (default true, viewable) for Assessment,
Scoring mode (default = no scoring, hidden) for Survey
So, a sample primary category form would be as follows:
Code Block |
---|
Practice
Shuffle: default false, editable
Submit required: hidden, no default (not applicable)
Show feedback: default true, viewable
Show solution: default true, hidden
... |
Add / Create New Question
Status | ||||
---|---|---|---|---|
|
Adding or Creating New question should allow creating question categories as specified in the category definition. For example, Assessment will not require Subjective Reference Questions
Conclusion: Editor allows configuring a list of allowed object types & primary categories for a collection / question set category.