Skip to Content
Last modified by Artur K. on 2026/05/29 14:29
From version 1.3
edited by Helena K.
on 2026/01/15 16:38
Change comment: There is no comment for this version
To version 1.1
edited by Helena K.
on 2026/01/15 16:35
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 -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
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
141 141  
142 142  Later work could be considered for further efficiency gains:
143 143  
... ... @@ -179,12 +179,13 @@
179 179  1. (in an MSD) the associated SDMX artefact type, e.g. Dataset; Dataflow; Provision agreement;
180 180  1. the associated “level” within the artefact, e.g. for a Dataset: Dataset; Series; Observation.
181 181  
182 +
183 +
182 182  These are some example attachments, others are possible:
183 183  
184 -* the “Contact” concept may be attached to a Dataset artefact at the Dataset level;
185 -* the “Adjustment” concept may be attached to a Dataset artefact at the Series level;
186 -* the “Statistical population” concept may be attached to a Codelist artefact.
186 + the “Contact” concept may be attached to a Dataset artefact at the Dataset level;  the “Adjustment” concept may be attached to a Dataset artefact at the Series level;  the “Statistical population” concept may be attached to a Codelist artefact.
187 187  
188 +
188 188  This version of the proposal does not include an attachment recommendation for each concept. Recommended attachments may be provided in a future version of this guideline based on the feedback and forthcoming implementations. If you have any questions on how to attach reference metadata, please contact the SDMX Statistical Working Group (swg@sdmx.org).
189 189  
190 190  == List of Reference Metadata Concepts ==
... ... @@ -225,7 +225,7 @@
225 225  
226 226  //Example usage: if an organisation receives data from a member agency and publishes it, the “Contact organisation” concept would usually be the publishing organisation.//
227 227  )))|CONTACT_ORGANISATION
228 -|**Contact organisation unit**|Addressable subdivision of an organisation.|ORGANISATION_UNIT
229 +|**Contact organisation unit**|Addressable subdivision of an organisation.|ORGANISATION_UNIT
229 229  |**Contact person function**|(((
230 230  Area of technical responsibility of the contact, such as “methodology”, “database management” or
231 231  
... ... @@ -233,6 +233,8 @@
233 233  )))|CONTACT_FUNCT
234 234  |**Contact phone number**|Telephone number of the contact points for the data or metadata.|CONTACT_PHONE
235 235  
237 +
238 +
236 236  === LEGAL AND INSTITUTIONAL ENVIRONMENT ===
237 237  
238 238  |**Name**|**Definition**|**Concept ID**
... ... @@ -245,13 +245,16 @@
245 245  * //or the granular “Institutional mandate xxx” concepts but not the “Institutional mandate” concept.//
246 246  )))|INST_MANDATE
247 247  |**Institutional mandate – data sharing**|Arrangements or procedures for data sharing and coordination between data producing agencies.|INST_MAN_SHAR
248 -|**Institutional mandate – legal acts and other agreements**|Legal acts or other formal or informal agreements that assign responsibility as well as the authority to an Agency for the collection, processing, and dissemination of statistics.|INST_MAN_LA_OA
251 +|**Institutional mandate - legal acts and other agreements**|Legal acts or other formal or informal agreements that assign responsibility as well as the authority to an Agency for the collection, processing, and dissemination of statistics.|INST_MAN_LA_OA
249 249  |**Confidentiality**|(((
250 250  Property of data indicating whether they are subject to dissemination restrictions.
251 251  
252 252  //Recommended usage. Use~://
253 253  
254 -* //either the summary “Confidentiality” concept but not the granular “Confidentiality xxx” concepts,//
257 +* //either the summary “Confidentiality” concept but not the granular//
258 +
259 +//“Confidentiality xxx” concepts,//
260 +
255 255  * //or the granular “Confidentiality xxx” concepts but not the “Confidentiality” concept.//
256 256  )))|CONF
257 257  |**Confidentiality - data treatment**|Rules applied for treating the Data Set to ensure that private information from individual units cannot be accessed and to prevent unauthorised disclosure.|CONF_DATA_TR
© Semantic R&D Group, 2026