Forum Discussion
Test results response file
Hi ChristyDotson , assuming SCORM 1.2, the T/F style questions are most likely using the SCORM defined cmi.interactions “true-false”. This means that the (legal) responses expected by an LMS are either "0","1" or "t","f". It won't matter what the text labels are, as the LMS would accept them, therefore Storyline will be hardcoded to send either "t" or "f".
Multiple choice or "choice" legal characters are "0","9" or "a","z".
Reporting for SCORM 1.2 quizzes is pretty awful and has been very rarely used in my experience and would need an accompanying document (Q and A matrix) to make sense of the data stored in the LMS.
The most flexible response type in SCORM is the "fill-in", which allows a string of up to 255 characters.
I've never looked into this in Storyline, but when I used to hand build courses, I would program all questions to use "fill-in". To the user, the front-end may look like T/F or multi choice questions, but I would use the "fill-in" type so I could store more meaningful data for reporting.
SCORM 2004 improved allowing you to store more meaningful data in multi choice questions.
Thanks for the reply SamHill. I figured that the response file would still use the 't' or 'f' marker but find it odd that only the ones that I altered the screen text on seem to reporting back weird. Do you know, within the SCORM file packet, if there is an answer key that one could review to see if the answer is coded correctly? Or do most users just rely on the .story file and how it's built/responding visually in the editor?
Hi ChristyDotson I'm not sure I understand the question. The SCORM cmi.interactions that are used by Storyline are determined by the SCORM 1.2 and 2004 specification document. To ensure that content is interoperable between different LMS, the content must follow the specification. The question type used determines the data that is expected by the LMS. Deviating from the expected data will cause issues with the LMS. In order for content to be interoperable, it must follow the specification.
If you would like to deviate from the SCORM specification you would need to make edits to the JavaScript file "scormdriver.js" which handles the data transaction between LMS and content. You would need to intercept the Get and Set functions and make the appropriate changes.
Let me know if you have any further questions.
