File:
[LON-CAPA] /
loncom /
html /
adm /
help /
tex /
Answer_Display_Overview.tex
Revision
1.4:
download - view:
text,
annotated -
select for diffs
Fri Oct 18 03:41:46 2013 UTC (10 years, 10 months ago) by
lira
Branches:
MAIN
CVS tags:
version_2_12_X,
version_2_11_X,
version_2_11_5_msu,
version_2_11_5,
version_2_11_4_uiuc,
version_2_11_4_msu,
version_2_11_4,
version_2_11_3_uiuc,
version_2_11_3_msu,
version_2_11_3,
version_2_11_2_uiuc,
version_2_11_2_msu,
version_2_11_2_educog,
version_2_11_2,
version_2_11_1,
version_2_11_0_RC3,
version_2_11_0_RC2,
version_2_11_0,
HEAD
add description of some additional tags helpful for displaying help and answers
1: \label{Answer_Display_Overview}
2: \index{answer display}
3: Several xml tags are available to provide student guidance during problem display
4: and also after the answer date. These include \texttt{<notsolved>}\index{notsolved},
5: \texttt{<preduedate>}\index{preduedate}, which are useful when the students are working
6: a problem, and \texttt{<solved>}\index{solved}, \texttt{<postanswerdate>}\index{postanswerdate},
7: which are helpful in providing feedback. The content in the xml tag \texttt{<postanswerdate>} is suppressed until after the answer date.
8:
9: Answers are typically not displayed to the student when they submit an answer to a problem,
10: unless their answer is correct.
11: When the problem is assigned in a course, a parameter for the `answer date' must be set such that students will see answers displayed when they revisit the problem after that date. The answer date is distinct from the due date which can also be set when a problem is assigned.
12:
13: Suppose you want the answer displayed as soon as the student finishes the problem rather than waiting until
14: the answer date. For example, this may occur in a multipoint problem where you
15: want the students to see the correct answer for one part before proceding to the next part. If you would like the
16: computer answer to be displayed after the student answer is correct, or the maximum number
17: of tries has been reached, this can be achieved by setting the parameter \texttt{problemstatus} = answer. Using
18: the colorful editor, the parameter can be inserted WITHIN the problem part, but BEFORE the response tag (e.g.
19: \texttt{numericalresponse}). For example:
20:
21: \begin{verbatim}
22: <part id="01">
23: <parameter name="problemstatus" id="11" type="string_problemstatus"
24: default="answer" description="Show Problem Status" />
25: <numericalresponse answer="$c" id="01a">
26: <!-- using no tolerance since exact integer is expected for answer -->
27: <textline readonly="no" spellcheck="none" />
28: </numericalresponse>
29: </part>
30: \end{verbatim}
31:
32: The options for the problemstatus are: ``yes'' - shows correct or incorrect only;
33: ``answer'' - shows computer answer as described above; ``no'' -
34: don't show correct/incorrect feedback; ``no\_feedback\_ever''- supresses all feedback.
35:
36: If you want to provide additional explanation in addition to the answer as soon as
37: the maximum tries allowed for the part have been reached, include a conditional
38: block in the problem part, and set the condition for the part to evaluate to
39: true when the problem is either correct, no tries remain, or it is post-answer date.
40:
41: To achieve this behavior, add a call to the LON-CAPA function \&check\_status(`partid')
42: for each part to the script block, and set a scalar to the value returned for each part, then use
43: that scalar in the conditional block, e.g.,
44:
45: \begin{verbatim}
46: <script type="loncapa/perl">
47: # for part: a
48: $status_a = &check_status('a');
49: # other computations
50: </script>
51:
52: <part id="a">
53: <block condition="$status_a">
54: <startouttext />
55: <br />
56: Some explanation text about the answer, $answer
57: <endouttext />
58: </block>
59: </part>
60: \end{verbatim}
61:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>