From 0495b892fba350096c8b1bd741c55e148e7fc2de Mon Sep 17 00:00:00 2001 From: Pjotr Prins Date: Fri, 29 May 2020 14:23:25 -0500 Subject: Blog info for uploading sequence --- doc/blog/using-covid-19-pubseq-part1.html | 64 ++++++++++++------------------- 1 file changed, 25 insertions(+), 39 deletions(-) (limited to 'doc/blog/using-covid-19-pubseq-part1.html') diff --git a/doc/blog/using-covid-19-pubseq-part1.html b/doc/blog/using-covid-19-pubseq-part1.html index 5e52b82..1959fac 100644 --- a/doc/blog/using-covid-19-pubseq-part1.html +++ b/doc/blog/using-covid-19-pubseq-part1.html @@ -3,7 +3,7 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - + COVID-19 PubSeq (part 1) @@ -242,40 +242,26 @@ for the JavaScript code in this tag. -
- UP - | - HOME -
+

COVID-19 PubSeq (part 1)

-

-As part of the COVID-19 Biohackathon 2020 we formed a working group -to create a COVID-19 Public Sequence Resource (COVID-19 PubSeq) for -Corona virus sequences. The general idea is to create a repository -that has a low barrier to entry for uploading sequence data using best -practices. I.e., data published with a creative commons 4.0 (CC-4.0) -license with metadata using state-of-the art standards and, perhaps -most importantly, providing standardised workflows that get triggered -on upload, so that results are immediately available in standardised -data formats. -

-
-

1 What does this mean?

+ +
+

1 What does this mean?

This means that when someone uploads a SARS-CoV-2 sequence using one @@ -328,8 +314,8 @@ initiative!

-
-

2 Fetch sequence data

+
+

2 Fetch sequence data

The latest run of the pipeline can be viewed here. Each of these @@ -353,8 +339,8 @@ these identifiers throughout.

-