Technical specifications for file export and import to ESS-MH

TECHNICAL SPECIFICATIONS FOR FILE EXPORT AND IMPORT TO ESS-MH

• 1. Introduction
• 2. Export options: MSD and Metadata files
• 3. Import options: Import Metadata files to ESS MH
  • 3.1 "SDMX" zip file
  • 3.2 "Excel" zip file
• 4. SDMX-ML file
  • 4.1 <Header> tag
  • 4.2 <MetadataSet> tag
    • 4.2.1 <TargetValues>
    • 4.2.2 Reported Metadata Attributes - The concepts and their values
    • 4.2.3 Annexes
    • 4.2.4 Publication flags and Restriction flags
• 5. xlsx file 
  • 5.1 Metadata - "Header" section
  • 5.2 Metadata "Concepts" section 
    • 5.2.1 Concept values
    • 5.2.2 Restricted for publication flag (at the concepts level)
  • 5.3 Parameters
  • 5.4 Annexes
• 6. Guidelines
  • 6.1 SDMX-ML file - specifics for "Guidelines"
    • 6.1.1 <Header> tag
    • 6.1.2 <MetadataSet> tag
      • 6.1.2.1 <TargetValues>
      • 6.1.2.2 Reported Metadata Attributes - The concepts and their values
      • 6.1.2.3 Annotations
  • 6.2 Excel file - specifics for "Guidelines"
    • 6.2.1 Metadata - "Header" section
    • 6.2.2 Metadata "Concepts" section 
    • 6.2.3 Parameters

1. Introduction

This document provides explanations about the

• Export options for retrieving of metadata files and MSDs from various tools and databases (in SDMX-ML 3.0 format)
• And particularly import features in ESS-MH for SDMX-ML 3.0 files  and Excel files to create or edit metadata files and Guidelines, along with extra annotations used to represent functionalities specific to the ESS-MH application.

These annotations cover the following subjects:

• Importation of concept values of various representation types
• Images
• Annexes – at the concepts level & global
• Publication flag (for the whole metadata file)
• Restricted for publication flag (at the concepts level)
• Editability of concepts

A metadata file can be exchanged by:

Using only an SDMX-ML 3.0 file if there is no annex and no image,

• Should follow the SDMX standard (with a <header> and specific tags…)
• Including the content itself following a valid MSD (Metadata Structure Definition, defining especially the reported concepts and its structure).

Using only an xlsx file if there is no annex and no image,

• Should follow a certain template complying with the SDMX standard
• Including the content itself following a valid MSD (Metadata Structure Definition, defining especially the reported concepts and its structure).

Using a zip file

• "SDMX" zip file (necessary if the file refers to annexes or images). Such an "SDMX" zip file should have a specific structure and contain an SDMX-ML file.
• "Excel" zip file (necessary if the file refers to annexes or images). Such an "Excel" zip file should have a specific structure and contain an xlsx file.

Until the end of 2025 the ESS-MH will also allow the import and export of files in SDMX-ML 2.0 format. Instructions for exports and imports of Metadata files in format SDMX 2.0 can be retrieved from CircaBC. 

2. Export options: MSD and Metadata files

Each metadata and quality report is described by an SDMX Metadata Structure Definition (MSD), and all Metadata Structure Definitions are publicly available in the Euro-SDMX Registry. The MSDs detail which concept IDs must be used and the structure the SDMX-ML file must have to be considered acceptable.

If you are not sure about the underlying MSD in use for a metadata or quality report, you may go to the ESS-MH and make sure that you select the “MSD” to be displayed in the metadata file overview or consult the Metadata flows report (accessible to Super Providers only).  

and

You may receive information on the MSD used for a specific metadata or quality reporting by exporting/downloading. To download the MSD, you have three options:

1. from the Euro-SDMX Registry, where you can download the MSD specifically (and you can find further referenced artefacts there, such as Concept Scheme and Code Lists);
2. from the ESS-MH, where you can download the metadata file, compressed in a zip file containing the MSD (and information on the Concepts and Code lists used), the metadata file itself and referenced documents, if any;
3. from the Eurostat website - Data Navigation Tree, Data Browser, Data Explorer and bulk down facility, where you can retrieve published zip files containing the metadata file itself and the MSD and Eurostat's new data navigation tree using the Data Browser. 

1. In the new Euro-SDMX Registry, at Metadata > Metadata Structures, search for the concerned MSD and click on the button “Export SDMX-ML 3.0”.

Alternatively, go to Export Structures > Metadata Structures, search for the concerned MSD(s) and click on the button “Download Selected Structures”.

Further selections are possible, such as the desired SDMX-ML format v3.0, or v2.1 and whether to include Descendants (referenced structures) etc.

2. You can go to the ESS-MH, go to the specific report you are interested in and click on Download. A pop-up will appear where you may select the desired SDMX format; by default it is set to 3.0, but you may also opt for 2.0. The download will include, among others, the MSD and the SDMX-ML version of the metadata or quality report in the selected SDMX format. 

3. From the Data Navigation Tree, you can retrieve Published files (currently in SDMX format2.0)

• via the HTML file accessible through the M-icon or  

Or the Data Browser

• directly from the published dataset 

• or following the modernised design

  

  Or

• Data Browser - Bulk download

   

  

3. Import options: Import Metadata files to ESS-MH

At present, the most common way how to import metadata files to the ESS-MH is "manually" by logging in and going to the "Import" section:

"Browse" the file you would like to import, and click "Import".
The application will automatically detect the SDMX format of the imported metadata file, that is either 3.0 or 2.0, hence no further specification is required from the user for importing a metadata file. 
A green success message, or a red error message with some indication will be returned consequently. 
Furthermore, efforts have been made to facilitate automated metadata file transmissions via EDAMIS without the need to login to the ESS-MH user interface. If you are interested in such transmission method, please reach out to ESTAT-DATA-METADATA-SERVICES@ec.europa.eu

3.1 "SDMX" zip file

It should be used when the metadata file refers to annexes or images.
In ESS-MH the files used to be called like xx.sdmx.zip (where xx is the name of the metadata file). Note that the file to be imported can have a different name, as long as the extension .sdmx.zip is kept.
Example: DMBB_SIMS_A_4D_2020_0000.sdmx.zip.
 

This zip file contains:

• One SDMX-ML file named xx.sdmx.xml (where xx is preferably the metadata file name)
  In our case: DMBB_SIMS_A_4D_2020_0000.sdmx.xml
• If there are annexes, one directory Annexes/ containing one file per annex:
  • Each annex is named like xx_an_nn.ext where:
    •  xx is the metadata file name,
    • nn is a sequential number starting from 1 or a customised name suffix,
    • ext is the extension of the annex according to the type of document.
      Example: DMBB_SIMS_A_4D_2020_0000_an_1.xlsx, DMBB_SIMS_A_4D_2020_0000_an_2.docx
  • Each annex should have a reference in the SDMX-ML file (like "Annexes/xx_an_nn.ext").
  • Note that you can put your own name (instead of xx_an_nn), but you should keep the extension, put the file in the "Annexes" directory, and refer to it in the SDMX-ML file by using "Annexes/YourOwnName.ext".
• If there are images, one directory Images/ containing one file per image:
  • Each image is named like xx_imgnn.ext (where xx is the metadata file name, nn is a number starting from 1, ext is the extension of the image).
    Example: DMBB_SIMS_A_4D_2020_0000_img1.png
  • Each image should have a reference in the SDMX-ML file.
  • Note that you can put your own name (instead of xx_imgnn), but you should keep the extension, put the file in the "Images" directory, and refer to it in the SDMX-ML file by using "Images/YourOwnName.ext".
• Not actually required, but can be inserted optionally: 
  • one MSD file (in SDMX-ML format) named yy.msd.xml (where yy is the name of the MSD in the SDMX registry).
    Example: SIMS_MSD.msd.xml
  • DSD file(s) (in SDMX-ML format) named as zz.xml. The DSDs are the basis for validating the structure of tabular files of type FILE_DSD, and they are stored in the ESS-MH, hence do not need to, but may be imported along with the FILE_DSD / structure .xlsx file.

For annexes, all formats are available but keep in mind that every person should be able to open it and sometimes might need a specific application to open them. Therefore, we propose to use "standard" files like PDF, XLSX, DOCX, jpg, png for example.

For images, JPEG (.jpg) is probably the lightest format but .png, .gif and .bmp are also accepted.

Currently there is a limit for the zip file of 10 MB.

3.2 "Excel" zip file

It should be used when the metadata file refers to annexes or images.

In ESS-MH we are used to call the file like xx.xlsx.zip (where xx is the name of the metadata file). Note that the file to be imported can have a different name, as long as the extension .xlsx.zip is kept.

Example: DMBB_SIMS_A_4D_2020_0000.xlsx.zip

This zip file contains:

• One xlsx file named xx.xlsx (where xx is preferably the metadata file name)
  In our case: DMBB_SIMS_A_4D_2020_0000.xlsx
• If there are annexes, one directory Annexes/ containing one file per annex:
  • Each annex is named like xx_an_nn.ext, where:
    • xx is the metadata file name,
    • nn is a number starting from 1 or a customised name suffix,
    • ext is the extension of the annex according to the type of document).
      Example: DMBB_SIMS_A_4D_2020_0000_an1.xlsx, DMBB_SIMS_A_4D_2020_0000_an2.docx
  • Each annex should have a reference in the xlsx file (like "Annexes/xx_an_nn.ext").
  • Note that you can put your own name (instead of xx_an_nn), but you should keep the extension, put the file in the "Annexes" directory, and refer to it in the xlsx file by using "Annexes/YourOwnName.ext".
• If there are images, one directory Images/ containing one file per image:
  • Each image is named like xx_imgnn.ext (where xx is the metadata file name, nn is a number starting from 1, ext is the extension of the image).
    Example: DMBB_SIMS_A_4D_2020_0000_img1.png
  • Each image should have a reference in the xlsx file.
  • Note that you can put your own name (instead of xx_imgnn), but you should keep the extension, put the file in the "Images" directory, and refer to it in the xlsx file by using "Images/YourOwnName.ext".
• Not actually required, but can be inserted optionally:  
  • one MSD file (in SDMX-ML format) named yy.msd.xml (where yy is the name of the MSD in the SDMX registry).
    Example: SIMS_MSD.msd.xml
  • Folder DSDs including the DSD file(s) (in SDMX-ML format) named as zz.xml. The DSDs are the basis for validating the structure of tabular files of type FILE_DSD, and they are stored in ESS-MH, hence do not need to, but may be imported along with the FILE_DSD / structured .xlsx file.

For annexes, all formats are available but keep in mind that every person should be able to open it and sometimes might need a specific program to open them. Therefore, we propose to use "standard" files like PDF, XLSX, DOCX, jpg, png for example.

For images, JPEG (.jpg) is probably the lightest format but .png, .gif and .bmp are also accepted.

Currently there is a limit for the zip file of 10 MB.

4. SDMX-ML file

In order to retrieve the correct template for the SDMX-ML used for the import, it is advised to download first an example file from ESS-MH, conveniently from a report based on the same MSD/typology.

The name of the file to be prepared for the import is like xx.sdmx.xml (where xx is preferably the metadata file name)
Example: DMBB_SIMS_A_4D_2020_0000.sdmx.xml

4.1 <Header> tag

The <Header> is mandatory and should contain all the tags presented in the example.

Some of the tags in the <Header> are mandatory to contain a value,

4.2 <MetadataSet> tag

The <MetadataSet> tag depends completely on the MSD it refers to, including as identifier the MSD id, the agency, the version.

4.2.1 <Annotations>

The first part of the MetadataSet comprises the Annotations made to the metadata file. Those are the Annotation Types

• REPORT_STRUCTURE with AnnotationText e.g. SIMS_REPORT_FULL. This item is not necessary in SDMX 3.0 however remains in the metadata file to ensure compatibility with SDMX 2.0 for the transition period. This item does not need to be included, filled in or altered.

• REFERENCE_PERIOD which identifies the periodicity of the metadata file replacing the former Target Value for the TimeDimension. This item is not necessary in SDMX 3.0 however remains in the metadata file to ensure compatibility with SDMX 2.0 for the transition period. This item needs to be included in the import file in for the time being.

  Periodicity	Description	Possible period	Example
  2	(every 2 years)	0	20
  3	(every 3 years)	0	30
  4	(every 4 years)	0	40
  5	(every 5 years)	0	50
  A	(Annual)	0	A0
  M	(Monthly)	1-12	M1 to M12
  Q	(Quarterly)	1-4	Q1 to Q4

• FOR_PUBLICATION which indicates whether the imported metadata file is targeted for Publication or not – see below under 4.2.4 Publication flags and Restriction flags.

• The global annexes for the Metadataset of types URL, FILE, FILE_DSD – see below under 4.2.3 Annexes.

4.2.2 Metadata Attributes - The concepts and their values

• Are reported in a tag <generic:Attribute id=”…”>
• Their value should be put in the tag <generic:Value>.
• The order and hierarchy should follow the MSD. 
• The representation types of the concepts are specified in the MSD. They can have String format, Date, reference to a Code List (CL_...) or be of type Boolean. In the table below are described some examples for each representation type.

4.2.3 Annexes

Annexes can be

• Global to the whole metadata file
• Or specific to one concept.

Global annexes should be added

• in the tag <MetadataSet>,
• in a tag <common:Annotations>
  and <common:Annotation> for each annex.

Concept's annexes should be added

• in the related tag <generic:Attribute id=…>
• in a tag <common:Annotations>
  and <common:Annotation> for each annex.

The different types of an annex are:

• FILE - any kind of file formats such as .doc, xlsx, pdf, jpg, etc...
• File_DSD [1] - SDMX compatible tabular data files that need to be provided in a pair of a DSD and underlying Excel file in .xlsx format. Tabular data files are being validated with STRUVAL.
• URL - a link to a webpage

4.2.4 Publication flags and Restriction flags, non editable concepts

5. xlsx file 

To retrieve the correct template for the xlsx used for the import, it is advised to download first an example file from ESS-MH, conveniently a comparable file from a report based on the same MSD/typology.

The name of the file to be prepared for the import is like xx.xlsx (where xx is preferably the metadata file name)
Example: DMBB_SIMS_A_4D_2020_0000.xlsx
The xlsx file comprises three sheets that serve different purposes and require different degree of filling.
•    Metadata
•    Parameters
•    Annexes
 

5.1 Metadata - "Header" section

Most parts in the Header section are mandatory and should contain the items presented in the example.

The Metadata file will be assembled based on the values provided in cells B4:B8.

5.2 Metadata "Concepts" section 

The Concepts section depends completely on the MSD. The order and hierarchy should follow the MSD. 

Column A contains the "Concept name" with the corresponding numbering based on the typology in ESS-MH. This information is retrievable from the underlying MSD to a certain extent, while the numbering is autogenerated by the application ESS-MH upon building the typology. Otherwise, this information can be obtained directly from the ESS-MH, or can be clarified with the Metadata Support or the Production Domain. 

5.2.1 Concept values

The concept values should be put in cells in column B "Concepts". According to the specifications in the MSD, concept values can be expressed in different representation types:

5.2.2 Restricted for publication flag (at the concepts level)

For each concept which should not be published, the corresponding cell in column C headed by "Restricted from publication" should be set to YES. Otherwise NO.

Then the value "Restricted for publication" will appear as content of the concept when the file is published.

5.3 Parameters

The second sheet is a Parameter sheet that specifies how the items and data in sheet "Metadata" should be coded and implemented in the Metadata files in ESS-MH. Generally, when you work with a downloaded template of a comparable Metadata file from ESS-MH, in sheet "Parameters" editing is neither expected nor advised.

In column A "Element name" you can find all items as per column A in the Metadata sheet.

Column B "Element code" lists the related IDs for the items and concepts.

Column C "Type" specifies the items further in terms of function and representation in the Metadata file while column D "Position" indicates the rows of the items of Metadata sheet, i.e. references the elements from the two sheets Metadata and Parameters and defines, which values will be taken into account for the importation. 

Lastly, column E identifies whether a concept is configured as being "Editable" or not. In case of "NO", any value inserted in the respective concept in Metadata tab / Annexes tab will not be taken into account on import of the Metadata file. Only, if you plan to set up your file import per Excel file from scratch with a blank file, or you plan to import only a subset of concepts to ESS-MH, you should ensure to align the Parameters sheet with the Metadata sheet respectively. 

5.4 Annexes

Equivalent to SDMX-ML files, Annexes can be attached

• Specifically to one concept,
• Globally to the whole metadata file.

The different types of an annex are:

• FILE - any kind of file formats such as .doc, .xlsx, pdf, jpg, etc..
• FILE_DSD [2] - SDMX compatible tabular data files that need to be provided in a pair of a DSD and underlying Excel file in .xlsx format. Tabular data files are being validated with STRUVAL.
• URL - a link to a webpage

Note: You can attach as many Annexes as necessary, provided you keep the maximum size of the entire Excel.zip file of 10MB.

Annexes need to be added in the corresponding "Annexes" sheet, both for concepts and globally for the whole metadata file.

In Column A "Concept", you specify whether an Annex is supposed to be attached

• To a concept by providing here the corresponding concept ID (can be looked up from the Parameters sheet),
• To the metadata file globally by leaving the cell blank.

In column B "Annex Type" you specify whether an Annex is of the type

• FILE, or
• FILE_DSD
• URL,
• adding «restricted» in case you want to flag the Annex not to be published.

In column C "Annex Name", you reference the Annex by providing

• Which file needs to be present from the subdirectory Annexes of the "Excel" zip file with the specified name.
• The concrete URL.

In column D "Annex Description", you specify the custom name of the Annex, as you wish it to appear in the HTML view of the metadata file later. In case of FILE_DSD, you must specify the referenced DSD + version in brackets. 

6. Guidelines

Users with role VALIDATOR may also create and edit Guidelines by file import. The importation mechanism is equivalent to the one for Metadata files, you can choose between 

Using only an SDMX-ML file if there is no annex and no image,

• Should follow the SDMX standard (with a <header> and specific tags…)
• Including the content itself following a valid MSD (Metadata Structure Definition, defining especially the reported concepts).

Using only an xlsx file if there is no annex and no image,

• Should follow a certain template complying with the SDMX standard
• Including the content itself following a valid MSD (Metadata Structure Definition, defining especially the reported concepts).

Using a zip file

• "SDMX" zip file (necessary if the file refers to images). Such an "SDMX" zip file should have a specific structure and contain an SDMX-ML file.
• "Excel" zip file (necessary if the file refers to images). Such an "Excel" zip file should have a specific structure and contain an xlsx file. 

Also for the guidelines, it is advised to download first an example file from ESS-MH, conveniently from a report based on the same MSD in order to retrieve the correct template for the SDMX-ML or Excel files used for the import.

Note: Annexes and Publication flags or 'Restricted from publication' flags are not part of the guidelines.

6.1 SDMX-ML file - specifics for "Guidelines"

In ESS-MH the guidelines used to be called like esms-xx-YYYY.sdmx (where xx is the name of the metadata flow and YYYY the reference year from which on the guidelines is valid). 

The imported file should be archived in an sdmx.zip file when the guidelines file refers to images. Note that the file to be imported can have a different name, as long as the extension .sdmx.zip is kept.

Example for guidelines containing Images: esms-DMAA_ESMS_A-2019.sdmx.zip.
The zip file contains:

• One SDMX-ML file named esms-xx-YYYY.sdmx.xml (where xx is preferably the metadata flow name)
  In our case: esms-DMAA_ESMS_A-2019.sdmx.xml
• If there are images, one directory Images/ containing one file per image.

For images, JPEG (.jpg) is probably the lightest format but .png, .gif and .bmp are also accepted.

Currently there is a limit for the zip file of 10 MB.

6.1.1<Header> tag

• The <Header> is mandatory and should contain all the tags presented in the example, of which the following items need to contain a value
  • <ExportType>EXPORT_GUIDELINES</ExportType>
  • <Sender id> should have the same value as Data Provider <componentValues component="DATA_PROVIDER"> (see below). The <Sender> is generally "ESTAT".
• A value in <DataSetAction> is optional, but might turn out useful to edit an existing file. Normally the Import is used by checking the "overwrite" box in ESS-MH UI. The content of the new file replaces the old one completely. With the <DataSetAction> tag, an incremental import is facilitated: The application is able to import partial files of the same report while keeping the existing content. Based on the value in the (optional) <DataSetAction> tag in the <Header> the following actions can be carried out:
  • Append: New data (i.e. concepts that are not empty) may be added, but cannot overwrite or delete existing ones.
    • Replace: New data (i.e. concepts that are not empty) may be added and also replace existing one. 
    • Delete: New data (both, concepts that are empty or contain a value) replace existing ones and old ones are deleted if the new ones are missing values.
    • [missing value in the<DataSetAction> tag]: the new file replaces the existing one entirely (= “Delete”, complete overwrite of the file).
    • Note: The "overwrite" checkbox in ESS-MH UI is taken into account only when there is no data set action tag in the SDMX-ML file. The data set action tag has priority over the checkbox.

6.1.2<MetadataSet> tag

The <MetadataSet> tag depends completely on the MSD it refers to, including the MSD id, the agency, the version.

An Annotation are included in the Export of guidelines, however are not needed for importing guidelines files, pointing to the Report Structure of the referenced MSD. This information is being kept for the time of transition from SDMX 2.0 to 3.0.

6.1.2.1<TargetValues>

The name of the guidelines file in ESS-MH (on an import) is defined based on the mandatory Component Values, as hereunder

6.1.2.2 Metadata Attributes - The concepts and their values

• Are reported in a tag <generic:Attribute id=…>
• Their value should be put in the tag <generic:Value> (without any '<' or '>').
• The order and hierarchy should follow the MSD. 
• The representation types of the concepts values can have String format and can be inserted as

6.1.2.3 Annotations

For concepts / Attributes, that are configured to be not editable by the Metadata providers, an annotation is added to the concerned concept. This annotation has no relevance for the import of guidelines, only serves as information upon export of guidelines from ESS-MH.

6.2 Excel file - specifics for "Guidelines"

In ESS-MH the guidelines used to be called like esms-xx-YYYY.xlsx (where xx is the name of the metadata flow and YYYY the reference year from which on the guidelines is valid). 

The imported file should be archived in an xlsx.zip file, when the guidelines file refers to images. Note that the file to be imported can have a different name, as long as the extension .xlsx.zip is kept.

Example for guidelines containing Images: esms-DMAA_ESMS_A-2019.xlsx.zip.
The zip file contains:

• One SDMX-ML file named esms-xx-YYYY.xlsx (where xx is preferably the metadata flow name)
  In our case: esms-DMAA_ESMS_A-2019.xlsx
• If there are images, one directory Images/ containing one file per image.

For images, JPEG (.jpg) is probably the lightest format but .png, .gif and .bmp are also accepted.

Currently there is a limit for the zip file of 10 MB.

The xlsx file comprises two sheets that serve different purposes and require different degree of filling.

• Metadata
• Parameters

6.2.1 Metadata - "Header" section

Most parts in the Header section are mandatory and should contain the items presented in the example.

The Metadata file will be assembled based on the values provided in cells B3:B7.

6.2.2 Metadata "Concepts" section 

The Concepts section depends completely on the MSD. The order and hierarchy should follow the MSD. 

Column A contains the "Concept name" with the corresponding numbering based on the typology in ESS-MH. This information is retrievable from the underlying MSD to a certain extent, while the numbering is autogenerated by the application ESS-MH upon building the typology. Otherwise, this information can be obtained directly from the ESS-MH, or can be clarified with the Metadata Support or the Production Domain. 

The concept values should be put in cells in column B "Concepts". Concept values can be expressed as string.

6.2.3 Parameters

The second sheet is a Parameter sheet that specifies how the items and data in sheet "Metadata" should be coded and implemented in the metadata files in ESS-MH. Generally, when you work with a downloaded template of a comparable guideline file from ESS-MH, in sheet "Parameters" editing is neither expected nor advised.

In column A "Element name" you can find all items as per column A in the Metadata sheet.

Column B "Element code" lists the related IDs for the items and concepts.

Column C "Type" specifies the items further in terms of function and representation in the guidelines file while column D "Position" indicates the rows of the items of Metadata sheet, i.e. references the elements from the two sheets Metadata and Parameters and defines, which values will be taken into account for the importation. 

Lastly, column E identifies whether a concept of the Metadata file is configured as being "Editable" or not.

Only, if you plan to set up your file import per Excel file from scratch with a blank file, you should ensure to align the Parameters sheet with the Metadata sheet respectively.

[1] The FILE_DSD always needs a reference to the DSD it is built upon. To retrieve the information on the DSD (ID and version), it is advisable to download a Metadata file from ESS-MH, in which the DSD is provided separately. On import of the Metadata file incl. a FILE_DSD, the DSD does not need to be physically provided, there reference on the FILE_DSD is sufficient.

[2] [1] The FILE_DSD always needs a reference to the DSD it is built upon. To retrieve the information on the DSD (ID and version), it is advisable to download a Metadata file from ESS-MH, in which the DSD is provided separately. On import of the Metadata file incl. a FILE_DSD, the DSD does not need to be physically provided, there reference on the FILE_DSD is sufficient.