Google’s Course Builder is a great resource for the MOOC community. Open source, simple, and easily modified, a programming novice can go from download to a working MOOC ready for thousands of people in a short period of time. Rapidly authored and easily deployed MOOCs are fantastic, but create a new problem: data integration. Many people will participate in multiple MOOCs over time, and bringing that data together will deliver a lot of value for individuals and organizations.
So, I’ve added simple support for the Tin Can API (also known as the Experience API) to Google Course Builder. The Tin Can API is a modern standard for communicating learning data, intended for recording learning anywhere and everywhere it occurs. In a typical Tin Can ecosystem, learning applications and related systems, such as a Google Course Builder MOOC, produce ‘statements’ describing the learning ‘activities’ that ‘agents’ are engaging in, such as completing assessments, answering questions, and completing the course as a whole (I added support for all three of those). Those statements are then sent to a ‘Learning Record Store’ (LRS), where they can be sliced, diced, and generally considered.