Fusion Registry 9.4

Fusion Registry

Release 9.4

Fusion Registry®9

Fusion Registry 9 is a statistical data management solution for central banks, international organisations, national statistics offices and other public bodies who need to report, collect, integrate, process and disseminate aggregated official statistics.

It uses the SDMX (Statistical Data and Metadata eXchange) ISO standard to model the complexities of statistical datasets and provide a common language for exchanging the data between organisations and systems.

The free-to-use Community Edition is suitable for data modelling, publishing structures and some data processing tasks, principally: structural validation, structural transformation and conversion to alternative SDMX versions and formats.

The Enterprise Edition adds data collection, integration and dissemination, plus reference metadata support and further data processing functions including time-series calculations.

New Charts and Visualisations

Enterprise Edition Only

The built-in Fusion Data Browser now allows data consumers and analysts to visualise data using an extended range of charts and tables including:

  • Interactive pivot tables
  • Time series line charts
  • Bar charts
  • Pie charts
  • Pyramid charts
  • Tree maps
  • Radar charts
  • Heat maps

Sharing and Embedding Live Charts and Tables

Enterprise Edition Only

Charts and tables created using the Fusion Data Browser can now be shared as URLs or embedded into websites and blog posts.

The visualisations are live. Users clicking on a link or viewing a web page with an embedded chart will always see the latest data. Here's an example of a live chart embedded as an iframe:


New Ways to Transform Data into Different Structures

Community and Enterprise Editions

Fusion Registry’s ‘Structure Mapping’ function allows data sets to be converted from one structure to another either when the observation data is loaded, or dynamically when executing queries. Use cases include converting a dataset into an alternative structure suitable for public dissemination, and converting series with a single series code dimension into a full multi-dimensional structure.

Fusion Registry 9.4 add some new ways to define these mapping rules:

Series Mapping
Series Mapping allows administrators to define rules which explicitly map one ‘series key’ to another. For instance, rules converting a simple two-dimensional data set consisting of a series code and country into a multi-dimensional structure may look like this:

Source Key Target Key

Remember that 'series keys' in SDMX are written as the values for each dimension separated by colons. So BOP_LOC_AX1:DE may be the key for a series with two dimensions. Dimension #1 'Series Code'=BOP_LOC_AX1, and Dimension #2 'Country'=DE.

Partial Code Mapping

Partial code mapping allows a dimension in the source data set to be mapped based on just part of the code. The main use case is where codes in source datasets carry multiple pieces of information – for instance: a code ‘FR_EUR’ may mean France (the FR component) and Euro currency (the EUR component).

In Fusion Registry 9.4, 'Substring' and 'Regex' expressions can be used to identify the part of the source code value to use in the mapping rule.

Source Target

In the above example, the source dataflow has an enumerated dimension REGION which includes the code 'FR_EUR'. In the target dataflow, we want two have two separate dimensions for Reference Area (REF_AREA), and Currency (CURRENCY). The Left() and Right() Substring operations are used to select the relevant parts of the source code to use in the conditional part of the mapping rules.

Synchronise Structural Metadata Between Environments

Community and Enterprise Editions

From Release 9.4, the Fusion Registry web user interface includes a visual tool for synchronising structures with another Fusion Registry environment. This allows changes such as creating a new data structure definition to be made on a 'test' environment, before being pushed to the 'live' production environment.

While copying structures between environments has always been possible using the file export-import method, the new 'structure synchronisation' feature simplifies and automates the process where metadata administrators want to move metadata between environments interactively.

Key benefits:

  • Examine all of the differences in the structural metadata content between the two Registries in a single view.
  • Easily identify content on the local environment that does not exist on the target (blue), content that exists on the target but not on the source (green) and collisions (red) where an artefact with the same ID exists on both source and target.
  • Single button to push or pull structures from the target Registry.

Item Validity

Community and Enterprise Editions

‘Item Validity’ allows structural metadata content managers to define a time period when an item such as a code is considered valid. A common use case involves country codes that are only valid between particular dates when the country was in ‘existence’. The feature also supports the case where a code changes meaning over time.

The Gilbert and Ellice Islands had the ISO country code ‘GE’ until 1977 when split to become the independent countries of Kiribati and Tuvalu. When Georgia gained independence from the former Soviet Union in 1991, the ‘GE’ code was reused. Item Validity now allows this logic to be described as part of the structural metadata.

From Release 9.4, Fusion Registry allows the GE code to be configured with the following validity periods:
Period up to 1977: GE = Gilbert and Ellice Islands
Period between 1977 and 1991: GE is invalid
Period from 1991: GE = Georgia

In practical terms, Item Validity allows data with dimension codes that vary in meaning over time to be robustly validated and correctly disseminated.

Observation data for country ‘GE’ and the time period ‘1970’ must relate to the Gilbert and Ellice islands. Whereas observations for the same ‘GE’ code but for the period 2005 must relate to Georgia. Observations for country ‘GE’ during the period 1978 and 1990 will be rejected as invalid because the validity rule states that no country with that code existed between those dates.
Visualisations showing observation data for country ‘GE’ and time period ‘1970’ will use the code named ‘Gilbert and Ellice’. When showing similar data for ‘2005’, the Item Validity rules will mean that the code named ‘Georgia’ will be displayed.
In addition to codes, Item Validity can be applied to Concepts, Hierarchical Codes, and Codelist Maps which are used by the Fusion Registry Structure Mapping function.