Conduct an economic research study of the costs/savings from shifting research software to open source #28
Labels
Activity: Research
This is a research-type activity
Activity
This is a policy activity
Effort: Small
Less than 1 person-year estimated to deliver this.
Topic: Impact
This topic encompasses software's academic impact, value and importance
Potential Activity Scope
Conduct an economic research study to quantify the money that has implicitly funded maintenance and sustainability, and has been saved or lost in the shift to open source for research software (e.g., where have funds been spent on one-off software rather than maintaining existing open source software, and where has an investment in software maintenance saved funds from being spent on one-off software).
Data collection should be a central component of the study. This should involve gathering diverse data sources, including financial records, project documentation, market analysis, and expert opinions specific to the research software domain. The data should be comprehensive, credible, and contextual, reflecting the unique characteristics and challenges of research software economics.
The analysis phase should employ rigorous economic models, methodologies, and metrics tailored to the research software context. This should enable a nuanced quantification of the financial investment, savings, losses, and overall value related to research software maintenance, sustainability, and open source transition. The analysis should be transparent, robust, and insightful, providing a clear understanding of the economic dynamics at play.
The findings of the research study should be synthesized into a coherent and compelling report.
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.
The text was updated successfully, but these errors were encountered: