[QTI] different feedbacks for different attempts

Pierre Gorissen P.Gorissen at fontys.nl
Tue Mar 7 18:51:53 GMT 2006
Previous message: [QTI] 2.0 / 2.1 Content
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Turadg,

No, having that buildin responseVariable wouldn't make the solution simpler. 
The reason for that is that you cant use numAttempts as an identifier so the 
response processing would be very similar to the example I posted.

numAttempts makes life simpler if for example you want the score for a 
correct answer dependent from the number of attempts (you don't have to 
provide the response processing code to keep track of that) and in the 
result reporting, where not being dependent of the item designer to provide 
that value makes life easier.

Pierre

----- Original Message ----- 
From: "Turadg Aleahmad" <turadg at berkeley.edu>
To: "IMS Question &amp; Test Interoperability" <ims-qti at lists.ucles.org.uk>
Sent: Tuesday, March 07, 2006 1:59 AM
Subject: Re: [QTI] different feedbacks for different attempts


> Pierre, I have a need similar to Mark's and your solution is very helpful. 
> I'm wondering: would an equivalent solution be simpler in QTI 2.1?  I see 
> that it has added a "numAttempts" attribute to itemSession.
>
>  http://www.imsglobal.org/question/qtiv2p1pd/imsqti_infov2p1pd.html
>
>
> -Turadg
>
>
> Pierre Gorissen wrote:
>> Hi Mark,
>>
>> I used the feedback.xml example that is provided with the QTI 2.0 set to 
>> create an adaptive feedback example that shows different modal feedback 
>> for each attempt and also provides the candidate with feedback if he/she 
>> chooses an answer option for the second time.
>>
>> I hope this answers your question, if not let me know.
>>
>> Pierre Gorissen
>>
>> p.s. there should be an xml file attached to this message, I hope it 
>> doesn't get filtered out along the way.
>>
>> ----- Original Message ----- From: "Mark B_" <markb_email at yahoo.de>
>> To: <ims-qti at lists.ucles.org.uk>
>> Sent: Friday, March 03, 2006 10:54 AM
>> Subject: [QTI] different feedbacks for different attempts
>>
>>
>>> Hi!
>>>
>>>  Is it possible to use different feedbacks for different attempts in QTI 
>>> v2.1?
>>>
>>>  For example in the first attempt the feedback "Please try it again" 
>>> should be shown and in the third and last attempt the feedback should 
>>> be: "No, that was not correct".
>>>
>>>  I assume it must be done with ResponseProcessing, but I didn't find a 
>>> variable counting the attempts.
>>>
>>>  Thanks
>>>  Mark
>>>
>>>
>>> ---------------------------------
>>> Telefonieren Sie ohne weitere Kosten mit Ihren Freunden von PC zu PC!
>>> Jetzt Yahoo! Messenger installieren!
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>
>>> _______________________________________________
>>> IMS-QTI mailing list
>>> IMS-QTI at lists.ucles.org.uk
>>> http://lists.ucles.org.uk/lists/listinfo/ims-qti
>>>
>>
>>
>> ----------------------------------------------------------------
>> Op deze e-mail zijn de volgende voorwaarden van toepassing:
>>
>> http://www.fontys.nl/disclaimer
>>
>> The above disclaimer applies to this e-mail message.
>> ----------------------------------------------------------------
>> ------------------------------------------------------------------------
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <assessmentItem xmlns="http://www.imsglobal.org/xsd/imsqti_v2p1" 
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>> xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqti_v2p1 
>> imsqti_v2p1.xsd" identifier="feedbackAdaptive" title="Mexican President 
>> with adaptive feedback" adaptive="true" timeDependent="false">
>> <responseDeclaration identifier="RESPONSE" cardinality="single" 
>> baseType="identifier">
>> <correctResponse>
>> <value>MGH001C</value>
>> </correctResponse>
>> </responseDeclaration>
>> <outcomeDeclaration identifier="ATTEMPTS" cardinality="single" 
>> baseType="identifier">
>> <defaultValue>
>> <value>start</value>
>> </defaultValue>
>> </outcomeDeclaration>
>> <outcomeDeclaration identifier="PREVIOUSRESPONSES" cardinality="multiple" 
>> baseType="identifier"/>
>> <outcomeDeclaration identifier="SCORE" cardinality="single" 
>> baseType="float"/>
>> <outcomeDeclaration identifier="FEEDBACK" cardinality="multiple" 
>> baseType="identifier"/>
>> <itemBody>
>> <choiceInteraction responseIdentifier="RESPONSE" shuffle="false" 
>> maxChoices="1">
>> <prompt>Who is the President of Mexico?</prompt>
>> <simpleChoice identifier="MGH001A"> George W Bush <feedbackInline 
>> outcomeIdentifier="FEEDBACK" identifier="MGH001A" showHide="show">No, he 
>> is the
>>                     President of the USA.</feedbackInline>
>> </simpleChoice>
>> <simpleChoice identifier="MGH001B"> Tony Blair <feedbackInline 
>> outcomeIdentifier="FEEDBACK" identifier="MGH001B" showHide="show">No, he 
>> is the
>>                     Prime Minister of England.</feedbackInline>
>> </simpleChoice>
>> <simpleChoice identifier="MGH001C"> Vicente Fox <feedbackInline 
>> outcomeIdentifier="FEEDBACK" identifier="MGH001C" 
>> showHide="show">Yes.</feedbackInline>
>> </simpleChoice>
>> <simpleChoice identifier="MGH001D"> Ariel Sharon <feedbackInline 
>> outcomeIdentifier="FEEDBACK" identifier="MGH001D" showHide="show">No, he 
>> is the
>>                     Prime Minister of Israel.</feedbackInline>
>> </simpleChoice>
>> </choiceInteraction>
>> <feedbackBlock outcomeIdentifier="FEEDBACK" showHide="show" 
>> identifier="again">
>> <p>You already tried that option!</p>
>> </feedbackBlock>
>> </itemBody>
>> <responseProcessing>
>> <setOutcomeValue identifier="completion_status">
>> <baseValue baseType="identifier">incomplete</baseValue>
>> </setOutcomeValue>
>> <responseCondition>
>> <responseIf>
>> <match>
>> <variable identifier="ATTEMPTS"/>
>> <baseValue baseType="identifier">start</baseValue>
>> </match>
>> <setOutcomeValue identifier="ATTEMPTS">
>> <baseValue baseType="identifier">firstAttempt</baseValue>
>> </setOutcomeValue>
>> </responseIf>
>> <responseElseIf>
>> <match>
>> <variable identifier="ATTEMPTS"/>
>> <baseValue baseType="identifier">firstAttempt</baseValue>
>> </match>
>> <setOutcomeValue identifier="ATTEMPTS">
>> <baseValue baseType="identifier">secondAttempt</baseValue>
>> </setOutcomeValue>
>> </responseElseIf>
>> <responseElseIf>
>> <match>
>> <variable identifier="ATTEMPTS"/>
>> <baseValue baseType="identifier">secondAttempt</baseValue>
>> </match>
>> <setOutcomeValue identifier="ATTEMPTS">
>> <baseValue baseType="identifier">thirdAttempt</baseValue>
>> </setOutcomeValue>
>> </responseElseIf>
>> <responseElse>
>> <setOutcomeValue identifier="ATTEMPTS">
>> <baseValue baseType="identifier">finalAttempt</baseValue>
>> </setOutcomeValue>
>> <setOutcomeValue identifier="completion_status">
>> <baseValue baseType="identifier">complete</baseValue>
>> </setOutcomeValue>
>> </responseElse>
>> </responseCondition>
>> <responseCondition>
>> <responseIf>
>> <match>
>> <variable identifier="RESPONSE"/>
>> <correct identifier="RESPONSE"/>
>> </match>
>> <setOutcomeValue identifier="SCORE">
>> <baseValue baseType="float">1</baseValue>
>> </setOutcomeValue>
>> <setOutcomeValue identifier="completion_status">
>> <baseValue baseType="identifier">complete</baseValue>
>> </setOutcomeValue>
>> <setOutcomeValue identifier="FEEDBACK">
>> <variable identifier="RESPONSE"/>
>> </setOutcomeValue>
>> </responseIf>
>> <responseElse>
>> <setOutcomeValue identifier="SCORE">
>> <baseValue baseType="float">0</baseValue>
>> </setOutcomeValue>
>> <setOutcomeValue identifier="FEEDBACK">
>> <multiple>
>> <variable identifier="ATTEMPTS"/>
>> <variable identifier="RESPONSE"/>
>> </multiple>
>> </setOutcomeValue>
>> </responseElse>
>> </responseCondition>
>> <responseCondition>
>> <responseIf>
>> <member>
>> <variable identifier="PREVIOUSRESPONSES"/>
>> <variable identifier="RESPONSE"/>
>> </member>
>> <setOutcomeValue identifier="FEEDBACK">
>> <multiple>
>> <variable identifier="FEEDBACK"/>
>> <baseValue baseType="identifier">again</baseValue>
>> </multiple>
>> </setOutcomeValue>
>> </responseIf>
>> <responseElse>
>> <setOutcomeValue identifier="PREVIOUSRESPONSES">
>> <multiple>
>> <variable identifier="PREVIOUSRESPONSES"/>
>> <variable identifier="RESPONSE"/>
>> </multiple>
>> </setOutcomeValue>
>> </responseElse>
>> </responseCondition>
>> </responseProcessing>
>> <modalFeedback outcomeIdentifier="FEEDBACK" identifier="MGH001C" 
>> showHide="show">Yes, that is correct.</modalFeedback>
>> <modalFeedback outcomeIdentifier="FEEDBACK" identifier="firstAttempt" 
>> showHide="show">No, that is not correct.</modalFeedback>
>> <modalFeedback outcomeIdentifier="FEEDBACK" identifier="secondAttempt" 
>> showHide="show">No, that is not correct.</modalFeedback>
>> <modalFeedback outcomeIdentifier="FEEDBACK" identifier="thirdAttempt" 
>> showHide="show">No, that is not correct, try one more 
>> time.</modalFeedback>
>> <modalFeedback outcomeIdentifier="FEEDBACK" identifier="finalAttempt" 
>> showHide="show">No, the correct answer is Vicente Fox.</modalFeedback>
>> </assessmentItem>
>>   ------------------------------------------------------------------------
>>
>> _______________________________________________
>> IMS-QTI mailing list
>> IMS-QTI at lists.ucles.org.uk
>> http://lists.ucles.org.uk/lists/listinfo/ims-qti
>>
>
>
> _______________________________________________
> IMS-QTI mailing list
> IMS-QTI at lists.ucles.org.uk
> http://lists.ucles.org.uk/lists/listinfo/ims-qti
> 


----------------------------------------------------------------
Op deze e-mail zijn de volgende voorwaarden van toepassing:

http://www.fontys.nl/disclaimer

The above disclaimer applies to this e-mail message.
----------------------------------------------------------------
Previous message: [QTI] 2.0 / 2.1 Content
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the IMS-QTI mailing list