5b. SDMX and reference metadata: guideline examples Bogdan ZDRENTU Eurostat Unit B5: “Central data and metadata services” SDMX Basics course, 27-29 October 2015

Guidelines for recording reference metadata according to ESMS

The Euro SDMX Metadata Structure (ESMS)

Guidelines for recording and disseminating metadata ESMS is currently to be used for dissemination of metadata on the web and therefore rather user- oriented. The information in ESMS is to be more synthesised compared to a comprehensive quality report according to the ESS Standard for Quality Reports (ESQRS).

Guidelines for recording and disseminating metadata Practical Guidelines for reporting on reference metadata are provided by the EURO-SDMX Metadata Structure which contains the concept names, concept codes, short "Descriptions" and "ESS Guidelines" on what is to be reported a supporting document "Good Practices for reference metadata in ESMS" which is available in the application ESS MH

The Euro SDMX Metadata Structure (ESMS)

Attachment level  Maintenance burden at an acceptable level! When many tables or datasets are produced on the basis of one statistical survey or data source, it is recommended that only one (identical) ESMS file is used. If a large part of information is repeated in a number of ESMS files, the production unit should try to upgrade the attachment levels of these files towards a higher one.

Timeliness The concepts in ESMS files should be checked at least once per year or more frequent if e.g. the data quality has deteriorated or improved or if more reporting on data quality is feasible. If data quality reports or other information on data are available, this information should be included into the ESMS. Generally, some information should be provided for each concept.

Completeness The information in ESMS is to be more synthesised and concise compared to a comprehensive quality report. But if e.g. no data quality reports or other information is available, at least basic information should be inserted. Hyperlinks and attachments of central documents are helpful in order to provide complementary sources for further detailed information.

Completeness Information not available or not applicable If no information is available this should be flagged as "Not available". An indication on the plans to provide e.g. quality related information in the future should be included, though. If a concept is not relevant it should be indicated as "Not applicable".

Examples – how it should not be…

"Not available" and "Not applicable"

Metadata update

Completeness of information I

Completeness of information II

References to other sources & documents I

References to other sources & documents II

Annexes and Titles

Guidelines: sum up Keep the maintenance burden at an acceptable level and make sure that each dataset is covered by reference metadata. The metadata should be up-to-date and the user should be informed about that. Make use of standardised set phrases when no information can be provided. Give as much information as possible, but as concise as possible at the same time. Check on the accessibility and clarity of provided links and attached annexes.

Questions?