obophenotype / obophenotype/uberon

review taxonomic distribution: syrinx

Open
#3,725 2 comments 1 reaction 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

@dragon-ai-agent please review this uberon term

id: UBERON:0009074
name: syrinx organ
def: "Vocal organ of birds, located at the base of a trachea." [Wikipedia:Syrinx_(bird_anatomy)]
subset: organ_slim
synonym: "avian vocal organ" RELATED []
synonym: "syrinx" RELATED []
xref: NCIT:C111323
xref: Wikipedia:Syrinx_(bird_anatomy)
is_a: UBERON:0000062 ! organ
relationship: capable_of_part_of GO:0071625 ! vocalization behavior
relationship: in_taxon NCBITaxon:8782 ! Aves
relationship: part_of UBERON:0003126 ! trachea
property_value: depiction "http://upload.wikimedia.org/wikipedia/commons/8/87/Syrinx.jpg" xsd:anyURI

review the sub-parts. Suggest a more precise definition (with provenance)

look at taxonomic distribution - when did this organ and its parts evolve? Where has this been lost as a functional organ? Should we add additional taxon constraints, particularly never_in

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 with the UBERON:0009074 YAML term and review its definition, sub-parts, relationships, and taxonomic distribution. Research when the syrinx and its parts evolved, where the functional organ was lost, and whether additional never_in constraints are justified. Done means a more precise definition with provenance and supported taxonomic constraints are proposed.

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
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.