What this category's data looks like
This page addresses the scenario of multilingual materials and terminology processing in research achievement registration and intellectual property management. The materials come from three categories: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration forms carry the achievement name, contributors, date, and institutional seal; patent disclosure documents carry technical terminology, invention names, and reference numerals; software copyright materials carry the software name, version number, and ownership attribution. The three categories of materials enter the workflow in parallel in Chinese-English or multilingual versions, and the update cadence advances with application batches, examination opinions, and version iterations. Field characteristics center on names, quantities, dates, signatures, and receipts. The same record must maintain translated names that can be traced back to the source text across multiple materials, and terminology usage must be consistent throughout, before it can be released externally.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branch. When a node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Whether the same achievement name, number of contributors, and date are consistent across multilingual versions, and whether signatures and receipts are complete | Check options and branch connections one by one in the node, trigger once and then view the node status in the run records, and reference the selection result variable for a trial run |
| Patent disclosure document | Whether the translated technical terminology can be traced back to the source text, and whether the invention name and reference numerals match across multilingual versions | Reference variables and nodeId in a subsequent node for a trial run, and check whether the terminology usage in this material is consistent with the unified terminology glossary |
| Software copyright materials | Whether the software name, version number, and ownership attribution date are consistent with the registration form, and whether the version is synchronized | Sample three terms to check whether their usage is consistent throughout, and check the branch direction and interaction state records |
| Unified terminology glossary and comparison draft | Sample three terms to check whether their usage is consistent throughout, and whether the translated names can be traced back to the source text | Continue execution according to the branch in a subsequent node, and check whether this output covers the fields of the three material categories |
Three common errors
- Symptom: The same achievement name is written differently in the registration form and the disclosure document. Cause: Multilingual materials did not use a unified terminology glossary, and each material was translated independently without checking back against the source text.
- Symptom: The number of contributors or the date does not match between two materials. Cause: Versions were not synchronized; after the registration form was updated, the disclosure document and copyright materials were not refreshed accordingly.
- Symptom: Missing signatures or receipts still proceed to the next step. Cause: After the interaction was completed, the branch direction and status records were not checked, and execution continued before the materials were completed.
How to verify the setup
Feature acceptance: Run a trial for each option one by one, check the branch direction and interaction state in the run records, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business testing: Sample three terms to check whether their usage is consistent throughout, and check whether the translated names can be traced back to the source text.
- Check options and branch connections one by one in the node, trigger once and then view the node status in the run records.
- Reference
variablesandnodeIdin a subsequent node for a trial run, and check the branch direction and interaction state records.