What this category's data looks like
This page addresses research achievement registration and intellectual property management scenarios, involving three types of materials: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration forms provide the achievement name, contributors, date, and signature/seal; patent disclosure documents carry the technical solution, terminology definitions, and inventor signatures; software copyright materials include source code descriptions, version numbers, and receipts. Material sources are scattered across different handling stages, and the update rhythm changes with registration batches and filing milestones; field characteristics manifest as names, quantities, dates, and signature fields appearing repeatedly across various forms. When materials enter the document parsing and chunking stage, each is stored as an independent file record, and after parsing is completed, visible data rows are formed for subsequent terminology extraction and comparison draft generation.
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 unified terminology glossary and comparison draft are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Fields, dates, and signatures must match those in the patent disclosure document and software copyright materials; the name, quantity, and date of the same record must not appear in two different versions | Open the data row to check whether the status is parsed, indexing, or indexed, and verify the file record and the data row separately |
| Patent disclosure document | Terminology definitions and translated names must be traceable back to the original text; inventor signatures and receipts must be complete; version numbers must be synchronized with the registration batch | Check the data rows covered by the training task, and confirm that reconstruction only lands on data with completed indexing |
| Software copyright materials | The version number, date, and signature fields in the source code description must be consistent with the achievement registration form; missing signatures or receipts are considered unsynchronized | View the chunking and training records corresponding to chunkSize, chunkSplitter, and trainingType |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across two materials. Cause: Each type of form is filled in separately, without terminology unification and field comparison.
- Symptom: The version is not synchronized; the version numbers referenced in the registration form and the disclosure document differ. Cause: Materials are uploaded in batches, and old versions are not marked with replacement relationships.
- Symptom: Signatures or receipts are missing, yet the materials still enter the parsing process. Cause: Signature fields are not included in the pre-parsing check, and the issue is only discovered after being stored in the database.
How to verify the setup
This feature's acceptance: upload one material and observe the data row status transitions and the coverage scope of the reconstruction task.
Business test: sample three terms and check whether their usage is consistent throughout the entire document.
- Open the data row to check whether the status is parsed, indexing, or indexed, and confirm that the interface display is consistent with the backend.
- Verify the file record and the data row separately, and confirm that the identifiers of the file and the data row are distinguishable.