Skip to content

docs(opentargets): clarify diseases score meaning and EFO/MONDO IDs (#168)#240

Draft
Elarwei001 wants to merge 1 commit into
scverse:devfrom
Elarwei001:feature/opentargets-diseases-score-168
Draft

docs(opentargets): clarify diseases score meaning and EFO/MONDO IDs (#168)#240
Elarwei001 wants to merge 1 commit into
scverse:devfrom
Elarwei001:feature/opentargets-diseases-score-168

Conversation

@Elarwei001

Copy link
Copy Markdown
Contributor

Resolves #168

Summary

gget opentargets: Clarified the meaning of the diseases resource score column and the disease IDs in the documentation (resolves issue 168).

Testing

Documentation-only change (no functional code modified), so no new unit tests were required.

…cverse#168)

Clarify in the documentation that the `diseases` resource `score` is
OpenTargets' single overall target–disease association score (0–1)
aggregated across all data types/sources (not a per-data-source score),
and that the returned `disease.id` values are EFO-mapped traits that
include not only MONDO diseases but also HP phenotypes and EFO
measurements (e.g. "blood protein measurement"). gget returns the
associations exactly as OpenTargets reports them; documented how to
filter to MONDO terms only. Also updated the diseases example table to
the current post-rewrite column names.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Elarwei001 Elarwei001 marked this pull request as draft June 25, 2026 03:44
@Qiaoli-Li-Res

Copy link
Copy Markdown

I checked this locally. The PR only touches two docs files, and pre-commit passes on those files. The failing pre-commit.ci check is mypy, with errors in existing gget/*.py files, so it looks like the failure may be unrelated to this docs-only change. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants