Skip to Content
Version 1.2 by Artur on 2025/05/20 14:28
Show last authors
1 {{box title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 == 7.1 Scope of this Chapter ==
6
7 (% style="text-align: center;" %)
8 [[image:SDMX_2-1_User_Guide_draft_0-1_html_fa163c2f118092e0.jpg||height="417" width="343"]]
9
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.
11
12 This Chapter discusses the role of the metadata repository in the context of:
13
14 * its logical structure
15 * loading metadata
16 * retrieving metadata
17
18 == 7.2 Structure of the Metadata Repository ==
19
20 In SDMX all metadata is characterized as:
21
22 * Metadata Attribute o Attached to a (SDMX) object
23
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.
25
26 (% style="width:1213.45px" %)
27 |**Metadata Attribute**|(% style="width:395px" %)**Description**|(% style="width:633px" %)**Attached To**
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
31 |UNIT_MEASURE|(% style="width:395px" %) |(% style="width:633px" %)SERIES KEY
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)
33 |OBS_STATUS|(% style="width:395px" %)Information on the quality of a value or an unusual or missing value|(% style="width:633px" %)OBSERVATION
34
35 Therefore the conceptual structure of a Metadata Repository is:
36
37 (% style="text-align: center;" %)
38 [[image:SDMX_2-1_User_Guide_draft_0-1_html_80254bb4443a6ba5.jpg||height="176" width="576"]]
39
40 (% style="text-align: center;" %)
41 **{{id name="image_14"/}}Figure 14: Conceptual Structure of a Metadata Repository**
42
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.
44
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.
46
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.
48
49 The way such a repository would support the linking of data to metadata is shown below.
50
51 == 7.3 Linking Data to Metadata ==
52
53 === 7.3.1 Examples ===
54
55 (% style="text-align: center;" %)
56 [[image:SDMX_2-1_User_Guide_draft_0-1_html_52419152fb71038.png||height="361" width="699"]]
57
58 (% style="text-align: center;" %)
59 [[image:SDMX_2-1_User_Guide_draft_0-1_html_1a7bc7f4af53ef18.png||height="424" width="699"]]
60
61 (% style="text-align: center;" %)
62 [[image:SDMX_2-1_User_Guide_draft_0-1_html_c0dbd61fc2de1d2d.png||height="417" width="699"]]
63
64 === 7.3.2 Metadata Structure Definition ===
65
66 ==== 7.3.2.1 MSD Visualised in a Tool ====
67
68 (% style="text-align: center;" %)
69 [[image:SDMX_2-1_User_Guide_draft_0-1_html_c395b26f603554fc.png||height="478" width="680"]]
70
71 (% style="text-align: center;" %)
72 **{{id name="image_15"/}}Figure 15: MSD - Metadata Targets**
73
74 ===== **Notes** =====
75
76 The DATA_KEY_TARGET comprises two components:
77
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.
80
81 The combination of these two components specifies a data key in the context of a specific Dataflow.
82
83 The DATAFLOW_TARGET comprises just one component:
84
85 ~1. An **Identifiable Object** which must be a Dataflow
86
87 (% style="text-align: center;" %)
88 [[image:SDMX_2-1_User_Guide_draft_0-1_html_1f7507712781fc80.jpg||height="293" width="576"]]
89
90 (% style="text-align: center;" %)
91 **{{id name="image_16"/}}Figure 16: MSD - Report Structure**
92
93 ===== Notes =====
94
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.
97
98 ==== 7.3.2.2 MSD SDMX-ML ====
99
100 (% style="text-align: center;" %)
101 [[image:SDMX_2-1_User_Guide_draft_0-1_html_c33453af365398ed.jpg||height="452" width="518"]]
102
103 (% style="text-align: center;" %)
104 **{{id name="image_17"/}}Figure 17: MSD - Metadata Targets**
105
106 (% style="text-align: center;" %)
107 [[image:SDMX_2-1_User_Guide_draft_0-1_html_20c6a0fb93ba4785.jpg||height="538" width="576"]]
108
109 (% style="text-align: center;" %)
110 **{{id name="image_18"/}}Figure 18: MSD - Metadata Report**
111
112 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.
113
114 === 7.3.3 Metadata Set ===
115
116 (% style="text-align: center;" %)
117 [[image:SDMX_2-1_User_Guide_draft_0-1_html_78c50612303a7fec.gif||alt="Shape1" height="626" width="485"]]
118
119 (% style="text-align: center;" %)
120 [[image:SDMX_2-1_User_Guide_draft_0-1_html_56dabe85f0ea1c96.jpg||height="526" width="576"]]