Core and Local Representations in a Data Structure

Within a Data Structure a component (such as a Dimension) is attached to an underlying concept. This concept can be coded and so the component "inherits" the representation from the concept constraining the values that may be reported for this component. This is the "core representation". The core representation can be over-ridden by a "local representation" of either a Codelist or a "Text Format". A "Text Format" has a type (e.g. String, Integer, DateTime, etc.) and may include further restrictions such as a minimum or maximum length. The rules of inheritance conform to the SDMX 3 standard and constrain the component as follows:

• If there is a Core Representation, but no Local representation or Text Format, the Core Representation constrains the component.
• If there is a Core Representation, and a Local representation but no Text Format, the Local Representation constrains the component.
• If there is a Core Representation, no Local representation but there is a Text Format, the Text Format constrains the component.
• If there is a Core Representation, Local representation and Text Format, the Local Representation constrains the component and the Text Format is for informational purposes only

The User Interface to define this relationship has changed in version 11.21.0 of the Fusion Metadata Registry. This information is displayed on Step 3 of the DSD wizard and now looks like the following:

The example above shows a DSD with 4 dimensions, 1 attribute and 1 measure. The Dimension "FREQ" is constrained by the Codelist WB:CL_FREQ_WDI(1.0) and has no local representation. The dimensions "SERIES" inherits from the codelist WB:CL_SERIES_WDI(1.0), but has a local Text Format of String. This overrides the codelist (shown by it being struck-through) and any content is permitted. Similarly the dimension "REF_AREA" is also over-ridden by a String, but this is further restricted (which is shown by the blue 'Details' label).