Course restarts learner from beginning and doesn't resume from last point reached

[Former Member]

Hello,

We are experiencing difficulty with externally-developed courses that have been produced in accordance with SCORMv1.2 standard. The issue is that for this particular vendor, none of these courses (SCOs) are correctly resuming the learner at the last place visited in the course.

According to SCORM standards and the Run-Time Environment data model, both the RTE and a SCO rely on the data model for functionality. Values for the data model elements are set and retrieved by SCOs via the RTE API's SetValue() and GetValue() functions.  The SetValue function allows the SCO to transfer to the LMS the value of the data model elements that it is capturing. The GetValue function requests information from the LMS.

For these problem courses, the value for data element “cmi.core.entry” for each attempt at the course is reset to “ab-initio” (from the beginning) instead of “resume.”   This leads me to believe that either the course isn’t setting it correctly, or the value coming back from the LMS is being corrupted in the API. I don't believe the LMS (ANY LMS actually) has the capacity to write/change this data. It just stores what's been sent.

Two things I've already tried:
- activated the CPCFG JSAPI switch in config (=X) which is used to activate the JavaScript implementation of the SCORM API. Basis team restarted the J2EE, but this had no impact
- within the LSOAE for this particular course, selected "content uses the SCORM interface" which sets a related data model element (cmi.core.lesson_status). If this switch is set, then the LSOCP expects the content to set this datamodel element. Again, no impact

I will have Basis run a trace to see what if anything can be discovered within the API.

Does anyone have any ideas about what’s wrong?  The vendor claims that the issue is within our LMS, which I am trying to discount.

Thank you,

Connie

[Former Member · Accepted solution]

We learned that the problem was indeed with the vendor. They corrected their code and the issue was resolved.