# ESGF Errata Service overview

The Errata Service centralizes timely information about known issues of ESGF hosted data. The errata database is populated by data providers and in the 2.0 version though community provided proposals as well. 

Proper handling of errata information in the ESGF publication workflow has major impact on the quality of data. Version changes should be documented and justified by explaining what was updated, retracted and/or removed. 

This is based on an unspoken rule that any publication of a newer version of a dataset needs to have a valid motivation, which we will refer to as an *issue*. Consequently, the publication of a new version of a dataset, as well as the unpublication of a dataset version, has to be motivated by an issue and conversely.

<mark style="color:red;">**Note:**</mark> The issue registration should be executed prior to the publication process and is ought to be mandatory for additional versions, version removal or retraction.

<figure><img src="/files/TMiusoUJOs5rNPfNZzNe" alt=""><figcaption><p>Errata Service v1.0 layout</p></figcaption></figure>

The Errata Service offers to ESGF users to query about modifications and/or corrections applied to their data in different ways:

* Through a user-friendly filtered list of ESGF known issues
* Through a search interface based on a dedicated API to get the version history of a (set of) file(s)/dataset(s)

<mark style="color:red;">**Note:**</mark> The errata service is as project-agnostic as it gets, with minimal to no back-end changes to support new projects. At the present time, CMIP5/6, CORDEX and input4MIPS are supported with future plans to include CMIP7 support.&#x20;

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ipsl.gitbook.io/esgf-errata-service/esgf-errata-service-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.