Research Workflows and Open Science - Data Set

Data set accompanying the report "Research Workflows and Open Science", a systematic study of open science research workflows. The data set summarises the open science characteristics exhibited by the analysed workflows. The first two columns ‘workflow ID’ and ‘URL’ are dedicated to the ID we used to identify each workflow and to the publications related to the workflows respectively. The remaining columns are dedicated to the characteristics exhibited by the analysed workflows and are named The remaining columns are dedicated to the characteristics exhibited by the analysed workflows and are named following the different categories identified: 'used/open science infrastructure/virtual' If a workflow relies on a virtual open infrastructure (yes/no) 'used/open science infrastructure/physical' If a workflow relies on a physical open infrastructure (yes/no) 'used/open scientific knowledge/open source software' If a workflow relies on open source software (yes/no) 'used/open scientific knowledge/open hardware' If a workflow relies on open hardware (yes/no) 'used/open scientific knowledge/open research data' If a workflow (re)uses open research data (yes/no) 'used/open scientific knowledge/open educational resources' If a workflow (re)uses open educational resources (yes/no) 'produced/open scientific knowledge/(open access) scientific publication' If a workflow envisages the release of a scientific publication (e.g. papers, reports, data management plans, preprints, study designs) under an open access licence (yes/no) 'produced/open scientific knowledge/open source software' If a workflow envisages the release of software (e.g. code, analysis scripts) under an open access licence (yes/no) 'produced/open scientific knowledge/open research data' If a workflow envisages the release of open research data (yes/no) 'produced/open scientific knowledge/open educational resources' If a workflow envisages the release of open educational resources (yes/no) 'transparency/transparency type' degree of transparency of a workflow, defined in terms of which research products are openly shared and when in order to document the research processes (‘built-in’ if transparent, ‘enabled’ if capable of being transparent, ‘opaque’ otherwise) 'transparency/sharing type' workflow categories based on when the research products are shared (‘end’ for sharing at the end of the workflow, mixed for sharing part of the research products during the workflow and the rest at the end of it, ‘iterative’ for sharing iteratively during or at the end of the related workflow phase, and ‘user-dependent’, where it is ultimately up to the researcher to decide when to share the research products since the workflow offers different paths to follow while imposing no sharing constraint.) 'collaboration/collaboration implementation' If a workflow implements collaborative practices (yes/no) 'collaboration/open engagement of societal actors/crowdfunding' If a workflow envisages crowdfunding (yes/no) 'collaboration/open engagement of societal actors/crowdsourcing' If a workflow envisages crowdsourcing (yes/no) 'collaboration/open engagement of societal actors/scientific volunteering' If a workflow envisages scientific volunteering (yes/no) 'collaboration/open engagement of societal actors/citizen and participatory science' If a workflow envisages citizen and participatory science (yes/no) 'collaboration/open dialogue with other knowledge systems/indigenous peoples' If a workflow envisages the establishment of a dialogue with indigenous peoples (yes/no) 'collaboration/open dialogue with other knowledge systems/marginalised scholars' If a workflow envisages the establishment of a dialogue with marginalised scholars (yes/no) 'collaboration/open dialogue with other knowledge systems/local communities' If a workflow envisages the establishment of a dialogue with local communities (yes/no) 'assessment' If a workflow implements assessment processes for the evaluation of the research products created (yes/no) 'automation' If a workflow includes automated processes (yes/no)