cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.5281/zenodo.5656116
title: Nufix: Escape From NuGet Dependency Maze

description: With the rapid evolution of the .NET ecosystem, managing dependencies in .NET projects becomes a critical challenge. Due to the fragmentation of .NET ecosystem, developers often suffer from dependency maze (DM) issues, i.e., package dependency constraints are violated (e.g, constraints on package versions and target platforms) when updating a project’s platform or dependency versions. DM issues are serious, since they can block the package installations, causing build errors. Fixing a DM issue can be challenging. Multiple DM issues often occur in a project at the same time. For those projects with large dependency graphs, fixing such issues is a time-consuming and error-prone process that exercises a series of changes in dependency constraints in response to newly induced DM issues. More importantly, when deciding a fixing solution, developers often consider their desired properties of configuration (e.g., installing fewer packages, inducing fewer risky build warnings). However, it is difficult for developers to imagine all possible dependency graphs affected by dependency changes, to figure out an optimal solution that satisfies their preferences. To help .NET developers tackle DM issues, we developed a tool, <strong>NuFix</strong> (VS plugin)(Homepage: http://www.nufix-dependency-maze.com/), to automatically generate fixes. It is built on top of our comprehensive study of developers’ preferences in fixing DM issues. By encoding the empirical findings into a linear optimization model, NuFix seeks for the global optimal fixing solution. One interesting feature of NuFix is that, it allows developers to customize and iteratively refine the search scope of package versions based on their requirements. A video demo is available at: https://youtu.be/8NECIM0wjhw Our evaluation shows that NuFix can generate fixes for a given .NET project within 12 seconds and achieves a 100% fixing ratio for 262 real DM issues. We invited ten experienced .NET experts working in MSRA to evaluate the quality our generated fixes. Their feedback indicates that the generated fixes meet the developers' desired properties for the build management. Encouragingly, 20 projects (including affected projects such as Dropbox) have approved and merged our generated fixes, and shown great interests in our technique (the merged PRs are available on NuFix's website).
DOI: 10.5281/zenodo.6346554
title: Nufix: Escape From NuGet Dependency Maze

description: Developers usually suffer from dependency maze (DM) issues, i.e., package dependency constraints are violated when a project’s platform or dependencies are changed. This problem is especially serious in .NET ecosystem due to its fragmented platforms (e.g., .NET Framework, .NET Core, and .NET Standard). Fixing DM issues is challenging due to the complexity of dependency constraints: multiple DM issues often occur in one project; solving one DM issue usually causes another DM issue cropping up; the exponential search space of possible dependency combinations is also a barrier. On the other hand, as observed in our empirical study, fixing DM issues for a .NET project is, however, a challenging task, which multiple DM issues often occur in a project at the same time. For those projects with large dependency graphs, fixing such issues is a time-consuming and error prone process that exercises a series of changes in dependency constraints in response to newly induced DM issues and it is difficult for developers to imagine all possible dependency graphs affected by dependency changes, to figure out an optimal solution that satisfies their preferences. To help .NET developers combat DM issues, we propose <strong>NuFix</strong>, an automated technique to repair DM issues. NuFix is implemented as a Visual Studio plugin, whose main features include: 1) building on top of a comprehensive study of developers’ preferences in fixing DC issues (e.g., installing fewer packages, inducing fewer risky build warnings); 2) seeking for the global optimal fixing solution based on a linear optimization model; 3) allowing developers to customize and iteratively refine the search scope of package versions based on their requirements; 4) visualizing dependency graph after adopting the derived fixes. Our evaluation shows that <strong>NuFix</strong> can generate fixes for a given .NET project within 12 seconds and achieves a 100% fixing ratio for 262 real DC issues. We invited ten experienced .NET experts working in a leading IT enterprise to evaluate the quality our generated fixes. Their feedback indicates that the generated fixes meet the developers’ desired properties for the build management. Encouragingly, 20 projects (including affected projects such as Dropbox) have approved and merged our generated fixes, and shown great interests in our technique.
DOI: 10.5281/zenodo.5912116
title: Nufix: Escape From NuGet Dependency Maze

description: Developers usually suffer from dependency maze (DM) issues, i.e., package dependency constraints are violated when a project’s platform or dependencies are changed. This problem is especially serious in .NET ecosystem due to its fragmented platforms (e.g., .NET Framework, .NET Core, and .NET Standard). Fixing DM issues is challenging due to the complexity of dependency constraints: multiple DM issues often occur in one project; solving one DM issue usually causes another DM issue cropping up; the exponential search space of possible dependency combinations is also a barrier. On the other hand, as observed in our empirical study, fixing DM issues for a .NET project is, however, a challenging task, which multiple DM issues often occur in a project at the same time. For those projects with large dependency graphs, fixing such issues is a time-consuming and error prone process that exercises a series of changes in dependency constraints in response to newly induced DM issues and it is difficult for developers to imagine all possible dependency graphs affected by dependency changes, to figure out an optimal solution that satisfies their preferences. To help .NET developers combat DM issues, we propose <strong>NuFix</strong>, an automated technique to repair DM issues. NuFix is implemented as a Visual Studio plugin, whose main features include: 1) building on top of a comprehensive study of developers’ preferences in fixing DC issues (e.g., installing fewer packages, inducing fewer risky build warnings); 2) seeking for the global optimal fixing solution based on a linear optimization model; 3) allowing developers to customize and iteratively refine the search scope of package versions based on their requirements; 4) visualizing dependency graph after adopting the derived fixes. Our evaluation shows that <strong>NuFix</strong> can generate fixes for a given .NET project within 12 seconds and achieves a 100% fixing ratio for 262 real DC issues. We invited ten experienced .NET experts working in a leading IT enterprise to evaluate the quality our generated fixes. Their feedback indicates that the generated fixes meet the developers’ desired properties for the build management. Encouragingly, 20 projects (including affected projects such as Dropbox) have approved and merged our generated fixes, and shown great interests in our technique.
DOI: 10.5281/zenodo.6140705
title: Nufix: Escape From NuGet Dependency Maze

description: Developers usually suffer from dependency maze (DM) issues, i.e., package dependency constraints are violated when a project’s platform or dependencies are changed. This problem is especially serious in .NET ecosystem due to its fragmented platforms (e.g., .NET Framework, .NET Core, and .NET Standard). Fixing DM issues is challenging due to the complexity of dependency constraints: multiple DM issues often occur in one project; solving one DM issue usually causes another DM issue cropping up; the exponential search space of possible dependency combinations is also a barrier. On the other hand, as observed in our empirical study, fixing DM issues for a .NET project is, however, a challenging task, which multiple DM issues often occur in a project at the same time. For those projects with large dependency graphs, fixing such issues is a time-consuming and error prone process that exercises a series of changes in dependency constraints in response to newly induced DM issues and it is difficult for developers to imagine all possible dependency graphs affected by dependency changes, to figure out an optimal solution that satisfies their preferences. To help .NET developers combat DM issues, we propose <strong>NuFix</strong>, an automated technique to repair DM issues. NuFix is implemented as a Visual Studio plugin, whose main features include: 1) building on top of a comprehensive study of developers’ preferences in fixing DC issues (e.g., installing fewer packages, inducing fewer risky build warnings); 2) seeking for the global optimal fixing solution based on a linear optimization model; 3) allowing developers to customize and iteratively refine the search scope of package versions based on their requirements; 4) visualizing dependency graph after adopting the derived fixes. Our evaluation shows that <strong>NuFix</strong> can generate fixes for a given .NET project within 12 seconds and achieves a 100% fixing ratio for 262 real DC issues. We invited ten experienced .NET experts working in a leading IT enterprise to evaluate the quality our generated fixes. Their feedback indicates that the generated fixes meet the developers’ desired properties for the build management. Encouragingly, 20 projects (including affected projects such as Dropbox) have approved and merged our generated fixes, and shown great interests in our technique.
DOI: 10.5281/zenodo.6477458
title: Development and implementation of a tool for measuring the training effectiveness of the patient-centered consultation model

description: <strong>Background:</strong> The patient-centered consultation model comprises four elements: exploring health, illness, and disease experiences, understanding the whole person, finding common ground, and enhancing the patient-doctor relationship. This method is taught at the course in general practice at Copenhagen University. The aim of the study was to develop a simple tool consisting of a questionnaire about the patient-centered elements and a test video consultation. The outcome is the change in the students’ ability to identify these elements. Used as a pre-course and post-course test it can inform the teachers which elements of the patient-centered consultation need intensifying in the teaching.<br> <strong>Methods:</strong> The students from a course in general practice volunteered to participate in all steps of the development. They took part in individual interviews to select items from an already existing questionnaire (DanSCORE). The preliminary questionnaire was tested for face and content validity, pilot-tested and tested for test-retest reliability. All video consultations were transcribed and assessed for patient-centered elements through a conversation analysis. The videos showed medical students seeing real patients.<br> <strong>Results:</strong> The preliminary version of the questionnaire (called DanOBS) [CM1] [MJ2] had 23 items. In the subsequent interviews, items were reduced to 17, each with three response options. After the pilot test, the questionnaire was further reduced to 13 items, all strictly relevant to the model and with two response options. The final questionnaire had acceptable test-retest reliability. The number of test consultation videos underwent a reduction from six videos to one.<br> <strong>Conclusions:</strong> The DanOBS combined with a test video consultation, used as a pre-and post-course test demonstrates for teachers which elements in the patient-centered consultation need to be intensified in the teaching.
DOI: 10.5281/zenodo.6298235
title: Development and implementation of a tool for measuring the training effectiveness of the patient-centered consultation model

description: <strong>Background:</strong> The patient-centered consultation model comprises four elements: exploring health, illness, and disease experiences, understanding the whole person, finding common ground, and enhancing the patient-doctor relationship. This method is taught at the course in general practice at Copenhagen University. The aim of the study was to develop a simple tool consisting of a questionnaire about the patient-centered elements and a test video consultation. The outcome is the change in the students’ ability to identify these elements. Used as a pre-course and post-course test it can inform the teachers which elements of the patient-centered consultation need intensifying in the teaching.<br> <strong>Methods:</strong> The students from a course in general practice volunteered to participate in all steps of the development. They took part in individual interviews to select items from an already existing questionnaire (DanSCORE). The preliminary questionnaire was tested for face and content validity, pilot-tested and tested for test-retest reliability. All video consultations were transcribed and assessed for patient-centered elements through a conversation analysis. The videos showed medical students seeing real patients.<br> <strong>Results:</strong> The preliminary version of the questionnaire (called DanOBS) [CM1] [MJ2] had 23 items. In the subsequent interviews, items were reduced to 17, each with three response options. After the pilot test, the questionnaire was further reduced to 13 items, all strictly relevant to the model and with two response options. The final questionnaire had acceptable test-retest reliability. The number of test consultation videos underwent a reduction from six videos to one.<br> <strong>Conclusions:</strong> The DanOBS combined with a test video consultation, used as a pre-and post-course test demonstrates for teachers which elements in the patient-centered consultation need to be intensified in the teaching.
DOI: 10.5281/zenodo.5912249
title: Nufix: Escape From NuGet Dependency Maze

description: Developers usually suffer from dependency maze (DM) issues, i.e., package dependency constraints are violated when a project’s platform or dependencies are changed. This problem is especially serious in .NET ecosystem due to its fragmented platforms (e.g., .NET Framework, .NET Core, and .NET Standard). Fixing DM issues is challenging due to the complexity of dependency constraints: multiple DM issues often occur in one project; solving one DM issue usually causes another DM issue cropping up; the exponential search space of possible dependency combinations is also a barrier. On the other hand, as observed in our empirical study, fixing DM issues for a .NET project is, however, a challenging task, which multiple DM issues often occur in a project at the same time. For those projects with large dependency graphs, fixing such issues is a time-consuming and error prone process that exercises a series of changes in dependency constraints in response to newly induced DM issues and it is difficult for developers to imagine all possible dependency graphs affected by dependency changes, to figure out an optimal solution that satisfies their preferences. To help .NET developers combat DM issues, we propose <strong>NuFix</strong>, an automated technique to repair DM issues. NuFix is implemented as a Visual Studio plugin, whose main features include: 1) building on top of a comprehensive study of developers’ preferences in fixing DC issues (e.g., installing fewer packages, inducing fewer risky build warnings); 2) seeking for the global optimal fixing solution based on a linear optimization model; 3) allowing developers to customize and iteratively refine the search scope of package versions based on their requirements; 4) visualizing dependency graph after adopting the derived fixes. Our evaluation shows that <strong>NuFix</strong> can generate fixes for a given .NET project within 12 seconds and achieves a 100% fixing ratio for 262 real DC issues. We invited ten experienced .NET experts working in a leading IT enterprise to evaluate the quality our generated fixes. Their feedback indicates that the generated fixes meet the developers’ desired properties for the build management. Encouragingly, 20 projects (including affected projects such as Dropbox) have approved and merged our generated fixes, and shown great interests in our technique.
DOI: 10.5281/zenodo.6477460
title: OD measurement data of Scenedesmus sp. on February

description: This document contains data on the OD measurement method used to calculate the growth rate in February of Scenedesmus sp, a microalgae species cultivated for a specific purpose.
DOI: 10.5281/zenodo.5912117
title: Nufix: Escape From NuGet Dependency Maze

description: Developers usually suffer from dependency maze (DM) issues, i.e., package dependency constraints are violated when a project’s platform or dependencies are changed. This problem is especially serious in .NET ecosystem due to its fragmented platforms (e.g., .NET Framework, .NET Core, and .NET Standard). Fixing DM issues is challenging due to the complexity of dependency constraints: multiple DM issues often occur in one project; solving one DM issue usually causes another DM issue cropping up; the exponential search space of possible dependency combinations is also a barrier. On the other hand, as observed in our empirical study, fixing DM issues for a .NET project is, however, a challenging task, which multiple DM issues often occur in a project at the same time. For those projects with large dependency graphs, fixing such issues is a time-consuming and error prone process that exercises a series of changes in dependency constraints in response to newly induced DM issues and it is difficult for developers to imagine all possible dependency graphs affected by dependency changes, to figure out an optimal solution that satisfies their preferences. To help .NET developers combat DM issues, we propose <strong>NuFix</strong>, an automated technique to repair DM issues. NuFix is implemented as a Visual Studio plugin, whose main features include: 1) building on top of a comprehensive study of developers’ preferences in fixing DC issues (e.g., installing fewer packages, inducing fewer risky build warnings); 2) seeking for the global optimal fixing solution based on a linear optimization model; 3) allowing developers to customize and iteratively refine the search scope of package versions based on their requirements; 4) visualizing dependency graph after adopting the derived fixes. Our evaluation shows that <strong>NuFix</strong> can generate fixes for a given .NET project within 12 seconds and achieves a 100% fixing ratio for 262 real DC issues. We invited ten experienced .NET experts working in a leading IT enterprise to evaluate the quality our generated fixes. Their feedback indicates that the generated fixes meet the developers’ desired properties for the build management. Encouragingly, 20 projects (including affected projects such as Dropbox) have approved and merged our generated fixes, and shown great interests in our technique.
DOI: 10.5281/zenodo.6477459
title: OD measurement data of Scenedesmus sp. on February

description: This document contains data on the OD measurement method used to calculate the growth rate in February of Scenedesmus sp, a microalgae species cultivated for a specific purpose.
DOI: 10.3886/icpsr22760.v1
title: Sacramento Area Latino Study on Aging (SALSA Study), 1996-2008
title: Version 1

description: The Sacramento Area Latino Study on Aging (SALSA Study) project tracked the incidence of physical and cognitive impairment as well as dementia and cardiovascular diseases in elderly Latinos in the Sacramento, California, region. The SALSA project aimed to assess cognitive, physical and social functions, which include the ability to follow instructions, to perform certain movements, and to interact with others. The study explored the effects that cultural, nutritional, social and cardiovascular risk factors have on overall health and dementia, and examined the association between diabetes and functional status. Demographic information includes age given at follow-up visits, country of birth, language, religion, marital status, educational level, occupation, household income, and size of household.
description: Datasets: DS0: Study-Level Files DS1: Baseline Public Use Data DS2: Baseline Restricted Use Data DS3: Follow-Up V1 Public Use Data DS4: Follow-Up V1 Restricted Use Data DS5: Follow-Up V2 Public Use Data DS6: Follow-Up V2 Restricted Use Data DS7: Follow-Up V3 Public Use Data DS8: Follow-Up V3 Restricted Use Data DS9: Follow-Up V4 Public Use Data DS10: Follow-Up V4 Restricted Use Data DS11: Follow-Up V5 Public Use Data DS12: Follow-Up V5 Restricted Use Data DS13: Follow-Up V6 Public Use Data DS14: Follow-Up V6 Restricted Use Data
description: Begun in 1996, the study includes 1,789 Latinos, 60 years and older, for up to five years, from the Sacramento, California, region. Most are from Sacramento County; the remainder are from Woodland, Dixon, Roseville, Yuba City, and from other small towns in the valley.
description: face-to-face interview; on-site questionnaireVariables in multiple datasets were left blanked and, for processing purposes, were replaced with the value "BLNK" or "BLN".Variable names longer than 12 characters were hyphenated during UNIX processing. (See "ph22760_all_namechange.txt" for the full listing of variables.)The SALSA project site link has been removed, as it is no longer accessible.
DOI: 10.3886/icpsr22880.v2
title: National Incident-Based Reporting System, 1995: Extract Files
title: Version 2

description: The National Incident-Based Reporting System (NIBRS) is a part of the Uniform Crime Reporting Program (UCR), administered by the Federal Bureau of Investigation (FBI). The extract files version of NIBRS was created to simplify working with NIBRS data. Data management issues with NIBRS are significant, especially when two or more segment levels are being merged. These issues require skills separate from data analysis. NIBRS data as formatted by the FBI are stored in a single file. These data are organized by various segment levels (record types). There are six main segment levels: administrative, offense, property, victim, offender, and arrestee. Each segment level has a different length and layout. There are other segment levels that occur with less frequency than the six main levels. Significant computing resources are necessary to work with the data in its single-file format. In addition, the user must be sophisticated in working with data in complex file types. For these reasons and the desire to facilitate the use of NIBRS data, ICPSR created the extract files. The data are not a representative sample of crime in the United States.
description: Datasets: DS0: Study-Level Files DS1: Incident-Level File DS2: Victim-Level File DS3: Offender-Level File DS4: Arrestee-Level File
description: Law enforcement agencies in the United States participating in the National Incident-Based Reporting System.
description: self-enumerated questionnaire