Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-36934

Remove selection-level feedback for distractors in matching questions to avoid loss of user data

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 11.4, 12.0, 19.0
    • Fix Version/s: 12.3
    • Labels:
    • 12 status:
      Merged
    • Previous Issue Keys:
      SAM-3387
    • Test Plan:
      Hide
      1. Create a quiz
      2. Add a 'matching' type question
      3. Create a new choice that is not a distractor; provide unique feedback for both correct and incorrect choices
      4. Create a new choice that is a distractor; provide unique feedback for both correct and incorrect choices
      5. Save the question
      6. Notice on the question preview UI that the feedback for the non distractor was saved and is displayed, but the feedback was not saved and is not displayed for the distractor

      After the fix, you should not be presented with the text areas to supply feedback for distractor choices, which prevents the opportunity for lost user data.

      Show
      Create a quiz Add a 'matching' type question Create a new choice that is not a distractor; provide unique feedback for both correct and incorrect choices Create a new choice that is a distractor; provide unique feedback for both correct and incorrect choices Save the question Notice on the question preview UI that the feedback for the non distractor was saved and is displayed, but the feedback was not saved and is not displayed for the distractor After the fix, you should not be presented with the text areas to supply feedback for distractor choices, which prevents the opportunity for lost user data.

      Description

      Selection-level feedback for distractor choices in matching questions currently does not work. You are provided the text area to enter feedback for both the correct and incorrect answers for distractors, but if you save the question and look at the resulting presentation of the question, you'll notice that the feedback you entered for the distractor is not present.

      The cause of this problem stems from a design decision in Samigo. Each choice for a matching question corresponds to an ItemTextIfc object, and each answer to the choices corresponds to an AnswerIfc object, except for distractors. In fact, the correct choice for a distractor does not have a corresponding AnswerIfc object, and all distractor "answers" are inferred on the fly in code where needed. Due to this decision, it becomes obvious why the feedback for the distractors isn't persisted: there's no object, or corresponding row(s) in the database to save the data to.

      Correcting this design would likely involve a lot of work and testing, and may have consequences on other types of questions as well. It would also have to be developed in a way that's backwards compatible, so that old questions with distractors in existing databases don't cause failures due to the missing backing data that newly created distractors would then have.

      The proposal here is to simply replace the text areas (and corresponding labels) for distractor choices (on the fly, client side), with a simple message indicating to the user that selection-level feedback is not available for distractor choices. This prevents the possibility of lost user data.

        Gliffy Diagrams

          Zeplin

            Attachments

            1. correctincorrectmatching.png
              correctincorrectmatching.png
              17 kB
            2. feedbackmissing.png
              feedbackmissing.png
              19 kB
            3. nofeedbackmessage.png
              nofeedbackmessage.png
              13 kB
            4. screenshot-1.png
              screenshot-1.png
              17 kB

              Issue Links

                Activity

                  People

                  Assignee:
                  bjones86 Brian Jones
                  Reporter:
                  bjones86 Brian Jones
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration