SCORM 1.2 player in the Mobile app: Difference between revisions
Juan Leyva (talk | contribs) No edit summary |
|||
| Line 8: | Line 8: | ||
}} | }} | ||
== Introduction == | '''== Introduction ==''' | ||
SCORM module support in the mobile app is one of the most requested features by users, specifically, the ability to play SCORM packages offline in the mobile app including synchronization of the tracking data once the device is online again. | |||
In this document we are going to do a brief analysis about what will be needed to implement in both the Mobile app and Moodle code to add support to play SCORM packages. | |||
'''Moodle Mobile''' | |||
The current Moodle Mobile app is an HTML 5 application that uses other common web technologies. It is a client application that uses REST protocol web services to send and get information from the Moodle installation. | |||
Recently, we have started working on another version of this Moodle Mobile app using Ionic framework with AngularJs to overcome the current mobile application’s technical problems. | |||
'''What is SCORM?''' | |||
SCORM stands for Sharable Content Object Reference Model. It is a common standard introduced by Advanced Distributed Learning. Those standards facilitate the use of SCORM based content in any management system without any hassle. | |||
SCORM consists of two main parts: Run Time Environment and Content Aggregation Model. | |||
''Run Time Environment'' | |||
This describes how the content of the SCORM package should behave when it is loaded by a learning management instance. In this project, we will mainly tackle this section. The run time environment consists of 8 main functions that facilitates the access to the LMS. | |||
''Content Aggregation Model'' | |||
This describes how a person who is creating SCORM packages should package that content according to the SCORM standards. | |||
The 8 main functions in the run time environment need to be implemented as a Javascript API. Since we are doing this project using AngularJs, this should be done by fixing it to an Angular Module. This Angular module will have all the necessary controllers and services to handle communication between an external SCORM package and the Moodle site. | |||
'''Functionalities''' | |||
The minimum functionalities to be supported would be: | |||
Support for SCORM 1.2 packages only | |||
Support for zip SCORM packages only (no alternative methods for adding SCORM contents) | |||
Complete support for the SCORM 1.2 API runtime | |||
Support for playing packages offline | |||
== Technical Overview == | == Technical Overview == | ||
Revision as of 15:51, 25 May 2015
| SCORM 1.2 player in the Mobile app | |
|---|---|
| Project state | In Progress |
| Tracker issue | https://tracker.moodle.org/browse/MOBILE-938 |
| Discussion | {{{discussion}}} |
| Assignee | Harindu Chathuranga korala |
== Introduction ==
SCORM module support in the mobile app is one of the most requested features by users, specifically, the ability to play SCORM packages offline in the mobile app including synchronization of the tracking data once the device is online again.
In this document we are going to do a brief analysis about what will be needed to implement in both the Mobile app and Moodle code to add support to play SCORM packages.
Moodle Mobile
The current Moodle Mobile app is an HTML 5 application that uses other common web technologies. It is a client application that uses REST protocol web services to send and get information from the Moodle installation. Recently, we have started working on another version of this Moodle Mobile app using Ionic framework with AngularJs to overcome the current mobile application’s technical problems.
What is SCORM?
SCORM stands for Sharable Content Object Reference Model. It is a common standard introduced by Advanced Distributed Learning. Those standards facilitate the use of SCORM based content in any management system without any hassle. SCORM consists of two main parts: Run Time Environment and Content Aggregation Model.
Run Time Environment
This describes how the content of the SCORM package should behave when it is loaded by a learning management instance. In this project, we will mainly tackle this section. The run time environment consists of 8 main functions that facilitates the access to the LMS.
Content Aggregation Model
This describes how a person who is creating SCORM packages should package that content according to the SCORM standards.
The 8 main functions in the run time environment need to be implemented as a Javascript API. Since we are doing this project using AngularJs, this should be done by fixing it to an Angular Module. This Angular module will have all the necessary controllers and services to handle communication between an external SCORM package and the Moodle site.
Functionalities
The minimum functionalities to be supported would be:
Support for SCORM 1.2 packages only Support for zip SCORM packages only (no alternative methods for adding SCORM contents) Complete support for the SCORM 1.2 API runtime Support for playing packages offline
