Community Sharing of Results Via GitHub

We want Nextstrain to be a community-driven platform, to share datasets with collaborators and the world. While you can install augur and auspice locally to analyse and interact with datasets, we wanted a way to share these with the world – without having to lose control of your data.

Our solution to this is to allow anyone to store the results of their analyses on GitHub but still analyse them through nextstrain.org. This gives you complete control, ownership, and discretion over your data.

How Does This Actually Work?

  • Run your analysis locally (see the bioinformatics introduction)

  • Create a GitHub repository for your analysis. For instance, Alli Black has created a “zika-colombia” in the “blab” group/organisation/username – github.com/blab/zika-colombia

    • This is your own github repository – you don’t even need to tell us about it if you don’t want to!

  • Make sure the JSONs you’ve produced start with the same name as the repository. In this case they’d need to be zika-colombia_meta.json and zika-colombia_tree.json

  • Store your final output from augur, i.e. the JSONs which auspice uses, in a directory called “auspice” – see here for an example

    • While you don’t need to, it’d be great if you also stored your analysis pipeline (e.g. Snakefile) on GitHub too! This doesn’t need to give away any data, just the recipe for the analysis.

  • Push things to github.

  • Access your data via “nextstrain.org/community” + “github organisation name” + “github repo name”. For this example, it’s at nextstrain.org/community/blab/zika-colombia.

    • Share your results with the world 🎉🎉

Some Examples