> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/publisher/collections.md).

# Collections

## Overview

Collections are customizable groups of files and tables from your connected data sources in [Publisher](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/publisher/collections/broken-reference/README.md). They allow you to organize and share specific datasets through federated data sharing networks, making them accessible to researchers.

## Types of Collections

### Library

The Library is a default, system-generated collection that:

* Contains all data connected to [Publisher](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/publisher/collections/broken-reference/README.md)
* Provides a complete view of your available data
* Cannot be modified or shared
* Serves as a reference for creating custom collections

### Custom Collections

Create your own collections to:

* Organize data into logical groups
* Share specific datasets with researchers
* Control access to your data
* Manage data discovery and distribution

## Working with Collections

Collections provide a flexible way to:

* Select specific files and tables from your data sources
* Create meaningful groupings of related data
* Control sharing permissions
* Enable data discovery through networks
* Manage access policies for different user groups


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.omics.ai/products/publisher/collections.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.