We’ve managed to get the bugs in SCORM down to 17 issues! 7 are related to SCORM 2004, 6 are feature requests, and the remaining issues have a low impact for people using SCORM!

This past couple of weeks the following issues have been resolved:
MDL-17115 – Improved API check, which greatly improves the speed in which a SCORM object loads/performs for a user.
MDL-16651 – ability to delete SCORM responses
MDL-12588 – Restrict SCORM module availability via time/date duration (only in 2.0)
MDL-17034 – Update Frequency not enforced
MDL-11908 – allow skip content page with Multiple SCOS
MDL-11501 – improved control over SCORM content (2.0 only)
MDL-16123 – improved method of accessing external scorm objects via proxy

A couple of other small ones have been fixed too!

Of the remaining issues, MDL-16184 is probably the highest priority, then there’s all the SCORM 2004 work that needs to be done. We really need to put together a costing/quote to get the SCORM 2004 stuff finished so we can raise some $$ to continue to work solidly on SCORM

I’ve been impressed with the number of people helping out in the SCORM forum on moodle.org recently! Thanks to everyone who has helped in the forums and in the Bug Tracker! There also seems to be a decline in the number of people asking for help using older versions of Moodle which is great! – I’ve tried to improve a lot of the SCORM Docs/Faqs to help with this as well.

Tags: Moodle, SCORM

This entry was posted on Sunday, December 7th, 2008 at 11:04 pm and is filed under Moodle, SCORM. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.