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

[Discovery] Making LTI scores available for CBE mastery calculations

未关闭
  • 哪里不对？
#908 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

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.

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

描述

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?

Whats the timeline?

LTI improvements for Willow are in progress and Xylon is being planned. If the solution we agree upon requires changes in LTI or how/whether it stores scores in the grade book, we'd like to plan for that.

主要语言
Python
星标
10
派生
33
平均合并
4 天 2 小时
30 天内合并 PR
31

环境准备

  • 没有 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 摘要。