Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing parent: inconsistent parentage in RNA processing branch #27828

Closed
ValWood opened this issue May 3, 2024 · 3 comments
Closed

Missing parent: inconsistent parentage in RNA processing branch #27828

ValWood opened this issue May 3, 2024 · 3 comments

Comments

@ValWood
Copy link
Contributor

ValWood commented May 3, 2024

rRNA modification/tNRA modification are under RNA processing
snRNA modification is not under snRNA processing

Screenshot 2024-05-03 at 12 28 15
  • GO term ID and label for which you request a new superclass

  • New superclass (parent) suggested

  • Reference(s), if appropriate
    PMID:nnnnnnn

@pgaudet
Copy link
Contributor

pgaudet commented May 6, 2024

Also - processing should not be under 'catabolic process'
It should mean biosynthetic process/maturation. But we need to check that the annotations are consistent with this.

Thanks, Pascale

@ValWood
Copy link
Contributor Author

ValWood commented May 6, 2024

Note the catabolism problem was due to a logical def issue and only appeared recently. Was dealt with in
#27633

@ValWood
Copy link
Contributor Author

ValWood commented Jun 28, 2024

Note that the modification terms have logical defs but the ones which are correctly positioned under their RNA processing
terms have this relation instantiated so I have done the same for snoRNA. Maybe one day the "RNA modification" terms will go, but this makes everything in the correct place.

@ValWood ValWood closed this as completed in b2c5ba7 Jul 1, 2024
ValWood added a commit that referenced this issue Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants