POST /data/status/update/

[PGijsbers]

[PGijsbers]

Mostly implemented but not covered by migration tests, see also #119

[PGijsbers]

We need to determine an effective test strategy (or decide not to do migration tests for this endpoint).

[omosola]

Functionality:

Change the status of a dataset to either 'active' or 'deactivated'
Upon success, returns the ID of the updated dataset and the new status

Legacy Reference (PHP):

PHP POST /data/status/update implementation

Request Parameters:

• data_id: (required) integer - ID of the dataset
• status: (required) string - the status on which to filter the results, either 'active' or 'deactivated'
• api_key: (required) string - API key to authenticate the user

Tables touched:

Dataset, Dataset_status

Success Response:

ID of the updated dataset

{
    "data-status-update": {
         "did": "2",
         "status": "active",
     }
}

Swagger API Documentation Reference:

Swagger POST /data/status/update

Concerns/Discussion topics:

None specific to this endpoint listed 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.