xAPI: Profile SCORM

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ.

1 Initial Problem

The initial problem is being described by ADL (http://adlnet.github.io/xAPI-SCORM-Profile/dev/dual-track.html) as follows:
"
Dual Tracking uses the existing SCORM infrastructure to deliver content and both SCORM and xAPI to record the learner's progress.
ADL recognizes that many organizations already have an e-Learning infrastructure in place. The costs in building up those systems, experience, and content makes it cost prohibitive to make a complete switch to xAPI. But the Experience API was designed with the understanding that the API may be part of a larger system, such as an enterprise LMS. Also, the xAPI is effective as a stand-alone system to collect, and provide access to, learner experiences without the coupling to content required by SCORM LMSs. This first approach of leveraging the xAPI understands that organizations have a dependence on an LMS and offers a low-impact solution to xAPI adoption, with benefits such as:

• Current investments in SCORM are not lost.
• Content is still launched by the LMS.
• Learners' progress and status is still stored in the LMS.
• Minimal effort to begin using the xAPI. See below

2 Conceptual Summary

The key benefits for ILIAS users are that a smooth transition from SCORM to xAPI can take place and that data in the LRS is available tools specialized in Learning Analytics.
In the 'xAPI Learning Modules Object', the SCORM profile should be selectable in addition to the xAPI: Support of multiple Assignable Units.

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Kohnle, Uwe [ukohnle]
• Maintainer: Kohnle, Uwe [ukohnle]
• Implementation of the feature is done by: Kohnle, Uwe [ukohnle]

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.