From 92fa550c6edfeb9acc9a5cbc31c0c272f8703898 Mon Sep 17 00:00:00 2001 From: Pjotr Prins Date: Fri, 29 May 2020 11:00:08 -0500 Subject: Blog stuff --- doc/blog/using-covid-19-pubseq-part3.html | 44 +++++++++++++++++++++++++------ 1 file changed, 36 insertions(+), 8 deletions(-) (limited to 'doc/blog/using-covid-19-pubseq-part3.html') diff --git a/doc/blog/using-covid-19-pubseq-part3.html b/doc/blog/using-covid-19-pubseq-part3.html index ac32717..7903791 100644 --- a/doc/blog/using-covid-19-pubseq-part3.html +++ b/doc/blog/using-covid-19-pubseq-part3.html @@ -3,7 +3,7 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
- +Work in progress! @@ -263,12 +265,38 @@ for the JavaScript code in this tag.
+The COVID-19 PubSeq allows you to upload your SARS-Cov-2 strains to a +public resource for global comparisons. Compute it triggered on +upload. Read the ABOUT page for more information. +
++We start with an assembled or mapped sequence in FASTA format. The +PubSeq uploader contains a QC step which checks whether it is a likely +SARS-CoV-2 sequence. While PubSeq deduplicates sequences and never +overwrites metadata it probably pays to check whether your data +already is in the system by querying some metadata as described in +Query metadata with SPARQL. +
+