> For the complete documentation index, see [llms.txt](https://c-comp.gitbook.io/data-management-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://c-comp.gitbook.io/data-management-handbook/executive-summary.md).

# Executive Summary

## Introduction

The [Center for Chemical Currencies of a Microbial Planet](https://ccomp-stc.org/) (C-CoMP) is a NSF-funded Science and Technology Center that promotes a *mechanistic understanding of the chemical currencies in microbial ecosystems in the context of a changing planet and through increased participation in ocean science*. Open science is a foundational, essential, and uniting component of C-CoMP’s research and knowledge transfer. As such, C-CoMP is committed to sharing all aspects of the research process in a timely manner to advance transparency and reproducibility in science, share knowledge, stimulate data integration efforts, and encourage others in the field of ocean science to participate in the open science movement.

## **Challenges for Open Science**

* C-CoMP generates observational, experimental, simulated, and derived data in both standard and non-standard formats using a variety of different methodologies, sample sources, and file naming conventions.
* There are no centralized repositories to store and curate such a diversity of data types.
* C-CoMP is composed of individual lab groups that already follow their own procedures for sharing data.
* There are various levels of risk associated with releasing data prior to article publication and this risk level changes with career stage.

## **Solutions for Open Science**

This living handbook presents Center-wide solutions for the challenges listed above and guidance for implementing [C-CoMP’s Open Science Policy](https://ccomp-stc.org/wp-content/uploads/2022/11/C-CoMP_OpenScience_Policy_9.16.22_v1.pdf). This handbook is a living document; we expect to update this handbook as the Center ages.

* The implementation of C-CoMP’s open science framework centers around the Data Roadmap, a general plan that outlines the data life cycle from initial study ideation through data deposition.
* C-CoMP uses standardized file naming conventions to facilitate internal and external data sharing.
* C-CoMP uses the [Biological and Chemical Oceanography Data Management Office](https://docs.google.com/document/d/1bPL9FMf8qDdpiMLbGUeZvEFaZIuq88cf9aRgzeRBumM/edit#bookmark=id.jhbso59bcafb) (BCO-DMO) repository to organize, describe, and store metadata and tabular data for all datasets; domain-specific datasets will be linked to the relevant BCO-DMO metadata landing pages using accession numbers.
* C-CoMP tracks all datasets by assigning internal dataset numbers and other metadata in the C-CoMP Data Catalog.
* C-CoMP expects timely submission of research products to publicly accessible repositories as defined in the data roadmap and open science policy. That being said, C-CoMP has included a moderate option for sharing intermediate research products with specific requestors during data analysis and prior to the onset of writing.


---

# 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://c-comp.gitbook.io/data-management-handbook/executive-summary.md?ask=<question>&goal=<endgoal>
```

`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.