Changes for page 13 Structure Mapping

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

From version 10.17
edited by Helena
on 2025/05/16 09:32
Change comment: There is no comment for this version
To version 10.14
edited by Helena
on 2025/05/16 09:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -426,22 +426,27 @@
426 426  
427 427  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
428 428  
429 -(% style="width:808.294px" %)
430 -|(% style="width:93px" %)**Rule**|(% style="width:385px" %)**Source**|(% style="width:328px" %)**Target**
431 -|(% style="width:93px" %)1|(% style="width:385px" %)(((
429 +|Rule|Source|Target
430 +|1|(((
432 432  If
432 +
433 433  INDICATOR=XULADS.
434 +
434 434  Validity Period start period=2007 end period=2009
435 -)))|(% style="width:328px" %)(((
436 +)))|(((
436 436  Set
438 +
437 437  OBS_CONF=F
438 438  )))
439 -|(% style="width:93px" %)2|(% style="width:385px" %)(((
441 +|2|(((
440 440  If
443 +
441 441  INDICATOR=XULADS.
445 +
442 442  Validity Period start period=2010
443 -)))|(% style="width:328px" %)(((
447 +)))|(((
444 444  Set
449 +
445 445  OBS_CONF=F** **
446 446  )))
447 447  
... ... @@ -453,20 +453,28 @@
453 453  
454 454  === 13.10.1 Many to one mapping (N-1) ===
455 455  
456 -(% style="width:762.294px" %)
457 -|(% style="width:474px" %)**Source**|(% style="width:284px" %)**Map To**
458 -|(% style="width:474px" %)(((
461 +|Source|Map To
462 +|(((
459 459  **FREQ**="A"
464 +
460 460  ADJUSTMENT="N"
466 +
461 461  **REF_AREA**="PL"
468 +
462 462  **COUNTERPART_AREA**="W0"
470 +
463 463  REF_SECTOR="S1"
472 +
464 464  COUNTERPART_SECTOR="S1" ACCOUNTING_ENTRY="B"
474 +
465 465  STO="B5G"
466 -)))|(% style="width:284px" %)(((
476 +)))|(((
467 467  FREQ="A"
478 +
468 468  REF_AREA="PL"
480 +
469 469  COUNTERPART_AREA="W0"
482 +
470 470  INDICATOR="IND_ABC"
471 471  )))
472 472  
... ... @@ -494,24 +494,28 @@
494 494  
495 495  The following representation mapping can be used to explicitly map each age to an output code.
496 496  
510 +:
511 +
497 497  (((
498 -(% style="width:669.294px" %)
499 -|(% style="width:218px" %)**Source Input Free Text**|(% style="width:448px" %)**Desired Output Code Id**
500 -|(% style="width:218px" %)0|(% style="width:448px" %)A
501 -|(% style="width:218px" %)1|(% style="width:448px" %)A
502 -|(% style="width:218px" %)2|(% style="width:448px" %)A
503 -|(% style="width:218px" %)3|(% style="width:448px" %)B
504 -|(% style="width:218px" %)4|(% style="width:448px" %)B
513 +|Source Input Free Text|Desired Output Code Id
514 +|0|A
515 +|1|A
516 +|2|A
517 +|3|B
518 +|4|B
505 505  )))
506 506  
507 507  If this mapping takes advantage of regular expressions it can be expressed in two 3464 rules:
508 508  
523 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8c1afe2b.gif||alt="Shape10" height="1" width="302"]]
524 +
509 509  __Regular Expression __Desired Output
510 510  
527 +:
528 +
511 511  (((
512 -(% style="width:675.294px" %)
513 -|(% style="width:219px" %)[0-2]|(% style="width:453px" %)A
514 -|(% style="width:219px" %)[3-4]|(% style="width:453px" %)B
530 +|[0-2]|A
531 +|[3-4]|B
515 515  )))
516 516  
517 517  === 13.10.3 Observation Attributes for Time Period ===
... ... @@ -518,18 +518,21 @@
518 518  
519 519  This use case is where a specific observation for a specific time period has an attribute 3468 value.
520 520  
538 +:
539 +
521 521  (((
522 -(% style="width:689.294px" %)
523 -|(% style="width:220px" %)**Input INDICATOR**|(% style="width:223px" %)**Input TIME_PERIOD**|(% style="width:243px" %)**Output OBS_CONF**
524 -|(% style="width:220px" %)XULADS|(% style="width:223px" %)2008|(% style="width:243px" %)C
525 -|(% style="width:220px" %)XULADS|(% style="width:223px" %)2009|(% style="width:243px" %)C
526 -|(% style="width:220px" %)XULADS|(% style="width:223px" %)2010|(% style="width:243px" %)C
541 +|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
542 +|XULADS|2008|C
543 +|XULADS|2009|C
544 +|XULADS|2010|C
527 527  )))
528 528  
529 529  __Or using a validity period on the Representation Mapping__:
530 530  
531 -Input INDICATOR Valid From/ Valid To Output OBS_CONF XULADS 2008/2010 C
549 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6dbf7f.gif||alt="Shape11" height="36" width="555"]] Input INDICATOR Valid From/ Valid To Output OBS_CONF
532 532  
551 +XULADS 2008/2010 C
552 +
533 533  === 13.10.4 Time mapping ===
534 534  
535 535  This use case is to create a time period from an input that does not respect SDMXTime Formats.
... ... @@ -536,15 +536,20 @@
536 536  
537 537  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
538 538  
559 +:
560 +
539 539  (((
540 -(% style="width:763.294px" %)
541 -|(% style="width:163px" %)**Source Value**|(% style="width:219px" %)**Source Mapping**|(% style="width:198px" %)**Target Frequency**|(% style="width:180px" %)**Output**
542 -|(% style="width:163px" %)18/07/1981|(% style="width:219px" %)dd/MM/yyyy|(% style="width:198px" %)A|(% style="width:180px" %)1981
562 +|Source Value|Source Mapping|Target Frequency|Output
563 +|18/07/1981|dd/MM/yyyy|A|1981
543 543  )))
544 544  
545 545  When the target frequency is based on another target Dimension value, in this example __the value of the FREQ Dimension in the tar__get DSD.
546 546  
568 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
547 547  
570 +:
571 +::
572 +
548 548  (((
549 549  |Source Value|Source Mapping|Target Frequency Output Dimension
550 550