23 March, 2011 · 1 minute to read
Relaxation of SCORM Criteria in SharePoint Learning Kit 1.6
I've just completed a couple of changes to SLK which although reported as bugs, were actually just rigidly enforcing the SCORM standard.
The first one was that you couldn't have a question where the question text is greater than 250 characters long. The question text gets stored in cmi.interactions.n.description so that when reviewing the results the context of the answer can be seen. However in the SCORM standard this value is limited to 250 characters. I must admit that the error message, while quite descriptive if you know the SCORM standard, wasn't very user friendly.
The second one was that you couldn't submit quizzes with a large number of questions. The reason here is that the questions and answers get stored in the cmi.suspend_data which in SCORM 2004 2nd Edition is limited to 4000 characters. This was actually masked by a bug where if the length of the data was greater than this, the error was ignored and the same page just displayed again.
Strictly speaking both of these problems are actually errors in the SCORM packages themselves as they are passing values which do not conform to the standards. There's even threads in the Articulate forums about it.
Normally, I'd be dead set against violating standards, however in these particular cases they are getting in the way of usability. So in these 2 specific cases I decided to relax the requirements and allow more data to be stored. Later versions of the SCORM standard do this for suspend_data anyway.
So in SLK 1.6, these restrictions have been relaxed.
Managing Director / Founder
Richard started SalamanderSoft in 2007 after a successful career as a software developer. Wanting to start his own company and with experience in integrating school systems he set out to build the best integration system for schools and to exceed customer expectations. He starting out on his own, doing all the coding, support and sales until finally the growing number of customers meant he needed to start growing the team. He is still heavily involved in coding the core Integration Suite product in addition to running the company and being the first point of contact for prospective customers.