Support for data management in DLN

DLN projects (including partner projects) can apply funding to support their data management work. Deadline 6. December.

DLN supports data management according to the FAIR principles. This includes secure management of sensitive data. We are strengthening our work and support on data management. Now in November, Korbinian Bösl is starting a senior engineer position on data management, shared between DLN and ELIXIR Norway. We hope the DLN projects will use this opportunity for support and advise on how to improve their data management. To make this easier, we strongly advice project leaders to appoint a responsible person for data management in the project. Several projects have done this already. These persons will be our major contact points towards the project on data management and they will be followed up more extensively

Available support for data management in research projects

Available funding: up to NOK 40 000,- pr application. Deadline; 30th November.

We have set aside funding to support projects on data management and welcome requests from the research projects (including partner projects). The limit for applied support is set to 40 000 NOK/application. However, this number will depend on the total amounts of applications or if several projects apply together. Examples of what we can support:

  • Collaborative developments between two or more projects. This could be developments of templates for data management, standard operating procedures, best practices, exchange of know how (meetings/workshops on data management).
  • Competence development of the appointed responsible data manager.
  • Manual help on FAIR data management. Resources for such support will likely have to involve several projects combined, but can be applied for separately.

Applications should be short and to the point, answer the requirements below and in the application form, including a tentative budget showing how the resources applied for will be used together with own contributions from the project(s).


The following requirements must be fulfilled and included to get the funding:

  • A responsible person (named) must be appointed for data management in the project.
  • A brief data management plan must be written for the project and attached (see suggested resources and checklist below).
  • A short description of how data management is executed in the project must be provided (see application form).

We welcome applications from single projects, however, if needed we will prioritize collaborative efforts between projects.

NB: Use the following on-line form for the application. A data management plan valid for the involved project(s) should be uploaded as an attachment (pdf). See below for suggestions on what to include.

Data Management Plan

Helpful resources for making data management plans can be found at the site of national infrastructures:

FAIR data management plan checklist

DMP component

Issues to be addressed

1. Data summary

  • What is the purpose of the data collection/generation and its relation to the objectives of the project?
  • What types and formats of data will the project generate/collect?
  • Will you re-use any existing data and how?
  • What is the origin of the data?
  • What is the expected size of the data? (if known)
  • To whom might it be useful ('data utility')?

2. FAIR Data

2.1. Making data findable, including provisions for metadata

  • Are the data produced and/or used in the project discoverable with metadata, identifiable and locatable by means of a standard identification mechanism (e.g. persistent and unique identifiers such as Digital Object Identifiers)?
  • What naming conventions do you follow?
  • Will search keywords be provided that optimize possibilities for re-use?
  • What metadata will be created? In case metadata standards do not exist in your discipline, please outline what type of metadata will be created and how.

2.2. Making data openly accessible

  • Which data produced and/or used in the project will be made openly available as the default? If certain datasets cannot be shared (or need to be shared under restrictions), explain why, clearly separating legal and contractual reasons from voluntary restrictions.
  • How will the data be made accessible (e.g. by deposition in a repository)?
  • What methods or software tools are needed to access the data?
  • Is documentation about the software needed to access the data included?
  • Is it possible to include the relevant software (e.g. in open source code)?
  • Where will the data and associated metadata, documentation and code be deposited? Preference should be given to certified repositories, which support open access where possible.
  • Have you explored appropriate arrangements with the identified repository? If there are restrictions on use, how will access be provided? Is there a need for a data access committee? Are there well-described conditions for access (i.e. a machine readable license)? How will the identity of the person accessing the data be ascertained?

2.3. Making data interoperable

  • Are the data produced in the project interoperable, that is allowing data exchange and re-use between researchers, institutions, organisations, countries, etc. (i.e. adhering to standards for formats, as much as possible compliant with available (open) software applications, and in particular facilitating re-combinations with different datasets from different origins)?
  • What data and metadata vocabularies, standards or methodologies will you follow to make your data interoperable?
  • Will you be using standard vocabularies for all data types present in your data set, to allow inter-disciplinary interoperability?
  • In case it is unavoidable that you use uncommon or generate project specific ontologies or vocabularies, will you provide mappings to more commonly used ontologies?

2.4. Increase data re-use (through clarifying licences)

  • How will the data be licensed to permit the widest re-use possible? (e.g.
  • Are the data produced and/or used in the project useable by third parties, in particular after the end of the project? If the re-use of some data is restricted, explain why.
  • How long is it intended that the data remains re-usable?
  • Are data quality assurance processes described? Further to the FAIR principles, DMPs should also address:
  • When will the data be made available for re-use? If an embargo is sought to give time to publish or seek patents, specify why and how long this will apply, bearing in mind that research data should be made available as soon as possible.

3. Allocation of resources

  • What are the costs for making data FAIR in your project?
  • How will these be covered?
  • Who will be responsible for data management in your
  • Are the resources for long term preservation discussed (costs and potential value, who decides and how what data will be kept and for how long)?


4. Data security

  • What provisions are in place for data security (including data recovery as well as secure storage and transfer of sensitive data)?
  • Is the data safely stored in certified repositories for long- term preservation and curation?

5. Ethical aspects

  • Are there any ethical or legal issues that can have an impact on data sharing? These can also be discussed in the context of the ethics review. If relevant, include references to ethics deliverables and ethics chapter in the Description of the Action (DoA).
  • Is informed consent for data sharing and long-term preservation included in questionnaires dealing with personal data?

6. Other

  • Do you make use of other national/funder/sectorial/departmental procedures for data management? If yes, which ones?


Rune Kleppe

Tlf: 55584068


Fatemeh Ghavidel


Korbinian Bösl




Publisert: 28. Oct 2019 - kl. 21:35
Sist oppdatert: 26. Nov 2019 - kl. 22:08