Build vs Buy:
Advanced Distributed Learning actually has a certification
for Learning Management Platforms. Since this application programming interface is in beta, it has not been submitted for this.
that effort requires a 3rd party to review/analyze your software for roughly $4,000.
There are often several threads/posts online seeking a free SCORM Runtime API, and anyone who has done a bit of research has
probably hasn't found anything. This is because of a number of reasons.
- This can take a handful of developers up to 2 years to create
- Finding developers familiar with end-to-end SCORM
- The testing, support, and performance can cause many headaches
- The availability of server-side code (PHP, ASP/ASP.NET, Ruby, JSP etc...)
This leaves you with other options. You subscribe and or license a LMS online, but aside from the
remarks [the company] makes about their SCORM support you still should test the platform. This is why the
SCOBot project was originally started. Many have partially implemented or watered down approaches
to SCORM, and a quick import of a Unit Test can highlight any problem areas. Some even have poor API performance,
which is due to round tripping the server on every SCORM request This can inflict 100-250ms lag on your Shareable
content objects. (250ms x 10 calls = 2.5 Seconds!)
Then, your team gets to workout how to get the look and feel blended in their environment.
Your team may decide building your own is the way to go, but if you are in a deadline pinch, you simply won't
have the time to fashion a SCORM Runtime API, and the necessary backend components (let alone the student frontend experience).
Build vs. Buy, the age-old question.
SCOBot SCORM 2004 Runtime Environment
This was built in conjunction with the SCOBot SCORM Content API which assists developers adding SCORM support
to their Shareable Content Objects. Much of the core student attempt work is finished and as mentioned this API is in beta.
if you currently hold a contract or are a non-profit you can request a copy.
- API Support for SCORM 2004 only
- Event triggers your LMS portal can 'listen' to
- Manages cached CMI (student attempt)
- Force terminate interval for SCOs that exit, but don't terminate
- Integrate with your backend language of choice
- Shared State Persistence namespace (in progress)
- Advanced Distributed Learning namespace (in progress)
attempt. Code on your server will still need to be required to fully support SCORM 2004 unpacking of content, validation and
mode, credit, student name, id, and other parameters required by the specification. Events as mentioned above are fired which
you can listen to, along with API support for direct interaction. Since server-side logic commonly occurs within languages
like PHP, ASP.NET, Ruby, etc, and other Databases like mySQL, SQL Server, Postgres, etc, it leaves these areas for your team to integrate.
If you are a commercial entity, and or have a paid service/access, and would like the source code, please make contact to discuss further.