Data Profile for This Category
Water utility marketing content data mainly comes from official website announcements of water enterprises, offline payment notice templates, official account promotional posts, and community activity materials. Update frequency aligns with marketing campaign cycles. Regular campaigns receive monthly updates, while policy-related content receives quarterly updates. Most documents are structured or semi-structured, with core fields including activity theme, applicable service area, application channel, and deadline. Involved units include cubic meters, number of service households, payment amount, and similar metrics.
Constraints Imposed on Retrieval and Recall
Water utility marketing content has scattered sources, covering web pages and digitized versions of offline materials. This requires the retrieval system to support unified parsing and recall of multi-format files. Some content has strong timeliness: campaign-related copy must be synced to the knowledge base quickly after publication. This requires an incremental update mechanism. Documents contain clear geographic and unit fields. The retrieval system must support precise filtering by service area and unit of measurement. Content length varies widely: from short activity prompts of a few dozen characters to long activity plans of thousands of characters. The retrieval system must adapt text segmentation and recall logic for different lengths. As the knowledge base content expands, the scope of a single recall must be limited to avoid invalid data slowing down response speed.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
UPLOAD_FILE_MAX_SIZE | 500 MB | Water utility marketing materials are mostly documents combining images and text, and single file size usually does not exceed 500 MB. This value covers most upload scenarios. |
PARSE_FILE_TIMEOUT_SECONDS | 120 seconds | Water utility documents may contain long-text activity plans. 120 seconds covers parsing time for most complex documents and avoids parsing failures. |
Recall count | Top 8 results | Water utility marketing content is often categorized by region and activity. Too many recall results increase context redundancy. 8 results cover most user retrieval needs. |
Similarity threshold | 0.72–0.85 | There are few technical terms in water utility marketing content. An overly high threshold will miss relevant activity information, while an overly low threshold will introduce irrelevant content. |
Reranked return count | Top 3 results | Users only need core activity information when searching for marketing content. 3 results ensure concise information that covers requirements. |
Segment length | 800–1200 characters | Water utility documents include both short copy and long plans. This segment range balances context coherence and retrieval accuracy. |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require targeted analysis, and testing on local samples is recommended before finalizing settings.
Three Common Configuration Mistakes
- Phenomenon: A
504 Gateway Timeouterror is returned when calling the knowledge base query interface, or response time exceeds 30 seconds. Cause: The values of recall count and reranked return count are not limited, and too much redundant data is recalled, increasing retrieval time. - Phenomenon: Non-target region water utility marketing activity content appears in retrieval results, and the
service_areafield is matched incorrectly or is empty. Cause: Retrieval filtering by geographic field is not configured, or the similarity threshold is set too low, introducing irrelevant content. - Phenomenon: When calling the upload interface via an external program, the title and content of HTML cannot be extracted correctly. Cause: Corresponding fields are not passed in the parameter format required by the interface documentation, resulting in missing core information in the parsed document.
How to Verify Proper Configuration
- Perform a single file upload test, confirm that the upload progress is normal, and that the parsed document can be viewed in the knowledge base list. Check the values of
UPLOAD_FILE_MAX_SIZEandPARSE_FILE_TIMEOUT_SECONDSto match the size and parsing time of the current upload document. - Initiate a retrieval test with region restriction, confirm that returned results only include marketing content for the target service area. Check the retrieval filtering rule configuration to ensure the geographic field is included in retrieval conditions.
- Initiate a batch retrieval test, count response time, adjust the values of recall count and reranked return count to ensure response time meets business requirements.
- Initiate a multi-format document upload test, confirm that text from web pages, PDFs, and image OCR can be correctly parsed and included in the retrieval scope.
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.