Search results

Jump to navigation Jump to search
  • ...reusable definitions for statistical concepts like frequency, currency and reference area (country), and are contained in a [[Concept Scheme V11|Concept Scheme] Concepts can be coded by linking them to a specific [[Codelist V11|Codelist]] or lef
    1 KB (156 words) - 08:34, 12 September 2023
  • ...eusable definitions for statistical items such as frequency, currency, and reference area (country). Concepts may be referenced by multiple structures in SDMX, and therefore provide re-
    5 KB (718 words) - 08:28, 12 September 2023
  • ...tructures are Cross Referenced by it and also the number of Dataflows that reference this DSD. ...list on the left. Selecting an item in the list shows the Structures that Reference it and those Structures that are referenced by it.
    4 KB (588 words) - 03:17, 15 September 2023
  • <strong>The Role of Concepts In Defining a DSD's Components</strong><br> ...dmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0 SDMX Cross Domain Concepts] where the default Representation is 'String', but the Component needs to b
    7 KB (1,003 words) - 09:33, 20 December 2019
  • ...ension, the Measure Dimension cannot reference a Codelist, however it must reference a Concept Scheme which is used to list the allowable measures. Each Concep ...rimary Measure, click on the text field to open up a list of all available Concepts.
    5 KB (832 words) - 07:53, 12 September 2023
  • <strong>The role of Concepts In defining a DSD's Components</strong><br> ...dmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0 SDMX Cross Domain Concepts] where the default Representation is 'String', but the Component needs to b
    8 KB (1,125 words) - 08:57, 12 September 2023
  • [[Category:Concepts Reference]] | 2 || Dimension || REF_AREA || Reference Area
    2 KB (343 words) - 00:12, 11 September 2023
  • ...horing and maintenance tool for all of the structures including Codelists, Concepts and Data Structure Definitions.<br> * Authoring and maintaining reference metadata
    2 KB (220 words) - 02:40, 12 September 2023
  • See also [[Reference_Metadata_API|Reference Metadata API]] ...ocument of information which can be attached to any SDMX structure. Whist Reference Metadata can be used to capture information to run business processes, the
    18 KB (2,645 words) - 07:23, 13 September 2023
  • ...tructure is both [[Identifiable]] and [[Nameable]], it also must contain a reference to the [[Agency]] that is responsible for maintaining it. | Concept Scheme || 1.0|| Yes || List of Concepts (used by Data Structures, Metadata Structures)
    4 KB (500 words) - 07:07, 18 March 2020
  • ...navigate to a particular codelist, and then discover which Data Structures reference the Codelists. ...structures have been organised into folders depending on which structures reference them. This is an extremely useful mechanism for quickly finding the desired
    17 KB (2,702 words) - 03:55, 4 May 2022
  • ...d list of allowable values. Codelists can be used by '''Dimensions''', '''Concepts''', and '''Metadata Attributes''' to define the allowable content for both ::<small>''Figure 1 showing part of a Reference Area Codelist''</small>
    3 KB (555 words) - 07:51, 12 September 2023
  • * To retrieve statistical data or reference metadata using keys (with options for wildcarding and support for the OR op * To further refine queries for statistical data or reference metadata using time information (start period and end period).
    25 KB (3,464 words) - 09:05, 2 August 2023
  • Item Validity allows for codes and concepts to be specified as being valid for specific periods of time. This is useful Item Validity can be applied to Concepts in a Concept Scheme or Codes in a Codelist, a Hierarchical Codelist or a Co
    11 KB (1,841 words) - 10:03, 13 September 2023
  • | DatasetNavigation || Defines which (if any) Concepts to allow a user to find data by (built into the sidebar) | ${REF_AREA} || Replaced by the value of the Reference Area Dimension, in the Locale set on the Data Browser (or an alternative Lo
    17 KB (2,516 words) - 00:50, 12 September 2023
  • ...inition|Data Structure Definitions]], or indirectly through [[Concepts V11|Concepts]] to explicitly define the closed set of values for enumerated [[Dimension| ...ata Structure Definition|Metadata Structure Definitions]] which describe [[Reference Metadata]].</p>
    8 KB (1,262 words) - 02:55, 8 August 2023
  • ...horing and maintenance tool for all of the structures including Codelists, Concepts and Data Structure Definitions. ...e_Metadata|'''Reference Metadata''']] || Guidance on working with SDMX 3.0 reference metadata in Fusion Registry 11
    9 KB (1,226 words) - 06:38, 26 October 2023
  • ...horing and maintenance tool for all of the structures including Codelists, Concepts and Data Structure Definitions. ...e_Metadata|'''Reference Metadata''']] || Guidance on working with SDMX 3.0 reference metadata in Fusion Registry 11
    9 KB (1,233 words) - 02:26, 7 October 2023
  • additional structures which reference, or are referenced by those identified in the query path. ...Schemes, Agency Schemes are returned as partial lists based on the Codes, Concepts, and Agencies used by the referencing Provision Agreements, Dataflows, Data
    12 KB (1,728 words) - 23:24, 10 September 2023
  • ===Key Concepts=== In the Data Rule example, we will look at how to restrict by reference to a dataflow’s specific series.
    16 KB (2,663 words) - 06:04, 16 August 2023

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)