> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/shade-academy/shade-academy-zh/su-cai/precision-filtering.md).

# 精确筛选

Shade 允许你按许多不同的属性进行筛选，包括你创建的链接、EXIF 和 IPTC 数据等元数据。可从任意资产页面顶部访问这些筛选器，如下所示。筛选器可以组合使用，以找到符合你所选所有属性的资产。

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2FxAusBnJZ8h1XvYq7RhP0%2FPercision%20filtering.gif?alt=media&#x26;token=5084e5b1-19a7-44c5-92af-39c91dcf8d2f" alt=""><figcaption></figcaption></figure>

## 使用 AI 生成筛选器

你无需逐个构建筛选器，只需描述你要查找的内容，Shade 就会为你创建筛选器：

1. 点击 **筛选器** 位于页面顶部。
2. 选择 **AI 筛选器** 并描述你想要的筛选条件，例如“过去 30 天上传的图片”或“超过 10GB 的文件”。你也可以直接在筛选搜索框中输入你的描述，并选择 **使用 AI 生成筛选器**.
3. 按 `回车`。Shade 会将你的描述转换为筛选器并应用它们。之后你可以像调整其他筛选器一样对它们进行调整。

如果 Shade 无法根据你的描述创建筛选器，请尝试重新表述，或检查你提到的属性是否存在于该驱动器中。

## 将筛选器保存为视图

视图可让你保存并重复使用筛选器、排序和显示设置的组合。要创建视图：

1. 设置好你想要的筛选器和显示方式，然后打开视图菜单（**选择视图**）并选择 **另存为新视图**。你也可以将鼠标悬停在 **视图** 侧边栏中你的驱动器下方，并点击 **+**.
2. 为视图命名并设置图标，如有需要还可以调整 **显示** 和 **排序和筛选器** 。
3. 在 **高级设置**，你可以选择启用：
   * **锁定此模板：** 其他驱动器用户无法发布对已锁定视图的更改。
   * **设为私有：** 私有视图只能由你查看和使用。
4. 点击 **创建视图**.

你的视图会显示在 **视图** 该驱动器在侧边栏中的位置。如果你更改了某个视图的筛选器，请点击 **保存更改** 并选择 **保存到当前视图** 以更新它，或选择 **将视图重置为原始状态** 以放弃你的更改。创建视图需要对该驱动器的编辑权限。


---

# 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://academy.shade.inc/shade-academy/shade-academy-zh/su-cai/precision-filtering.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.
