Skip to content
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -9,3 +9,4 @@ pages/Integrating New Platforms to EarthCODE/.DS_Store
pages/public/img/.DS_Store
pages/public/img/platforms/.DS_Store
pages/public/img/terms/.DS_Store
.vscode
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Help us maintain an organized forum by:

Use the EarthCODE portal to find and access published experiments, products, data or workflows and join discussions. From there, you have the ability to either contribute to the existing topic about the item or start a new one.

When using the EarthCODE Catalog:
When using the Open Science Catalog:

* Use the "Discuss This" feature to start forum discussions directly from catalog items
* Topics created this way will be automatically tagged with relevant metadata
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ When you log in, you’ll find the following categories in Discourse:
| **EarthCODE Architecture** | Technical standards and development |
| **Technical Support** | Technical support for EarthCODE and platforms |
| **Training and Resources** | Tutorials and best practices |
| **Data & Workflows** | Dataset and workflow discussions (autogenerated from the EarthCODE Catalog) |
| **Data & Workflows** | Dataset and workflow discussions (autogenerated from the Open Science Catalog) |
| **Community Engagement** | Events and recognition |
| **Feedback and Suggestions**| Feedback on how to improve EarthCODE |

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ order: 2

Finding content on the **EarthCODE Discourse forum** is key to making the most of the platform and avoiding duplication of the same questions. Before posting about a topic, follow these three steps:

## 1. Use the EarthCODE Catalog
## 1. Use the Open Science Catalog

If you are looking for a discussion about a particular item on the Open Science Catalog, you can see all the linked topics about that particular item on its open science catalog webpage.

Expand Down Expand Up @@ -92,15 +92,15 @@ For more formatting tips, [try this 10-minute markdown tutorial](https://commonm
Posting on the **EarthCODE Discourse forum** is straightforward, but following a few best practices ensures discussions remain relevant and organized.

You can start discussions about a variety of topics such as:
- Sharing datasets from Open Science Data Catalogue, discussing yours or others' project’s results and new ideas.
- Sharing datasets from Open Science Catalogue, discussing yours or others' project’s results and new ideas.
- Discussing platforms which will be integrated to EarthCODE, their features, and how to make the most out of them.
- Ask a question, share a resource (training, blog, article), or just share something relevant you’re passionate about
- Discuss an event, gathering or other community engagement
- Give feedback and suggestions about the EarthCODE and any features you would like to have
- Ask for technical support and post about issues you're facing


When posting about a dataset, workflow, or experiment in the EarthCODE Catalog, you can make contributions to improve reusability, quality or share constructive ideas to start a conversation about the item. You could start discussions about:
When posting about a dataset, workflow, or experiment in the Open Science Catalog, you can make contributions to improve reusability, quality or share constructive ideas to start a conversation about the item. You could start discussions about:
- Missing or incomplete metadata (e.g. missing spatial/temporal coverage, provenance details, variable definitions)
- Feedback on data quality (e.g. unexpected values, data gaps, inconsistencies)
- Questions about the methodology used to generate the product
Expand Down Expand Up @@ -130,9 +130,9 @@ When no relevant discussion exists, create a new topic. Follow these steps:

By following these guidelines, you help keep the forum organized, useful, and welcoming for all users.

**Starting a Discussion About an Item in the EarthCODE Catalog**
**Starting a Discussion About an Item in the Open Science Catalog**

If your discussion relates to an item in the **EarthCODE Catalog**, it’s best to use the [integrated features on the catalog](../../Technical%20Documentation/Data/Discovering%20Resources%20in%20The%20EarthCODE%20Catalog.md#start-discussions-directly-from-the-catalog):
If your discussion relates to an item in the **Open Science Catalog**, it’s best to use the [integrated features on the catalog](../../Technical%20Documentation/Data/Discovering%20Resources%20in%20The%20EarthCODE%20Catalog.md#start-discussions-directly-from-the-catalog):
1. Navigate to the catalog and locate the item.
2. Use the **"Start a new topic on the EarthCODE forum"** button.

Expand All @@ -153,7 +153,7 @@ Discourse includes a **chat feature** that allows you to connect directly with o
2. Start a chat directly from their profile on a post.
![onebox-paste-link](/img/discourse/chatfrompost.gif)

For example, you could find an interesting item in the EarthCODE catalog and want to ask the researcher who published it some questions. If they are registered on Discourse, you can search for them by name and send them a direct message.
For example, you could find an interesting item in the Open Science catalog and want to ask the researcher who published it some questions. If they are registered on Discourse, you can search for them by name and send them a direct message.


## Chat Etiquette
Expand Down
25 changes: 13 additions & 12 deletions pages/Getting started with EarthCODE/10 minutes to EarthCODE.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Go to the [**Open Science Catalog**](https://opensciencedata.esa.int/) to start
## Choosing a Platform
EarthCODE provides you *single‑sign‑on* access to a growing number of EO platforms that host EO data, development tools and compute. Once you log in with your EarthCODE account, you carry the same identity across the **EarthCODE Portal**, the **EarthCODE Forum**, each **integrated platform**, and the **Open Science Catalog**.

For all of the EarthCODE integrated platforms, you can apply for Network‑of‑Resources (NoR) sponsorship to cover compute costs. Every platform comes with FAIR tooling that lets you publish results to the Open Science Catalog in an automated manner. Additionally, some platforms support creating and executing several types of workflows, which means that if you develop a workflow on them, it will be cross-compatible with other platforms.
For all of the EarthCODE integrated platforms, you can apply for Network‑of‑Resources (NoR) sponsorship to cover compute costs. Every platform comes with FAIR tooling that lets you publish results to the Open Science Catalog in an automated manner. Additionally, some platforms support creating and executing several types of workflows, which means that if you develop a workflow on them, it will be cross-compatible with other platforms supporting the same type of workflow.

![EarthCODE Platform](/img/terms/earthcode-platfrom-generic.svg)

Expand All @@ -86,12 +86,12 @@ Each platform provides a variety of EO data stored on the cloud and expose acces
---

### Workflow Development
EarthCODE platforms differ in interface and how you build and run algorithms: some offer visual process designers, others provide Jupyter Notebooks with extensions, and several combine both. For example OpenEO provides both the OpenEO API and a graphical interface. Many platforms also ship pre‑configured machine‑learning environments and ready‑made domain algorithms. Pick the platform whose tooling matches the tools you already use and project goals; cloud execution keeps everything reproducible and scalable without local setup hassles. By using platforms to develop code you can directly publish end-to-end FAIR workflows that enable users to reproduce and reuse result datasets and code.
EarthCODE platforms differ in interface and how you build and run workflows: some offer visual process designers, others provide Jupyter Notebooks with extensions, and several combine both. For example OpenEO provides an API, a set of client libraries, supporting modern programming languages such as Python, and a graphical interface. Many platforms also ship pre‑configured machine‑learning environments and ready‑made domain workflows. Pick the platform whose tooling matches the tools you already use and project goals; cloud execution keeps everything reproducible and scalable without local setup hassles. By using platforms to develop code you can directly publish end-to-end FAIR workflows that enable users to reproduce and reuse result datasets and code.

<!-- :::tip Note to self turn this to a gif of how the editor produces something
::: -->
![OpenEO Editor](/img/terms/open_eo_save_process.png)
*Open EO Process Editor GUI*
![OpenEO Web Editor](/img/terms/open_eo_save_process.png)
*OpenEO Web Editor GUI*

---

Expand Down Expand Up @@ -137,11 +137,12 @@ Platforms differ in how they let you visualize published results from others and

Visit the [Working with Platforms](../Technical%20Documentation/Platforms/) page to explore EarthCODE platform and for help to choose the platform that best suits your research objectives.

## Exploring the EarthCODE Open Science Catalog
After completing your research and preparing your final results for journal publication, your validated data products and code can be published in the EarthCODE Catalog — the [Open Science Catalog](https://opensciencedata.esa.int/). Only finalized outputs that are ready for publication and long-term storage should be submitted. The catalog includes datasets, workflows, and software that follow EarthCODE best practices, most of which originate from integrated platforms. It's your gateway to a wide range of reusable scientific resources, from environmental data to executable workflows.ß
## Exploring the Open Science Catalog
After completing your research and preparing your final results for journal publication, your validated data products and code can be published in the [Open Science Catalog](https://opensciencedata.esa.int/). Only finalized outputs that are ready for publication and long-term storage should be submitted. The catalog includes datasets, workflows, and software that follow EarthCODE best practices, most of which originate from integrated platforms. It's your gateway to a wide range of reusable scientific resources, from environmental data to executable workflows.

### Validating and Publishing Data to the Catalog {#publishing-anchor}

EarthCODE allows you to validate products and experiments, ensuring they meet reproducibility and scientific standards. If you have an ESA-funded project, you can contribute to the platform by publishing your datasets, software, or experiments, making your work available for the broader community to use.
EarthCODE allows you to validate products, workflows and experiments, ensuring they meet reproducibility and scientific standards. If you have an ESA-funded project, you can contribute to the platform by publishing your datasets, workflows, or experiments, making your work available for the broader community to use.

#### How data is published
The [Open Science Catalog](https://opensciencedata.esa.int/) is built on the [SpatioTemporal Asset Catalog (STAC)](https://stacspec.org/en), a standardised format for describing geospatial data. To contribute your research, you need to create valid STAC objects and commit them to the [`open-science-catalog-metadata-staging`](https://github.com/EOEPCA/open-science-catalog-metadata-staging) repository on GitHub. These STAC objects, stored as JSON files, will be automatically processed and rendered in the catalog.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the publishing happen to the staging environment? If so and if my understanding is correct, their records will only be visualised in the staging catalog. If correct, it should be clear to the reader that this is not rendered in the main catalogue.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, this should be changed to the production repository URL.

Expand All @@ -166,15 +167,15 @@ You can read more on how to publish data in the [Uploading Your Data](../Technic
#### Best Practices
EarthCODE makes FAIR publishing the default. Scientists are expected to:

- Deliver publication‑ready outputs: final datasets, workflows, and models, kept in persistent cloud storage with open, clearly stated licences.
- Deliver publication‑ready outputs: final datasets, workflows, and models, kept in persistent cloud storage with open, clearly stated licenses.
- Attach rich, standards‑based metadata: STAC/ISO 19115 descriptions with DOIs, spatial‑temporal extents, provenance, and links to source data and code.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the user provide DOIs or is this done by EarthCODE? -> mentioned on line 196

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the user already has a DOI it should be reused. If none is available EarthCODE will automatically during publishing provide one.

- Maintain reproducibility: specify software environments, parameters, and lineage, ensuring others can rerun and verify results.

These practices align with the FAIR pillars:

| Findable | Accessible | Interoperable | Reusable |
|----------|------------|---------------|----------|
| DOIs, indexed metadata | HTTPS, STAC & OGC APIs | NetCDF, GeoTIFF, Zarr, CF vocabularies | Open licences, provenance, community standards |
| DOIs, indexed metadata | HTTPS, STAC & OGC APIs | NetCDF, GeoTIFF, Zarr, CF vocabularies | Open licenses, provenance, community standards |

For detailed guide on best practices refer to the [Best Practices Page](../Community%20and%20Best%20Practices/).

Expand All @@ -191,7 +192,7 @@ EarthCODE integrates FAIR tools and standards at every stage of the research lif
| **Development** | EarthCODE provides integrated platforms that provide different options for developing scientific workflows |
| **Data, Workflows and Platforms** | EarthCODE describes Data, workflows and platforms as FAIR objects. All items published on the Open Science Catalog follow EarthCODE metadata standards (STAC, OGC) for consistency across platforms and tools. |
| **EarthCODE Standard Variable Dictionary** | Shared [vocabulary](https://opensciencedata.esa.int/variables/catalog) for EO variables to ensure semantic consistency across datasets and workflows. |
| **Publishing Automation** | EarthCODE platforms provide automation to support publishing of finalized data and workflows to the EarthCODE catalog |
| **Publishing Automation** | EarthCODE platforms provide automation to support publishing of finalized data and workflows to the Open Science Catalog |
| **Publishing and Maintenance**| Users can maintain (or publish) FAIR data and workflows through the EarthCODE publishing GUI. |
| **Data Storage** | EarthCODE provides persistent cloud storage via ESA PRR which ensures accessibility and long-term preservation. |
| **Finding Products and Workflows** | The Open Science Catalog makes metadata discoverable via STAC API and its webpage search. |
Expand All @@ -202,9 +203,9 @@ EarthCODE integrates FAIR tools and standards at every stage of the research lif
| **Re-Using Workflows** | Users can directly re-use published workflows on the platform used to develop them, compatible platforms (or locally). |
| **Code Quality** | Automated pipelines integrate linting, code quality checking and recommendation, and security scanning to ensure code is robust and reusable. |
| **Reproducibility** | Published workflows are described in full as experiments, where you have information about inputs and configurations. EarthCODE provides the means to directly execute these experiments and reproduce data products. |
| **Intraoperability** | Shared metadata schemas and API protocols ensure you can execute worklows across platforms and published daat on EarthCODE follows common standards (Zarr, NetCDF) with standard variables (e.g. CF-Conventions). |
| **Intraoperability** | Shared metadata schemas and API protocols ensure you can execute workflows across platforms and published data on EarthCODE follows common standards (Zarr, NetCDF) with standard variables (e.g. CF-Conventions). |
| **Visualisation and Findability** | Dashboards and linked visual previews make datasets easier to interpret and explore. |
| **Contacts and Communication**| Published items have contact details in the metadata, EarthCODE additionally provides a chat functionallity in Discourse to connect and discuss. |
| **Contacts and Communication**| Published items have contact details in the metadata, EarthCODE additionally provides a chat functionality in Discourse to connect and discuss. |
| **Community** | Discourse forum, with published items linked directly to posts, and best practice documentation foster open collaboration. |


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,9 @@ Google Earth Engine is not yet one of the integrated EarthCODE platforms, and th
</details>

<details>
<summary><strong>Can I publish pretrained models or anonymised data?</strong></summary>
<summary><strong>Can I publish pre-trained models or anonymized data?</strong></summary>

Yes. The FAIR principles do **not** require assets to be fully open, so you may publish pretrained models or anonymised datasets. Wherever possible, include a small sample dataset to help others reproduce and validate your workflow.
Yes. The FAIR principles do **not** require assets to be fully open, so you may publish pre-trained models or anonymized datasets. Wherever possible, include a small sample dataset to help others reproduce and validate your workflow.
</details>

<details>
Expand Down
Loading