Difference between revisions of "Data Related Structure"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
* [[Content_Constraint|Reporting Constraints:]] Reporting Constraints are used to further restrict the allowable content of a [[Codelist|Codelist]] in the context of a DSD, Dataflow, Provision Agreement or Data Provider. 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). When viewing a Reporting Constraint, the details will show either an Included Cube (allowable Codes) or an Excluded Cube (excluded Codes) or both. The cascade feature of a Reporting Constraint enables the include/excluded rules to apply to any child Codes of the Constrained Code. | * [[Content_Constraint|Reporting Constraints:]] Reporting Constraints are used to further restrict the allowable content of a [[Codelist|Codelist]] in the context of a DSD, Dataflow, Provision Agreement or Data Provider. 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). When viewing a Reporting Constraint, the details will show either an Included Cube (allowable Codes) or an Excluded Cube (excluded Codes) or both. The cascade feature of a Reporting Constraint enables the include/excluded rules to apply to any child Codes of the Constrained Code. | ||
| − | * [[ | + | * [[Pre-Defined_Queries|Pre-Defined Queries:]] A pre-defined query is the same underlying SDMX Structure type as a Reporting Constraint (both structures are known as a Content Constraint). A Content Constraint can be constructed to define what data is allowed to be reported (Reporting Constraint) or alternatively it can be constructed to define existing data, the latter being used in the Registry as a Pre-Defined Query. A Pre-Defined Query is used to define a sub-cube of data for a Dataflow and giving the sub-cube a name and description. |
Revision as of 07:07, 1 September 2022
Data related structures are used to define the structure of datasets along with allowable content, and they are also used to define what datasets Data Providers are allowed to report data on. Data related structures includes:
- Data Structure Definition: A Data Structure Definition (DSD) defines a dataset in terms of its Dimensionality and allowable content. All reported datasets must conform to the description of a DSD.
- Dataflow: A Dataflow is a structure on which data is collected and disseminated. A Dataflow references a DSD which is used as the underlying template to which the data must conform.
- Provision Agreement: A Provision Agreement is the union of a Dataflow with a Data Provider. A Provision Agreement is a definition that the Data Provider is allowed to provide data for the Dataflow.
- Reporting Constraints: 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. 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). When viewing a Reporting Constraint, the details will show either an Included Cube (allowable Codes) or an Excluded Cube (excluded Codes) or both. The cascade feature of a Reporting Constraint enables the include/excluded rules to apply to any child Codes of the Constrained Code.
- Pre-Defined Queries: A pre-defined query is the same underlying SDMX Structure type as a Reporting Constraint (both structures are known as a Content Constraint). A Content Constraint can be constructed to define what data is allowed to be reported (Reporting Constraint) or alternatively it can be constructed to define existing data, the latter being used in the Registry as a Pre-Defined Query. A Pre-Defined Query is used to define a sub-cube of data for a Dataflow and giving the sub-cube a name and description.
