Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 10.10
edited by Helena
on 2025/05/16 09:18
Change comment: There is no comment for this version
To version 10.1
edited by Helena
on 2025/05/15 15:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,4 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 += 13 Structure Mapping =
4 4  
5 5  == 13.1 Introduction ==
6 6  
... ... @@ -18,7 +18,7 @@
18 18  
19 19  * Transforming received data into a common internal structure;
20 20  * Transforming reported data into the data collector's preferred structure;
21 -* Transforming unidimensional datasets{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
19 +* Transforming unidimensional datasets^^[[^^43^^>>path:#sdfootnote43sym||name="sdfootnote43anc"]]^^ to multi-dimensional; and
22 22  * Transforming internal datasets with a complex structure to a simpler structure with fewer dimensions suitable for dissemination.
23 23  
24 24  == 13.2 1-1 structure maps ==
... ... @@ -27,25 +27,25 @@
27 27  
28 28  In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
29 29  
30 -(% style="width:666.294px" %)
31 -|(% style="width:217px" %)**Country**|(% style="width:251px" %)**Alpha-2 code**|(% style="width:195px" %)**Alpha-3 code**
32 -|(% style="width:217px" %)Afghanistan|(% style="width:251px" %)AF|(% style="width:195px" %)AFG
33 -|(% style="width:217px" %)Albania|(% style="width:251px" %)AL|(% style="width:195px" %)ALB
34 -|(% style="width:217px" %)Algeria|(% style="width:251px" %)DZ|(% style="width:195px" %)DZA
35 -|(% style="width:217px" %)American Samoa|(% style="width:251px" %)AS|(% style="width:195px" %)ASM
36 -|(% style="width:217px" %)Andorra|(% style="width:251px" %)AD|(% style="width:195px" %)AND
37 -|(% style="width:217px" %)etc…|(% style="width:251px" %) |(% style="width:195px" %)
28 +|Country|Alpha-2 code|Alpha-3 code
29 +|Afghanistan|AF|AFG
30 +|Albania|AL|ALB
31 +|Algeria|DZ|DZA
32 +|American Samoa|AS|ASM
33 +|Andorra|AD|AND
34 +|etc…||
38 38  
39 39  Different source values can also map to the same target value, for example when deriving regions from country codes.
40 40  
41 -(% style="width:674.294px" %)
42 -|(% style="width:284px" %)**Source Component: REF_AREA**|(% style="width:387px" %)**Target Component: REGION**
43 -|(% style="width:284px" %)FR|(% style="width:387px" %)EUR
44 -|(% style="width:284px" %)DE|(% style="width:387px" %)EUR
45 -|(% style="width:284px" %)IT|(% style="width:387px" %)EUR
46 -|(% style="width:284px" %)ES|(% style="width:387px" %)EUR
47 -|(% style="width:284px" %)BE|(% style="width:387px" %)EUR
38 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape7" height="1" width="192"]]
48 48  
40 +|Source Component: REF_AREA|Target Component: REGION
41 +|FR|EUR
42 +|DE|EUR
43 +|IT|EUR
44 +|ES|EUR
45 +|BE|EUR
46 +
49 49  == 13.3 N-n structure maps ==
50 50  
51 51  N-n (pronounced 'N to N') mappings describe rules where a specified combination of values in multiple source Components map to specified values in one or more target Components. For example, when mapping a partial Series Key from a highly multidimensional cube (like Balance of Payments) to a single 'Indicator' Dimension in a target Data Structure.
... ... @@ -52,42 +52,51 @@
52 52  
53 53  Example:
54 54  
55 -(% style="width:760.294px" %)
56 -|(% style="width:58px" %)**Rule**|(% style="width:384px" %)**Source**|(% style="width:313px" %)**Target**
57 -|(% style="width:58px" %)1|(% style="width:384px" %)(((
53 +|Rule|Source|Target
54 +|1|(((
58 58  If
56 +
59 59  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
60 -)))|(% style="width:313px" %)(((
58 +)))|(((
61 61  Set
60 +
62 62  INDICATOR=A_N_L
63 63  )))
64 -|(% style="width:58px" %)2|(% style="width:384px" %)(((
63 +|2|(((
65 65  If
65 +
66 66  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
67 -)))|(% style="width:313px" %)(((
67 +)))|(((
68 68  Set
69 +
69 69  INDICATOR=MON_SAX_12
70 70  )))
71 71  
72 72  N-n rules can also set values for multiple source Components.
73 73  
74 -(% style="width:757.294px" %)
75 -|(% style="width:62px" %)**Rule**|(% style="width:378px" %)**Source**|(% style="width:312px" %)**Target**
76 -|(% style="width:62px" %)1|(% style="width:378px" %)(((
75 +|Rule|Source|Target
76 +|1|(((
77 77  If
78 +
78 78  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
79 -)))|(% style="width:312px" %)(((
80 +)))|(((
80 80  Set
81 -INDICATOR=A_N_L,
82 -STATUS=QXR15,
82 +
83 +INDICATOR=A_N_L, STATUS=QXR15,
84 +
83 83  NOTE="Unadjusted".
84 84  )))
85 -|(% style="width:62px" %)2|(% style="width:378px" %)(((
87 +|2|(((
86 86  If
89 +
87 87  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
88 -)))|(% style="width:312px" %)(((
91 +)))|(((
89 89  Set
90 -INDICATOR=MON_SAX_12, STATUS=MPM12,
93 +
94 +INDICATOR=MON_SAX_12,
95 +
96 +STATUS=MPM12,
97 +
91 91  NOTE="Seasonally Adjusted"
92 92  )))
93 93  
... ... @@ -97,26 +97,37 @@
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 -(% 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" %)(((
107 +|Source|Target|Output Series Key
108 +|SERIES_CODE=XMAN_Z_21|(((
103 103  Dimensions
110 +
104 104  INDICATOR=XM
112 +
105 105  FREQ=A
114 +
106 106  ADJUSTMENT=N
116 +
107 107  Attributes
118 +
108 108  UNIT_MEASURE=_Z
120 +
109 109  COMP_ORG=21
110 -)))|(% style="width:329px" %)XM:A:N
111 -|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((
122 +)))|XM:A:N
123 +|SERIES_CODE=XMAN_Z_34|(((
112 112  Dimensions
125 +
113 113  INDICATOR=XM
127 +
114 114  FREQ=A
129 +
115 115  ADJUSTMENT=N
131 +
116 116  Attributes
133 +
117 117  UNIT_MEASURE=_Z
135 +
118 118  COMP_ORG=34
119 -)))|(% style="width:329px" %)XM:A:N
137 +)))|XM:A:N
120 120  
121 121  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.
122 122  
... ... @@ -132,26 +132,24 @@
132 132  
133 133  A Representation Map mapping ISO 2-character to ISO 3-character Codelists would take the following form:
134 134  
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 +|CL_ISO_ALPHA2|CL_ISO_ALPHA3
154 +|AF|AFG
155 +|AL|ALB
156 +|DZ|DZA
157 +|AS|ASM
158 +|AD|AND
159 +|etc…|
143 143  
144 144  A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described:
145 145  
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" %)
163 +|Text|CL_ISO_ALPHA2
164 +|"Germany"|DE
165 +|"France"|FR
166 +|"United Kingdom"|GB
167 +|"Great Britain"|GB
168 +|"Ireland"|IE
169 +|"Eire"|IE
170 +|etc…|
155 155  
156 156  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.
157 157  
... ... @@ -159,11 +159,10 @@
159 159  
160 160  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:
161 161  
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
178 +|Value|Locale|Name
179 +|$|en|United States Dollar
180 +|%|En|Percentage
181 +||fr|Pourcentage
167 167  
168 168  Other characteristics of Representation Maps:
169 169  
... ... @@ -187,31 +187,30 @@
187 187  
188 188  Below is an example set of regular expression rules for a particular component.
189 189  
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
205 +|Regex|Description|Output
206 +|A|Rule match if input = 'A'|OUT_A
207 +|^[A-G]|Rule match if the input starts with letters A to G|OUT_B
208 +|A~|B|Rule match if input is either 'A' or 'B'|OUT_C
195 195  
196 196  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.
197 197  
198 198  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
199 199  
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
214 +|Regex|Target output|Example Input|Example Output
215 +|(((
216 +([0-9]{4})[0-
205 205  
218 +9]([0-9]{1})
219 +)))|\1-Q\2|200933|2009-Q3
220 +
206 206  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.
207 207  
208 208  The following example shows this:
209 209  
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
225 +|Priority|Regex|Description|Output
226 +|1|A|Rule match if input = 'A'|OUT_A
227 +|2|B|Rule match if input = 'B'|OUT_B
228 +|3|[A-Z]|Any character A-Z|OUT_C
215 215  
216 216  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.
217 217  
... ... @@ -223,10 +223,9 @@
223 223  
224 224  For instance:
225 225  
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
240 +|Input String|Start|Length|Output
241 +|ABC_DEF_XYZ|5|3|DEF
242 +|XULADS|1|2|XU
230 230  
231 231  Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' map to Y// as shown in the following example:
232 232  
... ... @@ -264,7 +264,7 @@
264 264  
265 265  Date and time formats are specified by date and time pattern strings based on Java's Simple Date Format. Within date and time pattern strings, unquoted letters from 'A' to 'Z' and from 'a' to 'z' are interpreted as pattern letters representing the components of a date or time string. Text can be quoted using single quotes (') to avoid interpretation. "''" represents a single quote. All other characters are not interpreted; they're simply copied into the output string during formatting or matched against the input string during parsing.
266 266  
267 -Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^44^^>>path:#sdfootnote44sym||name="sdfootnote44anc"]](%%)^^. An indicative list of examples is presented in the following table:
280 +Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale^^[[^^44^^>>path:#sdfootnote44sym||name="sdfootnote44anc"]]^^. An indicative list of examples is presented in the following table:
268 268  
269 269  |English (en)|Australia (AU)|en-AU
270 270  |English (en)|Canada (CA)|en-CA
... ... @@ -310,7 +310,7 @@
310 310  
311 311  |Letter|Date or Time Component|Presentation|Examples
312 312  |G|Era designator|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|AD
313 -|yy|Year short (upper case is Year of Week^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^45^^>>path:#sdfootnote45sym||name="sdfootnote45anc"]](%%)^^)|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
326 +|yy|Year short (upper case is Year of Week^^[[^^45^^>>path:#sdfootnote45sym||name="sdfootnote45anc"]]^^)|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
314 314  |yyyy|Year Full (upper case is Year of Week)|Year|1996
315 315  |MM|Month number in year starting with 1|Month|07
316 316  |MMM|Month name short|Month|Jul
... ... @@ -515,7 +515,7 @@
515 515  
516 516  The following representation mapping can be used to explicitly map each age to an output code.
517 517  
518 -:
531 +:
519 519  
520 520  (((
521 521  |Source Input Free Text|Desired Output Code Id
... ... @@ -532,7 +532,7 @@
532 532  
533 533  __Regular Expression __Desired Output
534 534  
535 -:
548 +:
536 536  
537 537  (((
538 538  |[0-2]|A
... ... @@ -543,7 +543,7 @@
543 543  
544 544  This use case is where a specific observation for a specific time period has an attribute 3468 value.
545 545  
546 -:
559 +:
547 547  
548 548  (((
549 549  |Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
... ... @@ -564,7 +564,7 @@
564 564  
565 565  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
566 566  
567 -:
580 +:
568 568  
569 569  (((
570 570  |Source Value|Source Mapping|Target Frequency|Output
... ... @@ -575,18 +575,18 @@
575 575  
576 576  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
577 577  
578 -:
579 -::
591 +:
592 +::
580 580  
581 581  (((
582 582  |Source Value|Source Mapping|Target Frequency Output Dimension
583 583  
584 -|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D)
597 +|18/07/1981 dd/MM/yyyy|FREQ||1981-07-18 (when FREQ=D)
585 585  |(% rowspan="2" %)(((
586 586  __When the source is a numerical form__at
587 587  
588 588  Source Value Start Period Interv
589 -)))| | |
602 +)))|||
590 590  |al|(((
591 591  Target
592 592  
... ... @@ -610,5 +610,3 @@
610 610  Dimension
611 611  
612 612  1981 yyyy D – End of Period 1982-03-31
613 -
614 -{{putFootnotes/}}