Wiring up blog entries

1 files changed, 16 insertions, 0 deletions

diff --git a/doc/blog/using-covid-19-pubseq-part2.org b/doc/blog/using-covid-19-pubseq-part2.org
index d61bf42..d2a1cbc 100644
--- a/doc/blog/using-covid-19-pubseq-part2.org
+++ b/doc/blog/using-covid-19-pubseq-part2.org
@@ -8,6 +8,22 @@
 #+HTML_LINK_HOME: http://covid19.genenetwork.org
 #+HTML_HEAD: <link rel="Blog stylesheet" type="text/css" href="blog.css" />
 
+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.
+
+* Table of Contents                                                     :TOC:noexport:
+ - [[#finding-output-of-workflows][Finding output of workflows]]
+ - [[#introduction][Introduction]]
+ - [[#the-arvados-file-interface][The Arvados file interface]]
+ - [[#using-the-arvados-api][Using the Arvados API]]
+
 * Finding output of workflows
 
 As part of the COVID-19 Biohackathon 2020 we formed a working group to