Research data management (RDM) encompasses all structured measures related to handling data in the research process. Ideally, RDM begins in the project’s planning phase and continues throughout, covering data collection, storage and description, and concluding with the data being made available for reuse, archiving and publication.
What Are Research Data?
Research data refers to digital or analog information generated, derived, or analyzed during scientific research. Examples include measurement data, source material, surveys, and observation logs. The scope of the term “research data” varies by research discipline.
Why Is Managing Research Data Necessary?
Although thorough research data management (RDM) takes time, it offers several benefits:
- Research visibility—and thus its citation frequency and reputation—is enhanced when data is discoverable during searches and in bibliographic databases. On average, publications with available data are cited slightly more frequently.
- The chances of securing research funding are improving. Many funding organizations now require applicants to submit a statement detailing their planned data management practices when applying, as data management is an integral part of good scientific practice. This is also considered in the evaluation of applications.
- The risk of data loss is minimized.
- Research data management ensures that data is preserved in a traceable manner over the long term. This helps when research findings need to be verified later and promotes transparency, facilitating the reuse of data in one’s own research.
Basic Principles of FDM
FAIR Principles
CARE Principles
Research Software Management
Research software management refers to the systematic management of software developed within a research project. In addition to data information, research funders often expect details about any software developed as part of the project. Research software management encompasses the creation, documentation, storage, versioning, licensing, archiving, and publication of software generated or used in a project.
This includes documentation of the underlying hardware, required software libraries, and other relevant resources. The documentation should provide enough detail to explain how a specific output was generated from an input using the software.