Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#843 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
django, python
领域
backend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
Python
星标
10
派生
33
平均合并
2 天 9 小时
30 天内合并 PR
9

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

openedx/openedx-core 的其他 Issue

查看 openedx/openedx-core 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。