Difference between revisions of "Organisations - Agency Schemes"

From Fusion Registry Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
[[Category:Structural Metadata]]
 
[[Category:Structural Metadata]]
== Overview ==
+
=Overview=
Organisations are used to define ownership of structures or data, allow users to report data, and in the case of a private Fusion Registry Organisations provide users with the ability to access Registry content to view.
+
An Agency is responsible for owning structures in the Fusion Registry.  Each structure in the Fusion Metadata Registry must be owned by an Agency.
Organisations include:
 
  
'''Agencies:''' An Agency is responsible for owning structures in the Fusion Registry.  Each structure in the Fusion Registry must be owned by an Agency.
+
Agencies are stored in an Agency scheme. The default scheme is SDMX.
  
'''Data Providers''': A Data Provider is responsible for loading data or registering the URL of where data can be obtained.
+
=Wizard=
  
'''Data Consumers:''' A Data Consumer can log into the Fusion Registry, however they have no special access beyond being able to use the user interface.  When a Fusion Registry is running in public mode, a Data Consumer has no extra privileges.  When a Fusion Registry is running in private mode, access is restricted to authenticated users only. In this condition, a Data Consumer will have access to browsing the content of the Fusion Registry via the Web Service only.
+
From the Organisations menu, select the Agency Page and use the maintenance button to create an Agency. [[File :cogs.PNG|40px]]<br>
  
== Organisation Wizard ==
+
==Step 1 - High Level Details==
  
The Organisation Wizard contains 2 steps.  Step 1 is the general details step. Step 2 allows for the provision of information about Contacts.
+
The steps in the Agency Wizard includes step 1 which provides the generic, high level details about the Agency. See this article [https://fmrwiki.sdmxcloud.org/All_Structures for more information on authoring and maintaining structures.]
  
 +
[[File:agency-wiz1.PNG|Step 1|500px]]<br>
  
[[File:Org_Fig_1.jpg|frameless|500px]]
+
==Step 2 - Contacts==
  
<small>''Figure 1 showing the creation of a Contact within an Organisation''</small>
+
Allows for the provision of information about Contacts.
 +
 
 +
[[File:agency-wiz2.PNG|Step 2|800px]]<br>
 +
 
 +
=Sub-Agencies=
 +
 
 +
It is also possible to have Sub Agencies which are owned by a parent agency.<br>
 +
 
 +
To create a sub agency, on the create step, ensure that you select the correct owning agency from the drop down list. Tip: Remember you can set the default agency on the Settings - General page which is in the Administration area of the Registry, available to System Administrators.
 +
 
 +
Creating a sub agency will (behind the scenes) create a new Agency Scheme for the Parent Agency. You can see the effect of this in the user interface in:
 +
 
 +
==The Agency List==
 +
 
 +
 
 +
[[File:agency-list.PNG|Agency Page|800px]]<br>
 +
 
 +
==Bulk Actions/Export Structures Page==
 +
 
 +
 
 +
[[File:bulkactions1.PNG|Bulk Export|800px]]<br>

Revision as of 10:25, 13 September 2023

Overview

An Agency is responsible for owning structures in the Fusion Registry. Each structure in the Fusion Metadata Registry must be owned by an Agency.

Agencies are stored in an Agency scheme. The default scheme is SDMX.

Wizard

From the Organisations menu, select the Agency Page and use the maintenance button to create an Agency. Cogs.PNG

Step 1 - High Level Details

The steps in the Agency Wizard includes step 1 which provides the generic, high level details about the Agency. See this article for more information on authoring and maintaining structures.

Step 1

Step 2 - Contacts

Allows for the provision of information about Contacts.

Step 2

Sub-Agencies

It is also possible to have Sub Agencies which are owned by a parent agency.

To create a sub agency, on the create step, ensure that you select the correct owning agency from the drop down list. Tip: Remember you can set the default agency on the Settings - General page which is in the Administration area of the Registry, available to System Administrators.

Creating a sub agency will (behind the scenes) create a new Agency Scheme for the Parent Agency. You can see the effect of this in the user interface in:

The Agency List

Agency Page

Bulk Actions/Export Structures Page

Bulk Export