> 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/explorer/browsing-collections.md).

# Browsing Collections

[Explorer](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/explorer/broken-reference/README.md) organizes research data into Collections—curated sets of related data tables maintained by data custodians. This guide explains how to find and browse collections effectively.

## Collection Overview

The Explorer landing page displays recent collections as interactive cards, each showing:

* Collection name and description
* Associated tags for quick reference
* Access policy status
* Number of available data tables

## Finding Collections

You have two main ways to locate specific collections:

### Direct Search

1. Use the search bar in the header
2. Enter keywords matching collection names, descriptions, or tags
3. Select a collection directly from the search results
4. Alternatively, press "Enter" to view all matching results

### Advanced Search

When you need more refined search options:

1. Press "Enter" after entering search terms
2. Browse the comprehensive results page
3. Use available filters to narrow down collections by:
   * Creation date
   * Last update
   * Data type
   * Access level

## Accessing Collections

Once you've found your desired collection, simply click its card to view the full details and access the data tables. Remember that some collections may require appropriate authentication based on their access policy.


---

# 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/explorer/browsing-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.