increase performance for SCORM 1.2 by changing manner of storing data

1 Requirements

Actually there are restrictions for improving performance for SCORM 1.2 learning modules resulting on the manner of storing data in the table scorm_tracking. In addition reporting is made more difficult.
Goal of this feature is to store data similar to SCORM 2004 with several tables without making an insert/update for each SCORM value. It might be useful to store detailled data for interactions or objectives as JSON objects.

2 Additional Information

• Idea / concept: Uwe Kohnle
• Funding: Required
• Maintainer: Uwe Kohnle
• Development: Feature is to be developed by Uwe Kohnle, Internetlehrer GmbH
• Testing: tbd

3 Discussion

Uwe Kohnle: 26 May 2014: I support this request and recommend its implementation for 4.5.

JF 7 Jul 2014: We support this improvements and schedule it for 4.5.

Matthias Kunkel, March 19, 2015: This feature was already scheduled for 5.0 but not implemented due to missing funding / time. There is still a need for this feature. Therefore I have re-scheduled it for 5.1 to save time for discussing new feature requests. Nevertheless, funding is still needed to make this feature go into the 5.1 version.

4 Implementation