What this category's data looks like
This category's data involves three types of materials: journal publication license, annual verification form, and rectification report. License fields include journal name, journal number, sponsoring organization, validity period, and issuing authority; verification form fields include year, publication period, circulation, responsible person's signature, and submission date; rectification report fields include issue items, rectification measures, completion date, and receipt signature. Material sources are approval documents from the publication administrative department, submission documents from the sponsoring organization, and internal archived scanned copies. The update rhythm is license renewal upon expiration, annual submission of verification forms, and closed-loop updates of rectification reports by issue. When the three types of materials enter this feature, the license and verification form serve as basis sources, and the rectification report serves as a supporting source, jointly supporting the generation of basis entries that can be traced back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Basis entries that can be traced back to the original text" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Whether fields, dates, and signatures are consistent with the current version | Check the journal name, journal number, sponsoring organization, validity period, and issuing authority; check the options and branch connections one by one in the node; confirm that the referenced variable variables has been passed to subsequent nodes |
| Annual verification form | Whether the name, quantity, and date of the same record match across the two materials | Check the year, publication period, circulation, responsible person's signature, and submission date; trigger one viewing of the node status in the run records; confirm the branch direction and interaction state records |
| Rectification report | Whether missing signatures or receipts and unsynchronized versions affect basis traceback | Check the issue items, rectification measures, completion date, and receipt signature; reference the selection result variable in subsequent nodes and run a test once; confirm that the branch corresponding to nodeId is correct |
| Basis entry | Whether the entry can match the original source | Compare the quoted text with the original paragraph one by one, record the number of array entries, separately check the tokens budget of the quoted text, and confirm that the source field in variables can be traced back |
Three common errors
- Phenomenon: The same journal name is written inconsistently in the license and the verification form. Cause: The two materials were entered in different handling stages, and field alignment and version synchronization were not performed, causing the basis entry to fail to match the original text when traced back.
- Phenomenon: The quantity in the verification form does not match the quantity in the rectification report. Cause: After rectification, the verification form was not backfilled, the version was not synchronized, subsequent nodes continued execution along the old branch, and the basis entry referenced an expired record.
- Phenomenon: The rectification report lacks the responsible person's signature or receipt. Cause: When the materials were archived, the signature and receipt fields were not validated; after the interaction was completed, the process stopped, and the basis entry could not be traced back to a valid original text.
How to verify the setup
Feature acceptance: run tests option by option, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that nodeId and variables references are correct.
Business test: ask a cross-material basis question, see whether the answer provides a traceable source, and check that the number of quoted entries and the tokens budget of the quoted text are recorded separately.
- Check the options and branch connections one by one in the node, trigger one viewing of the node status in the run records, and confirm that the interaction state is recorded.
- Reference the selection result variable in subsequent nodes and run a test once, confirm that
variablesandnodeIdcorrespond to the correct branch direction, and that the basis entry can be traced back to the original text.