> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/guides/controls/tagged-timeline-control.md).

# Tagged-timeline control

**When do you use it?**

Filter a network over time using years defined in the tag field.

*Note: If you include timeline data using the "tags" field, the controls will provide clickable dates that can be used to filter the map. We recommend using years to define when an element/connection was present. You can supply multiple years to be able to allow disjointed timelines (e.g. 2012, 2013, 2016 for an element that was part of the network until 2013, then left and joined again in 2016).*

{% hint style="info" %}
Want to learn more about why and how to use a Tagged-Timeline Control? \
[Check out this blog](https://blog.kumu.io/filtering-networks-over-time-using-custom-controls-dcb1382c9b7c). 
{% endhint %}

## **Advanced Editor**

```scss
@controls {
  bottom {
    tagged-timeline {
      range: 2000..2016;
      target: element;
    }
  }
}
```

**Supported properties**

* `range` defines the years that should be included as clickable links.
* `target` defines whether the filter should apply to elements, connections, or loops. To apply the filter to elements and connections, use `element,connection;`.
* `multiple` by default the timeline allows you to select multiple years. Use `multiple: false` to only allow a single year to be selected instead.
* `default` defines which values should be selected by default. Use `select-all` to select everything by default (or `show-all` for a similar effect without selecting).

[Check out our controls reference](/overview/advanced-editor-hub/controls-reference.md) to see the full list of properties and values recognized by the tagged timeline control.


---

# 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.kumu.io/guides/controls/tagged-timeline-control.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.