1. Administration
DMP version
RDMP-ID: {$f_19}	Creation date: {$f_29}	Last updated: {$f_31}
Document(s): {$f_55}	Data archive uploaded: {$f_56}	Archive name: {$f_59}
Project data manager(s)
Indicate the primary PI responsible for the project’s data management: supervising PI (for MSc students), (first) promotor (for PhD students), project/WP leader (for postdocs). Also include co-promotors and daily supervisors if different from the primary PI.
Student/researcher name: {$f_17}	S/P-number: {$f_18}	Research group: {$f_20}
Primary PI: {$f_30}	Additional supervisors: {$f_32}
Project administration
Briefly (3-5 sentences) describe the project and its expected results. For 2nd or 3rd money flow projects: indicate the funding agency and grant number.
Project title: {$f_21}
Project description: {$f_22}
Funding agency: {$f_23}	Grant number: {$f_24}	Project code: {$f_25}
Project start date: {$f_26}	Expected end date: {$f_27}	Extended end date: {$f_28}
External collaboration
In case of joint projects: indicate which external institutes/organizations are involved and who (PI) is responsible for data management at the external institute.
Institute/organization: {$f_33}	PI(s) responsible for externally collected data: {$f_34}
2. Data collection
For (legally) sensitive or confidential project data: indicate what type of data and which special procedures, permits and/or licenses are required.
Sensitive or confidential project data: {$f_60} {$f_61}
Indicate which special permits and/or licenses are required to collect the project data.
Required permit/license: {$f_35}
Description of the raw (primary) data
Indicate what type of data will be collected and whether a very large amount of data is expected (> 500 GB). Also indicate where the data will be collected (own/external institute), and whether the data is new or re-used from another project.
Primary data collected: {$f_36}
Expected amount of primary data: {$f_37}
Additional remarks: {$f_38}
Description of the processed (secondary) data
Indicate whether & how the raw data will be processed: what software, algorithms, workflows will be used?
Secondary data produced: {$f_39}
Expected amount of secondary data: {$f_58}
Additional remarks: {$f_40}
3. Data storage
Storage during the project
Indicate how & where primary and secondary data are stored during the project: how often are stored data backed-up; how is version control realized? If relevant: indicate how the privacy of test subjects is guaranteed.
Long-term storage with automated back-up: {$f_41}
Cloud-based storage & sharing: {$f_42}
Short-term storage: {$f_43}
Special storage facilities: {$f_44}
Data archiving
Indicate how, where & for how long primary and secondary data will be archived, including specific software that is used or other relevant information needed to verify the research results.
Default procedure:
All primary and secondary data are archived in a single zip-file, also including the final report, thesis or publication of the project and one or more metadata files that document the data archive. The archive is stored in the institute repository; archives will be stored for at least 10 years.
Additional archiving requirements/agreements: {$f_46}
4. Data ownership
If applicable: Indicate whether specific agreements apply with regard to data access, e.g. contractual obligations to third parties (commercial or other), embargo requirements for publication, etc.
RUG default:
The research institute acts as the legal representative of the University of Groningen and holds ownership of all research data collected, generated or otherwise acquired within the institute unless different arrangements are clearly documented and approved by the institute director.
Additional agreements on data ownership: {$f_48}
Default access:
The purpose of the institute data repository is archive-only; access to archive files is restricted to senior staff members ultimately responsible for the corresponding research projects.
Additional agreements on data access: {$f_50}
5. Data documentation
Metadata
Indicate how & for whom metadata (data documentation) is organized.
Default documentation:
The data archive includes a standard metadata file (read_me_first.txt) that is set up according to the guidelines in the institute data archiving procedure; for archives consisting of multiple folders a read_me_first.txt metadata file is included for each folder.
Additional remarks: {$f_52}
File formats & naming standards
Indicate which data formats will be used in the project; if non-standard data formats are used: explain how these formats can be read (include the appropriate software or a link to its source).
Default procedure:
The project aims to use the preferred or acceptable data formats listed in the guidelines in the institute data archiving procedure. All file names, metadata and other description files and comment lines in code are in English. The data archive follows the naming standards provided in the institute data archiving procedure.
Non-standard data formats used: {$f_54}