> 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/file-naming-conventions/sequencing-products.md).

# Sequencing Products

<figure><img src="/files/kHARwehjB4zKllSHLAyW" alt=""><figcaption><p>This file name refers to version one (v01) of a metagenome assembled genome from sequences in file number 8. </p></figcaption></figure>

### Field Definitions

1. Dataset Number:
   * All C-CoMP datasets will be assigned an internal dataset number. Please request this number on the #dataset\_number\_requests slack channel following the instructions provided above.
   * Metadata about the dataset (including Dataset number, method type, and data storage location) will be recorded in the C-CoMP Data Catalog.
2. Assembly Type:
   * The kind of method that was used for this specific project X sample (see examples and abbreviations below)
3. File Number (File\_No)
4. Assembly Version
   1. This field indicates the version number of the assembly
5. File-type Extension

Assembly type:

* MAG - Metagenome assembled genomes based on de-novo assembly. Read more about MAGs [here](https://anvio.org/vocabulary/#metagenome).&#x20;


---

# 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:

```
GET https://c-comp.gitbook.io/data-management-handbook/file-naming-conventions/sequencing-products.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.