Validate data - Revision history

Vmurrell at 11:27, 13 May 2024

2024-05-13T11:27:05Z

2023-10-23T12:41:57Z

‎Load Data

2023-08-14T10:19:39Z

‎Load Data

2022-11-03T11:14:25Z

2021-05-05T10:18:33Z

‎Creating the Validation Scheme from the User Interface

2021-05-05T10:15:06Z

‎How are Rules Applied

2021-05-05T10:14:21Z

‎How are Rules Applied

2021-05-05T10:13:11Z

‎How are Rules Applied

2021-05-05T10:08:28Z

‎Step 4: Expression Builder

2021-05-05T10:06:07Z

‎Step 3: CSV Import

@@ Line 40: / Line 40: @@
 '''Supported formats:'''
-* SDMX-ML (2.1 , 2.0 and 1.0)
+* SDMX-ML (3.0, 2.1 , 2.0 and 1.0)
 * EDI
 * SDMX-JSON
 * SDMX-CSV
 '''Unsupported formats:'''
 * Any other CSV format (Fusion CSV, Time Series CSV)
 * RDF, Turtle, etc.

@@ Line 31: / Line 31: @@
 Once all the elements are in place as described above, the next step is to load the data which is done via the Convert option on the Data Menu.
-Data can be loaded from a file of via a URL (for example from the Fusion Metadata Registry (FMR)  Demo site).
+Data can be loaded from a file of via a URL (for example from the SDMX Global Registry site).
 To successfully validate, the data must adhere to the SDMX standard in terms of format as well as what has been defined in the Data Structure.

@@ Line 31: / Line 31: @@
 Once all the elements are in place as described above, the next step is to load the data which is done via the Convert option on the Data Menu.
-Data can be loaded from a file of via a URL (for example from the Metadata Technology's Fusion Registry Demo site).
+Data can be loaded from a file of via a URL (for example from the Fusion Metadata Registry (FMR)  Demo site).
 To successfully validate, the data must adhere to the SDMX standard in terms of format as well as what has been defined in the Data Structure.

@@ Line 1: / Line 1: @@
 [[Category:How_To]]
 =Overview=
 To Validate data you need to have the following in place.

← Older revision		Revision as of 10:18, 5 May 2021
Line 116:		Line 116:


−	[[File:~~Valid5~~.PNG\|~~Creating a Validation Scheme\|850px~~]]<br>	+	[[File:Create Validation Scheme.PNG\|1000px]]<br>

	There are four steps to creating a Validation Scheme and are described in the following sections:		There are four steps to creating a Validation Scheme and are described in the following sections:

← Older revision		Revision as of 10:15, 5 May 2021
Line 102:		Line 102:


−	[[File:Valid4.PNG\|Rule ~~Application 3~~\|thumb\|850px]]<br>	+	[[File:Valid4.PNG\|Rule Diagram\|thumb\|850px]]<br>

	'''Note''': the Registry only checks data in the submitted file, and does not cross check against any persisted data when validating. For example, if you have already stored the totals in a Registry database, submitting a Dataset containing the values making up the totals, the Registry will not validate from the file against the totals already stored.		'''Note''': the Registry only checks data in the submitted file, and does not cross check against any persisted data when validating. For example, if you have already stored the totals in a Registry database, submitting a Dataset containing the values making up the totals, the Registry will not validate from the file against the totals already stored.

← Older revision		Revision as of 10:14, 5 May 2021
Line 102:		Line 102:


−	[[File:Valid4.PNG\|Rule Application 3\|850px]]<br>	+	[[File:Valid4.PNG\|Rule Application 3\|thumb\|850px]]<br>

	'''Note''': the Registry only checks data in the submitted file, and does not cross check against any persisted data when validating. For example, if you have already stored the totals in a Registry database, submitting a Dataset containing the values making up the totals, the Registry will not validate from the file against the totals already stored.		'''Note''': the Registry only checks data in the submitted file, and does not cross check against any persisted data when validating. For example, if you have already stored the totals in a Registry database, submitting a Dataset containing the values making up the totals, the Registry will not validate from the file against the totals already stored.

← Older revision		Revision as of 10:13, 5 May 2021
Line 102:		Line 102:


−	[[File:Valid4.PNG\|~~Diagram~~\|~~500px~~]]<br>	+	[[File:Valid4.PNG\|Rule Application 3\|850px]]<br>

	'''Note''': the Registry only checks data in the submitted file, and does not cross check against any persisted data when validating. For example, if you have already stored the totals in a Registry database, submitting a Dataset containing the values making up the totals, the Registry will not validate from the file against the totals already stored.		'''Note''': the Registry only checks data in the submitted file, and does not cross check against any persisted data when validating. For example, if you have already stored the totals in a Registry database, submitting a Dataset containing the values making up the totals, the Registry will not validate from the file against the totals already stored.

← Older revision		Revision as of 10:08, 5 May 2021
Line 184:		Line 184:


−	[[File:Valid10.PNG\|Validation Scheme - ~~Step 1~~\|800px]]<br>	+	[[File:Valid10.PNG\|Validation Scheme - Create Rule\|800px]]<br>

	As stated previously a rule must have an Id and Name and may have an optional description. The control at top-right allows the user to distinguish between a Custom Expression and a Hierarchical Expression (this choice is only available for Dimensions with a Concept that represents a Hierarchic codelist).		As stated previously a rule must have an Id and Name and may have an optional description. The control at top-right allows the user to distinguish between a Custom Expression and a Hierarchical Expression (this choice is only available for Dimensions with a Concept that represents a Hierarchic codelist).

← Older revision		Revision as of 10:06, 5 May 2021
Line 142:		Line 142:


−	[[File:Valid8.PNG\|Validation Scheme - Step 3\|~~800px~~]]<br>	+	[[File:Valid8.PNG\|Validation Scheme - Step 3\|600px]]<br>

	To create a rule, enter the rule details on its own line in the text area. Elements of the rule must be separated by commas. Each element must conform to the expected value of that field (e.g., the ID element must not contain illegal characters; the equality operator may only be one of the permitted values). The field order is determined by the drop-downs at the top of this step and can be changed by the user.		To create a rule, enter the rule details on its own line in the text area. Elements of the rule must be separated by commas. Each element must conform to the expected value of that field (e.g., the ID element must not contain illegal characters; the equality operator may only be one of the permitted values). The field order is determined by the drop-downs at the top of this step and can be changed by the user.