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

[Placeholder] Django admin pages to view and correct learner competency statuses

Abierto
  • ¿Algo no está bien?
#843 0 comentarios 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
django, python
Área
backend

Línea de trabajo

Start by reading ADR-0004 and the requirements in issues #642 and #643, then map the learner competency and mastery-status models they describe. Resolve how staff corrections and tree rollups should behave before locating the Django admin entry points. Done means the correction behavior is decided and the required admin views support viewing and editing the relevant statuses.

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

Descripción

Unresolved Requirements

  • Django admin pages are needed to view and correct a learner's competency status, meaning the mastery status recorded for a learner at the competency level, and at the criteria group and criterion levels once #642 adds those models.
  • Django admin pages are needed to view and correct the mastery statuses themselves, meaning the lookup table of AttemptedNotDemonstrated, PartiallyAttempted and Demonstrated.

Open Questions

  • How do we implement downward corrections? An automatic write may only raise a status, while a staff correction may lower one (ADR-0004 Decisions 4 and 6), and #643 states that no current work covers the staff correction path. Should a correction include the tree rollup, and can that rollup cause the loss of statuses on higher criteria groups or competencies, or the loss of a mastery status the learner had earned?
  • If a mastery status is changed by hand, how do we handle the tree no longer being in sync? The statuses above and below the changed row were computed from grades and from the old value, so they can disagree with the corrected row until something recalculates them.
Lenguaje dominante
Python
Estrellas
10
Forks
33
Merge medio
2 d 19 h
PR fusionados (30 d)
24

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.