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

RNA types #97

Open
eboileau opened this issue May 23, 2024 · 1 comment
Open

RNA types #97

eboileau opened this issue May 23, 2024 · 1 comment
Assignees
Labels
needs:help Infrastructure, sysadmin, etc. status:on-hold Temporarily not being dealt with or pursued type:enhancement New feature or request

Comments

@eboileau
Copy link
Collaborator

Aims/objectives.

The nomenclature for RNA types (table rna_type) is fixed e.g.

+---------+-------------------+
| id      | name              |
+---------+-------------------+
| circRNA | circular RNA      |
| mRNA    | messenger RNA     |
| miRNA   | micro RNA         |
| rRNA    | ribosomal RNA     |
| snRNA   | small nuclear RNA |
| tRNA    | transfer RNA      |
+---------+-------------------+

This means that anyone can eventually upload modification data associated with any of these RNA types. According to the specification,

a given dataset or bedRMod file can contain more than one modification, as reported in column 4 (MODOMICS short name), but this should be for the same RNA type.

otherwise it becomes practically impossible to search records, at least the way the model is designed.

A clear and concise description of todo items.

  • Do we actually need a special treatment for the RNA types other than tRNA? i.e. all of these can be annotated with Ensembl exactly as for mRNA, as far as I known. The only problem is that in principle this would require different bedRMod files (dataset) for different RNA types, whereas generally mapping includes all of mRNA, miRNA, rRNA (incl. MT), etc. In practice it may be difficult to differentiate mRNA from the other common small RNAs...
  • tRNA should definitely be handled separately, and in general anyway, mapping of mRNA/other RNAs will not include tRNA, unless I'm mistaken. On this, see RNA types: tRNA #69, but I have no clue how this can be implemented in practice. And do tRNA bedRMod files are the same (genomic coordinates, etc.)?
@eboileau eboileau added priority:high High priority issue needs:help Infrastructure, sysadmin, etc. labels May 23, 2024
@eboileau eboileau self-assigned this May 23, 2024
@eboileau eboileau added this to the First release milestone May 24, 2024
@eboileau
Copy link
Collaborator Author

eboileau commented Jun 7, 2024

The terminology is now fixed to

+------+---------------------+
| id   | name                |
+------+---------------------+
| tRNA | transfer RNA        |
| WTS  | whole transcriptome |
+------+---------------------+

It is built around the concept of sequencing method rather than the biological definition of RNA species. WTS thus stands for mRNA, ncRNAs, etc.

I started to work on integrating tRNAs...

We can eventually add rRNA, but unless I'm mistaken, this would not require changes, as they will be annotated with Ensembl and be handled as WTS.

eboileau added a commit that referenced this issue Jun 11, 2024
@eboileau eboileau added type:enhancement New feature or request status:on-hold Temporarily not being dealt with or pursued and removed priority:high High priority issue labels Jun 21, 2024
@eboileau eboileau removed this from the Q3 improvements & maintenance milestone Jul 1, 2024
@eboileau eboileau added this to the Settle for submission milestone Jul 16, 2024
@eboileau eboileau modified the milestones: To settle, Annotation Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:help Infrastructure, sysadmin, etc. status:on-hold Temporarily not being dealt with or pursued type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant