Skip to content

Conversation

@dragon-ai-agent
Copy link
Collaborator

Summary

  • Added new term 'cochlear nerve root' (UBERON:7770009) as requested in cochlear nerve root #3570
  • Definition based on validated assertions from Aurelian analysis using PMID:27289629
  • Term classified as a nerve root and part of brain
  • Includes only assertions confirmed by literature validation

Details

Based on the Aurelian validation in the issue comments, I included only the assertions that were confirmed:

  1. Location at the dorsolateral junction of the pons and medulla ✓
  2. Division of the ventral cochlear nucleus into anteroventral and posteroventral regions ✓

The definition excludes unvalidated assertions about nerve structure and fiber bifurcation that could not be confirmed by the reference paper.

Test plan

  • Term follows UBERON naming conventions
  • Uses next available UBERON:777xxxx ID (UBERON:7770009)
  • Proper parent classification (nerve root, part of brain)
  • Reference validated through Aurelian
  • Definition includes only confirmed assertions

Closes #3570

🤖 Generated with Claude Code

Added new term 'cochlear nerve root' with definition based on validated
assertions from Aurelian analysis of literature. Definition includes only
assertions confirmed by reference PMID:27289629. Term is classified as a
nerve root and is part of the brain.

Addresses #3570

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@dosumis
Copy link
Contributor

dosumis commented Jun 27, 2025

@RiveraAndrea83 - I think I might have asked the agent to do too much. Would have been better to use my brain to edit down :) .

[Term]
id: UBERON:7770009
name: cochlear nerve root
namespace: uberon
Copy link
Collaborator

@gouttegd gouttegd Jun 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(1) That namespace tag is not needed, since uberon is already the default namespace in the entire file. Not sure where the agent took the “inspiration” for that tag, given that no other term frame in uberon-edit.obo has such a tag.

(2) That tag causes the check-obo-for-standard-release.pl script to raise an error because it perceives the term as having a different namespace than its UBERON:0002211 parent. (The correctness of that check is dubious: yes, UBERON:0002211 does not have an explicit namespace, but it does inherit the default namespace declared in the header, and therefore is in fact in the uberon namespace – but apparently the script only takes into account term-level namespace tags, not the default namespace.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cmungall
Copy link
Member

cmungall commented Jul 4, 2025

@dragon-ai-agent please update the PR (do not make a new PR, check out this branch and commit here). I have updated your instructions. I mistakenly told you to add a namespace tag before. As @gouttegd points out this is not how we do things in this ontology. Remove the namespace tag on the term you made

As pointed out by @gouttegd, namespace tags are not standard practice in
this ontology. Removed the namespace tag from the cochlear nerve root term
to follow proper UBERON conventions.

@dragon-ai-agent
@dragon-ai-agent
Copy link
Collaborator Author

Updated the cochlear nerve root term (UBERON:7770009) to remove the namespace tag as pointed out by @gouttegd. This follows proper UBERON conventions - namespace tags are not standard practice in this ontology.

The term now properly follows the standard format without the namespace tag.

@dragon-ai-agent

@github-actions
Copy link
Contributor

github-actions bot commented Aug 7, 2025

This PR has not seen any activity in the past month; if nobody comments or reviews it in the next week, the PR creator will be allowed to proceed with merging without explicit approval, should they wish to do so.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cochlear nerve root

6 participants