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 project name, contributors, dates, and signatures/seals; patent disclosure documents carry the technical solution, inventors, and application milestones; software copyright materials include the version number, development completion date, and signature receipt. Material sources are scattered across research management departments, agencies, and R&D teams, and the update cadence is driven by application cycles and review progress, with field characteristics mainly consisting of names, quantities, dates, and signatures. After materials enter parsing and training tasks, they are first parsed and chunked into the database as data rows, then enter index flow, to be used for retrieval and subsequent processing to generate version ledgers and change records.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index statuses (parsed, indexing, indexed). The "version ledger and change records" are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Fields, dates, and signatures must be consistent with the patent disclosure document and software copyright materials | Check the names, quantities, dates, and signature receipts, and confirm that the current version is unique and old versions are traceable |
| Patent disclosure document | The names, quantities, and dates of the same record in the two materials must match | Compare the corresponding fields of the disclosure document and the registration form, and check for unsynchronized versions or missing signatures |
| Software copyright materials | The version number and references must be synchronized, and old versions must be traceable | After changing one piece of content, check whether the version number and references are updated in sync |
| Data row | It is in one of the three states and consistent with the interface display | Open the data row to check its status, distinguish the file record from the data row identifier, and check chunkSize, chunkSplitter, trainingType, and the rebuild scope |
Three common errors
- Symptom: The names, quantities, and dates of the same record in the two materials do not match. Cause: The achievement registration form and the patent disclosure document are maintained separately, without field-level comparison.
- Symptom: The version is not synchronized, and the old version is still referenced. Cause: After changing one piece of content, the version number and references are not triggered to update in sync.
- Symptom: Newly uploaded materials cannot be found. Cause: The data row is in parsed or indexing, and data pending indexing does not participate in recall.
How to verify the setup
Acceptance of this feature: Upload one material and observe the data row status transitions and the coverage scope of the rebuild task.
Business test: Change one piece of content and see whether the version number and references are updated in sync.
- Open the data row to check its status, and confirm that it is in one of parsed, indexing, or indexed and consistent with the interface display.
- Check the file record and the data row separately, and confirm that the identifiers of the file and the data row are distinguishable.