Propose an issue through webforms

Unauthenticated users can help populate the errata database by creating issues and submitting them to moderators to validate and persist for all users to see. The process is very similar to creating issues as a poweruser, minus the authentication bit.

Proposing an issue without authentication:

From the errata home page click on the propose button in the right side of the top menu
Fill the form following the (strict) set of requirements
- The project is mandatory and value controlled
- A title between 16 and 255 characters is mandatory Warning: you will not be able to change the project and title again.
- A description between 16 and 1023 characters is mandatory. A precise and conise issue description that must make sense for end-users (not just "wrong data") is highly recommended.
- The severity is mandatory and value-controlled, the field is a drop menu choice in any case. Note: The possible values for severity are: - low: issue concerning file management (e.g. addition, removal, period extension etc..) - medium: issue concerning metadata (NetCDF attributes) without undermining the values of the involved variable. - high: issue concerns single point variable or axis values - critical: issue concerns a varaible or axis values undermining the analysis. The use of this data is therefore strongly discouraged.
- A list of links and materials can be provided, the URLs will be checked to be valid (on validation)
- A dataset list is mandatory and will be used to extract the different identifiers of the affected datasets (experiment, variables etc) Note: A dataset identifier is a sequence of dot-separated facets that follows the Data Reference Syntax of the corresponding project. The dataset identifiers has to append the dataset version number. If one of the dataset ID is malformed or if the dataset list is empty, the form will raise an error.

Click on "Save" button on the upper menu
The request will be processed, fields need to be validated against the set of rules and controlled vocabulary (using pyessv).
If everything checks out, a success message is displayed, user is then redirected to the issue landing page (the URL can be shared and broadcasted), the issue is persisted in the database, accessible through an URL but unlisted from the index page pending review.
If an anomaly is detected, an error message is displayed with the cause of the error.

Few notes:

Moderators will have up to 14 days to make a decision about the proposed errata, passed that time, the issue is automatically published.
There might be a need for the issue creator and the moderator to discuss details and/or clarify the issue, this is not within the perimeter of the errata service and there is no discussion platform à la github. Moderators can get in touch with the issue authors via email.

PreviousCreate an issue through webforms NextUpdate an issue through webforms

Last updated 7 months ago

Proposing an issue without authentication:

From the errata home page click on the propose button in the right side of the top menu

Fill the form following the (strict) set of requirements

The project is mandatory and value controlled
A title between 16 and 255 characters is mandatory Warning: you will not be able to change the project and title again.
A description between 16 and 1023 characters is mandatory. A precise and conise issue description that must make sense for end-users (not just "wrong data") is highly recommended.
The severity is mandatory and value-controlled, the field is a drop menu choice in any case. Note: The possible values for severity are: - low: issue concerning file management (e.g. addition, removal, period extension etc..) - medium: issue concerning metadata (NetCDF attributes) without undermining the values of the involved variable. - high: issue concerns single point variable or axis values - critical: issue concerns a varaible or axis values undermining the analysis. The use of this data is therefore strongly discouraged.
A list of links and materials can be provided, the URLs will be checked to be valid (on validation)
A dataset list is mandatory and will be used to extract the different identifiers of the affected datasets (experiment, variables etc) Note: A dataset identifier is a sequence of dot-separated facets that follows the Data Reference Syntax of the corresponding project. The dataset identifiers has to append the dataset version number. If one of the dataset ID is malformed or if the dataset list is empty, the form will raise an error.

Click on "Save" button on the upper menu

The request will be processed, fields need to be validated against the set of rules and controlled vocabulary (using pyessv).

If everything checks out, a success message is displayed, user is then redirected to the issue landing page (the URL can be shared and broadcasted), the issue is persisted in the database, accessible through an URL but unlisted from the index page pending review.

If an anomaly is detected, an error message is displayed with the cause of the error.

Few notes:

Moderators will have up to 14 days to make a decision about the proposed errata, passed that time, the issue is automatically published.

There might be a need for the issue creator and the moderator to discuss details and/or clarify the issue, this is not within the perimeter of the errata service and there is no discussion platform à la github. Moderators can get in touch with the issue authors via email.