Forum Discussion
Hi Dana, the format of the timespan is correct as per the documentation for the SCORM 1.2 Run Time Environment. The data model element is required to use the CMITimespan, which is defined as follows:
A length of time in hours, minutes and seconds shown in the following numerical format: HHHH:MM:SS.SS
- Hours have a minimum of 2 digits and a maximum of 4 digits. (24 in your instance)
- Minutes shall consist of exactly 2 digits. (19 in your instance)
- Seconds shall contain 2 digits, with an optional decimal point and 1or2 additional digits. (i.e. 34.45). (20.97 in your instance)
The only thing I'm unsure about in your message, is you sat it is an "Upload issue". This is a run time element, and would not affect import into an LMS. It may throw an error when running on the LMS, but not when uploading. Usually when there is an upload error, this is due to a poorly formed or missing imsmanifest.xml file. I've sometimes experience import/upload issues due to a character in the manifest causing the LMS issues.
Also, this element cmi.core.total_time is read only. The LMS calculates this time based on a cmi.core.session_time that is written to the LMS from the content.
In terms of SCORM 1.2 compliance, I haven't experienced any issues with Storyline content. A good test case is to use the SCORM Cloud service, which is known to be one of the most compliant SCORM engines available and they offer a free account for testing your content. You can also access logs and provide these to the LMS provider so that you can prove the content is compliant and not throwing any errors on a compliant LMS.
Good luck.