Quote:
Originally Posted by beeneeb
Most LMS's have the ability to determine what should be done with the subsequent attempts. They can either accept each new attempt and overwrite the previous. They can accept each attempt and then average all of the attempts. They can accept only the first attempt and never allow subsequent attempts to be written. So, this is definitely something that should be handled on the LMS side.
|
Maybe I was not clear in my first explanation, or I'm missing something.... I'm realy confused... :S
I will try again.
From the "SCORM_RunTimeEnv.pdf" 3rd edition document:
The LMS is responsible for initializing the cmi.entry data model element based on the following rules:
o If this is the first learner session on a learner attempt, then the LMS shall set the cmi.entry to “ab-initio” upon initial launch of the SCO.
o If the learner attempt on the SCO is being resumed from a suspended learner session (cmi.exit was set to “suspend” or “logout”), then the LMS shall initialize this value to “resume”.
o If the previous learner session on the SCO ended due to a Suspend All Navigation Request triggered by the LMS, then the LMS shall initialize this value to “resume”.
o For all other conditions, the LMS shall set the cmi.entry to an empty characterstring (“”).
This is the behavior I'm describing (in my first post, the problem match with the second point here, the learner attempt is being resumed from a suspended learner session), I know some LMSs let you do other things, but I'm trying to make the basic behavior to work, and maybe later more advanced features.
I think the LMS is doing right, but, this is not working fine, so, I'm asking for some help because I can't see where is the problem.
BTW: Like Justin suggested, I asked a SCORM expert, I'm waiting the response....
Thanks
Javier