Data Structure Definitions¶
Selecting Data Structures Definitions from the “Meta Manager” module the application will show the list of DSDs present in the system similarly to the lists of all artefacts present, as explained in artefact list.
The View/Edit function allows the user to view the detail of the DSD and update it if the user has write privileges.
The main section of the DSD detail mask contains the following tabs :
General
In the “General” window user can configure annotations, among them it is possible to edit annotations for the “Table layout”, the “Chart layout” and the “Map layout”. Other annotations at dimension level (e.g. not displayed) can be edited directly in the dimension definition window. For the meaning of these annotations please refer to Other node configurations.Primary measure
The fields for both editing and insertion are:
– ID (mandatory alphanumeric): OBS_VALUE (not modifiable)
– Concept (mandatory alphanumeric)
The System allows the selection of a Concept Scheme by means of an interface that allows selection among the concepts present.
– Code List (alphanumeric not mandatory).
The System allows the selection of a List of Codes by means of an interface that allows selection from the list of codes present.
– Annotations
Note:
the definition of a unique measure complies with the SDMX standard, if it is necessary to display indicators, the measure will remain unique, what needs to be done is to define a dimension that expresses the name of the indicators.
Filtering on this dimension, the value of the chosen indicator will be obtained in obs_value.
Dimensions
The fields in insertion and modification are:
– Type Size: The System allows the choice between the following Size types: Normal, Frequency, Time, Measure
– ID : (alphanumeric mandatory)
– Order: (numeric optional)
– Concept:(alphanumeric mandatory)
The System allows the selection of a Concept Scheme by means of an interface that allows selection among the concepts present.
– Code List (alphanumeric not mandatory).
The System allows the selection of a List of Codes by means of an interface that allows selection from the list of codes present.
– HCL (alphanumeric not mandatory).
The System allows the selection of a List of Hierarchical Codelist by means of an interface that allows selection from the list of HCL present.
After the user has chosen the HCL list, a text field will appear in which the user must specify the desired hierarchy from those available in the chosen HCL.


These fields will be valorizable only after the ‘Codelist’ field is filled and will be automatically emptied if the codelist reference is removed.
– Annotations
Note:
What are “Normal” dimensions? They are all non-special classifications such as: gender, age, economic sector etc…
A “Measure” dimension is a special dimension that contains the names of several indicators so it will certainly be necessary to filter this dimension to show the values correctly.
A “Frequency” dimension is a special dimension that in some way is linked, for example, to update time of data and therefore contains items such as: annual, semi-annual etc..
A “Time” dimension is a special dimension that expresses the historical series so if the frequency is, for example, annual it will contain years.
Groups
The fields in insertion and modification are:
– Group ID: (alphanumeric mandatory)
– Dimensions: The list of dimensions defining the group is built on the basis of the user’s choice of one or more DSD Dimensions.
At least one dimension must be selected for the definition of a group.
– Annotations: (alphanumeric not mandatory)
Note:
Groups are nothing more than groupings of dimensions to which an ID is associated in order to refer to those dimensions in a simpler way.Attributes
The fields in insertion and modification are:
– ID: (mandatory alphanumeric)
– Order: (numeric optional)
– Concept: (alphanumeric mandatory)
The System allows the selection of a Concept Scheme by means of an interface that allows selection among the concepts present.
– Code List: (alphanumeric not mandatory)
The System allows the selection of a List of Codes by means of an interface that allows selection from the list of codes present.
– Assignment Status: (alphanumeric mandatory)
Possible values are: Mandatory, Optional
– Attachement Level: (alphanumeric mandatory)
Possible values are: Observation, Dataset, Size Group, Group
– HCL (alphanumeric not mandatory).
The System allows the selection of a List of Hierarchical Codelist by means of an interface that allows selection from the list of HCL present.
As already seen when describing the dimensions, the user after choosing the HCL list, he must specify the desired hierarchy from those available in the chosen HCL.
This field will be valorizable only after the ‘Codelist’ field is filled and will be automatically emptied if the codelist reference is removed.
– Annotations: (alphanumeric not mandatory)
Note:
Attributes are additional information that, although not modelled as dimensions, are equally fundamental to understand and use data that will later be associated with the DSD.
It is easy to understand, for example, that if the measure expresses payments, it is necessary to know: the currency, the number of decimal places or whether it is expressed in thousands or millions etc..
For all this information it is necessary to define an attribute and where it must be applied, if to the whole dataset, if to groups of dimensions or to single observations.
Categorisations
Not yet implemented.
General Note:
The user can edit codelists and conceptscheme used in a dsd in the dsd management window, without having to close the window and access the respective features from the left menu.
The artifacts mentioned above can be edited from the PrimaryMeasure/Dimensions/Attributes windows where the codelist/conceptscheme used by each component is indicated (in which case the artifacts will surely already be finalized).
When creating a component in an unfinalized dsd and selecting artifacts from the list of all available ones, it is also possible to finalize “unfinalized” codelists or conceptscheme so that these artifacts can be used in the dsd.