Asked this question in the dev chat, Eloy responded with these comments:

it sounds to me I commented something like that with Dan and some of the tables were related with SCORM 2004 sequencing, that aren't in use yet. But scoes_data isn't part of them, if 'm not wrong.

And...

(I think that the scorm_scoes_data contains package information... and seems to be filled when the package is deployed, thing that would happen after restore the 1st time module is "used" ?)

We did try restoring the scorm and then attempting it and it didn't seem to populate the scorm_scoes_data table. Perhaps more testing is needed here?

Hi Mark,

looking back at the history of scorm_scoes_data it looks like Bobo added the table in Nov 2006, included backup code, but didn't do the restore code at the same time - I would assume that this is just a bug and not done intentionally. - interesting that no-one has noticed it till now!

feel free to attach a patch to fix - otherwise I'll try to get to it at some point in future!

thanks!

Hi Dan, are you able to commit some time to resolving this one? Mark has indicated that this is a priority for Moodlerooms.

Here is a patch file for 1.9.9+ for:

• /mod/scorm/restorelib.php

This adds a function to restore scorm_scoes associated scorm_scoes_data information.

These tracker issues may be related:

• MDL-21299: cmi.core.lesson_location incorrectly set upon exiting second attempt resulting in improper initilization on entry to third attempt
• http://tracker.moodle.org/browse/MDL-21306
• http://tracker.moodle.org/browse/MDL-21305

Slight modification to the conditional restore clause.

Hi Michael, thanks for the patch!

I'm reluctant to commit this before Eloys new restore code lands in HEAD - I don't want to cause any unnecessary conflicts with his incoming work. As soon as his changes go in, I'll make sure we rework this to work with the 2.0 restore and will push it in.

thanks,

caught up with Eloy today and he was happy for this to go in now rather than waiting for his upcoming changes in HEAD - thanks for the report Mark and for the patch Michael! - could you please QA the commit and post results here?

thanks,