Last modified by Artur K. on 2026/05/29 14:29

From version 1.1
edited by Helena K.
on 2026/01/15 16:35
Change comment: There is no comment for this version
To version 1.2
edited by Helena K.
on 2026/01/15 16:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -134,10 +134,10 @@
134 134  
135 135  1. Create a mapping between the agency's existing metadata concepts and the Global MCS, or MSD derived from it. This mapping is an SDMX Structure Set (which is used to map concepts and codes in different structures) and is stored and shared in the agency's SDMX registry;
136 136  1. create or adopt a system component that acts as a proxy to the existing agency's metadata component. The component does the following:
137 -11. takes input from the agency's metadata component (the agency's metadata XML);
138 -11. **transforms** the input XML to SDMX (the agency's metadata framework);
139 -11. **transcodes** the SDMX by applying the mapping created in step 1. The result is an SDMX metadata message that matches the Global MCS, or MSD;
140 -11. outputs the resulting SDMX with an SDMX web service
137 +1*. a. takes input from the agency's metadata component (the agency's metadata XML);
138 +1*. b. **transforms** the input XML to SDMX (the agency's metadata framework);
139 +1*. c. **transcodes** the SDMX by applying the mapping created in step 1. The result is an SDMX metadata message that matches the Global MCS, or MSD;
140 +1*. d. outputs the resulting SDMX with an SDMX web service
141 141  
142 142  Later work could be considered for further efficiency gains:
143 143  
© Semantic R&D Group, 2026