Page Comparison

...

Port the current implementation from Sunbird CB to Sunbird ED. This will allow Sunbird to play and track SCORM files and their completion.

SCORM file upload -

Create content API (api/v1/create/content or update) along with content metadata should store following values against the content

Code Block

'scormValues': {
'entry': <First SCO to be launched>,
'version': <scorm2004/SCORM_1.2- to decide which API to be used> 
'grademethod': <Grading method to give score to the user in case of multiple attempts>
}

Tables to be populated after reading imsmanifest.xml file. (here)

Code Block

onScormPackageUpload(zipPath) {
    if (!file_exists(zipPath . '/imsmanifest.xml')) {
        throw_error('uploaded zip is not a scorm file')
    } else {
        readIMSManifestFile(zipPath . '/imsmanifest.xml')
    }
}

function readIMSManifestFile($manifestfile) {
    1. Load and read the imsmanifest.xml file
    2. Things needed to be stored against the content
       a. scorm version -> Read the manifest->metadata->shemaversion
       b. The first sco to be set as 'entry' against the content 
    3. Poulate the #__scorm_scoes table and #__scorm_scoes_data after reading all the items and resources
}

Table #__scorm_scoes

id	bigint(10)	AUTO_INCREMENT
content_id	bigint(10)
title	varchar(255)
scormtype	varchar(5)
manifest	varchar(255)
organization	varchar(255)
parent	varchar(255)
identifier	varchar(255)
launch	longtext

Table #__scorm_scoes_data

id	bigint(10)	AUTO_INCREMENT
sco_id	bigint(10)
name	varchar(255)
value	longtext

SCORM consumption through player

Tracking user

Here for the first step we will store all the data provided by scorm in the database and use it for tracking completion and passing status of a student (populate scorm tracking tables given in here)

Generating telemetry

https://docs.google.com/spreadsheets/d/1krwjn8t7H5Y80EtHsCKrUBALk5qw5jjH28atG3QjXPk/edit#gid=1594049563

Do we want to support Attempts?

SCORM is designed to allow a student to exit and return at a later date to the same point they left from. This means that each time they enter the SCORM they are using the same single attempt. Some SCORM packages are intelligent about handling re-entry, many are not. What this means is that if the student re-enters an existing attempt, if the SCORM content does not have internal logic to avoid overwriting cmi.core.lesson_status and cmi.core.score.raw, they can be overwritten by a lower score, confusing the learner.

When a SCORM sets the cmi.core.lesson_status value to 'completed', 'passed' or 'failed' then we can allow the user to create a new attempt by adding a Start new attempt checkbox to the entry page. If cmi.core.lesson_status is set to 'incomplete', 'browsed' or 'notattempted' the student can only re-enter the existing attempt.

With this we can provide settings to allow this to be controlled, some of these settings can be hidden by default as advanced options.

Number of attempts

This allows the teacher to set how many SCORM attempts the student may create - this is not how many times a student can re-enter a SCORM attempt.

Attempts grading

This allows the teacher to set how multiple SCORM attempts(not re-entries) are graded. It is important to note that a 'failed' cmi.core_lesson_status allows a new attempt to be generated but the attempts grading setting "last completed attempt" only includes 'completed' and 'passed' values in it's calculations.

Display attempt status

This displays a users SCORM attempts and how their final grade is calculated on the SCO

Force completed

This is a setting that can be used to force a SCORM package to report a 'completed' cmi.core.lesson_status if it doesn't currently set the value.

Force new attempt

This hides the Start new attempt checkbox and will force a new attempt if the previous attempt has cmi.core.lesson_status value to 'completed', 'passed' or 'failed'

http://www.vsscorm.net/2010/01/20/a-simple-scorm-1-2-content-package/

...

Versions Compared

Old Version 2

New Version Current

Key