Structure Map - Revision history

Vmurrell: /* Structure Properties */

2024-04-17T15:34:27Z

‎Structure Properties

Vmurrell at 12:40, 25 March 2024

2024-03-25T12:40:07Z

Vmurrell at 12:37, 25 March 2024

2024-03-25T12:37:22Z

Vmurrell: /* Structure Properties */

2022-09-05T08:35:41Z

‎Structure Properties

Vmurrell: /* Structure Properties */

2022-08-22T14:26:36Z

‎Structure Properties

Glenn at 11:04, 18 May 2022

2022-05-18T11:04:07Z

Glenn at 10:22, 18 May 2022

2022-05-18T10:22:59Z

Mnelson at 14:38, 6 May 2022

2022-05-06T14:38:32Z

Mnelson: /* Structure Properties */

2022-05-06T14:37:46Z

‎Structure Properties

Mnelson at 14:36, 6 May 2022

2022-05-06T14:36:50Z

@@ Line 11: / Line 11: @@
 |-
 ! scope=row style="text-align: left;"  | Maintainable
-| [[Maintainable|Yes]]
+| [[Maintainable V11|Yes]]
 |-
 ! scope=row style="text-align: left;"  | Identifiable
-| [[Identifiable|Yes]]
+| [[Identifiable V11|Yes]]
 |-
 ! scope=row style="text-align: left;"  | Item Scheme

@@ Line 1: / Line 1: @@
 [[Category:SDMX 3.0 Structures]]
 [[Category:SDMX 3.0 Mapping Structures]]
-[[Category:SDMX_3.0_Mapping]]
 = Overview =
 [[File:StructureMapModel.jpg|thumb|Simple example of a structure map]]

@@ Line 1: / Line 1: @@
 [[Category:SDMX 3.0 Structures]]
 [[Category:SDMX 3.0 Mapping Structures]]
 = Overview =
 [[File:StructureMapModel.jpg|thumb|Simple example of a structure map]]

@@ Line 16: / Line 16: @@
 |-
 ! scope=row style="text-align: left;"  | Item Scheme
-| No
+| [[Item_Scheme V11|No]]
 |-
 ! scope=row style="text-align: left;"  | SDMX Information Model Versions

@@ Line 24: / Line 24: @@
 | StructureMap
 |}
 ==Usage==

@@ Line 29: / Line 29: @@
 Structure Mapping does not create new data, it should '''not''' be thought of as a mechanism to aggregate data, only to re-organise and re-code it. <br>
 <br>
-Two Maintainable Structures are required to defining how two datasets relate to each other, one is the SDMX Structure Map which is used to define how Components from the source DSD relate to Components on the target DSD, and the other is the [[DRAFT_Representation_Map|Representation Map]] which is used to describe how values reported for source Components should be converted to conform to the desired output DSD.<br>
+Two Maintainable Structures are required to defining how two datasets relate to each other, one is the SDMX Structure Map which is used to define how Components from the source DSD relate to Components on the target DSD, and the other is the [[Representation_Map|Representation Map]] which is used to describe how values reported for source Components should be converted to conform to the desired output DSD.<br>
 <br>
-A simple example is a relationship between the source COUNTRY component to the target REF_AREA component.  The Structure Map has a source COUNTRY and target REF_AREA, the rules used to define how the values are mapped are maintained in the corresponding [[DRAFT_Representation_Map|Representation Map]], an example rule would be GB maps to GBR, US maps to USA, and UY maps to URY.
+A simple example is a relationship between the source COUNTRY component to the target REF_AREA component.  The Structure Map has a source COUNTRY and target REF_AREA, the rules used to define how the values are mapped are maintained in the corresponding [[Representation_Map|Representation Map]], an example rule would be GB maps to GBR, US maps to USA, and UY maps to URY.
 = Structure Map - Model =
@@ Line 54: / Line 54: @@
 === Defining how values map ===
 [[File:Two-set Venn diagram example.jpg|thumb|Finding the mapped output using the intersection of each output set]]
-Each Component Map can link to a [[DRAFT_Representation_Map|Representation Map]], which is used to describe how the source values map to the target values.  The linked Representation Map links to source and target Codelists, Valuelists, or Free text.  Like the Component Map, the Representation Map may contain multiple sources and multiple targets.  The number and order of sources and targets to a Representation Map must match exactly that of the Component Map.  For example if a Component Map has 2 sources REF_AREA and CURRENCY, then the linked Representation map must also have 2 sources, one for the REF_AREA Codelist and the other for the CURRENCY Codelist.
+Each Component Map can link to a [[Representation_Map|Representation Map]], which is used to describe how the source values map to the target values.  The linked Representation Map links to source and target Codelists, Valuelists, or Free text.  Like the Component Map, the Representation Map may contain multiple sources and multiple targets.  The number and order of sources and targets to a Representation Map must match exactly that of the Component Map.  For example if a Component Map has 2 sources REF_AREA and CURRENCY, then the linked Representation map must also have 2 sources, one for the REF_AREA Codelist and the other for the CURRENCY Codelist.
 Representation Maps can include complex rules, such as regular expressions on source values, and can even define periods of time for which a mapping relationship is true, for example if a relationship between source country and target currency is defined then one could map France to the French Franc up until 2002 and then map France to the Euro from 2002 onwards.
@@ Line 142: / Line 142: @@
 '''Component Map 3:''' Source=UNIQUE_KEY Target=INDICATOR <br>
 <br>
-Each Component Map is backed by a [[DRAFT_Representation_Map|Representation Map]], which maps the value of the Unique Key to the output.
+Each Component Map is backed by a [[Representation_Map|Representation Map]], which maps the value of the Unique Key to the output.
 <br>
 '''Representation Map''' = UNIQUE_KEY -> FREQ<br>
@@ Line 174: / Line 174: @@
 == If-Then-Else (default if not specified) ==
-The order of rules in a [[DRAFT_Representation_Map|Representation Map]] can be important, specifically when using regular expressions.  The regular expressions are tested in the same order that the appear they are defined, this allows for more specific expressions to be tested before a general catch all.
+The order of rules in a [[Representation_Map|Representation Map]] can be important, specifically when using regular expressions.  The regular expressions are tested in the same order that the appear they are defined, this allows for more specific expressions to be tested before a general catch all.
 '''<u>Example</u>'''
@@ Line 254: / Line 254: @@
 '''<u>Example</u>'''<br>
 '''Component Map 1''': BIRTHS maps to OBS_VALUE<br>
-'''Component Map 2''': BIRTHS maps to INDICATOR (uses Births [[DRAFT_Representation_Map|Representation Map]]) <br>
+'''Component Map 2''': BIRTHS maps to INDICATOR (uses Births [[Representation_Map|Representation Map]]) <br>
 <br>
 '''Births Representation Map''':  source=[anything], target=B

@@ Line 18: / Line 18: @@
 |-
 ! scope=row style="text-align: left;"  | SDMX Information Model Versions
-| 3.0-DRAFT
+| 3.0
 |-
 ! scope=row style="text-align: left;"  | Concept ID

← Older revision		Revision as of 14:36, 6 May 2022
Line 1:		Line 1:
		+	[[Category:SDMX Structures]]
	= Overview =		= Overview =
	[[File:StructureMapModel.jpg\|thumb\|Simple example of a structure map]]		[[File:StructureMapModel.jpg\|thumb\|Simple example of a structure map]]