You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/en/Authoring/index.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ A "question" is the basic object in the system. The following table shows the f
17
17
| [Inputs](Inputs/index.md) | The inputs are the things, such as form boxes, with which the student actually interacts.
18
18
| [Potential response trees](Potential_response_trees.md) | These are the algorithms which establish the mathematical properties of the students' answers and generate feedback.
19
19
| [Options](Question_options.md) | Many behaviours can be changed with the options.
20
+
| [Metadata](Metadata.md) | STACK questions support flexible metadata.
20
21
21
22
The authoring documentation also covers topics on:
Copy file name to clipboardExpand all lines: doc/en/Developer/Development_track.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ Issues with [github milestone 4.13.0](https://github.com/maths/moodle-qtype_stac
12
12
1. Remove all "cte" code from Maxima - mostly install.
13
13
2. Support for Maxima 5.47.0, 5.48.0, and 5.49.0. This includes a fix for issue #1281 from 5.48.0.
14
14
3. Question tests can now test the whole route through a PRT, rather than just the final node. This is a significant improvement on the ability to test questions. This is back-compatible with older questions.
15
+
4. Add in flexible [question metadata](../Authoring/Metadata.md). This fixes issue #1171.
Copy file name to clipboardExpand all lines: doc/en/Developer/Future_plans.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,7 +137,6 @@ Basic reports now work.
137
137
* Text based potential response trees (would allow for easier copying of complicated trees, etc).
138
138
* Changes to preset feedback to certain answer tests which might be more appropriate for different audiences. Could a 'simplified' English language pack allow for this (future changes might allow this to be done on a question-by-question basis).
139
139
* Check for potential issues with default correct/incorrect feedback for different languages (defaults can already be set on the server level by a Moodle administrator).
140
-
* Metadata on language for questions.
141
140
* Tools for language integrity (e.g. making it easier to identify what languages are in each question).
142
141
* Making sure Maxima knows the intended language (will allow for Maxima code to choose from the available languages).
143
142
* May want to have further discussions on how scores and penalties are handled (there is already a new feature in the latest version of STACK so that you can include functions in the "score" field.
Copy file name to clipboardExpand all lines: doc/en/STACK_question_admin/Authoring_workflow.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,11 @@ In theory one test case should be created for each anticipated response which ge
69
69
70
70
When updating a PRT at this stage we would _expect_ test cases added in step 2 to fail. This is reassuring as it indicates something significant has changed! You can easily confirm the new behaviour of the testcase is now what is intended.
71
71
72
-
### 6. Use data obtained from one cycle of attempts by students.
72
+
### 6. Add accurate metadata.
73
+
74
+
Check and add accurate [question metadata](../Authoring/Metadata.md).
75
+
76
+
### 7. Use data obtained from one cycle of attempts by students.
73
77
74
78
Rather than second-guess what students _might_ get wrong it is more effective to look at what they _do_. See the section on [reporting](Reporting.md) for documentation on how to review students' answers. When feedback/marks are delayed (e.g. online exam) this can be done between students taking the assessment and results being released. If feedback/marks are immediate then better quality feedback can still be usefully added later.
0 commit comments