What the Data for This Category Looks Like
Data related to livestock and poultry farming comes primarily from three sources: daily production logs of farms, inspection records from local animal husbandry and veterinary stations, and the Ministry of Agriculture and Rural Affairs’ livestock and poultry industry monitoring database.
There are two update schedules for this data. Farm production logs are updated daily or weekly. Public official monitoring data is released quarterly.
Most documents are structured tables, with fields including number of livestock on hand, slaughter volume, disease incidence rate, per-unit feed consumption, and unit weight gain cost. Units include head, kilogram, yuan per kilogram, and similar units. Some documents include complete cycle records for the corresponding breeding batch.
What Constraints Do These Characteristics Impose on the Citation Sources and Traceability Link
The multi-source nature of livestock and poultry farming data requires the traceability process to distinguish source identification rules for private farm logs and public industry monitoring data. This prevents mixing of data for the same indicator from different sources.
Differences in update cadences across data sources require configuring appropriate incremental sync cycles. These cycles must align with weekly updates for internal farm logs and quarterly updates for public data.
The presence of structured fields and specific units requires retaining field names and unit information during recall. This ensures the accuracy of cited content.
Some documents are tied to breeding batch IDs. Traceability must associate batch information, and cannot rely solely on file names. This avoids confusion between multiple records for the same batch.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
RECALL_TOP_N | Top 6-8 results | Livestock and poultry farming data has many fields, and individual chunked content is brief. A sufficient recall count is needed to cover core indicators |
SIMILARITY_THRESHOLD | 0.72-0.85 | Structured field matching has high precision requirements. A threshold that is too low will introduce irrelevant breeding batch data. A threshold that is too high may miss valid records |
PARSE_SEGMENT_LENGTH | 800-1200 characters | Breeding logs include multiple field combinations. Segments that are too long will destroy field relevance. Segments that are too short will split complete records for the same batch |
SOURCE_DISPLAY_MODE | Show full source path + batch ID | Livestock and poultry farming data must be tied to batch IDs for accurate traceability. Full source paths can distinguish private logs from public monitoring data |
FILE_PREVIEW_ENABLE | Enabled | Most breeding documents are structured tables. The original document before chunking can display complete batch information and raw data, making it easier to verify cited content |
SYNC_INCREMENTAL_INTERVAL | 168 hours (weekly) | Aligns with the weekly update cadence of farm logs, and adapts to the sync cycle for internal private data |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require targeted analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Misconfigurations
- Phenomenon: An API call returns a model response, but the citation field is empty or returns red error numbers. Cause: The
SOURCE_DISPLAY_MODEparameter is not configured correctly, or the traceability switch for the associated knowledge base data source is not enabled. - Phenomenon: The end-user response does not display source information for the cited snippet. Cause:
FILE_PREVIEW_ENABLEis not enabled, a citation display node is not added to the workflow, or traceability information is not bound to the response output. - Phenomenon: Cited content cannot be linked to the original document before chunking. Cause: Original file paths or batch ID information was not retained during knowledge base import, or the segment length was set too short, splitting complete batch records from the original document.
How to Confirm Proper Configuration
- Initiate a query for core breeding indicators. Check if the response includes source identifiers, including data source type and batch ID.
- Click the source link in the response. Confirm that it jumps to the original document page before chunking. Do not only display the file name or chunked snippet.
- View the knowledge base sync logs. Confirm that the update cycles for different data sources match the configured incremental sync interval.
- Call the API to retrieve response results. Check that the returned citation field includes complete document paths and slice position information.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.