Difference between revisions of "Pre-Defined Queries - Structural Metadata Management"
(Created page with "__NOTOC__ Category:Structural Metadata == Overview == A Pre-Defined query is stored in the Fusion Registry as an SDMX Content Constraint. In SDMX the Content Constraint...") |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category:RetiredFunctionality]] | |
| − | [[Category: | ||
== Overview == | == Overview == | ||
| + | This is not available in Version 11. | ||
A Pre-Defined query is stored in the Fusion Registry as an SDMX Content Constraint. In SDMX the Content Constraint can be used to define allowable content (see section [[Reporting Constraints - Structural Metadata Management|Reporting Constraints]]) or to define data present. The latter type of Content Constraint has been termed Pre-Defined Query in the Fusion Registry. The creation of a Pre-Defined query follows the same steps as a Reporting Constraint, with the exception that the constrained structure must be a Dataflow. | A Pre-Defined query is stored in the Fusion Registry as an SDMX Content Constraint. In SDMX the Content Constraint can be used to define allowable content (see section [[Reporting Constraints - Structural Metadata Management|Reporting Constraints]]) or to define data present. The latter type of Content Constraint has been termed Pre-Defined Query in the Fusion Registry. The creation of a Pre-Defined query follows the same steps as a Reporting Constraint, with the exception that the constrained structure must be a Dataflow. | ||
The view of the Pre-Defined Query is the same as the Reporting Constraint, with the additional feature of being able to run the query. | The view of the Pre-Defined Query is the same as the Reporting Constraint, with the additional feature of being able to run the query. | ||
| − | |||
Latest revision as of 02:15, 15 September 2023
Overview
This is not available in Version 11.
A Pre-Defined query is stored in the Fusion Registry as an SDMX Content Constraint. In SDMX the Content Constraint can be used to define allowable content (see section Reporting Constraints) or to define data present. The latter type of Content Constraint has been termed Pre-Defined Query in the Fusion Registry. The creation of a Pre-Defined query follows the same steps as a Reporting Constraint, with the exception that the constrained structure must be a Dataflow.
The view of the Pre-Defined Query is the same as the Reporting Constraint, with the additional feature of being able to run the query.
Figure 1 showing the view of a Pre-Defined Query, with the Run Query button in the details header
Running the query loads the browse data page with the Codes pre-selected based on the Pre-Defined Query definition.
Figure 1 showing the resultant data table after running the Pre-Defined Query above
