What this category's data looks like
Research achievement registration and intellectual property management involve three types of materials: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration forms record the name, contributors, date, and signature; patent disclosure documents contain the technical solution, inventors, filing date, and signature; software copyright materials include the software name, version number, development completion date, and seal. The material sources are research management departments, agencies, and R&D teams, and the update cadence advances with filing, examination, and change milestones. When entering scheduled tasks and automation features, the achievement registration form serves as the primary record to trigger version ledger generation, while patent disclosure documents and software copyright materials participate as reference sources in change record comparison, each taking on the roles of field validation and version traceability.
Configuration and implementation checks
This step is executed by trigger configuration and tool nodes (scheduling capability is not in the tool introduction), outputting trigger records and execution results. The "version ledger and change records" are completed by business processing according to records or by supplementary runs. Trigger configuration is responsible for invoking the corresponding tool node at the scheduled time; the tool node decides whether to execute according to the tool introduction, and the execution result is written into the trigger record.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Whether fields, dates, and signatures are consistent with the patent disclosure document | Check the name, contributors, and date fields, inspect whether the signature field and receipt are complete, and confirm the current version is unique |
| Patent disclosure document | Whether fields, dates, and signatures are consistent with the software copyright materials | Check the technical solution name, inventors, and filing date, inspect the signature and receipt, and confirm the old version is traceable |
| Software copyright materials | Whether fields, dates, and signatures are consistent with the achievement registration form | Check the software name, version number, and development completion date, inspect the seal and receipt, and confirm references are synchronized |
| Trigger record and execution result | Whether execution occurs at the scheduled time and only once | View the trigger record and execution time, confirm there is no duplicate execution, and that the tool call termination node is connected at the end |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the achievement registration form and the patent disclosure document. Cause: The two materials are maintained separately, fields are not compared for consistency, and changes are made in only one place.
- Symptom: Versions are not synchronized, and the old version is still referenced. Cause: Trigger configuration does not cover change milestones, the reference source is not updated after the tool node executes, and the ledger is not written back.
- Symptom: Missing signature or receipt. Cause: The material circulation step does not validate the signature field and receipt field, and the trigger record only records the execution result without marking missing items.
How to verify the setup
This feature acceptance: check the trigger record and execution time, and confirm execution occurs at the scheduled time and only once.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the connection between trigger configuration and tool nodes, confirm the tool introduction specifies the execution timing, and that the tool call termination node is connected at the end where no summary is needed.
- Check the version ledger and change records, and confirm the current version is unique, the old version is traceable, references are synchronized, and the signature and receipt fields are complete.