Translate and curate activities captured from a MOOC learner into a relational database with MOOC-Learner-Curated (MLC)
(see MOOC-Learner-Docker/curated_base_img )
Entry point is autorun.py
. Configuration is done with config/*yml
, see e.g. config/sample_config.yml
.
Description of MOOC-Learner-Curation execution is in docs/README.md
Two steps of an extension to MLC
apipe
: from MySQL db to intermediate CSVsqpipe
: from intermediate CSVs to new MySQL table
If you use data sources other than click-stream, you can follow a simpler track: only qpipe
If you rely on features that does not supported by the clickstream apipe
(e.g. new specifications) you have to add
patches to apipe
and debug
Course files from open edX servers with different specifications may have different formats. Pre-processing of the raw
course files and translating them into the correct format is inevitable. Connectors are the pre-processing tools of
MOOC-Learner-Curated. We do not integrate these into the pipeline of curated since we do not expect curated to identify
which type of course file it is processing. User should transform the course files in advance of running curated.
Currently we have to connectors which transform VisMOOC course files and MITx course tables into the MOOCdb
format.