Papers  /

304.1 Defining requirements for machine-actionable data management plans

Contributors:
  1. Tomasz Miksa
  2. Peter Neish
  3. Andreas Rauber

Date created: | Last Updated:

: DOI | ARK

Creating DOI. Please wait...

Create DOI

Category: Communication

Description: Data Management Plans (DMPs) are free-form text documents describing data used and produced in research projects. The workload and bureaucracy often associated with tradi- tional DMPs can be reduced when they become machine- actionable. However, there is no common definition of what machine-actionable DMPs really are. This hinders the com- munication between stakeholders and leads to scepticism, or conversely to exaggerated expectations. This paper aims to clarify what machine-actionable DMPs are and provides examples of how involved stakeholders can benefit from them. It describes an open stakeholder con- sultation performed by the RDA DMP Common Standards working group. The main objective was to define the scope of information covered by machine-actionable DMPs and formulate an initial set of requirements for a common data model for machine actionable DMPs. To do this we used methodology known from system and software requirements engineering to collect information on how needs for infor- mation of particular stakeholders evolve over phases of the research data lifecycle. Data Management Plans (DMPs) are free-form text documents describing data used and produced in research projects. The workload and bureaucracy often associated with tradi- tional DMPs can be reduced when they become machine- actionable. However, there is no common definition of what machine-actionable DMPs really are. This hinders the com- munication between stakeholders and leads to scepticism, or conversely to exaggerated expectations. This paper aims to clarify what machine-actionable DMPs are and provides examples of how involved stakeholders can benefit from them. It describes an open stakeholder con- sultation performed by the RDA DMP Common Standards working group. The main objective was to define the scope of information covered by machine-actionable DMPs and formulate an initial set of requirements for a common data model for machine actionable DMPs. To do this we used methodology known from system and software requirements engineering to collect information on how needs for infor- mation of particular stakeholders evolve over phases of the research data lifecycle.

License: CC-By Attribution 4.0 International

Files

Loading files...

Citation

Components

  • 304. Machines in Action

    The two papers in Session 304 explore the issues and topics pertaining to the theme of Machines in Action with technology-driven examples. Session cha...

    Recent Activity

    Loading logs...

Tags

Recent Activity

Loading logs...

OSF does not support the use of Internet Explorer. For optimal performance, please switch to another browser.
Accept
This website relies on cookies to help provide a better user experience. By clicking Accept or continuing to use the site, you agree. For more information, see our Privacy Policy and information on cookie use.
Accept
×

Start managing your projects on the OSF today.

Free and easy to use, the Open Science Framework supports the entire research lifecycle: planning, execution, reporting, archiving, and discovery.