Fusion Metadata RegistryVersion 11.14.1
Generate Excel Report Form
Allowable content may be free text, restricted by type, length, text patterns, and more. Allowable content may also be defined as an enumeration of allowable values, which will be defined in a separate structure known as a Codelist.
- out - The mapped output in the format of your choice.
- unmapped - The unmapped output in the same format as the mapped file.
- metrics.json - A JSON report stating the number of Series and Observations in both the mapped and unmapped files as well as a breakdown of why the elements were unmapped.
If a row of data is mapped successfully it can be subject to Data Validation. This will ensure that certain business rules are applied to the mapped data.
For example if the target structure has a FREQ dimension, the TIME_PERIOD must conform to that value. So a 4 digit-year must have a FREQ value of 'A'.
If you do not want validation to be perfomed, please ensure this setting is set so that "Invalid Data is Included in the Mapped Dataset".
Constraints can be applied to a Data Structure, Dataflow, Data Provider, or Provision Agreement. The rules of a constraint will cascade, so if a Constraint which restricts valid frequencies to Monthly or Annual is applied to a Dataflow, and another restricting valid countries to France is applied to a Data Provider, then the resultant restriction for the data provider loading data for the dataflow is "Monthly or Annual data for France".
Series ConstraintSelecting a Series Constraint will create a restriction based on all the series in the validated dataset.
Code ConstraintSelecting a Code Constraint will create a restriction based on all the unique code ids in the validated dataset.
A recommended naming convention is to use the text "CONS_" followed by either "KEY" or "CODE" depending on the constraint type, followed by the id of the structure that is being constrained. For example if the id of the constrained structure is "DF_GDP", the constraint id could be either "CONS_KEY_DF_GDP" or "CONS_CODE_DF_GDP"
Note that 'Overwrite Existing' will not overwrite an existing constraint against a constraint of a different type.
Constraint generated successfully. Details are:
Fusion Metadata Registry
Warning! You are submitting a file with extension "", but have selected the data format of "".
- Data Providers
- Dataset Attributes
- Series Attributes
- Observation Attributes
- Group Attributes
Select Item to Compare
Please click Confirm to complete your action
Important Structure Modification
You have changed the items:
Do you wish to create a new structure or update the existing structure to have these values?
Structure Already Exists
The structure you have specified already exists in the Registry.
If you wish you can edit this existing structure.
Alternatively you must change any of the values: Id, Agency Id or Version so there is no match with an existing structure in the Registry.
An email has been sent to: