Fusion Data Mapper - Revision history

Vmurrell at 13:41, 11 September 2023

2023-09-11T13:41:10Z

2020-09-14T11:53:44Z

‎Overview – Fusion Data Mapper

2019-10-30T11:20:12Z

‎Related Pages

2019-10-30T11:15:15Z

‎Related Pages

2019-10-29T13:01:34Z

‎Overview – Fusion Data Mapper

2019-10-29T12:56:57Z

‎Overview – Fusion Data Mapper

2019-10-29T12:56:24Z

‎Overview – Fusion Data Mapper

2019-10-29T12:55:22Z

‎Use Case

2019-10-25T13:18:48Z

Replaced content with "Category:Data Mapping Category:Fusion Data Mapper == Overview – Fusion Data Mapper== This document provides guidance and operating procedures for creating and ma..."

2019-10-25T12:50:36Z

‎Add a Mapped Dataset – Fusion Data Mapper

@@ Line 3: / Line 3: @@
 == Overview – Fusion Data Mapper==
 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'''

@@ Line 48: / Line 48: @@
 ==Related Pages==
 For further guidance on Fusion Data Mapper:
 [[Add a Mapped Dataset – Fusion Data Mapper]]

← Older revision		Revision as of 11:15, 30 October 2019
Line 48:		Line 48:
	==Related Pages==		==Related Pages==
	For further guidance on Fusion Data Mapper:		For further guidance on Fusion Data Mapper:
		+	[[Add a Mapped Dataset – Fusion Data Mapper]]

@@ Line 6: / Line 6: @@
 '''Use Case'''
 The primary use case is transforming single dimensional datasets to SDMX multi-dimensional
 structures.
@@ Line 17: / Line 18: @@
 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 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'''
+'''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'''
+'''Terminology'''
 {|
 |-style="vertical-align: top;"
@@ Line 42: / Line 45: @@
 | Time Series Database|| &nbsp;&nbsp;The source of time series observation data without metadata that Fusion Registry maps to Mapped Datasets using the defined mapping rules.
 |}

@@ Line 138: / Line 138: @@
 # Choose a Source Dataset from those available. All Dataflows in the Fusion Registry with a single dimension are shown in this list. However, it is important that the single dimension of the chosen source dataset must be the Series Code. If multiple Source Datasets are shown in the list, care should be taken to choose the correct one otherwise it will be impossible to create the metadata mappings.
 # Choose the Dataset Definition for the new dataset. A list of available Data Structure Definitions (DSDs) are shown to choose from.
-#:::The DSD chosen for the new dataset must follow these rules:
+#:::[[File:Triangle.jpg|frameless|30px]]The DSD chosen for the new dataset must follow these rules:
 #:::* the DSD must include a SERIES_CODE dimension
 #:::* the SERIES_CODE dimension must be coded (conventionally, the Codelist is named CL_SERIES_CODE)