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.
4
datasets available to search
ShareScore release 0.9.0
Dataset results
4 results for “code technical debt”
Replication Package for the Paper: "Potential Technical Debt and Its Resolution in Code Reviews: An Exploratory Study of the OpenStack and Qt Communities"
<p>This is the replication package for the paper: "Potential Technical Debt and Its Resolution in Code Reviews: An Exploratory Study of the OpenStack and Qt Communities", including the dataset and its description (README.md):</p> <ul> <li><strong>PTD-related Comments in Code Review and Data Extraction Results.xlsx</strong> is the dataset of our paper, which contains 2,030 review comments collected from the Nova project and Neutron project of OpenStack community. Among all the review comments, 163 review comments indicate PTD. For the rows of review comments that are related to PTD, we filled them with blue color as an indicator.</li> <li> <p><strong>README.md</strong></p> </li> </ul>
The Temporality of Technical Debt Introduction on New Code and Confounding Factors
<p>Code Technical Debt (TD) is intentionally or unintentionally created when developers introduce inefficiencies in the codebase. This can be attributed to various reasons such as heavy workload, tight delivery schedule, or developers' lack of experience. Since a software system grows mostly through the addition of new code, it is interesting to study how TD fluctuates along this process. Specifically, in this paper we investigate: (a) the temporality of code TD introduction in new code, i.e., whether the introduction of TD is stable across the lifespan of the project, or if its evolution presents spikes; and (b) the relation of TD introduction to the development team’s workload in a given period, as well as to the experience of the development team. To answer these questions, we have performed a case study on 47 open source projects from two well-known ecosystems (Apache and Eclipse) as well as additional isolated projects from GitHub (not selected from a specific ecosystem) and inspected the number of TD issues introduced in 6-month sliding temporal windows. The results of the study suggested that: (a) overall, the number of TD issues introduced through new code is a stable measure, although it presents spikes; and (b) the number of commits performed, as well as developers' experience are not strongly correlated to the number of introduced TD issues.</p>
Dataset: An empirical study on self-admitted technical debt in modern code review
<pre>This data was used in the IST paper "An Empirical Study on Self-Admitted Technical Debt in Modern Code Review". The program to use this data is published in GitHub (https://github.com/Yutaro-Kashiwa/ReviewSATD_RP) When you use this data in your research, please cite the following papers: ``` @article{Kashiwa:IST:2022:SATD_Review, author = {Yutaro Kashiwa and Ryoma Nishikawa and Yasutaka Kamei and Masanari Kondo and Emad Shihab and Ryosuke Sato and Naoyasu Ubayashi}, title = {An empirical study on self-admitted technical debt in modern code review}, journal = {Information and Software Technology}, volume = {146}, pages = {106855}, year = {2022}, url = {https://doi.org/10.1016/j.infsof.2022.106855}, doi = {10.1016/j.infsof.2022.106855} } ``` </pre>
Beyond the Code: Mining Self-Admitted Technical Debt in Issue Tracker Systems
<p>Self-admitted technical debt (SATD) is a particular case of Technical Debt (TD) where developers explicitly acknowledge their sub-optimal implementation decisions. Previous studies mine SATD by searching for specific TD-related terms in source code comments.By contrast, in this paper we argue that developers can admit technical debt by other means, e.g., by creating issues in tracking systems and labelling them as referring to TD. We refer to this type of SATD as issue-based SATD or just SATD-I. We study a sample of 286 SATD-I instances collected from five open source projects, including Microsoft Visual Studio and GitLab Community Edition. We show that only 29% of the studied SATD-I instances can be tracked to source code comments. We also show that SATD-I issues take more time to be closed, compared to other issues, although they are not more complex in terms of code churn. Besides, in 45% of the studied issues TD was introduced to ship earlier, and in almost 60%it refers to Design flaws. Finally, we report that most developers pay SATD-I to reduce its costs or interests (66%). Our findings suggest that there is space for designing novel tools to support technical debt management, particularly tools that encourage developers to create and label issues containing TD concerns.</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.