Changes for page Variablen verwenden

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -8,7 +8,7 @@
8	8	* **{{id name="PostVariablen_en"/}}Post-processed variables**
9	9	Post-variables are only assigned after the task has been answered, submitted, and automatically assessed, thus allowing access to response-specific values such as the learner's response or the points for correct answers. In this way, adaptive feedback content, follow-up tests, and task series can be enabled. The use of conditions and MAXIMA statements allows responses from learners to be analysed and typical errors identified. Based on these insights, teachers will then be able to provide appropriate feedback or customised exercises.
10	10
11		-[[image:attach:Editor - Tab Variablen_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
	11	+[[image:attach:Editor - Tab Variablen_de.png]]
12	12	{{/layout-cell}}
13	13
14	14	{{layout-cell}}
...	...	@@ -17,9 +17,9 @@
17	17	{{/panel}}
18	18
19	19	{{panel borderColor="#ddd" bgColor="#f0f0f0" borderStyle="solid" title="Related topics"}}
20		-* [[Calculation interaction>>doc:ONYX.Erstellung von Testinhalten.Aufgabentypen.Berechnungsaufgabe.WebHome]]
21		-* [[Formula comparison>>doc:ONYX.Erstellung von Testinhalten.Aufgabentypen.Formelvergleich.WebHome]]
22		-* [[Expert assessment>>doc:ONYX.Erstellung von Testinhalten.Aufgaben.Bewertung festlegen.Expertenbewertung.WebHome]]
	20	+* [[Calculation interaction>>doc:ONYX.ONYX Editor.Aufgaben.Variablen verwenden.Berechnungsaufgabe]]
	21	+* [[Formula comparison>>doc:ONYX.ONYX Editor.Aufgaben.Variablen verwenden.Formelvergleich]]
	22	+* [[doc:ONYX.ONYX Editor.Aufgaben.Variablen verwenden.Expertenbewertung]]
23	23	{{/panel}}
24	24
25	25	{{panel borderColor="#ddd" bgColor="#f0f0f0" borderStyle="solid" title="Further information"}}
...	...	@@ -38,7 +38,7 @@
38	38	(% class="help-heading" %)
39	39	Define variables that are determined before the task is displayed in order to use (% style="background-color:#ffffff; font-size:14.0px" %)**random parameters**(%%) in your tasks. Variables are supported in ONYX for all types of tasks and offer various possibilities, especially for calculation interactions. With the help of variables, it is possible to create task templates which automatically allow (% style="background-color:#ffffff; font-size:14.0px" %)**an unlimited number of different test and exam attempts**(%%).
40	40
41		-(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size image-center-wrapper" %)[[image:attach:Testrun - Beispielaufgaben_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
	41	+(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size image-center-wrapper" %)[[image:attach:Testrun - Beispielaufgaben_de.png]]
42	42
43	43	{{info}}
44	44	For a typical application example for the use of variables as random parameters, see [[Example "Transport" - Use of random parameters>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.X||shape="rect"]].
...	...	@@ -48,7 +48,7 @@
48	48
49	49	Define variables that are determined after the submission of the task in order to create adaptive task and test scenarios. Post-processed variables (in short: post-variables) allow you to access the learners' answers and points achieved. You can use this information to enhance following content such as feedback or task descriptions of follow-up attempts. In addition, it is possible to intervene in the assessment and make subsequent changes to it.
50	50
51		-(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size image-center-wrapper" %)[[image:attach:Testrun - Nutzerlösung einer Beispielaufgabe_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="454" width="276"]][[image:attach:Testrun - Post-Variable im Feedback_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="454" width="313"]][[image:attach:Testrun - Post-Variable Lösungshinweis_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="280" width="327"]]
	51	+(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size image-center-wrapper" %)[[image:attach:Testrun - Nutzerlösung einer Beispielaufgabe_de.png]][[image:attach:Testrun - Post-Variable im Feedback_de.png]][[image:attach:Testrun - Post-Variable Lösungshinweis_de.png]]
52	52
53	53	{{info}}
54	54	The following examples for the use of post-processed variables show possible application scenarios:
...	...	@@ -56,7 +56,7 @@
56	56	* [[Example "Transport" - Adaptive task feedback>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.X||shape="rect"]]
57	57	* [[Example "Transport" - Points deduction per attempt>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.X||shape="rect"]]
58	58	* [[Example "Transport" - Assessment of the maximum score>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.X||shape="rect"]]
59		-* [[Expert assessment>>doc:ONYX.Erstellung von Testinhalten.Aufgaben.Bewertung festlegen.Expertenbewertung.WebHome]]
	59	+* [[doc:ONYX.ONYX Editor.Aufgaben.Variablen verwenden.Expertenbewertung]]
60	60	{{/info}}
61	61
62	62	== Definition of a variable ==
...	...	@@ -63,7 +63,7 @@
63	63
64	64	Click on **//Add new variable// **in the tab// **Variables** //to define a new variable. The new variable is immediately added and displayed in the overview table. Below the table, an edit window opens for the new variable. The order of the variables and conditions within the variables table can be easily changed using drag-and-drop.
65	65
66		-[[image:attach:Editor - Definition einer Variable_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
	66	+[[image:attach:Editor - Definition einer Variable_de.png]]
67	67
68	68	Assign a **unique variable name **for your variable. The variable name serves as an identifier and allows you to **use the variable in the task text**. Please make sure that the variable name does not contain any umlauts, special characters, and spaces. The input is case sensitive. If a variable is defined with the name "a", it can be accessed via the placeholder {a}.
69	69
...	...	@@ -90,7 +90,7 @@
90	90
91	91	In the example, the variables {VAR1}, {VAR2}, and {VAR3} were declared:
92	92
93		-[[image:attach:Beispiel zur Verwendung von Variablen_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="420" width="429"]]
	93	+[[image:attach:Beispiel zur Verwendung von Variablen_de.png]]
94	94
95	95	== Definition of a condition ==
96	96
...	...	@@ -98,17 +98,17 @@
98	98
99	99	Click on **//Add new condition// **to define a new condition. The new condition is immediately added and displayed in the overview table. Below the table, an edit window opens for the new condition. The order of the variables and conditions within the variables table can be easily changed using drag-and-drop.
100	100
101		-[[image:attach:Editor - Neue Bedinung anlegen_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
	101	+[[image:attach:Editor - Neue Bedinung anlegen_de.png]]
102	102
103	103	Variables can be compared with other variables of the same type or with fixed values. The comparison operators depend on the type of the variable. You can, for example, check whether values are equal to (=) or not equal to (!=) another value.
104	104
105		-[[image:attach:Editor - Vergleichsoperatoren_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
	105	+[[image:attach:Editor - Vergleichsoperatoren_de.png]]
106	106
107	107	Please note: A variable that is used within a condition must be initialised before the condition. The variable which is used in the condition or statement must be added as a single variable before the condition can be added. If the value of a variable is set within one or more conditions, it will be unnecessary to set a value for the variable itself. Select the empty entry from the value selection list.
108	108
109	109	**Link conditions:** If you have created several conditions for an IF section, you can configure how these entries will be linked. Determine whether all conditions (AND) or at least one condition (OR) must be met for the condition to be executed.
110	110
111		-(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" style="color:#ff6600" %)[[image:attach:Editor - Verknüpfung von Bedingungen_de.png||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" width="500"]]
	111	+(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" style="color:#ff6600" %)[[image:attach:Editor - Verknüpfung von Bedingungen_de.png]]
112	112
113	113	(% style="color:#333333" %)**Alternative conditions (ELSE IF): **(%%)You can add any number of alternative conditions (ELSE IF branches). Different variables can be set in the conditions. In the simple mode, only one variable can be set per condition. For more complex rules, you can switch to the **expert mode**. A more detailed description can be found in the help pages for the expert mode.
114	114
...	...	@@ -116,11 +116,11 @@
116	116
117	117	The variable representation in the test and task content is based on the principle of template declaration and the template processing of the [[IMS QTI 2.1 specification>>url:http://www.imsglobal.org/question/||shape="rect"]]. The template processing of IMS QTI 2.1 offers far more possibilities for setting variables, in particular by the nesting of logical expressions and conditions. The description entered in the expert mode is directly transferred into the XML of the task as a single template processing expression.
118	118
119		-[[image:attach:Editor - Variable im Expertenmodus_de.jpg||data-xwiki-image-style="img-screen" data-xwiki-image-style-border="true" height="490" width="411"]]
	119	+[[image:attach:Editor - Variable im Expertenmodus_de.jpg]]
120	120
121	121	Please note that after changing the description in the expert mode, there is no way to return to the simple mode.
122	122
123		-For further information on the XML definition of the template processing, please refer to the section [[IMS QTI 2.1 specification>>http://www.imsglobal.org/question/]]. The ONYX Testsuite already supports a wide set of IMS QTI expressions and possibilities. A detailed check to ensure correct functioning of the task template is nevertheless recommended when using the expert mode.
	123	+For further information on the XML definition of the template processing, please refer to the section [[IMS QTI 2.1>>url:http://www.imsglobal.org/question/||shape="rect"]] [[specification>>url:http://www.imsglobal.org/question/||shape="rect"]]. The ONYX Testsuite already supports a wide set of IMS QTI expressions and possibilities. A detailed check to ensure correct functioning of the task template is nevertheless recommended when using the expert mode.
124	124
125	125	== View variable assignment ==
126	126