Wiki source code of Standardising Reference Metadata Reporting in SDMX

Last modified by Artur K. on 2026/05/29 14:29

version	line-number	content
1.1	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
	4
	5	= DOCUMENT HISTORY =
	6
	7	\|Version\|Date\|Comment
	8	\|1.0\|28/6/2019\|Initial version
	9
	10	= INTRODUCTION =
	11
	12	The goal of this guideline is to increase the efficiency of reference metadata exchange between statistical agencies, and for dissemination (where the consumer may not be known). The quality and timeliness of reference metadata exchange may be improved and harmonised, thereby enabling statistical data to be described more thoroughly in a comparable way using automated, shared systems.
	13
	14	This guideline includes a Global Reference Metadata Concept Scheme (hereafter referred to as “Global MCS”) that enumerates a standard list of reference metadata concepts. The Global MCS is not sufficient to implement an exchange; therefore, the document also describes how to derive implementation structures from the Global MCS.
	15
	16	By following the guideline, the same tools and mappings may be used across separate metadata flows, agencies and domains using community-driven systems, thus saving on reinvention of the same functionality. Furthermore, the use of the Global MCS is intended to boost the automation of metadata exchange.
	17
	18	= METHODOLOGY USED TO BUILD THE GLOBAL METADATA CONCEPT SCHEME =
	19
	20	The Global MCS is constructed from a subset of SDMX cross-domain concepts that are related to reference metadata in the SDMX Glossary Version 2.0{{footnote}}https://sdmx.org/wp-content/uploads/SDMX_Glossary_Version_2_0_October_2018.docx {{/footnote}}. When the SDMX Glossary was compiled, all relevant reference metadata concepts were included that can be mapped to metadata frameworks used by several international organisations.
	21
	22	The procedure of building the Global MCS was to group the concepts relating to reference metadata into homogeneous categories, for example: Administrative Information; Scope; Statistical Processing. The categories are simply guides in this document and are not functional categories.
	23
	24	For each metadata concept, this document includes the definition and concept ID from the SDMX Glossary for ease of reference. To avoid unnecessary duplication, the usage context, related terms and other fields have not been included here and are available in the SDMX Glossary.
	25
	26	The Global MCS is available in the Global Registry to enable direct referencing.
	27
	28	= DESCRIPTION =
	29
	30	The current situation of reference metadata exchange usually requires that, for an agency to exchange with another agency, a specific mapping between the two agencies is required. Reference metadata are provided in the following ways:
	31
	32	* either the providing agency maps to the consumer agency's framework and sends the metadata (provider mapping),
	33	* or the providing agency publishes metadata using their own framework structure, and the consumer has to map the metadata to their own framework (collector mapping). This situation results in many mappings to compile and maintain which increases quickly with each new agency in the exchange, as shown here:
	34
	35	[[image:1768483868713-856.png]]
	36
	37	Figure 1: Without the global MCS, agencies maintain many similar mappings to other agencies metadata reference frameworks
	38
	39	The mapping maintenance cost grows significantly if agencies exchange metadata with each other directly.
	40
	41	The recommendations in this guideline are designed to alleviate this issue by replacing the direct mappings between the different local frameworks by mappings from and to the Global MCS, as in the following diagram:
	42
	43	[[image:1768483895511-673.png]]
	44
	45	Figure 2: Agencies will map to and from the Global MCS rather than implement the concepts directly. The two-colour mapping arrows indicate that each agency needs to map to the Global MCS for dissemination (orange), and from the Global MCS for collection (blue)
	46
	47	It is important to note that this Global MCS guideline recommends that statistical agencies should not have to change their own internal metadata framework in order to implement and benefit from the Global MCS.
	48
	49	=== Implementation Artefacts ===
	50
	51	The Global MCS may be considered as an “abstract” artefact – it cannot be used directly to define the structure of reference metadata messages, validate and exchange them. Instead, “implementation artefacts” must be created that derive from the Global MCS. These artefacts may be Metadata Structure Definitions (MSDs), or Data Structure Definitions (DSDs) (usually in attributes).
	52
	53	There are certain advantages to implementing reference metadata exchange using either artefact:
	54
	55	\|FEATURES\|Use MSD\|Use DSD
	56	\|Reuse an instance of metadata, attaching it to multiple artefacts\|Yes\|No
	57	\|Exchange metadata separately from data\|Yes\|Possible{{footnote}}It is possible to exchange metadata separately from data using a DSD by querying using the detail=nodata parameter{{/footnote}}
	58	\|Define metadata for artefact types which are not a dataset\|Yes\|No
	59	\|Relate/exchange metadata tightly with data\|No\|Yes
	60	\|Use same SDMX tools as for data exchange\|No\|Yes
2.1	61	\|Reduce amount of artefacts to implement\|Maybe{{footnote}}This may be possible, depending on the current implementation such as if an MSD is already implemented{{/footnote}}\|Yes
1.1	62
	63	Table 1: Advantages of implementing reference metadata exchange using DSDs or MSDs
	64
	65	To simplify this guideline, the implementation artefact referred to from this point will be an MSD; however the points would apply if a DSD was chosen for the implementation.
	66
	67	The Global MCS encompasses all SDMX reference metadata concepts; however, some of them may not be relevant for a metadata exchange program; therefore, implementation structures will likely be created that use a subset of the MCS concepts. If required in special cases, reference metadata concepts that are not in the Global MCS may be added to the MSDs – however, such additions will result in non-standard exchanges so this should be used with caution. If the added concepts are considered to be cross-domain in character, please refer to the section on Maintenance of the Global Metadata Concept Scheme.
	68
	69	The figure 3 below shows the relationship between the Global MCS , the derived MSDs for implementation, and a possible custom MCS:
	70
	71	* The green Custom MSD is a typical subset of metadata concepts that will be implemented;
	72	* The light blue Custom MCS is a subset of metadata concepts that may have further MSDs derived from it;
	73	* The purple Custom MSD contains some concepts from the Global MCS but has also been extended with other metadata concepts.
	74
	75
	76
	77	[[image:1768484009171-749.png]]
	78
	79	Figure 3: Examples of deriving MSDs/MCSs and extending the Global MCS concepts
	80
	81	The figure 4 below shows how the above MCSs and MSDs can be used for various implementations:
	82
	83	[[image:1768484049135-897.png]]
	84
	85	Figure 4: Examples of creating custom MSDs for example use cases.
	86
	87	= RECOMMENDED USAGE =
	88
	89	The Global MCS is domain independent, and is designed to cover the typical cross-domain metadata frameworks that most official statistical agencies have implemented. In order to create and exchange metadata messages that can be validated, an MSD must exist. It is likely that metadata repositories and exchange frameworks only require a subset of all concepts, therefore custom MSDs will usually be created to limit the full set of concepts; for example, if a branch of social statistics only uses a subset of the Global MCS concepts, a custom MSD should be created for the social statistics branch reference metadata.
	90
	91	As mentioned above, the concepts in the Global MCS may be implemented as data message attributes. To make the choice, there are certain factors to consider as mentioned in //Table 1: Advantages of implementing reference metadata exchange using DSDs or MSDs//
	92
	93	There may also be some cases where an exchange program may have some reference metadata described by MSDs and some in DSDs; whichever architecture is chosen requires a thorough analysis beforehand.
	94
	95	Some example use cases that would require the creation of a MSD with concepts outside of the Global MCS (an extension) are:
	96
	97	* where the reference metadata concepts to exchange are very domain-specific, and/or;
	98	* this version of the Global MCS does not cover the type of reference metadata (e.g. detailed quality metadata).
	99
	100	= IMPLEMENTATION EXAMPLE =
	101
	102	In order to avoid a large impact on existing systems, this section describes how an agency can avoid changes to its metadata framework when implementing the recommendations in the guideline.
	103
	104	Figure 5 below shows the process involved in a theoretical implementation when sending metadata from a metadata provider (ILO) to a collector (OECD) using an MSD for Labour statistics that was derived from the Global MCS:
	105
	106	[[image:1768483755029-207.jpeg]]
	107
	108	Figure 5: Mapping and transform processes in an SDMX metadata exchange using the Global MCS
	109
	110	Before starting the exchange, the provider (ILO) and collector (OECD) each identify a mapping to reuse, or create a mapping between their metadata frameworks and the MSD (which is derived from the Global MCS).
	111
	112	For each transmission, the metadata provider (ILO):
	113
	114	1. extracts the metadata from their metadata store;
	115	1. transcodes it to the Labour MSD structure using a mapping between their local structure and the Labour MSD, and;
	116	1. sends the resulting SDMX metadata message to the collector.
	117
	118	The metadata collector (OECD) then:
	119
	120	1. transcodes the received message (in the Labour MSD structure) to their local structure using their mapping;
	121	1. uploads the resulting metadata to their metadata system.
	122
	123	It is recommended to use SDMX Structure Set artefacts for the metadata mappings and make them available in the SDMX global registry. The advantage of using SDMX Structure Sets is that they are part of the SDMX Information Model and may be used in system implementation to convert the Global MCS structure to and from the local metadata frameworks.
	124
	125	The user stories below describe how the implementation can be made in more detail.
	126
	127	== Implementation User Stories ==
	128
	129	=== Statistical agency/dissemination/reporting perspective ===
	130
	131	A statistical agency wishes to disseminate its reference metadata using a standard that can be easily used by metadata collectors, and using a system and metadata framework that can be reused across statistical domains while avoiding manual processing, and the agency recognises that the Global MCS provides this. Achieving these goals with a unified standard and automated system will save the agency time and money.
	132
	133	The agency currently stores its reference metadata in a database and has an extraction method to create XML files from it. The agency carries out the following work in order to disseminate its metadata:
	134
	135	1. Create a mapping between the agency's existing metadata concepts and the Global MCS, or MSD derived from it. This mapping is an SDMX Structure Set (which is used to map concepts and codes in different structures) and is stored and shared in the agency's SDMX registry;
	136	1. create or adopt a system component that acts as a proxy to the existing agency's metadata component. The component does the following:
1.2	137	1*. a. takes input from the agency's metadata component (the agency's metadata XML);
	138	1. b. transforms* the input XML to SDMX (the agency's metadata framework);
	139	1. c. transcodes* the SDMX by applying the mapping created in step 1. The result is an SDMX metadata message that matches the Global MCS, or MSD;
	140	1*. d. outputs the resulting SDMX with an SDMX web service
1.1	141
	142	Later work could be considered for further efficiency gains:
	143
	144	* Change the agency's native metadata XML format to SDMX. This would avoid step 2b (transform);
	145	* align the agency's metadata framework to the Global MCS. This would avoid steps 1 (create mapping) and 2c (transcoding).
	146
	147	=== International organisation/collector perspective ===
	148
	149	An international organisation maintains many different systems and manual processes to collect and process metadata from its constituent agencies. A lot of time is spent extracting the metadata, some of it is missed, and mistakes are naturally made during the different manual processes. The organisation wishes to avoid these mistakes while saving time and money, maintain all of the different processes, while increasing the amount of metadata it can reuse, therefore allowing better interpretation of the statistical data.
	150
	151	The organisation stores its metadata in a production system. Many agencies provide their metadata by email, Word or Excel documents, and these are processed by several bespoke ETL processes that import the metadata into the production system. Other agencies publish metadata on their web sites, and the organisation's statisticians search the web sites and copy/paste the metadata into their production system.
	152
	153	The organisation carries out the following work in order to implement collection using the Global MCS:
	154
	155	1. Create a mapping between the Global MCS or MSD derived from it, and the organisation's metadata framework. This mapping is an SDMX Structure Set (which is used to map concepts and codes in different structures) and is stored and shared in the agency's SDMX registry;
	156	1. create or adopt a new system component that does the following:
	157	11. takes as input an SDMX metadata message that matches the Global MSC (or MSD);
	158	11. transcodes the SDMX by applying the mapping created in step 1. The result is an SDMX metadata message that matches the organisation's metadata framework;
	159	11. transforms the SDMX metadata message into the format understood by the organisation's metadata production system;
	160	11. imports the message into the organisation's metadata production system.
	161
	162	Later work could be considered for further efficiency gains:
	163
	164	* Add an SDMX import function to the organisation's metadata production system. This would avoid step 2c (transform);
	165	* align the organisation's metadata framework to a relevant subset of the Global Metadata Concept Scheme. This would avoid steps 1 (create mapping) and 2b (transcoding).
	166
	167	= MAINTENANCE OF THE GLOBAL METADATA CONCEPT SCHEME =
	168
2.1	169	The concepts in the Global MCS are a subset of the concepts in the SDMX Glossary{{footnote}}https://sdmx.org/wp-content/uploads/SDMX_Glossary_Version_2_0_October_2018.docx{{/footnote}} (which defines the entire cross-domain concept scheme). Therefore, changes or additions to reference metadata concepts in the SDMX Glossary will result in a revision to the Global MCS. Conversely, requests to change the Global MCS will be considered in future revisions of the SDMX Glossary.
1.1	170
	171	Requests to extend the Global MCS or change this guideline should be sent to the SDMX Statistical Working Group (swg@sdmx.org).
	172
	173	= CONCEPTS IN THE GLOBAL METADATA CONCEPT SCHEME =
	174
	175	== Associating Reference Metadata Concepts to SDMX Artefacts ==
	176
	177	The metadata content has to be associated or “attached” to SDMX artefacts in two ways by stating:
	178
	179	1. (in an MSD) the associated SDMX artefact type, e.g. Dataset; Dataflow; Provision agreement;
	180	1. the associated “level” within the artefact, e.g. for a Dataset: Dataset; Series; Observation.
	181
	182	These are some example attachments, others are possible:
	183
1.3	184	* the “Contact” concept may be attached to a Dataset artefact at the Dataset level;
	185	* the “Adjustment” concept may be attached to a Dataset artefact at the Series level;
	186	* the “Statistical population” concept may be attached to a Codelist artefact.
1.1	187
	188	This version of the proposal does not include an attachment recommendation for each concept. Recommended attachments may be provided in a future version of this guideline based on the feedback and forthcoming implementations. If you have any questions on how to attach reference metadata, please contact the SDMX Statistical Working Group (swg@sdmx.org).
	189
	190	== List of Reference Metadata Concepts ==
	191
	192	As said earlier, the reference metadata concepts are a subset of the concepts in the SDMX Glossary (which defines the entire cross-domain concept scheme). The usage context, some examples, related terms and other fields for each concept are available in the SDMX Glossary.
	193
	194	Some metadata concepts may not be listed in this version of the Global MCS (for example, detailed quality metadata). However, they may be proposed as candidate concepts to include in a future revision of the Global MCS and SDMX Glossary.
	195
	196	== Mutually exclusive character of some concepts ==
	197
	198	The Global MCS containing the full list of metadata concepts used by international organisations, some of these concepts have overlaps. In such cases, this will be indicated under the “Recommended usage” section. As an example, organisations summarising all contact information (e.g. name, address, mail, etc.) into one property will use the generic property “Contact” while others wanting a more structured way of presenting the contact information will use atomic properties such as “Contact name”, “Contact organisation”, “Contact email address”, etc. This means that “Contact” on the one hand and “Contact name”, “Contact organisation”, “Contact email address”, etc. on the other hand are mutually exclusive
	199
	200	=== ADMINISTRATIVE INFORMATION ===
	201
	202	\|Name\|Definition\|Concept ID
	203	\|Data source\|Location or service from where data or metadata can be obtained.\|DATA_SOURCE
	204	\|Compiling agency\|(((
	205	Organisation collecting and/or elaborating the data being reported.
	206	//Example usage: if an organisation receives data from a member agency and publishes it, the “Compiling agency” concept would be the member agency.//
	207	)))\|COMPILING_ORG
	208	\|Dissemination agency\|Organisation disseminating the data being reported.\|DISS_ORG
	209	\|Name\|Definition\|Concept ID
	210	\|Contact\|(((
	211	Individual or organisational contact points for the data or metadata.
	212	//Recommended usage. Use~://
	213
	214	* //either the summary “Contact” concept but not the granular “Contact xxx” concepts,//
	215	* //or the granular “Contact xxx” concepts but not the “Contact” concept.//
	216	)))\|CONTACT
	217	\|Contact email address\|E-mail address of the contact points for the data or metadata.\|CONTACT_EMAIL
	218	\|Contact fax number\|Fax number of the contact points for the data or metadata.\|CONTACT_FAX
	219	\|Contact mail address\|Postal address of the contact points for the data or metadata.\|CONTACT_MAIL
	220	\|Contact name\|Name of the contact points for the data or metadata.\|CONTACT_NAME
	221	\|Contact organisation\|(((
	222	Organisation of the contact point(s) for the data or metadata.
	223
	224	//Example usage: if an organisation receives data from a member agency and publishes it, the “Contact organisation” concept would usually be the publishing organisation.//
	225	)))\|CONTACT_ORGANISATION
1.3	226	\|Contact organisation unit\|Addressable subdivision of an organisation.\|ORGANISATION_UNIT
1.1	227	\|Contact person function\|(((
	228	Area of technical responsibility of the contact, such as “methodology”, “database management” or
	229
	230	“dissemination”.
	231	)))\|CONTACT_FUNCT
	232	\|Contact phone number\|Telephone number of the contact points for the data or metadata.\|CONTACT_PHONE
	233
	234	=== LEGAL AND INSTITUTIONAL ENVIRONMENT ===
	235
1.4	236	\|(% style="width:417px" %)Name\|(% style="width:1392px" %)Definition\|(% style="width:264px" %)Concept ID
	237	\|(% style="width:417px" %)Institutional mandate\|(% style="width:1392px" %)(((
1.1	238	Set of rules or other formal set of instructions assigning responsibility as well as the authority to an organisation for the collection, processing, and dissemination of statistics.
	239	//Recommended usage. Use~://
	240
	241	* //either the summary “Institutional mandate” concept but not the granular “Institutional mandate xxx” concepts,//
	242	* //or the granular “Institutional mandate xxx” concepts but not the “Institutional mandate” concept.//
1.4	243	)))\|(% style="width:264px" %)INST_MANDATE
	244	\|(% style="width:417px" %)Institutional mandate – data sharing\|(% style="width:1392px" %)Arrangements or procedures for data sharing and coordination between data producing agencies.\|(% style="width:264px" %)INST_MAN_SHAR
	245	\|(% style="width:417px" %)Institutional mandate – legal acts and other agreements\|(% style="width:1392px" %)Legal acts or other formal or informal agreements that assign responsibility as well as the authority to an Agency for the collection, processing, and dissemination of statistics.\|(% style="width:264px" %)INST_MAN_LA_OA
	246	\|(% style="width:417px" %)Confidentiality\|(% style="width:1392px" %)(((
1.1	247	Property of data indicating whether they are subject to dissemination restrictions.
	248	//Recommended usage. Use~://
	249
1.3	250	* //either the summary “Confidentiality” concept but not the granular “Confidentiality xxx” concepts,//
1.1	251	* //or the granular “Confidentiality xxx” concepts but not the “Confidentiality” concept.//
1.4	252	)))\|(% style="width:264px" %)CONF
	253	\|(% style="width:417px" %)Confidentiality - data treatment\|(% style="width:1392px" %)Rules applied for treating the Data Set to ensure that private information from individual units cannot be accessed and to prevent unauthorised disclosure.\|(% style="width:264px" %)CONF_DATA_TR
	254	\|(% style="width:417px" %)Confidentiality - policy\|(% style="width:1392px" %)Legislative measures or other formal procedures which prevent unauthorised disclosure of data that identify a person or economic entity either directly or indirectly.\|(% style="width:264px" %)CONF_POLICY
	255	\|(% style="width:417px" %)Professionalism\|(% style="width:1392px" %)(((
1.1	256	Standard, skill and ability suitable for producing statistics of good quality.
	257	//Recommended usage. Use~://
	258
1.4	259	* //either the summary “Professionalism” concept but not the granular “Professionalism xxx” concepts,//
1.1	260	* //or the granular “Professionalism xxx” concepts but not the “Professionalism” concept.//
1.4	261	)))\|(% style="width:264px" %)PROF
	262	\|(% style="width:417px" %)Professionalism - code of conduct\|(% style="width:1392px" %)Provisions for assuring the qualifications of staff and allowing staff to perform their functions without intervention motivated by non-statistical objectives.\|(% style="width:264px" %)PROF_COND
	263	\|(% style="width:417px" %)Professionalism - impartiality\|(% style="width:1392px" %)Elements providing assurances that statistics are developed, produced and disseminated in a neutral (impartial) manner, and that all users are given equal treatment.\|(% style="width:264px" %)PROF_IMP
	264	\|(% style="width:417px" %)Professionalism - methodology\|(% style="width:1392px" %)Elements providing assurances that the choices of sources and statistical techniques as well as decisions about dissemination are informed solely by statistical considerations.\|(% style="width:264px" %)PROF_METH
	265	\|(% style="width:417px" %)Professionalism - statistical commentary\|(% style="width:1392px" %)Elements providing assurances that the statistical entity is entitled to comment on erroneous interpretation and misuse of statistics.\|(% style="width:264px" %)PROF_STAT_COM
	266	\|(% style="width:417px" %)Name\|(% style="width:1392px" %)Definition\|(% style="width:264px" %)Concept ID
	267	\|(% style="width:417px" %)Cost and burden\|(% style="width:1392px" %)(((
1.1	268	Cost associated with the collection and production of a statistical product, as well as the burden imposed on respondents.
	269	//Recommended usage. Use~://
	270
	271	* //either the summary “Cost and burden” concept but not the granular “Cost and burden xxx” concepts,//
	272	* //or the granular “Cost and burden xxx” concepts but not the “Cost and burden” concept.//
1.4	273	)))\|(% style="width:264px" %)COST_BURDEN
	274	\|(% style="width:417px" %)Cost and burden - efficiency management\|(% style="width:1392px" %)Cost-benefit analysis, effectiveness of execution of medium term statistical programmes, and ensuring efficient use of resources.\|(% style="width:264px" %)COST_BURDEN_EFF
	275	\|(% style="width:417px" %)Cost and burden – resources\|(% style="width:1392px" %)Metadata element providing assurances that staff, facilities, computing resources, and financing to undertake statistical production are commensurate with statistical programs.\|(% style="width:264px" %)COST_BURDEN_RES
1.1	276
	277	=== SCOPE ===
	278
1.4	279	\|(% style="width:416px" %)Name\|(% style="width:1394px" %)Definition\|Concept ID
	280	\|(% style="width:416px" %)Statistical population\|(% style="width:1394px" %)Total membership or population or “universe” of a defined class of people, objects or events.\|STAT_POP
	281	\|(% style="width:416px" %)Reference area\|(% style="width:1394px" %)Country or geographic area to which the measured statistical phenomenon relates.\|REF_AREA
	282	\|(% style="width:416px" %)Coverage\|(% style="width:1394px" %)(((
1.1	283	Definition of the scope of the data compiled.
	284	//Recommended usage. Use~://
	285
	286	* //either the summary “Coverage” concept but not the granular “xxx coverage” concepts and/or “Economic sector” concept,//
	287	* //or the granular “xxx coverage” concepts and/or “Economic sector” but not the “Coverage” concept.//
	288	)))\|COVERAGE
1.4	289	\|(% style="width:416px" %)Name\|(% style="width:1394px" %)Definition\|Concept ID
	290	\|(% style="width:416px" %)Geographical coverage\|(% style="width:1394px" %)(((
1.1	291	Characterisation of the statistical units according to geographical criteria.
	292	//Example usage: May exclude small parts of the national territory amounting to no more than 2% of the national population and the national territories.//
	293	)))\|COVERAGE_GEO
1.4	294	\|(% style="width:416px" %)Population coverage\|(% style="width:1394px" %)Definition of the main types of population covered by the statistics.\|COVERAGE_POP
	295	\|(% style="width:416px" %)Sector coverage\|(% style="width:1394px" %)Sector(s) covered by the statistics.\|COVERAGE_SECTOR
	296	\|(% style="width:416px" %)Economic sector\|(% style="width:1394px" %)High-level grouping of economic activities based on the types of goods and services produced.\|ECO_SECTOR
	297	\|(% style="width:416px" %)Time coverage\|(% style="width:1394px" %)Period of time for which data are provided.\|COVERAGE_TIME
1.1	298
	299	=== METHODOLOGICAL INFORMATION ===
	300
	301	//Data presentation//
	302
1.4	303	\|(% style="width:411px" %)Name\|(% style="width:1399px" %)Definition\|(% style="width:263px" %)Concept ID
	304	\|(% style="width:411px" %)Data description\|(% style="width:1399px" %)Metadata element describing the main characteristics of the Data Set in an easily understandable manner, referring to the main data and indicators disseminated.\|(% style="width:263px" %)DATA_DESCR
1.1	305
	306	//Other Methodological Information//
	307
1.4	308	\|(% style="width:408px" %)Name\|(% style="width:1403px" %)Definition\|(% style="width:261px" %)Concept ID
	309	\|(% style="width:408px" %)Source data type\|(% style="width:1403px" %)Characteristics and components of the raw statistical data used for compiling statistical aggregates.\|(% style="width:261px" %)SOURCE_TYPE
	310	\|(% style="width:408px" %)Data collection method\|(% style="width:1403px" %)Method applied for gathering data for official statistics.\|(% style="width:261px" %)COLL_METHOD
	311	\|(% style="width:408px" %)Reference period\|(% style="width:1403px" %)Timespan or point in time to which the measured observation is intended to refer.\|(% style="width:261px" %)REF_PERIOD
	312	\|(% style="width:408px" %)Base period\|(% style="width:1403px" %)Period of time used as the base of an index number, or to which a constant series refers.\|(% style="width:261px" %)BASE_PER
1.1	313
	314
	315
1.4	316	\|(% style="width:411px" %)Name\|(% style="width:1401px" %)Definition\|(% style="width:260px" %)Concept ID
	317	\|(% style="width:411px" %)Base weight\|(% style="width:1401px" %)Weights of a weighting system for an index number computed according to the information relating to the base period instead, for example, of the current period.\|(% style="width:260px" %)BASE_WEIGHT
	318	\|(% style="width:411px" %)Frequency of observation\|(% style="width:1401px" %)Time interval at which observations occur over a given time period.\|(% style="width:260px" %)FREQ
	319	\|(% style="width:411px" %)Frequency of data collection\|(% style="width:1401px" %)Time interval at which the source data are collected.\|(% style="width:260px" %)FREQ_COLL
	320	\|(% style="width:411px" %)Classification system\|(% style="width:1401px" %)Metadata element used to a) list the classification(s) being used for a given Data Set or set of Data Sets, and b) describe how these conform to internationally agreed standards, guidelines, or good practices.\|(% style="width:260px" %)CLASS_SYSTEM
	321	\|(% style="width:411px" %)Statistical concepts and definitions\|(% style="width:1401px" %)Definitions and descriptions of the main variables provided.\|(% style="width:260px" %)STAT_CONC_DEF
	322	\|(% style="width:411px" %)Statistical unit\|(% style="width:1401px" %)Entity for which information is sought and for which statistics are ultimately compiled.\|(% style="width:260px" %)STAT_UNIT
	323	\|(% style="width:411px" %)Unit of measure\|(% style="width:1401px" %)Unit in which the data values are expressed.\|(% style="width:260px" %)UNIT_MEASURE
	324	\|(% style="width:411px" %)Accounting conventions\|(% style="width:1401px" %)Practical procedures, standards and other aspects used when compiling data from diverse sources under a common methodological framework.\|(% style="width:260px" %)ACC_CONV
	325	\|(% style="width:411px" %)Valuation\|(% style="width:1401px" %)Definition of the price per unit, for goods and services flows and asset stocks.\|(% style="width:260px" %)VALUATION
1.1	326
	327	=== STATISTICAL PROCESSING ===
	328
1.5	329	\|(% style="width:415px" %)Name\|(% style="width:1400px" %)Definition\|(% style="width:257px" %)Concept ID
	330	\|(% style="width:415px" %)Data compilation\|(% style="width:1400px" %)Operations performed on data to derive new information according to a given set of rules.\|(% style="width:257px" %)DATA_COMP
	331	\|(% style="width:415px" %)Adjustment\|(% style="width:1400px" %)(((
1.1	332	Set of procedures employed to modify statistical data to enable it to conform to national or international standards or to address data quality differences when compiling specific Data Sets.
	333	//Recommended usage. Use~://
	334
	335	* //either the summary “Adjustment” concept but not the granular “xxx adjustment” concepts,//
	336	* //or the granular “xxx adjustment” concepts but not the “Adjustment” concept.//
1.5	337	)))\|(% style="width:257px" %)ADJUSTMENT
	338	\|(% style="width:415px" %)Price adjustment\|(% style="width:1400px" %)Statistical technique used to remove the effects of price influences operating on a data series.\|(% style="width:257px" %)PRICE_ADJUST
	339	\|(% style="width:415px" %)Seasonal adjustment\|(% style="width:1400px" %)Statistical technique used to remove the effects of seasonal and calendar influences operating on a data series.\|(% style="width:257px" %)SEASONAL_ADJUST
	340	\|(% style="width:415px" %)Data validation\|(% style="width:1400px" %)Process of monitoring the results of data compilation and ensuring the quality of the statistical results.\|(% style="width:257px" %)DATA_VALIDATION
	341	\|(% style="width:415px" %)Data revision\|(% style="width:1400px" %)(((
1.1	342	Change in a value of a statistic released to the public.
	343	//Recommended usage. Use~://
	344
	345	* //either the summary “Data revision” concept but not the granular “Data revision xxx” concepts,//
	346	* //or the granular “Data revision xxx” concepts but not the “Data revision” concept.//
1.5	347	)))\|(% style="width:257px" %)DATA_REV
	348	\|(% style="width:415px" %)Data revision - policy\|(% style="width:1400px" %)Policy aimed at ensuring the transparency of disseminated data, whereby preliminary data are compiled that are later revised.\|(% style="width:257px" %)REV_POLICY
	349	\|(% style="width:415px" %)Data revision - practice\|(% style="width:1400px" %)Information on the data revision practice.\|(% style="width:257px" %)REV_PRACTICE
	350	\|(% style="width:415px" %)Data revision - studies\|(% style="width:1400px" %)Information about data revision studies and analyses.\|(% style="width:257px" %)REV_STUDY
	351	\|(% style="width:415px" %)Imputation\|(% style="width:1400px" %)Procedure for entering a value for a specific data item where the response is missing or unusable.\|(% style="width:257px" %)IMPUTATION
	352	\|(% style="width:415px" %)Imputation rate\|(% style="width:1400px" %)Ratio of the number of replaced values to the total number of values for a given variable.\|(% style="width:257px" %)IMPUTATION_RATE
1.1	353
	354	=== QUALITY ===
	355
1.5	356	\|(% style="width:418px" %)Name\|(% style="width:1401px" %)Definition\|(% style="width:253px" %)Concept ID
	357	\|(% style="width:418px" %)Quality management\|(% style="width:1401px" %)(((
1.1	358	Systems and frameworks in place within an organisation to manage the quality of statistical products and processes.
	359	//Recommended usage. Use~://
	360
	361	* //either the summary “Quality management” concept but not the granular “Quality management xxx” concepts,//
	362	* //or the granular “Quality management xxx” concepts but not the “Quality management” concept.//
1.5	363	)))\|(% style="width:253px" %)QUALITY_MGMNT
	364	\|(% style="width:418px" %)Quality management - quality assessment\|(% style="width:1401px" %)Overall evaluation of data quality, based on standard quality criteria.\|(% style="width:253px" %)QUALITY_ASSMNT
	365	\|(% style="width:418px" %)Quality management - quality assurance\|(% style="width:1401px" %)Guidelines focusing on quality in general and dealing with quality of statistical programmes, including measures for ensuring the efficient use of resources.\|(% style="width:253px" %)QUALITY_ASSURE
	366	\|(% style="width:418px" %)Quality management - quality documentation\|(% style="width:1401px" %)Documentation on procedures applied for quality management and quality assessment.\|(% style="width:253px" %)QUALITY_DOC
1.1	367
	368
	369
1.5	370	\|(% style="width:419px" %)Name\|(% style="width:1402px" %)Definition\|(% style="width:252px" %)Concept ID
	371	\|(% style="width:419px" %)Accuracy\|(% style="width:1402px" %)(((
1.1	372	Closeness of computations or estimates to the unknown exact or true values that the statistics were intended to measure.
	373	//Recommended usage. Use~://
	374
	375	* //either the summary “Accuracy” concept but not the granular “Accuracy - overall”, “Non-sampling error” or “Sampling error” concepts,//
	376	* //or the granular “Accuracy - overall”, “Non-sampling error” or “Sampling error” concepts but not the “Accuracy” concept.//
1.5	377	)))\|(% style="width:252px" %)ACCURACY
	378	\|(% style="width:419px" %)Accuracy - overall\|(% style="width:1402px" %)Assessment of accuracy, linked to a certain Data Set or domain, which is summarising the various components into one single measure.\|(% style="width:252px" %)ACCURACY_OVERALL
	379	\|(% style="width:419px" %)Sampling error\|(% style="width:1402px" %)Part of the difference between a population value and an estimate thereof, derived from a random sample, which is due to the fact that only a subset of the population is enumerated.\|(% style="width:252px" %)SAMPLING_ERR
	380	\|(% style="width:419px" %)Non-sampling error\|(% style="width:1402px" %)Error in sample estimates which cannot be attributed to sampling fluctuations.\|(% style="width:252px" %)NONSAMPLING_ERR
	381	\|(% style="width:419px" %)Coverage error\|(% style="width:1402px" %)Error caused by a failure to cover adequately all components of the population being studied, which results in differences between the target population and the sampling frame.\|(% style="width:252px" %)COVERAGE_ERR
	382	\|(% style="width:419px" %)Measurement error\|(% style="width:1402px" %)Error in reading, calculating or recording a numerical value.\|(% style="width:252px" %)MEASUREMENT_ERR
	383	\|(% style="width:419px" %)Non-response error\|(% style="width:1402px" %)Error that occurs when the survey fails to get a response to one, or possibly all, of the questions.\|(% style="width:252px" %)NONRESPONSE_ERR
	384	\|(% style="width:419px" %)Processing error\|(% style="width:1402px" %)Error in final survey results arising from the faulty implementation of correctly planned implementation methods.\|(% style="width:252px" %)PROCESSING_ERR
1.1	385
1.5	386	\|(% style="width:418px" %)Model assumption error\|(% style="width:1402px" %)Error that occurs due the use of methods, such as calibration, generalised regression estimator, calculation based on full scope or constant scope, benchmarking, seasonal adjustment and other models not included in other accuracy components, in order to calculate statistics or indexes.\|(% style="width:252px" %)MODEL_ASSUMP_ERR
	387	\|(% style="width:418px" %)Coherence\|(% style="width:1402px" %)(((
1.1	388	Adequacy of statistics to be reliably combined in different ways and for various uses.
	389	//Recommended usage. Use~://
	390
1.5	391	* //either the summary “Coherence” concept but not the granular “Coherence xxx” concepts,//
1.1	392	* //or the granular “Coherence xxx” concepts but not the “Coherence” concept.//
1.5	393	)))\|(% style="width:252px" %)COHERENCE
	394	\|(% style="width:418px" %)Coherence - cross domain\|(% style="width:1402px" %)Extent to which statistics are reconcilable with those obtained through other Data Sources or statistical domains.\|(% style="width:252px" %)COHER_X_DOM
	395	\|(% style="width:418px" %)Coherence - internal\|(% style="width:1402px" %)Extent to which statistics are consistent within a given Data Set.\|(% style="width:252px" %)COHER_INTERNAL
	396	\|(% style="width:418px" %)Comparability\|(% style="width:1402px" %)(((
1.1	397	Extent to which differences between statistics can be attributed to differences between the true values of the statistical characteristics.
	398	//Recommended usage. Use~://
	399
1.5	400	* //either the summary “Comparability” concept but not the granular “Comparability xxx” concepts,//
1.1	401	* //or the granular “Comparability xxx” concepts but not the “Comparability” concept.//
1.5	402	)))\|(% style="width:252px" %)COMPARABILITY
	403	\|(% style="width:418px" %)Comparability - geographical\|(% style="width:1402px" %)Extent to which statistics are comparable between geographical areas.\|(% style="width:252px" %)COMPAR_GEO
	404	\|(% style="width:418px" %)Comparability - over time\|(% style="width:1402px" %)Extent to which statistics are comparable or reconcilable over time.\|(% style="width:252px" %)COMPAR_TIME
1.1	405
1.6	406	\|(% style="width:418px" %)Name\|(% style="width:1403px" %)Definition\|(% style="width:252px" %)Concept ID
	407	\|(% style="width:418px" %)Punctuality\|(% style="width:1403px" %)Time lag between the actual delivery of the data and the target date when it should have been delivered.\|(% style="width:252px" %)PUNCTUALITY
	408	\|(% style="width:418px" %)Relevance\|(% style="width:1403px" %)(((
1.1	409	Degree to which statistical information meets the real or perceived needs of clients.
	410	//Recommended usage. Use~://
	411
1.6	412	* //either the summary “Relevance” concept but not the granular “Relevance xxx” concepts,//
1.1	413	* //or the granular “Relevance xxx” concepts but not the “Relevance” concept.//
1.6	414	)))\|(% style="width:252px" %)RELEVANCE
	415	\|(% style="width:418px" %)Relevance - completeness\|(% style="width:1403px" %)Extent to which all statistics that are needed are available.\|(% style="width:252px" %)COMPLETENESS
	416	\|(% style="width:418px" %)Relevance - user needs\|(% style="width:1403px" %)Description of requirements with respect to the statistical output.\|(% style="width:252px" %)USER_NEEDS
	417	\|(% style="width:418px" %)Relevance - user satisfaction\|(% style="width:1403px" %)Description of how well the disseminated statistics meet the expressed user needs.\|(% style="width:252px" %)USER_SAT
	418	\|(% style="width:418px" %)Timeliness\|(% style="width:1403px" %)(((
2.1	419	Length of time between data availability and the event or phenomenon they describe.
1.1	420	//Recommended usage. Use~://
	421
1.6	422	* //either the summary “Timeliness” concept but not the granular “Timeliness xxx” concepts,//
1.1	423	* //or the granular “Timeliness xxx” concepts but not the “Timeliness” concept.//
1.6	424	)))\|(% style="width:252px" %)TIMELINESS
	425	\|(% style="width:418px" %)Timeliness - source data\|(% style="width:1403px" %)Time between the end of a reference period and actual receipt of the data by the compiling agency.\|(% style="width:252px" %)TIME_SOURCE
1.1	426
	427	=== DISSEMINATION ===
	428
1.6	429	\|(% style="width:417px" %)Name\|(% style="width:1407px" %)Definition\|(% style="width:248px" %)Concept ID
	430	\|(% style="width:417px" %)Release policy\|(% style="width:1407px" %)(((
1.1	431	Rules for disseminating statistical data to interested parties.
	432	//Recommended usage. Use~://
	433
	434	* //either the summary “Release policy” concept but not the granular “Release policy xxx” concepts,//
	435	* //or the granular “Release policy xxx” concepts but not the “Release policy” concept.//
1.6	436	)))\|(% style="width:248px" %)REL_POLICY
	437	\|(% style="width:417px" %)Release policy - release calendar\|(% style="width:1407px" %)Schedule of statistical release dates.\|(% style="width:248px" %)REL_CAL_POLICY
	438	\|(% style="width:417px" %)Release policy - release calendar access\|(% style="width:1407px" %)Description of how the release calendar can be accessed.\|(% style="width:248px" %)REL_CAL_ACCESS
	439	\|(% style="width:417px" %)Release policy - transparency\|(% style="width:1407px" %)Statement describing whether and how the release policy is disseminated to the public.\|(% style="width:248px" %)REL_POL_TRA
	440	\|(% style="width:417px" %)Release policy - user access\|(% style="width:1407px" %)Policy for release of the data to users, scope of dissemination (e.g. to the public, to selected users), how users are informed that the data are being released, and whether the policy determines the dissemination of statistical data to all users.\|(% style="width:248px" %)REL_POL_US_AC
	441	\|(% style="width:417px" %)Frequency of dissemination\|(% style="width:1407px" %)Time interval at which the statistics are disseminated over a given time period.\|(% style="width:248px" %)FREQ_DISS
	442	\|(% style="width:417px" %)Dissemination format\|(% style="width:1407px" %)(((
1.1	443	Media by which statistical data and metadata are disseminated.
	444	//Recommended usage. Use~://
	445
	446	* //either the summary “Dissemination format” concept but not the granular “Dissemination format xxx” concepts,//
1.6	447	* //or the granular “Dissemination format xxx” concepts but not the “Dissemination format” concept.//
	448	)))\|(% style="width:248px" %)DISS_FORMAT
	449	\|(% style="width:417px" %)Dissemination format - microdata access\|(% style="width:1407px" %)Information on whether microdata are also disseminated.\|(% style="width:248px" %)MICRO_DAT_ACC
	450	\|(% style="width:417px" %)Dissemination format - news release\|(% style="width:1407px" %)Regular or ad-hoc press releases linked to the data.\|(% style="width:248px" %)NEWS_REL
1.1	451
2.1	452	\|(% style="width:422px" %)Name\|(% style="width:1407px" %)Definition\|(% style="width:244px" %)Concept ID
	453	\|(% style="width:422px" %)Dissemination format - online database\|(% style="width:1407px" %)Information about on-line databases in which the disseminated data can be accessed.\|(% style="width:244px" %)ONLINE_DB
	454	\|(% style="width:422px" %)Dissemination format - publications\|(% style="width:1407px" %)Regular or ad-hoc publications in which the data are made available to the public.\|(% style="width:244px" %)PUBLICATIONS
	455	\|(% style="width:422px" %)Dissemination format - other formats\|(% style="width:1407px" %)References to the most important other data dissemination done.\|(% style="width:244px" %)DISS_OTHER
	456	\|(% style="width:422px" %)Documentation on methodology\|(% style="width:1407px" %)Descriptive text and references to methodological documents available.\|(% style="width:244px" %)DOC_METHOD
	457	\|(% style="width:422px" %)Documentation on methodology - advance notice\|(% style="width:1407px" %)Policy on notifying the public of changes in methodology, indicating whether the public is notified before a methodological change affects disseminated data and, if so, how long before.\|(% style="width:244px" %)ADV_NOTICE
	458	\|(% style="width:422px" %)Recommended uses and limitations\|(% style="width:1407px" %)Metadata element guiding users with limited knowledge of the statistics presented and helping them determine whether the product meets their requirements.\|(% style="width:244px" %)REC_USE_LIM
1.1	459
	460	=== MISCELLANEOUS ===
	461
2.1	462	\|(% style="width:423px" %)Name\|(% style="width:1405px" %)Definition\|(% style="width:244px" %)Concept ID
	463	\|(% style="width:423px" %)Metadata update\|(% style="width:1405px" %)(((
1.1	464	Date on which the metadata element was created or modified.
	465	//Recommended usage. Use~://
	466
	467	* //either the summary “Metadata update” concept but not the granular “Metadata update xxx” concepts,//
	468	* //or the granular “Metadata update xxx” concepts but not the “Metadata update” concept.//
2.1	469	)))\|(% style="width:244px" %)META_UPDATE
	470	\|(% style="width:423px" %)Metadata update - last certified\|(% style="width:1405px" %)Date of the latest certification provided by the domain manager to confirm that the metadata posted are still up-to-date, even if the content has not been amended.\|(% style="width:244px" %)META_CERTIFIED
	471	\|(% style="width:423px" %)Metadata update - last posted\|(% style="width:1405px" %)Date of the latest dissemination of the metadata.\|(% style="width:244px" %)META_POSTED
	472	\|(% style="width:423px" %)Metadata update - last update\|(% style="width:1405px" %)Date of last update of the content of the metadata.\|(% style="width:244px" %)META_LAST_UPDATE
	473	\|(% style="width:423px" %)Comment\|(% style="width:1405px" %)Descriptive text which can be attached to data or metadata.\|(% style="width:244px" %)COMMENT
	474	\|(% style="width:423px" %)Technical information\|(% style="width:1405px" %)Technical details related to the data, for example the storage system used, or technical systems related to the exchange.\|(% style="width:244px" %)TECH_INFO
1.1	475
	476	----
	477
	478	{{putFootnotes/}}