Changes for page 16 Annex 6: Worked Use Case
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,34 +4,34 @@ 4 4 5 5 == 16.1 Scope == 6 6 7 -The scope of this Chapter is to show the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]interactions with the Registry, database, and[[metadata repository>>doc:sdmx:Glossary.Metadatarepository.WebHome]]for the use case scenario outlined in Chapter 3. The scenario is repeated below.7 +The scope of this Chapter is to show the SDMX-ML interactions with the Registry, database, and metadata repository for the use case scenario outlined in Chapter 3. The scenario is repeated below. 8 8 9 -The [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]examples used are(% style="color:#e74c3c" %)version(%%)2.1.9 +The SDMX-ML examples used are version 2.1. 10 10 11 11 == 16.2 Scenario == 12 12 13 -This scenario is the dissemination of data and related [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]]using[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]web services. It shows how the data,[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]], and[[structural metadata>>doc:sdmx:Glossary.Structuralmetadata.WebHome]] are used to build a web dissemination system.13 +This scenario is the dissemination of data and related reference metadata using SDMX web services. It shows how the data, reference metadata, and structural metadata are used to build a web dissemination system. 14 14 15 15 [[image:image-20250318221512-1.jpeg||data-xwiki-image-style-alignment="center"]] 16 16 17 17 (% style="text-align: center;" %) 18 -**{{id name="image_47"/}}Figure 47: Process flow of an [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]WebData Dissemination System**18 +**{{id name="image_47"/}}Figure 47: Process flow of an SDMX Web Data Dissemination System** 19 19 20 20 (% style="width:753.446px" %) 21 21 |**Process**|(% style="width:670px" %)**Description** 22 -|1|(% style="width:670px" %)Retrieve the [[DSD>>doc:sdmx:Glossary.Datastructure definition.WebHome]] from a[[structural metadata>>doc:sdmx:Glossary.Structuralmetadata.WebHome]]source (e.g. an[[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]), and create database tables.23 -|2|(% style="width:670px" %)Read an [[SDMX>>doc:sdmx:Glossary.Statisticaldataand metadata exchange.WebHome]] [[dataset>>doc:sdmx:Glossary.Dataset.WebHome]]file and load the data into the database24 -|3|(% style="width:670px" %)Data discovery system continually synchronises its metadata with the [[structural metadata>>doc:sdmx:Glossary.Structuralmetadata.WebHome]]source. A user makes a data selection from choices built from the information held in an[[SDMX Registry>>doc:sdmx:Glossary.SDMXRegistry.WebHome]]([[structural metadata>>doc:sdmx:Glossary.Structuralmetadata.WebHome]]such as[[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]],[[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]],[[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]],[[data provider>>doc:sdmx:Glossary.Data provider.WebHome]],[[provision agreements>>doc:sdmx:Glossary.Provisionagreement.WebHome]] and data registration)25 -|3|(% style="width:670px" %)These choices are logical choices, built from the [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]selections.26 -|5|(% style="width:670px" %)The logical choice is formatted as an [[SDMX>>doc:sdmx:Glossary.Statisticaldataand metadata exchange.WebHome]] dataquery. This is passed to the Data Base which responds with an[[SDMX>>doc:sdmx:Glossary.Statisticaldataand metadata exchange.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].27 -|6|(% style="width:670px" %) [[Reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]]relevant to the data returned is retrieved from a[[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]].28 -|7|(% style="width:670px" %)The data and metadata are passed to a visualization tool to display the data in tables, charts, graphs, (% style="color:#e74c3c" %)maps(%%)etc. Often a download is offered in various formats. The download options often include also the[[DSD>>doc:sdmx:Glossary.Datastructure definition.WebHome]] or MSD.22 +|1|(% style="width:670px" %)Retrieve the DSD from a structural metadata source (e.g. an SDMX Registry), and create database tables. 23 +|2|(% style="width:670px" %)Read an SDMX data set file and load the data into the database 24 +|3|(% style="width:670px" %)Data discovery system continually synchronises its metadata with the structural metadata source. A user makes a data selection from choices built from the information held in an SDMX Registry (structural metadata such as category scheme, dataflow, DSD, data provider, provision agreements and data registration) 25 +|3|(% style="width:670px" %)These choices are logical choices, built from the dimension selections. 26 +|5|(% style="width:670px" %)The logical choice is formatted as an SDMX data query. This is passed to the Data Base which responds with an SDMX data set. 27 +|6|(% style="width:670px" %)Reference metadata relevant to the data returned is retrieved from a metadata repository. 28 +|7|(% style="width:670px" %)The data and metadata are passed to a visualization tool to display the data in tables, charts, graphs, maps etc. Often a download is offered in various formats. The download options often include also the DSD or MSD. 29 29 30 30 == 16.3 Structural Metadata == 31 31 32 32 === 16.3.1 Schematic === 33 33 34 -The following [[structural metadata>>doc:sdmx:Glossary.Structuralmetadata.WebHome]] and provisioning metadata is used in the scenario.34 +The following structural metadata and provisioning metadata is used in the scenario. 35 35 36 36 [[image:image-20250318221512-2.jpeg||data-xwiki-image-style-alignment="center"]] 37 37 ... ... @@ -40,7 +40,7 @@ 40 40 41 41 === 16.3.2 Data Structure Definition === 42 42 43 -For the reasons of clarity a sub set of the contents of the [[Code Lists>>doc:sdmx:Glossary.Codelist.WebHome]]and[[Concept Schemes>>doc:sdmx:Glossary.Conceptscheme.WebHome]]are used in this example, and only a few of the[[DSD>>doc:sdmx:Glossary.Datastructure definition.WebHome]] [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]are used.43 +For the reasons of clarity a sub set of the contents of the Code Lists and Concept Schemes are used in this example, and only a few of the DSD Attributes are used. 44 44 45 45 (% class="wikigeneratedid" id="HDimensions" %) 46 46 **Dimensions** ... ... @@ -75,10 +75,9 @@ 75 75 (% style="text-align: center;" %) 76 76 **{{id name="image_49"/}}Figure 49: User Case - Create Database Tables from DSD** 77 77 78 -The following [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]is extracted from the Registry using the REST query http:~/~/[ ws-entry-point]/DataStructure_ECB/ECB_EXR178 +The following SDMX-ML is extracted from the Registry using the REST query http:~/~/[ ws-entry-point]/DataStructure_ECB/ECB_EXR1 79 79 80 -(% class="wikigeneratedid" id="HDimensions" %) 81 -**Dimensions** 80 +===== Dimensions ===== 82 82 83 83 [[image:image-20250318221512-8.jpeg||data-xwiki-image-style-alignment="center"]] 84 84 ... ... @@ -87,9 +87,9 @@ 87 87 (% class="wikigeneratedid" id="HNotes" %) 88 88 **Notes** 89 89 90 -1. A [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]can state its position in the key, but the actual sequence is defined by the sequence in the i.e. the inferred sequence in the takes precedence over the value of the position attribute.91 -1. This [[DSD>>doc:sdmx:Glossary.Datastructure definition.WebHome]] is converted from(% style="color:#e74c3c" %)version(%%)2.0. The(% style="color:#e74c3c" %)version(%%)2.0(% style="color:#e74c3c" %)Concepts(%%)were standalone in the form <Concept agencyID=”ECB” version=”1.0”/>92 -1. The standalone (% style="color:#e74c3c" %)concept(%%)is not supported in 2.1 and any standalone(% style="color:#e74c3c" %)concept(%%)is placed in a[[Concept Scheme>>doc:sdmx:Glossary.Conceptscheme.WebHome]]with the Id “STANDALONE_CONCEPT_SCHEME” of the(% style="color:#e74c3c" %)version(%%)corresponding to the(% style="color:#e74c3c" %)version(%%)of the original standalone(% style="color:#e74c3c" %)concept(%%).89 +1. A Dimension can state its position in the key, but the actual sequence is defined by the sequence in the <DimensionList> i.e. the inferred sequence in the <DimensionList> takes precedence over the value of the position attribute. 90 +1. This DSD is converted from version 2.0. The version 2.0 Concepts were standalone in the form <Concept agencyID=”ECB” version=”1.0”/> 91 +1. The standalone concept is not supported in 2.1 and any standalone concept is placed in a Concept Scheme with the Id “STANDALONE_CONCEPT_SCHEME” of the version corresponding to the version of the original standalone concept. 93 93 94 94 (% class="wikigeneratedid" id="HGroup-1" %) 95 95 **Group** ... ... @@ -102,8 +102,7 @@ 102 102 1. A Group in version 2.1 plays the same role as it does in version 2.0 except that it does not group Series in the data set. The Group in version 2.1 is used solely as a mechanism to attach Attributes in the data set. 103 103 1. The Group in version 2.1 is retained for compatibility with version 2.0 and for avoiding repetition in the new Attribute Relationship construct which is introduced in version 2.1. 104 104 105 -(% class="wikigeneratedid" id="HAttributes" %) 106 -**Attributes** 104 +===== Attributes ===== 107 107 108 108 [[image:image-20250318221512-10.jpeg||data-xwiki-image-style-alignment="center"]] 109 109