Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Discovery] Making LTI scores available for CBE mastery calculations

Abierto
#908 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
django, python
Área
api, backend

Línea de trabajo

Start with the linked discussion in #731, then find the Open edX LTI AGS models where line items and criterion-level scores are stored. Trace the CBE mastery logic that evaluates gradeable subsections to see where an LTI score could be read. Done here is a written recommendation for bridging the two without tying every LTI line item to a visible course subsection; no patch is expected yet.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

discovery
Purpose of this issue

Following the discussion in #731, how can we make individual LTI scores available for competency-based education (CBE) mastery calculations?

Use case and gap

In EDL’s use case, a single Muzzy Lane assessment returns multiple criteria-level scores through LTI Assignment and Grade Services (AGS). A learner demonstrates a sub-competency by meeting the required threshold on each relevant criterion.

As noted in the original discussion, these line items and scores are stored in the Open edX LTI models. However, the CBE MVP uses gradeable subsections to define competency criteria and evaluate mastery. The individual LTI scores therefore need a way to become available to that subsection-based logic.

Approach suggested so far

@mgwozdz-unicon suggested representing each LTI line item as a gradeable subsection, potentially through a hidden subsection, so existing CBE logic can evaluate its score without changing the learner’s course outline.
This could let us use the existing subsection-based CBE model.

Concerns with this approach:

This could couple externally managed LTI line items to course structure. Creating or deleting a line item could require creating or deleting a corresponding subsection. Even if those subsections are hidden from learners, what implications would this have for course authoring and maintenance?

So what approach can bridge this gap?
Lenguaje dominante
Python
Estrellas
10
Forks
33
Merge medio
3 d 8 h
PR fusionados (30 d)
30

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openedx/openedx-core

Todos los issues de openedx/openedx-core

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.