Changes for page 13 Structure Mapping
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -97,37 +97,26 @@ 97 97 98 98 A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below: 99 99 100 -|Source|Target|Output Series Key 101 -|SERIES_CODE=XMAN_Z_21|((( 100 +(% style="width:819.294px" %) 101 +|(% style="width:240px" %)**Source**|(% style="width:246px" %)**Target**|(% style="width:329px" %)**Output Series Key** 102 +|(% style="width:240px" %)SERIES_CODE=XMAN_Z_21|(% style="width:246px" %)((( 102 102 Dimensions 103 - 104 104 INDICATOR=XM 105 - 106 106 FREQ=A 107 - 108 108 ADJUSTMENT=N 109 - 110 110 Attributes 111 - 112 112 UNIT_MEASURE=_Z 113 - 114 114 COMP_ORG=21 115 -)))|XM:A:N 116 -|SERIES_CODE=XMAN_Z_34|((( 110 +)))|(% style="width:329px" %)XM:A:N 111 +|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)((( 117 117 Dimensions 118 - 119 119 INDICATOR=XM 120 - 121 121 FREQ=A 122 - 123 123 ADJUSTMENT=N 124 - 125 125 Attributes 126 - 127 127 UNIT_MEASURE=_Z 128 - 129 129 COMP_ORG=34 130 -)))|XM:A:N 119 +)))|(% style="width:329px" %)XM:A:N 131 131 132 132 The above behaviour can be okay if the series XMAN_Z_21 contains observations for different periods of time then the series XMAN_Z_34. If however both series contain observations for the same point in time, the output for this mapping will be two observations with the same series key, for the same period in time. 133 133 ... ... @@ -143,24 +143,26 @@ 143 143 144 144 A Representation Map mapping ISO 2-character to ISO 3-character Codelists would take the following form: 145 145 146 -|CL_ISO_ALPHA2|CL_ISO_ALPHA3 147 -|AF|AFG 148 -|AL|ALB 149 -|DZ|DZA 150 -|AS|ASM 151 -|AD|AND 152 -|etc…| 135 +(% style="width:763.294px" %) 136 +|(% style="width:252px" %)**CL_ISO_ALPHA2**|(% style="width:508px" %)**CL_ISO_ALPHA3** 137 +|(% style="width:252px" %)AF|(% style="width:508px" %)AFG 138 +|(% style="width:252px" %)AL|(% style="width:508px" %)ALB 139 +|(% style="width:252px" %)DZ|(% style="width:508px" %)DZA 140 +|(% style="width:252px" %)AS|(% style="width:508px" %)ASM 141 +|(% style="width:252px" %)AD|(% style="width:508px" %)AND 142 +|(% style="width:252px" %)etc…|(% style="width:508px" %) 153 153 154 154 A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described: 155 155 156 -|Text|CL_ISO_ALPHA2 157 -|"Germany"|DE 158 -|"France"|FR 159 -|"United Kingdom"|GB 160 -|"Great Britain"|GB 161 -|"Ireland"|IE 162 -|"Eire"|IE 163 -|etc…| 146 +(% style="width:770.294px" %) 147 +|(% style="width:247px" %)**Text**|(% style="width:520px" %)**CL_ISO_ALPHA2** 148 +|(% style="width:247px" %)"Germany"|(% style="width:520px" %)DE 149 +|(% style="width:247px" %)"France"|(% style="width:520px" %)FR 150 +|(% style="width:247px" %)"United Kingdom"|(% style="width:520px" %)GB 151 +|(% style="width:247px" %)"Great Britain"|(% style="width:520px" %)GB 152 +|(% style="width:247px" %)"Ireland"|(% style="width:520px" %)IE 153 +|(% style="width:247px" %)"Eire"|(% style="width:520px" %)IE 154 +|(% style="width:247px" %)etc…|(% style="width:520px" %) 164 164 165 165 Valuelists, introduced in SDMX 3.0, are equivalent to Codelists but allow the maintenance of non-SDMX identifiers. Importantly, their IDs do not need to conform to IDType, but as a consequence are not Identifiable. 166 166 ... ... @@ -168,10 +168,11 @@ 168 168 169 169 In common with Codelists, each item in a Valuelist has a multilingual name giving it a human-readable label and an optional description. For example: 170 170 171 -|Value|Locale|Name 172 -|$|en|United States Dollar 173 -|%|En|Percentage 174 -| |fr|Pourcentage 162 +(% style="width:780.294px" %) 163 +|(% style="width:126px" %)**Value**|(% style="width:153px" %)**Locale**|(% style="width:498px" %)**Name** 164 +|(% style="width:126px" %)$|(% style="width:153px" %)en|(% style="width:498px" %)United States Dollar 165 +|(% style="width:126px" %)%|(% style="width:153px" %)En|(% style="width:498px" %)Percentage 166 +|(% style="width:126px" %) |(% style="width:153px" %)fr|(% style="width:498px" %)Pourcentage 175 175 176 176 Other characteristics of Representation Maps: 177 177 ... ... @@ -195,30 +195,31 @@ 195 195 196 196 Below is an example set of regular expression rules for a particular component. 197 197 198 -|Regex|Description|Output 199 -|A|Rule match if input = 'A'|OUT_A 200 -|^[A-G]|Rule match if the input starts with letters A to G|OUT_B 201 -|A~|B|Rule match if input is either 'A' or 'B'|OUT_C 190 +(% style="width:708.294px" %) 191 +|(% style="width:133px" %)**Regex**|(% style="width:377px" %)**Description**|(% style="width:194px" %)**Output** 192 +|(% style="width:133px" %)A|(% style="width:377px" %)Rule match if input = 'A'|(% style="width:194px" %)OUT_A 193 +|(% style="width:133px" %)^[A-G]|(% style="width:377px" %)Rule match if the input starts with letters A to G|(% style="width:194px" %)OUT_B 194 +|(% style="width:133px" %)A~|B|(% style="width:377px" %)Rule match if input is either 'A' or 'B'|(% style="width:194px" %)OUT_C 202 202 203 203 Like all mapping rules, the output is either a Code, a Value or free text depending on the representation of the Component in the target Data Structure Definition. 204 204 205 205 If the regular expression contains capture groups, these can be used in the definition of the output value, by specifying \//**n** //as an output value where //**n**// is the number of the capture group starting from 1. For example 206 206 207 -|Regex|Target output|Example Input|Example Output 208 -|((( 209 -([0-9]{4})[0- 200 +(% style="width:720.294px" %) 201 +|(% style="width:199px" %)**Regex**|(% style="width:126px" %)**Target output**|(% style="width:192px" %)**Example Input**|(% style="width:200px" %)**Example Output** 202 +|(% style="width:199px" %)((( 203 +([0-9]{4})[0-9]([0-9]{1}) 204 +)))|(% style="width:126px" %)\1-Q\2|(% style="width:192px" %)200933|(% style="width:200px" %)2009-Q3 210 210 211 -9]([0-9]{1}) 212 -)))|\1-Q\2|200933|2009-Q3 213 - 214 214 As regular expression rules can be used as a general catch-all if nothing else matches, the ordering of the rules is important. Rules should be tested starting with the highest priority, moving down the list until a match is found. 215 215 216 216 The following example shows this: 217 217 218 -|Priority|Regex|Description|Output 219 -|1|A|Rule match if input = 'A'|OUT_A 220 -|2|B|Rule match if input = 'B'|OUT_B 221 -|3|[A-Z]|Any character A-Z|OUT_C 210 +(% style="width:725.294px" %) 211 +|(% style="width:198px" %)**Priority**|(% style="width:148px" %)**Regex**|(% style="width:212px" %)**Description**|(% style="width:164px" %)**Output** 212 +|(% style="width:198px" %)1|(% style="width:148px" %)A|(% style="width:212px" %)Rule match if input = 'A'|(% style="width:164px" %)OUT_A 213 +|(% style="width:198px" %)2|(% style="width:148px" %)B|(% style="width:212px" %)Rule match if input = 'B'|(% style="width:164px" %)OUT_B 214 +|(% style="width:198px" %)3|(% style="width:148px" %)[A-Z]|(% style="width:212px" %)Any character A-Z|(% style="width:164px" %)OUT_C 222 222 223 223 The input 'A' matches both the first and the last rule, but the first takes precedence having the higher priority. The output is OUT_A. 224 224 ... ... @@ -230,9 +230,10 @@ 230 230 231 231 For instance: 232 232 233 -|Input String|Start|Length|Output 234 -|ABC_DEF_XYZ|5|3|DEF 235 -|XULADS|1|2|XU 226 +(% style="width:742.294px" %) 227 +|(% style="width:191px" %)**Input String**|(% style="width:154px" %)**Start**|(% style="width:211px" %)**Length**|(% style="width:182px" %)**Output** 228 +|(% style="width:191px" %)ABC_DEF_XYZ|(% style="width:154px" %)5|(% style="width:211px" %)3|(% style="width:182px" %)DEF 229 +|(% style="width:191px" %)XULADS|(% style="width:154px" %)1|(% style="width:211px" %)2|(% style="width:182px" %)XU 236 236 237 237 Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' map to Y// as shown in the following example: 238 238