adding status

.gitlab-ci.yml

@@ -29,13 +29,17 @@ build:
     paths:
       - Deliverable_4-8.md
       - Deliverable_4-9.md
+      - statuspage.md
     expire_in: 3 weeks
 
 # the 'pages' job will deploy and build your site to the 'public' path
 pages:
   stage: deploy
+  dependencies: 
+    - build
   script:
     - gitbook build . public # build to public path
+    - mv statuspage.md public
   artifacts:
     paths:
       - public

SUMMARY.md

@@ -39,4 +39,5 @@
 * Data publication
 
 ## [References](pages/References.md)
+## [Deliverable status](statuspage.md)
 

filelist_D4-8.txt

@@ -16,8 +16,7 @@ pages/VOserver.md
 pages/KM3NeTserver.md
 pages/Git.md
 pages/Docker.md
-pages/Repositories_VOserver.md
-pages/Repositories_Zenodo.md
+pages/Repositories.md
 pages/Courses.md
 pages/OSP.md
 pages/Python.md

make_documents.py

 #!/usr/bin/python
 
 def fulltext_from_filelist(filelistname, onlystatus = ""):
-    fulltext = ""
+    fulltext = "Summary for "+filenamelist+"\n\n"
+    fulltext += "[[_TOC_]]"
+    overview = {"filename": [], "author": [], "status": []}
     with open(filelistname, "r") as f:
         infilename = f.readline().rstrip("\n")
         while infilename:
             with open(infilename, "r") as ftext:
                 addtext = ftext.read()
-                #info = yaml.load(addtext[addtext.find("---")+3:addtext.find("---", 5)])
+                infotext = addtext[addtext.find("---")+3:addtext.find("---", 5)].split("\n")
+                status, author = "", ""
+                for line in infotext:
+                    if line.find("status:")> -1:
+                        status = line[9:len(line)]
+                    if line.find("Author")> -1:
+                        author = line[9:len(line)]
                 takeit = True
-                '''if onlystatus:
+                if onlystatus:
                     takeit = False
-                    if "status" in info:
-                        if info["status"] == onlystatus:
-                            takeit = True'''
+                    if status:
+                        if status == onlystatus:
+                            takeit = True
                 if takeit:
                     fulltext += addtext[addtext.find("---", 5)+3:len(addtext)] + "\n"
+                overview["filename"].append(infilename)
+                overview["author"].append(author)
+                overview["status"].append(status)
             infilename = f.readline().rstrip("\n")
-    return fulltext
+            
+    return fulltext, overview
 
-deliverable_description = fulltext_from_filelist("filelist_D4-8.txt")
+deliverable_description, status1 = fulltext_from_filelist("filelist_D4-8.txt")
 
 with open("Deliverable_4-8.md", "w") as f:
     f.write(deliverable_description)
 
-deliverable_manuals = fulltext_from_filelist("filelist_D4-9.txt")
+deliverable_manuals, status2 = fulltext_from_filelist("filelist_D4-9.txt")
 
 with open("Deliverable_4-9.md", "w") as f:
     f.write(deliverable_manuals)
 
+with open("statuspage.md", "w") as f:
+    status = "## Current page status\n\n"
+    status += "| Filename | Author | Status |\n"
+    status += "| -------- | ------ | ------ |\n"
+    for stats in (status1, status2)
+    for i in range(len(stats["filename"])):
+        status += "| " + stats["filename"] \
+                + " | " + stats["author"] \
+                + " | " + stats["status"] + " |\n"
+    f.write(status)
+
     

pages/Courses.md

@@ -5,6 +5,7 @@ Topics:
   - summary on education center (from D4.10)
   - summary on webinar
   - How to use the webinar materials
+status: unedited
 ---
 
 Please add links and summary to open courses in edu portal

pages/Dataformats.md

@@ -4,35 +4,13 @@ Author: Jutta
 status: dump
 ---
 
-# Open data formats
+## Open data products
 
-## Neutrino sets in the VO
+### Neutrino sets in the VO
 
-Tabulated high-level neutrino event data can be provided through the VO
-registry, utilizing access protocols like the Table Access Protocol
-(TAP) and query languages like the Astronomical Data Query Language
-(ADQL). To query these data sets related to astronomical sources, the
-Simple Cone Search (SCS) protocol allows to pick specific events
-according to particle source direction, using Unified Content
-Descriptors (UCDs) to identify the relevant table columns. The
-underlying data format is the VOTable which allows for metadata
-annotation of data columns. As the DaCHS software provides input
-capabilities for various formats like FITS\footnote{Flexible Image
-  Transport System, \url{https://fits.gsfc.nasa.gov/}.} or text-based
-tables on the server side, a common KM3NeT open event table format
-can be chosen quite independently and the interface adapted such that high-level neutrino data
-sets can be both offered through the VO and alternative access
-protocols, as long as the required metadata description is handled
-adequately.
 
-VO standards are at the current stage not fully adapted
-to the inclusion of neutrino data and require development of metadata
-standards for easy interpretability of the data, a matter which is targeted within the ESCAPE project. Open questions in this regard are the linkage of observation probabilities to a given event selection, the inclusion of ``non-observation'' in a given field of view
-and within a given time as relevant scientific information to retrieve
-from the services, and the introduction of a dedicated vocabulary for the
-description of neutrino data. This vocabulary will need to be developed within KM3NeT as a matter of internal standardization, however, the process will draw guidance from the VO expertise and framework.
 
-## Multimessenger alerts
+### Multimessenger alerts
 
 Single or stacked neutrino events of high astrophysical signal probability will be selected in KM3NeT to trigger an alert to other observatories indicating a
 possible target for multimessenger observations \cite{MM}. The

pages/Datamodels.md

@@ -4,6 +4,7 @@ Author: Jutta
 Topics:
   - data models
   - configurations for software
+status: dump
 ---
 
 * Started collection of metadata definitions (from publication level), based on standards of e.g. W3C, IVOA, DataCite etc.

pages/Dataserver_api.md

 ---
 Title: KM3NeT server REST API
 Author: Jutta
+status: unedited
 ---

pages/Detector.md

 ---
 Title: Detector and Data Taking
 Author: Jannik
-
+status: draft
 Comment: Mainly based on LoI
 ---
 

pages/Docker.md

@@ -5,4 +5,5 @@ Title:
   - short description
   - software interoperability
   - archiving of software
+status: unedited
 ---

pages/ESCAPE.md

 ---
 Title: ESAP & ESCAPE
 Author: Jutta
+status: dump
 ---
+
+## Further integration with the Virtual Observatory
+
+VO standards are at the current stage not fully adapted
+to the inclusion of neutrino data and require development of metadata
+standards for easy interpretability of the data, a matter which is targeted within the ESCAPE project. Open questions in this regard are the linkage of observation probabilities to a given event selection, the inclusion of ``non-observation'' in a given field of view and within a given time as relevant scientific information to retrieve from the services, and the introduction of a dedicated vocabulary for the description of neutrino data. This vocabulary will need to be developed within KM3NeT as a matter of internal standardization, however, the process will draw guidance from the VO expertise and framework.

pages/FAIR.md

@@ -4,6 +4,7 @@ Author: Jutta
 Topics:
   - Policy basics
   - dedication to open science
+status: dump
 ---
 
 ## Publishing FAIR data

pages/Git.md

@@ -5,6 +5,7 @@ Title:
   - use for software, plots and analysis
   - integration to github
   - Documentation on Git & automatic software docs
+status: dump
 ---
 
 KM3NeT uses GitLab as the main platform to develop and discuss software,

pages/Infrastructure.md

@@ -3,5 +3,12 @@ Title: Architecture overview
 Author: Jutta
 Topics:
   - servers, repositories, webpages
+status: dump
 ---
 
+## Platforms for Open Science
+
+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.
+

pages/KM3NeTserver.md

 ---
 Title: KM3NeT server
 Author: Jutta
+status: dump
 ---
 
 * For all data not publishable through the IVOA, serving as interface and/or server to the data

pages/Multimessenger.md

@@ -4,4 +4,5 @@ Author: Feifei
 Topics:
   - alert types
   - short description of the system
+status: unedited
 ---

pages/OSP.md

@@ -4,6 +4,7 @@ Author: Jutta
 Topics:
   - installation
   - interface through software
+status: dump
 ---
 
 * Git project serving webpage (Gitbook)

pages/Procedures.md

@@ -4,6 +4,7 @@ Author: Kay, Jutts
 Topics:
     - data/software releases
     - publication procedures
+status: dump
 ---
 
 ## Establishing the Open Science Committee

pages/Processing.md

 ---
 Title: Processing overview
 Author: Jutta
+status: dump
 ---
 
 Data processing therefore follows a tier-based approach \cite{km3comp}, where initial

pages/Python.md

@@ -4,6 +4,7 @@ Authors: Tamas, Jutta
 Topics:
   - installation
   - interface through software
+status: dump
 ---