Changes for page 7 Metadata Repository and Linking Data to Metadata
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki.he lena1 +xwiki:XWiki.arturkryazhev - Tags
-
... ... @@ -1,1 +1,0 @@ 1 -Attribute|Category|Code|Component|Concept|Data consumer|Data provider|Data structure definition|Dataflow|Dimension|Item scheme|Metadata repository|Metadata set|Metadata structure definition|Reference area|Reference metadata|Statistical data and metadata exchange - Content
-
... ... @@ -4,11 +4,12 @@ 4 4 5 5 == 7.1 Scope of this Chapter == 6 6 7 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_fa163c2f118092e0.jpg||data-xwiki-image-style-alignment="center" height="417" width="343"]] 7 +(% style="text-align: center;" %) 8 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_fa163c2f118092e0.jpg||height="417" width="343"]] 8 8 9 -The storage, retrieval and linkage to data of [[Reference Metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]](often known as “footnote” metadata) is becoming more and more important in the dissemination of statistics. All organizations that compile statistical data have[[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] and it is often useful to[[data consumers>>doc:sdmx:Glossary.Dataconsumer.WebHome]]for the[[data providers>>doc:sdmx:Glossary.Dataprovider.WebHome]]to disseminate this with the data. This can be done in a simple way by disseminating all such metadata regardless of whether it pertains to the data, or it can be done in a more intelligent way, and therefore more useful to the[[data consumer>>doc:sdmx:Glossary.Data consumer.WebHome]], by disseminating only that metadata which pertains to the data being viewed or downloaded.10 +The storage, retrieval and linkage to data of Reference Metadata (often known as “footnote” metadata) is becoming more and more important in the dissemination of statistics. All organizations that compile statistical data have reference metadata and it is often useful to data consumers for the data providers to disseminate this with the data. This can be done in a simple way by disseminating all such metadata regardless of whether it pertains to the data, or it can be done in a more intelligent way, and therefore more useful to the data consumer, by disseminating only that metadata which pertains to the data being viewed or downloaded. 10 10 11 -This Chapter discusses the role of the [[metadata repository>>doc:sdmx:Glossary.Metadatarepository.WebHome]] in the context of:12 +This Chapter discusses the role of the metadata repository in the context of: 12 12 13 13 * its logical structure 14 14 * loading metadata ... ... @@ -16,100 +16,104 @@ 16 16 17 17 == 7.2 Structure of the Metadata Repository == 18 18 19 -In [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] all metadata is characterized as:20 +In SDMX all metadata is characterized as: 20 20 21 -* Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]o Attached to a ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]) object22 +* Metadata Attribute o Attached to a (SDMX) object 22 22 23 -Examples are shown below. The “Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]” is taken from the[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]Cross Domain(% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%)and the “Attached to” is a typical object to which it would be attached in a data dissemination scenario.24 +Examples are shown below. The “Metadata Attribute” is taken from the SDMX Cross Domain Concepts and the “Attached to” is a typical object to which it would be attached in a data dissemination scenario. 24 24 25 25 (% style="width:1213.45px" %) 26 26 |**Metadata Attribute**|(% style="width:395px" %)**Description**|(% style="width:633px" %)**Attached To** 27 -|COMPILING_ORG|(% style="width:395px" %)The organisation compiling the data being reported|(% style="width:633px" %)Data Key – this can be a full or partial key. In thie specific example presented here it would probably be attached to the [[Reference Area>>doc:sdmx:Glossary.Referencearea.WebHome]] [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]].28 -|COVERAGE_SECTOR|(% style="width:395px" %)Main economic or other sectors covered by the statistics|(% style="width:633px" %) [[CODE>>doc:sdmx:Glossary.Code.WebHome]]29 -|SOURCE_TYPE|(% style="width:395px" %)Characteristics and [[components>>doc:sdmx:Glossary.Component.WebHome]]of the raw statistical data used for compiling statistical aggregates|(% style="width:633px" %)[[DATAFLOW>>doc:sdmx:Glossary.Dataflow.WebHome]]28 +|COMPILING_ORG|(% style="width:395px" %)The organisation compiling the data being reported|(% style="width:633px" %)Data Key – this can be a full or partial key. In thie specific example presented here it would probably be attached to the Reference Area dimension. 29 +|COVERAGE_SECTOR|(% style="width:395px" %)Main economic or other sectors covered by the statistics|(% style="width:633px" %)CODE 30 +|SOURCE_TYPE|(% style="width:395px" %)Characteristics and components of the raw statistical data used for compiling statistical aggregates|(% style="width:633px" %)DATAFLOW 30 30 |UNIT_MEASURE|(% style="width:395px" %) |(% style="width:633px" %)SERIES KEY 31 -|COMMENT|(% style="width:395px" %)Supplementary descriptive text which can be attached to data or metadata|(% style="width:633px" %) (% style="color:#e74c3c" %)[[CONCEPT>>doc:sdmx:Glossary.Concept.WebHome]](%%)( if applicable to all uses of the(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%))or[[DIMENSION>>doc:sdmx:Glossary.Dimension.WebHome]](if applicable to the use of a(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%)in a specific[[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]])32 +|COMMENT|(% style="width:395px" %)Supplementary descriptive text which can be attached to data or metadata|(% style="width:633px" %)CONCEPT ( if applicable to all uses of the Concept) or DIMENSION (if applicable to the use of a Concept in a specific DSD) 32 32 |OBS_STATUS|(% style="width:395px" %)Information on the quality of a value or an unusual or missing value|(% style="width:633px" %)OBSERVATION 33 33 34 -Therefore the conceptual structure of a [[Metadata Repository>>doc:sdmx:Glossary.Metadatarepository.WebHome]] is:35 +Therefore the conceptual structure of a Metadata Repository is: 35 35 36 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_80254bb4443a6ba5.jpg||data-xwiki-image-style-alignment="center" height="176" width="576"]] 37 +(% style="text-align: center;" %) 38 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_80254bb4443a6ba5.jpg||height="176" width="576"]] 37 37 38 38 (% style="text-align: center;" %) 39 39 **{{id name="image_14"/}}Figure 14: Conceptual Structure of a Metadata Repository** 40 40 41 -This is only a conceptual structure and is purposefully over-simplistic as it is drawn to show conceptually how such a [[metadata repository>>doc:sdmx:Glossary.Metadatarepository.WebHome]] may work.43 +This is only a conceptual structure and is purposefully over-simplistic as it is drawn to show conceptually how such a metadata repository may work. 42 42 43 -The Metadata Key is comprised of one or more Object Type/Object Id. For instance, for a [[Code>>doc:sdmx:Glossary.Code.WebHome]]or a(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%)it would be the Id of the[[Code>>doc:sdmx:Glossary.Code.WebHome]]or(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%)such as the URN. For a specific key or partial key there would be two Objects, the[[DSD>>doc:sdmx:Glossary.Datastructure definition.WebHome]]and the Data Key. Clearly, this is a conceptual structure as it is probable that the Metadata Key would combine the value of all of the individual Object Ids, as this would be necessary in order to find metadata quickly.45 +The Metadata Key is comprised of one or more Object Type/Object Id. For instance, for a Code or a Concept it would be the Id of the Code or Concept such as the URN. For a specific key or partial key there would be two Objects, the DSD and the Data Key. Clearly, this is a conceptual structure as it is probable that the Metadata Key would combine the value of all of the individual Object Ids, as this would be necessary in order to find metadata quickly. 44 44 45 -The Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]Table may, of course, contain additional information depending on the actual requirements. For instance, it may not be necessary to reference the[[Metadata Structure Definition>>doc:sdmx:Glossary.Metadatastructure definition.WebHome]]([[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]) providing the(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%)name and Description are contained in the table. Also, it may be useful to add a “Short Name” to be used by applications such as web sites. Note that the metadata[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]structure can be hierarchical (i.e. a Metadata[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]can have child Metadata[[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]). As each Metadata[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]can have only one parent this structure is achieved by the Parent[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]Id.47 +The Metadata Attribute Table may, of course, contain additional information depending on the actual requirements. For instance, it may not be necessary to reference the Metadata Structure Definition (MSD) providing the Concept name and Description are contained in the table. Also, it may be useful to add a “Short Name” to be used by applications such as web sites. Note that the metadata attribute structure can be hierarchical (i.e. a Metadata Attribute can have child Metadata Attributes). As each Metadata Attribute can have only one parent this structure is achieved by the Parent Attribute Id. 46 46 47 -The way such 49 +The way such a repository would support the linking of data to metadata is shown below. 48 48 49 -a repository would support the linking of data to metadata is shown below. 50 - 51 51 == 7.3 Linking Data to Metadata == 52 52 53 53 === 7.3.1 Examples === 54 54 55 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_52419152fb71038.png||data-xwiki-image-style-alignment="center" height="361" width="699"]] 55 +(% style="text-align: center;" %) 56 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_52419152fb71038.png||height="361" width="699"]] 56 56 57 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_1a7bc7f4af53ef18.png||data-xwiki-image-style-alignment="center" height="424" width="699"]] 58 +(% style="text-align: center;" %) 59 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_1a7bc7f4af53ef18.png||height="424" width="699"]] 58 58 59 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_c0dbd61fc2de1d2d.png||data-xwiki-image-style-alignment="center" height="417" width="699"]] 61 +(% style="text-align: center;" %) 62 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_c0dbd61fc2de1d2d.png||height="417" width="699"]] 60 60 61 61 === 7.3.2 Metadata Structure Definition === 62 62 63 63 ==== 7.3.2.1 MSD Visualised in a Tool ==== 64 64 65 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_c395b26f603554fc.png||data-xwiki-image-style-alignment="center" height="478" width="680"]] 68 +(% style="text-align: center;" %) 69 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_c395b26f603554fc.png||height="478" width="680"]] 66 66 67 67 (% style="text-align: center;" %) 68 -**Figure 15: MSD - Metadata Targets** 72 +**{{id name="image_15"/}}Figure 15: MSD - Metadata Targets** 69 69 70 -(% class="wikigeneratedid" id="HNotes" %) 71 -**Notes** 74 +===== **Notes** ===== 72 72 73 -The DATA_KEY_TARGET comprises two [[components>>doc:sdmx:Glossary.Component.WebHome]]:76 +The DATA_KEY_TARGET comprises two components: 74 74 75 -1. A **Key Descriptor** ( [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]descriptor) – this specifies that a key (one or more[[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]values) must be specified in the[[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]76 -1. An **Identifiable Object** which must be a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]– this specifies that a[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]must be specified in the[[Metadata Set>>doc:sdmx:Glossary.Metadataset.WebHome]].If required, the valid list of[[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]]can be specified in an[[Item Scheme>>doc:sdmx:Glossary.Itemscheme.WebHome]] such as a[[Category>>doc:sdmx:Glossary.Category.WebHome]]Scheme.78 +1. A **Key Descriptor** (dimension descriptor) – this specifies that a key (one or more dimension values) must be specified in the Metadata Set 79 +1. An **Identifiable Object** which must be a Dataflow – this specifies that a Dataflow must be specified in the Metadata Set. If required, the valid list of Dataflows can be specified in an Item Scheme such as a Category Scheme. 77 77 78 -The combination of these two [[components>>doc:sdmx:Glossary.Component.WebHome]]specifies a data key in the context of a specific[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].81 +The combination of these two components specifies a data key in the context of a specific Dataflow. 79 79 80 80 The DATAFLOW_TARGET comprises just one component: 81 81 82 -~1. An **Identifiable Object** which must be a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]85 +~1. An **Identifiable Object** which must be a Dataflow 83 83 84 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_1f7507712781fc80.jpg||data-xwiki-image-style-alignment="center" height="293" width="576"]] 87 +(% style="text-align: center;" %) 88 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_1f7507712781fc80.jpg||height="293" width="576"]] 85 85 86 86 (% style="text-align: center;" %) 87 -**Figure 16: MSD - Report Structure** 91 +**{{id name="image_16"/}}Figure 16: MSD - Report Structure** 88 88 89 -(% class="wikigeneratedid" id="HNotes-1" %) 90 -**Notes** 93 +===== Notes ===== 91 91 92 -1. There is only one Report Structure. The same structure is used for both Metadata Targets ( [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]and Data Key).93 -1. It is possible to have many Report Structure in an [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], each referencing a different Metadata Target.95 +1. There is only one Report Structure. The same structure is used for both Metadata Targets (Dataflow and Data Key). 96 +1. It is possible to have many Report Structure in an MSD, each referencing a different Metadata Target. 94 94 95 95 ==== 7.3.2.2 MSD SDMX-ML ==== 96 96 97 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_c33453af365398ed.jpg||data-xwiki-image-style-alignment="center" height="452" width="518"]] 100 +(% style="text-align: center;" %) 101 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_c33453af365398ed.jpg||height="452" width="518"]] 98 98 99 99 (% style="text-align: center;" %) 100 -**Figure 17: MSD - Metadata Targets** 104 +**{{id name="image_17"/}}Figure 17: MSD - Metadata Targets** 101 101 102 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_20c6a0fb93ba4785.jpg||data-xwiki-image-style-alignment="center" height="538" width="576"]] 106 +(% style="text-align: center;" %) 107 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_20c6a0fb93ba4785.jpg||height="538" width="576"]] 103 103 104 104 (% style="text-align: center;" %) 105 -**Figure 18: MSD - Metadata Report** 110 +**{{id name="image_18"/}}Figure 18: MSD - Metadata Report** 106 106 107 -Note that the reasons of brevity content of many of the Metadata [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]has been collapsed e.g. each has112 +Note that the reasons of brevity content of many of the Metadata Attributes has been collapsed e.g. each has a Concept identity and Local Representation. 108 108 109 -a (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) identity and Local Representation. 110 - 111 111 === 7.3.3 Metadata Set === 112 112 113 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_78c50612303a7fec.gif||alt="Shape1" data-xwiki-image-style-alignment="center" height="626" width="485"]] 116 +(% style="text-align: center;" %) 117 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_78c50612303a7fec.gif||alt="Shape1" height="626" width="485"]] 114 114 115 -[[image:SDMX_2-1_User_Guide_draft_0-1_html_56dabe85f0ea1c96.jpg||data-xwiki-image-style-alignment="center" height="526" width="576"]] 119 +(% style="text-align: center;" %) 120 +[[image:SDMX_2-1_User_Guide_draft_0-1_html_56dabe85f0ea1c96.jpg||height="526" width="576"]]
- SKMS.Methodology.Code.MethodologyClass[0]
-
- Index
-
... ... @@ -1,1 +1,0 @@ 1 -8
- SUZ.Methodology.Code.MethodologyClass[0]
-
- index
-
... ... @@ -1,0 +1,1 @@ 1 +8