OK – it’s time to get started. I’m going to set a few ground rules to bound the problem a little better.
- I’m going to limit the investigation to SCORM 1.2. There’s not many people using versions of SCORM earlier than 1.2, and SCORM 2004 is a lot more complicated. But, if I can figure out SCORM 1.2, that should be a good stepping stone if I choose to go further.
- Rather than build it into a real LMS, I’m going to mimic the LMS side of things with some simple PHP coding, and use a MySQL database to store the data.
That’s it. I’ll let you know if I can think of any more.
Pingback: Desarrollando un LMS(con soporte de SCORM)
Gee, Tony, did you wake up on the wrong side of the bed this morning? You are a voice of crehey optimism with this post ;). Seriously, not that I don’t agree with a lot of what you say, but mobile has taken a big step this year. I may be an optimist, but having been on the stump (along with others) for quite a while, it really feels like the interest has firmed up. That doesn’t necessarily mean things will become concrete this coming year, but there’re already a number of experiments, so I’m expecting many more, and success stories (which we’re already seeing).Also on serious games, if we can break the hype around the requirement for $2M budgets, and realize that meaningful outcomes can be generated by games with a budget of $200K, or even less, people don’t have to be sitting on the outside. It’s just that they have to penetrate the smokescreen by those who have a vested interest in such budgets…. And branching scenarios are a worthwhile approximation with much of the value for less of the investment (you too can do branching scenarios in your own home!).I agree with you on much (e.g. LMS), but I’d like to believe that there more reasons for optimism than I hear here.
I’m looking forward to learn about trnasporting custom data using SCORM API. My authoring tool is Adobe Captivate.