Expansion health classification in the API
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 28/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 領域
- api
研究方向
Read the definitions in OpenConceptLab/ocl_issues#2942 and the read-only analysis behind OpenConceptLab/ocl_online#549; coordinate the design with Sunny before implementation. The API work depends on mapping classes from OpenConceptLab/ocl_online#640 and references related decisions in #2943. Done means health classes, reasons, counts and per-member details are computed and saved for new and copied expansions, existing expansions can be computed without changing members, and every class and reason has tests.
由索引模型根據 Issue 內容生成。
描述
Repo: oclapi2 · Depends on: OpenConceptLab/ocl_online#640 for mapping classes
Part of OpenConceptLab/ocl_issues#2942, which has the definitions. The API reports each expansion's health, so users, TBv3 and FHIR can see when an expansion isn't healthy without working it out themselves. The read-only analysis behind OpenConceptLab/ocl_online#549 is the starting point for the logic. Agree the design with Sunny before building.
ACs
- Each member, concept or mapping, gets a class against the repo version its reference resolved to: member of that release, HEAD, interim resource version, resource-versioned reference, version mismatch, ambiguous, or unattributed.
- Each expansion is healthy, HEAD-resolved, unhealthy or empty, with every reason that applies: inconsistent resolution, duplicate repo versions, resource-versioned references, unresolved references, interim resource versions, version mismatches, ambiguous or unattributed members.
- A
system-versionthat fails to resolve (OpenConceptLab/ocl_issues#2943) is a parameter reason, apart from lock failures. - Two versions of one source: OpenConceptLab/ocl_issues#2943 rejects them in
system-version. A value set whose own references name both is valid in FHIR, so the design says whether it counts under duplicate repo versions. - Computed when an expansion is built or copied and saved with it. A command computes it for existing expansions without changing members.
- Shown on the expansion (class, reasons, counts) and, on request, per member.
- Tests for every class and reason.
- 主要語言
- 沒有語言資料
- 星號
- 4
- 分支
- 2
- 平均合併
- 2 小時 12 分鐘
- 30 天內合併 PR
- 1
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
OpenConceptLab/ocl_issues 的其他 Issue
-
component/fhir type/bug
難度 2/5 1-3 小時 新手友好度 82/100
OpenConceptLab/ocl_issues#3026 ·
-
component/api decision/human-review signal/needs-access signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
難度 2/5 1-3 小時 新手友好度 72/100
OpenConceptLab/ocl_issues#3012 · 2 則留言 ·
-
component/design-system decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/docs
難度 2/5 半天 新手友好度 70/100
OpenConceptLab/ocl_issues#2983 · 1 則留言 ·
-
component/mapper decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
難度 2/5 1-3 小時 新手友好度 78/100
OpenConceptLab/ocl_issues#2966 · 2 則留言 ·
-
component/mapper component/web decision/human-review signal/low-risk signal/needs-human signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
難度 2/5 1-3 小時 新手友好度 76/100
OpenConceptLab/ocl_issues#2920 · 1 則留言 ·
查看 OpenConceptLab/ocl_issues 的全部 Issue
相似的 Issue
-
needs-triage
難度 2/5 1-3 小時 新手友好度 72/100
coder/claudecode.nvim#587 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
digitalbazaar/http-client#60 ·
-
難度 2/5 1-3 小時 新手友好度 72/100
fivetran/dbt_recurly#55 ·
-
難度 2/5 1-3 小時 新手友好度 78/100
topmonks/hlidac-shopu#3687 ·
維護者通常 1 天內回覆
-
bug lane: fast
難度 2/5 1-3 小時 新手友好度 76/100
unicef/adt-studio#1109 ·
維護者通常 2 天內回覆