I am creating a custom LMS within our company that can handle SCORM 1.2 packages and tracking information. In the future this needs to be able to support TinCan API (xApi).I'm pretty new to working with products like these, however I've made headway and have the SCORM API endpoints in place and validated. Any information fed to the browser from a SCORM package is now collated and at the end of the package when the user finishes, it is sent to a PHP script.I've not been able to find much online at all about how one would go about storing SCORM data so with that in mind I thought about doing it the following way.Create a database which simply stores KEY=>VALUE pairs of all of that data. For example SCORM 1.2 sends data to the client scripts like cmi.interactions.n.result which tells the client script whether a user has answered a question successfully or not. As all of SCORM 1.2 data is sent this way I can easily create a table with data stored like:cmi.core.student_name              Joe Bloggscmi.interactions.1.result          wrongcmi.interactions.1.latency         00:00:02cmi.interactions.1.time            15:19:28Is this ill advised? Its easy to read out like this, easy to format and display to LMS administrators for tracking details.TinCan API is so vastly different to SCORM 1.2 is it possible to break it back down to key value pairs and rebuild the JSON objects if TinCan needs it back? and again, is this a bad way to store this information?
Creating an e-learning SCORM / Tin Can storage solution
data structures