-
Notifications
You must be signed in to change notification settings - Fork 5
Description
We started the review of the Technical Documentation, with the main focus on Publishing part. Please find the first comments related to that part here:
As agreed during the Scrums of Scrums I am adding here the checkboxes to tick once the changes (that we all agree upon are implemented)
##Publishing Science Results:
-
Introduction ( I would suggest following): "The ESA Open Science Data Catalogue provides free and open access to geoscience products for any user, without the need for authorization. By promoting FAIR and Open Science principles, this catalogue invites contributions from authorized users, enriching the scientific community with a diverse array of geospatial products. Contributions from users willing to share scientific outcomes and experiments help foster collaboration, innovation, and the continuous growth of scientific knowledge."
-
- [x] Add a link to STAC official tutorial: https://stacspec.org/en/tutorials/intro-to-stac/ -
#Who can contribute?
Contributions to the Open Science Data Catalogue are vital for advancing FAIR Open Science Principles across ESA-funded Earth Science activities.
We would like to specifically encourage contributions from:
-
Principal Investigators of ESA EO (Earth Observation Programme) funded Projects,
-
Researchers, Scientists, Data Owners working on ESA-funded EO Projects,
-
Principal Investigators, Researchers and Scientists from ESA Science Cluster Projects,
-
ESA Technical Officers leading ESA EO Projects
-
ESA-ESRIN Science Hub Members (e.g. ESA post-doctoral Research Fellows, ESA Living Planet Fellowship, ESA Visiting Scientists)
-
Wider EO Research and Science Community: contact EarthCODE team for more details! [earth-code@esa.int]
-
You can enrich EarthCODE in several impactful ways:
-
Publish Research Products: Add new content to the Open Science Data Catalogue.
-
Update content: Keep the descriptions and metadata of products, projects, and more up-to-date.
-
Request removals: Ensure the catalogue remains accurate by requesting the removal of outdated or incorrect entries.
-
To contribute, you need to have an active GitHub account. If you don't have one yet, please create an account [https://github.com/signup] to get started.
-
**#Other user requirements include ** - to be removed
-
#How to Publish Results
Open Science Data Catalogue provides functionalities of data discovery and access to any user/ Earth Observation Scientist, with or without GitHub account. Open Science Data Catalogue offers easy and transparent way of accessing and exploitation of wide range of the latest EO project's results (research outcomes). Implementation of structured and harmonized way of describing result's metadata facilitates publication and data discovery process.
The Open Science Data Catalogue is built on the open-source STAC Browser application, that allows users to explore various inter-linked elements: themes, variables, eo-missions, projects, products, workflows and experiments described in format of JSON files structured in a STAC Catalog.
-
To publish your scientific outcomes you need to do following:
-
Create valid STAC and/or OGC API Record objects (in JSON format).
-
Submit a Pull Request to the open-science-catalog-metadata-staging repository with your new entry.
-
Preparing your Research For Publication
I feel this secton is exactly the repetition of the STEPS described below. We can just add one sentence such as:
"To contribute to the Open Science Catalog, your research data must be openly accessible and persistent. This can be achieved by following these 3 steps described below:"
Step 1: Make Your Data Accessible: reviews under: Technical Documentation/ Working with Data/ Publishing Science Results - STEP 1 #44
Step 2: Generate a Self-Contained STAC Catalog: Technical Documentation / Working with Data / Publishing Science Results - STEP 2 #45
Step 3: Describe Your Research in the Open Science Catalog: Technical Documentation / Working with Data / Publishing Science Results - STEP 3 #49
Each step should be the described in more details.