Asynchronous Data Validation and Transformation - Revision history

Plazarou: /* Data Load Response */

2024-02-16T15:38:34Z

‎Data Load Response

Plazarou: /* Load Status Response */

2024-02-16T15:21:23Z

‎Load Status Response

Plazarou: /* Data Load Response */

2024-02-16T15:19:53Z

‎Data Load Response

Mnelson: /* Data export/transform */

2021-01-08T09:09:51Z

‎Data export/transform

Mnelson: /* Revalidate */

2020-08-05T12:37:46Z

‎Revalidate

Mnelson: /* Revaidate */

2020-08-05T12:29:51Z

‎Revaidate

Mnelson: /* Revaidate */

2020-08-05T12:28:43Z

‎Revaidate

Mnelson: /* Revaidate */

2020-08-05T12:26:44Z

‎Revaidate

Mnelson: /* Data export/Transform */

2020-08-05T12:22:12Z

‎Data export/Transform

Mnelson at 09:18, 29 April 2020

2020-04-29T09:18:44Z

@@ Line 34: / Line 34: @@
+  {
-   "Success" : true,
+    "Success" : true,
-     "uid"    : "unique token"
+     "uid"     : "unique token"
+  }

@@ Line 73: / Line 73: @@
 | Validating || The dataset is being validated
 |-
-| Complete || The dataset validation process has finished, there may/man not be errors
+| Complete || The dataset validation process has finished, there may/may not be errors
 |-
 | Consolidating || The dataset is being consolidated, duplicate series and observations are being merged into one final dataset

@@ Line 31: / Line 31: @@
 == Data Load Response ==
-The response to a data load is a token, which can be used in subsequent calls to track the data load and validation process and, once validation is complete, the token can be used to perform actions such as a pulish, obtain validation report, export in a different format, or export with mapping.
+The response to a data load is a token, which can be used in subsequent calls to track the data load and validation process and, once validation is complete, the token can be used to perform actions such as a publish, obtain validation report, export in a different format, or export with mapping.
+  {

@@ Line 95: / Line 95: @@
 |style="background-color:#eaecf0"|<b>Http Method</b>|| GET
 |-
-|style="background-color:#eaecf0"|<b>Response Format</b>|| Determined by [[HTTP_Accept_Headers|Accept Header]]
+|style="background-color:#eaecf0"|<b>Response Format</b>|| Determined by [[Data_Formats#HTTP_Accept_Headers|Accept Header]]
 |}

@@ Line 129: / Line 129: @@
 =  Revalidate =
-A Re-validation service is provided if there is more information that can be provided to the dataset(s) loaded against the token, this may include if the Dataflow or Provision Agreement link changes which may result in a different set of Constraints to be applied on validation.  If a structure is linked to a different Dataflow or Provision Agreement, this link information will be included in the exported dataset if it is in a format which supports it.
+A Re-validation service is provided if there is more information that can be provided to the dataset(s) loaded against the token.  The reason to revalidate is if the dataset is to be attached to a different Dataflow or Provision Agreement.  When this link changes, it may impact the validation results due to the application of different Constraints or Validation Schemes.  The underlying datasaet will be updated to refer to this different Dataflow/.Provision Agreement, which will be reflected in the exported dataset if the data format supports this information (for example SDMX-ML contains the linked structure in the Header section of the dataset).
 Revalidation is an asynchronous action, whose progress can be tracked using the same token and tracking web services provided.
 {| class="wikitable"
 |-
@@ Line 141: / Line 144: @@
 |-
 |style="background-color:#eaecf0"|<b>Response Format</b>|| JSON
 |-
 |style="background-color:#eaecf0"|<b>Accepts</b>|| JSON

@@ Line 128: / Line 128: @@
 |}
-=  Revaidate =
+=  Revalidate =
-A Re-validation service is provided if there is more information that can be provided to the dataset(s) loaded against the token, this may include if the Dataflow or Provision Agreement link changes which may result in a different set of Constraints to be applied on validaiton.  If a structure is linked to a different Dataflow or Provision Agreement, this link information will be included in the exported dataset if it is in a format which supports it.
+A Re-validation service is provided if there is more information that can be provided to the dataset(s) loaded against the token, this may include if the Dataflow or Provision Agreement link changes which may result in a different set of Constraints to be applied on validation.  If a structure is linked to a different Dataflow or Provision Agreement, this link information will be included in the exported dataset if it is in a format which supports it.
 Revalidation is an asynchronous action, whose progress can be tracked using the same token and tracking web services provided.
@@ Line 149: / Line 149: @@
 |style="background-color:#eaecf0"|<b>Response Format</b>|| JSON
 |-
-|style="background-color:#eaecf0"|<b>Response Statuses</b>|| <p><b>200</b> - request recieved and being processed</p>
+|style="background-color:#eaecf0"|<b>Response Statuses</b>|| <p><b>200</b> - request received and being processed</p>
 <p><b>400</b> - request could not be performed (possibly due to bad syntax of JSON POST)</p>
 <p><b>401</b> - Unauthorized (if access has been restricted)</p>
@@ Line 156: / Line 156: @@
 == Post Body ==
-The POST request must contain the token of the dataset to revalidate, this is the same token that was provided by the server on data load.  The SRef is an array of URNs, one for each Dataset that was present in the data file loaded to the server.  Each URN refers to which structure to use to validate the daaset against.  The URN can either be to a Data Structure Definition, Dataflow, or Provision Agreement.
+The POST request must contain the token of the dataset to revalidate, this is the same token that was provided by the server on data load.  The SRef is an array of URNs, one for each Dataset that was present in the data file loaded to the server.  Each URN refers to which structure to use to validate the dataset against.  The URN can either be to a Data Structure Definition, Dataflow, or Provision Agreement.
+  {
     UID : "datasetdetailsuid",
@@ Line 163: / Line 163: @@
 == Revalidate Response ==
-The response is a JSON message with a sucess message.  The validation progress should be tracked using the token that was used in the re-validation request against the [[Asynchronous_Data_Validation_and_Transformation#Request_Load_Status|Load Status]] web service.
+The response is a JSON message with a success message.  The validation progress should be tracked using the token that was used in the re-validation request against the [[Asynchronous_Data_Validation_and_Transformation#Request_Load_Status|Load Status]] web service.
+  {

@@ Line 143: / Line 143: @@
 |}
-== Post Parameters ==
+== Post Body ==
 = Data Publish =

@@ Line 86: / Line 86: @@
 |}
-=  Data export/Transform =
+=  Data export/transform =
 {| class="wikitable"
 |-
@@ Line 127: / Line 127: @@
 || If the map parameter is supplied, and some series or observation can not be mapped, the unmapped data will be included in either the zip file (if zip is true) or in a multipart-form boundry (if zip is false)
 |}
 = Data Publish =

@@ Line 1: / Line 1: @@
 [[Category:WebService]]
 = Asynchronous Data Load =
 {| class="wikitable"