Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 6.1
edited by Artur
on 2025/09/10 11:19
Change comment: Migrated property [LightLLMprompt] from class [SKMS.Methodology.Code.MethodologyClass]
To version 2.1
edited by Helena
on 2025/05/23 17:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.arturkryazhev
1 +xwiki:XWiki.helena
Tags
... ... @@ -1,1 +1,0 @@
1 -Attribute|Category|Code list|Concept|Constraint|Data set|Data source|Data structure definition|Dataflow|Dimension|Facet|Measure|Provision agreement|SDMX Information Model|Statistical data and metadata exchange|Structural metadata
Content
... ... @@ -28,14 +28,14 @@
28 28  
29 29  Annex 6: Worked Use Case shows data discovery using this “drill down” approach.
30 30  
31 -Another means in which users might discover data is through known (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) or [[code lists>>doc:sdmx:Glossary.Code list.WebHome]]. This further emphasises the point made in Chapter 4, that standard (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] should be used whenever possible. For example, suppose a user seeking demographic data knows that they are looking for data which uses a life birth (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) as a [[measure>>doc:sdmx:Glossary.Measure.WebHome]]. The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] SOAP query allows for such queries. But this will only result in data being returned from the query if the standard (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) is used.
31 +Another means in which users might discover data is through known (% style="color:#e74c3c" %)concepts(%%) or [[code lists>>doc:sdmx:Glossary.Code list.WebHome]]. This further emphasises the point made in Chapter 4, that standard (% style="color:#e74c3c" %)concepts(%%) and [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] should be used whenever possible. For example, suppose a user seeking demographic data knows that they are looking for data which uses a life birth (% style="color:#e74c3c" %)concept(%%) as a [[measure>>doc:sdmx:Glossary.Measure.WebHome]]. The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] SOAP query allows for such queries. But this will only result in data being returned from the query if the standard (% style="color:#e74c3c" %)concept(%%) is used.
32 32  
33 33  == 6.4 Querying Data ==
34 34  
35 35  Once a user has discovered the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] on which data is based more specific queries can be made to get the specific data being sought. It is often true that a user may not wish to receive an entire [[data set>>doc:sdmx:Glossary.Data set.WebHome]], but rather data for particular keys within the [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. The [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] gives the user enough detail to inform how to query for data, but it does not make any guarantees about the presence of data. It is quite possible that the [[data source>>doc:sdmx:Glossary.Data source.WebHome]] is a sparse cube - that is to say that there may not be data for every possible key permutation. To help users with this issue, there are two possible approaches.
36 36  
37 -The first approach is to describe the available content of the [[data source>>doc:sdmx:Glossary.Data source.WebHome]] as a content [[constraint>>doc:Glossary.Constraint.WebHome]]. A content [[constraint>>doc:Glossary.Constraint.WebHome]] is [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] which details the key sets for which data is present. The [[constraint>>doc:Glossary.Constraint.WebHome]] is attached to a particular [[data set>>doc:sdmx:Glossary.Data set.WebHome]], [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]], or data structure. Therefore, if the user application knows the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] which the data is based on, it can query for the content [[constraint>>doc:Glossary.Constraint.WebHome]] in order to determine which data is present.
37 +The first approach is to describe the available content of the [[data source>>doc:sdmx:Glossary.Data source.WebHome]] as a content (% style="color:#e74c3c" %)constraint(%%). A content (% style="color:#e74c3c" %)constraint(%%) is [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] which details the key sets for which data is present. The (% style="color:#e74c3c" %)constraint(%%) is attached to a particular [[data set>>doc:sdmx:Glossary.Data set.WebHome]], [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]], or data structure. Therefore, if the user application knows the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] which the data is based on, it can query for the content (% style="color:#e74c3c" %)constraint(%%) in order to determine which data is present.
38 38  
39 -The second approach is to support the data query mechanism which allows for only key values to be returned. In this approach, the user queries for data in the usual way, but specifies that the detail returned should contain no data or data [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. This information is effectively equivalent to a content [[constraint>>doc:Glossary.Constraint.WebHome]] but does not require the extra bit of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] be maintained. These keys can be stored locally or cached by the application and processes to ensure that the user is presented with [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] value choices that will return data.
39 +The second approach is to support the data query mechanism which allows for only key values to be returned. In this approach, the user queries for data in the usual way, but specifies that the detail returned should contain no data or data [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. This information is effectively equivalent to a content (% style="color:#e74c3c" %)constraint(%%) but does not require the extra bit of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] be maintained. These keys can be stored locally or cached by the application and processes to ensure that the user is presented with [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] value choices that will return data.
40 40  
41 41  Finally, it is important to note that Part 7 of the specification is very clear in the fact that a query web service does not need to implement every feature of the various query protocols. It simply states that the query be accepted even if the result is an error stating that the given feature is not implemented. Therefore, the implementer need not be overwhelmed by all of the finer details of the queries.
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -7
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +7