This guide walks through the five key tenets of ASAP's Open Science Policy and uses a color-coded system to demonstrate how our requirements appear in different components of a research publication.

This document contains answers to common questions related to ASAP’s Open Science Policies. The ASAP Open Science Policy can be found on our website.

This document is intended to provide a detailed overview of ASAP’s Open Science Policies and compliance requirements. The ASAP Open Science Policy can be found on our website and in the ASAP Open Science Policy Handbook.

This document provides guidance on how to create a key resource table. The ASAP Open Science Policy requires all datasets, protocols, code & software, and lab materials be unambiguously identified in a manuscript. ASAP requires that ASAP-funded researchers complete a Key Resource Table (KRT) for every manuscript.

This document provides guidance on how to create an Availability Statement. We use the term Availability Statement broadly to encompass any and all sections of a manuscript that appear under a header that is specifically related to the availability of data, code, protocols, and/or lab materials. These section headers could be: Data Availability, Data and Code Availability, Materials Availability, Resource Availability, Open Science Practices, or contain other relevant terms. The ASAP Open Science Policy requires that all manuscripts (including drafts, preprints, and publications) include a section that speaks to the availability of: 1. Data 2. Code/software 3. Protocols 4. Key lab materials

This document provides a template for creating a key resource table in line with ASAP's Open Science Policy requirements.

This document contains answers to common questions related to Key Resource Tables. The ASAP Open Science Policy requires all datasets, code & software, protocols, and key lab materials be unambiguously identified in a manuscript. ASAP recommends that ASAP-funded researchers complete a Key Resource Table (KRT) for every manuscript.

The purpose of this document is to provide guidance on how to write README files for code. The ASAP Open Science Policy requires that all code generated as part of an ASAP funded project be deposited in a publicly accessible repository, assigned a persistent identifier, and that the identifier be cited in all publications that use the code. Throughout this document, we use the term code broadly to encompass all scripts, software, packages, libraries, macros, pipelines, algorithms, executables, batch files, and any other code that manipulates data in any way, including but not limited to cleaning data, preprocessing data, analyzing data, and producing figures, tables, and results. Code can be written specifically to clean and analyze the data for a particular study or with flexibility so that other researchers can easily use the code (e.g., software). This guide focuses on the former. The ASAP Open Science Policy also requires that a README file be included in each repository where code is deposited. README files must include enough information that someone who was not part of the study team can access the code, identify which scripts execute which functions (e.g., clean data, produce figures), and understand the scripts well enough to reuse them.

The purpose of this document is to provide guidance on how to write README files to accompany datasets. The ASAP Open Science Policy requires all research outputs, including datasets, be deposited in a publicly accessible repository no later than the time of publication and cited in the publication with a permanent identifier. ASAP requires a README file to be included in the upload of all datasets. To assist ASAP grantees in sharing usable data and to ensure that they meet the ASAP data-sharing standards outlined in this document, the Open Science Team will review all ASAP-affiliated Zenodo dataset uploads for inclusion of a README file.

This document provides a step-by-step guide to registering preclinical research tools. The ASAP Open Science Policy requires researchers to (1) cite all newly-generated lab resources (antibodies, cell lines, plasmids/clones, transgenic models, and other reagents) and (2) to deposit those resources in a publicly accessible repository.

This document provides guidance on how to write recipe-style protocols. The ASAP Open Science Policy requires all research outputs, including protocols, be deposited in a publicly accessible repository no later than the time of publication and cited in the publication with a persistent identifier. ASAP recommends using protocols.io to deposit protocols.