Difference between revisions of "Mapping behaviour using item validity"
(→Overview) |
(→Overview) |
||
| Line 4: | Line 4: | ||
Fusion Registry's [[Structure mapping|Structure Mapping]] function allows datasets to be transformed from one structure and classification scheme to another. Mapping of classifications is performed using [[Codelist map|Codelist Maps]] which define how Codes in one Codelist map to those in another. | Fusion Registry's [[Structure mapping|Structure Mapping]] function allows datasets to be transformed from one structure and classification scheme to another. Mapping of classifications is performed using [[Codelist map|Codelist Maps]] which define how Codes in one Codelist map to those in another. | ||
<br><br> | <br><br> | ||
| − | When defining ''Codelist Maps'', multiple mapping rules can be specified for each Code with a ''Validity Period'' for each. The Validity Period sets the period in real time when the rule will be active. Mapping rules with Validity Periods are executed if the time at which the mapping is performed falls within the time range specified. Conversely, rules without Validity Periods are always active and are executed irrespective of when the mapping is actually performed. | + | When defining ''Codelist Maps'', multiple mapping rules can be specified for each Code with a ''Validity Period'' for each. The Validity Period sets the period in '''real time''' when the rule will be active. Mapping rules with Validity Periods are executed if the time at which the mapping is performed falls within the time range specified. Conversely, rules without Validity Periods are always active and are executed irrespective of when the mapping is actually performed. |
| + | |||
| + | ==Use Cases== | ||
| + | The main use case for setting Validity Periods on Codelist Maps is to forward schedule changes in the behaviour of the map with respect to how classifications are transformed. By way of an example, consider a map that translates a country code dimension into a trading bloc dimension. If it is known that a particular will move to a different trading bloc on a particular date, two separate rules can be created. | ||
==Example== | ==Example== | ||
Revision as of 08:39, 21 January 2020
Overview
Fusion Registry's Structure Mapping function allows datasets to be transformed from one structure and classification scheme to another. Mapping of classifications is performed using Codelist Maps which define how Codes in one Codelist map to those in another.
When defining Codelist Maps, multiple mapping rules can be specified for each Code with a Validity Period for each. The Validity Period sets the period in real time when the rule will be active. Mapping rules with Validity Periods are executed if the time at which the mapping is performed falls within the time range specified. Conversely, rules without Validity Periods are always active and are executed irrespective of when the mapping is actually performed.
Use Cases
The main use case for setting Validity Periods on Codelist Maps is to forward schedule changes in the behaviour of the map with respect to how classifications are transformed. By way of an example, consider a map that translates a country code dimension into a trading bloc dimension. If it is known that a particular will move to a different trading bloc on a particular date, two separate rules can be created.
