aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/blog/using-covid-19-pubseq-part3.html28
-rw-r--r--doc/blog/using-covid-19-pubseq-part3.org10
2 files changed, 8 insertions, 30 deletions
diff --git a/doc/blog/using-covid-19-pubseq-part3.html b/doc/blog/using-covid-19-pubseq-part3.html
index 94d5a2e..ac32717 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">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
-<!-- 2020-05-27 Wed 07:27 -->
+<!-- 2020-05-27 Wed 07:41 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>COVID-19 PubSeq Uploading Data (part 3)</title>
@@ -248,39 +248,27 @@ for the JavaScript code in this tag.
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<ul>
-<li><a href="#orgb387609">1. Uploading Data</a></li>
-<li><a href="#org7dd876c">2. What does this mean?</a></li>
+<li><a href="#org074cf76">1. Uploading Data</a></li>
+<li><a href="#org00e6dd5">2. What does this mean?</a></li>
</ul>
</div>
</div>
-<div id="outline-container-orgb387609" class="outline-2">
-<h2 id="orgb387609"><span class="section-number-2">1</span> Uploading Data</h2>
+<div id="outline-container-org074cf76" class="outline-2">
+<h2 id="org074cf76"><span class="section-number-2">1</span> Uploading Data</h2>
<div class="outline-text-2" id="text-1">
<p>
<i>Work in progress!</i>
</p>
-
-<p>
-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.
-</p>
</div>
</div>
-<div id="outline-container-org7dd876c" class="outline-2">
-<h2 id="org7dd876c"><span class="section-number-2">2</span> What does this mean?</h2>
+<div id="outline-container-org00e6dd5" class="outline-2">
+<h2 id="org00e6dd5"><span class="section-number-2">2</span> What does this mean?</h2>
</div>
</div>
<div id="postamble" class="status">
-<hr><small>Created by <a href="http://thebird.nl/">Pjotr Prins</a> (pjotr.public768 at thebird 'dot' nl) using Emacs org-mode and a healthy dose of Lisp!<br />Modified 2020-05-27 Wed 07:27</small>.
+<hr><small>Created by <a href="http://thebird.nl/">Pjotr Prins</a> (pjotr.public768 at thebird 'dot' nl) using Emacs org-mode and a healthy dose of Lisp!<br />Modified 2020-05-27 Wed 07:41</small>.
</div>
</body>
</html>
diff --git a/doc/blog/using-covid-19-pubseq-part3.org b/doc/blog/using-covid-19-pubseq-part3.org
index d088f78..1cd2db1 100644
--- a/doc/blog/using-covid-19-pubseq-part3.org
+++ b/doc/blog/using-covid-19-pubseq-part3.org
@@ -11,16 +11,6 @@
/Work in progress!/
-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:
- [[#uploading-data][Uploading Data]]
- [[#table-of-contents][Table of Contents]]