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
-
... ... @@ -78,7 +78,9 @@ 78 78 FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L. 79 79 )))|(% style="width:312px" %)((( 80 80 Set 81 -INDICATOR=A_N_L, STATUS=QXR15, NOTE="Unadjusted". 81 +INDICATOR=A_N_L, 82 +STATUS=QXR15, 83 +NOTE="Unadjusted". 82 82 ))) 83 83 |(% style="width:62px" %)2|(% style="width:378px" %)((( 84 84 If ... ... @@ -85,7 +85,8 @@ 85 85 FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12. 86 86 )))|(% style="width:312px" %)((( 87 87 Set 88 -INDICATOR=MON_SAX_12, STATUS=MPM12, NOTE="Seasonally Adjusted" 90 +INDICATOR=MON_SAX_12, STATUS=MPM12, 91 +NOTE="Seasonally Adjusted" 89 89 ))) 90 90 91 91 == 13.4 Ambiguous mapping rules == ... ... @@ -94,37 +94,26 @@ 94 94 95 95 A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below: 96 96 97 -|Source|Target|Output Series Key 98 -|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" %)((( 99 99 Dimensions 100 - 101 101 INDICATOR=XM 102 - 103 103 FREQ=A 104 - 105 105 ADJUSTMENT=N 106 - 107 107 Attributes 108 - 109 109 UNIT_MEASURE=_Z 110 - 111 111 COMP_ORG=21 112 -)))|XM:A:N 113 -|SERIES_CODE=XMAN_Z_34|((( 110 +)))|(% style="width:329px" %)XM:A:N 111 +|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)((( 114 114 Dimensions 115 - 116 116 INDICATOR=XM 117 - 118 118 FREQ=A 119 - 120 120 ADJUSTMENT=N 121 - 122 122 Attributes 123 - 124 124 UNIT_MEASURE=_Z 125 - 126 126 COMP_ORG=34 127 -)))|XM:A:N 119 +)))|(% style="width:329px" %)XM:A:N 128 128 129 129 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. 130 130 ... ... @@ -140,24 +140,26 @@ 140 140 141 141 A Representation Map mapping ISO 2-character to ISO 3-character Codelists would take the following form: 142 142 143 -|CL_ISO_ALPHA2|CL_ISO_ALPHA3 144 -|AF|AFG 145 -|AL|ALB 146 -|DZ|DZA 147 -|AS|ASM 148 -|AD|AND 149 -|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" %) 150 150 151 151 A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described: 152 152 153 -|Text|CL_ISO_ALPHA2 154 -|"Germany"|DE 155 -|"France"|FR 156 -|"United Kingdom"|GB 157 -|"Great Britain"|GB 158 -|"Ireland"|IE 159 -|"Eire"|IE 160 -|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" %) 161 161 162 162 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. 163 163 ... ... @@ -165,10 +165,11 @@ 165 165 166 166 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: 167 167 168 -|Value|Locale|Name 169 -|$|en|United States Dollar 170 -|%|En|Percentage 171 -| |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 172 172 173 173 Other characteristics of Representation Maps: 174 174 ... ... @@ -192,30 +192,31 @@ 192 192 193 193 Below is an example set of regular expression rules for a particular component. 194 194 195 -|Regex|Description|Output 196 -|A|Rule match if input = 'A'|OUT_A 197 -|^[A-G]|Rule match if the input starts with letters A to G|OUT_B 198 -|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 199 199 200 200 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. 201 201 202 202 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 203 203 204 -|Regex|Target output|Example Input|Example Output 205 -|((( 206 -([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 207 207 208 -9]([0-9]{1}) 209 -)))|\1-Q\2|200933|2009-Q3 210 - 211 211 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. 212 212 213 213 The following example shows this: 214 214 215 -|Priority|Regex|Description|Output 216 -|1|A|Rule match if input = 'A'|OUT_A 217 -|2|B|Rule match if input = 'B'|OUT_B 218 -|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 219 219 220 220 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. 221 221 ... ... @@ -227,9 +227,10 @@ 227 227 228 228 For instance: 229 229 230 -|Input String|Start|Length|Output 231 -|ABC_DEF_XYZ|5|3|DEF 232 -|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 233 233 234 234 Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' map to Y// as shown in the following example: 235 235