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.org | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
(limited to 'doc/blog/using-covid-19-pubseq-part1.org')
diff --git a/doc/blog/using-covid-19-pubseq-part1.org b/doc/blog/using-covid-19-pubseq-part1.org
index 5a749d6..0fd5589 100644
--- a/doc/blog/using-covid-19-pubseq-part1.org
+++ b/doc/blog/using-covid-19-pubseq-part1.org
@@ -5,18 +5,8 @@
# C-c C-t task rotate
# RSS_IMAGE_URL: http://xxxx.xxxx.free.fr/rss_icon.png
-#+HTML_LINK_HOME: http://covid19.genenetwork.org
#+HTML_HEAD:
-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:
- [[#what-does-this-mean][What does this mean?]]
@@ -261,7 +251,6 @@ Now we know how to get at the origin we can do it the other way round
and fetch all sequences referring to Washington state
#+begin_src sql
-
select ?seq ?sample
{
?seq ?sample .
@@ -272,6 +261,18 @@ select ?seq ?sample
which lists 300 sequences originating from Washington state! Which is almost
half of the set coming out of GenBank.
+Likewise to list all sequences from Turkey we can find the wikidata
+entity is [[https://www.wikidata.org/wiki/Q43][Q43]]:
+
+#+begin_src sql
+select ?seq ?sample
+{
+ ?seq ?sample .
+ ?sample
+}
+#+end_src
+
+
* Discussion
The public sequence uploader collects sequences, raw data and
--
cgit v1.2.3