Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19

From 9.1 to 8.1 From 10.9 to 10.8

From version 10.8

edited by Helena
on 2025/05/16 09:15

Change comment: There is no comment for this version

To version 9.1

edited by Helena
on 2025/05/15 15:48

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a3215c79.jpg

Details

Page properties

Content

@@ -1,6 +1,4 @@
--{{box title="**Contents**"}}
--{{toc/}}
--{{/box}}
++= 13 Structure Mapping =
  == 13.1 Introduction ==
@@ -18,7 +18,7 @@
  * Transforming received data into a common internal structure;
  * Transforming reported data into the data collector's preferred structure;
--* Transforming unidimensional datasets{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
++* Transforming unidimensional datasets^^[[^^43^^>>path:#sdfootnote43sym||name="sdfootnote43anc"]]^^ to multi-dimensional; and
  * Transforming internal datasets with a complex structure to a simpler structure with fewer dimensions suitable for dissemination.
  == 13.2 1-1 structure maps ==
@@ -27,25 +27,25 @@
  In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
--(% style="width:666.294px" %)
--|(% style="width:217px" %)**Country**|(% style="width:251px" %)**Alpha-2 code**|(% style="width:195px" %)**Alpha-3 code**
--|(% style="width:217px" %)Afghanistan|(% style="width:251px" %)AF|(% style="width:195px" %)AFG
--|(% style="width:217px" %)Albania|(% style="width:251px" %)AL|(% style="width:195px" %)ALB
--|(% style="width:217px" %)Algeria|(% style="width:251px" %)DZ|(% style="width:195px" %)DZA
--|(% style="width:217px" %)American Samoa|(% style="width:251px" %)AS|(% style="width:195px" %)ASM
--|(% style="width:217px" %)Andorra|(% style="width:251px" %)AD|(% style="width:195px" %)AND
--|(% style="width:217px" %)etc…|(% style="width:251px" %) |(% style="width:195px" %)
++|Country|Alpha-2 code|Alpha-3 code
++|Afghanistan|AF|AFG
++|Albania|AL|ALB
++|Algeria|DZ|DZA
++|American Samoa|AS|ASM
++|Andorra|AD|AND
++|etc…||
  Different source values can also map to the same target value, for example when deriving regions from country codes.
--(% style="width:674.294px" %)
--|(% style="width:284px" %)**Source Component: REF_AREA**|(% style="width:387px" %)**Target Component: REGION**
--|(% style="width:284px" %)FR|(% style="width:387px" %)EUR
--|(% style="width:284px" %)DE|(% style="width:387px" %)EUR
--|(% style="width:284px" %)IT|(% style="width:387px" %)EUR
--|(% style="width:284px" %)ES|(% style="width:387px" %)EUR
--|(% style="width:284px" %)BE|(% style="width:387px" %)EUR
++[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape7" height="1" width="192"]]
++|Source Component: REF_AREA|Target Component: REGION
++|FR|EUR
++|DE|EUR
++|IT|EUR
++|ES|EUR
++|BE|EUR
++
  == 13.3 N-n structure maps ==
  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 @@
  Example:
--(% style="width:760.294px" %)
--|(% style="width:58px" %)**Rule**|(% style="width:384px" %)**Source**|(% style="width:313px" %)**Target**
--|(% style="width:58px" %)1|(% style="width:384px" %)(((
++|Rule|Source|Target
++|1|(((
  If
++
  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
--)))|(% style="width:313px" %)(((
++)))|(((
  Set
++
  INDICATOR=A_N_L
  )))
--|(% style="width:58px" %)2|(% style="width:384px" %)(((
++|2|(((
  If
++
  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
--)))|(% style="width:313px" %)(((
++)))|(((
  Set
++
  INDICATOR=MON_SAX_12
  )))
  N-n rules can also set values for multiple source Components.
--(% style="width:757.294px" %)
--|(% style="width:62px" %)**Rule**|(% style="width:378px" %)**Source**|(% style="width:312px" %)**Target**
--|(% style="width:62px" %)1|(% style="width:378px" %)(((
++|Rule|Source|Target
++|1|(((
  If
++
  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
--)))|(% style="width:312px" %)(((
++)))|(((
  Set
--INDICATOR=A_N_L,
--STATUS=QXR15,
++
++INDICATOR=A_N_L, STATUS=QXR15,
++
  NOTE="Unadjusted".
  )))
--|(% style="width:62px" %)2|(% style="width:378px" %)(((
++|2|(((
  If
++
  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
--)))|(% style="width:312px" %)(((
++)))|(((
  Set
--INDICATOR=MON_SAX_12, STATUS=MPM12,
++
++INDICATOR=MON_SAX_12,
++
++STATUS=MPM12,
++
  NOTE="Seasonally Adjusted"
  )))
@@ -97,26 +97,37 @@
  A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below:
--(% style="width:819.294px" %)
--|(% style="width:240px" %)**Source**|(% style="width:246px" %)**Target**|(% style="width:329px" %)**Output Series Key**
--|(% style="width:240px" %)SERIES_CODE=XMAN_Z_21|(% style="width:246px" %)(((
++|Source|Target|Output Series Key
++|SERIES_CODE=XMAN_Z_21|(((
  Dimensions
++
  INDICATOR=XM
++
  FREQ=A
++
  ADJUSTMENT=N
++
  Attributes
++
  UNIT_MEASURE=_Z
++
  COMP_ORG=21
--)))|(% style="width:329px" %)XM:A:N
--|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((
++)))|XM:A:N
++|SERIES_CODE=XMAN_Z_34|(((
  Dimensions
++
  INDICATOR=XM
++
  FREQ=A
++
  ADJUSTMENT=N
++
  Attributes
++
  UNIT_MEASURE=_Z
++
  COMP_ORG=34
--)))|(% style="width:329px" %)XM:A:N
++)))|XM:A:N
  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.
@@ -138,7 +138,7 @@
  |DZ|DZA
  |AS|ASM
  |AD|AND
--|etc…|
++|etc…|
  A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described:
@@ -149,7 +149,7 @@
  |"Great Britain"|GB
  |"Ireland"|IE
  |"Eire"|IE
--|etc…|
++|etc…|
  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.
@@ -160,7 +160,7 @@
  |Value|Locale|Name
  |$|en|United States Dollar
  |%|En|Percentage
--| |fr|Pourcentage
++||fr|Pourcentage
  Other characteristics of Representation Maps:
@@ -259,7 +259,7 @@
  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.
--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:
++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:
  |English (en)|Australia (AU)|en-AU
  |English (en)|Canada (CA)|en-CA
@@ -305,7 +305,7 @@
  |Letter|Date or Time Component|Presentation|Examples
  |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
--|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
++|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
  |yyyy|Year Full (upper case is Year of Week)|Year|1996
  |MM|Month number in year starting with 1|Month|07
  |MMM|Month name short|Month|Jul
@@ -510,7 +510,7 @@
  The following representation mapping can be used to explicitly map each age to an output code.
--:
++:
  (((
  |Source Input Free Text|Desired Output Code Id
@@ -527,7 +527,7 @@
  __Regular Expression __Desired Output
--:
++:
  (((
  |[0-2]|A
@@ -538,7 +538,7 @@
  This use case is where a specific observation for a specific time period has an attribute 3468 value.
--:
++:
  (((
  |Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
@@ -559,7 +559,7 @@
  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
--:
++:
  (((
  |Source Value|Source Mapping|Target Frequency|Output
@@ -570,18 +570,18 @@
  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
--:
--::
++:
++::
  (((
  |Source Value|Source Mapping|Target Frequency Output Dimension
--|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D)
++|18/07/1981 dd/MM/yyyy|FREQ||1981-07-18 (when FREQ=D)
  |(% rowspan="2" %)(((
  __When the source is a numerical form__at
  Source Value Start Period Interv
--)))| | |
++)))|||
  |al|(((
  Target
@@ -605,5 +605,3 @@
  Dimension
 yyyy D – End of Period 1982-03-31
--
--{{putFootnotes/}}

SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a3215c79.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-30.6 KB

Content