> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/fields/best-practices-3.md).

# 最佳实践

## 以下是文档处理系统字段配置的最佳实践，强调了理解文档工作流和数据要求的重要性。

### **了解文档工作流：**

* 全面分析文档工作流，确定文档从采集到处理，再到存储或发布所经历的不同阶段和步骤。
* 确定工作流每个步骤中需要采集、审核、处理或提取的具体数据。

### **确定关键数据点：**

* 确定对业务流程或分析至关重要的关键数据。
* 根据字段对业务流程或分析的重要性为其排序，确保正确采集和处理这些字段。

### **使字段与数据要求相匹配：**

* 根据具体的数据要求匹配字段属性，包括字段类型（文本、日期、数值等）、验证规则，以及必填或只读等属性。
* 配置字段属性时，还要考虑安全要求、隐私法规和法律要求。

### **考虑灵活性和可扩展性：**

* 设计字段时应确保其具备灵活性和可扩展性，以适应未来的自定义设置，或文档工作流及数据要求的变化。
* 确保字段配置能够轻松、高效地纳入新的数据点或变更后的要求。

### **测试和验证：**

* 进行全面测试，确保配置的字段能够正常工作并产生预期结果。
* 通过处理大量文档并验证所采集的数据是否符合要求，来验证字段配置。

通过了解文档工作流和数据要求，并应用字段配置的最佳实践，您可以确保文档处理系统高效、准确地运行。这有助于提高数据质量、优化工作流，并提升整体业务绩效。


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/fields/best-practices-3.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.