Changes between Version 60 and Version 61 of SatelliteBigData

Timestamp:

2009/03/20 14:49:57 (16 years ago)

Author:

severin

Comment:

--

SatelliteBigData

@@ -87 +87 @@
 Currently the available public resources like SRA, GEO, ArrayExpress, Cibex[http://cibex.nig.ac.jp/index.jsp] are only providing query facilities on the metadata of the experiments surrounding the data.  The data is available as files to download (often in the original format) but they do not provide facilities to externally explore the data and ask biological questions on the data.  This then forces anyone who wants to explore the dataset to download this data into local integration systems before they can ask their biological questions. 
 
-But not all data is public.  Research centers who generate this data need to manage it and data-mine it in order to produce publications and do science.  This means they need the same or greater sophistication of tools than are available on the public services.  Many of these research projects are often collaborative and international, which means this private datasets need to be accessible on the web, but protected and secured.  These "collaboration webservices" are often then made public when the research is published (for example the FANTOM4 project). 
+But not all data is public.  Research centers who generate this data need to manage it and explore it in order to produce publications and do science.  This means they need the same or greater sophistication of tools than are available on the public services.  Many of these research projects are often collaborative and international, which means this private datasets need to be accessible on the web, but protected and secured.  These "collaboration webservices" are often then made public when the research is published (for example the FANTOM4 project). 
 
 With more and more international efforts, not all data may end up in one archive. Even today we see this between GEO, ArrayExpress and CIBEX where some datasets are only available on one or two of the three services.  This means that next-generation queries may always have to query multiple databases simultaneously in order to find the data they need.