> 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/collection-filters.md).

# Collection Filters

Publisher's collection filters dynamically manage collection contents, automatically updating as new [data sources](/products/publisher/data-sources.md) match your filter criteria. These filters are available for both files and tables, helping administrators precisely define collection contents.

## How Filters Work

Publisher automatically updates collection contents based on your filter settings, ensuring collections stay current with your data sources. When new data is connected to [Publisher](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/publisher/collections/broken-reference/README.md), it's automatically evaluated against existing collection filters.

### Example Scenario

Let's say you create a collection to gather all files containing "portal" in their names:

1. Initial State:
   * One file in Publisher contains "portal"
   * Your collection has the <mark style="color:orange;">`Name`</mark> filter condition set to <mark style="color:orange;">`Contains`</mark> and the value to <mark style="color:orange;">`portal`</mark>
   * This collection contains only one file since it's the only file that has "portal" in its name
2. After Adding New Data:
   * A new data source with a "portal" file is connected
   * Collection automatically includes this new file
   * Collection now contains both matching files

#### Collections automatically:

* Evaluate new data against filter criteria
* Include matching content from new data sources
* Update without manual intervention
* Maintain consistent organization of your data


---

# 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/collection-filters.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.