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

Additional info for page: Epitranscriptome data #1098

Open
daniwelter opened this issue Dec 8, 2022 · 1 comment
Open

Additional info for page: Epitranscriptome data #1098

daniwelter opened this issue Dec 8, 2022 · 1 comment
Assignees

Comments

@daniwelter
Copy link
Contributor

I would like to request additional information for the Epitranscriptome data page at /epitranscriptome_data. The page should cover in a bit more detail the kind of metadata that should be stored with analysis output files, since intermediate data files are not routinely stored. If standard analysis metadata logs are provided by the tools being described, this should be explicitly stated.

@lauportell
Copy link
Collaborator

Answer from contributors of this pages:

I went through the problem. From my side, I don’t think we should add further information because the protocol to detect RNA editing events starts from a table of RNA variants and then it proceeds through several filtering steps in which no metadata are introduced. Low quality variants are simply discarded and what we think the best candidates are written in the output table.

I don’t think that intermediate files are useful, they are all subsets of the original table. So, the only metadata to save are at the beginning and they are related to the specific experiment, I mean the accession number of the RNAseq run, the main features of the input RNA (if polyA+ or total RNA ribo depleted, if reads are stranded or not), the origin of RNA (tissue, cell line, healthy or affected) and probably the lab producing the data.

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

3 participants