Changes for page 13 Structure Mapping

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

From version 4.9
edited by Helena
on 2025/06/16 14:50
Change comment: There is no comment for this version
To version 7.1
edited by Helena
on 2025/06/16 15:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,52 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 +(% contenteditable="false" tabindex="-1" %)
2 +(((
3 +(% class="macro" data-macro="startmacro:box|-|title=~"**Contents**~"|-|\{\{toc/}}" data-widget="xwiki-macro" %)
4 +(((
5 +(% class="macro-placeholder hidden" %)
6 +(((
7 +macro:box
8 +)))
4 4  
10 +(% class="box" %)
11 +(((
12 +(% class="box-title" %)
13 +(((
14 +**Contents**
15 +)))
16 +
17 +(% class="macro" data-macro="startmacro:toc|-|" %)
18 +(((
19 +(% class="macro-placeholder hidden" %)
20 +(((
21 +macro:toc
22 +)))
23 +
24 +(% class="wikitoc" %)
25 +*
26 +** [[13.1 Introduction>>doc:null||anchor="H13.1Introduction"]]
27 +** [[13.2 1-1 structure maps>>doc:null||anchor="H13.21-1structuremaps"]]
28 +** [[13.3 N-n structure maps>>doc:null||anchor="H13.3N-nstructuremaps"]]
29 +** [[13.4 Ambiguous mapping rules>>doc:null||anchor="H13.4Ambiguousmappingrules"]]
30 +** [[13.5 Representation maps>>doc:null||anchor="H13.5Representationmaps"]]
31 +** [[13.6 Regular expression and substring rules>>doc:null||anchor="H13.6Regularexpressionandsubstringrules"]]
32 +*** [[13.6.1 Regular expressions>>doc:null||anchor="H13.6.1Regularexpressions"]]
33 +*** [[13.6.2 Substrings>>doc:null||anchor="H13.6.2Substrings"]]
34 +** [[13.7 Mapping non-SDMX time formats to SDMX formats>>doc:null||anchor="H13.7Mappingnon-SDMXtimeformatstoSDMXformats"]]
35 +*** [[13.7.1 Pattern based dates>>doc:null||anchor="H13.7.1Patternbaseddates"]]
36 +*** [[13.7.2 Numerical based datetime>>doc:null||anchor="H13.7.2Numericalbaseddatetime"]]
37 +*** [[13.7.3 Mapping more complex time inputs>>doc:null||anchor="H13.7.3Mappingmorecomplextimeinputs"]]
38 +** [[13.8 Using TIME_PERIOD in mapping rules>>doc:null||anchor="H13.8UsingTIME_PERIODinmappingrules"]]
39 +** [[13.9 Time span mapping rules using validity periods>>doc:null||anchor="H13.9Timespanmappingrulesusingvalidityperiods"]]
40 +** [[13.10 Mapping examples>>doc:null||anchor="H13.10Mappingexamples"]]
41 +*** [[13.10.1 Many to one mapping (N3513 -1)>>doc:null||anchor="H13.10.1A0Manytoonemapping28N3513-129"]]
42 +*** [[13.10.2 Mapping other data types to Code Id>>doc:null||anchor="H13.10.2MappingotherdatatypestoCodeId"]]
43 +*** [[13.10.3 Observation Attributes for Time Period>>doc:null||anchor="H13.10.3ObservationAttributesforTimePeriod"]]
44 +*** [[13.10.4 Time mapping>>doc:null||anchor="H13.10.4Timemapping"]]
45 +)))
46 +)))
47 +)))
48 +)))
49 +
5 5  == 13.1 Introduction ==
6 6  
7 7  The purpose of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure mapping is to transform [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] from one dimensionality to another. In practice, this means that the input and output [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] conform to different Data Structure Definition.
... ... @@ -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>>doc:sdmx:Glossary.Data set.WebHome]]{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
66 +* Transforming unidimensional [[datasets>>doc:sdmx:Glossary.Data set.WebHome]](% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|Unidimensional datasets are those with a single 'indicator' or 'series code' dimension." data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|Unidimensional datasets are those with a single 'indicator' or 'series code' dimension." data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_1" %)^^[[1>>doc:null||anchor="x_footnote_1"]]^^(%%) to multi-dimensional; and
22 22  * Transforming internal [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] with a complex structure to a simpler structure with fewer [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] suitable for dissemination.
23 23  
24 24  == 13.2 1-1 structure maps ==
... ... @@ -225,7 +225,7 @@
225 225  
226 226  The input 'G' matches on the last rule which is used as a catch-all or default in this example.
227 227  
228 -=== 13. Substrings ===
273 +=== 13.6.2 Substrings ===
229 229  
230 230  Substrings provide an alternative to regular expressions where the required section of an input value can be described using the number of the starting character, and the length of the substring in characters. The first character is at position 1.
231 231  
... ... @@ -278,7 +278,7 @@
278 278  
279 279  Date and [[time formats>>doc:sdmx:Glossary.Time format.WebHome]] 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>>doc:sdmx:Glossary.Component.WebHome]] 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.
280 280  
281 -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{{footnote}} A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html{{/footnote}}. An indicative list of examples is presented in the following table:
326 +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(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html" data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html" data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_2" %)^^[[2>>doc:null||anchor="x_footnote_2"]]^^(%%). An indicative list of examples is presented in the following table:
282 282  
283 283  (% style="width:604.294px" %)
284 284  |(% style="width:172px" %)English (en)|(% style="width:216px" %)Australia (AU)|(% style="width:213px" %)en-AU
... ... @@ -311,58 +311,55 @@
311 311  Examples
312 312  
313 313  22/06/1981 would be described as dd/MM/YYYY, with locale en-GB
314 -
315 315  2008-mars-12 would be described as YYYY-MMM-DD, with locale fr-FR
316 -
317 317  22 July 1981 would be described as dd MMMM YYYY, with locale en-US
318 -
319 319  22 Jul 1981 would be described as dd MMM YYYY
320 -
321 321  2010 D62 would be described as YYYYDnn (day 62 of the year 2010)
322 322  
323 323  The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):
324 324  
325 -|Letter|Date or Time Component|Presentation|Examples
326 -|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
327 -|yy|Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}})|[[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
328 -|yyyy|Year Full (upper case is Year of Week)|Year|1996
329 -|MM|Month number in year starting with 1|Month|07
330 -|MMM|Month name short|Month|Jul
331 -|MMMM|Month name full|Month|July
332 -|ww|Week in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|27
333 -|W|Week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
334 -|DD|Day in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|189
335 -|dd|Day in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|10
336 -|F|Day of week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
337 -|E|Day name in week|[[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]]|Tuesday; Tue
338 -|U|Day number of week (1 = Monday, ..., 7 = Sunday)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|1
339 -|HH|Hour in day (0-23)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
340 -|kk|Hour in day (1-24)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|24
341 -|KK|Hour in am/pm (0-11)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
342 -|hh|Hour in am/pm (1-12)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
343 -|mm|Minute in hour|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|30
344 -|ss|Second in minute|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|55
345 -|S|Millisecond|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|978
346 -|n|(((
366 +(% style="width:850.294px" %)
367 +|(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples**
368 +|(% style="width:125px" %)G|(% style="width:385px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD
369 +|(% style="width:125px" %)yy|(% style="width:385px" %)Year short (upper case is Year of Week(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years" data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years" data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_3" %)^^[[3>>doc:null||anchor="x_footnote_3"]]^^(%%))|(% style="width:180px" %)Year|(% style="width:157px" %)96
370 +|(% style="width:125px" %)yyyy|(% style="width:385px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996
371 +|(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07
372 +|(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul
373 +|(% style="width:125px" %)MMMM|(% style="width:385px" %)Month name full|(% style="width:180px" %)Month|(% style="width:157px" %)July
374 +|(% style="width:125px" %)ww|(% style="width:385px" %)Week in year|(% style="width:180px" %)Number|(% style="width:157px" %)27
375 +|(% style="width:125px" %)W|(% style="width:385px" %)Week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
376 +|(% style="width:125px" %)DD|(% style="width:385px" %)Day in year|(% style="width:180px" %)Number|(% style="width:157px" %)189
377 +|(% style="width:125px" %)dd|(% style="width:385px" %)Day in month|(% style="width:180px" %)Number|(% style="width:157px" %)10
378 +|(% style="width:125px" %)F|(% style="width:385px" %)Day of week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
379 +|(% style="width:125px" %)E|(% style="width:385px" %)Day name in week|(% style="width:180px" %)Text|(% style="width:157px" %)Tuesday; Tue
380 +|(% style="width:125px" %)U|(% style="width:385px" %)Day number of week (1 = Monday, ..., 7 = Sunday)|(% style="width:180px" %)Number|(% style="width:157px" %)1
381 +|(% style="width:125px" %)HH|(% style="width:385px" %)Hour in day (0-23)|(% style="width:180px" %)Number|(% style="width:157px" %)0
382 +|(% style="width:125px" %)kk|(% style="width:385px" %)Hour in day (1-24)|(% style="width:180px" %)Number|(% style="width:157px" %)24
383 +|(% style="width:125px" %)KK|(% style="width:385px" %)Hour in am/pm (0-11)|(% style="width:180px" %)Number|(% style="width:157px" %)0
384 +|(% style="width:125px" %)hh|(% style="width:385px" %)Hour in am/pm (1-12)|(% style="width:180px" %)Number|(% style="width:157px" %)12
385 +|(% style="width:125px" %)mm|(% style="width:385px" %)Minute in hour|(% style="width:180px" %)Number|(% style="width:157px" %)30
386 +|(% style="width:125px" %)ss|(% style="width:385px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55
387 +|(% style="width:125px" %)S|(% style="width:385px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978
388 +|(% style="width:125px" %)n|(% style="width:385px" %)(((
347 347  Number of periods, used after a SDMX
348 -
349 349  Frequency Identifier such as M, Q, D (month, quarter, day)
350 -)))|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
391 +)))|(% style="width:180px" %)Number|(% style="width:157px" %)12
351 351  
352 352  The model is illustrated below:
353 353  
395 +(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png||data-widget="image"]]
354 354  
355 -
356 356  **Figure 24 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD dimension with the additional information on the component map to describe the time format?**
357 357  
399 +(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png||data-widget="image"]]
358 358  
401 +(% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %)
402 +**Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension**
359 359  
360 -==== Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension ====
404 +=== 13.7.2 Numerical based datetime ===
361 361  
362 -=== 13.3.6 Numerical based datetime ===
406 +Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Time Period>>doc:sdmx:Glossary.Time period.WebHome]], and the **Period** which must take one of the following enumerated values:
363 363  
364 -Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid SDMX Time Period, and the **Period** which must take one of the following enumerated values:
365 -
366 366  * day
367 367  * second
368 368  * millisecond
... ... @@ -369,75 +369,63 @@
369 369  * microsecond
370 370  * nanosecond
371 371  
372 -|Numerical datetime systems|Base|Period
373 -|(((
414 +(% style="width:545.294px" %)
415 +|(% style="width:268px" %)Numerical datetime systems|(% style="width:121px" %)Base|(% style="width:153px" %)Period
416 +|(% style="width:268px" %)(((
374 374  Epoch Time (UNIX)
375 -
376 376  Milliseconds since 01 Jan 1970
377 -)))|1970|millisecond
378 -|(((
419 +)))|(% style="width:121px" %)1970|(% style="width:153px" %)millisecond
420 +|(% style="width:268px" %)(((
379 379  Windows System Time
380 -
381 381  Milliseconds since 01 Jan 1601
382 -)))|1601|millisecond
423 +)))|(% style="width:121px" %)1601|(% style="width:153px" %)millisecond
383 383  
384 384  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
385 385  
386 386  The model is illustrated below:
387 387  
388 -[[image:1750072341491-790.jpeg]]
429 +(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png||data-widget="image"]]
389 389  
390 -**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the**
431 +**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use **
391 391  
392 -==== TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use ====
433 +=== 13.7.3 Mapping more complex time inputs ===
393 393  
394 -=== Mapping more complex time inputs ===
435 +[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
395 395  
396 -VTL should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
437 +== 13.8 Using TIME_PERIOD in mapping rules ==
397 397  
398 -== Using TIME_PERIOD in mapping rules ==
439 +The source TIME_PERIOD [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] can be used in conjunction with other input [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] to create discrete mapping rules where the output is conditional on the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] value.
399 399  
400 -The source TIME_PERIOD Dimension can be used in conjunction with other input Dimensions to create discrete mapping rules where the output is conditional on the time period value.
441 +The main use case is setting the value of Observation [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] in the target [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
401 401  
402 -The main use case is setting the value of Observation Attributes in the target dataset.
403 -
404 -|Rule|Source|Target
405 -|1|(((
443 +(% style="width:709.294px" %)
444 +|(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target**
445 +|(% style="width:103px" %)1|(% style="width:405px" %)(((
406 406  If
407 -
408 408  INDICATOR=XULADS; and TIME_PERIOD=2007.
409 -)))|(((
410 -Set
411 -
412 -OBS_CONF=F
448 +)))|(% style="width:198px" %)(((
449 +Set OBS_CONF=F
413 413  )))
414 -|2|(((
451 +|(% style="width:103px" %)2|(% style="width:405px" %)(((
415 415  If
416 -
417 417  INDICATOR=XULADS; and TIME_PERIOD=2008.
418 -)))|Set OBS_CONF=F
419 -|3|(((
454 +)))|(% style="width:198px" %)Set OBS_CONF=F
455 +|(% style="width:103px" %)3|(% style="width:405px" %)(((
420 420  If
421 -
422 422  INDICATOR=XULADS; and TIME_PERIOD=2009.
423 -)))|(((
424 -Set
425 -
426 -OBS_CONF=F
458 +)))|(% style="width:198px" %)(((
459 +Set OBS_CONF=F
427 427  )))
428 -|4|(((
461 +|(% style="width:103px" %)4|(% style="width:405px" %)(((
429 429  If
430 -
431 431  INDICATOR=XULADS; and TIME_PERIOD=2010.
432 -)))|(((
433 -Set
434 -
435 -OBS_CONF=**C**
464 +)))|(% style="width:198px" %)(((
465 +Set OBS_CONF=**C**
436 436  )))
437 437  
438 -In the example above, OBS_CONF is an Observation Attribute.
468 +In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
439 439  
440 -== 13. Time span mapping rules using validity periods ==
470 +== 13.9 Time span mapping rules using validity periods ==
441 441  
442 442  Creating discrete mapping rules for each TIME_PERIOD is impractical where rules need to cover a specific span of time regardless of frequency, and for high-frequency data.
443 443  
... ... @@ -445,25 +445,22 @@
445 445  
446 446  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
447 447  
448 -|Rule|Source|Target
449 -|1|(((
478 +(% style="width:516.294px" %)
479 +|(% style="width:74px" %)Rule|(% style="width:215px" %)Source|(% style="width:223px" %)Target
480 +|(% style="width:74px" %)1|(% style="width:215px" %)(((
450 450  If
451 -
452 452  INDICATOR=XULADS.
453 -
454 -
455 -Validity Period start period=2007 end period=2009
456 -)))|Set OBS_CONF=F
457 -|2|(((
483 +Validity Period
484 +start period=2007
485 +end period=2009
486 +)))|(% style="width:223px" %)Set OBS_CONF=F
487 +|(% style="width:74px" %)2|(% style="width:215px" %)(((
458 458  If
459 -
460 460  INDICATOR=XULADS.
461 -
462 -
463 -Validity Period start period=2010
464 -)))|(((
490 +Validity Period
491 +start period=2010
492 +)))|(% style="width:223px" %)(((
465 465  Set
466 -
467 467  OBS_CONF=F
468 468  )))
469 469  
... ... @@ -471,132 +471,132 @@
471 471  
472 472  In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of C.
473 473  
474 -== 13. Mapping examples ==
501 +In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of C.
475 475  
476 -=== 13. Many to one mapping (N-1) ===
503 +== 13.10 Mapping examples ==
477 477  
478 -|Source|Map To
479 -|(((
480 -**FREQ**="A"
505 +=== 13.10.1 Many to one mapping (N3513 -1) ===
481 481  
507 +(% style="width:542.294px" %)
508 +|(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To**
509 +|(% style="width:274px" %)(((
510 +(% style="color:#8e44ad" %)**FREQ**="A"
482 482  ADJUSTMENT="N"
483 -
484 484  **REF_AREA**="PL"
485 -
486 486  **COUNTERPART_AREA**="W0"
487 -
488 488  REF_SECTOR="S1"
489 -
490 490  COUNTERPART_SECTOR="S1"
491 -
492 492  ACCOUNTING_ENTRY="B"
493 -
494 494  STO="B5G"
495 -)))|(((
496 -FREQ="A"
497 -
518 +)))|(% style="width:265px" %)(((
519 +(% style="color:#8e44ad" %)FREQ="A"
498 498  REF_AREA="PL"
499 -
500 500  COUNTERPART_AREA="W0"
501 -INDICATOR="IND_ABC"
522 +INDICATOR="IND_ABC"(%%)
502 502  
503 503  )))
504 504  
505 -The bold Dimensions map from source to target verbatim. The mapping simply specifies:
526 +The bold [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)map(%%) from source to target verbatim. The mapping simply specifies:
506 506  
507 -FREQ => FREQ
528 +> FREQ => FREQ
529 +> REF_AREA=> REF_AREA
530 +> COUNTERPART_AREA=> COUNTERPART _AREA
508 508  
509 -REF_AREA=> REF_AREA
532 +No [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified.
510 510  
511 -COUNTERPART_AREA=> COUNTERPART _AREA
534 +The remaining [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] all (% style="color:#e74c3c" %)map(%%) to the Indicator [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. This is an example of many [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] mapping to one [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. In this case a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required, and the mapping first describes the input 'partial key' and how this (% style="color:#e74c3c" %)maps(%%) to the target indicator:
512 512  
513 -No Representation Mapping is required. The source value simply copies across unmodified.
536 +> N:S1:S1:B:B5G => IND_ABC
514 514  
515 -The remaining Dimensions all map to the Indicator Dimension. This is an example of many Dimensions mapping to one Dimension. In this case a Representation Mapping is required, and the mapping first describes the input 'partial key' and how this maps to the target indicator:
538 +Where the key sequence is based on the order specified in the (% style="color:#e74c3c" %)mapping(%%) (i.e [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]], REF_SECTOR, etc will result in the first value N being taken from [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]] as this was the first item in the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] list.
516 516  
517 -N:S1:S1:B:B5G => IND_ABC
540 +**Note**: The key order is NOT based on the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] order of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], as the (% style="color:#e74c3c" %)mapping(%%) needs to be resilient to the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] changing.
518 518  
519 -Where the key sequence is based on the order specified in the mapping (i.e ADJUSTMENT, REF_SECTOR, etc will result in the first value N being taken from ADJUSTMENT as this was the first item in the source Dimension list.
542 +=== 13.10.2 Mapping other data types to Code Id ===
520 520  
521 -**Note**: The key order is NOT based on the Dimension order of the DSD, as the mapping needs to be resilient to the DSD changing.
544 +In the case where the incoming data type is not a string and not a [[code>>doc:sdmx:Glossary.Code.WebHome]] identifier i.e. the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
522 522  
523 -1.
524 -11.
525 -111. Mapping other data types to Code Id
546 +The following [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)mapping(%%) can be used to explicitly (% style="color:#e74c3c" %)map(%%) each [[age>>doc:sdmx:Glossary.Age.WebHome]] to an output [[code>>doc:sdmx:Glossary.Code.WebHome]].
526 526  
527 -In the case where the incoming data type is not a string and not a code identifier i.e. the source Dimension is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
548 +(% style="width:402.294px" %)
549 +|(% style="width:197px" %)**Source Input Free Text**|(% style="width:204px" %)**Desired Output Code Id**
550 +|(% style="width:197px" %)0|(% style="width:204px" %)A
551 +|(% style="width:197px" %)1|(% style="width:204px" %)A
552 +|(% style="width:197px" %)2|(% style="width:204px" %)A
553 +|(% style="width:197px" %)3|(% style="width:204px" %)B
554 +|(% style="width:197px" %)4|(% style="width:204px" %)B
528 528  
529 -The following representation mapping can be used to explicitly map each age to an output code.
530 -
531 -|Source Input Free Text|Desired Output Code Id
532 -|0|A
533 -|1|A
534 -|2|A
535 -|3|B
536 -|4|B
537 -
538 538  If this mapping takes advantage of regular expressions it can be expressed in two rules:
539 539  
558 +(% style="width:336.294px" %)
559 +|(% style="width:182px" %)**Regular Expression**|(% style="width:151px" %)**Desired Output**
560 +|(% style="width:182px" %)[0-2]|(% style="width:151px" %)A
561 +|(% style="width:182px" %)[3-4]|(% style="width:151px" %)B
540 540  
541 -Regular Expression Desired Output
563 +=== 13.10.3 Observation Attributes for Time Period ===
542 542  
543 -|[0-2]|A
544 -|[3-4]|B
565 +This use case is where a specific observation for a specific [[time period>>doc:sdmx:Glossary.Time period.WebHome]] has an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] value.
545 545  
546 -=== 13. Observation Attributes for Time Period ===
567 +(% style="width:621.294px" %)
568 +|(% style="width:201px" %)Input INDICATOR|(% style="width:192px" %)Input TIME_PERIOD|(% style="width:225px" %)Output OBS_CONF
569 +|(% style="width:201px" %)XULADS|(% style="width:192px" %)2008|(% style="width:225px" %)C
570 +|(% style="width:201px" %)XULADS|(% style="width:192px" %)2009|(% style="width:225px" %)C
571 +|(% style="width:201px" %)XULADS|(% style="width:192px" %)2010|(% style="width:225px" %)C
547 547  
548 -This use case is where a specific observation for a specific time period has an attribute value.
573 +Or using a validity period on the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping:
549 549  
550 -|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
551 -|XULADS|2008|C
552 -|XULADS|2009|C
553 -|XULADS|2010|C
575 +(% style="width:629.294px" %)
576 +|(% style="width:202px" %)Input INDICATOR|(% style="width:197px" %)Valid From/ Valid To|(% style="width:227px" %) Output OBS_CONF
577 +|(% style="width:202px" %)XULADS|(% style="width:197px" %) 2008/2010|(% style="width:227px" %)С
554 554  
555 -Or using a validity period on the Representation Mapping:
579 +=== 13.10.4 Time mapping ===
556 556  
557 -Input INDICATOR Valid From/ Valid To Output OBS_CONF
581 +This use case is to create a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] from an input that does not respect [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Time Formats.
558 558  
559 -XULADS 2008/2010 C
583 +The [[Component>>doc:sdmx:Glossary.Component.WebHome]] Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
560 560  
561 -=== 13. Time mapping ===
585 +(% style="width:652.294px" %)
586 +|(% style="width:139px" %)Source Value|(% style="width:165px" %)Source Mapping|(% style="width:182px" %)Target Frequency|(% style="width:163px" %)Output
587 +|(% style="width:139px" %)18/07/1981|(% style="width:165px" %)dd/MM/yyyy|(% style="width:182px" %)A|(% style="width:163px" %)1981
562 562  
563 -This use case is to create a time period from an input that does not respect SDMX Time Formats.
589 +When the target frequency is based on another target [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] value, in this example the value of the FREQ [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in the target [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
564 564  
565 -The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
591 +(% style="width:658.294px" %)
592 +|(% style="width:143px" %)Source Value|(% style="width:163px" %) Source Mapping|(% style="width:176px" %)Target Dimension|(% style="width:173px" %)Frequency Output
593 +|(% style="width:143px" %)18/07/1981|(% style="width:163px" %)dd/MM/yyyy|(% style="width:176px" %)FREQ|(% style="width:173px" %)1981-07-18 (when FREQ=D)
566 566  
567 -|Source Value|Source Mapping|Target Frequency|Output
568 -|18/07/1981|dd/MM/yyyy|A|1981
595 + When the source is a numerical format.
569 569  
570 -When the target frequency is based on another target Dimension value, in this example the value of the FREQ Dimension in the target DSD.
597 +(% style="width:658.294px" %)
598 +|(% style="width:143px" %)Source Value|(% style="width:163px" %) Start Period|(% style="width:176px" %)Interval|(% style="width:176px" %)Target FREQ|(% style="width:173px" %) Output
599 +|(% style="width:143px" %)1589808220|(% style="width:163px" %)1970|(% style="width:176px" %) millisecond|(% style="width:176px" %)M|(% style="width:173px" %)2020-05
571 571  
572 -Source Value Source Mapping Target Frequency Output
573 -
574 -Dimension
575 -
576 -|18/07/1981 dd/MM/yyyy FREQ| |1981-07-18 (when FREQ=D)
577 -| When the source is a numerical format| |
578 -|Source Value Start Period Interval|(((
579 -Target
580 -
581 -FREQ
582 -)))|Output
583 -|1589808220 1970 millisecond|M|2020-05
584 -
585 585  When the source frequency is lower than the target frequency additional information 3568 can be provided for resolve to start of period, end of period, or mid period, as shown 3569 in the following example:
586 586  
587 - Source Value Source Mapping Target Frequency Output
603 +(% style="width:666.294px" %)
604 +|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
605 +|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1981-12-31
588 588  
589 -Dimension
607 +When the start of year is April 1^^st^^ the Structure (% style="color:#e74c3c" %)Map(%%) has YearStart=04-01:
590 590  
591 - 1981 yyyy D – End of Period 1981-12-31
609 +(% style="width:666.294px" %)
610 +|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
611 +|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1982-03-31
592 592  
593 -
594 -When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
595 -
596 - Source Value Source Mapping Target Frequency Output
597 -
598 -Dimension
599 -
600 600  ----
601 601  
602 -{{putFootnotes/}}
615 +(% contenteditable="false" tabindex="-1" %)
616 +(((
617 +(% class="macro" data-macro="startmacro:putFootnotes|-|" data-widget="xwiki-macro" %)
618 +(((
619 +(% class="macro-placeholder hidden" %)
620 +(((
621 +macro:putFootnotes
622 +)))
623 +
624 +(% class="footnotes" %)
625 +1. [[^>>doc:null||anchor="x_footnote_ref_1" id="x_footnote_1" class="footnoteBackRef"]] Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.
626 +1. [[^>>doc:null||anchor="x_footnote_ref_2" id="x_footnote_2" class="footnoteBackRef"]] A list of commonly used locales can be found in the Java supported locales: https~://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html//
627 +1. [[^>>doc:null||anchor="x_footnote_ref_3" id="x_footnote_3" class="footnoteBackRef"]] yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years
628 +)))
629 +)))
1750074822764-573.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +25.1 KB
Content
1750074865924-797.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +46.8 KB
Content
1750074994887-415.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +12.4 KB
Content