DMP requirements in FWF
As of 1 January 2019, the FWF requires a data management plan (DMP) for all project applications seeking approval and has provided its own template for this purpose. This DMP describes how data is collected, organised, stored, secured, preserved, shared, archived and destroyed for each specific project.
The DMP must be submitted together with the FWF funding contract for all approved projects and must be written in the same language as the funding application. It is a prerequisite for the start of your project and the FWF will check for completeness. The DMP should contain only the most important information and must not exceed a length of 10,000 characters (including spaces). If more information is needed, it can be provided via links to external sources.
The DMP should be regarded as a living document. It may be changed throughout the project, but be sure to document all changes. Submit the final version of your DMP with your final report. The FWF has defined a minimum set of criteria which must be addressed when filling out the DMP template.
- PDF: https://www.fwf.ac.at/fileadmin/files/Dokumente/Open_Access/FWF_DMPTemplate_e.pdf
- Word: https://www.fwf.ac.at/fileadmin/files/Dokumente/Open_Access/FWF_DMPTemplate_e.docx
When creating a FWF DMP, do consider the policy Open Access to Research Data.
This policy states that the research data which supports your scientific publication must be made openly available on a mandatory basis. This includes all the data required to reproduce and verify the results of your publications, including the associated metadata. This data should be published as soon as possible, but, at the latest, together with the corresponding scientific publication. If, for legal, ethical or other reasons, open access to this data is not at all or only partially possible, you must justify this in your data management plan. In addition, the following criteria apply:
- Data must be prepared in accordance with the FAIR principles.
- Institutional, disciplinary or cross-disciplinary repositories must be used for archiving.
- Data must be stored in such a way that it can be reused without restrictions (e.g. by granting a free licence).
- Archived records must be citable using a persistent identifier (e.g. DOI).