# Filters

You can constrain the content that is being displayed by adding certain `require-...="..."`  attributes to the html snippet, for example

```markup
<div
    class="tq-talque-view"
    org-id="VDYRv7v7oaA2s432rwMg"
    view-id="IoKwbA39MxcntEocizXB"
    initial="lecture-list"
    require-tags="tag1,tag2">
</div>
```

will list only the lectures that are tagged with `tag1` and `tag2`. Here, the tags are the internal codes for the tags, not the (potentially multiple) translations.

### Filtering lectures

* `require-tags="tag1,tag2"` where the tag codes are the internal codes for the lecture tags. Type data.org.tagLabels in the javascript console for the mapping to their translated label.
* `require-formats="format1, format2"` where the format codes are the internal codes for the lecture formats. Type data.org.formatLabels in the javascript console for the mapping to their translated label.&#x20;
* `require-topics="topic1, topic2"` where the topic codes are the internal codes for the lecture topics

### Filtering speakers

To display only a subset of the speakers, use `require-badges="badge1,badge2"`. The internal codes of the badge categories can be seen when you type data.org.badgeLabels into the javascript console.

### Filtering sponsors

To display only a subset of the sponsor categories, use `require-sponsors="cat1,cat2"`. The internal codes of the sponsor categories can be seen when you type `data.org.sponsorLabels` into the javascript console.

### Filtering exhibitors

To display only a subset of the exhibitor categories, use `require-exhibitors="cat1,cat2"`. The internal codes of the exhibitor categories can be seen when you type `data.org.vendorLabels` into the javascript console.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://talque.gitbook.io/public/view-plugin/installation/filters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.