Giter Club home page Giter Club logo

eubic / reproduciblemsguidelines Goto Github PK

View Code? Open in Web Editor NEW
6.0 11.0 1.0 340 KB

This project aims at defining a set of guidelines for reproducible mass spectrometry-based experiments.

Home Page: https://eubic.github.io/ReproducibleMSGuidelines

License: Creative Commons Attribution 4.0 International

HTML 9.82% CSS 6.65% JavaScript 82.95% Shell 0.58%
mass-spectrometry proteogenomics proteomics metabolomics lipidomics guidelines openaccess

reproduciblemsguidelines's Introduction

Minimal Guidelines for Reproducible MS-based Research

This project aims at defining a set of guidelines to report mass spectrometry-based experiments in a reproducible fashion.

To view the guidelines, use https://eubic.github.io/ReproducibleMSGuidelines. This uses a JavaScript application to render the actual guidelines.md document. This rendering tool can also be used offline when downloading the repositories content and opening the index.html file.

Introduction

There is a growing concern about a lack of reproducibility in science that also affects bioinformatics and mass spectrometry (MS-based) technologies. One aspect of this problem is that bioinformatic analysis are increasingly complex and greatly influence the outcome of a study. Current bioinformatic analysis commonly consist of multiple tools and algorithms, each with its own set of parameters. Recording all of these settings in full detail is rarely possible in methods sections of a research manuscript. This often leads to vital details about the bioinformatic processing of the data to be missing. In this work, we, therefore, try to establish a set of guidelines to describe

  • The minimal information required in the bioinformatic methods section of MS-based manuscripts.
  • A well-defined checklist of requirements to help authors, reviewers, and editors to assess bioinformatic analyses
  • The required extended information data (supplementary) that needs to accompany any manuscript in order to ensure its reproducibility

Scope

These guidelines aim to provide recommendations for mass spectrometry-based experimental techniques. The guidelines currently contain recommendations for

  • MS-based bottom-up proteomics
  • Proteogenomics

Fields that we are currently working on are

  • Lipidomics
  • Metabolomics
  • MS-based imaging

Contributions for any other MS-based method are highly welcome!

The Guidelines

The complete guidelines are stored in the guidelines.md file in this repository. We created a JavaScript application that nicely renders this document as a webpage at https://eubic.github.io/ReproducibleMSGuidelines. The actual file is a standard markdown file that can be viewed here.

We are currently working on a more user-friendly web-based rendering of these guidelines.

Who can contribute?

Everyone! The creation of this guidelines as a completely community-driven project. How to contribute

How can I contribute?

  • Fork this repository, adapt the guidelines.md file and create a pull request
  • Send an e-mail with your changes to [email protected]
  • If you want to work on a larger section of the document, let us know and we will move the Guidelines into a Microsoft Word document for you.

Guidelines format

While the guidelines.md file is a normal markdown file, it does follow some conventions in order to render a user-friendly version.

Sections

The guidelines are grouped into sections, each represented as the top level scope of the markdown file:

# Section name
...

Every section may have a description:

# Section name
SectionDescription: A great description that
may span multiple lines.

Finally, a section may have an example section:

# Section name
SectionExample: A reference to a study that created a very reproducible
workflow. Again, the example may span multiple lines.

Items

Items are the actual recommendations in the guideline.

# Public Data Deposition

Name: Raw data deposition
Category: bronze
Description: The complete RAW data must be deposited in a public repository.
Fields: all

Items start with the Name: tag. Every item is assigned to a category, either "bronze", "silver", or "gold" and has a descrition. Items are linked to specific fields, such as "proteomics", or "metabolomics", but may also be applicable to "all" fields. The Fields: slot is a comma-delimited list of field names. Finally, every item may have an Example: field that again may span multiple lines. Items must end with an empty line.

reproduciblemsguidelines's People

Contributors

jgriss avatar mlocardpaulet avatar ralfg avatar veitveit avatar ypriverol avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

mlocardpaulet

reproduciblemsguidelines's Issues

[viewer] Firefox only prints first page

Currently, Firefox only prints the first page of the guidelines document. This seems to be a recurring issue with Firefox.

Google Chrome prints the page as expected.

guidelines ordering

Is there a logic behind the order of the guidelines? Should we order them with bronze/silver/gold?

Guidelines 243: The protein sequence database used including the exact version/date of download (if a release version is not available) are described

The description of that guideline does not really make sense to me:
"If the original FASTA file from the resource is not transform/change and the release number of the file is not available; the exact version/date of the downloaded FASTA file should be provided."

Do you want to say, that the original file should not be changed? Or do you want to say, that either the release version or an exact download date should be provided? Or both?

New item: Use of Docker images

Category: Workflow Software (or new section?)

Name: If containers are used in the analysis, they should be referenced through stable version numbers
Category: "bronze"
Description: If containers, such as Docker or Singularity containers, are used in the analysis
they should be referenced through stable version numbers. This explicitly relates to not
using the ":latest" tag for Docker images as these are bound to change upon new releases
of the software.
Fields: "all"

Name: If containers are used in the analysis, these should be available in a public repository
Category: "silver"
Description: If containers, such as Docker or Singularity containers, are used in the analysis
they should be available through a public repository, such as Docker Hub.
Fields: "all"

Reason

The use of containers becomes increasingly common and is increasingly supported by worfklow systems, such as nextflow

Linked pages through top-level tabs

Linked pages through top-level tabs are somewhat arbitrary:

  • Scope: pop-up
  • Google / Support / EuBIC: new tab
  • Contribute: page redirect

This could be more uniform or at least more transparent for improved user-friendliness

Typo's

Tab Headers: Support this Guideline
ToC: Manual Curation

Guidelines 248: The method used to create a decoy database is specified

Several typos in the description. Here is the corrected text:
"During the peptide identification step, the search engine uses a decoy database to statistically access the quality of the peptide identifications. Multiple methods are available to generate the decoy databases (e.g reverse, random, etc). We recommende to mention the strategy used to generate the decoy database in the main manuscript."

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.