Search results

Jump to navigation Jump to search
  • ...ffers depending on the type of component and whether it is 'coded' or not. Components in a Data Structure can be linked to a Codelist to ensure that only permitt | Black|| Coded Attributes which are not mandatory. Time and Measure Components
    1 KB (200 words) - 08:22, 13 May 2024
  • ...ps area allows you to define a number of map types that can be used to map components (Dimensions and Attributes) from one Data Structure to another. This relati Data Structure Maps are used to map Components (Dimensions and Attributes) from one Data Structure to another. This relati
    7 KB (1,237 words) - 05:30, 5 September 2022
  • ...ip where there is a semantic equivalence between the source and the target Components.
    2 KB (223 words) - 08:36, 17 April 2024
  • The Author Helper is an extremely useful tool which allows you to see the Components and allowable Codes expected based on the Dataflow and Data Provider combin ===Uncoded Components===
    4 KB (642 words) - 03:12, 13 September 2023
  • ...[[Data_Structure_Definitions|Data Structure]] with a number of [[Component|Components]]. They are all [[Dimension|Dimensions]] except the Observation Value which The image below shows that 3 Components are '''Enumerated''' and the Codes which are in the linked [[Codelists|Code
    5 KB (862 words) - 08:45, 17 April 2024
  • In practice, Attributes are [[Component|Components]] used in [[Data_or_Metadata_Structure_Definition|Data Structure Definition
    793 bytes (104 words) - 00:44, 23 August 2022
  • ...he Included Cube shows which Codes remain valid for any of the Constrained Components. The excluded Cube shows which Codes are no longer valid. ...ilable 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 Ag
    4 KB (671 words) - 03:37, 28 March 2024
  • ...nsions]], [[Attribute|Attributes]] and [[Measure V11|Measures]] are the '''components''' of a [[Data_or_Metadata_Structure_Definition|Data Structure Definition]]
    1 KB (152 words) - 01:21, 30 August 2022
  • ...ribe the structure of datasets by specifying their constituent [[Component|Components]]: =Data Structure Components=
    8 KB (1,125 words) - 05:28, 28 March 2024
  • ...ribe the structure of datasets by specifying their constituent [[Component|Components]]: =Data Structure Components=
    8 KB (1,126 words) - 03:05, 8 August 2023
  • ...re - the URN of the DSD (and possibly Dataflow) used in the source and its components ...re - the URN of the DSD (and possibly Dataflow) used in the target and its components
    17 KB (2,154 words) - 02:56, 2 November 2023
  • ...l need to specify the Domain Components. Please note that the order of the components is very important here.
    7 KB (1,049 words) - 01:25, 13 May 2024
  • ...resentation Map]] which is used to describe how values reported for source Components should be converted to conform to the desired output DSD.<br> ...ent Map has 1 or more Components from the source DSD, mapping to 1 or more Components in the target DSD.
    17 KB (2,734 words) - 08:34, 17 April 2024
  • ...oblems like conflicting duplicate observations. For [[Component|enumerated components]], dimension or attribute values submitted must match those in the specifie
    2 KB (313 words) - 04:35, 13 May 2024
  • ...st can be referenced for defining the set of allowed values for enumerated Components in Data Structure Definitions (DSDs) or Metadata Structure Definitions whic
    2 KB (276 words) - 01:23, 5 September 2022
  • ...st can be referenced for defining the set of allowed values for enumerated Components in Data Structure Definitions (DSDs) or Metadata Structure Definitions whic
    2 KB (276 words) - 01:24, 5 September 2022
  • Set which components to include in the data set and the values they take.
    2 KB (294 words) - 07:58, 13 May 2024
  • ...ncipally for defining the set of allowed values for enumerated [[Component|Components]] in [[Data_or_Metadata_Structure_Definition|Data Structure Definitions (DS
    2 KB (294 words) - 06:59, 13 May 2024
  • ...ncipally for defining the set of allowed values for enumerated [[Component|Components]] in [[Data Structure Definition V10|Data Structure Definitions (DSDs)]] or | M || Seasonal and calendar components || Synonyms: Seasonal and calendar effects; seasonal and calendar factors
    8 KB (1,256 words) - 01:34, 30 August 2022
  • ...st can be referenced for defining the set of allowed values for enumerated Components [[Data_Structure_Definitions|Data Structure Definitions (DSDs)]] or [[Metad
    2 KB (337 words) - 07:07, 13 May 2024
  • ...ncipally for defining the set of allowed values for enumerated [[Component|Components]] in [[Data_or_Metadata_Structure_Definition|Data Structure Definitions (DS | M || Seasonal and calendar components || Synonyms: Seasonal and calendar effects; seasonal and calendar factors
    8 KB (1,259 words) - 03:04, 28 March 2024
  • ...ersion numbers, but users of structures like DSDs may be surprised to find components have been added or removed unless other metadata governance procedures are
    3 KB (423 words) - 07:08, 13 May 2024
  • [[File:DS.PNG|DSD Components|700px]]<br>
    3 KB (587 words) - 07:24, 7 September 2022
  • .... When writing an EDI structure file, does not check that cross-referenced components are of the same aganecy as the DSD. This feature is part of EDI Leniency mo
    4 KB (556 words) - 08:38, 17 April 2024
  • ...sts of Dimensions, Attributes, and Measures, collectively these are termed Components. Each Component of a DSD references a Concept to provide a semantic meanin
    4 KB (594 words) - 01:29, 5 May 2021
  • ...sts of Dimensions, Attributes, and Measures, collectively these are termed Components. Each Component of a DSD references a Concept to provide a semantic meanin
    4 KB (608 words) - 05:34, 28 March 2024
  • ...be assigned a default representation. This representation is inherited by Components of a Data Structure Definition (DSD) as a default. Default representation
    4 KB (627 words) - 03:57, 22 August 2022
  • A new <code>GeospatialInformation</code> type is provided for non-enumerated components. This uses the same 'geofeature set' syntax as for Geographic Codelists and ...onents in the source dataset can be mapped to a combination of one or more components in the target.
    17 KB (2,449 words) - 04:11, 22 July 2022
  • You will note that the [[Component|Components]] of the underlying Data Structure are displayed and REF-AREA has been tick
    6 KB (1,056 words) - 04:26, 28 March 2024
  • ...e columns describe each component of the Observation value, reflecting the Components in the Data Structure Definition.
    10 KB (1,268 words) - 03:18, 14 August 2023
  • ...ecify the Components it is restricting, so it can be a subset of the DSD’s components. If the constraint is attached to multiple DSDs (either directly, or indire
    17 KB (2,693 words) - 05:34, 4 October 2022
  • Enriches a dataset by adding one or more components whose values can be fixed, or contain content taken from other reported val
    9 KB (1,369 words) - 02:47, 19 July 2023
  • ...s). The Structure Maps describe the relationships between the [[Component|Components]] of the two DSDs, whilst Relationship Maps are used to describe how the va
    14 KB (2,219 words) - 07:58, 17 April 2024
  • ...ormat template. The output format template is a string that defines which components of time are output an in which order and style. For example to output a da Components of the underlying Data Structure can be explicitly referenced using the fol
    52 KB (8,490 words) - 05:14, 18 July 2023
  • FMR11-285 - Components with Time based Mappings cannot be edited in the Structure Map Wizard... FMR11-296 - Missing components in the 'unmapped' part in case of partial mapping ht
    71 KB (10,701 words) - 07:52, 18 April 2024