Fusion Registry®11
SDMX Statistical Data WarehouseFusion Registry 11 is for central banks, international organisations, national statistics offices, development banks and regional statistics authorities who need an enterprise SDMX statistical data warehouse for storage of aggregated time series, data cataloguing and public dissemination.
Its data validation, mapping and format conversion services support statistics production and data reporting use cases while Excel data reporting forms generated from the metadata simplify the data collection process.
Fusion Registry 11 implements the SDMX 3.0 information model.
SDMX is designed for statistics.
SDMX provides a structured and standardised way to describe statistical data in any domain, and a common language for exchanging both the data and its structural metadata between organisations and systems (information about how the data is or should be structured).
It allows statisticians to robustly describe the structure and rules for complex datasets, provides data providers with a clear description about what the data should look like, and data users with an unambiguous understanding of how to interpret it.
SDMX is a proven, open, non-proprietary standard sponsored by seven international organisations including the World Bank, the International Monetary Fund and the United Nations Statistics Division. It's also an International Standard ISO 17369:2013.
Aggregated time series
Fusion Registry currently supports aggregated time series.
Microdata - planned for 2023
The ability to model microdata was introduced in SDMX 3.0 and Fusion Registry 11.0.
Microdata storage is on the Fusion Registry roadmap with delivery planned for 2023.
Yes
Fusion Registry has an integrated structural metadata registry to the SDMX 3.0 specification. The structural metadata functionality is identical to Fusion Metadata Registry.
Reference metadata storage - planned for 2022
In SDMX 3.0, metadatasets, also called 'metadata reports' are managed as structural metadata artefacts. This means they are stored alongside the other structures such as DSDs, Concepts and Codelists which simplifies their creation, maintenance, storage and exchange. The SDMX 3.0 reference metadata REST API has also been improved and now allows users to query for a specific report.
Reference Metadata (also called Referential Metadata) is human-readable information that can be attached to datasets, series, observations, concepts and other data and structural metadata elements. If you want to provide some explanatory notes to help users interpret a dataset, Reference Metadata is the thing to use. And it's not just restricted to text. Reference Metadata can be plain text, HTML or links to other documents and resources such as videos and images.
No
Fusion Registry is closed-source with a proprietary commerical right to use license.
However, if you're a central bank or international organisation user you can get access to the source code.
Yes
Yes, Metadata Technology in conjuction with our integration partners can design and build complete solutions to meet your official statistics requirements based on Fusion Registry.
No
Fusion Registry is a only available as a commercial product - either installed on-premises, or delivered as a fully-managed cloud service (SaaS).
Yes
Fusion Registry Cloud gives you a SDMX statistical data warehouse service in the cloud, installed, configured and ready to go. There's a live demonstration here.
Pricing information can be found here.
Yes
Fusion Registry has an integrated structural metadata registry to the SDMX 3.0 specification. The structural metadata functionality is identical to Fusion Metadata Registry.
Reference metadata storage is on the 2022 roadmap.
In SDMX 3.0, metadatasets, also called 'metadata reports' are managed as structural metadata artefacts. This means they are stored alongside the other structures such as DSDs, Concepts and Codelists which simplifies their creation, maintenance, storage and exchange. The SDMX 3.0 reference metadata REST API has also been improved and now allows users to query for a specific report.
Reference Metadata (also called Referential Metadata) is human-readable information that can be attached to datasets, series, observations, concepts and other data and structural metadata elements. If you want to provide some explanatory notes to help users interpret a dataset, Reference Metadata is the thing to use. And it's not just restricted to text. Reference Metadata can be plain text, HTML or links to other documents and resources such as videos and images.
- Transformation - SDMX Structure Maps can be used to transform data to different structures and classification schemes.
- Calculation - Calculate new series using Metadata Technology's Time Series Expression Language.
- Format Conversion - Convert data between formats including SDMX formats, non-SDMX formats like Excel.
- Aggregation - Aggregate series to a higher level using definable functions.
- Frequency Conversion - Convert time series to different frequencies using definable re-sampling and interpolation functions.
- Structural Validation - Check data for compliance with the information model defined by the SDMX structural metadata. This can also check for other potential problems such as duplication observations.
- Semantic Validation - Check data for compliance with definable business rules such as observations for individual classifications match the value reported for TOTAL.
Registry Content: Yes
Registry content (names, labels, descriptions etc) can be loaded, displayed and retrieved in multiple languages, including those written right-to-left such as Arabic and Hebrew. Users can choose their preferred language - content will be displayed in that language if available, or the default language otherwise. The default is often English, but it doesn't need to be.
Fusion Registry Web User Interface: No
Text on Fusion Registry's web user interface - including the menu bar, buttons and informational messages displayed for various reasons - are always in English.
Fusion Data Browser Web User Interface: Yes
Legends, buttons, menu items and other text can all appear in a language of a your choice using configurable language translation JSON files.
Fusion Registry core is a Java web application so it will run on most compute platforms with a Java run-time environment and a suitable Java web application server such as Apache Tomcat. It has a web user interface so users require only a standard web browser.
Fusion Registry provides a comprehensive REST web services API for integration with other systems. The API is compliant with the standard SDMX RESTful web services specification, and also provides a range of other functions:
- Query for data - retrieve data for a specified selection of series from a dataset
- Submit data content - load data into local Fusion Registry managed data stores, including the in-memory database
- Delete data content - delete selected datasets, series and observations
- Rollback data change - rollback data submissions
- Data registration - registration of external data sources
- Data reporting forms - generate Excel forms for reporting data
- Freetext search - search the metadata and data content
- Reference metadata - query for and submit reference metadata
- Audit - query audit logs
- Fusion Edge Server - take snapshots of the data warehouse for publication using Fusion Edge Servers
- Content Security - query for and manage Content Security rules
Operating System - Windows or Linux. Other platforms including Apple Mac, HP-UX and IBM AIX should also work provided they have a suitable Java Runtime Environment (JRE) or Java Development Kit (JDK), and Java Web Application Server.
Java Runtime Environment - Java 8, Java 10 and Java 11 are supported.
Java Web Application Server - Apache Tomcat 8.0, 8.5 or 9.0 are recommended. Jetty, RedHat JBoss and Oracle WebLogic are also tested and proven. Other application servers like IBM WebSphere Application Server should also work.
Processor - A minimum of 4 cores.
Memory - 4GB is sufficient for testing and basic use cases. However, plan for between 16GB and 128GB for heavier workloads or where extensive use of the Fusion Data Store in-memory database is planned.
Database - Fusion Registry requires a SQL database service for storage of structural metadata, Fusion Data Store in-memory database persistence, audit logs and configuration settings. The following are supported: MySQL 5.6 and 5.7, Oracle 11g,12c and 19c, SQL Server.
Web Server - A web server is recommended working in reverse-proxy mode for all production systems. Apache Web Server 2.4 is recommended although cloud deployment platforms such as Amazon Web Services and Microsoft Azure generally provide a reverse proxy service meaning that Apache is not required in those circumstances.
SDMX 3.0 support, Publication Tables, improvements to the web data browser, improved data and metadata access controls, more granular control over admin rights, scheduled data and structure import jobs, refreshable Excel data workbooks read more...
Fusion Registry 11 uses SDMX 3.0 as its internal information model which supports modelling of microdata. There's backward compatibility for most SDMX 2.1 structures except for Structure Sets and Hierarchical Codelists which are converted to their SDMX 3.0 equivalents on load. Backward compatibility is similarly provided for earlier transmission formats.
Version 11.0 supports a lot of the SDMX 3.0 specification with the rest planned for future releases.
read more...
| SDMX 3.0 feature support | Version 11.0 | Future 11 releases |
|---|---|---|
| SDMX 3.0 information model | All structures except for Concept Scheme Map, Category Scheme Map, Metadata Constraint, Metadataset | |
| Aggregated data storage | ||
| Microdata storage | ||
| Codelist inheritance | ||
| Geographic and Geogrid codelists | ||
| GeospatialInformation representation type | ||
| SDMX 3.0 structure mapping | ||
| SDMX 2.1 and earlier structure transmission formats backward compatibility | ||
| SDMX 3.0 XML structure transmission format | ||
| SDMX 3.0 JSON structures transmission format | Selected structures supported | |
| SDMX 2.1 and earlier data transmission formats backward compatibility | ||
| SDMX 3.0 XML data transmission format | ||
| SDMX 3.0 JSON data transmission format | ||
| SDMX 3.0 CSV data transmission format | Supported with the exception of complex reference metadata embedded in data messages | |
| Semantic versioning | Three-digit version numbers and structure queries using semantic expressions such as 1.3+ supported |
|
| Discriminated union of codelists | ||
| SDMX 3.0 constraints model including % wildcard operator | ||
| SDMX 3.0 REST structure API | ||
| SDMX 3.0 REST data API | Supported with the exception of some of the component query predicate operators such as 'sw', 'ew' and 'co'. 'ne' and 'eq' work with all components except TIME_PERIOD. For TIME_PERIOD, 'gt','ge',lt' and 'le' are currently implemented. |
|
| SDMX 3.0 REST data availability API | ||
| SDMX 3.0 REST schema API | ||
| SDMX 3.0 REST reference metadata API |
read more...
read more...
- Improved data table with interactive column selection, filtering and pivot mode. Export the table as shown to Excel or CSV.
- Calculations: percentage change, moving average, interpolation of missing values, number precision and frequency conversion.
- Get simple API URLs for all queries and series selections, including series baskets.
- Simpler chart and table sharing.
- Category trees for searching the data catalogue by theme and category.
- Improved default selection of components for dataflows when displaying the series list.
- Interactively manage the series list configuration for each dataflow from the Browser.
- Interactively create and manage pre-defined queries from the Browser.
- Interactively manage category trees from the Browser and easily categorise Dataflows and pre-defined queries.
read more...
- Structure write rules - control who can maintain which structures
- Dataset write rules - control who can publish, modify and delete datasets and series
- Structure read rules - control what structural metadata users can see (note that restricting access to a structure or item such as a code also restricts access to any data that references it)
- Dataset read rules - control access to data at the dataset (Dataflow) level
- Data point read rules - control granular access to data at the series or data point (observation) level
- Data attribute read rules - control which attributes are visible to users when querying for data
read more...
- Data manager - grants full access to data functions for loading, maintaining and deleting data.
- Audit manager - grants access to audit information.
- Error subscriber - grants the user rights to subscribe to system error reports.
- Server admin - grants rights to set and modify the Fusion Registry server configuration.
- User admin - grants rights to administer user privileges and groups.
- Structure admin - grants full access to administer all structural metadata.
- Kafka admin - grants rights to manage Kafka services.
- Portal admin - grants right to manage and run Fusion Portal jobs for scheduled loads of SDMX structures and data.
In addition to the usual SDMX, CSV and static Excel data export options, users can now choose to retrieve data as refreshable Excel workbooks. This feature is available from both the data REST API using the format=excel-refresh URL parameter or Accept header, and also as an export option from the Fusion Data Browser.
try it...
- Download and install the Fusion FXLData add in for Excel
- Retrieve a refreshable Excel workbook for ECB Exchange Rates from the live Fusion Registry 11 demo service:
https://demo11.metadatatechnology.com/FusionRegistry/sdmx/v2/data/dataflow/ECB/EXR/1.0/?c[FREQ]=A,M&c[CURRENCY]=BRL,CAD,CHF,MXN&format=excel-refresh - In Windows and Microsoft 365 Excel, you may need to choose 'Enable Editing'. Save the workbook, close and re-open it to see the data.
Use Cases
Use Fusion Registry 11 for storage of all aggregated time series data. There are several storage options available including the Fusion in-memory database for maximum performance, and SQL tables.
Granular access control rules provide tight control over precisely what data and metadata users can see.
Fusion Registry 11 can physically or virtually integate aggregated statistical data from multiple sources into a single searchable data catalogue. There's specific support for mapping FAME series with a single series key to richer multi-dimensional structures including adding useful attributes like units and series confidentiality.
Create hierarchical category trees of datasets and pre-defined queries to simplify data discovery.
Fusion Registry 11 has been designed to specifically support the needs of public dissemination in particular: security, performance, scalability and embargo.
All dissemination services are driven from its SDMX-compliant REST API supporting a wide range of dissemination channels including 'statistics database' web sites, data dashboards, data / metadata API services and analytics tools including Excel, Tableau and Power BI.
The challenge of publishing curated but dynamic web data tables is solved by Fusion Registry 11's Publication Tables feature. Design tables showing precisely the statistics required that are both user interactive and update when the data is refreshed. Combine statistics from multiple datasets in the same table.
In addition to data storage, Fusion Registry 11 can be used as a decoupled data processing engine for SDMX data structural validation, mapping to different structures and conversion of data between transmission formats.
All processing functions are available through the REST API making them easy to integrate into data engineering pipelines.
Use Fusion Registry 11 to prepare and store SDMX data for reporting.
Importing the data collector's structural metadata allows datasets to transformed into the required structure and validated for compliance prior to submission.
Excel remains a popular way to collect aggregated data. Using Fusion Registry 11, that process is simplified and automated by generating pre-formatted Excel forms directly from the dataset metadata.
Features
| Function | Feature | Fusion Registry 10 | Fusion Registry 11 |
|---|---|---|---|
| Internal Information Model | SDMX 2.1 | ||
| SDMX 3.0 | |||
| Structural Metadata Formats | SDMX-ML v3.0 | ||
| SDMX-ML v2.1 | |||
| SDMX-ML v2.0 | |||
| SDMX-ML v1.0 | |||
| SDMX-JSON v3.0 | AgencyScheme Categorisation CategoryScheme Codelist ConceptScheme ContentConstraint DataConsumerScheme Dataflow DataProviderScheme DataStructureDefinition ProvisionAgreement RepresentationMap StructureMap The remainder of the structures are on the roadmap |
||
| SDMX-JSON v2.1 | |||
| EDI | |||
| Structural Metadata Management | Load structural metadata from file | ||
| Load structural metadata from URL | |||
| Author and maintain structural metadata using the web interface | |||
| Author and maintain structural metadata using FusionXL addin for Excel | |||
| ACID structure repository | |||
| Structural metadata import / export as SDMX | |||
| Structural metadata import / export as Excel | |||
| SDMX structures REST API | |||
| Structure storage (limited by available memory) | |||
| Structure comparison | |||
| Structure validation on import | |||
| Structure referential integrity enforcement | |||
| Tools to correct referential integrity issues (fix 'zombie' structures) | |||
| Time dependant constraints | |||
| Structure-level validity | |||
| Item-level validity | |||
| Subscription / notification of changes to structures via email or HTTP POST | |||
| Structure update transaction journalling | |||
| Rollback structure changes to a specified journalled transaction | |||
| Structural metadata time travel | On roadmap | ||
| SDMX Structures | Agency Schemes | ||
| Constraints | Converted to Data Constraints on import | ||
| Categorisations | |||
| Category Schemes | |||
| Codelists | |||
| Concept Schemes | |||
| Data Consumer Schemes | |||
| Data Provider Schemes | |||
| Data Structure Definitions | |||
| Dataflows | |||
| Hierarchical Codelists | Converted to Hierarchies on import | ||
| Metadata Structure Definitions | |||
| Metadataflows | |||
| Organisation Unit Schemes | |||
| Processes | |||
| Provision Agreements | |||
| Reporting Taxonomies | |||
| Structure Sets | Converted to Structure Maps on import | ||
| Structure Map | |||
| Representation Map | |||
| Organisation Scheme Map | |||
| Concept Scheme Map (SDMX 3.0) | On roadmap | ||
| Category Scheme Map | On roadmap | ||
| Reporting Taxonomy Map | |||
| Value List | |||
| Hierarchy | |||
| Hierarchy Association | |||
| Metadata Constraint | On roadmap | ||
| Data Constraint | |||
| Metadata Constraint | |||
| Metadata Provision Agreement | |||
| Metadata Provider Scheme | |||
| Metadataset | On roadmap | ||
| 'Extended' Structures (structures that are not part of the formal SDMX specification) | Validation Schemes | ||
| Reporting Templates | |||
| Publication Tables | |||
| Structural Metadata Storage Options | MySQL | ||
| Oracle | |||
| Microsoft SQL Server | |||
| Identity and Access Management | Microsoft Active Directory service integration | ||
| OpenLDAP directory service integration | |||
| Fusion Security directory service integration | |||
| Single-user mode (no directory service required) | |||
| Certificate authentication | |||
| SSO (AD Kerberos, SAML, oauth) | On 2023 roadmap | ||
| Data | Load data from file | ||
| Load data from URL (file or REST API) | |||
| SDMX-ML v3.0 structure specific data format (XML) | On roadmap | ||
| SDMX-ML v2.1 structure specific data format (XML) | |||
| SDMX-ML v2.0 structure specific data format (XML) | |||
| SDMX-ML v2.1 generic data format (XML) | |||
| SDMX-ML v2.0 generic data format (XML) | |||
| SDMX-JSON v2.1 data format | |||
| SDMX-JSON v3.0 data format | On roadmap | ||
| SDMX-CSV v2.1 data format | |||
| SDMX-CSV v3.0 data format | (some limitations) | ||
| EDI data format | |||
| Excel FusionXL data format | |||
| Interactive data load using the web user interface | |||
| Aggregated time series data storage | |||
| Microdata storage | On roadmap | ||
| In-memory data store (Fusion Data Store) | |||
| SQL table data store | |||
| Data processing REST API (validation, conversion, mapping) | |||
| Data storage REST API | |||
| Plugin interface for adding custom data readers and writers | |||
| Data Publication | Publication Tables | ||
| Analytics Tools Connectors | Tableau | ||
| Excel | |||
| Power BI | Using third-party connector | Using third-party connector | |
| R | Using third-party connector | Using third-party connector | |
| SAS | Using third-party connector | Using third-party connector | |
| Matlab | Using third-party connector | Using third-party connector | |
| Data Registration | SDMX data source registration | ||
| Validation and indexing of registered data sources | |||
| Data Validation | Structural compliance | ||
| Compliance of data values with the DSD | |||
| Compliance with constraint rules | |||
| Duplicate observations or series checks | |||
| Mandatory attributes | |||
| Validation Schemes - basic business rule validation expressions | |||
| Validation Schemes - advanced business rule validation expressions | |||
| Validation rules configuration - set what rules are applied and whether they prevent conversion or data publication | |||
| Plugin interface for adding custom validators | |||
| Data validation processing (load data, validate it against the defined structure and business rules, return a validation report plus valid and invalid series as separate output datasets) | |||
| Data validation REST API | |||
| VTL 2.0 | Storage of VTL programs as SDMX structural metadata | ||
| Execution of VTL programs for validation or transformation of data | |||
| SDMX Structure Mapping | Concept Scheme Maps (SDMX 2.1) | ||
| Codelist Maps | |||
| Data Structure Maps | |||
| Dataflow Maps | |||
| Regex pattern mapping rules | |||
| N-to-N data maps | |||
| N-to-1 data maps | |||
| 1-to-N data maps | |||
| 1-to-1 data maps | |||
| Mapped Datasets | Dynamically mapped datasets - like SQL views | ||
| Virtual Dataflows | Virtual Dataflows describe a sub-cube of a dataflow | On roadmap | |
| Data Transformation | Data transformation processing (load data, transform it to a different structure using SDMX Structure Mapping and return the result) | ||
| Data transformation REST API | |||
| Data Conversion | Between supported SDMX formats and versions (SDMX-ML, SDMX-JSON, SDMX-CSV, EDI) | ||
| From Excel Reporting Template to SDMX formats | |||
| Quick convert to SDMX-ML 2.1 Structure Specific format | |||
| Conversion to and from Fusion Excel format for SDMX datasets | |||
| Data Reporting | Excel Reporting Templates - definition and generation | ||
| Excel Reporting Templates - validation and conversion of reported data | |||
| Excel Reporting Templates - load and storage of reported data | |||
| Excel Reporting Templates - configurable template security rules | |||
| Content Security / Access Controls | Structure creation and maintenance controls (Agency privileges) | ||
| Data load and modification controls (Data Provider privileges) | |||
| Data access controls at the dataflow, series or observation level | |||
| Data attribute visibility control | |||
| Structure access controls at the structure or item level | |||
| Granular administraive privileges | |||
| Public mode - Registry content is readable by both unauthenticated guest and authenticated users | |||
| Private mode - Registry content is accessible only to authenticated users | |||
| Auditing | SDMX structure transaction auditing | ||
| User activity auditing | |||
| Enterprise Deployment | Load balancer support (clustering multiple Registry instances behind a load balancer for resilience and load tolerance) | ||
| Apache Kafka Integration | Kafka 'Structure Notification' Producer for publishing changes to structural metadata on a definable topic | ||
| Client-side API | IM-JS JavaScript client-side programming library | ||
| SDMX-UI TypeScript client-side programming library (higher-level abstraction) | On roadmap | ||
| Command Line Interface | Fusion Command Line Interface for managing structural metadata, data and reference metadata |
Metadata and data
- Publication tables
- New presentational metadata artefact describing curated tables of statistics for publication on websites or dashboards (more)
- Reference metadata reports (metadataset)
- Support for reference metadata report / metadataset artefacts
- SDMX-JSON 3.0 structure format
- Support for the SDMX 3.0 JSON transmission format for structural metadata
- Improved error handling framework
- Improved capture, handling and reporting of errors such as referential integrity violations
- Structural metadata consistency checks and 'safe mode'
- Strengthened checks on Registry start-up with the Registry placed in 'safe mode' if problems are detected
- Performance improvements
- Improved support for very large structures, improved performance when processing large datasets
- Metadata time travel
- Retrieve structual metadata as it was at a defined point in the past
- Structure mapping default observation value
- Option to to set a default ouput observation value for use where the input value is missing
- SDMX-JSON 3.0 data format
- Support for the SDMX 3.0 JSON transmission format for data excluding hierarchical reference metadata embedded within the data message
- SDMX Data Registration
- Support for registering SDMX data sources
- Virtual dataflows
- Virtual dataflows describe a sub-cube of data similar in concept to a SQL view
Data processing
- Mapping microservice
- Decoupled stateless SDMX mapping microservice
Features
- Change to SDMX 3.0 as the internal information model (Fusion Registry 10 used SDMX 2.1).
- Microdata modelling using the SDMX 3.0 enhanced Data Structure Definition.
- Geospatial data modelling using the SDMX 3.0 Geographic and Geogrid codelists, and the GeospatialInformation representation type.
- Improved modelling of constraints (note that only data constraints are supported in 11.0.0 with metadata constraints planned for a future release). Addition of the '%' and '+' wildcard operators.
- Support for three-digit semantic version numbers and REST API support for querying structures using version number of the form 1.3+ to mean any version 1 greater that 1.3.
- Fusion Portal - scheduled and manual loads of structure and data.
- Improved more granular access control rules for data and structures. New Fusion Security Manager UI for rules maintenance.
- Improved Fusion Data Browser - for users: improved data table, category tree search, data sharing by API URL. For administrators: simplified maintenance of series presentation configuration, category trees and pre-defined queries.
- JNDI data source support.
- Strengthened security by externalising the password used to encrypt database and other passwords.
- Oracle Weblogic web application server support.
- Operating database schema - Fusion Registry 11 is not compatible with Fusion Registry 10 operating databases. Upgrading from Fusion Registy 10 to 11 requires a fresh installation and migration of the settings, data and structural metadata content.
- Upper case enforced for maintainable structure IDs - structure IDs must always be upper case in Fusion Registry 11. IDs in lower or mixed case will be converted to upper case on import, but any duplicates that result will raise an error.
- Fusion Security support deprecated - Fusion Registry 11 supports Active Directory and OpenLDAP directory services only.
- All SDMX 2.1 stuctures can be loaded into Fusion Registry 11, although some such as Structure Maps and Hierarchical Codelists are converted irreversably to the equivalent SDMX 3.0 model structures.
- SDMX 2.1, 2.0 and EDI structure and data formats continue to be supported where possible. Structures such as Representation Maps which only exist in the SDMX 3.0 information model cannot be exported in legacy structure formats. Similarly, data that uses some of the features introduced in SDMX 3.0 for handling microdata cannot be converted to an SDMX 2.1 or older data format.
- The SDMX 2.1 structure and data REST API syntax and entry points are supported meaning that most systems and processes designed for use with Fusion Registry 10 will continue to work with Fusion Registry 11.
Fusion Registry Deployment Options
SDMX data warehouse delivered as a managed software as a service (SaaS)
A cloud hosted Fusion Registry SDMX statistical data warehouse pre-configured, maintained and ready to go.
Annual subscription.
Custom designed SDMX data and metadata solutions
Metadata Technology will custom design solutions to precisely meet your SDMX data and metadata management needs using the Fusion Registry toolset for on-premises deployment.
You can choose to implement the solutions yourself, if ncessary buying specific advice and services like modelling or SDMX training to support your project.
Alternatively Metadata Technology, in conjunction with our integration partners, can plan and manage your entire implementation project including detailed design, modelling of your data domains in SDMX, data collection and ETL processes, data migration, custom dashboards / dissemination portals, training and handover.
Fusion Registry components, modules and integrations
1. Fusion Registry 11 Core
The main statistical data warehouse engine with an integrated SDMX 3.0 structural metadata registry and maintenance / administration web user interface.
2. Fusion Edge Server
Secure high-performance data dissemination server.
Fusion Edge Server is a separate light-weight dissemination module that works in tandem with Fusion Registry. It's designed for public dissemination use cases that need scalability, high-performance and resilience, and where it is desirable to isolate the master Fusion Registry. Fusion Edge Server has no user interface and provides a read-only SDMX REST API suitable for driving a range of dissemination services and tools.
more
3. Fusion Data Browser
Web tool for data discovery, evaulation and retrieval.
Fusion Data Browser is a web application suitable for both internal and external users to search and explore the catalogue of datasets, select series and cubes of interest, build visualisations using tables and charts, and retrieve selected data in a variety of formats including SDMX, Excel and CSV.
video
4. FXLData
An Excel add-in providing a collection of functions for retrieving statistical data from Fusion Registry directly into a worksheet.
more
5. Fusion Portal
Management web user interface to administer both manual and scheduled data and structure loads into a Fusion Registry 11 data warehouse, where the content is pulled from external sources such as SDMX web services, a local file system or from URLs. video
6. Fusion Security Manager
Management web user interface for administering granular access control rules for both data and structures. video
7. Fusion Fame Mapper
Management web user interface for administering mapping rules for transforming FAME series identified by a single series code to SDMX data sets with multiple dimensions and attributes.
8. Fusion Shell
Command line interface providing a range of utility commands such as comparing the data content between two Fusion Registry instances - useful for testing data migration.
9. Fusion Command Line Interface
Command line interface for scripting the publication and maintenance of structures, data and reference metadata.