Fusion Data Mapper - Add Dataset - Revision history

Vmurrell at 13:17, 11 September 2023

2023-09-11T13:17:54Z

Vmurrell at 13:17, 11 September 2023

2023-09-11T13:17:16Z

Vmurrell at 13:15, 11 September 2023

2023-09-11T13:15:09Z

Vmurrell at 13:14, 11 September 2023

2023-09-11T13:14:11Z

Vmurrell at 12:16, 11 September 2023

2023-09-11T12:16:41Z

Vmurrell at 12:16, 11 September 2023

2023-09-11T12:16:15Z

Mnelson at 13:20, 24 July 2020

2020-07-24T13:20:33Z

Mnelson: /* Forward Data Queries */

2020-07-24T13:18:59Z

‎Forward Data Queries

Mnelson: /* Forward Data Queries */

2020-07-24T13:09:35Z

‎Forward Data Queries

Mnelson at 13:07, 24 July 2020

2020-07-24T13:07:59Z

@@ Line 1: / Line 1: @@
-[[Category:DataMapperFunctions]]
+[[Category:Fusion Data Mapper]]
 = Overview =
 [[File:TargetToSourceFlow.png|thumb|right|Mapping Dataflows]]

@@ Line 1: / Line 1: @@
 [[Category:DataMapperFunctions]]
 = Overview =
 [[File:TargetToSourceFlow.png|thumb|right|Mapping Dataflows]]

@@ Line 1: / Line 1: @@
 [[Category:DataMapperFunctions]]
-[[Category:Data Mapping]]
+[[Category:RetiredFunctionality]]
 = Overview =
 [[File:TargetToSourceFlow.png|thumb|right|Mapping Dataflows]]

@@ Line 1: / Line 1: @@
 [[Category:DataMapperFunctions]]
-[[Category:RetiredFunctionality]]
+[[Category:Data Mapping]]
 = Overview =
 [[File:TargetToSourceFlow.png|thumb|right|Mapping Dataflows]]

@@ Line 1: / Line 1: @@
 [[Category:DataMapperFunctions]]
-Category:RetiredFunctionality
+[[Category:RetiredFunctionality]]
 = Overview =

← Older revision		Revision as of 12:16, 11 September 2023
Line 1:		Line 1:
	[[Category:DataMapperFunctions]]		[[Category:DataMapperFunctions]]
		+	Category:RetiredFunctionality

	= Overview =		= Overview =

@@ Line 17: / Line 17: @@
 = Create Dataset Result =
-The result of creating a dataset, from the UI perspective, is an empty table, with a column for the source dimension and a column for each Dimension and Series Attributes in the Target.  This table can be used to define mapping rules.
+The result of creating a dataset, from the UI perspective, is an empty table, with a column for the source dimension and a column for each Dimension and Series Attributes in the Target.  This table can be used to [[Fusion_Data_Mapper_-_Creating_Mapping_Rules|define mapping rules]].
 [[File:Emptymappingtable.png]]

← Older revision		Revision as of 13:18, 24 July 2020
Line 14:		Line 14:

	The Data Query forwarding option is available on the form used to create the Dataflow. If this is set to YES then in addition to creating a Structure Map, a Provision Agreement will be created, and linked to the Dataflow Map as a source of Data.		The Data Query forwarding option is available on the form used to create the Dataflow. If this is set to YES then in addition to creating a Structure Map, a Provision Agreement will be created, and linked to the Dataflow Map as a source of Data.
		+
		+
		+	= Create Dataset Result =
		+	The result of creating a dataset, from the UI perspective, is an empty table, with a column for the source dimension and a column for each Dimension and Series Attributes in the Target. This table can be used to define mapping rules.
		+	[[File:Emptymappingtable.png]]

	= Summary of Structures Created =		= Summary of Structures Created =

@@ Line 10: / Line 10: @@
 = Forward Data Queries =
-[[File:Map Data Query.png|thumb|Map Data Query]]
+[[File:Mapquery.png|thumb|Map Data Query]]
 If the Source Dataflow has data loaded against it, then it is possible to link the Target Dataflow to this source Data.  This results in the Fusion Registry forwarding all the data queries against the Target Dataflow to the data store or the Source Dataflow.  When the data query is forwarded, the mapping rules are used to re-write the multidimensional data query to the corresponding series identifiers understood by the Source Dataflow. When the dataset is extracted from the data source, the same mapping rules are applied to convert it from a single dimensional time series dataset to a multidimensional time series.
 The Data Query forwarding option is available on the form used to create the Dataflow.  If this is set to YES then in addition to creating a Structure Map, a Provision Agreement will be created, and linked to the Dataflow Map as a source of Data.
-−
 = Summary of Structures Created =
 == Creating a new Dataflow==

← Older revision		Revision as of 13:07, 24 July 2020
Line 2:		Line 2:

	= Overview =		= Overview =
		+	[[File:TargetToSourceFlow.png\|thumb\|right\|Mapping Dataflows]]
		+
		+	The job of the Fusion Data Mapper is to map [[Dataflow_-_Structural_Metadata_Management\|Dataflows]] backed by Multidimesional [[Data_Structure_Definition_(DSD)_-_Structural_Metadata_Management\|Data Structures]] to a Dataflow backed by a [[Data_Structure_Definition_(DSD)_-_Structural_Metadata_Management\|Data Structure]] with only one Dimension other then Time. The Single Dimension Dataflow is referred to as the '''Source''' Dataflow with the multidimensional Dataflow being referred to as the '''Target'''.
		+
		+	The process of adding a Dataset results in linking a Target Dataflow to the Source Dataflow via a [[/Data_Structure_and_Dataflow_Maps_-_Structural_Metadata_Management\|Structure Map]]. The Source Dataflow must exist in the Fusion Registry before a Dataset can be added. The Target Dataflow does not have to exist, it can be created by the Data Mapper, or reused if it already exists. On adding a Dataset the Fusion Data Mapper will create a new Structure Map linking the Source Dataflow to the Target Dataflow.
		+
		+	= Forward Data Queries =
		+
		+	[[File:Map Data Query.png\|thumb\|Map Data Query]]
		+	If the Source Dataflow has data loaded against it, then it is possible to link the Target Dataflow to this source Data. This results in the Fusion Registry forwarding all the data queries against the Target Dataflow to the data store or the Source Dataflow. When the data query is forwarded, the mapping rules are used to re-write the multidimensional data query to the corresponding series identifiers understood by the Source Dataflow. When the dataset is extracted from the data source, the same mapping rules are applied to convert it from a single dimensional time series dataset to a multidimensional time series.
		+
		+	The Data Query forwarding option is available on the form used to create the Dataflow. If this is set to YES then in addition to creating a Structure Map, a Provision Agreement will be created, and linked to the Dataflow Map as a source of Data.
		+
		+	= Summary of Structures Created =
		+	== Creating a new Dataflow==
		+	This process will create a new Dataflow linked to the Data Structure Definition specified. A Structure Map will be created linking the new Dataflow to the Source Dataflow. If Forward Data Queries is selected, a Provision Agreement will be created and linked to the Structure Map as a source of Data.
		+
		+	== Map Existing Dataflow ==
		+	This process will craete a Structure Map linking the existing Dataflow to the Source Dataflow. If forward Data Queries is selected, the Mapping tool will search for a Provision Agreement against the target Dataflow, and this will be linked to the Structure Map as a source of Data. '''Note''' Linking an existing Provision Agreement to the Structure Map as a Data store will unlink it from any existing data store and may result in loss of data. If a Provision Agreement can not be found against the Target Dataflow, one will be created.
		+
		+	== Dataflow Construction ==
		+	The Dataflow Properties of Agency Id, Id, Version and Name are taken from the Form.
		+
		+	== Provision Agreement Construction ==
		+	Provision Agreements are created with the same Agency Id, Id and Version as the Target Dataflow. The system will look for a Data Provider with the same Id as the Agency Id of the Dataflow, under a Data Provider Scheme owned by the same Agency. For example if the Dataflow has the following properties:
		+
		+	Agency Id : CB1
		+	Id : CBS
		+	Version : 1.0
		+
		+	The Provision Agreement will have the same Agency Id, Id and Version, and Name as the Dataflow. The Data Provider for the Provision Agreement will have the following properties:
		+	Data Provider Scheme Agency Id: CB1
		+	Data Provider Id : CB1
		+
		+	If the Data Provider Scheme or Data Provider does not exist, it will be created.
		+
		+	== Structure Map Construction ==
		+	A Structure Set is created with the same Agency Id, Id and Version, and Name as the Dataflow. The Structure Map has the same Id as the Dataflow.