|
|
| Line 14: |
Line 14: |
| | * Transforming single-dimension FAME series into multi-dimensional SDMX series | | * Transforming single-dimension FAME series into multi-dimensional SDMX series |
| | * Authoring and maintaining reference metadata | | * Authoring and maintaining reference metadata |
| − |
| |
| − | ==Specification==
| |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | | Application Type || Server
| |
| − | |-
| |
| − | | User Interface || Web user interface accessible using a standard web browser [https://demo.metadatatechnology.com/FusionRegistry/overview.html Live Demo]
| |
| − | |-
| |
| − | | API || SDMX-compliant REST API with proprietary extensions [https://demo.metadatatechnology.com/FusionRegistry/webservice/data.html Data API Example]
| |
| − | |-
| |
| − | | Technology || Java web application
| |
| − | |-
| |
| − | | Compatible platforms || Linux, Windows, Mac and other platforms supporting a Java web runtime environment
| |
| − | |-
| |
| − | | Minimum operating configuration || The minimim list of components required to deploy a Fusion Registry Core service are:<br>
| |
| − | The Fusion Registry web app (WAR file)<br>
| |
| − | Java Runtime Environment<br>
| |
| − | Java web application server (for instance Apache Tomcat)<br>
| |
| − | SQL database (MySQL, SQL Server or Oracle
| |
| − | |-
| |
| − | | Configuration maintenance || Primarily using the admin functions under the web user interface
| |
| − | |-
| |
| − | | Configuration information storage || Configuration information is stored in the main operating database, with database connection information stored in a properties file
| |
| − | |}
| |
| − |
| |
| − | [[Category:Components and Modules]]
| |
| − |
| |
| − | ==Functionality by Edition==
| |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | ! style="width:300px"| !! style="width:150px" | Data Essentials !! style="width:150px" | Enterprise !! style="width:150px" | Cloud
| |
| − | |-
| |
| − | | Structural Metadata Registry || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Data Collection || One data provider, pull from registered data sources not supported || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Data Integration || Registry managed SQL data stores only || style="background:#00FF55 | Full || Registry managed datastores and registered data sources only
| |
| − | |-
| |
| − | | Data Storage || Registry managed SQL data stores only || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Data Structural Validation ||style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Data Business Rules Validation using Metadata Technology's proprietary expression language|| Arithmetric rules only || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Data Structural Transformation || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Time Series Calculations || No || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Data Conversion || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Data Query Execution Engine || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Mapped Datasets ||style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Reference Metadata || No || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Audit || No || style="background:#00FF55 | Full|| style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Content Security || No || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | SDMX REST API || style="background:#00FF55 | Full|| style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | Extended REST API || style="background:#00FF55 | Full || style="background:#00FF55 | Full || style="background:#00FF55 | Full
| |
| − | |-
| |
| − | | VTL source code repository || colspan="4" | No - Planned for April 2021
| |
| − | |-
| |
| − | | VTL execution engine || colspan="4" | No - Planned for 2021/2022
| |
| − | |}
| |
SDMX statistical data engine and structural metadata registry.
This is the main engine at the heart of all Fusion-based SDMX systems providing data collection, integration, processing, storage, query execution and time-series calculation services.
Its integrated SDMX structural metadata registry acts as the central repository, authoring and maintenance tool for all of the structures including Codelists, Concepts and Data Structure Definitions.
Key Use Cases
- Statistical data warehouse
- Collecting and integrating data from multiple data providers
- Data dissemination - Fusion Registry's SDMX-compliant REST API is suitable for driving a range of dissemination services
- Authoring, maintaining and storing SDMX structural metadata
- Validating SDMX data prior to submission to another organisation
- Converting data between different formats (SDMX to SDMX, non-SDMX to SDMX, SDMX to non-SDMX)
- Transforming the structure of data to different dimensionality and coding schemes using SDMX Structure Mapping (for instance, map a dataset to a simplier DSD with fewer dimensions suitable for publication)
- Transforming single-dimension FAME series into multi-dimensional SDMX series
- Authoring and maintaining reference metadata
