obophenotype / obophenotype/uberon

Using Uberon terms with human labels

Open
#2,860 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Emacs Lisp
Stars
163
Forks
43
Avg merge
1d 17h
Merged PRs (30d)
5

Description

Is there a plan for providing Uberon terms with human/clinically relevant labels? Re: https://github.com/obophenotype/uberon/issues/1522#issuecomment-547575843

I see that some human terms have been tagged with "human_preferred" (https://github.com/obophenotype/uberon/issues/278). Can those annotations be used to swap the general labels with their human counterparts?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Uberon issues #1522 and #278, especially the discussion of human_preferred annotations. No files or tests are identified in this issue. Clarify whether those annotations should replace general labels and define the expected scope before implementation.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.