obophenotype / obophenotype/uberon

NTR: cnidarian polyp stage

Open
#3,706 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hello UBERON Team,

There are some recent transcriptomic datasets for cnidarian species that may benefit from improved anatomical and developmental stage representation:

For example:
“we profiled gene expression in Acropora millepora across 26 life stages from unfertilised eggs to juvenile polyps”

Currently, I am limited to annotating the ‘polyp’ samples using only very general terms such as:

  • UBERON:0000468 ! multicellular organism
  • UBERON:0000092 ! post-embryonic stage

I would like to ask whether it would be possible to add a more specific class:

cnidarian polyp stage
Def:'A post-embryonic life stage of a cnidarian organism characterized by a sessile, radially symmetric body form with an oral-aboral axis, a gastrovascular cavity, and tentacles surrounding the oral opening.'
synonym: "polyp stage" EXACT []
synonym: "polyp form stage" RELATED []
synonym: "sessile polyp stage" RELATED []
is_a UBERON:0000092 ! post-embryonic stage

Thank you very much in advance for your feedback

Anne

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 proposed “cnidarian polyp stage” class, definition, synonyms, and is_a relationship in the issue. Check the UBERON ontology conventions for adding a developmental-stage term, then verify that the new class represents the described polyp samples and has the requested parent relationship.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.