Errors in reports.

Errors in reports.

by Sam Thing -
Number of replies: 2

Hi All,

We have a scorm package developed by an external provider with an assessment at the end.

The assessment is supposed to present the learner with 10 questions and pass them if they get 80% or more.

In practice the assessment can be "broken" by erratic user behaviour (logging in and out part way through, closing the browser window).

This "brokenness" consists of users being presented with more than 10 questions (over 130 in one instance), the assessment recording as passed with correct answers being below 80% and blank reports on moodle.

The failure rate of the assessment to work as it was designed is about 60%, which is unacceptably high.

For those of you that have experience of admining scorms, what is your experience of their reliability and accuracy in reporting in a Moodle environment?

Thanks, Sam.

Average of ratings: -
In reply to Sam Thing

Re: Errors in reports.

by Sam Thing -

Bump,

Someone must have experience in this area surely?

Average of ratings: -
In reply to Sam Thing

Re: Errors in reports.

by Matteo Scaramuccia -

Hi Sam,
the very first step is to activate the API logging to record how the Content reacts in terms of tracking calls in the different scenarios, including to look at the manifest file to see if a Mastery Score has been set there.

If the Content doesn't talk with Moodle, via the SCORM API, enough to track the relevant data, your reports will be blank in any LMS: the key point is to identify what the Content misses to tell about the User's experience and when. Then you can start looking at the JS code of your Content to address most of the problems, the why part of the game.
You can't be sure that Network and Session issues will be 100% under your control so expect at least a 2-5% of "strange" tracking situations, if you can't control OS, Browser, Network and Bandwidth of your Users.

HTH,
Matteo

Average of ratings: -