Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
113
datasets available to search
ShareScore release 0.9.0
Dataset results
113 results for “research software”
GitHub Profiles (users/organisations) and Repositories (research/non-research) of Potsdam Researchers and Research Organisations: An annotated dataset of with howfairis and software quality variables.
<p>This dataset accompanies the paper <em>"Software FAIRness, Documentation and Development Practices in Potsdam Researchers' GitHub Repositories"</em> It includes 3 CSV files that contain data related to github profiles of users/organisations, their repositories annotated as research/non-research repositories and followed by FAIRness and other software qualtiy variables. The data were collected using <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP">SWORDS-template-UP</a> (v1.0.0) methods (collect_users, collect_repositories, collect_variables) which is extended version of <a href="https://github.com/UtrechtUniversity/SWORDS-template">SWORS-template</a> adopted according our needs and detailed in the paper.</p> <p><strong>GitHub (research) user/organisation profiles. ( <em>github_profiles.csv )</em></strong></p> <table> <tbody> <tr> <td><strong>Column name</strong></td> <td><strong>Description </strong></td> </tr> <tr> <td>user_id</td> <td>GitHub username </td> </tr> <tr> <td>html_url </td> <td>URL of the GitHub profile </td> </tr> <tr> <td>type </td> <td>Type of profile (user or organization)</td> </tr> <tr> <td>organisation</td> <td>Acronym or name of the organization </td> </tr> </tbody> </table> <p><strong>GitHub repositories <em>(github_repositories.csv)</em></strong></p> <p>This file contains the repositories scraped from the GitHub profiles of research users and organizations.</p> <table> <tbody> <tr> <td><strong>Column name </strong></td> <td><strong>Description </strong></td> </tr> <tr> <td>html_url </td> <td>URL link to the repository </td> </tr> <tr> <td>description</td> <td>GitHub project description </td> </tr> <tr> <td>project</td> <td>Specifies if the project is research or non-research</td> </tr> <tr> <td>language</td> <td>Programming language used in the project </td> </tr> <tr> <td>organisation</td> <td>Acronym or name of the university, institution, or research organization</td> </tr> <tr> <td>research_group</td> <td>Acronym or name of the research group the repository belongs to</td> </tr> </tbody> </table> <p><strong>Research repositories filtered and annotated <em>(github_research_repositories_filtered_annotated.csv)</em></strong></p> <p>This file contains filtered and annotated information about research repositories.</p> <table> <tbody> <tr> <td><strong>Column Name </strong></td> <td><strong>Description </strong></td> <td><strong>Collection Method </strong></td> </tr> <tr> <td>html_url </td> <td>Repository URL </td> <td> </td> </tr> <tr> <td>howfairis_repository</td> <td>Indicates if the repository is public or private (True/False) </td> <td>(Script- <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/tree/main/collect_variables#usage">howfairis_variable.py</a>) is a wrapper for <a href="https://pypi.org/project/howfairis/">howfairis</a> pypi library that checks the 5 recommendations of <a href="https://fair-software.nl">FAIR</a></td> </tr> <tr> <td>howfairis_license </td> <td>Indicates if the repository has a license (True/False)</td> <td>(Script- <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/tree/main/collect_variables#usage">howfairis_variable.py</a>) is a wrapper for <a href="https://pypi.org/project/howfairis/">howfairis</a> pypi library that checks the 5 recommendations of <a href="https://fair-software.nl">FAIR</a></td> </tr> <tr> <td>howfairis_registry</td> <td>Indicates if the repository has implemented community registry (True/False)</td> <td>(Script- <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/tree/main/collect_variables#usage">howfairis_variable.py</a>) is a wrapper for <a href="https://pypi.org/project/howfairis/">howfairis</a> pypi library that checks the 5 recommendations of <a href="https://fair-software.nl">FAIR</a></td> </tr> <tr> <td>howfairis_citation</td> <td>Indicates if the repository has a .cff file (True/False) </td> <td>(Script- <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/tree/main/collect_variables#usage">howfairis_variable.py</a>) is a wrapper for <a href="https://pypi.org/project/howfairis/">howfairis</a> pypi library that checks the 5 recommendations of <a href="https://fair-software.nl">FAIR</a></td> </tr> <tr> <td>howfairis_checklist</td> <td>Indicates if the repository has implemented OpenSSF best practices badge (True/False)</td> <td>(Script- <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/tree/main/collect_variables#usage">howfairis_variable.py</a>) is a wrapper for <a href="https://pypi.org/project/howfairis/">howfairis</a> pypi library that checks the 5 recommendations of <a href="https://fair-software.nl">FAIR</a></td> </tr> <tr> <td>fair_score</td> <td>Score based on howfairis variables (0-5) </td> <td> </td> </tr> <tr> <td>dlr_soft_class</td> <td>Name of the university, company, research institute, or research organization</td> <td>(Manual) Annotated the repository based on <a href="https://core.ac.uk/reader/211557820">DLR software engineering guideline.</a> There are no specific definitions on metrics how to categorise them (github repositories) into application classes. Which were needed to do a comparitive analysis. </td> </tr> <tr> <td>installation_instruction</td> <td>Presence of installation instruction (True/False) </td> <td>(Manual) Checked the presense of Installation Instruction in the readme or in the project wiki pages. </td> </tr> <tr> <td>project_information </td> <td>Presence of basic project information in README (True/False) </td> <td>(Manual) Checked if the readme have basic information about the project. </td> </tr> <tr> <td>usage_guide</td> <td>Presence of folder named test/tests in the root directory (True/False)</td> <td>(Manual) Checked the presense of Usage Guide in the readme or in the project wiki pages. For command line tools checked if they have help command which guides how to use the tool. </td> </tr> <tr> <td>test_folder</td> <td>Presence of folder named test/tests in the root directory (True/False)</td> <td> <p>(Script - <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/blob/docs/collect_variables/scripts/soft_dev_pract/test_folder.py">test_folder.py</a>) Checks the folder names test/tests in the root directory of the repository.</p> </td> </tr> <tr> <td>requirements_explicit </td> <td>Explicit requirements for Python, R, C++ repositories (True/False)</td> <td>(Script - <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/blob/main/collect_variables/scripts/soft_dev_pract/requirement_explicit.py">requirement_explicit.py</a>) Checks the files (requirements.txt, DESCRIPTION, CMakeLists.txt) in the root directory. </td> </tr> <tr> <td>continuous_integration</td> <td>Indicates if the repository uses continuous integration (True/False)</td> <td>(Script- <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/blob/main/collect_variables/scripts/soft_dev_pract/continious_integration.py">continious_integration.py</a>) Checks the presence of folder .github (github actions) same for other continious integration (travisCI, CircleCI, Jekins, azure pipeline)</td> </tr> <tr> <td>ci_tool </td> <td>Name of the continuous integration tool used</td> <td>(Script- <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/blob/main/collect_variables/scripts/soft_dev_pract/continious_integration.py">continious_integration.py</a>) Checks the presence of folder .github (github actions) same for other continious integration (travisCI, CircleCI, Jekins, azure pipeline)</td> </tr> <tr> <td>add_lint_rule </td> <td>Indicates if additional linting rules are present (True/False)</td> <td>(Script - <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/blob/main/collect_variables/scripts/soft_dev_pract/add_ci_rules.py">add_ci_rules.py</a>) - it scans the YAML files in the <br>.github/workflows directory to detect the presence of (linters) Python, R, and C++.</td> </tr> <tr> <td>add_test_rule</td> <td>Indicates if additional testing rules are present (True/False) </td> <td>(Script - <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/blob/main/collect_variables/scripts/soft_dev_pract/add_ci_rules.py">add_ci_rules.py</a>) - it scans the YAML files in the <br>.github/workflows directory to detect the presence of (testing libraries) Python, R, and C++.</td> </tr> <tr> <td>comment_at_start</td> <td>Indicates the level of comments at the start of the program (most, more, some, less)</td> <td>(Script - <a href="https://github.com/Software-Engineering-Group-UP/SWORDS-template-UP/blob/main/collect_variables/scripts/soft_dev_pract/comment_at_start.py">comment_at_start.py</a>) Checks the presence of brief comments at the start at source code files in GitHub repositories.</td> </tr> <tr> <td>language </td> <td>Programming language used in the repository </td> <td> </td> </tr> <tr> <td>type </td> <td>Specifies if the profile is a user or organization </td> <td>Github organisation or user profiles.</td> </tr> <tr> <td>organisation </td> <td>Name of the university, company, research institute, or research organization</td> <td>Oraganisation name (from where the user was found)</td> </tr> <tr> <td>research_group</td> <td>Name or acronym of the research group </td> <td> </td> </tr> </tbody> </table> <p> </p> <p>Data for publication - https://github.com/Software-Engineering-Group-UP/potsdam-research-repos</p>
The Research Software Alliance (ReSA) and the community landscape
<p>The Research Software Alliance (ReSA)’s mission is to bring research software communities together to collaborate on the advancement of research software. ReSA has formed taskforces and one of them revolves around a <strong>software landscape analysis</strong> aiming to answer the question "How can we identify the different communities and topics of interest for the research software community (e.g., preservation, RSEs, citation, productivity, sustainability)?"</p> <p>Here we include text describing the work of the taskforce to date (see <a href="https://zenodo.org/api/files/5a1e0c32-cbf7-4b9a-9c02-139b2ce66e85/2020-03-11-ReSA-landscape.md?versionId=ffedcfe9-33f4-4aba-9d6b-9975fc1c548d">2020-03-11-ReSA-landscape.md</a>), as well as plans for the future, and an invitation to readers to contribute to the ReSA list of research software communities. We are a;sp including the current version of the list in a CSV file (see <a href="https://zenodo.org/api/files/5a1e0c32-cbf7-4b9a-9c02-139b2ce66e85/2020-03-11-ReSA-landscape.csv?versionId=be4bbcdd-79a8-4444-a764-98bf0d548922">2020-03-11-ReSA-landscape.csv </a>), and we welcome contributions on the live spreadsheet that can be found via this <a href="https://docs.google.com/spreadsheets/d/15JHqOxR4HIKHYe821IPvbxIuXP1zMjXKGEIJwB-GPqE/edit#gid=0">link</a>.</p>
Replication data [The who, what and how of the current research at the Brazilian Symposium on Software Engineering]
<p>Replication Data for the SBES paper <em>"The who, what and how of the current research at the Brazilian Symposium on Software Engineering"</em></p> <p>Dataset containing analysis (who, what and how) of 90 SBES papers: 27 from SBES’19, 43 from SBES’20, and 20 from SBES’21.</p>
Impact of Software Engineering Research in Practice: A Patent and Author Survey Analysis
<p>Dataset of the research paper: <strong>Impact of Software Engineering Research in Practice: A Patent and Author Survey Analysis</strong></p> <p>Existing work on the practical impact of software engineering (SE) research examines industrial relevance rather than adoption of study results, hence the question of how results have been practically applied remains open. To answer this and investigate the outcomes of impactful research, we performed a quantitative and qualitative analysis of 4 354 SE patents citing 1 690 SE papers published in four leading SE venues between 1975–2017. Moreover, we conducted a survey on 475 authors of 593 top-cited and awarded publications, achieving 26% response rate. Overall, researchers have equipped practitioners with various tools, processes, and methods, and improved many existing products. SE practice values knowledge-seeking research and is impacted by diverse cross-disciplinary SE areas. Practitioner-oriented publication venues appear more impactful than researcher-oriented ones, while industry-related tracks in conferences could enhance their impact. Some research works did not reach a wide footprint due to limited funding resources or unfavorable cost-benefit trade-off of the proposed solutions. The need for higher SE research funding could be corroborated through a dedicated empirical study. In general, the assessment of impact is subject to its definition. Therefore, academia and industry could jointly agree on a formal description to set a common ground for subsequent research on the topic.</p> <p>The following data files are included.</p> <ul> <li><em>./fields</em>: <ul> <li><strong>engi-fields.csv</strong>: Publication and PhD dissertation counts of main engineering branches</li> <li><strong>engi-fields-queries.txt</strong>: Queries applied to Elsevier's Scopus and Open Access Theses and Dissertations databases to retrieve the publication and dissertation counts</li> </ul> </li> <li><em>./patents</em>: <ul> <li><strong>sample-se-references-verified.csv</strong>: Manual verification of a random sample of references by software engineering (SE) patents to SE papers</li> <li><strong>se-cpc.tsv</strong>: Manually-identified SE-related Cooperative Patent Classification (CPC) categories</li> <li><strong>se-references-in-patents.csv</strong>: SE references made by SE patents to SE papers</li> <li><em>./patents/litigation</em>: <ul> <li><strong>case-values.csv</strong>: Manually-retrieved litigation damages of citing SE patents</li> <li><strong>lit-per-paper.csv</strong>: Litigation cases of citing SE patents</li> </ul> </li> <li><em>./patents/maintenance</em>: <ul> <li><strong>maint-code-fee-mapping.csv</strong>: Mapping of patent maintenance fee codes to their fee values</li> <li><strong>maint-fees.csv</strong>: Fee values of maintenance fee codes</li> <li><strong>maint-per-paper.csv</strong>: Maintenance fee events of citing SE patents</li> </ul> </li> <li><em>./patents/reports</em>: <ul> <li><strong>lit-sum-per-paper.csv</strong>: Counts and total damages of litigation cases of patent-cited SE papers</li> <li><strong>maint-sum-per-paper.csv</strong>: Counts and total values of maintenance fee events of patent-cited SE papers</li> <li><strong>patent-ref-counts.csv</strong>: SE patent citation counts of patent-cited SE papers</li> </ul> </li> </ul> </li> <li><em>./survey</em>: <ul> <li><strong>emse-top.csv</strong>: Most-cited papers of the Empirical Software Engineering (EMSE) journal</li> <li><strong>icse-bp.csv</strong>: Distinguished papers of the International Conference of Software Engineering (ICSE)</li> <li><strong>icse-mip.csv</strong>: Most influential ICSE papers</li> <li><strong>icse-top.csv</strong>: Most-cited ICSE papers</li> <li><strong>survey-questionnaire-emse.pdf</strong>: The EMSE survey questionnaire</li> <li><strong>survey-questionnaire.pdf</strong>: The ICSE, TSE, and TOSEM survey questionnaire</li> <li><strong>survey-responses.csv</strong>: The anonymized survey responses</li> <li><strong>tosem-top.csv</strong>: Most-cited papers of the ACM Transactions on Software Engineering and Methodology (TOSEM)</li> <li><strong>tse-top.csv</strong>: Most-cited papers of the IEEE Transactions on Software Engineering (TSE)</li> <li><em>./survey/manual-coding</em>: <ul> <li><strong>feedback.txt</strong>: Manual coding of survey feedback</li> <li><strong>practical-impact.csv</strong>: Manual coding of responses about practical impact of work</li> <li><strong>practical-impact-lack.csv</strong>: Manual coding of responses about lack of practical impact</li> <li><strong>research-methods.csv</strong>: Manual coding of additional research methods of surveyed papers</li> <li><strong>state-of-practice.csv</strong>: Manual coding of responses about changes in state of practice</li> </ul> </li> </ul> </li> <li><em>./venues</em>: <ul> <li><strong>se-venues.csv</strong>: Top SE venues according to Google Scholar Metrics</li> <li><strong>se-venues-impact.csv</strong>: SE patent citations and patent-based impact factors of SE venues</li> <li><strong>se-venues-scopus-queries.txt</strong>: Queries applied to Scopus to retrieve the publication counts of the SE venues</li> </ul> </li> </ul>
Data Echoes: Tracking Data Availability and Integrity in Software Engineering Research
<p><strong>This is the dataset of the report: Data Echoes: Tracking Data Availability and Integrity in Software Engineering Research</strong></p> <p>It contains the following information of all the papers from ASE, FSE, and ICSE in 2023:</p> <ul> <li>Paper title</li> <li>Keyword</li> <li>Is the source data available and accessible in the paper?</li> <li>If the source data is not available, do the authors explain why?</li> <li>Hosting platforms</li> <li>Access mode</li> <li>License</li> <li>Is their experiment data reused from previous work, or newly generated specifically for this study, or combination of both? </li> <li>Do the authors change/modify their experiment data before experiment?</li> <li>What modifications do they perform?</li> <li>Does the link provide detailed instructions about how to replicate their paper?</li> <li>Does the link contains their complete experiment data, their source code or other materials that are necessary to replicate their experiments?</li> <li>What's the data format inside the link?</li> <li>What's the content of the link?</li> </ul> <p> </p> <p>This is a course project and I collect the data in a rush.</p> <p>If you want to use this dataset and find any error, please contact me ;-)</p> <p>My email: echo.xiangchen@gmail.com</p>
WSSSPE5.1 presentations: Research software sustainability activity analysis
<p>Distribution of actors, actions and actees from <a href="https://www.slideshare.net/danielskatz/research-software-sustainability-wssspe-urssi">Daniel S. Katz' schematic of research software sustainability</a> over presentations given at the Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE5.1) on 6 September 2017 in Manchester, UK (Proceedings: <a href="https://doi.org/10.6084/m9.figshare.c.3869782.v3">https://doi.org/10.6084/m9.figshare.c.3869782.v3</a>).</p>
Long-term moss monitoring network for atmospheric deposition in Germany, link to research data and scientific software
<p>Research data and scientific software related to a study that aims to restructure a long-term monitoring network using moss as biomonitor for atmospheric deposition in Germany. Data from the European Moss Survey 2005 and a statistically based methodology including a decision support system were used to design the spatial network for the 2005 survey.</p>
Estimating heavy metal deposition in Germany using model calculations and biomonitoring data, link to research data and scientific software
<p>Research data and scientific software related to an investigation dealing with modelled data on Cd and Pb deposition (LOTOS-EUROS, EMEP/MSC-East) and monitoring data from the International Cooperative Programme on Effects of Air Pollution on Natural Vegetation and Crops (ICP Vegetation Moss Survey) and the German Environmental Specimen Bank (ESB) providing corresponding parameters on HM concentration in various biota. The study aimed at examining, whether an integrated use of model calculations and monitoring data can extend established methods for estimating and evaluating spatial patterns of atmospheric Pb and Cd deposition across Germany.</p>
Fuzzy modelling and mapping soil moisture in Germany, link to research data and scientific software
<p>Research data and scientific software related to spatio-temporal estimations of ecological soil moisture with available data covering the whole territory of Germany and the Kellerwald National Park (Hesse). Temporal trends of modelled soil moisture for the time period 1961–2070 were statistically analyzed. Soil moisture changes (drying-out) at both national and regional levels were mapped.</p>
research-software/resosuma-data: 0.4.1
<p><strong><em>resosuma-data</em></strong> represents activities in the research software sustainability space in the CSV format, where column 1 contains actors in the space, column 2 contains activities, and column 3 contains actees.</p> <p>resosuma-0.4.1.csv fixes issues <a href="https://github.com/research-software/resosuma-data/issues/3">#3</a> and <a href="https://github.com/research-software/resosuma-data/issues/4">#4</a>.</p>
Diversity Awareness in Software Engineering Participant Research
<p>This dataset contains the result of a classification of three ICSE venues namely, ICSE 2019, 2020, and 2021 technical tracks, as stated in the methodology of the paper “Diversity awareness in software engineering participant studies” by Dutta et al. (2023).</p>
A census of research software in 171 academic institutional repositories.
<p> A dataset of metadata for 171 UK academic institutional repositories, including a census of research software contained.</p> <table> <tbody> <tr> <td><strong>URL</strong></td> <td>The OAI url</td> </tr> <tr> <td><strong>id</strong></td> <td>CORE Identifier</td> </tr> <tr> <td><strong>openDoarId</strong></td> <td>Open DOAR identifier</td> </tr> <tr> <td><strong>name</strong></td> <td>Name of repository</td> </tr> <tr> <td><strong>Russell_member</strong></td> <td>If the university is a member of the Russell Group of research intensive universities</td> </tr> <tr> <td><strong>RSE_group</strong></td> <td>If an RSE group is present (based on Soc of RSE data)</td> </tr> <tr> <td><strong>email</strong></td> <td>Redacted</td> </tr> <tr> <td><strong>uri</strong></td> <td>Not used</td> </tr> <tr> <td><strong>uni_sld</strong></td> <td>Second level domain (the part of the url between . And .ac.uk</td> </tr> <tr> <td><strong>homepageUrl</strong></td> <td>University website</td> </tr> <tr> <td><strong>source</strong></td> <td>Not used</td> </tr> <tr> <td><strong>ris_software</strong></td> <td>the Research Information System software used</td> </tr> <tr> <td><strong>ris_software_enum</strong></td> <td>Resolve ris_software into similar types (e.g. Eprints 3, EPrints3.3.16 both equal eprints)</td> </tr> <tr> <td><strong>metadataFormat</strong></td> <td>the protocol used for metadata</td> </tr> <tr> <td><strong>createdDate</strong></td> <td>Repository creation date</td> </tr> <tr> <td><strong>location</strong></td> <td>location of university</td> </tr> <tr> <td><strong>logo</strong></td> <td>University logo (resolves in error)</td> </tr> <tr> <td><strong>type</strong></td> <td>Only = Repository for this dataset. Can be = journal etc.</td> </tr> <tr> <td><strong>stats</strong></td> <td>Not used</td> </tr> <tr> <td><strong>contains_software_set</strong></td> <td>Whether the OAI-PMH software set is present in the repository.</td> </tr> <tr> <td><strong>Num_sw_records</strong></td> <td>The response of the OAI-PMH query for software (erroneous as discussed in paper)</td> </tr> <tr> <td><strong>Error</strong></td> <td>The category of error returned by the experiment’s OAI-PMH queries (see paper)</td> </tr> <tr> <td><strong>Manual_Num_sw_records</strong></td> <td>The true amount of software contained in the repository as found by a manual exhaustive search of each university website</td> </tr> <tr> <td><strong>Category</strong></td> <td>Whether the repository (a) contains software; (b) can contain software, but doesn’t yet; (c) has no separate type of research output called software or similar</td> </tr> </tbody> </table>
A dataset of metadata for UK academic institutional repositories, including a census of research software contained.
<p>A dataset of metadata for UK academic institutional repositories, including a census of research software contained.</p> <table> <tbody> <tr> <td><strong>URL</strong></td> <td>The OAI url</td> </tr> <tr> <td><strong>id</strong></td> <td>CORE Identifier</td> </tr> <tr> <td><strong>openDoarId</strong></td> <td>Open DOAR identifier</td> </tr> <tr> <td><strong>name</strong></td> <td>Name of repository</td> </tr> <tr> <td><strong>Russell_member</strong></td> <td>If the university is a member of the Russell Group of research intensive universities</td> </tr> <tr> <td><strong>RSE_group</strong></td> <td>If an RSE group is present (based on Soc of RSE data)</td> </tr> <tr> <td><strong>email</strong></td> <td>Redacted</td> </tr> <tr> <td><strong>uri</strong></td> <td>Not used</td> </tr> <tr> <td><strong>uni_sld</strong></td> <td>Second level domain (the part of the url between . And .ac.uk</td> </tr> <tr> <td><strong>homepageUrl</strong></td> <td>University website</td> </tr> <tr> <td><strong>source</strong></td> <td>Not used</td> </tr> <tr> <td><strong>ris_software</strong></td> <td>the Research Information System software used</td> </tr> <tr> <td><strong>ris_software_enum</strong></td> <td>Resolve ris_software into similar types (e.g. Eprints 3, EPrints3.3.16 both equal eprints)</td> </tr> <tr> <td><strong>metadataFormat</strong></td> <td>the protocol used for metadata</td> </tr> <tr> <td><strong>createdDate</strong></td> <td>Repository creation date</td> </tr> <tr> <td><strong>location</strong></td> <td>location of university</td> </tr> <tr> <td><strong>logo</strong></td> <td>University logo (resolves in error)</td> </tr> <tr> <td><strong>type</strong></td> <td>Only = Repository for this dataset. Can be = journal etc.</td> </tr> <tr> <td><strong>stats</strong></td> <td>Not used</td> </tr> <tr> <td><strong>contains_software_set</strong></td> <td>Whether the OAI-PMH software set is present in the repository.</td> </tr> <tr> <td><strong>Num_sw_records</strong></td> <td>The response of the OAI-PMH query for software (erroneous as discussed in paper)</td> </tr> <tr> <td><strong>Error</strong></td> <td>The category of error returned by the experiment’s OAI-PMH queries (see paper)</td> </tr> <tr> <td><strong>Manual_Num_sw_records</strong></td> <td>The true amount of software contained in the repository as found by a manual exhaustive search of each university website</td> </tr> <tr> <td><strong>Category</strong></td> <td>Whether the repository (a) contains software; (b) can contain software, but doesn’t yet; (c) has no separate type of research output called software or similar</td> </tr> </tbody> </table> <p> </p>
Rapid Review Dataset for Seeking Enlightenment: Incorporating Evidence-Based Practice Techniques in a Research Software Engineering Team
<p>A collection of evidence briefings produced through a rapid literature review protocol the Department of Software Engineering and Research at Sandia National Laboratories. These briefings are described in our research paper, "Seeking Enlightenment: Incorporating Evidence-Based Practice Techniques in a Research Software Engineering Team", which was accepted for publication at the 1st Annual Conference of the United States Research Software Engineer Association (US-RSE'23).</p> <p>Sandia National Laboratories is a multimission laboratory managed and operated by National Technology & Engineering Solutions of Sandia, LLC, a wholly owned subsidiary of Honeywell International Inc., for the U.S. Department of Energy's National Nuclear Security Administration under contract DE-NA0003525. SAND2023-06549O.</p>
MongoDB database dump for the analysis of the current sustainability state of research software
<p>This data set is the MongoDB dump (bson files) of the data created and analyzed with the rsps framework. In the first step, a research subject is assigned to the research software repositories. Afterwards, the current sustainability state is evaluated. The data set comprises the following six bson files:</p> <p><strong>repositories: </strong>metadata, received from the GitHub REST API, for repositories containing the search terms "doi+10" or "doi+10+in:readme", additional information are the request date, the contained search term, and the repository hosting service, in this case for all repositories "github". For repositories the Readme files are available.</p> <p><strong>publications:</strong> metadata of publications, published on arXiv and ACM, that contain the search term "github.com".</p> <p><strong>rs_repositories:</strong> research software candidates containing a DOI or that are referenced by the publications contained in the publications data set.</p> <p><strong>rs_artifacts: </strong>research software artifacts that are referenced in the harvested GitHub repositories by a DOI and the harvested publications.</p> <p><strong>publication_subjects:</strong> All Science Journal Classification (ASJC) of Scopus combined with the Scopus source list and Scopus book title list (https://www.scopus.com/home.uri)</p> <p><strong>arxiv_subjects:</strong> arXiv taxonomy complemented with the ASJC research subject.</p> <p> </p>
Softcite Dataset: A dataset of software mentions in research publications
<p>The Softcite dataset is a gold-standard dataset of software mentions in research publications, a free resource primarily for software entity recognition in scholarly text. This is the first release of this dataset.</p> <p><strong>What's in the dataset</strong></p> <p>With the aim of facilitating software entity recognition efforts at scale and eventually increased visibility of research software for the due credit of software contributions to scholarly research, a team of trained annotators from Howison Lab at the University of Texas at Austin annotated 4,093 software mentions in 4,971 open access research publications in biomedicine (from PubMed Central Open Access collection) and economics (from Unpaywall open access services). The annotated software mentions, along with their <em>publisher</em>, <em>version</em>, and access <em>URL</em>, if mentioned in the text, as well as those publications annotated as containing no software mentions, are all included in the released dataset as a TEI/XML corpus file.</p> <p>For understanding the schema of the Softcite corpus, its design considerations, and provenance, please refer to our paper included in this release (preprint version).</p> <p><strong>Use scenarios</strong></p> <p>The release of the Softcite dataset is intended to encourage researchers and stakeholders to make research software more visible in science, especially to academic databases and systems of information retrieval; and facilitate interoperability and collaboration among similar and relevant efforts in software entity recognition and building utilities for software information retrieval. This dataset can also be useful for researchers investigating software use in academic research.</p> <p><strong>Current release content</strong></p> <p><em>softcite-dataset v1.0</em><strong> </strong>release includes<strong>:</strong></p> <ul> <li>The Softcite dataset corpus file: softcite_corpus-full.tei.xml</li> <li><em>Softcite Dataset: A Dataset of Software Mentions in Biomedical and Economic Research Publications</em>, our paper that describes the design consideration and creation process of the dataset: Softcite_Dataset_Description_RC.pdf. (This is a preprint version of our forthcoming publication in the Journal of the Association for Information Science and Technology.)</li> </ul> <p>The Softcite dataset is licensed under a <a href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.</p> <p>If you have questions, please start a discussion or issue in the <a href="https://github.com/howisonlab/softcite-dataset">howisonlab/softcite-dataset Github repository</a>.</p>
UK Research Software Survey 2014
<p>This spreadsheet contains the anonymised data collected as part of a survey of UK researchers in their use of research software.</p> <p>We asked people specifically about “research software” which we defined as:</p> <blockquote> <p>“Software that is used to generate, process or analyse results that you intend to appear in a publication (either in a journal, conference paper, monograph, book or thesis). Research software can be anything from a few lines of code written by yourself, to a professionally developed software package. Software that does not generate, process or analyse results - such as word processing software, or the use of a web search - does not count as ‘research software’ for the purposes of this survey.”</p> </blockquote> <p>We contacted 1,000 randomly selected researchers at each of 15 Russell Group universities. From the 15,000 invitations to complete the survey, we received 417 responses – a rate of 3% which is fairly normal for a blind survey. We used Google Forms to collect responses.</p> <p>The responses have good representation from across the disciplines, seniorities and genders. This is a statistically significant number of responses that can be used to represent the views of people in research-intensive universities in the UK.</p> <p>An overview of the data is available on the worksheet "Summary data". Responses to questions are ordered by unique respondent ID. Please read the "README" worksheet for additional information about the collection and processing of this data.</p> <p>This survey data is licensed under a Creative Commons by Attribution licence. Copyright resides with The University of Edinburgh on behalf of the Software Sustainability Institute.</p> <p>Please cite as:</p> <p><strong>APA</strong></p> <p>Hettrick. S. J., et al. (2014). UK Research Software Survey 2014 [Data set]. doi:10.5281/zenodo.14809</p> <p><strong>Chicago</strong></p> <p>S.J. Hettrick et al, UK Research Software Survey 2014 (accessed December 4, 2014), 10.5281/zenodo.14809.</p> <p><strong>MLA</strong></p> <p>Hettrick S.J., et al. “UK Research Software Survey 2014” ZENODO, 2014. Web. 4 December 2014. .</p>
Research Software Engineers Supporting Science: Survey Responses
<p>Raw survey data for "Not everyone can use git: Research Software Engineers’ recommendations for scientist-centred software support (and what researchers think of them)", a talk given by Caroline Jay at RSE16, Manchester, UK.</p>
Package and Dependency Metadata for CZI Hackathon: Mapping the Impact of Research Software in Science
<p>A collection of useful datasets extracted from <a href="https://packages.ecosyste.ms">https://packages.ecosyste.ms</a> and <a href="https://repos.ecosyste.ms/">https://repos.ecosyste.ms</a> for use at the CZI Hackathon: Mapping the Impact of Research Software in Science.</p><p>All data is provided as NDJSON (new line delimited JSON), each line represents a valid JSON object, and they are separated by newline characters. There are <a href="https://pypi.org/project/ndjson/">python</a> and <a href="https://www.rdocumentation.org/packages/ndjson/versions/0.9.0/topics/stream_in">R</a> libraries for reading these files, or you can maually read each line and parse each line as a single JSON object.</p><p>Each ndjson file has been compressed with gzip (actual command: `tar -czvf`) to reduce download size, they expand to significantly bigger files after extraction.</p><h4>Package Data</h4><p>Package names from cran, bioconductor and pypi that have been parsed by the <a href="https://github.com/chanzuckerberg/software-mentions">software-mentions</a> project (data: <a href="https://datadryad.org/stash/dataset/doi:10.5061/dryad.6wwpzgn2c">https://datadryad.org/stash/dataset/doi:10.5061/dryad.6wwpzgn2c</a>) are collected together with their latest release at time of publishing along with the names of their dependencies, those dependency names have then also been recursively fetched with latest release and dependencies until the full list of transitive dependencies is included. </p><p>Note: This approach uses a simplified method of dependency resolution, always picking the latest version of each package rather than taking into account each dependencies specific version range requirements, this is primarily due to time constraints and allows all software ecosystems to be processed in the same way. A future improvement would be to use each package ecosystem's specific dependency resolution algorithm to compute the full transitive dependency tree for each mentioned software package.</p><h4>GitHub Data</h4><p>Two different approaches were taken for collecting data for referenced GitHub mentions:</p><p>1. `github.ndjson` is metadata for each repository from GitHub, including "manifest" files which are known files that contain dependency information for a project such as requirements.txt, DESCRIPTION and package.json, parsed using <a href="https://github.com/ecosyste-ms/bibliothecary">https://github.com/ecosyste-ms/bibliothecary</a>, which may include transitive dependencies that have been discovered in a `lockfile` within the repository.</p><p>2. `github_packages.ndjson` is metadata for each package that was found on any package manager that references the GitHub url as it's repository url/source/homepage, these packages, like the cran and pypi data above, include the latest release and their direct dependencies. There may be more than one package for each GitHub URL as it is a one to many relationship. `github_packages_with_transitive.ndjson` follows the same format but also includes the extra resolved transitive dependencies of all packages using the same approach as with cran and pypi data above with the same caveats. </p><p>There are also many more ecosystems referenced in these files than just cran, bioconductor and pypi, https://packages.ecosyste.ms provides a standardized metadata format for all of them to enable comparison and simplification of automation.</p><h4>Contact</h4><p>If you would like any help, support or more data from Ecosyste.ms please do get in touch via email: hello@ecosyste.ms or open an issue on GitHub: https://github.com/ecosyste-ms/packages/issues</p>
Awareness of FAIR and FAIR4RS among international research software funders (Dataset)
<p><span>This research employed a mixed methods online survey to investigate research software funders’ perspectives. </span></p> <p><span>All participants gave informed consent at the start of the online survey. The University of Illinois Urbana-Champaign Institutional Review Board (no. 24374) reviewed the study and determined it exempt.</span></p> <p><span>Data collection took place from December 2023 to May 2024. The mean completion time for the detailed survey was 28 minutes and 13 seconds. The data were cleaned and prepared for analysis by removing any identifiable respondent details. </span></p> <h2><span>Survey design</span></h2> <p><span>The survey began by collecting profile information, including institutional affiliation and job title. The survey primarily gathered detailed information about initiatives, policies, or programs to support research software but also included a much smaller set of questions about additional topics, such as strategic funding priorities and awareness of key concepts. The data generated from this survey are too extensive to report in a single manuscript. Here, we focus on the results generated via the set of questions asking about FAIR and FAIR4RS, specifically, the following survey items: </span></p> <table> <tbody> <tr> <td> <p><strong><span>Variable</span></strong></p> </td> <td> <p><strong><span>Survey item</span></strong></p> </td> <td> <p><strong><span>Response options</span></strong></p> </td> </tr> <tr> <td> <p><span>Awareness of FAIR principles</span></p> </td> <td> <p><span>“Have you ever heard of the FAIR (findable, accessible, interoperable, and reusable) principles for data?”</span></p> </td> <td> <p><span>Yes, No, Unsure</span></p> <p><span>(If ‘Yes’, then the next question was asked)</span></p> </td> </tr> <tr> <td> <p><span>“How familiar are you with the FAIR principles for data?”</span></p> </td> <td> <p><span>Not at all Familiar, Slightly Familiar, Somewhat Familiar, Moderately Familiar, Extremely Familiar</span></p> </td> </tr> <tr> <td> <p><span>Awareness of FAIR4RS principles</span></p> </td> <td> <p><span>“Have you ever heard of the FAIR4RS principles for research software?”</span></p> </td> <td> <p><span>Yes, No, Unsure</span></p> <p><span>(If ‘Yes’, then the next question was asked)</span></p> </td> </tr> <tr> <td> <p><span>“How familiar are you with the FAIR4RS principles for research software?”</span></p> </td> <td> <p><span>Not at all Familiar, Slightly Familiar, Somewhat Familiar, Moderately Familiar, Extremely Familiar</span></p> </td> </tr> </tbody> </table> <p><span> </span></p> <p><span>In addition, an open-ended question asked for further detail about the respondents’ assessments of FAIR4RS’s relevance to their work.</span></p> <h2><span>Sampling</span></h2> <p><span>The survey targeted international research funders, including governmental and non-governmental (e.g., philanthropic) organizations. An initial contact list was created based on participation in the Research Software Association (ReSA) and known responsibilities for research software funding among the authors' networks. This list was refined by removing individuals who had moved to unrelated professional roles or were unavailable long-term due to personal issues.</span></p> <p><span>The final contact list comprised 71 people at 37 funding organizations. After excluding individuals when a member of their organization had already provided a complete response or when the person was no longer working on a relevant topic or was otherwise unavailable (total of n=30), 41 people remained. Of these, five did not complete the survey, while 36 individuals (representing 30 research funding organizations) did, yielding a response rate of 87.8% (and representing 81% of the original organizations). Fully completed survey responses were not required for inclusion in the sample, resulting in varied sample sizes across different survey questions.</span></p> <p><span>The respondents represented governmental (n=26), philanthropic (n=6), and corporate (n=1) research funders.</span></p> <p><span>Respondents’ job titles spanned the following categories: Senior Leadership and Executive (e.g., Vice President of Strategy); Program and Project Management (e.g., Senior Program Manager); Planning and Business Development; and Scientific, Technical, and IT roles (e.g., Scientific Information Lead).</span></p> <p><span>Most respondents, 72.7% (n=24), answered “Yes” to the question, “Has your organization established any policies, initiatives, or programs aimed at supporting research software?” Meanwhile, 18.2% (n=6) said “No,” and 9.1% (n=3) were “Unsure.”</span></p> <p><span>Regarding geographic distribution in the achieved sample, most survey respondents were from North America and Europe, with 15 and 12 participants, respectively. The sample also comprised 4 participants from South America, 3 from Oceania, and 1 from Asia, reflecting a global but uneven representation across continents. Some participating funders covered a broad spectrum of disciplines, while others focused on specific domains such as social sciences, health, environment, physical sciences, or humanities.</span></p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.