Reporting Constraints - Structural Metadata Management - Revision history

Vmurrell: /* Step 2 - Attachment */

2023-09-13T16:42:34Z

‎Step 2 - Attachment

Vmurrell: /* Step 2 - Attachment */

2023-09-13T16:42:21Z

‎Step 2 - Attachment

Vmurrell: /* Step 2 - Attachment */

2023-09-13T16:41:50Z

‎Step 2 - Attachment

Vmurrell: /* Step 4 - Manual Editing */

2023-09-13T16:38:13Z

‎Step 4 - Manual Editing

Vmurrell: /* Step 2 - Attachment */

2023-09-13T16:36:57Z

‎Step 2 - Attachment

Vmurrell: /* Step 1 - High Level Details */

2023-09-13T16:34:17Z

‎Step 1 - High Level Details

Vmurrell at 16:31, 13 September 2023

2023-09-13T16:31:59Z

Vmurrell at 14:59, 12 September 2023

2023-09-12T14:59:12Z

Vmurrell at 10:34, 8 August 2023

2023-08-08T10:34:37Z

Mbaird at 12:12, 22 November 2019

2019-11-22T12:12:24Z

← Older revision		Revision as of 16:42, 13 September 2023
Line 59:		Line 59:


−	[[File:Seriescon1.png\|Series Constraint - Attachment\|~~100px~~]]<br>	+	[[File:Seriescon1.png\|Series Constraint - Attachment\|1000px]]<br>

	==Steps 3 - CSV Import Values==		==Steps 3 - CSV Import Values==

← Older revision		Revision as of 16:42, 13 September 2023
Line 59:		Line 59:


−	[[File:Seriescon1.png\|Series Constraint - Attachment\|~~800px~~]]<br>	+	[[File:Seriescon1.png\|Series Constraint - Attachment\|100px]]<br>

	==Steps 3 - CSV Import Values==		==Steps 3 - CSV Import Values==

← Older revision		Revision as of 16:41, 13 September 2023
Line 59:		Line 59:


−	[[File:~~CONST3~~.~~PNG~~\|Series Constraint - Attachment\|800px]]<br>	+	[[File:Seriescon1.png\|Series Constraint - Attachment\|800px]]<br>

	==Steps 3 - CSV Import Values==		==Steps 3 - CSV Import Values==

← Older revision		Revision as of 16:38, 13 September 2023
Line 69:		Line 69:
	Step 4 allows you to add restrictions manually.		Step 4 allows you to add restrictions manually.

−	[[File:~~seriescon2~~.~~PNG~~\|Series Constraint - Manual Editing\|1000px]]<br>	+	[[File:Seriescon2.png\|Series Constraint - Manual Editing\|1000px]]<br>

← Older revision		Revision as of 16:36, 13 September 2023
Line 59:		Line 59:


−	[[File:~~seriescon1~~.PNG\|Series Constraint - Attachment\|~~1000px~~]]<br>	+	[[File:CONST3.PNG\|Series Constraint - Attachment\|800px]]<br>

	==Steps 3 - CSV Import Values==		==Steps 3 - CSV Import Values==

@@ Line 48: / Line 48: @@
 ==Step 1 - High Level Details==
-The steps in a Constraint Wizard includes step 1 which provides the generic, high level details about the Constraint. See this article [https://fmrwiki.sdmxcloud.org/All_Structures_-_FMR for more information on authoring and maintaining structures.]
+The steps in a Constraint Wizard includes step 1 which provides the generic, high level details about the Constraint. See this article [[All Structures]] for more information on authoring and maintaining structures.
 ==Step 2 - Attachment==

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Structural Metadata]]
-== Overview ==
+=Overview=
-Reporting Constraints are used to further restrict the allowable content of a '''Codelist''' in the context of a '''DSD, Dataflow, Provision Agreement,''' or '''Data Provider'''.  Collectively these are termed as Constrainable Structures.  The restrictions imposed by Reporting Constraints are taken into account when validating a dataset reported by a '''Data Provider'''.  A Reporting Constraint defines restrictions against Dimensions and Attributes of a DSD which take allowable content from an enumerated list (e.g Codelist).
+Content Constraints or Reporting Constraints are used to further restrict the allowable content of a Codelist in the context of a DSD, Dataflow, Provision Agreement, or Data Provider.  Collectively these are termed as Constrainable Structures.  The restrictions imposed by Reporting Constraints are considered when validating a dataset reported by a Data Provider.  A Reporting Constraint defines restrictions against Dimensions and Attributes of a DSD which take allowable content from an enumerated list (e.g. Codelist).
-The Codelists which can be constrained are determined from the Constrainable structures that the Reporting Constraint is referencing.
+A Constrainable Structure, such as a Provision Agreement will inherit any Reporting Constraints which are attached to lower-level structures that it references.  For example, the Provision Agreement will inherit any Reporting Constraints against the Dataflow it uses, and the DSD that the Dataflow uses.  It will also inherit any Content Constraints against the Data Provider it references.
-A Reporting Constraint can impose a rule on any of the available Codelists to remove any number of allowable Codes, therefore reducing the universe of the enumerated list.  A Codelist is constrained by either defining which Codes in the Codelist are included (remain valid) or which codes are excluded (are not valid).  An included or excluded Code may also be marked as cascade, which means any Codes which are children of that Code also inherit the rule of inclusion or exclusion.
+==Step 1 - High Level Details==
-When viewing a Reporting Constraint, the Included Cube shows which Codes remain valid for any of the Constrained Components.  The excluded Cube shows which Codes are no longer valid.
+The steps in a Constraint Wizard includes step 1 which provides the generic, high level details about the Constraint. See this article[https://fmrwiki.sdmxcloud.org/All_Structures for more information on authoring and maintaining structures.]
-::<small>''Figure 1 showing the view of the included Cube for a Reporting Constraint''</small>
+[[File:CONST3.PNG|Selecting Structures|800px]]<br>
-The rules defined by Reporting Constraints will be enforced when performing data validation.  The rules are also reflected when viewing a DSD, Dataflow, or Provision Agreement, as shown below.
+[[File:CONST4.PNG|Included Values|1000px]]<br>
-::[[File:Reporting Constraints 3.jpg‎|frameless|750px]]
+==Step 1 - High Level Details==
-::<small>''Figure 2 showing a constrained Reference Area Codelist in the Context of a Data Provider and Dataflow combination (Provision Agreement)''</small>
+The steps in a Constraint Wizard includes step 1 which provides the generic, high level details about the Constraint. See this article [https://fmrwiki.sdmxcloud.org/All_Structures_-_FMR for more information on authoring and maintaining structures.]
-== Report Constraint Wizard ==
+==Step 2 - Attachment==
-The Reporting Constraint Wizard includes the first generic step for information.
+'''Options are:'''
-::[[File:Reporting Constraints 4.jpg‎|frameless|750px]]
+==Steps 3 - CSV Import Values==
-::<small>''Figure 3 showing the Constrained Structure and selected Components to include in the Constraint''</small>
+The third step allows the user to import Codes from CSV. CSV text can be copied and pasted into the text field. On clicking ‘Next’, the CSV is checked for correctness. If valid, Codes are created and added to the Constraint.
-The third and fourth steps are to define the included and excluded values respectively.  A Component can only be defined to contain included codes or excluded Codes not both.
+==Step 4 - Manual Editing==
-::[[File:Reporting Constraints 5.jpg‎|frameless|750px]]
+Step 4 allows you to add restrictions manually.
-::<small>''Figure 4 showing step 3 of the Reporting Constraint Wizard''</small>
+[[File:seriescon2.PNG|Series Constraint - Manual Editing|1000px]]<br>

← Older revision		Revision as of 12:12, 22 November 2019
Line 29:		Line 29:

	::<small>''Figure 2 showing a constrained Reference Area Codelist in the Context of a Data Provider and Dataflow combination (Provision Agreement)''</small>		::<small>''Figure 2 showing a constrained Reference Area Codelist in the Context of a Data Provider and Dataflow combination (Provision Agreement)''</small>
		+
		+	== Report Constraint Wizard ==
		+
		+	The Reporting Constraint Wizard includes the first generic step for information.
		+
		+	The second step is used to define what Structures are being constrained and of the constrained structures, which Components will be included in the Constraints. Only Components which reference a Codelist are included in the available list. If the Constrained structure is a Data Provider, the list of Components will be derived from all the Dataflows the Data Provider has a Provision Agreement for.
		+
		+
		+	::[[File:Reporting Constraints 4.jpg‎\|frameless\|750px]]
		+
		+	::<small>''Figure 3 showing the Constrained Structure and selected Components to include in the Constraint''</small>
		+
		+	The third and fourth steps are to define the included and excluded values respectively. A Component can only be defined to contain included codes or excluded Codes not both.
		+
		+	::[[File:Reporting Constraints 5.jpg‎\|frameless\|750px]]
		+
		+	::<small>''Figure 4 showing step 3 of the Reporting Constraint Wizard''</small>