Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-31611

SCORM: user results get "lost" when two (or more) users are doing a SCORM test at the same time

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.9.16, 2.2
    • Fix Version/s: 2.6
    • Component/s: SCORM
    • Environment:
      Any
    • Database:
      Any
    • Testing Instructions:
      Hide

      You need 2 different browsers for this, and 2 student accounts.

      1. set 'Auto-update frequency' for the scorm activity to 'every time it's used'
      2. on browser#1 log in as user#1 and start the scorm activity.
      3. check the scorm_scoes_track table that the first entries for this attempt have been recorded
      4. on browser#2 log in als user#2 and start the same scorm activity
      5. check the scorm_scoes_track table. You'll notice that all existing entries for user#1 have been updated to a new scoid value
      6. continue in the browser for user#1, finish and close the scorm-activity.
      7. check scorm_scoes_track again. all entries made after user#2 has started the scorm will have an outdated scoid. I.e. the scoid that was current when user#1 started the scorm session. You'll see a result that is very similar to the image Bas Brands has posted in http://moodle.org/mod/forum/discuss.php?d=173471#p845325
      Show
      You need 2 different browsers for this, and 2 student accounts. set 'Auto-update frequency' for the scorm activity to 'every time it's used' on browser#1 log in as user#1 and start the scorm activity. check the scorm_scoes_track table that the first entries for this attempt have been recorded on browser#2 log in als user#2 and start the same scorm activity check the scorm_scoes_track table. You'll notice that all existing entries for user#1 have been updated to a new scoid value continue in the browser for user#1, finish and close the scorm-activity. check scorm_scoes_track again. all entries made after user#2 has started the scorm will have an outdated scoid. I.e. the scoid that was current when user#1 started the scorm session. You'll see a result that is very similar to the image Bas Brands has posted in http://moodle.org/mod/forum/discuss.php?d=173471#p845325
    • Workaround:
      Hide

      set 'Auto-update frequency' to 'never' or 'every day'

      Show
      set 'Auto-update frequency' to 'never' or 'every day'
    • Affected Branches:
      MOODLE_19_STABLE, MOODLE_22_STABLE
    • Fixed Branches:
      MOODLE_26_STABLE

      Description

      Situation:
      Occasionally, a student finishes a scorm activity successfully but in gradebook the grade turns out to be set to 0.0.

      Occurrence:
      It turns out that this will happen when

      1. The setting 'Auto-update frequency' for the scorm instance is set to 'every time it's used'
      2. A second user opens the same scorm activity while the first user is still using it

      After finishing the scorm the grade for the first user will be set to 0.0 regardless of the actual grade passed by the scorm

      Analysis
      when 'Auto-update frequency' is set to 'every time it's used', the scorm player in Moodle will update scoid values in the scorm_scoes and scorm_scoes_track tables every time a user opens the activity.

      1. user#1 starts the scorm, scoids get updated to scold#1
      2. user#2 starts the scorm a little later and all scoids get updated to scoid#2 including all entries already in scorm_scoes_track for user#1
      3. user#1 continues but all new entries in scorm_scoes_track for this scorm session will still have the value for scoid set to the original scold#1

      Result of all this is that only the steps user#1 has done before user#2 started will be considered when user#1 is graded. Later steps stored in scorm_scoes_track have an outdated scoid and will be ignored. Effectively, user#1 ends up with an incomplete attempt.

      Refer to forum post: http://moodle.org/mod/forum/discuss.php?d=173471#p845325 for an illustration

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Votes:
                  3 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    18/Nov/13