Search result

User roles

The relevant employees in a research project must be created as users in Denmark’s Data Portal. You have different options when using Denmark’s Data Portal, depending on which user role your institution assigned to you. Below you can read which rights the different roles have. In Denmark’s Data Portal, you can see your role under ‘My overview’ next to your institution. If a specific role has not been indicated, you are a ‘User’., There are seven different roles in Denmark’s Data Portal:, Responsible for authorisation, Substitute, Administrator, Contact person with powers, Signatory, Contact person, User, Below you can read which rights the different roles have. You can also read more about how the roles are assigned.,  , What can the different roles do? , Responsible for authorisation, This role is responsible for the institution’s authorisation under microdata schemes with Statistics Denmark and approves association agreements under the authorisation. The person responsible for authorisation is legally responsible for the users associated with the institution complying with the current guidelines for use of data. This person is the only one who can assign the roles as substitute, administrator and signatory. See how under ’How to assign roles?’ below., Substitute, A user who can approve association agreements on behalf of the person responsible for authorisation. It is highly recommended that you appoint one or more substitutes. In the dropdown menu ‘Assigning roles’ below, you can read how to select substitutes in Denmark’s Data Portal. Note that the person responsible for authorisation cannot be his/her own substitute., Administrator, It is the institution administrator who must approve and submit all of the institution’s project proposals to Statistics Denmark via Denmark’s Data Portal. The administrator works as an internal approver, whenever a project proposal is to be submitted or resubmitted. The administrator is thus charged with quality assuring the content of the project proposals from the institution, making sure that the proposals meet requirements to form and GDPR. This means that an administrator should be available and is expected to be a regular user of Denmark’s Data Portal., The administrator must contact Research Services if the institution wishes to have a new user created. An institution must have at least one administrator, and we recommended that you appoint at least two administrators. This is because some tasks in Denmark’s Data Portal can only be carried out by an administrator, and because a given administrator is not allowed to administer him- or herself. It is possible to appoint up to 10 administrators in one institution., Contact person with power, An institution can choose that a contact person can have powers corresponding to those of an administrator on the projects for which the user is a contact person. If a contact person has powers, the role is delimited to the institutions that the user is associated with. If you - as the person responsible for authorisation - want this solution for a user, you must contact Research Services., Signatory, On behalf of the institution, persons with the signatory role can sign to pledge that a project proposal is conforming to Article 6 of the General Data Protection Regulation. , When your project proposal has been approved, an employee in Research Services will sign it. After that, the person who submitted the proposal, i.e. the contact person for the project, the administrator or the contact person with powers, as well as the chosen signatory will receive an email with information indicating that the project proposal has been approved and signed. Subsequently, you need to sign the project proposal. Only users who have been assigned the role of signatory can sign project proposals., The role as signatory is assigned by the person responsible for authorisation or a substitute. Remember that it is a requirement that people with a signatory role are formally employed by the institution where they have the signatory role. There is no limit on the number of signatories. , Contact person, A user with access to a project has the role as contact person for the project. The contact person has the dialogue with Research Services regarding the project proposal. A project can only have one contact person. Administrator can change the project contact person., User, This is the basic role for users. The role gives access to information on the entities with which the user is associated, and the user can edit his or her own information. When a user is associated with a project in Denmark’s Data Portal, he or she also gets access to the project data on the researcher machine. Contact an administrator or the person responsible for authorisation, if you want to be created as a user under an authorised institution., Project owner at Statistics Denmark, When you submit a project to us, we will assign a project owner in Research Services to you with whom you will have direct contact. We do our best to answer your enquiry as soon as possible. , See the average response times under Contact Research Services, Who can edit user information in Denmark’s Data Portal?, The individual user can update his or her own user information in Denmark’s Data Portal. This could be relevant, e.g. if a user changes workplace and therefore wants to update his or her email address., If an association agreement must be terminated, this must either be done by the user him- or herself, the institution administrator, the person responsible for authorisation or a substitute hereof. In our , video guides, , you can see the respective tasks and responsibilities of a user, an administrator and a person responsible for authorisation in Denmark’s Data Portal. , How to assign roles, The person responsible for authorisation at the institution is the only one who can assign the roles as substitute, administrator and signatory., To do so, you must as the person responsible for authorisation log into Denmark’s Data Portal and select ‘My overview’. Click the institution where you are responsible for authorisation, and then click the three dots to the right of the institution name. If you want to assign/discontinue the role as administrator, you must click ‘Administration of administrators’. If you want to assign/discontinue the role as substitute, you must click ‘Administration of substitutes’, etc. Now a list appears of all users associated with the institution. Click ’Select’ next to the user you want to make either a substitute, an administrator or a signatory., The administrators of the institution can create new association agreements for the institution and attach users to projects., See table of the rights of user roles in Denmark’s Data Portal (pdf, in Danish)

https://www.dst.dk/en/TilSalg/data-til-forskning/brugeradgang/brugerroller

Cropland

How big is the Danish agricultural area, and how did it develop over time? What crops are grown, and how much of it is organic?

https://www.dst.dk/en/Statistik/emner/erhvervsliv/landbrug-gartneri-og-skovbrug/det-dyrkede-areal

Subject page

Documentation of statistics: Road Traffic Accidents

Contact info, Population and Education, Social Statistics , Jørn Korsbø Petersen , +45 20 11 68 64 , JKP@dst.dk , Get documentation of statistics as pdf, Road Traffic Accidents 2021 , Previous versions, Road Traffic Accidents 2020, Road Traffic Accidents 2019, Road Traffic Accidents 2018, Road Traffic Accidents 2017, Road Traffic Accidents 2015, Road Traffic Accidents 2014, Road Traffic Accidents 2013, The purpose of the statistics is to collect and publish information on road traffic accidents in order to create a basis of knowledge for making decisions that can reduce the number of road traffic accidents and the consequences thereof. The statistics on road traffic accidents originate from 1 January 1930. The source of the statistics has until 1 January 2003 been the temporary and final reports from the police. From this date Statistics Denmark only receives an annual extract from the Road Directory with the police's final reports. Apart from this, the most fundamental alterations that have been introduced concern the classification of accidents, the scope of the statistics and the actual reporting procedures., Until 1938, the classification of accidents was not unambiguous. From 1938 to 1966, accidents were categorized according to the main cause of the accident, which was determined by a legal judgement. From 1967 onwards, this judgement has been replaced by a classification of the accident, which is not based on the concept of blame, but on the actual description of the circumstances surrounding the accident., From 1930 to 1958, the statistics included accidents resulting in personal injury as well as damage to property. Since 1958, accidents involving only damage to property are no longer covered by the statistics, and from 1967 accidents involving only pedestrians are no longer covered either, whether the accident resulted in a casualty or not., Up until and including 1975, the police reports were sent straight to Statistics Denmark. In 1976, the reporting system was expanded, so that the highway authorities in counties and municipalities take part in the reporting by locating the accidents. As from November 1997 and up to and including April 2000, a new system of computerized reporting was gradually introduced in the police., Since 1 January 2003 the police reports have been sent to the Road Directorate from whom Statistics Denmark receives an annual extract., Statistical presentation, The statistics on road traffic accidents illustrate the extent and the nature of all accidents involving casualties, who are known by the police. The information on road traffic accidents is classified into three main groups: information about the accident, information about the element (vehicles, pedestrians and obstacles) and information about the person., Read more about statistical presentation, Statistical processing, Annual extract from the Road Directorate, Road Accident Information System with information for all accidents with injured., The data is checked for errors. Only few corrections is made. No seasonally adjustment is made., Read more about statistical processing, Relevance, National users: Ministries (primarily the Ministry of Traffic), the police districts, the highway authorities in counties and municipalities, organizations, research centers, the education system and private persons., Eurostat: The register is made anonymous and sent to Eurostat, as input for the Community Database on Accidents on the Roads in Europe (CARE)., Area of application: Local and central planning aimed at reducing road traffic accidents, education, research and public debate., Read more about relevance, Accuracy and reliability, A general problem concerning the road traffic accident statistics is that they do not include accidents involving casualties, which are not reported to the police. The severity of the accident and the mode of transport are factors, which influence whether the police are involved. Examinations - pooling with the Register of Causes of Death and with registries of casualty award visits and hospital admissions caused by road traffic accidents - have proven that almost all accidents involving deaths are reported. Accidents involving serious personal injury are more frequently reported than accidents involving only slight injuries. Furthermore, accidents involving cars are more frequently reported than accidents involving bicycles and mopeds. In average only 20 per cent of the casualties come to the knowledge of the police. Results of the pooling with registries of casualty award visits can be found in the table MOERKE in , Statbank, ., Read more about accuracy and reliability, Timeliness and punctuality, The statistics are usually published without delay in relation to the scheduled date - ult. June after the year after., Read more about timeliness and punctuality, Comparability, These include changes in the registration of road traffic accidents resulting in inconsistencies of data as well as the introduction of new variables. Since 1958, accidents involving only damage to property have been omitted from the statistics. In January 1967, the definition of road traffic accident involving casualties was changed to include only accidents involving at least one vehicle. This leaves out accidents involving only pedestrians. From January 1967, the classification of accidents according to main and secondary causes was changed to a classification according to the accident situation, based on an objective evaluation of the course of events leading up to the accident. In January 1981, the definition of slightly injured was changed. Minor bruises, scrapes and the like are no longer considered as slight injuries. In January 1983, the structure and contents of the statistical system were changed. New parameters - e.g., cycle paths, collision point, maneuver concerning the element record, and on driving license and moped license - were introduced. From January 1997, individuals who are admitted to hospital for observation due to concussion should be registered as slightly injured in cases where the diagnosis does not turn out to be concussion of the brain., Legal changes, such as the introduction of and changes to speed limits and limits for level of alcohol in the blood, and requirements concerning the use of seat belts, helmets, child seats, lights, etc., can influence the overall development in the road traffic accident statistics., Read more about comparability, Accessibility and clarity, Statistics appear in:, News from Statistics Denmark., Annual publications: , Statistical Yearbook, Statistical 10-Year Review, and , Færdselsuheld, (Road Traffic Accidents)., Statbank, .Transport, Traffic accidents: UHELD1, UHELDK1, UHELD2, UHELDK2, UHELD3, UHELD4, UHELD5, UHELD6, UHELD7, UHELDK7, UHELD8, UHELD9, UHELD10, UHELD11, UHELD12, UHELD13, MOERKE., Read more about accessibility and clarity

https://www.dst.dk/en/Statistik/dokumentation/documentationofstatistics/road-traffic-accidents

Documentation of statistics

Contact: IT

Section/Title, Name, Phone, Mail, IT management, Head of Division, Head of Division, Peter Filtenborg Madsen , +45 20 35 30 16, pfm@dst.dk, Head of Division, Head of Division, Carsten Zornig , +45 25 17 03 13, czo@dst.dk, Deputy Head of Division, Deputy Head of Division, Bo Guldager Clausen , +45 28 14 38 15, bgc@dst.dk, Executive chief consultant, Executive chief consultant, Frank Holdt , +45 27 51 18 31, fah@dst.dk, Data Collection Systems, Chief Adviser, Chief Adviser, Maja Kirchhoff Krølner , +45 21 76 67 79, mkk@dst.dk, Chief Adviser, Chief Adviser, Nicolai Zangenberg , +45 23 37 34 51, niz@dst.dk, Senior Adviser, Senior Adviser, Henning Tornhøj Christensen , +45 20 43 95 31, hng@dst.dk, Senior Adviser, Senior Adviser, Knud Wharton Hammerich , +45 21 53 80 35, knh@dst.dk, Head of Section, Head of Section, Mikkel Baand Rasmussen , +45 21 59 30 22, mbu@dst.dk, System Analyst, System Analyst, Jens Schouv Andersen , +45 40 10 80 75, jea@dst.dk, System Analyst, System Analyst, Leif Bochis Madsen , +45 24 81 67 05, lbm@dst.dk, System Analyst, System Analyst, John Hertz Nielsen , +45 20 41 49 05, jni@dst.dk, System Analyst, System Analyst, Jan Ole Nørregård Sørensen , +45 23 64 18 01, jos@dst.dk, RS Team CZO, Karsten Bjergkvist , +45 22 87 18 71, kbk@dst.dk, System Analyst, System Analyst, Leif Aller , +45 23 47 09 10, lal@dst.dk, System Analyst, System Analyst, Morten Schou Gross , +45 21 62 86 23, mgr@dst.dk, System Analyst, System Analyst, Marcel Kristensen , +45 21 62 56 19, mrc@dst.dk, RS Team PGL, Systems Consultant, Systems Consultant, Hans Henrik Andersen , +45 53 57 08 03, has@dst.dk, Senior Systems Analyst, Senior Systems Analyst, Allan Bo Jørgensen , +45 51 71 57 35, alj@dst.dk, System Analyst, System Analyst, Jesper Skibber Hansen , +45 23 27 36 39, jsh@dst.dk, System Analyst, System Analyst, Flemming Fogh Simbold , +45 24 49 35 23, ffs@dst.dk, Service Desk, Chief Adviser, Chief Adviser, Niels Jespersen , +45 42 42 93 73, njn@dst.dk, Systems Consultant, Systems Consultant, Carsten Frank Jørgensen , +45 29 36 13 59, cfj@dst.dk, Systems Consultant, Systems Consultant, Henrik Philip Jørgensen , +45 28 14 38 17, hph@dst.dk, Systems Consultant, Systems Consultant, Lars Roediger , +45 53 27 11 10, lro@dst.dk, Bachelor, Bachelor, Jesper Korsgaard Jensen , +45 40 22 75 65, jpr@dst.dk, Clerk, Clerk, Pia Isaksen , +45 23 80 01 67, pii@dst.dk, EDP Consultant, EDP Consultant, Jan Vibe , +45 30 69 52 15, jvi@dst.dk, Senior Systems Analyst, Senior Systems Analyst, Mette Lisberg , +45 41 17 90 60, mli@dst.dk, System Analyst, System Analyst, Patrick Søbjerg Andersen , +45 21 17 64 51, psm@dst.dk, System Analyst, System Analyst, Marianne Blom , +45 24 67 74 68, mbt@dst.dk, System Analyst, System Analyst, Lars Dohn , +45 28 83 49 52, ldo@dst.dk, System Analyst, System Analyst, Betina Hansen , +45 30 54 75 53, bti@dst.dk, System Analyst, System Analyst, Henrik Kjær , +45 21 24 02 90, hkj@dst.dk, System Analyst, System Analyst, Kristian Kassø Meier , +45 21 18 24 11, kmi@dst.dk, System Analyst, System Analyst, Mark Rørvig , +45 24 61 61 54, mro@dst.dk, Strategy, Architecture, Governance and IT Security, Chief Adviser, Chief Adviser, Jeanne Camilla Hellemose Henriksen , +45 91 37 67 73, jnh@dst.dk, Chief Adviser, Chief Adviser, Sanne Vestergaard Nielsen , +45 24 63 22 60, svn@dst.dk, Senior Adviser, Senior Adviser, Cajsa Mølskov , +45 61 15 38 41, cms@dst.dk, Senior Adviser, Senior Adviser, Sara Rytter Nielsen , +45 41 43 64 48, sry@dst.dk, Bachelor, Bachelor, Simon Gyldendal Svensson , +45 31 36 72 86, sgs@dst.dk, Team InFlow, Senior Systems Analyst, Senior Systems Analyst, Allan Henrik Rasmussen , +45 21 19 55 69, ahr@dst.dk, System Analyst, System Analyst, Catharina Agger , +45 91 37 64 11, cag@dst.dk, System Analyst, System Analyst, Thomas Bo Nielsen , +45 21 19 46 39, tbn@dst.dk, Team META-KOM, Chief Adviser, Chief Adviser, Stefan Jul Gunnersen , +45 21 45 47 04, sjg@dst.dk, Chief Adviser, Chief Adviser, Peter Sandager , +45 20 61 49 14, pms@dst.dk, Chief Adviser, Chief Adviser, Giovanni Tagliaferri , +45 29 21 63 70, gta@dst.dk, Senior Adviser, Senior Adviser, Simon Christiansen , +45 21 59 36 68, sbc@dst.dk, Senior Adviser, Senior Adviser, Flemming Dannevang , +45 40 40 56 06, fda@dst.dk, Senior Adviser, Senior Adviser, Dorthe Helstrup Poulsen , +45 40 23 52 29, dop@dst.dk, Head of Section, Head of Section, Flemming Dahl Christiansen , +45 21 34 40 75, fch@dst.dk, Head of Section, Head of Section, Nanna Laksø , +45 20 55 73 12, nlk@dst.dk, Head of Section, Head of Section, Rasmus Ludvigsen , +45 23 69 67 77, rlu@dst.dk, Head of Section, Head of Section, Michael Wiingaard , +45 23 43 70 76, miw@dst.dk, Bachelor, Bachelor, Anders Ibsen , +45 30 89 40 66, aib@dst.dk, Senior Systems Analyst, Senior Systems Analyst, Mike Elkjær Barbré , +45 23 27 75 59, meb@dst.dk, Senior Systems Analyst, Senior Systems Analyst, Michael Nielsen , +45 29 60 36 27, min@dst.dk, System Analyst, System Analyst, Kim Duncan-Bendix , +45 29 36 59 72, kdb@dst.dk, System Analyst, System Analyst, Jens Erik Hagedorn , +45 23 11 83 75, jhg@dst.dk, System Analyst, System Analyst, Jakob Traun Jørgensen , +45 30 46 33 15, jtj@dst.dk, System Analyst, System Analyst, Michael Pedersen , +45 41 19 10 51, mip@dst.dk, Team Registre, Head of Section, Head of Section, Mikkel Illum Svendsen , +45 30 89 40 55, mse@dst.dk, Head of Section, Head of Section, Josefine Gløerfeldt Kjæmpe , +45 20 55 83 51, jgk@dst.dk, Head of Section, Head of Section, Astrid Neumann , +45 30 62 40 24, neu@dst.dk, Head of Section, Head of Section, Albert Elias Öhrman Wellendorf , +45 21 19 78 33, awd@dst.dk, System Analyst, System Analyst, Christian Flies Bendtsen , +45 51 48 61 49, chb@dst.dk, System Analyst, System Analyst, Lise Tanghus , +45 21 72 75 68, lta@dst.dk

https://www.dst.dk/en/OmDS/organisation/TelefonbogOrg?kontor=09&tlfbogsort=sektion

VNKSFK: Versionstabel NKSFK - Nationalregnskabets finansielle konti

version, sector, balance sheets, account entry, financial instrument, counterpart sector and time
1999Q1-2025Q1 (m DKK)

https://www.statbank.dk/VNKSFK

Tables in StatBank

BIL63: Families purchase of vehicles

unit, family type, patteren of purchase and time
1999-2024 (Per cent)

https://www.statbank.dk/BIL63

Tables in StatBank

LABY36A: 20 year-olds upper secondary school (share in per cent))

municipality groups, educational graduation statement and time
2008-2024 (Share in per cent)

https://www.statbank.dk/LABY36A

Tables in StatBank

SILC60: Health issues

question, background information, unit and time
2021-2024 (-)

https://www.statbank.dk/SILC60

Tables in StatBank

Linking of additional data

Statistics Denmark’s register data can be linked with other data materials, here called additional data. This can be, for example, extractions from registers outside Statistics Denmark, your own data – for example survey data – or data from other data providers., Additional data must be documented and comply with the same requirements to data minimisation and statistical disclosure control that Statistics Denmark applies in general., These requirements must ensure that only additional data needed in the project is provided and that Research Services get the information necessary to be able to handle the additional microdata and make it available in the specific project., Use of additional data must comply with the same rules regarding confidentiality and transfer as those that apply to Statistics Denmark’s microdata. , Read more about the rules on transfer and sanctioning, Any other data must be provided safely to Statistics Denmark. , You will find the guide for uploading additional data sets under ‘Use of FSE upload’, Requirements for additional data, Only approved and documented data:, Additional data must be covered by an approved project proposal. Documentation of the additional data content must be uploaded as an appendix in Denmark’s Data Portal. See below under ‘Documentation of additional data’., No information identifying individuals or businesses:, Personal names, company names, responses with free text in surveys and other information roughly identifying individuals or businesses is not allowed to be included in additional data. Such variables must be removed or categorised before additional data is provided to Research Services., Only the required key variables:, You may include only the key variables, e.g. civil registration number, required to link the additional data with the other data on the project. Key variables that are not needed must be removed before data is provided to Research Services., Only numeric variables and categorised text variables:, Additional data may not include non-categorised text variables, such as free text., Only information required for the specific project:, Key variables for which there is no need, must be removed before data is provided to Research Services., File formats, Additional data may be provided in the following formats:, .ASC, .CSV, .DTA, .ODS, .PDF, .SAS7BCAT, .SAS7BDAT, .SAV, .XLS, .XLSX, Documentation of additional data, Additional data must be documented, so that Research Services gets the information that is necessary to be able to handle the additional data and provide it for the specific project. For that reason, the institution is responsible for uploading an overview with the below content as an appendix in Denmark’s Data Portal., A short description of data (for example origin and content), Name of the data set, names of variables and a description of the variable content., The key variables that must be de-identified. This means the variables required to link the additional data with the other data in the project (e.g. civil registration number)., Which additional variables must be de-identified? This means variables that can be attributed directly to individuals or businesses (e.g. CVR number, grant number for health practitioner, serial number, or other ID numbers)., Does the additional data include key variables that must be linked with key variables in previously provided data sets?, If data is provided directly to Research Services from another data provider, further documentation may be necessary, e.g. variables that must be deleted (see ‘Requirements for additional data’ above)., The overview must be uploaded as an appendix in Denmark’s Data Portal under ’Additional data sources’ in a generally available format (Excel, Word or similar)., If data is to be linked with more populations, the documentation must be attached as an appendix under ‘Additional data sources’ for minimum one of these populations. The additional data must appear under ‘Additional data sources’ for each population., When the additional data has been provided to Statistics Denmark and the documentation has been uploaded in Denmark’s Data Portal, it is recommended that you notify the project owner in Research Services via email., Prices for delivery of submitted data, The price for the delivery of submitted data is variable. Once we have received the data, we prepare a framework agreement with a maximum expected time consumption. After delivery of the data, we settle based on the actual time consumption. , See more about framework agreements under Prices and price agreements, ., The expected time consumption depends on many factors, including the number, size, complexity and format of the files. Therefore, we always prepare framework agreements for submitted data on a case-by-case basis, and only when we have received the specific data sets., The table below provides a guide to the typical relationship between the number of data sets and the maximum expected time consumption. Please note, however, that the number of data sets is only one of many factors, and the table is therefore only a guide. Other factors, such as size, number of variables, or special treatment, may increase or decrease the number of hours in the specific framework agreement. Contact the project manager in Research Services if you need a more precise estimate., See the current hourly rates under Prices and price agreements, Number of datasets, Typical number of hours in framework agreement (indicative), 1-2, 2-4, 3-10, 4-8, 11-20, 8-14, 21-50, 14-20, NOTE: The number of hours in the framework agreement is typically set to accommodate unforeseen circumstances. Since the settlement is based on the actual time spent, the final price will in many cases be lower., Submitting files that do not include microdata, Files that you need in your project and that do not include microdata (e.g. programme files), must not be uploaded via FSE Upload., The files can be sent directly to the project owner in Research Services, if you are working on a subproject for a project database. If you are working under the researcher scheme, you can send an email to , forskningsservice@dst.dk, . In both instances, you must attach the files to the email. Further, you must:, Confirm that you have checked the files to ensure that they do not include microdata., Confirm that the files do not include microdata., Provide a short description of the content of the files and its relevance in terms of the purpose of the project., Indicate the specific path to where the files must be located., Ensure that the files are submitted in a generally available format that can be opened and checked by Research Services without use of specialised software.,  , De-identification, When the additional data has been received in Research Services it will be de-identified in the same way as any other data that belongs to the project. This happens by de-identifying key variables. Subsequently, the additional data is made available together with any other data in the project., Providing additional data to Research Services, Additional data must be provided safely to Statistics Denmark, Additional data can be provided safely to Statistics Denmark in the ways stated below:, Use of FSE Upload, Under Statistics Denmark’s microdata schemes, it is possible to upload additional files with data to be used in an existing project. Only data and documentation can be uploaded. Programmes etc. can be sent to the Research Services employee who is responsible for the project (project owner)., The documentation must either be sent to the project owner from Statistics Denmark or be uploaded in one of the allowed file formats., Before you upload, Before you upload data to be used in a project, you must ensure that the criteria for use of your data in the project have been met. The requirements are described at the top of the page under ‘Requirements for additional data’., The handling of additional data is invoiced according to the actual time used, unless otherwise agreed., Contact the project owner in Statistics Denmark in advance., How to upload the files, You log in via remote.dst.dk in the same way as when you are going to work on a project., Under 'Applications and Links' select 'FSE-UPLOAD'., Write the project number of the project where your data is to be used., When the project title is shown next to the project number, you must check that you have selected the right project for uploading of data., If relevant, add a comment concerning your data in the comments field for the project owner at Statistics Denmark. Actual correspondence should take place via email. , Add files to be uploaded by clicking `Add file'. You can add one or more files. Each file may run up to 2 GB., Note that not all types of files can be uploaded. You can see the list of allowed types under `File formats' further up on the page., When all files have been selected, you must click `Upload'., When all the files have been uploaded, you can log out in the bottom right-hand corner., If relevant, see , this guide for FSE upload (pdf, in Danish), , which includes screenshots of the upload process., Use of secure email, Data can be sent via secure email to , forskerpost@dst.dk, in one of two ways: , The institution retrieves Statistics Denmark's certificate at the website for download of security certificates (in Danish): Select , forskerpost@dst.dk, . For Outlook, we recommend the Vcf format. , After this, additional data must be sent to , forskerpost@dst.dk, . Always indicate project number and project owner in Research Services in the subject field of the email and notify the project owner in Research Services directly, once the additional data has been sent. Statistics Denmark does not offer any support for encryption or digital signature. Refer to your own IT department for guidance using mitID and secure email., The institution can use a secure, encrypted tunnel (SEPO). The set-up is individual for different institutions and must be handled by the institution's IT department, which should be involved before the additional data is sent., You must always indicate the project number and notify the project owner in Research Services that the email has been sent using an encrypted tunnel (SEPO). If using an encrypted tunnel, additional data must also be sent to , forskerpost@dst.dk, ., Registered letter or personal delivery, For data security reasons, we recommend that you use one of the above options., If this is not possible (e.g. if the files are very big), it is possible to provide password-protected additional data on physical media directly to Statistics Denmark at the below address. The contact person for the project in Research Services and the project number must always appear from the material handed in:, Statistics Denmark, Service Desk, Sankt Kjelds Plads 11, 2100 Copenhagen Ø, Att. Contact person for the project in Research Services, Re. project number: 7XXXXX, Additional data can either be delivered personally at Statistics Denmark's reception or be sent by registered mail to Statistics Denmark on a physical medium (DVD, CD-ROM or USB, which will not be returned). When provided on a physical medium, the additional data must be password-protected. Password must not be provided together with the physical medium., When the additional data has been received, you must send the password via email to the contact person for the project in Research Services.,  , Other data providers, Other data providers can provide additional data directly to Statistics Denmark at the request of the institution and by agreement between Research Services and the data provider. Delivery of additional data must take place in one of the above ways, but you must make sure that the additional data complies with the requirements above before it are delivered to Research Services., Do , not , send data via standard email, Additional data must not be sent via standard email, since this is not a secure delivery mode.

https://www.dst.dk/en/TilSalg/data-til-forskning/anmodning-om-data/tilknytning-af-ovrige-data

Sanction rules

It is important that you familiarise yourself with and comply with Statistics Denmark’s transfer and data security rules. If you do not comply with the rules, you risk suspension of you or your entire institution with Statistics Denmark. Read about our sanction rules and case processing in case of data breach., Users of Statistics Denmark’s researcher machines are responsible for complying with our transfer and data security rules. This means that you, as a user, are responsible for: , Your work on the researcher machines being compliant with Statistics Denmark’s data security rules. , Read more under Rules for working with microdata,  , Transferring analysis results and materials in compliance with Statistics Denmark’s transfer rules. , Read more under Rules on transfer of analysis results,  , Notifying Research Services immediately if you realise that you have failed to comply with Statistics Denmark’s data security or transfer rules., For more details, read Statistics Denmark’s guideline material:, Rules for data safety under the microdata schemes (pdf), Breach of the rules? This is how you handle it, If you have broken Statistics Denmark’s rules or suspect that you have, you have a duty of notification. Complying with the duty of notification in relation to breach will be considered a mitigating circumstance., Please notify both the person responsible for authorisation in your institution and Research Services; the latter by sending an email to , FSEHjemtag@dst.dk, with the following: , Your ident and the authorisation number of the institution you are associated with, Project number, if any, A description of the breach or where you suspect a breach, Date and time of the breach , If the breach involves files, for example files you have transferred, image files on your computer, in your mail box or similar, you must delete them immediately from your PC, Denmark’s Data Portal, mail folders etc. and inform about this in your email to Research Services.,  , Statistics Denmark’s sanction rules, If there is a breach of Statistics Denmark’s transfer rules or data security rules, Statistics Denmark can sanction users and, worst-case-scenario, entire institutions. Statistics Denmark’s sanction rules will be deployed if: , A user breaks the rules for working with microdata on Statistics Denmark’s researcher machines, for example by taking a screendump or transcribing from the researcher machine, , or, A user has transferred data with microdata, for example transferred a file with pseudonymised key variables from BOPIKOM, Note, : An isolated breach of the rules of statistical disclosure control will not result in sanctions. In case of repeated non-compliance, however, it can result in sanctions for the institution., Sanctions in case of breach - Assessment of severity and scope, Statistics Denmark makes decisions about sanctions. We distinguish between less severe and severe breaches: , Less severe breaches, : Thoughtless action or accident – for example identification in connection with troubleshooting, Severe breaches, : Conscious action – for example conscious attempt to identify individuals or enterprises in data , Statistics Denmark decides whether a breach is categorised as less severe or severe. In the assessment of the severity of a breach, we take the following into account:, Was it a thoughtless or conscious action?, Has the user detected the breach himself, and if so, observed his duty of notification?, In connection with transfer, : How large a volume of microdata has the user transferred?, In connection with transfer, : Has the transfer tool in Denmark’s Data Portal been used for the transfer, and if so, has the user ignored the transfer module’s warning? , In case of isolated, less severe breaches, the sanction will target the user and the project where the breach has happened. This means that the project where the breach took place will be temporarily closed for everybody and the user’s access temporarily closed, so that he or she cannot access his or her projects. In case of severe or repeated breaches, i.e. where breaches have previously been registered on the institution number, the sanctions will be more rigorous. See the overview of sanctions below., Note, : If Statistics Denmark has previously registered a breach for an institution, breaches dating back more than 2 years will not be taken into consideration. This means that any new breaches will be handled as first-time-breaches., Overview of sanctions , Sanction system for the researcher scheme,  , Sanction against user and project, Access is closed for user and access to the project is closed , Sanction against institution, Access is closed for all users and access to all projects is closed , Occurrence, First time, Second time, in 2 years, Third time, in 2 years, Fourth time, in 2 years, Less severe , breach, Until report can be approved*, 1-month suspension*, 3-month suspension*, Concrete, assessment*, Potential termination of the institution’s authorisation agreement, Severe breach, 3-month suspension*, 3-month suspension*, Potential termination of the institution’s authorisation agreement and/or specific user agreement, 6-month suspension*, Concrete evaluation of the institution’s authorisation agreement and potential termination of the institution’s authorisation agreement*, Sanction system for the authority scheme,  , Sanction against user , Access is closed for user , Sanction against scheme, Access is closed for users of the scheme, Occurrence, First time, Second time , in 2 years, Third time , in 2 years, Fourth time , in 2 years, Less severe , breach, Until report can be approved*, 1-month suspension, 1-month suspension, Concrete assessment, Potential termination of authorisation agreement, Severe breach, 3-month suspension, 3-month suspension, Potential termination of authorisation agreement and/or user agreement, 3-month suspension, 6-month suspension, Potential termination of authorisation agreement, * When Statistics Denmark detects a breach that comes under the sanction rules, the user and the project where the breach occurred will be temporarily suspended, until Statistics Denmark has processed the case and made a decision. This applies regardless if it is an isolated breach or repeated breaches within two years. , Statistics Denmark makes a decision based on a report and a plan that must be presented to Statistics Denmark by the institution with which the user is associated. Statistics Denmark will not commence the processing of the case, until we have received an adequate report and plan. Statistics Denmark estimates whether the report and plan of an institution is adequate or should be rewritten.  , You can read more about Statistics Denmark’s case processing and the requirements to the report and the plan under ”Statistics Denmark’s case processing in connection with breach of rules - guide”.,  , Statistics Denmark’s case processing in connection with breach of rules - guide, When Statistics Denmark receives a notification, or we find out ourselves that a user has not complied with Statistics Denmark’s data security and transfer rules, the user in question and the project where the breach has taken place will be temporarily suspended. The suspension lasts until Statistics Denmark has received an adequate report about the incident and a plan for prevention of similar breaches in future, and Statistics Denmark has processed and decided the case., The case processing step-by-step , The process takes place in the following steps:, Step: Presentation and demand for report and plan, When Research Services receives a notification, or find out themselves that a user has not complied with Statistics Denmark’s rules, the user in question and the person responsible for authorisation in the institution will be notified by email., Research Services informs about the date of the suspension of the project and of the user in question, and they will request an adequate report about the incident and the scope of the breach as well as an adequate plan for preventing similar breaches in future. Both the report and the plan must be completed in the standard template provided by Research Services., The person responsible for authorisation in the institution is responsible for the report and the plan being prepared and sent to Research Services., Presentation and plan – demand for “adequacy”, With the demand for adequacy, Research Services asks for an adequate report about the incident and the scope of the breach. By an adequate plan is meant a report and any documentation for appropriate technical, organisational and/or staff-related measures the institution has implemented in the light of the breach. The plan can consist of e.g.:, A brief account of the current rules and practice in the institution that may be relevant for the case, A presentation of what the institution has done in connection with the breach, for example, which consequences it has had for the user, A plan for what the institution is going to do to prevent similar breaches in future, It is important that it is not statements of intent. This means that the institution must account for the initiatives that they have already implemented or will implement, and describe the process behind it. Examples could be:, Has the person responsible for authorisation held a meeting with relevant stakeholders in the institution about the breach? (Indicate: Who? When? Which proposals/decisions were made?). Attach any resolution minutes., Has the person responsible for authorisation made proposals or suggested solutions to a relevant committee, the executive board, the governing body or similar? (Indicate: Who? When? What is/was on the agenda? What was decided?). Attach the agenda and/or resolution minutes., Has a decision been made in the institution to enhance for example the communication, instructional materials, code of conduct or similar? (What? How? When? Who is the target group?)., Has the institution adopted or made any other efforts to prevent similar breaches in future? (What? How? When? Who is the target group?)., If Research Services estimates that the report, plan or both are inadequate, Statistics Denmark will notify you about it and request a new one., Step: The case processing in Statistics Denmark, When Statistics Denmark estimates that the report and plan we have received are adequate, Research Services will prepare the case for Statistics Denmark’s Supervisory Board and Director General. You can expect the case processing to take approximately 8 working days from we receive the adequate report until we send our decision., Step: Decision, When Statistics Denmark has made a decision of the case, we send a decision letter by email to the person responsible for authorisation. The letter contains the final decision from Statistics Denmark’s Director General, including the reason for the decision and information on whether the temporary suspension of the project and the user is lifted or whether further sanctions are imposed on the user or the institution., Guides, agreements and documents in relation to data security and responsibility, Statistics Denmark’s data security rules under the Microdata schemes, Rules for data safety under the microdata schemes (pdf), Statistics Denmark’s information security and data confidentiality policy , Information security and data confidentiality policy – Statistics Denmark, Agreements (in Danish), Autorisationsaftale (pdf), Databehandleraftale (pdf), Tilknytningsaftale (pdf), Brugeraftale (pdf)

https://www.dst.dk/en/TilSalg/data-til-forskning/regler-og-datasikkerhed/sanktionsregler