A method, system, equipment, and medium for pre-archiving defense documents

By generating defense event fingerprints and pre-archiving containers, the problem of cross-system archiving of graduate students' defense files in universities has been solved, realizing unique binding and automatic verification of materials, and improving the traceability and data consistency of the files.

CN123068362APending Publication Date: 2026-11-10GUILIN UNIV OF AEROSPACE TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611308980.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-27
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

The dissertation defense files of university graduate students are scattered across multiple systems, lacking automatic conversion relationships, which leads to difficulties in cross-system archiving, missing material verification, confusion of dissertation versions, separation of paper and electronic documents, and poor traceability of archives.

Method used

By generating defense event fingerprints, creating a defense pre-archiving container, achieving unique binding of materials across systems, performing field-level matching and verification, automatically identifying missing documents, version conflicts, and unbound paper and electronic documents, intercepting unqualified files in advance, and generating archived information packages for the college.

Benefits of technology

It enables unique archiving of cross-system files, automatically verifies the integrity of materials, isolates different defense processes, and improves the traceability of files and data consistency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123068362A_ABST
    Figure CN123068362A_ABST
Patent Text Reader

Abstract

This invention belongs to the field of archival management technology and relates to a method, system, device, and medium for pre-archiving defense archives. The method includes: determining whether pre-archiving triggering conditions are met; generating defense event fingerprints based on defense process instance data and creating or updating corresponding defense pre-archiving containers; generating materials M01-M06; collecting archived materials matching the defense event fingerprints; performing field-level matching on materials M01-M06 to generate material status; determining whether the container event-level status is pre-archiving qualified; if so, encapsulating all data in the defense pre-archiving container into a college-side archiving information package; otherwise, prohibiting packet encapsulation. This invention solves the problems of difficulty in cross-system archiving of defense archives, missing material verification, thesis version confusion, separation of paper and electronic documents, inability to pre-intercept unqualified archives, and poor archive traceability by using defense event fingerprints, defense pre-archiving containers, field-level matching, and container event-level status.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of archives management technology, and specifically discloses a method, system, equipment and medium for pre-archiving defense documents. Background Technology

[0002] Currently, graduate students' defense files are scattered across multiple independent platforms, including graduate management systems, OA approval systems, thesis submission systems, and paper signature page scanning interfaces. There is a lack of automatic conversion between the defense process status and the file objects. Different defense processes for the same student and the same thesis lack unique identifiers at the process instance level, easily leading to duplicate filing, incorrect filing, and omissions.

[0003] The required materials for the defense file are not standardized, making it impossible to automatically check for missing items before handover; the final version of the thesis is easily confused with the version before the defense and the version before revision; the lack of a binding verification mechanism between the paper signature page and the electronic scanned copy leads to inconsistencies between paper and electronic documents, and unqualified files entering the formal archiving stage.

[0004] While existing technologies can achieve electronic file uploading, directory management, or general integrity checks, problems still exist such as difficulties in cross-system archiving of defense files, lack of verification of missing materials, confusion of thesis versions, separation of paper and electronic documents, inability to intercept unqualified files in advance, and poor traceability of files. Summary of the Invention

[0005] The technical problems to be solved by this invention are: difficulty in cross-system archiving of defense files, lack of verification of missing materials, confusion of thesis versions, separation of paper and electronic documents, inability to intercept unqualified files in advance, and poor traceability of files.

[0006] The technical solution of the present invention to solve the above-mentioned technical problems is as follows: A method for pre-archiving defense files, comprising: Obtain sample data of the defense process from the graduate student management system; Determine whether the pre-archiving trigger condition is met. If so, start the pre-archiving process; otherwise, do not start the pre-archiving process. Generate defense event fingerprints based on the defense process instance data, and after creating or updating the corresponding defense pre-archiving container, update the container event-level state; Call the preset defense file template to generate materials M01-M06 and store them in the defense pre-archiving container; Collect archival materials that match the fingerprint of the defense event from the graduate student management system, OA approval system, thesis submission system, and signature page scanning / binding interface, and store them in the defense pre-archiving container; Based on the materials to be archived and the fingerprint of the defense event, the M01-M06 materials are matched at the field level to generate the material status and stored in the defense pre-archiving container. Update the container event-level status based on the material status, and determine whether the container event-level status is qualified for pre-archiving. If so, encapsulate all data in the defense pre-archiving container into a college-side archive information package; otherwise, prohibit encapsulation.

[0007] Furthermore, the pre-archiving trigger condition is: The defense status has changed to "defense completed" or "defense passed".

[0008] Furthermore, based on the defense process instance data, a defense event fingerprint is generated, and after creating or updating the corresponding defense pre-archiving container, the container event-level state is updated, including: The defense process instance data includes the college code, student ID, defense process instance number, and thesis number; A unique defense event fingerprint is generated using a hash algorithm based on the college code, student ID, defense process instance number, and thesis number. Create or update the corresponding defense pre-archiving container based on the defense event fingerprint, and update the container event-level state through a state machine.

[0009] Furthermore, when the same student initiates a re-defense for the same thesis, a new defense process instance number is generated, and a new defense event fingerprint and a corresponding new defense pre-archive container are generated based on the new defense process instance number.

[0010] Furthermore, based on the archived materials and the fingerprint of the defense event, field-level matching is performed on materials M01-M06 to generate material status, including: Based on the material code, defense event fingerprint, student number, defense process instance number, thesis number, file hash value, version status, and paper-electronic binding status, the materials to be archived are matched with materials M01-M06 at the field level to obtain the matching results, and the material status is generated according to the matching results.

[0011] Furthermore, field-level matching includes: For materials M01-M04, verify whether the document exists and whether the key fields are consistent with the defense event fingerprint and the defense process instance data. If they are, the material status is qualified; if the document is missing, the material status is missing; if the key fields are inconsistent with the defense event fingerprint and the defense process instance data, the material status is inconsistent. For M05 materials, verify whether the document exists and whether the version status is marked as the final version or the final submission status after the defense. If so, the material status is qualified; if the document is missing, the material status is missing; if the version status is not marked as the final version or the final submission status after the defense, the material status is version conflict. For material M06, verify whether the paper signature page number and the scanned copy number exist simultaneously and are both bound to the same defense event fingerprint. If so, the material status is qualified; otherwise, the material status is paper and electronic not bound.

[0012] Furthermore, the update rules for container event-level state include: The initial event-level state of the container is not created; After creating the corresponding defense pre-archiving container based on the defense event fingerprint, the container event-level status is updated to "created". After calling the defense file template and collecting the archived materials that match the defense event fingerprint, the container event-level status is updated to "Collecting". After field-level matching, if any material status of materials M01-M06 is abnormal (including missing parts, inconsistent fields, version conflicts, and paper / electronic not bound), the container event-level status is updated to unqualified. If abnormal status still exists after correcting the materials and re-matching the field level, the container event-level status remains unqualified. If the material status of materials M01-M06 is qualified, the container event-level status is updated to pre-archive qualified. After encapsulating all data in the defense pre-archiving container into a college-side archive information package, the container's event-level status is updated to "encapsulated".

[0013] This invention also relates to a defense file pre-archiving system for the above-mentioned defense file pre-archiving method, comprising: The defense event collection module is used to obtain instance data of the defense process from the graduate management system, and to collect archived materials that match the fingerprint of the defense event from the graduate management system, OA approval system, thesis submission system, and signature page scanning / binding interface. The defense trigger judgment module is used to determine whether the pre-archiving trigger condition is met. If it is, the pre-archiving process is started; otherwise, the pre-archiving process is not started. The defense event fingerprint generation module is used to generate defense event fingerprints based on defense process instance data. The defense pre-archive container module is used to create or update pre-archive containers and store various data. The fixed material template module is used to call the defense file template to generate materials M01-M06; The field-level matching module is used to perform field-level matching on materials M01-M06 based on the materials to be archived and the fingerprint of the defense event; The material state machine module is used to generate material states and update container event-level states; The archive information package encapsulation module is used to determine whether the container event-level status is pre-archiving qualified. If so, it encapsulates all data in the defense pre-archiving container into a college-side archive information package; otherwise, it prohibits encapsulation.

[0014] The present invention also relates to an electronic device comprising: a processor and a memory; the memory for storing executable instructions of the processor, the processor being configured to execute the aforementioned method for pre-archiving defense documents by executing the executable instructions.

[0015] The present invention also relates to a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for pre-archiving defense documents.

[0016] The beneficial effects of this invention are: This invention generates defense event fingerprints using college codes, student IDs, defense process instance IDs, and thesis IDs, achieving unique binding of materials across systems and avoiding incorrect or duplicate archiving, thus solving the problem of difficult cross-system archiving of defense files. Through a one-to-one correspondence between defense event fingerprints and pre-archiving containers, it achieves unique aggregation of materials from the same defense process instance. When the same student and the same thesis initiate a re-defense, a new defense process instance ID is generated, corresponding to a new defense event fingerprint and a new pre-archiving container, enabling independent archiving of different defense processes and isolating materials from multiple defenses. Field-level matching automatically identifies missing documents, inconsistent fields, version conflicts, and unbound paper / electronic documents, solving problems such as missing document verification, thesis version confusion, and separation of paper and electronic files. Container event-level status enables pre-interception of unqualified files, encapsulating only qualified files and intercepting unqualified files at the data level. The material_manifest, hash_set, paper_scan_binding_set, and status_log stored in the college-side archiving information package provide a unified data foundation for subsequent file reception, return, review, and accountability, improving traceability. Attached Figure Description

[0017] Figure 1 This is a flowchart of a method for pre-archiving defense documents in an embodiment of the present invention; Figure 2 This is a block diagram of a defense file pre-archiving system according to an embodiment of the present invention. Detailed Implementation

[0018] The principles and features of the present invention are described below. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0019] A method for pre-archiving defense files, such as Figure 1 As shown, it includes the following steps: S1. Obtain sample data of the defense process from the graduate student management system; The defense process instance data includes the college code, student ID, defense process instance number, thesis number, defense status, and defense completion time.

[0020] S2. Determine whether the pre-archiving trigger condition is met. If yes, start the pre-archiving process; otherwise, do not start the pre-archiving process. The defense status includes pending defense, defense incomplete, defense completed, and defense passed.

[0021] The pre-archiving trigger condition is: the defense status changes to defense completed or defense passed.

[0022] By monitoring the defense status in real time, when the defense status changes from defense incomplete to defense completed or defense passed, it is determined that the pre-archiving trigger condition is met, and the pre-archiving process is started.

[0023] S3. Generate defense event fingerprints based on the defense process instance data, and after creating or updating the corresponding defense pre-archiving container, update the container event-level status. A unique defense event fingerprint is generated using a hash algorithm based on the college code, student ID, defense process instance number, and thesis number. Create or update the corresponding defense pre-archiving container based on the defense event fingerprint, and update the container event-level state through a state machine.

[0024] When the same student initiates a re-defense of the same thesis, the system will generate a new defense process instance number. Based on the new defense process instance number, a new defense event fingerprint and a new defense pre-archive container will be generated to prevent confusion with the materials of the first defense. This will enable independent archiving of different defense processes and isolate the materials of multiple defenses from each other.

[0025] The defense event fingerprint F1 is used as a unique event-level identifier for cross-system material binding and distinguishing multiple defenses.

[0026] The defense pre-archiving container C1 is used to hold materials, status, status logs and package data of M01-M06 under the same defense process instance number; the status includes version status, paper-electronic binding status, material status and container event level status.

[0027] Hash algorithms include SHA-256, SM3, etc.

[0028] This invention uses the defense event fingerprint F1 generated by the college code, student number, defense process instance number, and thesis number to achieve unique binding of materials across systems, thus avoiding incorrect archiving and duplicate archiving.

[0029] S4. Call the preset defense file template, generate materials M01-M06, and save them into the defense pre-archiving container; Materials M01-M06 are as follows: Defense Application Form M01, List of Defense Experts M02, Defense Record Form M03, Voting Results or Review Opinions M04, Final Thesis Version M05, and Paper Signature Page (Paper-Electronic Binding Item) M06.

[0030] The defense file template T1 is used to define the materials that should be archived in M01-M06, as well as the source field and matching field for each material.

[0031] M05 materials can be obtained from the final submission module of the thesis submission system or the final thesis confirmation module of the graduate management system.

[0032] S5. Collect the materials that should be archived and match the fingerprint of the defense event from the graduate management system, OA approval system, thesis submission system, and signature page scanning / binding interface, and store them in the defense pre-archiving container. Materials to be archived include documents, paper signature pages with numbers, and scanned copies with numbers.

[0033] The paper signature page number can be a QR code, barcode, RFID tag, or a system-generated number.

[0034] S6. Based on the materials to be archived and the fingerprint of the defense event, perform field-level matching on materials M01-M06 to generate material status and store it in the defense pre-archiving container. Based on the material code, defense event fingerprint, student ID, defense process instance ID, thesis ID, file hash value, version status, and paper / electronic binding status, the materials to be archived are matched against materials M01-M06 at the field level to obtain matching results. The material status is then generated based on the matching results, specifically including: For materials M01-M04, verify whether the file exists and whether the key fields are consistent with the defense event fingerprint and the defense process instance data. If they are consistent, the material status is qualified; if the file is missing, the material status is missing; if the key fields are inconsistent with the defense event fingerprint and the defense process instance data, the material status is inconsistent, and write it to the status log. For M05 materials, verify whether the document exists and whether the version status is marked as the final version or the final submission status after the defense. If so, the material status is qualified; if the document is missing, the material status is missing; if the version status is not marked as the final version or the final submission status after the defense, the material status is version conflict. For material M06, verify whether the paper signature page number and the scanned copy number exist simultaneously and are both bound to the same defense event fingerprint. If so, the material status is qualified; otherwise, the material status is paper and electronic not bound.

[0035] For example, if the student ID on the M01 defense application form in the OA approval system does not match the student ID corresponding to F1 in the graduate management system, the system will set the material status of the M01 material to "field mismatch". After verification, the correct M01 material is re-uploaded, and the system will re-execute field-level matching. If the student ID, defense process instance number, and material code all match, the material status of the M01 material will be restored to "qualified", thus restoring the material status after a matching failure.

[0036] This invention automatically identifies missing parts, inconsistent fields, version conflicts, and unbound paper and electronic documents by field-level matching, thereby solving the problems of missing material verification, mixed paper versions, and disconnected paper and electronic documents.

[0037] Among them, the material code is used to match items one by one and generate material states.

[0038] The file hash value (file_hash) is used to identify file consistency and prevent files with the same name or renamed files from being mixed in.

[0039] The version status (version_status) is used to determine whether M05 is the final paper version.

[0040] The paper-electronic binding status (binding_status) is used to determine whether the M06 paper signature page number and the scanned document number are bound to the same defense event fingerprint.

[0041] The material_status field indicates whether the material has not been collected, is missing, has inconsistent fields, has a version conflict, is not bound to paper or electronic documents, or is qualified.

[0042] S7. Update the container event-level status according to the material status, and determine whether the container event-level status is qualified for pre-archiving. If so, encapsulate all data in the defense pre-archiving container into a college-side archive information package; otherwise, prohibit encapsulation.

[0043] The container event-level status is updated based on the material status, including: if any material status of materials M01-M06 is missing, inconsistent fields, version conflict, or paper / electronic not bound, the container event-level status is updated to unqualified; if the material status of materials M01-M06 is qualified, the container event-level status is updated to pre-archive qualified.

[0044] The files, metadata, defense event fingerprints, hash values, paper-to-electronic binding status, and status logs within the pre-archiving container for the defense are encapsulated into a college-side archiving information package, which is then assigned a package number and the encapsulation time is recorded. The package number, package_id, is used to uniquely identify a single encapsulated college-side archiving information package. The college-side archiving information package can use ZIP, OFD / PDF with XML metadata, or a data package format recognized by the school's archive system.

[0045] For example, if the thesis submission system contains multiple files without a final version label, and the material status of material M05 is "version conflict," then the container event level status is "unqualified," and the system prohibits packet sealing, thus achieving final thesis version conflict interception. If material M06 is only an uploaded scanned copy without the paper signature page number entered, and its material status is "paper and electronic not bound," then the container event level status is "unqualified," and the system prohibits packet sealing, thus achieving paper and electronic not bound interception.

[0046] This invention achieves pre-interception of unqualified files through container event-level states, encapsulating only qualified files and intercepting unqualified files at the data level.

[0047] Container event-level states include not created, created, collecting, not qualified, pre-archiving qualified, and packaged.

[0048] The rules for updating container event-level state include: The initial container event-level state is "not created"; after the corresponding defense pre-archiving container is created based on the defense event fingerprint, the container event-level state is updated to "created". After calling the defense file template and collecting the archived materials that match the defense event fingerprint, the container event-level status is updated to "Collecting". After field-level matching, if any material status of materials M01-M06 is missing, inconsistent fields, version conflict, or paper and electronic not bound (i.e., abnormal status), the container event-level status is updated to unqualified. If the abnormal status still exists after correcting the materials and re-matching the field level, the container event-level status remains unqualified. If the material status of materials M01-M06 is qualified, the container event-level status is updated to pre-archive qualified. After encapsulating all data in the defense pre-archiving container into a college-side archive information package, the container's event-level status is updated to "encapsulated".

[0049] For example: After C1 is created, the material status of materials M01-M06 is all "uncollected"; after collecting materials M01-M04, their material status is set to "qualified"; if two versions of the thesis file are found during the collection of material M05 and neither is marked as the final version, the material status of material M05 is set to "version conflict," the container event level status is set to "unqualified," and packetization is prohibited. After the materials are corrected, after the administrator confirms the defense and finally submits the file in the thesis submission system, the system recalculates the file hash value and sets the material status of material M05 to "qualified"; subsequently, if the material status of material M06 is also qualified, the container event level status is set to "pre-archiving qualified."

[0050] The archived information package on the college side includes multiple data objects, as shown in Table 1: This invention improves traceability by using the material_manifest, hash_set, paper_scan_binding_set, and status_log stored in the archived information package at the college level to provide a unified data foundation for subsequent file reception, return, review, and accountability.

[0051] This invention also relates to a pre-archiving method for defense files, used in the aforementioned pre-archiving method for defense files, such as... Figure 2 As shown, it includes: The defense event collection module is used to obtain instance data of the defense process from the graduate management system, and to collect archived materials that match the fingerprint of the defense event from the graduate management system, OA approval system, thesis submission system, and signature page scanning / binding interface. The defense trigger judgment module is used to determine whether the pre-archiving trigger condition is met. If it is, the pre-archiving process is started; otherwise, the pre-archiving process is not started. The defense event fingerprint generation module is used to generate defense event fingerprints based on defense process instance data. The defense pre-archive container module is used to create or update pre-archive containers and store various data. The fixed material template module is used to call the defense file template to generate materials M01-M06; The field-level matching module is used to perform field-level matching on materials M01-M06 based on the materials to be archived and the fingerprint of the defense event; The material state machine module is used to generate material states and update container event-level states; Material status (material_status) includes not collected, missing parts, inconsistent fields, version conflict, paper / electronic not bound, qualified, etc.; container event-level status (C1_status) includes not created, created, collecting, unqualified, pre-archiving qualified, and packaged, used to manage archive package packaging permissions.

[0052] The archive information package encapsulation module is used to determine whether the container event-level status is pre-archiving qualified. If so, it encapsulates all data in the defense pre-archiving container into a college-side archive information package; otherwise, it prohibits encapsulation.

[0053] The present invention also relates to an electronic device comprising: a processor and a memory; the memory for storing executable instructions of the processor, the processor being configured to execute the aforementioned method for pre-archiving defense documents by executing the executable instructions.

[0054] The present invention also relates to a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for pre-archiving defense documents.

[0055] Example 1 In the graduate student management system of a certain college, the defense process instance number of a student's first defense is DFI2026-001, and the thesis number is TH2026-001. When the defense status changes from pending defense to defense passed, the pre-archiving process is initiated.

[0056] Based on the collected college code, student number, DFI2026-001, and TH2026-001, a defense event fingerprint F1 is generated using a hash algorithm, and a defense pre-archiving container C1 corresponding to F1 is created.

[0057] The defense file template T1 is called to generate materials M01-M06, and materials that should be archived are collected across multiple systems and matched with the fingerprint of the defense event.

[0058] Material M05 represents the final submission status after the defense. For material M06, the paper signature page number P001 and the scanned copy number S001 are both bound to the same F1. The material status of materials M01-M06 is all qualified. The container event level status C1 is pre-archiving qualified. All data in the defense pre-archiving container will be encapsulated into a college-side archiving information package.

[0059] When a student initiates a re-defense of the same thesis, the system generates a new defense process instance number DFI2026-002. Based on the original college code, student number, thesis number, and the new defense process instance number, a new defense event fingerprint and a corresponding new defense pre-archiving container are generated to avoid confusion with the initial defense materials and to achieve independent archiving of different defense processes.

[0060] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for pre-archiving defense files, characterized in that, include: Obtain sample data of the defense process from the graduate student management system; Determine whether the pre-archiving trigger condition is met. If so, start the pre-archiving process; otherwise, do not start the pre-archiving process. Generate defense event fingerprints based on the defense process instance data, and after creating or updating the corresponding defense pre-archiving container, update the container event-level state; Call the preset defense file template to generate materials M01-M06 and store them in the defense pre-archiving container; Collect archival materials that match the fingerprint of the defense event from the graduate student management system, OA approval system, thesis submission system, and signature page scanning / binding interface, and store them in the defense pre-archiving container; Based on the materials to be archived and the fingerprint of the defense event, the M01-M06 materials are matched at the field level to generate the material status and stored in the defense pre-archiving container. Update the container event-level status based on the material status, and determine whether the container event-level status is qualified for pre-archiving. If so, encapsulate all data in the defense pre-archiving container into a college-side archive information package; otherwise, prohibit encapsulation.

2. The method for pre-archiving defense files according to claim 1, characterized in that, The pre-archiving trigger condition is: The defense status has changed to "defense completed" or "defense passed".

3. The method for pre-archiving defense files according to claim 1, characterized in that, The step of generating defense event fingerprints based on defense process instance data, and creating or updating the corresponding defense pre-archiving container and then updating the container event-level state includes: The defense process instance data includes the college code, student ID, defense process instance number, and thesis number; A unique defense event fingerprint is generated using a hash algorithm based on the college code, student ID, defense process instance number, and thesis number. Create or update the corresponding defense pre-archiving container based on the defense event fingerprint, and update the container event-level state through a state machine.

4. The method for pre-archiving defense files according to claim 3, characterized in that... : When the same student initiates a re-defense for the same thesis, a new defense process instance number is generated, and a new defense event fingerprint and a corresponding new defense pre-archive container are generated based on the new defense process instance number.

5. The method for pre-archiving defense files according to claim 1, characterized in that, The process of generating material status by performing field-level matching on materials M01-M06 based on archived materials and defense event fingerprints includes: Based on the material code, defense event fingerprint, student number, defense process instance number, thesis number, file hash value, version status, and paper-electronic binding status, the materials to be archived are matched with materials M01-M06 at the field level to obtain the matching results, and the material status is generated according to the matching results.

6. The method for pre-archiving defense files according to claim 5, characterized in that, Field-level matching includes: For materials M01-M04, verify whether the document exists and whether the key fields are consistent with the defense event fingerprint and the defense process instance data. If they are, the material status is qualified; if the document is missing, the material status is missing; if the key fields are inconsistent with the defense event fingerprint and the defense process instance data, the material status is inconsistent. For M05 materials, verify whether the document exists and whether the version status is marked as the final version or the final submission status after the defense. If so, the material status is qualified; if the document is missing, the material status is missing; if the version status is not marked as the final version or the final submission status after the defense, the material status is version conflict. For material M06, verify whether the paper signature page number and the scanned copy number exist simultaneously and are both bound to the same defense event fingerprint. If so, the material status is qualified; otherwise, the material status is paper and electronic not bound.

7. The method for pre-archiving defense files according to claim 1, characterized in that, The rules for updating container event-level state include: The initial event-level state of the container is not created; After creating the corresponding defense pre-archiving container based on the defense event fingerprint, the container event-level status is updated to "created". After calling the defense file template and collecting the archived materials that match the defense event fingerprint, the container event-level status is updated to "Collecting". After field-level matching, if any material status of materials M01-M06 is abnormal (including missing parts, inconsistent fields, version conflicts, and paper / electronic not bound), the container event-level status is updated to unqualified. If abnormal status still exists after correcting the materials and re-matching the field level, the container event-level status remains unqualified. If the material status of materials M01-M06 is qualified, the container event-level status is updated to pre-archive qualified. After encapsulating all data in the defense pre-archiving container into a college-side archive information package, the container's event-level status is updated to "encapsulated".

8. A pre-archiving system for defense files, characterized in that, A method for pre-archiving defense documents according to any one of claims 1-7 includes: The defense event collection module is used to obtain instance data of the defense process from the graduate management system, and to collect archived materials that match the fingerprint of the defense event from the graduate management system, OA approval system, thesis submission system, and signature page scanning / binding interface. The defense trigger judgment module is used to determine whether the pre-archiving trigger condition is met. If it is, the pre-archiving process is started; otherwise, the pre-archiving process is not started. The defense event fingerprint generation module is used to generate defense event fingerprints based on defense process instance data. The defense pre-archive container module is used to create or update pre-archive containers and store various data. The fixed material template module is used to call the defense file template to generate materials M01-M06; The field-level matching module is used to perform field-level matching on materials M01-M06 based on the materials to be archived and the fingerprint of the defense event; The material state machine module is used to generate material states and update container event-level states; The archive information package encapsulation module is used to determine whether the container event-level status is pre-archiving qualified. If so, it encapsulates all data in the defense pre-archiving container into a college-side archive information package; otherwise, it prohibits encapsulation.

9. An electronic device, characterized in that, include: Processor and memory; The memory is used to store executable instructions of the processor, which is configured to execute a pre-archiving method for defense documents according to any one of claims 1-7 by executing the executable instructions.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements a method for pre-archiving defense documents according to any one of claims 1-7.