Data from data providers to the databank of basic data
Here you can read about the guidelines for receiving data intended for publication in the databank of basic data of Denmark’s Data Portal (DDP).
If a statistical authority wishes to have its data published in DDP’s databank of basic data, the authority must contact DDP at ddvgrunddatateam@dst.dk. DDP will arrange an initial meeting with the statistical authority to discuss the overall characteristics of the register, including dataset size, number of tables, update timing and frequency, timeline, and conditions for publication in DDP databank of basic data. If desired, Statistics Denmark’s (DST) Data Protection Officer (DPO) may be invited to participate in the meeting.
DST enters into data transfer agreements with all external data providers in order to transfer data ownership and responsibility to DST. These agreements specify update formats and frequencies, handling of data breaches, and related matters.
After this, communication becomes more detailed, covering topics such as naming of the register and how data will be transferred to DDP. The formats must comply with the quality requirements listed below.
Receiving External Data
DDP prefers data delivery via transfer to an SFTP server. DDP provides guidance and assistance in setting up this process. Other delivery methods are also possible.
When creating data, the provider must ensure that they comply with the general guidelines for establishing Basic Data in DDP.
Variable types, lengths, and names
Data types relate to the content of the variable. The following describes how to determine the appropriate data type for a variable.
Keys and Identifiers
Keys and identifiers should have the same names across all data series. They must all be defined as character variables, and when they contain purely numeric content, they must include leading zeros (see below).
They must also have an accurate and precise length specification corresponding to the maximum value of the content, and the length must remain consistent over time.
Examples (Name, Variable Type, Length):
PNR — CHAR 10
CVRNR — CHAR 8
SENR — CHAR 8 (leading zeros)
JOURNR — CHAR 16
RECNUM — CHAR 16
EJENDOMSNUMMER — CHAR 6 (leading zeros)
ADRESSE_ID — CHAR 8 (leading zeros)
There are, of course, more keys and identifiers than those listed above. DDP is happy to advise on their correct setup.
Character Variables – Classifications
Classifications such as SEX, AGE, MUNICIPALITY, and MARITAL STATUS, where the value can be translated into text via a code-text table or format description, must be defined as character variables. Most variables will fall into this category. These fields must also have an accurate length specification, and fields with length > 1 must include leading zeros when they contain purely numeric content.
Numeric Variables – Calculation Variables
Variables that can be used for calculations—such as quantities, sums, amounts, or counts—must be numeric. The variable must have an accurate length specification corresponding to the maximum value.
For example, AGE should be defined as CHAR(3), as the maximum value may exceed 100. Example of content with leading zeros: AGE = 001, 010, 100.
Date Variables
Date fields may be pure dates, but where time information is relevant, they may also be of the timestamp type.
Variable Names
Variable names must not contain the Danish characters Æ/æ, Ø/ø, or Å/å.
Missing Values in SAS
Variable Type Missing in SAS
Numeric . (period)
Character '' (empty string)
1.Numeric variables
A period (.) can be processed in SAS when it is a numeric variable.
2.Character variables
An empty string ('') indicates that the variable is character but contains no value. Values such as “Unknown”, “None”, or 0 must not be used.
Documentation requirements for external data to be included in databank of basic data
The external data provider must supply register and variable documentation when the delivery agreement is established. The documentation is published in the DDP App and on DST’s website. Documentation can be uploaded via the Metadata Loader. Guidance can be provided upon request.
Variable descriptions are published in the DDP App after the documentation has been uploaded, allowing users to find the relevant information when ordering data.
Additional descriptions of the basic data register are published on DDP’s website under Data from other sources, where the register receives its own section.
In addition to the documentation mentioned above, the data provider is also required to keep DDP informed about data breaches, changes in reporting, changes in legislation, etc. A written notification is required so that DDP can pass the information on to users or add it to the website. This is further specified in the data transfer agreement prepared between the data provider and DDP.