What this category's data looks like
In the scenario of signing research project task books, materials are mainly of three types: project task books, subject task breakdown tables, and budget books. Their sources are the research management department, subject leaders, and the financial review stage, and their update cadence follows signing rounds and change approval milestones. The project task book carries the research objectives, assessment indicators, and signature fields; the subject task breakdown table carries the sub-project names, responsible persons, start and end dates, and task boundaries; the budget book carries subject amounts, calculation bases, and approval signatures. When these three types of materials enter the knowledge base retrieval and recall function, they serve respectively as source documents for candidate snippets, and differences in their fields, dates, and signatures are amplified during recall and reranking. Therefore, a version ledger and change records are needed to support a unique current version, traceability of old versions, and synchronized citations.
Configuration and implementation checks
This step is performed by the knowledge base retrieval service (retrieval node and search test), which outputs candidate snippets and similarity scores (after mode, merge, rerank, filter, and limit trimming). The "version ledger and change records" are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Project task book | Whether the research objectives, assessment indicators, signature fields, and signing date are consistent across versions | In the search test, test once each with synonymous questions, record the number of candidates and scores, and check whether the signature and date fields fall within the same current version |
| Subject task breakdown table | Whether the sub-project names, responsible persons, start and end dates, and task boundaries match the task book | Switch searchMode to semantic, full-text, or hybrid, observe whether the candidates cover both the breakdown table and task book snippets, and check the names and dates |
| Budget book | Whether the subject amounts, calculation bases, and approval signatures are consistent with the task book and breakdown table | Enable or disable usingReRank, compare the ranking of the top few results, and check whether the amounts and signature receipts come from the same source |
| Version ledger and change records | Whether the current version is unique, old versions are traceable, and citations are synchronized | After changing one piece of content, check the version number change, and use similarity and limit to observe whether candidates and citations are updated synchronously |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the task book and the breakdown table. Cause: The two materials are updated separately, and fields are not aligned through the version ledger.
- Symptom: After changing one piece of content, the old version is still recalled, and citations are inconsistent with the current version. Cause: The version is not synchronized, and the knowledge base is not updated according to the change records.
- Symptom: The budget book lacks a signature or receipt, but retrieval still returns that snippet. Cause: Signatures and receipts are not included in material admission checks, and candidates are not filtered by version status.
How to verify the setup
This function's acceptance: test once each with synonymously rewritten questions, compare candidates and scores, then toggle reranking to inspect the ranking of the top few results; record the number of candidates and scores, and observe the impact of similarity, limit, searchMode, and usingReRank on the results.
Business test: change one piece of content and see whether the version number and citations are updated synchronously.
- In the knowledge base search test, retrieve separately by material category, record the number of candidates and scores, and check whether the returned snippets cover the key fields of the project task book, breakdown table, and budget book.
- Check the current version, old version retention, and citation synchronization status one by one against the version ledger; when inconsistencies in names, quantities, dates, or signatures are found, return to the source materials to correct them.