Difference between revisions of "Fusion Data Mapper"

From Fusion Registry Wiki
Jump to navigation Jump to search
 
(169 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
== Overview ==
+
[[Category:Fusion Data Mapper]]
 +
== Overview – Fusion Data Mapper==
 
This document provides guidance and operating procedures for creating and managing mapped
 
This document provides guidance and operating procedures for creating and managing mapped
−
datasets using Fusion Registry 9 and the Fusion Data Mapper.
+
datasets using Fusion Registry 10 and the Fusion Data Mapper.
 +
 
 +
'''Use Case'''
  
−
====== Use Case ======
 
 
The primary use case is transforming single dimensional datasets to SDMX multi-dimensional
 
The primary use case is transforming single dimensional datasets to SDMX multi-dimensional
 
structures.
 
structures.
Line 15: Line 17:
 
Mapper provides an easy-to-use user interface for defining and management the mapping rules.
 
Mapper provides an easy-to-use user interface for defining and management the mapping rules.
  
−
====== Audience ======
+
'''Audience'''
 
* Metadata Managers – those responsible for managing the metadata mappings on the Bank’s catalogue of time series on a day to day basis.
 
* Metadata Managers – those responsible for managing the metadata mappings on the Bank’s catalogue of time series on a day to day basis.
 
* Metadata Superusers – those responsible for managing the core structural metadata including Agencies, Concepts, Data Structure Definitions and Codelists.
 
* Metadata Superusers – those responsible for managing the core structural metadata including Agencies, Concepts, Data Structure Definitions and Codelists.
 
* System Administrators – those responsible for administering Fusion Registry 9 as part of the integrated statistical data and metadata system, and managing the Time Series Database as the source of observation data.
 
* System Administrators – those responsible for administering Fusion Registry 9 as part of the integrated statistical data and metadata system, and managing the Time Series Database as the source of observation data.
−
====== Prerequisites ======
+
 
 +
'''Prerequisites'''
 +
 
 
Readers are assumed to have an understanding of basic SDMX principles and the purpose of the
 
Readers are assumed to have an understanding of basic SDMX principles and the purpose of the
 
main SDMX structural metadata artefacts including Concepts, Codes and Codelists, Categories, Data
 
main SDMX structural metadata artefacts including Concepts, Codes and Codelists, Categories, Data
 
Structure Definitions (DSDs), Dataflows, Provision Agreements, Structure Sets and Dataflow Maps.
 
Structure Definitions (DSDs), Dataflows, Provision Agreements, Structure Sets and Dataflow Maps.
  
−
====== Terminology ======
+
'''Terminology'''
−
Dataset Dataset            
+
 
 +
{|
 +
|-style="vertical-align: top;"
 +
| Dataset ||  Dataset refers to a named collection of series that typically all fall under a specific topic, for instance ‘National Accounts’. In Fusion Registry, an SDMX Dataflow represents a dataset.
 +
 
 +
 
 +
 
 +
|-style="vertical-align: top;"
 +
| Mapped Dataset||   A Mapped Dataset is an SDMX Dataflow where data is taken from a ‘source’ Dataflow and transformed to different dimensionality using defined mapping rules. The Fusion Data Mapper manages these mapping rules.
 +
 In this document, the source Dataflow is assumed to be observation data from the Time Series Database which is described by a Data Structure Definition having only SERIES_CODE, TIME_PERIOD and OBS_VALUE dimensions.
 +
 
 +
 
 +
|-style="vertical-align: top;"
 +
| Time Series Database||   The source of time series observation data without metadata that Fusion Registry maps to Mapped Datasets using the defined mapping rules.
 +
|}
 +
 
 +
==Related Pages==
 +
For further guidance on Fusion Data Mapper:
 +
 
 +
[[Add a Mapped Dataset – Fusion Data Mapper]]
 +
 
 +
[[Add Series to a Dataset – Fusion Data Mapper]]
 +
 
 +
[[Browse Privileges – Fusion Data Mapper]]
 +
 
 +
[[Bulk Maintenance of Metadata Values using Excel Import / Export – Fusion Data Mapper]]
 +
 
 +
[[Changing the Dimensionality of a Dataset – Fusion Data Mapper]]
  
−
refers to a named collection of series that typically all fall under a
+
[[Clone a Dataset – Fusion Data Mapper]]
−
specific topic, for instance ‘National Accounts’. In Fusion Registry, an SDMX
 
−
Dataflow represents a dataset.
 
−
Mapped Dataset A Mapped Dataset is an SDMX Dataflow where data is taken from a
 
−
‘source’ Dataflow and transformed to different dimensionality using
 
−
defined mapping rules. The Fusion Data Mapper manages these mapping
 
−
rules.
 
−
In this document, the source Dataflow is assumed to be observation data
 
−
from the Time Series Database which is described by a Data Structure
 
−
Definition having only SERIES_CODE, TIME_PERIOD and OBS_VALUE
 
−
dimensions.
 
−
Time Series Database The source of time series observation data without metadata that Fusion
 
−
Registry maps to Mapped Datasets using the defined mapping rules.
 
  
−
= The Fusion Data Mapper User Interface =
+
[[Codelists - Adding and Removing Codes – Fusion Data Mapper]]
−
The Fusion Data Mapper is a web user interface providing the following main functions:
 
  
−
'''Authenticated users with sufficient structural metadata maintenance privileges'''
+
[[Codelists – Adding and Changing Multilingual Code Names with Impact Analysis - Fusion Data Mapper]]
  
−
* Add and remove mapped datasets
+
[[Content Security Caveats – Fusion Data Mapper]]
−
* Add and remove series on mapped datasets
 
−
* Interactively set and change the metadata values on a series by series basis
 
−
* Export metadata values for selected series to Excel
 
−
* Import metadata values for defined series from Excel
 
−
* Change code names with impact analysis
 
  
−
'''Anonymous or authenticated users with sufficient privileges to view but not change the structural metadata'''
+
[[Content Security Metadata Management Use Cases – Fusion Data Mapper]]
  
−
* Browse the catalogue of mapped datasets
+
[[Default Code Values – Fusion Data Mapper]]
−
* Examine the ‘definition’ of a dataset – its dimensionality and list of possible codes for each
 
−
* Dimension or Attribute
 
−
* Browse the series in each dataset
 
  
−
= The Fusion Registry Administration Interface =
+
[[Maintaining Metadata Values on Series Interactively using the Web Interface – Fusion Data Mapper]]
  
−
The Administration Interface is Fusion Registry’s main web user interface.
+
[[Maintenance Privileges – Fusion Data Mapper]]
  
−
For the purposes of managing the metadata on mapped datasets, it provides the following functions:
+
[[Registering a Series – Fusion Data Mapper]]
  
−
'''Authenticated users with sufficient structural metadata management privileges'''
+
[[Remove a Mapped Dataset – Fusion Data Mapper]]
  
−
* Create and modify SDMX Data Structure Definitions (DSDs)
+
[[Removing Series from a Dataset – Fusion Data Mapper]]
−
* Create and modify SDMX Concepts
 
−
* Create and modify SDMX Codelists
 
−
* Add and remove codes from SDMX Codelists
 
−
* Register a series (series must be ‘registered’ before they can be mapped in dataset by adding the Series Code and Series Name to the relevant SERIES_CODE Codelist)
 
  
−
Refer to the ''Fusion Registry Structural Metadata Management Guide'' for general information on using the Fusion Registry Administration Interface for creating and maintaining core SDMX structure
+
[[The Fusion Data Mapper User Interface]]
−
metadata artefacts including DSDs, Dataflows, Concepts, Categories and Codelists.
 

Latest revision as of 06:41, 11 September 2023

Overview – Fusion Data Mapper

This document provides guidance and operating procedures for creating and managing mapped datasets using Fusion Registry 10 and the Fusion Data Mapper.

Use Case

The primary use case is transforming single dimensional datasets to SDMX multi-dimensional structures.

Single dimensional datasets are those with a single unique identifier for each series (e.g. Series Code) such as created by FAME or similar time-series production systems.

One-to-one transformations only are supported by this version of the Fusion Data Mapper.

The transformation is performed by Fusion Registry using SDMX Structure Mapping. Fusion Data Mapper provides an easy-to-use user interface for defining and management the mapping rules.

Audience

  • Metadata Managers – those responsible for managing the metadata mappings on the Bank’s catalogue of time series on a day to day basis.
  • Metadata Superusers – those responsible for managing the core structural metadata including Agencies, Concepts, Data Structure Definitions and Codelists.
  • System Administrators – those responsible for administering Fusion Registry 9 as part of the integrated statistical data and metadata system, and managing the Time Series Database as the source of observation data.

Prerequisites

Readers are assumed to have an understanding of basic SDMX principles and the purpose of the main SDMX structural metadata artefacts including Concepts, Codes and Codelists, Categories, Data Structure Definitions (DSDs), Dataflows, Provision Agreements, Structure Sets and Dataflow Maps.

Terminology

Dataset   Dataset refers to a named collection of series that typically all fall under a specific topic, for instance ‘National Accounts’. In Fusion Registry, an SDMX Dataflow represents a dataset.


Mapped Dataset   A Mapped Dataset is an SDMX Dataflow where data is taken from a ‘source’ Dataflow and transformed to different dimensionality using defined mapping rules. The Fusion Data Mapper manages these mapping rules.

 In this document, the source Dataflow is assumed to be observation data from the Time Series Database which is described by a Data Structure Definition having only SERIES_CODE, TIME_PERIOD and OBS_VALUE dimensions.


Time Series Database   The source of time series observation data without metadata that Fusion Registry maps to Mapped Datasets using the defined mapping rules.

Related Pages

For further guidance on Fusion Data Mapper:

Add a Mapped Dataset – Fusion Data Mapper

Add Series to a Dataset – Fusion Data Mapper

Browse Privileges – Fusion Data Mapper

Bulk Maintenance of Metadata Values using Excel Import / Export – Fusion Data Mapper

Changing the Dimensionality of a Dataset – Fusion Data Mapper

Clone a Dataset – Fusion Data Mapper

Codelists - Adding and Removing Codes – Fusion Data Mapper

Codelists – Adding and Changing Multilingual Code Names with Impact Analysis - Fusion Data Mapper

Content Security Caveats – Fusion Data Mapper

Content Security Metadata Management Use Cases – Fusion Data Mapper

Default Code Values – Fusion Data Mapper

Maintaining Metadata Values on Series Interactively using the Web Interface – Fusion Data Mapper

Maintenance Privileges – Fusion Data Mapper

Registering a Series – Fusion Data Mapper

Remove a Mapped Dataset – Fusion Data Mapper

Removing Series from a Dataset – Fusion Data Mapper

The Fusion Data Mapper User Interface

Retrieved from "https://wiki.sdmxcloud.org/index.php?title=Fusion_Data_Mapper&oldid=6072"