Updating headers

pages/SeaScience.md

+--- 
 Title: Environmental data
-Author: Jannik, Daniele, Giorgio
+Author: Jannik
 Topics:
   * options for sea science
   * types of environmental data
+Status: draft
 ---
 
-**Proposed text by Jannik**
-
-**Environmental data**
+## Environmental data
 
 The KM3NeT research infrastructure will also house instrumentation for Earth and Sea sciences for long-term and on-line monitoring of the deep-sea environment. Until now, measurements in the deep sea are typically performed by deploying and recovering autonomous devices that record data over periods of months to years. This method is severely constrained by bandwidth limitations, by the absence of real-time interaction with the measurement devices and by the delayed access to the data. A cabled deep-sea marine observatory, like KM3NeT, remedies these disadvantages by essentially providing a power socket and high bandwidth Ethernet connection at the bottom of the sea. This is an important and unique opportunity for performing deep-sea research in the fields of marine biology, oceanography, environmental sciences and geosciences. To this end, both the French and Italian KM3NeT sites are nodes of the European Multidisciplinary Seafloor and water column Observatory (EMSO) [1].
 

pages/Simulation.md

+---
 Title: Event simulation
 Author: Jutta, Tamas
 ---

pages/Softwaredevelopment.md

+---
 Title: How to develop software
 Author: Tamas
 Topics:

pages/Usecase_ANTARES.md

+---
 Title: ANTARES use case
 Author: Rebecca
 Topics:

pages/Usecase_Environmental.md

+---
 Title: Environmental data usecase
 Topics:
   * short description use
   * data description
   * interfaces
 ---
+
+* Acoustic data will be provided through separate REST-API
+* Envisioned data including psd tables and audio as wave files for a few minutes per day/week
+* Data sets integrated as km3resources to Open Data Center
+* Jupyter notebook demonstrating data use
+

pages/Usecase_KM3NeT.md

+---
 Title: KM3NeT use case
 Author: Steffen
 Topics:
@@ -5,3 +6,9 @@ Topics:
   * data description
   * linking to notebooks & background
 ---
+
+
+* Dataset to show use of KM3NeT data in a non-astrophyics context (or using a muon dominated data samples)
+* Runs selected from ORCA4 line data according to quality criteria
+* Processed to metadata enriched hdf5
+* Analysis examples provided as jupyter notebook

pages/Using_alerts.md

+---
 Title: How alert data can be used
 Author: Feifei, Jutta
 Topics:

pages/Using_km3events.md

+---
 Title: How to read hdf5 data
 Author: Steffen, Jutta
 Topics:

pages/Using_plotdata.md

+---
 Title: How to use analysis data
 Author: Rebecca, Jutta
 Topics:

pages/Using_templates.md

+---
 Title: Using public plot and analysis templates
 Author: Zineb, Jutta
 Topics:

pages/Using_vo.md

+---
 Title: How to use VO SCS data
 Author: Jutta
 Topics:
   * summary from open course 
   * https://edu.km3net.de/course/accessing-the-km3net-open-data/
+
+Status: draft
 ---
+
+# Accessing data through the VO server
+
+A short [online course](https://edu.km3net.de/course/accessing-the-km3net-open-data/) has been provided at our Education Portal.
+
+Complying with the standards set by IVOA, the KM3NeT open data are accessible with services defined by the Table Access Protocol (TAP). The services operating under this protocol allow the execution of queries in order to retrieve the data from the database tables as well as to inspect various metadata. The TAP services support SQL commands. It is highly recommended the queries to be written in Astronomical Data Query Language (ADQL). A nice introduction of ADQL used in a TAP service is found here. Another way to retrieve the data is the Simple Cone Search (SCS). This defines queries for sky search in a cone with given position and radius.
+
+The standard Table Access Protocol allows the existance of TAP clients. The most widely used are the Aladin client as well as the TOPCAT client. The TAP clients interoperate and communicate under the Simple Application Messaging Protocol (SAMP). There is also an option to access the data via python scripting. This is possible using the pyVO, a package affiliated with Astropy.
+
+## Using VO clients
+Information on how to download and install Aladin is found at https://aladin.u-strasbg.fr/java/nph-aladin.pl?frame=downloading.
+
+An introduction on how to use ADQL is found here.
+
+## Using the VO python interface
+You can find information on how to install Astropy at https://www.astropy.org/ and for the pyVO at https://pyvo.readthedocs.io/en/latest/
+
+```python
+import pyvo as vo
+
+service = vo.dal.TAPService("http://vo.km3net.de/__system__/tap/run/tap")
+
+# resultset works like a numpy record array
+resultset = service.search("SELECT * FROM ant20_01.main")
+print(resultset.fieldnames)
+print(resultset)
+
+resultset = service.search("SELECT * FROM ant20_01.main WHERE ABS(decl)<10 AND ABS(ra)<20 AND nhit>90")
+print(resultset)
+
+resultset = service.search("SELECT * FROM ant20_01.main WHERE ABS(mjd-57474.8)<1.0")
+print(resultset)
+```
+
+An introduction on how to use ADQL is found [here](http://docs.g-vo.org/adql/html/)

pages/VOserver.md

+---
 Title: VOserver
 Author: Jutta
 ---
+
+## Approach to the Virtual Observatory standard
+
+The Virtual Observatory (VO) standards\cite{VO}
+serve to create an interface between astronomy-related data resources
+from astrophysics experiments which act as data providers. The focus is on the scientific end user to easily interface from their personal
+computer with the provided data sets. The KM3NeT collaboration is a data
+provider to the VO and operates a data server\footnote{at \url{http://vo.km3net.de/}} running the DaCHS software\cite{dachs}.
+The well-developed data sharing regime of the VO serves well as a
+guideline for the implementation of astrophysical data sharing in the
+KM3NeT collaboration. However, considering the role of neutrino physics
+just at the edge of use for astronomical studies, KM3NeT data
+integration also meets some limitations considering the scientific
+usability of the provided data sets. In addition to that, publication of
+data through VO standards is clearly limited to astronomy-related data
+in a celestial reference frame.
+
+* Running server with DaCHS software
+* Registered as data provider to the VO (ivo://km3net.org)
+* Can publish data sets to the VO registry - done with Antares 2007-2017 data
+* Data accessible through widely used tools in astrophysics (Aladin, Topcat …)
+
+
+
+

pages/Workflows.md

+---
 Title: Workflow management
 Author: Jutta, Tamas
 ---