Data Registration - Revision history

Vmurrell at 10:16, 12 November 2025

2025-11-12T10:16:45Z

Vmurrell at 11:35, 3 November 2025

2025-11-03T11:35:47Z

Vmurrell at 14:54, 4 September 2023

2023-09-04T14:54:49Z

Mnelson: /* Overview */

2020-02-20T17:09:28Z

‎Overview

Mnelson: /* Overview */

2020-02-20T17:08:52Z

‎Overview

Mnelson at 11:35, 20 February 2020

2020-02-20T11:35:44Z

Mnelson: /* Alternative web Service */

2020-02-20T11:34:26Z

‎Alternative web Service

Mnelson: /* Example Document */

2020-02-20T11:33:15Z

‎Example Document

Mnelson: /* Example Document */

2020-02-20T11:33:08Z

‎Example Document

Mnelson: Created page with "= Overview =
A Data Registration tells the Fusion Registry that data exists for a Provision Agreement. Data Registrations are automatically managed by the Fusion Registry..."

2020-02-20T11:32:08Z

Created page with "= Overview = A Data Registration tells the Fusion Registry that data exists for a Provision Agreement. Data Registrations are automatically managed by the Fusion Registry..."

New page

= Overview =
A Data Registration tells the Fusion Registry that data exists for a Provision Agreement. Data Registrations are automatically managed by the Fusion Registry for data stores which are managed by the Fusion Registry (Fusion Store and Registry Managed Databases). For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration. For externally managed databases, the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.

== Re-Registering Data ==
=== User Interface ===
For registry managed, and external databases and Admin user can re-register data from the admin -> datasources page. For URLs and files data can be re-registered from the home page.

=== SDMX web Service ===
Data can be re-registered by submitting a SDMX Data Registration request to the following service.
{| class="wikitable"
|-
|style="background-color:#eaecf0"|Entry Point|| /ws/secure/sdmxapi/rest
|-
|style="background-color:#eaecf0"|Access|| Private (admin/agency/data provider for the Provision Agreement)
|-
|style="background-color:#eaecf0"|Http Method|| POST
|-
|style="background-color:#eaecf0"|Accepts|| SDXM-ML Submit Registration Request
|-
|style="background-color:#eaecf0"|Compression || gzip
|-
|style="background-color:#eaecf0"|Content-Type || xml
|-
|style="background-color:#eaecf0"|Response Format|| xml
|-
|style="background-color:#eaecf0"|Response Statuses|| 200 - registration success 
400 - Bad URN syntax
401 - Unauthorized (if access has been restricted)
403 - No results (no data)
500 - Server Error
|}

==== Example Document ====
<?xml version="1.0" encoding="UTF-8"?>
<mes:RegistryInterface xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:mes="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/message" xmlns:reg="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/registry" xmlns:com="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/common" xsi:schemaLocation="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/message https://registry.sdmx.org/schemas/v2_1/SDMXMessage.xsd">
<mes:Header>
<mes:ID>IREF981386</mes:ID>
<mes:Test>false</mes:Test>
<mes:Prepared>2020-02-20T11:28:51Z</mes:Prepared>
<mes:Sender id="S1"/>
<mes:Receiver id="not_supplied"/>
</mes:Header>
<mes:SubmitRegistrationsRequest>
<reg:RegistrationRequest action="Replace">
<reg:Registration lastUpdated="2019-03-21T12:58:17" indexReportingPeriod="false" indexDataSet="false" indexAttributes="false" id="1167332d21d37d8589879ce5ff7d35ee" indexTimeSeries="false">
<reg:ProvisionAgreement>
<Ref package="registry" agencyID="MY_ACY" id="PROV_ID" version="1.0" class="ProvisionAgreement"/>
</reg:ProvisionAgreement>
<reg:Datasource>
<reg:SimpleDataSource>http://myserver.org/MYDATA.xml</reg:SimpleDataSource>
</reg:Datasource>
</reg:Registration>
</reg:RegistrationRequest>
</mes:SubmitRegistrationsRequest>
</mes:RegistryInterface>

=== Alternative web Service ===
An alternative, and simpler mechanism is via this web service
{| class="wikitable"
|-
|style="background-color:#eaecf0"|Entry Point|| /ws/registry/registration/reRegisterService
|-
|style="background-color:#eaecf0"|Access|| Private (admin/agency/data provider for the Provision Agreement)
|-
|style="background-color:#eaecf0"|Http Method|| POST
|-
|style="background-color:#eaecf0"|Accepts|| application/json
|-
|style="background-color:#eaecf0"|Compression || N/A
|-
|style="background-color:#eaecf0"|Content-Type|| N/A
|-
|style="background-color:#eaecf0"|Response Format|| application/json
|-
|style="background-color:#eaecf0"|Response Statuses|| 200 - registration success 
400 - Bad URN syntax
401 - Unauthorized (if access has been restricted)
403 - No results (no data)
500 - Server Error
|}

@@ Line 1: / Line 1: @@
 [[Category:WebService]]
 = Overview =
 <p>A Data Registration tells the Fusion Registry that data exists for a Provision Agreement.  Data Registrations are automatically managed by the Fusion Registry for [[Registry_Data_Stores#Registry_Managed_Data_Store|data stores which are managed by the Fusion Registry]] (Fusion Store and Registry Managed Databases).  For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration.  For [[Registry_Data_Stores#Externally_Managed_Database|externally managed databases]], the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.</p>

← Older revision		Revision as of 11:35, 3 November 2025
Line 1:		Line 1:
−	~~[[Category:Functions]]~~
	[[Category:WebService]]		[[Category:WebService]]
	[[Category:How_To]]		[[Category:How_To]]

← Older revision		Revision as of 14:54, 4 September 2023
Line 1:		Line 1:
	[[Category:Functions]]		[[Category:Functions]]
		+	[[Category:WebService]]
		+	[[Category:How_To]]

	= Overview =		= Overview =

@@ Line 2: / Line 2: @@
 = Overview =
-<p>A Data Registration tells the Fusion Registry that data exists for a Provision Agreement.  Data Registrations are automatically managed by the Fusion Registry for [[Registry_Data_Stores#Registry_Managed_Data_Store|data stores which are managed by the Fusion Registry]] (Fusion Store and Registry Managed Databases).  For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration.  For externally managed databases, the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.</p>
+<p>A Data Registration tells the Fusion Registry that data exists for a Provision Agreement.  Data Registrations are automatically managed by the Fusion Registry for [[Registry_Data_Stores#Registry_Managed_Data_Store|data stores which are managed by the Fusion Registry]] (Fusion Store and Registry Managed Databases).  For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration.  For [[Registry_Data_Stores#Externally_Managed_Database|externally managed databases]], the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.</p>
 == Re-Registering Data ==

@@ Line 2: / Line 2: @@
 = Overview =
-<p>A Data Registration tells the Fusion Registry that data exists for a Provision Agreement.  Data Registrations are automatically managed by the Fusion Registry for data stores which are managed by the Fusion Registry (Fusion Store and Registry Managed Databases).  For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration.  For externally managed databases, the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.</p>
+<p>A Data Registration tells the Fusion Registry that data exists for a Provision Agreement.  Data Registrations are automatically managed by the Fusion Registry for [[Registry_Data_Stores#Registry_Managed_Data_Store|data stores which are managed by the Fusion Registry]] (Fusion Store and Registry Managed Databases).  For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration.  For externally managed databases, the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.</p>
 == Re-Registering Data ==

← Older revision		Revision as of 11:35, 20 February 2020
Line 1:		Line 1:
		+	[[Category:Functions]]
		+
	= Overview =		= Overview =
	<p>A Data Registration tells the Fusion Registry that data exists for a Provision Agreement. Data Registrations are automatically managed by the Fusion Registry for data stores which are managed by the Fusion Registry (Fusion Store and Registry Managed Databases). For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration. For externally managed databases, the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.</p>		<p>A Data Registration tells the Fusion Registry that data exists for a Provision Agreement. Data Registrations are automatically managed by the Fusion Registry for data stores which are managed by the Fusion Registry (Fusion Store and Registry Managed Databases). For data stores which are accessed via a URL (Registered SDMX web services, Files) the Fusion Reigstry must be told where those URLs are via a Data Registration. For externally managed databases, the Fusion Registry will automaitcally create a data registration when the data store is initially linked to, when the data changes in the database, the Fusion Registry must be told to update it's caches via a re-registration request.</p>

← Older revision		Revision as of 11:34, 20 February 2020
Line 79:		Line 79:
	<p><b>500</b> - Server Error</p>		<p><b>500</b> - Server Error</p>
	\|}		\|}
		+
		+	The POST should include the URN of the Provision Agreement to re-register data for, in the body of the message.

@@ Line 32: / Line 32: @@
 ==== Example Document ====
-<?xml version="1.0" encoding="UTF-8"?>
+ <?xml version="1.0" encoding="UTF-8"?>
   <mes:RegistryInterface xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:mes="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/message" xmlns:reg="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/registry" xmlns:com="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/common" xsi:schemaLocation="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/message https://registry.sdmx.org/schemas/v2_1/SDMXMessage.xsd">
    <mes:Header>

@@ Line 34: / Line 34: @@
 <?xml version="1.0" encoding="UTF-8"?>
   <mes:RegistryInterface xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:mes="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/message" xmlns:reg="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/registry" xmlns:com="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/common" xsi:schemaLocation="http://www.sdmx.org/resources/sdmxml/schemas/v2_1/message https://registry.sdmx.org/schemas/v2_1/SDMXMessage.xsd">
-	<mes:Header>
+  <mes:Header>
-		<mes:ID>IREF981386</mes:ID>
+    <mes:ID>IREF981386</mes:ID>
-		<mes:Test>false</mes:Test>
+    <mes:Test>false</mes:Test>
-		<mes:Prepared>2020-02-20T11:28:51Z</mes:Prepared>
+    <mes:Prepared>2020-02-20T11:28:51Z</mes:Prepared>
-		<mes:Sender id="S1"/>
+    <mes:Sender id="S1"/>
-		<mes:Receiver id="not_supplied"/>
+    <mes:Receiver id="not_supplied"/>
-	</mes:Header>
+  </mes:Header>
-	<mes:SubmitRegistrationsRequest>
+    <mes:SubmitRegistrationsRequest>
-		<reg:RegistrationRequest action="Replace">
+      <reg:RegistrationRequest action="Replace">
-			<reg:Registration lastUpdated="2019-03-21T12:58:17" indexReportingPeriod="false" indexDataSet="false" indexAttributes="false" id="1167332d21d37d8589879ce5ff7d35ee" indexTimeSeries="false">
+        <reg:Registration lastUpdated="2019-03-21T12:58:17" indexReportingPeriod="false" indexDataSet="false" indexAttributes="false" id="1167332d21d37d8589879ce5ff7d35ee" indexTimeSeries="false">
-				<reg:ProvisionAgreement>
+          <reg:ProvisionAgreement>
-					<Ref package="registry" agencyID="MY_ACY" id="PROV_ID" version="1.0" class="ProvisionAgreement"/>
+            <Ref package="registry" agencyID="MY_ACY" id="PROV_ID" version="1.0" class="ProvisionAgreement"/>
-				</reg:ProvisionAgreement>
+          </reg:ProvisionAgreement>
-				<reg:Datasource>
+          <reg:Datasource>
-					<reg:SimpleDataSource>http://myserver.org/MYDATA.xml</reg:SimpleDataSource>
+            <reg:SimpleDataSource>http://myserver.org/MYDATA.xml</reg:SimpleDataSource>
-				</reg:Datasource>
+          </reg:Datasource>
-			</reg:Registration>
+        </reg:Registration>
-		</reg:RegistrationRequest>
+      </reg:RegistrationRequest>
-	</mes:SubmitRegistrationsRequest>
+    </mes:SubmitRegistrationsRequest>
   </mes:RegistryInterface>
 === Alternative web Service ===

Data Registration - Revision history

Vmurrell at 10:16, 12 November 2025

Vmurrell at 11:35, 3 November 2025

Vmurrell at 14:54, 4 September 2023

Mnelson: /* Overview */

Mnelson: /* Overview */

Mnelson at 11:35, 20 February 2020

Mnelson: /* Alternative web Service */

Mnelson: /* Example Document */

Mnelson: /* Example Document */

Mnelson: Created page with "= Overview = A Data Registration tells the Fusion Registry that data exists for a Provision Agreement. Data Registrations are automatically managed by the Fusion Registry..."

Mnelson: Created page with "= Overview =
A Data Registration tells the Fusion Registry that data exists for a Provision Agreement. Data Registrations are automatically managed by the Fusion Registry..."