Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 14.1
edited by Helena
on 2025/07/20 13:39
Change comment: There is no comment for this version
To version 11.1
edited by Artur
on 2025/07/14 10:19
Change comment: Imported from XAR

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Tags
... ... @@ -1,0 +1,1 @@
1 +Attribute|Attribute relationship|Category|Category scheme|Code|Code list|Concept|Concept scheme|Data provider|Data provider scheme|Data set|Data source|Data structure definition|Dataflow|Decimals|Dimension|Measure|Metadata repository|Metadata structure definition|Provision agreement|Reference metadata|SDMX Registry|SDMX-ML|Series key|Statistical data and metadata exchange|Structural metadata|Title
Content
... ... @@ -293,7 +293,7 @@
293 293  (% style="text-align: center;" %)
294 294  **{{id name="image_56"/}}Figure 56: Selection Screen build from SDMX DSD**
295 295  
296 -The user can click on each of the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] and the relevant [[code>>doc:sdmx:Glossary.Code.WebHome]] selections are displayed. Note that in the example above the application is assumed to have queries for all the keys so that it can process them in order to grey-out the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] selections for which there is no data. These are greyed-out based on the current selections in the other [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]. This shows the importance of content [[constraints>>doc:Glossary.Constraint.WebHome]] in a web dissemination system, as they can be used to guide the user to make only the selections that will return data. The same result can be achieved if these [[constraints>>doc:Glossary.Constraint.WebHome]] are available for query (e.g. in a Registry), but this is a less effective way of processing if the contenrts of the database are dynamic.
296 +The user can click on each of the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] and the relevant [[code>>doc:sdmx:Glossary.Code.WebHome]] selections are displayed. Note that in the example above the application is assumed to have queries for all the keys so that it can process them in order to grey-out the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] selections for which there is no data. These are greyed-out based on the current selections in the other [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]. This shows the importance of content [[constraints>>path:/xwiki/wiki/sdmx/get/Methodology/SDMX%202.1%20User%20Guide/6%20Data%20and%20Structure%20Query?sheet=CKEditor.ResourceDispatcher&outputSyntax=plain&language=en&type=doc&reference=Glossary.Constraint.WebHome&typed=true]] in a web dissemination system, as they can be used to guide the user to make only the selections that will return data. The same result can be achieved if these [[constraints>>path:/xwiki/wiki/sdmx/get/Methodology/SDMX%202.1%20User%20Guide/6%20Data%20and%20Structure%20Query?sheet=CKEditor.ResourceDispatcher&outputSyntax=plain&language=en&type=doc&reference=Glossary.Constraint.WebHome&typed=true]] are available for query (e.g. in a Registry), but this is a less effective way of processing if the contenrts of the database are dynamic.
297 297  
298 298  === 16.4.6 Query Database ===
299 299