What this category's data looks like
This page addresses the National Key R&D Program project application scenario, where materials include three types: the project application form, the budget application form, and the cooperation agreement. The project application form states the research content, assessment indicators, and undertaking units; the budget application form states the funding categories and amounts; the cooperation agreement states the division of labor, funding allocation, and intellectual property ownership. When these three types of materials enter the conversation logs and auditing function, each plays a different role: the project application form provides the task and indicator definitions, the budget application form provides the quantity and date definitions, and the cooperation agreement provides the signature and receipt definitions. The update cadence of materials advances with the application milestones, and versions increment in sync with revisions. Field characteristics are concentrated in four categories: name, quantity, date, and signature. The same record must be aligned item by item across the three materials; unsynchronized versions or missing signatures will directly cause missing items on the handover form.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), which outputs the session message list and the total record count, including role and reference information. "Handover-ready deployment status and operation records" are then completed by a human or an external system.
| Object | Check | Verification action |
|---|---|---|
| Application and session identifiers | Consistent with the actual application and actual session | Check the source of chatId and the application identifier in the request parameters, and confirm they correspond to the current deployment environment |
| Pagination parameters | Record count matches the total count | Pull two consecutive pages and compare the offset and the total record count total, confirming that only the first page was not retrieved |
| Role field | message roles correspond to the original conversation | Look at the order of the two role types in the returned list, and check whether dataId and value are returned with the records |
| Project application form, budget application form, cooperation agreement | Name, quantity, date, and signature are consistent item by item | Check the fields, dates, and signatures of the three materials against the handover form, confirming that versions are synchronized and receipts are complete |
Three common errors
- Symptom: The name and quantity of the same record do not match between the project application form and the budget application form. Cause: The two materials are maintained separately and not registered under the same definitions, so there is no comparison record at handover.
- Symptom: The cooperation agreement version is not synchronized, and signatures or receipts are missing. Cause: It was not re-signed after modification, the handover form does not list signature items, and the next shift cannot verify it.
- Symptom: The interface returns empty but there are sessions in the interface. Cause: The sources of the application and session identifiers are inconsistent, or only the first page was retrieved, and the total record count and message count are not aligned.
How to verify the setup
This function's acceptance: page through using the total record count total to retrieve everything, sample one record to check the role, reference information, and time, confirm response code of 200, and check the message identifiers and content fields _id, dataId and value.
Business test: check item by item against the handover form once, see which record item is missing, and confirm that the version, connection, and task record are consistent.
- Page through by application and session dimension, record the offset and total record count, and confirm there are no omissions between the two pages.
- Open one record to check the reference and elapsed time fields, and check and register the tokens of the reference text and the array item count separately.