Forum Discussion
web publishing and bookmarking
Hi RachelDavis-7dd it sounds like your courses are currently using cookies to track. These, as you are finding, are localised to a computer, and not associated with a login on the LMS. If you want to use SCORM 1.2 tracking, and ensure that the tracking data is being sent to the Xyleme LMS, then you will need to publish the content as SCORM 1.2 for the LMS and select the required tracking/completion from the publish settings.
What I can tell you, is that it is very uncomment for Storyline to have an issue with tracking on an LMS. I've deployed to many LMS (SCORM 1.2 and SCORM 2004) and there are generally not any issues. The only issues you might find occasionally is SCORM 2004 and changes needed to the manifest document.
As an LMS provider, the default stance can be to point the finger at the content.
What I would recommend is:
- Ensure the content is published as SCORM 1.2
- Ensure the content is imported in Xyleme LMS as a SCORM 1.2 package
- Confirm that the content is accessed through a unique login/password for each user (this is required to associate the data with an individual user on the LMS).
- Enable SCORM debugging window in your Storyline files
- Locate the file named scormdriver.js
- Edit the following (line:99)
FROM
var SHOW_DEBUG_ON_LAUNCH = false;
TO
var SHOW_DEBUG_ON_LAUNCH = true;
Enabling the SCORM debugging window will launch a pop-up window and will show all of the SCORM communications taking place between the content and the LMS. The most important being, finding the API and running the LMSIinitialize("") method successfully.
Here's what it looks like when it successfully finds the API:
Wed Nov 27 2024 09:57:03 GMT+1100 (Australian Eastern Daylight Time) - SCORM_GrabAPI, returning
Wed Nov 27 2024 09:57:03 GMT+1100 (Australian Eastern Daylight Time) - Calling LMSInit
And the kind of message you will see when it fails to find the API:
Wed Nov 27 2024 09:59:01 GMT+1100 (Australian Eastern Daylight Time) - Unable to acquire SCORM API:
Wed Nov 27 2024 09:59:01 GMT+1100 (Australian Eastern Daylight Time) - SCORM_objAPI=object
Wed Nov 27 2024 09:59:01 GMT+1100 (Australian Eastern Daylight Time) - In InitializeExecuted, blnSuccess=false, strErrorMessage=Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.
Wed Nov 27 2024 09:59:01 GMT+1100 (Australian Eastern Daylight Time) - ERROR - LMS Initialize Failed
Wed Nov 27 2024 09:59:01 GMT+1100 (Australian Eastern Daylight Time) - In DisplayError, strMessage=Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.
Thanks SamHill for the response. I do agree, publishing as SCORM 1.2 or SCORM 2004 would solve our bookmarking issues. However, due to our current eLearning course delivery ecosystem, that is not an option. Our LMS is built internally and depends on the Xyleme LCMS to deliver content packaged as one file. This is why we are needing to use Xyleme to combine our Storyline modules into one course. At this point, what I need is a way to setup Storyline such that the bookmarking within the web publishing works as well as the bookmarking within SCORM. I realize that this is not a usual ask and may not even be possible but I've committed to doing the research.
- SamHill24 days agoSuper Hero
I'm afraid there are not any simple solutions. You would need to contact your CMS provider. You need to store user tracking data in a database so that it can be persisted between sessions. This is what SCORM provides. Without SCORM, you do not have interoperability and would require a custom solution to be developed for your content.