Skip to Content

Changes for page 13 Structure Mapping

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

Summary

Details

Page properties
Content
... ... @@ -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^^[[(% class="wikiinternallink wikiinternallink" %)^^43^^>>path:#sdfootnote43sym||name="sdfootnote43anc"]](%%)^^ to multi-dimensional; and
21 +* Transforming unidimensional datasets{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} 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 -|Country|Alpha-2 code|Alpha-3 code
31 -|Afghanistan|AF|AFG
32 -|Albania|AL|ALB
33 -|Algeria|DZ|DZA
34 -|American Samoa|AS|ASM
35 -|Andorra|AD|AND
36 -|etc…| |
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" %)
37 37  
38 38  Different source values can also map to the same target value, for example when deriving regions from country codes.
39 39  
40 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape7" height="1" width="192"]]
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
41 41  
42 -|Source Component: REF_AREA|Target Component: REGION
43 -|FR|EUR
44 -|DE|EUR
45 -|IT|EUR
46 -|ES|EUR
47 -|BE|EUR
48 -
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,51 +52,42 @@
52 52  
53 53  Example:
54 54  
55 -|Rule|Source|Target
56 -|1|(((
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" %)(((
57 57  If
58 -
59 59  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
60 -)))|(((
60 +)))|(% style="width:313px" %)(((
61 61  Set
62 -
63 63  INDICATOR=A_N_L
64 64  )))
65 -|2|(((
64 +|(% style="width:58px" %)2|(% style="width:384px" %)(((
66 66  If
67 -
68 68  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
69 -)))|(((
67 +)))|(% style="width:313px" %)(((
70 70  Set
71 -
72 72  INDICATOR=MON_SAX_12
73 73  )))
74 74  
75 75  N-n rules can also set values for multiple source Components.
76 76  
77 -|Rule|Source|Target
78 -|1|(((
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" %)(((
79 79  If
80 -
81 81  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
82 -)))|(((
79 +)))|(% style="width:312px" %)(((
83 83  Set
84 -
85 -INDICATOR=A_N_L, STATUS=QXR15,
86 -
81 +INDICATOR=A_N_L,
82 +STATUS=QXR15,
87 87  NOTE="Unadjusted".
88 88  )))
89 -|2|(((
85 +|(% style="width:62px" %)2|(% style="width:378px" %)(((
90 90  If
91 -
92 92  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
93 -)))|(((
88 +)))|(% style="width:312px" %)(((
94 94  Set
95 -
96 -INDICATOR=MON_SAX_12,
97 -
98 -STATUS=MPM12,
99 -
90 +INDICATOR=MON_SAX_12, STATUS=MPM12,
100 100  NOTE="Seasonally Adjusted"
101 101  )))
102 102  
... ... @@ -106,37 +106,26 @@
106 106  
107 107  A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below:
108 108  
109 -|Source|Target|Output Series Key
110 -|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" %)(((
111 111  Dimensions
112 -
113 113  INDICATOR=XM
114 -
115 115  FREQ=A
116 -
117 117  ADJUSTMENT=N
118 -
119 119  Attributes
120 -
121 121  UNIT_MEASURE=_Z
122 -
123 123  COMP_ORG=21
124 -)))|XM:A:N
125 -|SERIES_CODE=XMAN_Z_34|(((
110 +)))|(% style="width:329px" %)XM:A:N
111 +|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((
126 126  Dimensions
127 -
128 128  INDICATOR=XM
129 -
130 130  FREQ=A
131 -
132 132  ADJUSTMENT=N
133 -
134 134  Attributes
135 -
136 136  UNIT_MEASURE=_Z
137 -
138 138  COMP_ORG=34
139 -)))|XM:A:N
119 +)))|(% style="width:329px" %)XM:A:N
140 140  
141 141  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.
142 142  
... ... @@ -279,7 +279,7 @@
279 279  
280 280  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.
281 281  
282 -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" %)^^44^^>>path:#sdfootnote44sym||name="sdfootnote44anc"]](%%)^^. An indicative list of examples is presented in the following table:
262 +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:
283 283  
284 284  |English (en)|Australia (AU)|en-AU
285 285  |English (en)|Canada (CA)|en-CA
... ... @@ -325,7 +325,7 @@
325 325  
326 326  |Letter|Date or Time Component|Presentation|Examples
327 327  |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
328 -|yy|Year short (upper case is Year of Week^^[[(% class="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
308 +|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
329 329  |yyyy|Year Full (upper case is Year of Week)|Year|1996
330 330  |MM|Month number in year starting with 1|Month|07
331 331  |MMM|Month name short|Month|Jul
... ... @@ -625,3 +625,5 @@
625 625  Dimension
626 626  
627 627  1981 yyyy D – End of Period 1982-03-31
608 +
609 +{{putFootnotes/}}