Deliverables
Means for navigating from Open edX LMS to Superset
Course dashboard in Superset
Course dashboard for a subset of learners in Superset
Ability to search for an individual student and view subset dashboard for a single student in Superset
Operator dashboard in Superset (as it currently appears in beta - improvements to follow in a future release)
See Product Requirements Document for end user facing detailed requirements for each deliverable listed above.
Technical Details
Technical Approach
In short, this is a list detailing the selected technologies being used to run Aspects:
...
This link provides more detail about each technology selected to build aspects. See the
View file | ||
---|---|---|
|
Alternative Approaches Considered
Implementation Details
Aspects will be developed as a Tutor plugin, supporting all of the Tutor modes of operation (development, local, and Kubernetes).
Instructions for how to run Aspects outside of Tutor will also be provided, but not supported for v1.
By default we will share the Tutor-configured MySQL and redis instances, as well as a ClickHouse instance configured by the Aspects plugin, however these can be overridden to use separate instances or 3rd party hosted services.
We will rely on a Studio / LMS plugin to deliver platform metadata that is not appropriate for xAPI learning traces, such as course structure and learner metadata.
We will use single-sign-on with the LMS as a backend to provide Superset user authentication and permissions.
Numerous extension points will be provided to allow operators to create and maintain additional data sources, transformations, charts, and dashboards using configuration-as-code.
Technical Limitations
We’ve decided to omit demographics data from this initial release due to limitations around demographics data on the platform to date.
Right-to-left language support is not yet available in Superset.
Currently the LMS only provides relatively course permissions, therefore the roles in Superset are not able to be very fine grained.
Technical Requirements for Aspects V1
Deployment Requirements
Can be deployed in Tutor local or Tutor Kubernetes
Can be deployed using ClickHouse Cloud or Altinity Cloud to host ClickHouse
Resolution of known bugs
Before we consider this V1 release complete, we must address the following known bugs with Aspects beta:
Nonfunctional Requirements
Nonfunctional Requirements are also listed in the Product Requirements Document and consist of the following:
...