What this category's data looks like
Research achievement registration and intellectual property management involves 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 receipt; software copyright materials contain the version number, development completion date, ownership, and seal. The materials come from the research management department, inventors, and the development team, and are updated by batch and by application milestone. When entering deployment, operations, and application handover, achievement registration forms are used to verify the achievement name and registration date, patent disclosure documents are used to verify the inventors and filing date, and software copyright materials are used to verify the version and ownership signature; together, the three support a handover-ready deployment state and operation records.
Configuration and implementation checks
This step is handled by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and it outputs whether the connection is available (service startup result and connection logs). "A handover-ready deployment state and operation records" are then completed by deployment handover and subsequent business processing. The connection addresses are configured via 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 |
|---|---|---|
| Achievement registration form | Name, contributors, date, and signature are complete and consistent with the patent disclosure document | Compare against the database address of the deployment environment, verify the registration form fields and signature, and check the connection logs |
| Patent disclosure document | Inventors, filing date, and receipt are complete and consistent with the achievement registration form | Verify the disclosure document date and receipt, and check whether the log database connection variable is set separately |
| Software copyright materials | Version number, development completion date, and ownership signature are complete and consistent with the registration form | Verify the version and signature, connect once to the cache instance with a client, and verify the response |
| Vector database connection variable | Consistent with the vector database actually in use and connectable | Compare against the deployment instructions to verify the selected vector database and address, and confirm the value of PG_URL |
Three common errors
- Symptom: The name, quantity, and date of the same achievement do not match across the two materials. Cause: The registration form and the disclosure document are updated separately, and signatures and receipts are not verified against the same batch.
- Symptom: The version in the software copyright materials is not synchronized, and the handover form is missing one record. Cause: The version number is updated only on the development side, and the registration form and disclosure document do not synchronize the version.
- Symptom: After startup, the logs continuously report connection timeouts. Cause: The connection addresses of the main business database, log database, cache, or vector database are inconsistent with the actual instances.
How to verify the setup
Acceptance for this feature: connect once to each of the main business database, log database, cache, and vector database, verify the connection results in the startup logs, and confirm that the values of MONGODB_URI, PG_URL, and REDIS_URL are consistent with the deployment instructions.
Business test: verify each item once according to the handover form, see which record is missing, and confirm that the version, connection, and task records are consistent.
- In the deployment environment, verify that the value of this variable is consistent with the database address, and check which database the logs are written to.
- Connect once to the cache instance with a client, verify the response, and compare against the deployment instructions to verify the selected vector database and address.