What this category's data looks like
At the signing stage of research project task books, source materials include the project task book, the subject task breakdown table, the budget book, and the progress records and statistical ledgers generated during the signing process. The project task book provides the project name, principal investigator, start and end dates, and signature fields; the subject task breakdown table breaks the research content down to subjects, responsible persons, and milestone dates; the budget book lists budget categories, amounts, and matching-fund notes. After these materials enter the progress records and statistical verification function, they respectively take on three roles: source of definitions, basis for breakdown, and funding verification: the task book defines the overall definitions, the breakdown table defines milestones and responsible persons, and the budget book defines funding fields. The update cadence follows the signing process: entry on the day of signing, weekly aggregation, and monthly statistics. Field characteristics are concentrated in five categories: names, quantities, dates, signatures, and receipts. The latest signed draft is treated as the current version, and historical drafts are retained for comparison.
Configuration and implementation checks
This step is executed by the connection configuration of the deployment environment (server side), not by the capabilities of a model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical definitions description" is then completed by deployment handover and subsequent business processing. The connection address is configured through environment variables; the main business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it reuses the main database.
| Object | Check | Verification action |
|---|---|---|
| Project task book | Check whether the project name, principal investigator, start and end dates, and signature fields are consistent with the signed draft | Compare field by field against the signed draft, and check whether signatures and receipts are complete |
| Subject task breakdown table | Check whether the subject names, responsible persons, milestone dates, and definitions match the task book | Check names, quantities, and dates row by row by subject, and record exceptions |
| Budget book | Check whether the budget categories, amounts, and matching-fund notes are consistent with the definitions in the task book and breakdown table | Check amounts and notes by budget category, and mark entries whose versions are not synchronized |
| Main business database connection variable | Points to the main business database actually in use and can be connected | In the deployment environment, check that the variable value matches the database address, and inspect the startup logs of MONGODB_URI |
Three common errors
- Symptom: the name and quantity of the same subject do not match across two materials. Cause: fields were not unified according to the task book definitions during entry, and versions were not synchronized.
- Symptom: milestone dates differ by several days across two materials. Cause: after the breakdown table was updated, it was not written back to the task book, and historical drafts were not retained for comparison.
- Symptom: missing signatures or receipts make records impossible to archive. Cause: the signing process did not collect all receipts, and statistics treat them as incomplete.
How to verify the setup
This function's acceptance: connect once to the main business database, log database, cache, and vector database item by item, and check the connection results in the startup logs; for the main business database check MONGODB_URI, for the vector database check PG_URL, and for the cache check REDIS_URL.
Business test: use one week of records to check totals, and see whether definitions and exceptions are clearly written
- Compare the names, quantities, dates, and signatures of the project task book, subject task breakdown table, and budget book item by item on a weekly basis, and write exceptions into the header of the definitions description table.
- Check that the values of the connection variables for the main business database, log database, cache, and vector database match the database addresses, and inspect the service startup results and connection logs.