Skip to content

Header: Mandatory Annotation database? #6

@ThomasDesvignes

Description

@ThomasDesvignes
Member

It was suggested during the authors' review of the mirGFF3 paper that the mirGFF3 file should have the annotation database used for the initial step of detection, annotation, and quantification as mandatory header.

While this seems absolutely logical for researchers working on well characterized model species or human data, this is impractical for researchers working on non-model organisms for which no database is well maintained or don't even include these species.

Marc Friedländer suggested to specify as mandatory header either "miRBase (with version)", "MirGeneDB (with version)" or "custom".

I think this would be satisfactory for everyone and if an analysis using a 'custom' annotation database get published, then it would be easy to obtain a Github/Zenodo DOI that could be used as a header in addition to the "custom information". Something like: "Custom (DOI:Zenodo....)"

Any opinion on this? Should we make mandatory a header with the annotation database used?

Activity

changed the title [-]Mandatory Annotation database?[/-] [+]Header: Mandatory Annotation database?[/+] on Dec 18, 2018
phillipeloher

phillipeloher commented on Dec 18, 2018

@phillipeloher

Our aligner is currently using miRCarta 1.1 and miRBase 22.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @phillipeloher@ThomasDesvignes

        Issue actions

          Header: Mandatory Annotation database? · Issue #6 · miRTop/mirGFF3