Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 6.1
edited by Artur
on 2025/07/14 10:19
Change comment: Imported from XAR
To version 5.1
edited by Artur
on 2025/05/27 15:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,1 +1,0 @@
1 -Attribute|Attribute relationship|Category|Code|Code list|Component|Concept|Content-Oriented Guidelines|Currency|Data provider|Data set|Data source|Data structure definition|Dataflow|Dimension|Dissemination format|Hierarchy|Hub (dissemination architecture)|Imputation|Metadata set|Quality management - quality assurance|Representation|SDMX Registry|SDMX-EDI|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Version
Content
... ... @@ -10,7 +10,7 @@
10 10  
11 11  This example is not a technical one – rather, it is meant to describe the use of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] from a business perspective: how, where, and why is [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] used? These questions will be answered by using the example of effective exchange rates..
12 12  
13 -It is important to note that in some scenarios, where collected data is already in the form of aggregates, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] might be used earlier in the business process. However, for NSOs the most common scenario is probably where micro-data are collected and aggregated at the national level.
13 +It is important to note that in some scenarios, where collected data is already in the form of aggregates, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] might be used earlier in the business process. However, for NSOs the most common scenario is probably where micro-data are collected and aggregated at the national (% style="color:#e74c3c" %)level(%%).
14 14  
15 15  There are many benefits to the use of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], and while many of these are related to the use of technology, in the end the real benefits are simple: it becomes easier for users to locate and utilize data, and the data themselves are more comparable. Further, the data become easier to visualize and format, into whatever form is needed, either for the creation of dissemination outputs, or for re-formatting by data users or collectors.
16 16  
... ... @@ -23,7 +23,7 @@
23 23  (% style="text-align: center;" %)
24 24  **{{id name="image_35"/}}Figure 35: Hush-level schematic of the GSBPM**
25 25  
26 -Across the top of the diagram, we see the high-level process steps, from 1 to 9. The process begins with the evaluation of data collection needs, and proceeds through the design and creation of data-collection instruments, and then moves on to the actual collection of data. Once collected, data are processed, coded, edited, [[imputation>>doc:sdmx:Glossary.Imputation.WebHome]] is performed, weights are calculated, and the data are aggregated.
26 +Across the top of the diagram, we see the high-(% style="color:#e74c3c" %)level(%%) process steps, from 1 to 9. The process begins with the evaluation of data collection needs, and proceeds through the design and creation of data-collection instruments, and then moves on to the actual collection of data. Once collected, data are processed, coded, edited, [[imputation>>doc:sdmx:Glossary.Imputation.WebHome]] is performed, weights are calculated, and the data are aggregated.
27 27  
28 28  Up to this point (i.e. 5.6), the GSBPM has been concerned with the collection and processing of micro-data (at least from the perspective of an NSO – from the perspective of a supra-national organization, the collected data may themselves often be aggregates.)
29 29  
... ... @@ -48,7 +48,7 @@
48 48  
49 49  Once data have been aggregated from the micro-data (Step 5.7 of the GSBPM) they will be stored in some format such as a relational database or data warehouse (Oracle, etc.) or in some processing format (SAS, SPSS), or in Excel spreadsheets or similar format. This will depend on the internal system and tools used within the organization, and is different in different organizations.
50 50  
51 -In order to capture the aggregates in a standard [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] format, we must first look at the required data structures as dictated by the collecting agency. In our example, we will use the Effective Exchange Rates data structure developed by the ECB^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^4^^>>path:#sdfootnote4sym||name="sdfootnote4anc"]](%%)^^. Below is an example of the type of data which is contained in a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] structured according to this [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
51 +In order to capture the aggregates in a standard [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] format, we must first look at the required data structures as dictated by the collecting agency. In our example, we will use the Effective Exchange Rates data structure developed by the ECB^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^4^^>>path:#sdfootnote4sym||name="sdfootnote4anc"]](%%)^^. Below is an example of the type of data which is contained in a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] structured according to this [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
52 52  
53 53  [[image:SDMX_2-1_User_Guide_draft_0-1_html_e5d197f835ebb755.jpg||data-xwiki-image-style-alignment="center" height="529" width="575"]]
54 54  
... ... @@ -59,7 +59,7 @@
59 59  
60 60  It is important to understand the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], because this is the resource which describes how the reported aggregates themselves must be structured. Below is view of the Effective Exchange Rates [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
61 61  
62 -The [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] is an XML file, created according to the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] standard (it can also be expressed in [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]], but the XML version is more common). The fact that is XML is important to the IT staff who must process it, and is used by many [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] tools, but what is most important is that the statistical (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and codelists (or “classifications”) it uses are also used in the reported aggregate data file. Thus, we do not look at the XML for this example – it is enough to know that the XML version of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] exists, and may be needed by tools or developers at some point.
62 +The [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] is an XML file, created according to the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] standard (it can also be expressed in [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]], but the XML (% style="color:#e74c3c" %)version(%%) is more common). The fact that is XML is important to the IT staff who must process it, and is used by many [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] tools, but what is most important is that the statistical (% style="color:#e74c3c" %)concepts(%%) and codelists (or “classifications”) it uses are also used in the reported aggregate data file. Thus, we do not look at the XML for this example – it is enough to know that the XML (% style="color:#e74c3c" %)version(%%) of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] exists, and may be needed by tools or developers at some point.
63 63  
64 64  [[image:SDMX_2-1_User_Guide_draft_0-1_html_bd8d57aa9f34e7ce.jpg||data-xwiki-image-style-alignment="center" height="227" width="575"]]
65 65  
... ... @@ -73,24 +73,22 @@
73 73  
74 74  The view here shows a number of very important things:
75 75  
76 -The ID, Agency, and [[version>>doc:Glossary.Version.WebHome]] of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] are displayed at the top of the screen. Below this, there is a listing of statistical (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) which are used as [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]. (Frequency, [[Currency>>doc:sdmx:Glossary.Currency.WebHome]], Exchange Rate Type, etc.) Each of these (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) will be taken from some authoritative source, and descriptions and definitions can be obtained from the organization which publishes and maintains the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. In many cases, these (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) will be the standard (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) defined in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Cross-Domain Statistical (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) document (which can be obtained at [[__www.__>>https://xwiki:www.sdmx.org]][[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].org). In other cases, they may be formally defined and documented by the maintaining agency which publishes the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. It is important to understand the definition of these (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), as they may be slightly different from those used by the NSO or Central Bank, but in most cases they will likely be very similar or the same as the (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) already used at the national level for this data.
76 +The ID, Agency, and (% style="color:#e74c3c" %)version(%%) of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] are displayed at the top of the screen. Below this, there is a listing of statistical (% style="color:#e74c3c" %)concepts(%%) which are used as [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]. (Frequency, [[Currency>>doc:sdmx:Glossary.Currency.WebHome]], Exchange Rate Type, etc.) Each of these (% style="color:#e74c3c" %)concepts(%%) will be taken from some authoritative source, and descriptions and definitions can be obtained from the organization which publishes and maintains the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. In many cases, these (% style="color:#e74c3c" %)concepts(%%) will be the standard (% style="color:#e74c3c" %)concepts(%%) defined in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Cross-Domain Statistical (% style="color:#e74c3c" %)Concepts(%%) document (which can be obtained at [[__www.__sdmx.org>>https://xwiki:www.sdmx.org]]). In other cases, they may be formally defined and documented by the maintaining agency which publishes the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. It is important to understand the definition of these (% style="color:#e74c3c" %)concepts(%%), as they may be slightly different from those used by the NSO or Central Bank, but in most cases they will likely be very similar or the same as the (% style="color:#e74c3c" %)concepts(%%) already used at the national (% style="color:#e74c3c" %)level(%%) for this data.
77 77  
78 -The (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) used as [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] each take a value which has a standard [[representation>>doc:sdmx:Glossary.Representation.WebHome]]. In most cases, this [[representation>>doc:sdmx:Glossary.Representation.WebHome]] will be a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] – a standard classification which must be used to identify and describe the observations. In the righthand part of the screen, we can see which [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] is used to represent each (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) used as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. For example, the Frequency [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] uses a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] called “CL_FREQ” version 1.0:
78 +The (% style="color:#e74c3c" %)concepts(%%) used as [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] each take a value which has a standard [[representation>>doc:sdmx:Glossary.Representation.WebHome]]. In most cases, this [[representation>>doc:sdmx:Glossary.Representation.WebHome]] will be a codelist – a standard classification which must be used to identify and describe the observations. In the righthand part of the screen, we can see which codelist is used to represent each (% style="color:#e74c3c" %)concept(%%) used as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. For example, the Frequency [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] uses a codelist called “CL_FREQ” (% style="color:#e74c3c" %)version(%%) 1.0:
79 79  
80 80  Frequency is perhaps the simplest example, as the reporting agency will generally know what the frequency of the data is, and have a record of this in their systems (quarterly, monthly, etc.)
81 81  
82 82  Notice that the Time [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is not coded, but instead has a time value, indicating the time of the observation.
83 83  
84 -The values for the [[codes>>doc:sdmx:Glossary.Code.WebHome]] may or may not match the classification used at the national level, and if they do not match then it will be necessary to map the [[codes>>doc:sdmx:Glossary.Code.WebHome]] used internally against the classification used by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
84 +The values for the [[codes>>doc:sdmx:Glossary.Code.WebHome]] may or may not match the classification used at the national (% style="color:#e74c3c" %)level(%%), and if they do not match then it will be necessary to (% style="color:#e74c3c" %)map(%%) the [[codes>>doc:sdmx:Glossary.Code.WebHome]] used internally against the classification used by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
85 85  
86 -For each statistical (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) used as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]], it must be possible to provide a value as specified by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. This might seem like a lot of work, but it is done for obvious and important reasons – if the collected data are to be comparable at the supranational level, then there must be a standard expression of the data, using the same statistical (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and classifications to identify and describe the observations. This is no different than when reporting aggregate data today – each data collector will want to have a specific expression of the data collected. What is different, with [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], however, is that the data collectors are harmonizing the DSDs used in each domain, and there is an effort, through the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Content-Oriented Guidelines>>doc:sdmx:Glossary.Content-Oriented Guidelines.WebHome]], to use identical statistical (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and [[representations>>doc:sdmx:Glossary.Representation.WebHome]] where this is possible.
86 +For each statistical (% style="color:#e74c3c" %)concept(%%) used as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]], it must be possible to provide a value as specified by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. This might seem like a lot of work, but it is done for obvious and important reasons – if the collected data are to be comparable at the supranational (% style="color:#e74c3c" %)level(%%), then there must be a standard expression of the data, using the same statistical (% style="color:#e74c3c" %)concepts(%%) and classifications to identify and describe the observations. This is no different than when reporting aggregate data today – each data collector will want to have a specific expression of the data collected. What is different, with [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], however, is that the data collectors are harmonizing the DSDs used in each domain, and there is an effort, through the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Content-Oriented Guidelines>>doc:sdmx:Glossary.Content-Oriented Guidelines.WebHome]], to use identical statistical (% style="color:#e74c3c" %)concepts(%%) and [[representations>>doc:sdmx:Glossary.Representation.WebHome]] where this is possible.
87 87  
88 -Harmonization of data is a difficult process, but it is one which will result, in time, in more useful data (because it is more comparable), and also hopefully in a more uniform collection of data at the national level, because all reporting countries must conform to a standard [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] as they calculate aggregates, which in turn impacts the data collection process as shown in the GSBPM.
88 +Harmonization of data is a difficult process, but it is one which will result, in time, in more useful data (because it is more comparable), and also hopefully in a more uniform collection of data at the national (% style="color:#e74c3c" %)level(%%), because all reporting countries must conform to a standard [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] as they calculate aggregates, which in turn impacts the data collection process as shown in the GSBPM.
89 89  
90 -If we look again at the high-level picture of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] (above), we will also see a section which shows statistical
90 +If we look again at the high-(% style="color:#e74c3c" %)level(%%) picture of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] (above), we will also see a section which shows statistical (% style="color:#e74c3c" %)concepts(%%) used as “[[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]”. These are descriptive (% style="color:#e74c3c" %)concepts(%%), sometimes represented with [[codes>>doc:sdmx:Glossary.Code.WebHome]], or sometimes with strings. They are different from Dimensional (% style="color:#e74c3c" %)concepts(%%), because they are not always required – in the table [[image:SDMX_2-1_User_Guide_draft_0-1_html_7b5b4145814c1ed2.jpg||height="25" width="21"]] indicates “Conditional” and [[image:SDMX_2-1_User_Guide_draft_0-1_html_711950811766087b.jpg||height="21" width="23"]] indicates “Mandatory”.
91 91  
92 -(% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) used as “[[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]”. These are descriptive (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), sometimes represented with [[codes>>doc:sdmx:Glossary.Code.WebHome]], or sometimes with strings. They are different from Dimensional (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), because they are not always required – in the table [[image:SDMX_2-1_User_Guide_draft_0-1_html_7b5b4145814c1ed2.jpg||height="25" width="21"]] indicates “Conditional” and [[image:SDMX_2-1_User_Guide_draft_0-1_html_711950811766087b.jpg||height="21" width="23"]] indicates “Mandatory”.
93 -
94 94  An [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] also has a relationship “[[Attribute Relationship>>doc:sdmx:Glossary.Attribute relationship.WebHome]]” to a construct such as a group of [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], which can be one or more [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], Observation etc. as discussed in Chapter 4.
95 95  
96 96  In other ways, the [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are very similar to the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] – the coding (if they are coded) must be standard, as dictated by the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], and for the same reasons.
... ... @@ -99,11 +99,11 @@
99 99  
100 100  Once it has been determined that the aggregate data can be expressed as [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], according to the rules of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], then we need to think about what is involved in actually creating the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] format for the data. This is important because if we can express the aggregates as [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], there are a number of tools which will become useful in performing later activities in the GSBPM.
101 101  
102 -There are several techniques for creating [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], and several choices will need to be made. First, there are several “flavours” of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]: [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] (also known as GESMES/TS) and four types of [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] (the XML version). This is a technical consideration, and it is typically the case that the data collector will dictate exactly which format is wanted. The XML formats include “Generic”, and “Structure Specific”. Different organizations use different flavours of [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], but it is important to note that there are free tools available which will allow for transformations between these different flavours.
100 +There are several techniques for creating [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], and several choices will need to be made. First, there are several “flavours” of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]: [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] (also known as GESMES/TS) and four types of [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] (the XML (% style="color:#e74c3c" %)version(%%)). This is a technical consideration, and it is typically the case that the data collector will dictate exactly which format is wanted. The XML formats include “Generic”, and “Structure Specific”. Different organizations use different flavours of [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], but it is important to note that there are free tools available which will allow for transformations between these different flavours.
103 103  
104 104  These are technical considerations which should be left to the IT staff, so we will not go into them in depth here – the reasons for using one or another are most often purely ITtechnical ones.
105 105  
106 -We do need to look at the practical options for creating the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] files, however. The options are discussed in Chapter 4- Data and Metadata Creation and Reporting and the technical mechanism for achieving different outputs from a database is discussed in Annex 4 – Data Reader and Data Writer Functions. There are several types of tools which will allow the formatting of aggregates into the correct form: tools based on Excel, tools which take the data from a relational database such as Oracle, and tools which work within processing tools such as SAS or PCAxis. Again, we will not look at the technical details of these tools, as this is an IT issue, but it is important to be aware that there are several different tools available. Eurostat provides a free tool for “data mapping” which is broadly useful, and PCAxis will have native [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] support built into it in future versions. It should be noted that when working with processing applications such as SAS and SPSS, it is often the case that dedicated scripts will need to be written within those environments, as different national formats within those applications will require specific formatting scripts to produce [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] outputs.
104 +We do need to look at the practical options for creating the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] files, however. The options are discussed in Chapter 4- Data and Metadata Creation and Reporting and the technical mechanism for achieving different outputs from a database is discussed in Annex 4 – Data Reader and Data Writer Functions. There are several types of tools which will allow the formatting of aggregates into the correct form: tools based on Excel, tools which take the data from a relational database such as Oracle, and tools which work within processing tools such as SAS or PCAxis. Again, we will not look at the technical details of these tools, as this is an IT issue, but it is important to be aware that there are several different tools available. Eurostat provides a free tool for “data mapping” which is broadly useful, and PCAxis will have native [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] support built into it in future (% style="color:#e74c3c" %)versions(%%). It should be noted that when working with processing applications such as SAS and SPSS, it is often the case that dedicated scripts will need to be written within those environments, as different national formats within those applications will require specific formatting scripts to produce [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] outputs.
107 107  
108 108  ==== 12.3.1.3 SDMX and Analysis of Aggregates (Step 6) ====
109 109  
... ... @@ -179,7 +179,7 @@
179 179  (% style="text-align: center;" %)
180 180  **{{id name="image_41"/}}Figure 41: Schematic of Model for Process in SDMX**
181 181  
182 -The process can be expressed in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], so that documentation can be produced in many useful formats, using the same types of transforms described earlier for disseminating statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]. Thus, a PDF or HTML version of a process description could be generated from the XML.
180 +The process can be expressed in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], so that documentation can be produced in many useful formats, using the same types of transforms described earlier for disseminating statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]. Thus, a PDF or HTML (% style="color:#e74c3c" %)version(%%) of a process description could be generated from the XML.
183 183  
184 184  It is easy to see that a particular organization could use the GSBPM as the basis of such a process, describe each input and output, and then send this to another organization, so that the exact processing of the data was clear.
185 185  
... ... @@ -211,21 +211,20 @@
211 211  |7.4 Promote Dissemination products|(((
212 212  Use of [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services
213 213  
214 -provides a high level of visibility for data
212 +provides a high (% style="color:#e74c3c" %)level(%%) of visibility for data
215 215  )))|(% style="width:505px" %)Depends on the availability of a domain registry for this purpose – requires that new data be registered automatically or manually
216 216  |8.2 Manage Archive Repository|(((
217 217  [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] provides an easy format for generation of formats needed, based on the user demands on the archive;
218 218  
219 -strict version control allows for explicit management of dependencies between data and metadata
217 +strict (% style="color:#e74c3c" %)version(%%) control allows for explicit management of dependencies between data and metadata
220 220  )))|(% style="width:505px" %)
221 221  |8.3 Preserve Data and Associated Metadata|Rich metadata and application/platform independence make [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] a good archival format|(% style="width:505px" %)
222 222  
223 223  The benefits of using [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] here are several:
224 224  
225 -* Standard data structures, statistical (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and classifications, and formats make it easy to process and compare similar types of data from different national sources, both for data collectors and other users
223 +* Standard data structures, statistical (% style="color:#e74c3c" %)concepts(%%) and classifications, and formats make it easy to process and compare similar types of data from different national sources, both for data collectors and other users
226 226  * Richer [[dissemination format>>doc:sdmx:Glossary.Dissemination format.WebHome]], complete with metadata, supports not only good visualization of data, but also allows easy downloading and use of data in internal systems
227 -* SDMX-ML pro
228 -* vides an excellent format for having a single source of data which can be easily transformed into different output formats for use
225 +* [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] provides an excellent format for having a single source of data which can be easily transformed into different output formats for use
229 229  * Data becomes easier to find and use, through [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services, promoting the use of the data
230 230  * Data is archived in a long-lived format, independent of applications/platforms, and is accompanied by rich metadata, managed according to strict versioning rules
231 231  
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -13
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +13