obophenotype / obophenotype/uberon

EHDAA2:0001090 medulla oblongata alar plate (human), wrong part_of relationship

Open
#1,725 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Not sure I am at the right place, but...

[Term]
id: EHDAA2:0001090
name: medulla oblongata alar plate (human)
is_a: AEO:0001012 ! neuronal grey matter
is_a: UBERON:0004121 ! ectoderm-derived structure
is_a: UBERON:0005291 ! embryonic tissue
is_a: UBERON:0010314 ! structure with developmental contribution from neural crest
relationship: develops_from EHDAA2:0000924 ! myelencephalon alar plate (human)
relationship: existence_starts_during_or_after HsapDv:0000025 ! CS18
relationship: part_of UBERON:0005240 ! basal plate medulla oblongata

alar plate and basal plate are distinct neural structure, actually

Please note that
EHDAA2:0001090 medulla oblongata alar plate (human)
may have
relationship: dorsal_to UBERON:0009576 ! medulla oblongata sulcus limitans

and please note also that there is no UBERON class for 'alar plate medulla oblongata' so far

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 locating the EHDAA2:0001090 term in the ontology source and review its current relationships, especially the part_of assertion and the surrounding medulla oblongata terms. Compare the alar-plate and basal-plate distinctions described in the issue, then validate the corrected relationship against the ontology's checks. Done means the term no longer asserts the anatomically incorrect relationship and the ontology passes validation.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.