Question types for Siyavula assessments
Context
Siyavula would like to use the Wax question types in their workflow for creating questions.
Wax currently has 8 question types, these can be viewed at the Wax demo site: http://wax-demo.coko.foundation/
Terminology: Wax question type
is synonymous with Siyavula's response type
. This sheet maps Siyavula’s response types to existing question types in Wax, showing 4 possible question types that can be used:
- Fill in the gap
- Multiple choice question (single correct)
- Multiple choice question (multiple correct)
- Multiple dropdowns
Proposal
Siyavula and Coko will collaborate to create versions of these questions that are relevant to Siyavula's needs. Here's the rough plan:
- Coko provides the editor structure in HTML and JSON that ProseMirror expects (https://prosemirror.net/docs/ref/#model.Node) for Siyavula to transform their import XML structure
- Coko implements any Wax-specific design amendments to the question type. We’ll start with ‘Fill in the Gap’
- Coko creates a package for each question type for Siyavula use
- Siyavula implements any React-specific design amendments to the question type.
- Siyavula integrates Wax into their assessment application
- Siyavula imports the questions
- A user views the question and adds the
response type
andmodifier
values (when relevant) - Siyavula exports the questions
Once the Coko team has completed step one and two above, we should meet to confirm how each response type and its modifier is handled. For example: maths input requirements.
Design
The wireframe below shows how the the response type
and modifier
could be set after the question has been imported. See this sheet for Column A and B values
Wireframe 1: Fill in the gap question showing the amendments for Siyavula's needs
Wireframe 2: Fill in the gap question showing the section a user has made for both response type
and modifier
dropdowns
Implementation (if applicable)
[A description of the steps to implement the feature.]
Alternative approaches (if applicable)
[Include any alternatives to meet this use case.]
Open issues (if applicable)
[Links to and a discussion of related issues, if applicable.]