Conduct a study to document maintenance and associated funding requirements for critical research software packages for a research discipline or field #30
Potential Activity Scope
This process would need to begin with a clear definition of the scope of the study, identifying the specific research discipline or field, and the criteria for determining what constitutes ""critical"" research software packages within that context.
Next, a comprehensive review of existing literature and data sources would be conducted to gather preliminary information about the software packages, their usage, maintenance needs, and funding mechanisms. This review would help in understanding the landscape and identifying gaps in existing knowledge.
Following the review, a research methodology would be designed, outlining the approach for data collection and analysis. This might include surveys, interviews, or focus groups with developers, users, and other stakeholders involved in the software packages. The methodology would need to be tailored to capture detailed information about the maintenance needs, including technical requirements, human resources, timelines, and potential challenges (including funding-related challenges).
Throughout the entire process, continuous engagement with stakeholders should ideally be maintained, ensuring that the study remains aligned with the needs and interests of the research discipline or field.
Potential Objectives
To define the scope of the study by identifying the specific research discipline or field and determining the criteria for "critical" research software packages.
To conduct a comprehensive review of existing literature and data sources to understand the current landscape of software packages, their usage, maintenance needs, and funding mechanisms.
To design a research methodology tailored to capture detailed information about maintenance needs, including technical requirements, human resources, timelines, and potential challenges.
To execute surveys, interviews, or focus groups with developers, users, and other stakeholders to gather insights into the maintenance and funding requirements.
To analyze the collected data, identifying patterns, trends, relationships, and disparities within the maintenance and funding requirements.
To synthesize the findings into a cohesive report or publication, providing key insights, implications, and recommendations.
To develop a dissemination strategy to ensure that the study reaches relevant stakeholders, including researchers, developers, funders, policymakers, and the broader research community.
To maintain continuous engagement with stakeholders, ensuring alignment with the needs and interests of the research discipline or field.
To conduct regular monitoring and evaluation to ensure the quality and relevance of the study.
Targeted Impacts
Enhanced understanding of the maintenance needs and funding requirements for critical research software packages within a specific discipline or field.
Identification of gaps and challenges in the current maintenance and funding landscape, providing actionable insights for improvement.
Increased awareness and collaboration among researchers, developers, funders, and other stakeholders, fostering a shared commitment to supporting critical research software.
Development of evidence-based recommendations and guidelines that can inform policies, practices, and investments related to research software maintenance and funding.
Strengthened alignment between research software needs and available resources, leading to more efficient and effective use of funds and human capital.
Creation of a valuable knowledge base that can be leveraged by other disciplines or fields, contributing to broader efforts to enhance the sustainability and impact of research software.
This potential activity was curated as part of "Charting the Course: Policy and Planning for Sustainable Research Software," a Sloan Foundation-funded project within URSSI dedicated to supporting the future of research software through evidence-informed policy work (Project contacts are: @danielskatz and @dr-eric-jensen). If you are interested in working on this, please add a comment.
Potential Activity Scope This process would need to begin with a clear definition of the scope of the study, identifying the specific research discipline or field, and the criteria for determining what constitutes ""critical"" research software packages within that context.
Next, a comprehensive review of existing literature and data sources would be conducted to gather preliminary information about the software packages, their usage, maintenance needs, and funding mechanisms. This review would help in understanding the landscape and identifying gaps in existing knowledge.
Following the review, a research methodology would be designed, outlining the approach for data collection and analysis. This might include surveys, interviews, or focus groups with developers, users, and other stakeholders involved in the software packages. The methodology would need to be tailored to capture detailed information about the maintenance needs, including technical requirements, human resources, timelines, and potential challenges (including funding-related challenges).
Throughout the entire process, continuous engagement with stakeholders should ideally be maintained, ensuring that the study remains aligned with the needs and interests of the research discipline or field.
Potential Objectives
Targeted Impacts
This potential activity was curated as part of "Charting the Course: Policy and Planning for Sustainable Research Software," a Sloan Foundation-funded project within URSSI dedicated to supporting the future of research software through evidence-informed policy work (Project contacts are: @danielskatz and @dr-eric-jensen). If you are interested in working on this, please add a comment.