Add a Mapped Dataset – Fusion Data Mapper - Revision history

Vmurrell at 13:22, 11 September 2023

2023-09-11T13:22:29Z

Vmurrell at 13:13, 11 September 2023

2023-09-11T13:13:16Z

Mbaird at 12:52, 25 October 2019

2019-10-25T12:52:08Z

Mbaird at 11:29, 25 October 2019

2019-10-25T11:29:49Z

Mbaird at 11:49, 23 October 2019

2019-10-23T11:49:05Z

Mbaird at 11:46, 23 October 2019

2019-10-23T11:46:08Z

Mbaird at 11:45, 23 October 2019

2019-10-23T11:45:21Z

Mbaird at 11:43, 23 October 2019

2019-10-23T11:43:46Z

Mbaird at 11:41, 23 October 2019

2019-10-23T11:41:51Z

Mbaird at 11:40, 23 October 2019

2019-10-23T11:40:55Z

← Older revision		Revision as of 13:22, 11 September 2023
Line 1:		Line 1:
−	~~[[Category:Data Mapping]]~~
	[[Category:Fusion Data Mapper]]		[[Category:Fusion Data Mapper]]

← Older revision		Revision as of 13:13, 11 September 2023
Line 1:		Line 1:
−
−
−
−
	[[Category:Data Mapping]]		[[Category:Data Mapping]]
	[[Category:Fusion Data Mapper]]		[[Category:Fusion Data Mapper]]

@@ Line 44: / Line 44: @@
 # 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)

@@ Line 49: / Line 49: @@
 #:::* the codes of series in the Time Series Database to be included in the dataset must be ‘registered’ by adding them to the SERIES_CODE Codelist (refer to [[Registering a Series – Fusion Data Mapper|Registering a Series]])
 #:::If an invalid DSD is chosen, the dataset will be created but it will be impossible to add series to it.
-# Set the name for the new Dataset in the chosen language. This the descriptive name of mapped dataset’s Dataflow, for instance ‘Employment’, ‘National Accounts’ or ‘Financial Activity’. After the Dataset has been created, changes to the name, including adding alternative names in different languages, can be made using the Fusion Registry Administration Interface – Dataflow maintenance. In the example shown in Figure 1, the name has been set in Hebrew.
+# Set the name for the new Dataset in the chosen language. This the descriptive name of mapped dataset’s Dataflow, for instance ‘Employment’, ‘National Accounts’ or ‘Financial Activity’. After the Dataset has been created, changes to the name, including adding alternative names in different languages, can be made using the Fusion Registry Administration Interface – Dataflow maintenance. In the example shown the name has been set in Hebrew.
 # Set the SDMX ID for the new dataset. The ID is the unique reference for the dataset’s SDMX Dataflow. You must follow these rules when choosing the ID:
 #:::*The ID must be unique
@@ Line 59: / Line 59: @@
 #::::NATIONAL_ACCOUNTS
 #:::*By convention, IDs are in upper case. For example, use ‘NATIONAL_ACCOUNTS’ rather than ‘National_Accounts’
-#::[[File:SS3.jpg|frameless|500px|''Figure 1 Fusion Data Mapper - Add Dataset Example'']]
+#::[[File:SS3.jpg|frameless|500px|''Add Dataset Example'']]
 #Set the Version for the dataset. This will be used to set the version of the dataset’s SDMX Dataflow. Version numbers are of the form <major_number>.<minor_number>. The following are valid:
 #:1.0

@@ Line 47: / Line 47: @@
 #:::* the DSD must include a SERIES_CODE dimension
 #:::* the SERIES_CODE dimension must be coded (conventionally, the Codelist is named CL_SERIES_CODE)
-#:::* the codes of series in the Time Series Database to be included in the dataset must be ‘registered’ by adding them to the SERIES_CODE Codelist (refer to [[Registering a Series – Fusion Data Mapper]])
+#:::* the codes of series in the Time Series Database to be included in the dataset must be ‘registered’ by adding them to the SERIES_CODE Codelist (refer to [[Registering a Series – Fusion Data Mapper|Registering a Series]])
 #:::If an invalid DSD is chosen, the dataset will be created but it will be impossible to add series to it.
 # Set the name for the new Dataset in the chosen language. This the descriptive name of mapped dataset’s Dataflow, for instance ‘Employment’, ‘National Accounts’ or ‘Financial Activity’. After the Dataset has been created, changes to the name, including adding alternative names in different languages, can be made using the Fusion Registry Administration Interface – Dataflow maintenance. In the example shown in Figure 1, the name has been set in Hebrew.

@@ Line 66: / Line 66: @@
 #:By convention, the first version is 1.0.
 #:
-#:Create new versions of a dataset when you need to change the dimensionality – refer to [[#Changing the Dimensionality of a Dataset – Fusion Data Mapper|Changing the Dimensionality of a Dataset]].
+#:Create new versions of a dataset when you need to change the dimensionality – refer to [[Changing the Dimensionality of a Dataset – Fusion Data Mapper|Changing the Dimensionality of a Dataset]].
 #Choosing ‘Add’ will create the new dataset which should then appear in the left-hand bar
 #::[[File:Pic2.jpg|frameless|500px]]