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

SCORM 2004 objectives report status field always empty

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.3
    • Fix Version/s: 2.4
    • Component/s: SCORM
    • Labels:
    • Testing Instructions:
      Hide

      Create a SCORM package using the attached zip
      enter the scorm as a student and answer some questions.
      Check the interactions report to see if it displays a valid status for the entries in the objectives table.

      Show
      Create a SCORM package using the attached zip enter the scorm as a student and answer some questions. Check the interactions report to see if it displays a valid status for the entries in the objectives table.
    • Affected Branches:
      MOODLE_22_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE
    • Pull Master Branch:
      MDL-33702-master

      Description

      In SCORM 1.2 the status of an objective comes from cmi.objectives.n.status. In SCORM 2004 this was split into cmi.objectives.n.success_status and cmi.objectives.n.completion_status, with cmi.objectives.n.progress_measure a useful normalised value.

      The /mod/scorm/userreport.php page currently creates an HTML table for objectives with columns 'identifier', 'status', 'raw', 'min' and 'max'. It seems strange for the raw value to come before the min and max bounds, rather than in between.

      The status column is populated only from the SCORM 1.2 data model location. There needs to be added consideration for SCORM 2004 so that something suitable gets displayed in this column. Perhaps the progress_measure as a percentage could be used until success_status is known? e.g. "Unattempted" > "25% done" > "Passed/Failed", with fallback to completion_status if those properties are undefined.

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  3/Dec/12