-
-
Notifications
You must be signed in to change notification settings - Fork 71
Description
Feature Description
Hi Jonathan,
Thank you for continuing to invest your time and effort in this project, I'm sure it's helping countless applications. One thing I've noticed since upgrading to a later version is that validation has been added around the 'suspend_data' attribute of the SCORM specification. In SCORM 1.2, the spec states this supports a maximum of 4096 characters, however e-learning designers such as Articulate Storyline will chuck out values much greater when published to SCORM 1.2 (even with their built-in compression enabled).
Since updating scorm_again, some of our larger e-learning packages are presenting problems when users resume their previous progress. A workaround would be to republish the packages to SCORM 2004, which we are slowly starting to do in our organisation, but the sheer number of packages is making this a slow process.
I was wondering whether there is any scope to include a flag to disable the validation in scorm_again for the 'suspend_data' attribute, with validation being enabled by default? This would mean that by default the library stays true to the SCORM specification, but gives the flexibility for users who are upgrading from an earlier version. I apologise if this functionality is already included?