> 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/data-deposition-instructions/metadata-and-tabular-data-files.md).

# Metadata and Tabular Data Files

Metadata and tabular data (e.g. culture data) generated by C-CoMP will ultimately be stored in at least two separate places:

1. Archived on a computer and/or storage server in lab of origin
2. C-CoMP Google Drive (temporary storage)
3. BCO-DMO Dataset entry as part of the [C-CoMP Program](https://www.bco-dmo.org/program/871064)

This storage scheme ensures that 1) there are multiple back-ups of the metadata and tabular data in different physical and cloud-based locations, 2) all C-CoMP members have access to facilitate direct and efficient collaboration, and 3) metadata and tabular data are publicly accessible on BCO-DMO and linked to domain repositories.

Instructions for submitting metadata and tabular data are shared below. Please submit metadata in the following order to avoid lags in data sharing.

#### C-CoMP Google Drive 

We can temporarily store metadata and tabular data in the C-CoMP Google Drive to facilitate data sharing within the Center. This data will be archived once the metadata and tabular data has been deposited at BCO-DMO. 

#### BCO-DMO

1. C-CoMP projects will be registered with BCO-DMO as part of the C-CoMP Program using the [online submission tool](https://submit.bco-dmo.org/). The Digital Coordinator can register projects on your behalf, but will ask you for additional information. At BCO-DMO, projects oversee a collection of one or more datasets.
   1. If you need help, consult [these instructions](https://bcodmo.gitbook.io/how-to/submission-tool/registering-a-project). 
2. Once your project is registered, individual datasets can be submitted and filed underneath the project.
   1. At BCO-DMO, datasets are licensed under Creative Commons Attribution 4.0. For more guidance, please read the BCO-DMO [Terms of Use](https://www.bco-dmo.org/terms-use).

<figure><img src="/files/hvbxBquU3xXEMLoDpezt" alt=""><figcaption><p>Figure caption: Hierarchy of the C-CoMP Program at BCO-DMO. Datasets are filed under individual projects that are encapsulated within the C-CoMP Program. Projects are registered before datasets are submitted.</p></figcaption></figure>


---

# 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/data-deposition-instructions/metadata-and-tabular-data-files.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.