Dashboard > SCORM 2004 > 2008 > February > 15 > Problem persisting data between sessions in a SCORM 2004 course
  SCORM 2004 Log In   View a printable version of the current page.  
  Problem persisting data between sessions in a SCORM 2004 course
Added by Anonymous, last edited by Anonymous on Feb 15, 2008
Labels: 
(None)

Hi, we are trying to persist data between sessions in a SCORM 2004 course hosted on an Icodeon server

When we save any data, say to suspend data, it stores it OK. However, when I run the course again by running a SCORM Initialize from the HTML body tag, all the existing stored data seems to disappear?

This means I cannot retrieve any stored VLE data as it does not exist any more so I cannot persist data between sessions? This means that users can store data whilst using the course but cannot retrieve saved data when they leave a course and go back to it some days later as all the data is deleted when the new course is run i.e. when the "inititalize"  call is made to the SCORM VLE.

I am not really sure what is happening here as all of this works fine on our local Moodle VLE?

I wondered if there is a setting in Icodeon that has been set/not been set that automatically deletes the stored SCORM data when a course is run again?

FYI I used the SCORM 2004 detective supplied on the install using the default settings and there is a similar problem with suspend data not being able to be retrieved on subsequent visits to this course. 

I noticed there is a config file where you can change the data persistence settings and whether to store the data in a database or in XML. I thought there might be a setting here for persisting data between sessions which might help with my problem? Or do I need to chage my manifest SCORM calls and /or manisfest XML file in some way?

Thanks in advance for any information on this.

Thank you for your post.

Icodeon will need a little more detail to from you to process this support request. Please advise:

(a) which organization/vendor you are representing

(b) SCORM Player Version (either Version 1 or Version 2)

(c) Java Edition or .NET Edition

Looking forward to your comments.

Posted by Icodeon Customer Support at Feb 15, 2008 10:40; last updated at Feb 15, 2008 13:25

Hi, we are developing the resources using a third party host, I have asked them for the details you require. Unfortunately we cannot make changes to the Icodeon player directly, I just need to know to find out if it is an issue with our packages or a setting that the host can change?

Posted by Anonymous at Feb 15, 2008 14:02

Thank you for that - please advise when you have details on those three points.

In the meantime, without further details that might suggest something more specific, the obvious thing to check is that the correct "exit" data model value is being set.

To persist data between sessions (such as the suspend data) it is necessary to set the "exit" data model value to "suspend". According to the SCORM documentation:

If the cmi.exit is set to 'suspend' then the SCOs current learner attempt does
not end. The SCOs Run-Time Environment data model element values for the
current learner session will be available to the SCO if the SCO is relaunched in a
subsequent learner session.

So, for SCORM 2004, you will need to first set the suspend data, then the "exit" data model, and then terminate the session:

SetValue("cmi.suspend_data","my data to be persisted")

SetValue("cmi.exit","suspend") 

Terminate("") 

Please confirm that the "exit" data model value is being set to "suspend".

Please also advise the other details. Thank you.


Comments? 

Hi, I am not using SetValue("cmi.exit","suspend") , I will give this a try, it certainly sounds very promising  

FYI I am simply using Terminate("") which seems to work in Moodle.

I will try this out.

 Thank you very much for your help so far!

Posted by Anonymous at Feb 15, 2008 14:47

Thanks for the update. Please advise the result, as well as the details from your provider, when available.

Also note that SCORM 2004 is more "precise" that the more "loosely" defined SCORM 1.2.

SCORM 1.2 would persist data between sessions even though the "exit" was not set to "suspend".

In SCORM 2004 you will need to explicitly indicate that the state needs to be persisted between sessions with the "exit" set to "suspend".

Comments? 

Hi, thanks you for this info. I have just had chance to try this out, I added this to the body tag in the index.html page:
onUnload="doSetValue('cmi.exit','suspend'); doCommit();doTerminate();"

FYI I added in the commit as a failsafe just in case.

I tested this in Moodle and Rustici TestTrack just to check that the cmi.exit was being set and it seems that cmi.exit is being set to suspend OK.

In the Icodeon player the suspend data persists during a browser session, however when I close the browser and re-open the browser and log back in suspend data is no longer available?

I also noticed that  the "Resume with the activity I last worked with." is greyed out as well, I wonder if this option needs to be activated by the host?

BTW the host in question have not given me the technical details you requested, so I cannot provide this as yet

Thanks again for any help on this. 

Posted by Anonymous at Feb 21, 2008 10:26

The comment

"Resume with the activity I last worked with." is greyed out

Indicates that you are using SCORM Player Version 1. All vendors are currently being advised to upgrade to Version 2 which has been through much wider content testing, as well as the standard SCORM conformance tests. This issue is most likely to be resolved when your provider deploys SCORM Player Version 2.

Comments? 

Ah Ok thanks again BTW I have just got the player info from the host:

SCORM Player Version 1 - Java Edition

Posted by Anonymous at Feb 21, 2008 15:30
February 2008
Sun Mon Tue Wed Thu Fri Sat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29  

Icodeon SCORM Player .NET Edition 2.05 Released
SCORM Content Development Tools

Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.2 Build:#807 May 20, 2007) - Bug/feature request - Contact Administrators