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

SCORM - add Moodle logging for opening individual SCO

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.2, 2.2, 2.3
    • Fix Version/s: 2.2.1
    • Component/s: SCORM
    • Labels:
    • Environment:
      Linux Debian 2.6.32-5-amd64
    • Database:
      PostgreSQL
    • Testing Instructions:
      Hide

      With debugging level set lower than developer,
      Enter a SCORM package and launch any of the SCO's in the package - Check the live logs:
      /report/loglive/index.php

      Check to see if "launch" actions for each sco with the path to the sco in the details field are listed - previously these actions were only shown when developer level set.

      Show
      With debugging level set lower than developer, Enter a SCORM package and launch any of the SCO's in the package - Check the live logs: /report/loglive/index.php Check to see if "launch" actions for each sco with the path to the sco in the details field are listed - previously these actions were only shown when developer level set.
    • Difficulty:
      Easy
    • Affected Branches:
      MOODLE_20_STABLE, MOODLE_22_STABLE, MOODLE_23_STABLE
    • Fixed Branches:
      MOODLE_22_STABLE
    • Pull Master Branch:
      master_MDL-26974

      Description

      mdl_log table doesn't save the "launch" action for SCORM module.
      An example is if we want to see the report log live. We can see when an user enter in a SCORM, but in previous versions we could know when a user changed to section (in SCORM), but now this detail isn't. That's due to now in the database the "launch" action refered to SCORM isn't saved.

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  9/Jan/12