> 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/filtering-data-in-tables/dates.md).

# Dates

How to use filter operators for facets containing values of date datatype.

Explorer provides powerful date filtering capabilities to help you find data within specific time periods. You can filter date columns using a variety of standard operators and date formats.

## Available Date Operators

When filtering date columns, you can use these operators:

* **equals** - Matches exact dates
* **before** - Shows dates before a specified date
* **after** - Shows dates after a specified date
* **between** - Shows dates within a specified range
* **empty** - Shows only empty date values
* **not empty** - Shows only non-empty date values

## Using Date Filters

Date filtering is straightforward but flexible. Simply:

1. Click the search input in a date column filter
2. Choose your preferred operator
3. Select or enter the date(s)
4. Click "Apply" to activate the filter

## Date Ranges

The "between" operator lets you filter for a specific time period. This is particularly useful when you want to analyze data from a certain timeframe or study changes over time.

{% hint style="info" %}
All dates use UTC time zone for consistency across different regions.
{% endhint %}


---

# 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/filtering-data-in-tables/dates.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.
