GET /data/{id}

[PGijsbers]

Get dataset description. Contains all the meta-data about the dataset, as well as links to download the formatted data.

[PGijsbers]

Metadata fields with url are currently defined as anyURI which is too lenient. References should be a URL, so that it may be resolved without context from any connected machine. Here I would propose a parse-only test, such as provided by Pydantic's HttpUrl or similar.

[PGijsbers]

All tests pass when comparing /old/datasets/{id} to /data/{id} against the test database on 2919fe2

[PGijsbers]

Not sure which properties are set by this bit:

foreach( $this->xml_fields_dataset['csv'] as $field ) {
    $dataset->{$field} = getcsv( $dataset->{$field} );
}

[omosola]

Functionality:

Returns information about a dataset. The information includes the name, information about the creator, URL to download it, and more.

Legacy Reference (PHP):

PHP GET /data/{id} implementation

Request Parameters:

• id: (required) integer - ID of the dataset

Tables touched:

Dataset, File, Dataset_tag, Dataset_description, Data_processed, Dataset_status

Success Response:

From the current implementation -

A dataset description

{
    "data-get": {
        "dataset": Dataset object..
     }
}

Swagger API Documentation Reference:

Swagger POST /data/{id}

Concerns/Discussion topics:

Concerns related to GET /{dataset_id} in Migration Notes

As a general topic for all endpoints, we want to migrate from 412 Precondition failed to 422 Unprocessable Entity for errors related to invalid input types.

Please list any additional concerns or discussion points in the comments.