Difference between revisions of "Fusion Metadata Overview"
(Created page with "Fusion Metadata Registry is a free to use structural metadata registry for SDMX supporting EDI, SDMX 1.0, 2.0, 2.1 and 3.0. == Inside Fusion Metadata Registry == The heart of...") |
(→FMR provides two interfaces) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
Fusion Metadata Registry is a free to use structural metadata registry for SDMX supporting EDI, SDMX 1.0, 2.0, 2.1 and 3.0. | Fusion Metadata Registry is a free to use structural metadata registry for SDMX supporting EDI, SDMX 1.0, 2.0, 2.1 and 3.0. | ||
| − | + | = Inside Fusion Metadata Registry = | |
The heart of Fusion Metadata Registry is its structural metadata repository - essentially a database that implements the SDMX 3.0 information model. | The heart of Fusion Metadata Registry is its structural metadata repository - essentially a database that implements the SDMX 3.0 information model. | ||
| Line 14: | Line 15: | ||
- FMR 10 implements the SDMX 2.1 registry specification. | - FMR 10 implements the SDMX 2.1 registry specification. | ||
| − | - FMR 11 implements the SDMX 3.0 registry specification. | + | - FMR 11 implements the SDMX 3.0 registry specification. Click here to read the [[FMR_11.0_release_notes |Release notes for Version 11.]] |
== Data Processing == | == Data Processing == | ||
| Line 26: | Line 27: | ||
Finally for for data collectors, FMR's Excel data collection forms generator generates cross-tabulation data collection forms allowing data reporters to simply fill in the blank cells with the required observation values. The precise content and layout of these forms are defined by creating templates from which a personalised form is generated for each data provider. | Finally for for data collectors, FMR's Excel data collection forms generator generates cross-tabulation data collection forms allowing data reporters to simply fill in the blank cells with the required observation values. The precise content and layout of these forms are defined by creating templates from which a personalised form is generated for each data provider. | ||
| + | |||
| + | = Key Use Cases = | ||
| + | == Structural metadata management == | ||
| + | |||
| + | * Centralise and control structural metadata | ||
| + | * Author and maintain structural metadata | ||
| + | * Drive statistics production using centrally-controlled metadata | ||
| + | * Provide an SDMX-compliant a REST structure API | ||
| + | |||
| + | == Statistics production == | ||
| + | * Validate data for compliance with structural metadata, constraints and business rules (not VTL) | ||
| + | * Execute complex data mapping (SDMX structure maps, not VTL) | ||
| + | * Convert data between formats (convert between SDMX formats) | ||
| + | |||
| + | == Data collection == | ||
| + | * Collect data using metadata-driven Excel forms | ||
| + | * Map incoming data into standardised structures | ||
| + | |||
| + | == Data reporting == | ||
| + | * Prepare SDMX data for reporting | ||
| + | * Validate data for compliance with the data collector's specifications prior to reporting | ||
| + | |||
| + | ==Capacity == | ||
| + | * No fixed limits on the number of users | ||
| + | * No fixed limits on the volume of structures - in practice the volume of structures is limited by the available compute platform memory | ||
Latest revision as of 03:04, 30 March 2024
Fusion Metadata Registry is a free to use structural metadata registry for SDMX supporting EDI, SDMX 1.0, 2.0, 2.1 and 3.0.
Inside Fusion Metadata Registry
The heart of Fusion Metadata Registry is its structural metadata repository - essentially a database that implements the SDMX 3.0 information model.
All structural metadata objects are stored according to this model which provides a rigorous dependency graph that defines and enforces the metadata's referential integrity. This strongly enforced referential integrity provides confidence that the metadata model is always complete - a DSD for instance can never exist without its referenced Codelists.
FMR provides two interfaces
- Web user interface: a web interface for interactively discovering and retrieving structures, structure authoring and maintenance, and system administration.
- REST application programming interface: a REST web services API for automation that implements the SDMX v2 structure REST API specification, with additional extensions for creating and modifying structures, data validation and data transformation.
- FMR 10 implements the SDMX 2.1 registry specification.
- FMR 11 implements the SDMX 3.0 registry specification. Click here to read the Release notes for Version 11.
Data Processing
In addition to its core role as a structural metadata registry, FMR's integrated data processing services support:
- Data validation: submitted data is checked against nine separate quality rules including consistency with the DSD, and compliance with any Data Constraints
- Data conversion: conversion of SDMX datasets between transmission formats including EDI, XML, JSON, CSV and Excel
- Data mapping: transformation of a dataset to a different DSD using SDMX structure mapping
Data Collection
Finally for for data collectors, FMR's Excel data collection forms generator generates cross-tabulation data collection forms allowing data reporters to simply fill in the blank cells with the required observation values. The precise content and layout of these forms are defined by creating templates from which a personalised form is generated for each data provider.
Key Use Cases
Structural metadata management
- Centralise and control structural metadata
- Author and maintain structural metadata
- Drive statistics production using centrally-controlled metadata
- Provide an SDMX-compliant a REST structure API
Statistics production
- Validate data for compliance with structural metadata, constraints and business rules (not VTL)
- Execute complex data mapping (SDMX structure maps, not VTL)
- Convert data between formats (convert between SDMX formats)
Data collection
- Collect data using metadata-driven Excel forms
- Map incoming data into standardised structures
Data reporting
- Prepare SDMX data for reporting
- Validate data for compliance with the data collector's specifications prior to reporting
Capacity
- No fixed limits on the number of users
- No fixed limits on the volume of structures - in practice the volume of structures is limited by the available compute platform memory
