> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/redivis-for-open-science/open-access.md). # Open access The ability to view, reproduce, and build upon other works is a core tenet of the scientific process. Redivis provides tools for data storage, access, analysis, documentation, and publication that can help researchers and institutions implement public access and open science practices. Not all research can be made fully public. Redivis supports a responsible approach to data sharing by allowing data owners to make datasets and their metadata as accessible as possible while applying appropriate protections to sensitive or restricted information. ## Background In August 2022, the United States Office of Science and Technology Policy (OSTP) released a [memorandum on public access](https://bidenwhitehouse.archives.gov/wp-content/uploads/2022/08/08-2022-OSTP-Public-Access-Memo.pdf) to federally funded research (known as “Nelson Memo”) which outlined new requirements affecting both faculty and students who conduct research using federal funding: 1. Make publications and their supporting data resulting from federally funded research publicly accessible without an embargo on their free and public release. 2. Enact transparent procedures that ensure scientific and research integrity is maintained in public access policies. 3. Ensure equitable delivery of federally funded research results and data. ## 1. Public accessibility Redivis helps data owners make research data as broadly accessible as possible while supporting appropriate protections for sensitive or restricted information. Public datasets and workflows can be explored without an account, while researchers can create a free account when they need to request restricted access or work with data. Open science does not require all research data to be released without restriction. Instead, data should be made as open as possible and as restricted as necessary. Redivis supports this approach by allowing data owners to: * Make data and documentation public by providing public access to dataset [descriptions, metadata, documentation, sample data, and complete data](/reference/data-access/access-levels.md) when appropriate. * [Keep restricted data discoverable](/guides/administer-an-organization/configure-access-systems.md) by making a dataset's overview and metadata publicly available while restricting access to the underlying data. * Provide responsible access by allowing data owners to limit access to [approved researchers ](/guides/discover-and-access-data/apply-to-access-restricted-data.md)through setting [application requirements](/reference/organizations/requirements.md). {% hint style="info" %} Redivis provides the technical tools for configuring and administering these access models. Institutions, dataset owners, and researchers remain responsible for determining appropriate conditions based on applicable laws, consent, licenses, data-use agreements, ethical obligations, and institutional policies. {% endhint %} ## 2. Transparent procedures Redivis systems are built to automatically capture and document any work done on datasets and analyses in standardized formats, while giving researchers and administrators the ability to supplement or override these when necessary. * [Datasets](/reference/datasets.md) are automatically [versioned](/reference/datasets/versions.md). All changes to variables and rows are recorded and made available to administrators and data viewers. * Redivis offers a no-code interface to build [transform](/reference/workflows/transforms.md) queries that compiles to SQL code. This code is available to the analyst and any viewers. * [Workflows](/reference/workflows.md) are [self-documenting](/reference/workflows/overview.md#project-tree-layout-and-operation). Every step taken in an analysis workflow is recorded sequentially in a visual format that is easy to follow. * Workflows are [version controlled](/reference/workflows/transforms/transform-concepts.md#history-and-revert). Every step is versioned and time-stamped, allowing users to revert to a previous iteration, or a viewer to understand how queries might have changed over time. * Workflows can be [forked](/reference/workflows/overview.md#fork-the-project), allowing researchers to build on, adapt, and extend prior research analyses while maintaining a connection to the original work. ## 3. Equitable delivery Redivis is free and accessible to any researcher, reviewer, or casual data browser. By taking multiple complex data storage and analysis systems and centralizing them with clear UI, Redivis makes full workflows easier to understand without specific technical knowledge. * Redivis uses transparent, open-source formats, allowing data, analyses, and workflows to be exported and used within other systems. * [APIs](https://docs.redivis.com/api/) make data and workflows available to researchers and administrators using their own systems. * No-code interfaces allow researchers at any skill level to build and understand research steps. * Common, open-source coding languages (SQL, Python, R) form the foundation of tools supported in [analysis workflows](/reference/workflows/notebooks.md). * All researchers receive a free [data storage allotment](/reference/your-account/workspace.md) and can explore and query data at no cost. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.redivis.com/redivis-for-open-science/open-access.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.