Structure Maps
| Structure Map Details | |
|---|---|
| URN | |
| URL | |
| Revisions | |
| Description | |
| Annotations | |
| Valid From | |
| Valid To | |
| Id | Name | Latest Version |
|---|
| Structure Map Details | |
|---|---|
| URN | |
| URL | |
| Revisions | |
| Description | |
| Annotations | |
| Valid From | |
| Valid To | |
| Structure Type | Structure Id | Annotation Id | Annotation Type | Annotation Title | Annotation Text | Annotation URI |
|---|
| Detail | |
|---|---|
| Structure Id | |
| Annotation Id | |
| Annotation Type | |
| Annotation Title | |
| Annotation Text | |
| Annotation URI | |
| Source | |
|---|---|
| Target |
| Source | Target | Mapping Rules |
|---|
To test the Structure Map, please load a SDMX data set which references either the source or target data structure.
The Fusion Metadata Registry will then produce a report listing each input row of data, with the corresponding output row
Further details about the mapping can then be obtained for any row of data
| Status | Source Row | Target Row |
|---|
The following table shows the row of data used as an input to the mapping
| Component Id | Component Value |
|---|
The following table shows the row of data that was input from the mapping
| Component Id | Component Value |
|---|
The following table shows the breakdown of all the mappings used to derive the output. The bold values indicate the final value that was output, this is either because it was the only output for that component, or it was the result of taking the intersection from all the mappings that were used to create an output for the target component
| Source Component(s) | Output | |||
|---|---|---|---|---|
| Period | Component | Value | ||
The following table shows the rule(s) that were used for the selected Component Mapping in the above table
| Component | Rule | Input | Match | Capture Group | Substring Start | Substring End |
|---|---|---|---|---|---|---|
| REF_AREA | REF_AREA | REF_AREA | REF_AREA | REF_AREA | REF_AREA | UK |
This user guide aims to help IMF member countries to manually create and maintain the machine-readable (SDMX) component of their National Summary Data Page (NSDP) using SDMX Central, a cloud-based tool. SDMX Central provides member countries the ability to convert data in Excel into SDMX format using an easy-to-follow Graphical User Interface.
The IMF SDMX Central offers web services for querying structures e.g. (Dataflows, Codelists, Concepts, Data Structures) and data. These services enable seamless integration with external software that can communicate with the SDMX web services, facilitating efficient data exchange and management. The web service conforms to the SDMX Web Service Guidelines which can be found at https://sdmx.org. The Guide assumes familiarity with the installation and use of Python code and Bash commands.
| GUID | Item | Id | Property | Master Value | Target Value | Action |
|---|
| Difference Details | |
|---|---|
| Master value | |
| Target value | |
| Master Annotation |
|---|
| Target Annotation |
|---|
| Agency | Id | Name | Version | State |
|---|
You have changed the items:
Do you wish to create a new structure or update the existing structure to have these values?
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:
| Type | Agency | Id | Version |
|---|