File management method, electronic device, and storage medium

Abstract

The application discloses a file management method, an electronic device and a storage medium, and belongs to the technical field of digital management. The file management method comprises the following steps: in response to a creation operation of a first file of a specified type, a file editing interface is provided, and the file editing interface comprises a plurality of editable fields; in response to an editing trigger operation on a target field in the editable field, the input type of the target field is determined; in the case that the input type is a standardized input type, a plurality of candidate standardized data associated with the target field are obtained and displayed; and in response to a selection operation on target data in the plurality of candidate standardized data, the target data is filled into the target field to obtain the first file. The application ensures the consistency and standardization of the names of the files.

Description

Technical Field

[0001] This application relates to the field of digital management technology, specifically to a document management method, electronic device, and storage medium. Background Technology

[0002] In today's rapidly developing digital management landscape, documents (such as system documents, technical documents, and management systems) serve as the core basis for enterprise operations, quality control, and compliance management. Their consistency and standardization directly affect the operational quality and market competitiveness of enterprises.

[0003] Currently, companies typically generate documents through offline editing and uploading or online editing. However, due to inconsistencies in the definition of the same name among different departments and business systems within a company, problems such as ambiguity and difficulty in data integration arise when documents are transferred across departments. Summary of the Invention

[0004] This application provides a file management method, electronic device, and storage medium that ensure the consistency and standardization of file names.

[0005] Firstly, a file management method is provided, including the following steps: In response to a file creation operation on a first file of a specified type, a file editing interface is provided, the file editing interface containing several editable fields; In response to an edit-triggered operation on a target field in the editable fields, the input type of the target field is determined; If the input type is a standardized input type, obtain and display multiple candidate standardized data associated with the target field; In response to the selection operation of target data among the plurality of candidate standardized data, the target data is filled into the target field to obtain the first file.

[0006] In some of these design approaches, obtaining multiple candidate standardized data associated with the target field includes: Determine the data type corresponding to the target field; Retrieve the standard dataset corresponding to the data type from the standard database; The standardized data in the standard dataset are used as multiple candidate standardized data associated with the target field.

[0007] In this way, based on the data type corresponding to the target field, the corresponding standard dataset is matched and obtained. The standardized data in the standard dataset is used as the standardized data associated with the target field, thereby achieving more accurate recommendations based on standardized data and improving the efficiency and accuracy of document editing.

[0008] In some of these design approaches, after obtaining the first file, the method further includes: Establish a reference relationship between the target data and the first file; In response to an update operation on the target data in the standard database, the content of the fields in the first file that reference the target data is updated according to the reference relationship.

[0009] In this way, all files that reference the target data can be updated in batches based on the reference relationship, thus improving the update efficiency.

[0010] In some of these design approaches, obtaining multiple candidate standardized data associated with the target field includes: Displays a list of files in the file library; In response to the selection operation of the second file in the file list, the referenceable data in the second file is used as multiple candidate standardized data associated with the target field.

[0011] This allows users to select data from the file library to fill in new files, achieving efficient and accurate reuse of file content.

[0012] In some of these design approaches, the method further includes: Based on the reference relationships between the target data and one or more files, a reference relationship graph corresponding to the target data is constructed. The reference relationship graph includes file nodes and connecting edges between file nodes. The file nodes include start nodes and referencing nodes. The start node corresponds to the origin file of the target data, and each referencing node corresponds to a file that references the target data. The connecting edges between the file nodes are used to indicate the reference relationships between files.

[0013] In this way, after a reference occurs, a reference relationship graph is constructed, which can continuously record and display which files reference the data and how the reference path extends, realizing the transformation of file relationship management from implicit and scattered to explicit and centralized.

[0014] In some design approaches, after constructing the reference relationship graph corresponding to the target data, the method further includes: In response to an update operation on the target data in any file, the origin file defining the target data is located based on the reference relationship graph corresponding to the target data; Update the target data in the source file; Based on the reference relationship graph, the updated target data will be synchronized to the files corresponding to all reference nodes in the reference relationship graph.

[0015] In this way, when data in any file is updated, the source file can be located and modified, and the changes can be synchronized to all files in the reference graph that reference that data, thus achieving automated updates without the need for manual searching and modification, improving the efficiency and reliability of file content synchronization.

[0016] In some of these design approaches, the method further includes: In response to a save operation on the first file, identify the target version of the first file; If the target version is version i, obtain the (i-1)th version file corresponding to the first file, where i is a natural number greater than 1; Compare the first file and the (i-1)th version file to generate change information; Based on the change information, a change history corresponding to the first file is generated.

[0017] In this way, when saving a file, the differences in content between adjacent versions of the text are compared, change information is automatically generated, and a change history is formed to provide a clear file revision history, making it easy to quickly understand the specific content of each modification and improving the transparency of file management.

[0018] In some of these design approaches, the method further includes: The first file is calibrated; If the calibration is successful, the reviewer corresponding to the first file is determined based on the file attributes of the first file, and the review process is initiated. If the review is approved, the distribution scope of the first document is determined based on the document attributes, and the document release process is executed.

[0019] In this way, document quality is ensured through calibration; reviewers and review paths are automatically determined based on document attributes, ensuring compliance during document review; and the distribution scope is determined and release is executed based on document attributes, ensuring the accuracy of document distribution. This guarantees that documents can efficiently and systematically complete the transformation from editing to review to effectiveness, improving the efficiency and controllability of document management.

[0020] Secondly, a file management device is also provided, the device comprising: A module is provided to provide a file editing interface in response to a file creation operation on a first file of a specified type, the file editing interface including several editable fields defined in the target file template; A determination module is used to determine the input type of the target field in response to an edit trigger operation on the target field in the editable field; The acquisition module is used to acquire and display multiple candidate standardized data associated with the target field when the input type is a standardized input type. A module is created to fill the target data into the target field in response to the selection operation of target data among the plurality of candidate standardized data, thereby obtaining the first file.

[0021] Thirdly, embodiments of this application also provide an electronic device, including a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of any of the file management methods provided in embodiments of this application.

[0022] Fourthly, embodiments of this application also provide a computer-readable storage medium including a computer program, which, when run on an electronic device, causes the electronic device to perform the steps of any of the file management methods provided in embodiments of this application.

[0023] Fifthly, embodiments of this application also provide a computer program product, including a computer program stored in a computer-readable storage medium; when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, causing the electronic device to perform the steps of any of the file management methods provided in embodiments of this application.

[0024] Beneficial effects: In this embodiment of the application, when a user edits a target field in the file editing interface, the input type of the target field is first determined. If the input type is a standardized input type, multiple candidate standardized data associated with the target field are obtained and displayed, and the selected target data is filled into the target field. Thus, for fields with standardized input types, the target data can only be selected from the candidate standardized data, and the user cannot input the data themselves, ensuring the consistency and standardization of names between files. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is a flowchart illustrating the document management methods provided by existing technologies; Figure 2 This is a schematic diagram illustrating an implementation scenario of the file management method provided in this application embodiment; Figure 3 This is a flowchart illustrating the file management method provided in the embodiments of this application; Figure 4 This is a schematic diagram of the architecture of the file management platform provided in the embodiments of this application; Figure 5 This is a schematic diagram of the file management system provided in the embodiments of this application; Figure 6 This is another flowchart illustrating the file management method provided in the embodiments of this application; Figure 7 This is a schematic diagram of the structure of the file management device provided in the embodiments of this application; Figure 8 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0027] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0028] In the description of this application, it should be understood that the orientations or positional relationships indicated by the names "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer" are based on the orientations or positional relationships shown in the accompanying drawings and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Furthermore, the names "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0029] "A and / or B" includes the following three combinations: A only, B only, and a combination of A and B.

[0030] The use of "applies to" or "configured to" in this application implies open and inclusive language, which does not exclude the applicability to or configuration to devices performing additional tasks or steps. Additionally, the use of "based on" implies openness and inclusivity, because processes, steps, calculations, or other actions "based on" one or more of the stated conditions or values ​​may in practice be based on additional conditions or values ​​beyond those stated.

[0031] In this application, the term "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be made without using these specific details. In other instances, well-known structures and processes are not described in detail to avoid obscuring the description of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0032] In today's rapidly developing digital management landscape, documents (such as system documents, technical documents, and management systems) serve as the core basis for enterprise operations, quality control, and compliance management. Their consistency and standardization directly affect the operational quality and market competitiveness of enterprises.

[0033] Currently, corporate documents are typically processed through offline editing and online approval, resulting in issues such as version inconsistencies, lack of standardized procedures, and low efficiency in cross-departmental collaboration. While departmental platforms support online editing (e.g., basic editing functions), the lack of a unified underlying standard database for management leads to inconsistent file names. Because documents are maintained by different personnel, file format templates and content updates cannot be synchronized. Regarding document standardization, there are also issues with publishing permissions and review processes. Document distribution to executors also relies on manual maintenance, leading to inaccurate and untimely publication. The lack of integrated AI-assisted tools results in low document reuse rates and time-consuming retrieval.

[0034] like Figure 1 The diagram shown is a flowchart of a file management method provided by existing technology. The process includes: First, templates are created and published in OA (Office Automation). Users download templates from the published templates and edit them. After editing, the files are sent to the relevant personnel for format and content review. Once approved, the files are published in OA and distributed to the document management platform or enterprise document library. Then, paper documents are managed in a document-based system. Finally, during application, the consistency between the actual application content and the documents is reviewed to perform a quality audit.

[0035] Figure 1 In the diagram, the steps indicated by the dashed lines represent limited / low-value work, non-closed-loop processes that are prone to errors.

[0036] Specifically, in the above process, the editing operation mainly relies on the standard documents or experience known to the user. For example, when editing a work instruction, when it is necessary to fill in the product model, equipment name, technical parameters or standard terms, the user inputs them based on personal memory or experience, without the constraints and prompts of the standard database. This can easily lead to inconsistencies in the naming or numerical description of the same thing in different documents. If the document being edited needs to reference certain clauses or data in existing documents, the user needs to manually find the relevant documents and manually copy and paste the content. This method cannot establish a traceable reference relationship between documents, and when the referenced source document is updated later, the current document cannot automatically detect and synchronize. The file format and style (e.g., heading level, numbering rules) are entirely dependent on the user to set manually.

[0037] During the notification process, it is usually visible to all personnel with access to the file management platform or file library, and it is impossible to accurately distribute the notification to specific users or terminals based on the file content attributes (e.g., applicable positions, product lines).

[0038] If this file references content from other files, or if it is referenced by other files subsequently, when this file is republished as a revised version, all related files need to be manually searched and their references manually updated. This process is tedious and prone to omissions, leading to version inconsistencies and content conflicts between files.

[0039] The update status of files on the file management platform or file library cannot be automatically and in real time synchronized to downstream business execution systems or job terminals. This often requires additional manual notification or secondary data entry, resulting in information transmission delays.

[0040] After a file is published, it can only be searched by keywords, resulting in low search efficiency.

[0041] To address the aforementioned issues, this application provides a file management method. When a user edits a target field in a file editing interface, the input type of the target field is first determined. If the input type is a standardized input type, multiple candidate standardized data associated with the target field are obtained and displayed. The selected target data is then filled into the target field. Thus, for fields with standardized input types, target data can only be selected from the candidate standardized data, and user input is not allowed, ensuring the consistency and standardization of file names.

[0042] This application provides a file management method, a file management device, an electronic device, and a storage medium. The file management device can be integrated into an electronic device, which can be a server, a terminal, or other similar device.

[0043] The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network (CDN) acceleration services, and big data and artificial intelligence platforms. The terminal can include, but is not limited to, mobile phones, computers, smart voice interaction devices, smart home appliances, vehicle terminals, and aircraft. The terminal and server can be directly or indirectly connected via wired or wireless communication, which is not limited herein.

[0044] Taking the integration of file management devices into electronic devices as an example, such as Figure 2 The diagram shown is a schematic representation of an implementation scenario of the file management method provided in this application. The electronic device can be a server or a terminal. In response to a file creation operation on a first file of a specified type, the electronic device provides a file editing interface containing several editable fields. In response to an editing trigger operation on a target field among the editable fields, the input type of the target field is determined. If the input type is a standardized input type, multiple candidate standardized data associated with the target field are acquired and displayed. In response to a selection operation on the target data among the multiple candidate standardized data, the target data is filled into the target field to obtain the first file.

[0045] It should be noted that, Figure 2The illustrated scenario of the file management method is merely an example. The implementation environment of the file management method described in this application is intended to more clearly illustrate the technical solutions of this application and does not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will recognize that, with the evolution of data processing and the emergence of new business scenarios, the technical solutions provided in this application are equally applicable to similar technical problems.

[0046] The solutions provided in this application are specifically illustrated through the following embodiments. It should be noted that the order of description of the following embodiments is not intended to limit the preferred order of the embodiments.

[0047] This embodiment will be described from the perspective of a file management device, which can be integrated into an electronic device, such as a server or a terminal, and this application does not impose any restrictions on it.

[0048] like Figure 3 The diagram shown is a flowchart of a file management method provided in an embodiment of this application. The file management method includes steps S31-S35: S31. In response to a file creation operation on a first file of a specified type, a file editing interface is provided, wherein the file editing interface contains several editable fields.

[0049] Specifically, the file creation operation can be triggered by the user through a graphical user interface, such as clicking the "New" button on a file management platform (a file management platform refers to an integrated software system used to realize the creation, review, publication, storage, updating, retrieval, and full lifecycle management of files; in this application, it can be a software environment or application that supports the operation of file management methods), selecting the file type option in the menu, or initiating it via voice command. The first file of the specified type can be a system document (e.g., operation manual, control plan, etc.), a contract, report, application form, invoice, or other document type with structured content.

[0050] In some embodiments, in response to a file creation operation on a first file of a specified type, a file editing interface is provided, the file editing interface including several editable fields, including: in response to a file creation operation on a first file of a specified type, displaying candidate file templates corresponding to the specified type; in response to a selection operation on a target file template among the candidate file templates, providing a file editing interface based on the target file template, the file editing interface including several editable fields defined in the target file template.

[0051] Specifically, after detecting a file creation operation on a first file of a specified type, one or more candidate file templates associated with it are selected from the template library and displayed on the interface in the form of a list, thumbnails, or cards. The candidate file templates are pre-categorized and stored according to file type, and each template defines the basic structure, fixed content, and editable areas of that type of file.

[0052] Users select one of the candidate file templates from the displayed options by clicking, touching, or dragging. The file management platform loads the corresponding file editing interface based on the selected target file template. In addition to displaying the fixed text, formatting, charts, and other non-editable content in the template, this editing interface also highlights one or more editable fields. These editable fields are pre-marked as areas to be filled in the target file template, such as text boxes, drop-down selection boxes, date pickers, or attachment upload areas. Each field can be associated with a field name, input prompts, or formatting requirements.

[0053] S32. In response to an edit trigger operation on the target field in the editable field, determine the input type of the target field.

[0054] Specifically, the editing trigger operation includes the user clicking or touching a target field in the editable field. The file management platform identifies the target field's predefined input type in the target file template. This input type includes standardized input types and non-standardized input types. Standardized input types indicate that the field content should be selected from a predefined standard database, such as equipment name, national standard classification code, unit of measurement, and normative terminology. Non-standardized input types indicate that the field content allows the user to freely input text, numbers, or mixed content. The input type definition information is stored in the template configuration data and associated with the field identifier.

[0055] S33. If the input type is a standardized input type, obtain and display multiple candidate standardized data associated with the target field.

[0056] Specifically, when the file management platform determines that the input type of the target field is a standardized input type, it recognizes that the target field requires content that conforms to a specific format and specification, rather than arbitrary text. The file management platform initiates a standardized data acquisition process, providing the target field with a set of structured candidate standardized data items that meet preset requirements. The candidate standardized data can have its content, format, or value predefined within one or more controlled datasets to ensure data consistency and accuracy. Based on the target field's identifier, associated data type, or its semantics within the file context, the file management platform executes query or matching logic to identify multiple associated candidate standardized data. After acquiring the candidate standardized data, the file management platform displays these options to the user through a user interface (e.g., drop-down menus, selection panels, floating lists, etc.) for the user to view and select from, thereby completing the standardized filling of the target field.

[0057] S34. In response to the selection operation of target data among the plurality of candidate standardized data, the target data is filled into the target field to obtain the first file.

[0058] Specifically, the user selects one of several candidate standardized data as the target data from the displayed options. Selection methods include clicking the option, selecting and confirming via keyboard, or voice selection. Upon receiving this selection, the file management platform automatically fills the target data into the input area corresponding to the target field and displays it according to the format defined in the target file template. After all editable fields are filled in, the file management platform generates a first file based on the target file template structure and the filled content. This first file can be saved, exported, or used in subsequent processing flows.

[0059] In some embodiments, obtaining multiple standardized data associated with the target field from a standard database includes steps S3311-S3313: S3311. Determine the data type corresponding to the target field.

[0060] Specifically, after detecting an edit trigger operation on a target field, the file management platform parses the configuration file or metadata of the target file template to obtain the field identifier or field attribute definition of the target field. Based on preset field type mapping rules, it maps this field identifier or attribute to a specific data type, such as "equipment name," "national standard code," "date," "unit of measurement," "product model," or "administrative division name." This data type is used to precisely describe the content scope and format specifications required by the target field.

[0061] S3312. Obtain the standard dataset corresponding to the data type from the standard database.

[0062] Specifically, the file management platform generates query instructions based on the determined data type and initiates a query to the standard database. The standard database stores standardized data sets corresponding to various fields; for example, it stores terminology sets, name sets, national standard code sets, unit of measurement sets, and numerical sets. The query carries field identifiers, file types, or contextual information to obtain multiple standardized data options associated with the semantics or purpose of that field. The file management platform displays the obtained standardized data in the file editing interface in the form of drop-down lists, pop-up panels, or auto-completion suggestions for users to browse and select from.

[0063] S3313. The standardized data in the standard dataset are used as multiple candidate standardized data associated with the target field.

[0064] Specifically, the file management platform receives a standard dataset returned by a standard database. This dataset typically contains multiple records or data items that conform to the defined data type and have a uniform format. The file management platform directly uses all data items in this dataset, or a subset of data after preliminary filtering based on the current file context (e.g., other related fields that have already been filled in), as multiple candidate standardized data options for the user to select and fill in for the target field. This standardized data exists in a normalized and structured form, ensuring that its content is accurate and conforms to business or industry standards, thereby guaranteeing standardized input for the target field.

[0065] In some embodiments, after obtaining the first file, the method further includes steps S3501-S3502: S3501. Establish a reference relationship between the target data and the first file.

[0066] Specifically, after the target data is filled into the target fields and the first file is created, the file management platform generates and stores a reference relationship record. This record includes at least the unique identifier of the target data in the standard database (e.g., data ID, version number, or key value), the first file identifier, and the location information of the fields in the first file that reference the target data (e.g., field identifier, field path). This reference relationship can be stored in a reference relationship table, the file's metadata block, or a dedicated index file. By establishing this reference relationship, the file management platform can trace the data source of specific content in the first file.

[0067] S3502. In response to the update operation of the target data in the standard database, update the content of the field in the first file that references the target data according to the reference relationship.

[0068] Specifically, when target data in the standard database is updated due to rule changes, information corrections, or version upgrades, the file management platform will detect the update event. The file management platform will then automatically query all files that reference the data before the update based on pre-stored reference relationship records, and locate the specific field in the specific file.

[0069] Then, the file management platform replaces the old data content of the corresponding fields in all referenced files (including the first file) with the updated target data obtained from the standard database, thereby achieving synchronous updates of the file content. This update process can be completed automatically in the background, or prompted and executed when the user opens the file again, ensuring that the file content remains consistent with the data in the standard database.

[0070] In some embodiments, obtaining multiple candidate standardized data associated with the target field includes steps S3321-S3322: S3321. Display the list of files in the file library.

[0071] Specifically, after determining that the input type of the target field is a standardized input type, the file management platform can initiate a process to retrieve candidate standardized data from existing files. The platform accesses and queries the file library, filtering files according to preset rules (e.g., similar type to the first file, related to the first file (e.g., belonging to the same product), containing specific keywords, or belonging to the same business domain), generating a relevant set of existing files. Subsequently, the platform displays the file list to the user in the file editing interface via a sidebar, pop-up window, or independent panel. This file list can include information such as the file name, identifier, brief description, and last modified time, and allows users to quickly locate the desired file by entering keywords in the search box or using filter conditions.

[0072] Understandably, files in the file library can be files that have already been reviewed and published, or files that users have just created. For example, a user may create multiple files at once, and the later-created file can reference the content of the earlier-created file.

[0073] S3322. In response to the selection operation of the second file in the file list, the referenceable data in the second file is used as multiple candidate standardized data associated with the target field.

[0074] Specifically, when a user selects an existing file as a second file from the displayed file list by clicking or checking a box, the file management platform responds to this selection by parsing the content of the second file, identifying and extracting data items that conform to preset standardized specifications. These data items constitute the referenceable data of the second file. Specifically, referenceable data can include: standardized data selected and entered from a standard database when creating or editing the second file; or, although user-defined input, structured data that has been confirmed as valid and marked as referenceable after subsequent calibration and review processes. The file management platform presents this extracted referenceable data as multiple candidate standardized data associated with the currently edited target field, in the form of drop-down lists or selection panels, for the user to choose from and enter into the target field. This approach not only achieves efficient and accurate reuse of file content but also ensures consistency and coherence in data expression between newly created and historical files.

[0075] In some embodiments, the method further includes: Based on the reference relationships between the target data and one or more files, a reference relationship graph corresponding to the target data is constructed. The reference relationship graph includes file nodes and connecting edges between file nodes. The file nodes include start nodes and referencing nodes. The start node corresponds to the origin file of the target data, and each referencing node corresponds to a file that references the target data. The connecting edges between the file nodes are used to indicate the reference relationships between files.

[0076] Specifically, upon detecting that target data is referenced by a new file (e.g., the first file), the file management platform triggers the construction or update process of a reference relationship graph. The platform first identifies the origin file of the target data—the file that initially defined or first entered the target data—and marks it as the starting node in the reference relationship graph. Then, the platform searches for all files that reference the target data, including the first file and other historical files that reference the same data, marking each such file as a referencing node. Next, the platform builds the reference relationship graph based on the order or logical hierarchy of references, graphically representing the paths through which data is referenced and the dependencies between files. This reference relationship graph can be stored in a structured data format (e.g., adjacency lists, graph database records), where each file node is associated with a corresponding file identifier and metadata, and each connection edge is associated with attributes of the reference relationship (e.g., reference time, reference fields, etc.). Furthermore, the reference relationship graph can support visualization, showing users the data flow and file association network.

[0077] By constructing a reference relationship graph, the file management platform achieves centralized and explicit management of data reference links, providing support for subsequent tracking, analysis, and consistency maintenance.

[0078] In some embodiments, after constructing the reference relationship graph corresponding to the target data, the method further includes steps S3511-S3513: S3511. In response to an update operation on the target data in any file, the origin file defining the target data is located based on the reference relationship graph corresponding to the target data.

[0079] Specifically, when the file management platform detects that a user has edited or updated target data in any file (which could be the origin file, the first file, or another file corresponding to a reference node), it triggers the data synchronization process. The file management platform first identifies the specific data content to be updated and obtains its unique identifier. Then, based on this identifier, it searches the corresponding reference relationship graph and locates the starting node representing the data source from the graph. In this way, regardless of which file the update request originates from, the file management platform can accurately trace the original source of the data.

[0080] S3512. Update the target data in the source file.

[0081] Specifically, after locating the origin file, the file management platform applies the actual update operation to the target data stored in that origin file. This process includes modifying the content or replacing the values ​​of specific fields containing the target data in the origin file's editing interface or the backend data layer. After the update is complete, the target data in the origin file will be recorded as the latest. This step ensures that all subsequent synchronization operations are based on a unified data source.

[0082] S3513. Based on the reference relationship graph, synchronize the updated target data to the files corresponding to all reference nodes in the reference relationship graph.

[0083] Specifically, after the data in the origin file is updated, the file management platform traverses all reference nodes in the reference relationship graph except for the starting node. For each reference node, based on its associated file identifier, it locates the corresponding field in the corresponding reference file (i.e., all files that reference the target data, including the first file). Then, it replaces the old version of the target data stored in the corresponding fields of these reference files with the latest target data obtained from the updated origin file.

[0084] This synchronization process enables global synchronization updates, improving the efficiency and reliability of file content maintenance.

[0085] In some embodiments, the method further includes steps S3521-S3524: S3521. In response to the save operation of the first file, identify the target version of the first file.

[0086] Specifically, when the file management platform receives a user's save instruction for the first file, it triggers the version management process. The file management platform parses the content, metadata, or filename of the file to be saved, and automatically determines and records the target version corresponding to the current save operation based on preset version naming rules (e.g., version numbers like "V1.0" or "V2.1", or timestamp-based serial numbers) or by querying the existing version history of the file in the file library. For example, if the latest version of the file in the file library is version 2, then the file generated by this save will be identified as version 3 (i.e., the target version).

[0087] S3522. If the target version is version i, obtain the (i-1)th version file corresponding to the first file, where i is a natural number greater than 1.

[0088] Specifically, after identifying the target version as version i (i>1), the previous version of the first file, i.e., version i-1, is retrieved from the version history of the file library.

[0089] S3523. Compare the first file and the i-1th version file to generate change information.

[0090] Specifically, the file management platform compares the content of the first file (i.e., the newly saved version i) with the obtained version i-1. Comparisons can be performed at multiple levels, such as: at the field level, comparing the content differences of each editable field in the two versions; at the chapter or paragraph level, comparing the addition, deletion, and modification of text. All identified differences are recorded, generating change information. This change information includes the location of the change (e.g., field identifier, chapter number), the change type (e.g., addition, deletion, modification), the old content before the change, and the new content after the change.

[0091] S3524. Generate a change history corresponding to the first file based on the change information.

[0092] Specifically, the file management platform associates the change information with the relevant information of this operation (e.g., save time, operator identity, target version number) to create a version change record. This record is then added to the change history of the first file. By maintaining and displaying this change history, users can understand the entire revision process of the file and the specific details of each modification.

[0093] In some embodiments, the method further includes steps S3531-S3533: S3531. Calibrate the first file.

[0094] Specifically, after the first file is edited, the file management platform can automatically or in response to user instructions perform a calibration operation on the first file. The calibration process includes checking the standardization, completeness, and consistency of the file content. For example, it can verify whether the data entered into all fields marked as standardized input types in the file comes from standard databases or referenceable data and conforms to predefined formats and value rules; check whether all required fields in the file have been filled; and verify whether the file structure conforms to the specifications of the selected target file template. The calibration results can be presented in the form of a report. If all checks pass, the calibration status is marked as "passed," and the file can proceed to the next process.

[0095] S3532. If the calibration is successful, determine the reviewer corresponding to the first file based on the file attributes of the first file, and initiate the review process.

[0096] Specifically, when the calibration status of the first document is "passed," the review path is automatically determined based on the document's attributes. Document attributes can include document type (e.g., technical specifications, management regulations), department, security classification, and relevant business areas. The document management platform matches these attributes with personnel roles and responsibilities using a pre-configured review matrix or rule engine, thereby identifying one or more reviewers with review permissions. After the reviewers are determined, a review task (including review nodes and the corresponding reviewers for each node) is created, and the review process is initiated. Reviewers at each node can be notified via SMS, email, or platform messages. Reviewers can then review the document content, provide feedback, or approve it on the display interface.

[0097] S3533. If the review is passed, determine the distribution scope of the first document based on the document attributes and perform the document release process.

[0098] Specifically, once approval is granted, the scope of effect or distribution of the first document is determined based on its document attributes. For example, based on the applicable job positions, product lines, departments, or user group tags of the first document's content, the corresponding target user list or terminal list is determined. Subsequently, the document release process is executed, which includes: changing the status of the first document to "released"; setting corresponding document access and operation permissions according to the determined distribution scope; accurately pushing the document release notification or link to the target users or target terminals; and archiving the document to the corresponding location in the preset document management repository.

[0099] The above process ensures that the document can be efficiently and compliantly transformed from editing to taking effect.

[0100] In some embodiments, the file management method further includes AI-enabled operations. Specifically, in the file editing and calibration stages, the file management platform integrates an intelligent calibration algorithm based on natural language processing and machine learning models. When a user completes editing the first file or triggers calibration, the file content can be automatically analyzed. This includes not only basic compliance checks (e.g., field completeness, format compliance) but also semantic-level intelligent verification. For example, it identifies technical parameters, process steps, or management requirements described in the file, compares them with historical standards in a standards database or external regulatory libraries, marks contradictions, outdated content, or deviations from standard expressions, and provides correction suggestions, thereby improving the quality and compliance of the file content.

[0101] In the content association and recommendation stage, the file management platform utilizes AI technology to intelligently generate and recommend related files. When a user edits the first file, the semantics of the entered content can be analyzed in real time. Through a pre-trained model, it automatically retrieves and recommends existing files with highly relevant or potentially cited content (as candidates for the second file) from the file library, improving the accuracy and efficiency of data reuse. Furthermore, after generating a citation relationship graph, the structure and node attributes of the graph can be analyzed to predict missing citations.

[0102] In the document publishing and usage phase, the document management platform provides an AI-based intelligent question-and-answer function. Users can ask questions using natural language (e.g., "What are the operational safety requirements for device XX?" or "Please compare the main differences between version A and version B in Chapter 5"). The document management platform understands the user's intent, locates relevant information, and generates accurate answers to return to the user, improving the efficiency of document retrieval.

[0103] By introducing AI technology, the document management method of this application not only automates and standardizes the process, but also enables intelligent processing, thereby improving the overall efficiency, accuracy, and user experience of document management.

[0104] In this embodiment, templates are set to ensure file format consistency; for fields of standardized input types, candidate standardized data are determined from files in a standard database or file library to ensure consistency and standardization among files; all files with reference relationships are updated with one click through reference relationships or reference relationship graphs, improving file maintenance efficiency; reviewers are determined based on file attributes, and a review process is initiated, improving the compliance and efficiency of the review; the scope of file distribution is determined based on file attributes, and a release process is initiated, achieving accurate and efficient push.

[0105] like Figure 4 The diagram shown is an architectural schematic of the file management platform provided in this application embodiment. The file management platform architecture includes a four-layer architecture system: access layer, business layer, technical support layer, and data layer.

[0106] The access layer is responsible for user access and interfacing with external systems, specifically including: Multiple access points: Supports access via PC (web version) and instant messaging tools such as WeChat Work and Lark, to adapt to different user needs.

[0107] External system integration interfaces: Interoperable with Manufacturing Execution System (MES), Enterprise Asset Management System (EAM), Human Resources (HR) Master Data System, portal integration (interfacing with enterprise portal systems), and signature integration (integrating electronic signature functionality) through standardized API interfaces.

[0108] The business layer is used to manage the entire lifecycle of files, including a standard database management module, a standard editing module, a system management module, a release management module, an intelligent association generation module, and a knowledge data center module. Each module runs independently but can exchange data. Standard database management module: Includes sub-modules such as terminology library and name library, realizing unified input, classification, archiving and query of terms and names to ensure the consistency of data representation.

[0109] The standard editing module comprises five sub-modules: template management, online editing, file association, parameter association, and AI calibration. The template management sub-module manages templates to ensure consistency in file formats of the same type. The online editing sub-module displays the editing interface for users to edit files. The file association sub-module displays the relationships between the current file and other files based on a reference graph. The parameter association sub-module binds parameters from the standard database for parameter synchronization and consistency verification. The AI ​​calibration sub-module uses AI to calibrate the compliance of file content and the consistency of terminology.

[0110] The system management module includes four sub-modules: document management, change management, task management, and system definition. The document management sub-module manages documents throughout their entire lifecycle, covering document creation, editing, review, and archiving. The change management sub-module manages changes to documents. The task management sub-module manages tasks, such as review tasks and release tasks. The system definition sub-module defines system categories and hierarchical relationships.

[0111] The release management module includes four sub-modules: file release, digital release, access control, and security control. The file release sub-module is used to execute the file release process and ensure release compliance; the digital release sub-module is used to accurately push files to the corresponding positions or terminals; the access control sub-module is used to assign file operation permissions according to roles; and the security control sub-module is used to strengthen file security management through file watermarking, operation logs, and other means.

[0112] The associated intelligent generation module includes five sub-modules: equipment technical agreement, equipment acceptance report, AI intelligent compilation, standardization management, and standardization digitization. Among them, the equipment technical agreement sub-module is used to generate standardized equipment technical agreement documents based on templates and parameters; the equipment acceptance report sub-module is used to generate equipment acceptance reports; the AI ​​intelligent compilation sub-module is used to automatically generate initial drafts of documents, improving compilation efficiency; the standardization management sub-module is used to formulate standardization plans and track implementation; and the standardization digitization sub-module is used to manage the standardization process online.

[0113] The Knowledge Data Center module comprises four sub-modules: document query, standard library query, database query, and AI intelligent question answering. The document query sub-module is used to query system documents; the standard database query sub-module is used to retrieve standardized data such as terminology and name databases; the database query sub-module is used to query business data stored on the document management platform; and the AI ​​intelligent question answering sub-module is used to answer user questions using AI.

[0114] The technical support layer includes a data dictionary module, a workflow engine module, a template engine module, a knowledge graph module, a file editor module, a file format conversion and preview module, a standard parameter module and a file reference plugin module, a file watermark module, and a single sign-on module, among which: The data dictionary module stores standardized data to ensure data consistency; the process engine module automates business processes (such as approval and change processing); the template engine module provides storage, retrieval, and customization of file templates; the knowledge graph module constructs a reference relationship graph; the file editor module enables online file editing and preview; the file format conversion and preview module supports mutual conversion and online viewing of different file formats; the standard parameter and file reference plugin module enables the referencing and synchronous updating of standard database parameters and related files; the file watermark module adds identifying watermarks to files; and the single sign-on module implements unified identity authentication across multiple systems to simplify the login process.

[0115] The data layer includes a file status report module, a publication report module, and a leaderboard module, among which: The file status report module is used to statistically analyze the status distribution of files during creation, review, and publication; the publication report module is used to record data such as the number of times files are published and their coverage; and the leaderboard module is used to rank files by dimensions such as search popularity and execution rate.

[0116] like Figure 5 The diagram shown is a schematic of a document management system provided in an embodiment of this application. The document management system includes a standard management module, a standard document editing module, and a system management module.

[0117] The standard management module (process pre-process preparation) includes four sub-modules: system basic definition, template library, standard database, and matrix definition. The system basic definition submodule is used to define file classification, file relationships, organizational relationships, numbering rules, version management, validity period, etc.; the template library submodule is used to store standardized templates; the standard database submodule is used to define standardized data such as terminology, process name, parameter, equipment name, etc.; the matrix definition submodule is used to preset the reviewers, notification recipients, and job posting scope.

[0118] The standard document editing module is used for document creation and review. The specific workflow includes: Start → Basic Definition: Initiates the file editing process and calls resources such as the system basic definition and template library of the standard management module; Content creation: Create documents through online editing, uploading attachments, etc., and reference terms and parameters from standard databases; Calibration: The document content is calibrated (and conflicting references are identified and updated accordingly). If changes are needed, the document is returned to the content creation stage for modification; otherwise, it proceeds to document control review. Document control review: According to the preset rules of the matrix definition module, the review is completed by designated personnel, and after approval, it enters the release review.

[0119] Release review: Complete the compliance verification before release, and release after passing the verification.

[0120] The system management module is used for document publishing, execution, and maintenance, specifically including: Released standard: Supports output in formats such as PDF, Word, and Excel, and associates with parameter libraries to bind files with standardized data.

[0121] Release management: Release documents to the corresponding positions; Display Terminal: Displays the published files on the terminal; Actual index collection or input: Connect to digital platforms such as MES / EAM to input actual values; Implementation standard: Compare and verify the actual values ​​with the data in the file to ensure compliance. Document management: System management, change management, document integration and processing of published documents; Query: File retrieval is achieved through parameter-level multi-dimensional search, AI-powered intelligent question answering, and difference comparison; File update: If data needs to be adjusted, trigger the update process and synchronize it to the standard file editing module. After the iteration is completed, republish the file, and the process ends.

[0122] like Figure 6 The diagram shown is another flowchart illustrating the file management method provided in this application embodiment. The method includes: Online template creation: Create standardized document templates online; Publish: Publish the created file template to the template library; Online editing (referencing standards): Online editing is performed based on modules selected from the module library. During the editing process, standardized data from the standard database is referenced to ensure the standardization and consistency of the document content. AI proofreading + human review: First, AI tools are used to proofread the edited files for content compliance and parameter consistency, and then human review is completed. Release + Paperless Release: Approved documents are released within the document management platform and simultaneously pushed accurately to the corresponding job terminals and personnel in a paperless manner; Digital system management + consistency audit: Digital full lifecycle management of released documents, with simultaneous consistency audit and execution quality verification; AI Search + File Library: Use the AI ​​search function to retrieve resources in the file library. The file library supports automatic updates to ensure real-time data synchronization. Automatic standard integration + closed-loop management: Document standards are integrated with the execution end, and through strong calibration, parameter adjustment and feedback, a closed-loop management of formulation-execution-optimization is formed.

[0123] In this embodiment, online editing, reference association, document digitization, and AI applications enable the management of the entire process from the formulation to the execution and review of system standards. This eliminates low-value work, achieves closed-loop error prevention, realizes digital management of standards, and facilitates the rapid dissemination of various standards.

[0124] like Figure 7 The diagram shown is a structural schematic of the file management device 7 provided in an embodiment of this application. The file management device 7 includes: Module 71 is provided to provide a file editing interface in response to a file creation operation on a first file of a specified type, the file editing interface including several editable fields; The determination module 72 is used to determine the input type of the target field in response to an edit trigger operation on the target field in the editable field; The acquisition module 73 is used to acquire and display multiple candidate standardized data associated with the target field when the input type is a standardized input type; A creation module 74 is used to fill the target data into the target field in response to the selection operation of target data among the plurality of candidate standardized data, thereby obtaining the first file.

[0125] In some embodiments, the acquisition module 73 is further configured to: Determine the data type corresponding to the target field; Retrieve the standard dataset corresponding to the data type from the standard database; The standardized data in the standard dataset are used as multiple candidate standardized data associated with the target field.

[0126] In some embodiments, after obtaining the first file, the file management device 7 further includes an update module (not shown), the update module being used for: Establish a reference relationship between the target data and the first file; In response to an update operation on the target data in the standard database, the content of the fields in the first file that reference the target data is updated according to the reference relationship.

[0127] In some embodiments, the acquisition module 73 is further configured to: Displays a list of files in the file library; In response to the selection operation of the second file in the file list, the referenceable data in the second file is used as multiple candidate standardized data associated with the target field.

[0128] In some embodiments, the file management device 7 further includes a construction module (not shown), which is used for: Based on the reference relationships between the target data and one or more files, a reference relationship graph corresponding to the target data is constructed. The reference relationship graph includes file nodes and connecting edges between file nodes. The file nodes include start nodes and referencing nodes. The start node corresponds to the origin file of the target data, and each referencing node corresponds to a file that references the target data. The connecting edges between the file nodes are used to indicate the reference relationships between files.

[0129] In some embodiments, after constructing the reference relationship graph corresponding to the target data, the update module is further configured to: In response to an update operation on the target data in any file, the origin file defining the target data is located based on the reference relationship graph corresponding to the target data; Update the target data in the source file; Based on the reference relationship graph, the updated target data will be synchronized to the files corresponding to all reference nodes in the reference relationship graph.

[0130] In some embodiments, the file management device 7 further includes a generation module (not shown), which is used for: In response to a save operation on the first file, identify the target version of the first file; If the target version is version i, obtain the (i-1)th version file corresponding to the first file, where i is a natural number greater than 1; Compare the first file and the (i-1)th version file to generate change information; Based on the change information, a change history corresponding to the first file is generated.

[0131] In some embodiments, the file management device 7 further includes a publishing module (not shown), which is used for: The first file is calibrated; If the calibration is successful, the reviewer corresponding to the first file is determined based on the file attributes of the first file, and the review process is initiated. If the review is approved, the distribution scope of the first document is determined based on the document attributes, and the document release process is executed.

[0132] The file management device 7 provided in this application embodiment first determines the input type of the target field when the user edits the target field in the file editing interface. If the input type is a standardized input type, it obtains and displays multiple candidate standardized data associated with the target field, and fills the selected target data into the target field. Thus, for fields with standardized input types, the target data can only be selected from the candidate standardized data, and the user cannot input the data manually, ensuring the consistency and standardization of names between files.

[0133] like Figure 8The diagram shown is a structural schematic of an electronic device provided in an embodiment of this application. The electronic device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a file management method. The display unit of the electronic device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the electronic device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the electronic device, or external keyboards, touchpads, or mice, etc.

[0134] Those skilled in the art will understand that Figure 8 The structure shown is only a block diagram of a part of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0135] Based on the same inventive concept, embodiments of this application also provide a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0136] Since the computer program stored in the computer-readable storage medium can execute any of the file management methods provided in the embodiments of this application, the beneficial effects that any of the file management methods provided in the embodiments of this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0137] Based on the same inventive concept, embodiments of this application also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the methods provided in the various optional implementations of the above embodiments.

[0138] It should be noted that the object data (including but not limited to user device information, user personal information, etc.) and dialogue data involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of relevant countries and regions. Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods.

[0139] Any reference to memory, database, or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0140] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0141] In the above embodiments of the file management device, computer-readable storage medium, electronic device, and computer program product, the descriptions of each embodiment have different focuses. Parts not described in detail in a particular embodiment can be referred to in the relevant descriptions of other embodiments. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes and beneficial effects of the file management device, computer-readable storage medium, computer program product, electronic device, and their corresponding units described above can be referred to the description of the file management method in the above embodiments, and will not be repeated here.

[0142] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0143] The foregoing has provided a detailed description of a file management method, file management device, electronic device, computer-readable storage medium, and computer program product provided by the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A file management method, characterized in that, Includes the following steps: In response to a file creation operation on a first file of a specified type, a file editing interface is provided, the file editing interface containing several editable fields; In response to an edit-triggered operation on a target field in the editable fields, the input type of the target field is determined; If the input type is a standardized input type, obtain and display multiple candidate standardized data associated with the target field; In response to the selection operation of target data among the plurality of candidate standardized data, the target data is filled into the target field to obtain the first file.

2. The method according to claim 1, characterized in that, The step of obtaining multiple candidate standardized data associated with the target field includes: Determine the data type corresponding to the target field; Retrieve the standard dataset corresponding to the data type from the standard database; The standardized data in the standard dataset are used as multiple candidate standardized data associated with the target field.

3. The method according to claim 2, characterized in that, After obtaining the first file, the method further includes: Establish a reference relationship between the target data and the first file; In response to an update operation on the target data in the standard database, the content of the fields in the first file that reference the target data is updated according to the reference relationship.

4. The method according to claim 1, characterized in that, The step of obtaining multiple candidate standardized data associated with the target field includes: Displays a list of files in the file library; In response to the selection operation of the second file in the file list, the referenceable data in the second file is used as multiple candidate standardized data associated with the target field.

5. The method according to claim 3, characterized in that, The method further includes: Based on the reference relationships between the target data and one or more files, a reference relationship graph corresponding to the target data is constructed. The reference relationship graph includes file nodes and connecting edges between file nodes. The file nodes include start nodes and referencing nodes. The start node corresponds to the origin file of the target data, and each referencing node corresponds to a file that references the target data. The connecting edges between the file nodes are used to indicate the reference relationships between files.

6. The method according to claim 5, characterized in that, After constructing the reference relationship graph corresponding to the target data, the method further includes: In response to an update operation on the target data in any file, the origin file defining the target data is located based on the reference relationship graph corresponding to the target data; Update the target data in the source file; Based on the reference relationship graph, the updated target data will be synchronized to the files corresponding to all reference nodes in the reference relationship graph.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: In response to a save operation on the first file, identify the target version of the first file; If the target version is version i, obtain the (i-1)th version file corresponding to the first file, where i is a natural number greater than 1; Compare the first file and the (i-1)th version file to generate change information; Based on the change information, a change history corresponding to the first file is generated.

8. The method according to any one of claims 1-6, characterized in that, The method further includes: The first file is calibrated; If the calibration is successful, the reviewer corresponding to the first file is determined based on the file attributes of the first file, and the review process is initiated. If the review is approved, the distribution scope of the first document is determined based on the document attributes, and the document release process is executed.

9. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of the file management method according to any one of claims 1-8.

10. A storage medium, characterized in that, Includes a computer program, which, when run on an electronic device, causes the electronic device to perform the steps of the file management method according to any one of claims 1-8.

Images