Data Validation Web Service - Revision history

Mnelson: /* HTTP Headers */

2022-12-21T12:49:49Z

‎HTTP Headers

Mnelson: /* HTTP Headers */

2022-12-21T12:39:11Z

‎HTTP Headers

Mnelson: /* Data Formats */

2022-09-29T08:59:20Z

‎Data Formats

Mnelson: /* Data Formats */

2022-09-29T08:58:37Z

‎Data Formats

Mnelson: /* Data Formats */

2022-09-29T08:52:12Z

‎Data Formats

Mnelson: /* HTTP Headers */

2022-09-29T08:52:05Z

‎HTTP Headers

Plazarou: /* Response */

2020-10-07T10:28:50Z

‎Response

Mnelson: /* HTTP Headers */

2020-08-18T20:43:52Z

‎HTTP Headers

Mnelson: /* HTTP Headers */

2020-08-18T20:43:39Z

‎HTTP Headers

Mnelson: /* HTTP Headers */

2020-03-19T09:49:41Z

‎HTTP Headers

@@ Line 31: / Line 31: @@
 |-
 !|HTTP Header || Purpose || Allowed Values
 |-
 |style="background-color:#eaecf0"|<b>Data-Format</b>|| Used to inform the server when the data is in CSV format. ||csv;delimiter=[delimiter]
@@ Line 67: / Line 75: @@
 ||Boolean (true/false)
 |-
 |style="background-color:#eaecf0"|<b>Zip</b><p style="font-size:0.85em">(Since v9.8)</p>||Optional. Compresses the output as a zip file.  If used in conjunction with <b>Inc-Valid</b> or <b>Inc-Invalid</b> the zip will contain multiple files.

@@ Line 69: / Line 69: @@
 |-
 |style="background-color:#eaecf0"|<b>Accept</b><p style="font-size:0.85em">(Since v9.8)</p>||<p>Optional. Instructs the service which data output format to output the valid or invalid datasets in.
 </p>
-<p>This Header is only used if Inc-Valid or Inc-Invalid are set to true.</p>
+<p>'''Note''': This Header is only used if Inc-Valid or Inc-Invalid are set to true.</p>
 ||[[Data_Formats|See Accept Formats]]
 |-

@@ Line 25: / Line 25: @@
 = Data Formats =
-The Fusion Registry supports the following data input formats
+See [[Data_Load_Formats|Data Load Formats]]
 = HTTP Headers =

@@ Line 25: / Line 25: @@
 = Data Formats =
-The validation web service will validate data in many formats, including:
+The Fusion Registry supports the following data input formats
 * [[SDMX-ML_Structure_Specific_Data|SDMX-ML Structure Specific]]
 * [[SDMX-ML_Generic_Data|SDMX-ML Generic Data]]
 * [[SDMX-JSON_Data|SDMX-JSON v1.0]]
 * [[SDMX-CSV|SDMX-CSV v1.0, v2.0]]
 * [[Fusion-Excel_Default|Excel (default)]]
 * [[Excel_Reporting_Template_Data_Format|Excel Report Template]]
 = HTTP Headers =

@@ Line 31: / Line 31: @@
 * [[SDMX-JSON_Data|SDMX-JSON v1.0]]
 * [[SDMX-CSV|SDMX-CSV v1.0, v2.0]]
-* [[Fusion-Excel_Default|Excel (default)]
+* [[Fusion-Excel_Default|Excel (default)]]
 * [[Excel_Reporting_Template_Data_Format|Excel Report Template]]

@@ Line 23: / Line 23: @@
 <p><b>500</b> - Server Error</p>
 |}
 = HTTP Headers =

@@ Line 84: / Line 84: @@
 <p>
 The validation output contains both human readable error descriptions, as well as machine processible locations of the errors within the dataset.  The location in the dataset is described as a key or observation locator in the format; A:UK:M:2008 – where each component relates to the Dimension value, separated by a colon.  If the error position is observation, the last part of the key is the observation time period.</p>
 <p>There are 3 types of output that can be produced which share a common structure: unable to parse input(returns HTTP 400); able to parse input but references invalid data structure (returns HTTP 200); parsed input and returns output, which may have validation errors (return HTTPS 200). Below are examples of each:</p>
@@ Line 178: / Line 180: @@
            "Errors": [
+             {
                "Message": "Disallowed Dimension Value: REF_AREA=AFR",
                "Dataset": 0,
@@ Line 191: / Line 194: @@
            "Errors": [
+           {
              "Message": "Dimension 'VARIABLE' is reporting value 'AA' which  is not a valid representation in referenced Codelist 'OECD:CL_HIGH_AGLINK_2011_VARIABLE(1.0)'",
              "Dataset": 0,
@@ Line 199: / Line 203: @@
            },
+           {
              "Message": "Error in Primary Measure 'OBS_VALUE': Reported value 'XXX' is not of expected type 'Double'",
              "Dataset": 0,

@@ Line 41: / Line 41: @@
 <p>This information may be present in the header of the dataset, if provided this value will override the value in the dataset.</p>
-<p>Fusion Registry v10.4.7 accepts a comma separated list of URNs if multiple datasets exist in the loaded file, however if multiple URNs are provided, URN must be of a Dataflow or Provision Agreement and the datasets must identify at a minimum the Data Structure that is needed to read the file.</p>
+<p>Fusion Registry v10.4.7 onwards accepts a comma separated list of URNs if multiple datasets exist in the loaded file, however if multiple URNs are provided, URN must be of a Dataflow or Provision Agreement and the datasets must identify at a minimum the Data Structure that is needed to read the file.</p>
 || Valid SDMX URN for Provision Agreement, Dataflow, or Data Structure Definition

@@ Line 40: / Line 40: @@
 |style="background-color:#eaecf0"|<b>Structure</b> || <p>(optional) Provides the structure to validate the data against.</p>
-<p>This is optional as this information may be present in the header of the DataSet.  If provided this value will override the value in the dataset (if present).</p>
+<p>This information may be present in the header of the dataset, if provided this value will override the value in the dataset.</p>
 || Valid SDMX URN for Provision Agreement, Dataflow, or Data Structure Definition
 |-