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

SCORM - implement better sorting of scos

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 2.6
    • 2.6
    • SCORM
    • MOODLE_26_STABLE
    • MOODLE_26_STABLE
    • master_MDL-41434
    • Hide

      This can only be tested by someone who has access to view database tables.
      NOTE: the scorm packages provided here aren't very good and should only be used for testing the structure order of the scos - not for general user data etc.

      First Add "tu95bear.zip" as a new SCORM package to your course and take a look at the structure order of the scos so you know what you should expect.

      Next Add tu95bear_small.zip as a new SCORM package to your course. (not replacing the above package)
      Take a look at the database table

      {scorm_scoes} and look the id field of each of the scos added. (remember these somehow). This SCORM package has a smaller set of SCOS and misses the one titled "the fastest propeller driven..."

      Then update this"tu95bear_small.zip" SCORM package replacing it with the package "tu95bear.zip" and make sure the order of scos shown is the same as the first package you added earlier - the new sco "the fastest propeller driven" should not appear at the end of the list but in the same place as earlier.

      Then check the database table - the records in the {scorm_scoes}

      table for scos that existed in the tu95bear_small.zip should have the same id numbers as before and the new sco should be added at the end of the table somewhere (prior to this patch on every update to a SCORM pacakge the records in scorm_scoes would be deleted and recreated generating new ids for each record)

      The scorm_scoes table is the only one that updates with this patch - other tables will have data deleted and recreated.

      hopefully that makes sense - ping Dan M if you need help.

      Show
      This can only be tested by someone who has access to view database tables. NOTE: the scorm packages provided here aren't very good and should only be used for testing the structure order of the scos - not for general user data etc. First Add "tu95bear.zip" as a new SCORM package to your course and take a look at the structure order of the scos so you know what you should expect. Next Add tu95bear_small.zip as a new SCORM package to your course. (not replacing the above package) Take a look at the database table {scorm_scoes} and look the id field of each of the scos added. (remember these somehow). This SCORM package has a smaller set of SCOS and misses the one titled "the fastest propeller driven..." Then update this"tu95bear_small.zip" SCORM package replacing it with the package "tu95bear.zip" and make sure the order of scos shown is the same as the first package you added earlier - the new sco "the fastest propeller driven" should not appear at the end of the list but in the same place as earlier. Then check the database table - the records in the {scorm_scoes} table for scos that existed in the tu95bear_small.zip should have the same id numbers as before and the new sco should be added at the end of the table somewhere (prior to this patch on every update to a SCORM pacakge the records in scorm_scoes would be deleted and recreated generating new ids for each record) The scorm_scoes table is the only one that updates with this patch - other tables will have data deleted and recreated. hopefully that makes sense - ping Dan M if you need help.

      The order of records in the scorm_scoes table is used so each time we update a SCORM package we delete the existing data and recreate it - this can cause a range of different issues (see linked bugs)

      We should add a sortorder field to the scorm_scoes table and use this for the order of scoes instead of deleting/re-creating them.

            danmarsden Dan Marsden
            danmarsden Dan Marsden
            Sam Hemelryk Sam Hemelryk
            Frédéric Massart Frédéric Massart
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.