Data Store Management - Revision history

Vmurrell: /* Fusion Registry Managed Relational Database */

2025-10-09T15:13:00Z

‎Fusion Registry Managed Relational Database

2025-01-16T08:24:35Z

‎Mapped Data Store

2025-01-16T08:22:17Z

‎Data Sources Manager (new page)

2020-10-24T18:12:13Z

‎Viewing Historical Data Registrations

2020-10-24T18:11:43Z

‎Mapped Data Store

2020-10-24T18:11:03Z

‎“Default” External mode

2020-10-24T18:10:35Z

‎“Registry” External mode

2020-10-24T18:10:00Z

‎“Registry” External mode

2020-10-24T18:09:20Z

‎Data Sources Manager

2020-10-24T18:08:43Z

‎RSS Feed

← Older revision		Revision as of 15:13, 9 October 2025
Line 55:		Line 55:

	[[File:Dsmfig3.PNG\|600px]]		[[File:Dsmfig3.PNG\|600px]]
		+
		+	This feature is not available in Version 11 and subsequent versions.

	====Externally Managed Relational Database====		====Externally Managed Relational Database====

@@ Line 208: / Line 208: @@
 ''Figure 5 showing the mapping workflow from data query to data response where the Population Dataflow is linked to a mapped store, the target dataflow for the mapped store (defined by the associated structure map) is FAME_POP which itself links to a relational database.  The client remains agnostic to the mapping, and can retrieve the data in any Fusion Registry supported data format.''
-[[Data_Sources_Manager| Data Sources Manager]]
+[[Data_Sources_Manager| Click here to go to the Data Sources Manager article.]]
 ==Monitoring Data Publication Activity==

@@ Line 208: / Line 208: @@
 ''Figure 5 showing the mapping workflow from data query to data response where the Population Dataflow is linked to a mapped store, the target dataflow for the mapped store (defined by the associated structure map) is FAME_POP which itself links to a relational database.  The client remains agnostic to the mapping, and can retrieve the data in any Fusion Registry supported data format.''
-=='''[https://wiki.sdmxcloud.org/Data_Sources_Manager Data Sources Manager (new page)]'''==
+[[Data_Sources_Manager| Data Sources Manager]]
 ==Monitoring Data Publication Activity==

← Older revision		Revision as of 18:12, 24 October 2020
Line 219:		Line 219:


−	[[File:Dsmact1.PNG\|~~600px~~]]	+	[[File:Dsmact1.PNG\|1000px]]

	Data Registration information can be broken down in different ways, the upper table contains the high level breakdown, and the lower table shows the Data Registrations, this is shown in the above image.		Data Registration information can be broken down in different ways, the upper table contains the high level breakdown, and the lower table shows the Data Registrations, this is shown in the above image.

← Older revision		Revision as of 18:11, 24 October 2020
Line 204:		Line 204:


−	[[File:DsmfigExt14.PNG\|600px]]	+	[[File:DsmfigExt14.PNG\|600px]]<br>
		+
	''Figure 5 showing the mapping workflow from data query to data response where the Population Dataflow is linked to a mapped store, the target dataflow for the mapped store (defined by the associated structure map) is FAME_POP which itself links to a relational database. The client remains agnostic to the mapping, and can retrieve the data in any Fusion Registry supported data format.''		''Figure 5 showing the mapping workflow from data query to data response where the Population Dataflow is linked to a mapped store, the target dataflow for the mapped store (defined by the associated structure map) is FAME_POP which itself links to a relational database. The client remains agnostic to the mapping, and can retrieve the data in any Fusion Registry supported data format.''

@@ Line 70: / Line 70: @@
 The table name must be in upper case, and any ‘.’ or ‘-’ characters must be replaced with the underscore character ‘_’.  For example:
 [[File:DsmfigExt1.PNG|600px]]
@@ Line 76: / Line 75: @@
 '''Table Structure'''
 The database table or view must contain a column for each of the Components of the Data Structure Definition that the Dataflow conforms to.  For time series data, an additional column with the name FR_OBS_DATE must be providing containing the date and time of the observation. For MySQL the column type should be “datetime”, for Oracle: “timestamp”.
 [[File:DsmfigExt2.PNG|600px]]
 The FR_OBS_DATE column is used when performing data queries which have start and end date restrictions. However, the value in the TIME_PERIOD column must represent the same date, formatted according to the frequency of the series.  The following table shows an example of the observation frequency vs the expected date format.
 [[File:DsmfigExt3.PNG|600px]]

@@ Line 112: / Line 112: @@
 The following example shows the table Series Table columns required for a DSD with 3 dimensions:
 [[File:DsmfigExt6.PNG|600px]]
@@ Line 122: / Line 121: @@
 The table name must be in upper case, and any ‘.’ or ‘-’ characters must be replaced with the underscore character ‘_’.  For example:
 [[File:DsmfigExt7.PNG|600px]]
@@ Line 131: / Line 129: @@
 The table must have the following structure:
 [[File:DsmfigExt8.PNG|600px]]

@@ Line 87: / Line 87: @@
 =====“Registry” External mode=====
 In “Registry” External mode, the data must be presented in a normalised schema consisting of two tables or views in a one-to-many relationship.
 [[File:DsmfigExt4.PNG|600px]]
@@ Line 100: / Line 99: @@
 For example:
 [[File:DsmfigExt5.PNG|600px]]

← Older revision		Revision as of 18:08, 24 October 2020
Line 236:		Line 236:

	===RSS Feed===		===RSS Feed===
−	The Fusion Registry provides a RSS feed which is updated every time a structure or registration event occurs in the Fusion Registry. This includes creation, updates, and deletions. The RSS feed is linked to from the Fusion Registry home page by clicking on the RSS icon: [[File:Rss.~~PNG~~\|~~50px~~]]	+	The Fusion Registry provides a RSS feed which is updated every time a structure or registration event occurs in the Fusion Registry. This includes creation, updates, and deletions. The RSS feed is linked to from the Fusion Registry home page by clicking on the RSS icon: [[File:Rss.png\|20px]]<br>