This is the beginning of a collection of useful how-to information and resources for Berkeley faculty interested in offering all or part of a course using the EdX platform and technology. Contact email@example.com if you'd like to contribute to this Wiki and are not in the EECS Dept. (people with EECS logins already have edit access).
This information is for developers who want to create custom functionality for a particular course or research project (see below) based on the edX platform.
The edx-dev group
is for people across campus hacking edX directly. We meet weekly and sometimes there's free food. The requirement is you sign up to present something useful at the meeting.
documentation on both how to create a course and how to get/work with learner data; you can browse online, download as PDF, or download as an ebook.
Sef Kloninger's Five Ways to Extend edX
gives a good overview of the different ways to think about customizing the platform.
All About Autograding
has some specific info on building an external “custom grader” (one of the Five Ways described in Sef's overview, sometimes referred to as an “external grader” or “external checker” in the official edX developer documentation
is a Ruby-embedded domain-specific language for creating quiz questions that can be exported to edX, to a printable quiz, or to AutoQCM
, an open-source tool that lets you create scantron sheets and grade scanned filled-in scantron sheets.
Doing Research on MOOC Data
Generally speaking, you must:
In general, an edX MOOC produces three different data sources:
MySQL databases store info about students, their grades, and earned certificates.
The MongoDB databases that store the edX forum data (discussion boards)–the full text of posts, replies, and so on. Importing them into Mongo is straightforward using mongoimport.
To learn more about the data:
There's also a variety of user-contributed tools (both for data management and other stuff) on the edX Tools wiki.