Knowledge base file processing method, system, electronic device, medium and product

Abstract

Embodiments of the present application provide a knowledge base file processing method, system, electronic device, medium and product, the method comprising: determining a target network disk file to be associated to a target knowledge base, wherein the target network disk file is a network disk file uploaded into a network disk file system; obtaining network disk file metadata of the target network disk file in the network disk file system; generating a first knowledge base file in the target knowledge base according to the network disk file metadata of the target network disk file, wherein the first knowledge base file records the network disk file metadata of the target network disk file, and is used to enable a knowledge base server to respond to an operation request for the first knowledge base file, request the network disk file system to operate the target network disk file according to the network disk file metadata recorded in the first knowledge base file. The technical solution of the embodiments of the present application can access the knowledge base and associate the existing network disk file in the network disk file system, without the need for repeated uploading.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, system, electronic device, medium, and product for processing knowledge base files. Background Technology

[0002] A knowledge base file system (BFS) is a system for storing, organizing, and managing knowledge information. It typically consists of multiple knowledge categories and knowledge base files, aiming to help users efficiently organize, share, and utilize knowledge. Compared to traditional file systems, BFS places greater emphasis on the logical relationships between files, knowledge organization, and intelligent management, thus providing users with an intelligent knowledge management and collaboration platform. Existing BFS systems usually require users to manually upload files to a specific knowledge base, which reduces the efficiency and user experience. Summary of the Invention

[0003] This application provides a method for processing knowledge base files, a knowledge base file system, a file system, an electronic device, a computer-readable storage medium, and a computer program product to alleviate or solve one or more technical problems existing in the prior art.

[0004] In a first aspect, embodiments of this application provide a method for processing knowledge base files, applied to a knowledge base server. The method includes: determining a target cloud storage file from uploaded cloud storage files in a cloud storage file system, wherein the target cloud storage file is an uploaded cloud storage file to be associated with a target knowledge base; obtaining the cloud storage file metadata of the target cloud storage file in the cloud storage file system; generating a first knowledge base file in the target knowledge base based on the cloud storage file metadata of the target cloud storage file, wherein the first knowledge base file records the cloud storage file metadata of the target cloud storage file, used to enable the knowledge base server to respond to an operation request for the first knowledge base file, and request operation on the target cloud storage file from the cloud storage file system based on the cloud storage file metadata recorded in the first knowledge base file.

[0005] Secondly, embodiments of this application provide a method for processing knowledge base files, applied to a knowledge base server. The method includes: in response to an operation request for a first knowledge base file in a target knowledge base, obtaining metadata of a cloud storage file recorded in the first knowledge base file; wherein the cloud storage file metadata is the metadata of the target cloud storage file in the cloud storage file system, and the first knowledge base file is generated based on the cloud storage file metadata when the target cloud storage file is associated with the target knowledge base; and requesting an operation on the target cloud storage file from the cloud storage file system based on the cloud storage file metadata.

[0006] Thirdly, embodiments of this application provide a method for processing knowledge base files, applied to a client. The method includes: responding to a user's creation request for a target knowledge base, displaying file information of at least one uploaded cloud storage file in a cloud storage file system, so that the user can select a target cloud storage file from the at least one uploaded cloud storage file, wherein the target cloud storage file is an uploaded cloud storage file to be associated with the target knowledge base; forwarding the creation request to a knowledge base server, the creation request being used to request the knowledge base server to generate a first knowledge base file in the target knowledge base based on the cloud storage file metadata of the target cloud storage file, wherein the first knowledge base file records the cloud storage file metadata of the target cloud storage file, so that the knowledge base server, in response to an operation request for the first knowledge base file, requests to operate on the target cloud storage file from the cloud storage file system based on the cloud storage file metadata recorded in the first knowledge base file.

[0007] Fourthly, embodiments of this application provide a knowledge base file system, including: a knowledge base server for implementing the methods of the first and second aspects of embodiments of this application; and a client for communicating with the knowledge base server and for using the methods of the third aspect of embodiments of this application.

[0008] Fourthly, embodiments of this application provide a file system, including: a cloud storage file system; a knowledge base server, communicatively connected to the cloud storage file system, and used to implement the methods of the first and second aspects of embodiments of this application; and a client, communicatively connected to the knowledge base server and the cloud storage file system, and used to implement the method of the third aspect of embodiments of this application.

[0009] Fifthly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor implements any of the methods of embodiments of this application when executing the computer program.

[0010] Sixthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method of any one of the embodiments of this application.

[0011] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method of any one of the embodiments of this application.

[0012] According to the technical solution of this application embodiment, users can associate uploaded cloud storage files (target cloud storage files) in the cloud storage file system with one or more knowledge bases (target knowledge bases). Specifically, this includes: using the metadata of the target cloud storage file in the cloud storage file system (cloud storage file metadata), generating a corresponding knowledge base file (first knowledge base file) in the target knowledge base, thereby realizing the association function between cloud storage files and knowledge bases. Based on this, users can seamlessly access and associate existing cloud storage files in the cloud storage file system for knowledge bases without repeated uploads. Furthermore, a single cloud storage file can be associated with multiple knowledge bases without creating a copy of the cloud storage file in each knowledge base or repeatedly uploading the cloud storage file to each knowledge base, thereby improving the management efficiency of the knowledge base file system and enhancing the user experience.

[0013] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application, it can be implemented according to the contents of the specification. In order to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0014] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments according to this application and should not be construed as limiting the scope of this application.

[0015] Figure 1 This application provides a system architecture diagram of the file system provided in an embodiment.

[0016] Figure 2 , Figure 3 and Figure 4 The interaction flowcharts between the various execution entities in different scenarios are shown respectively;

[0017] Figure 5 A flowchart illustrating a method for processing knowledge base files according to an embodiment of this application;

[0018] Figure 6 An example diagram illustrating the creation of a knowledge base according to an embodiment of this application is shown;

[0019] Figure 7 An example diagram illustrating the updated and synchronized knowledge base of this application is shown;

[0020] Figure 8 An example diagram illustrating the knowledge classification of embodiments of this application is shown;

[0021] Figure 9 A flowchart illustrating a method for processing knowledge base files according to an embodiment of this application;

[0022] Figure 10 A flowchart illustrating a method for processing knowledge base files according to an embodiment of this application;

[0023] Figure 11 A block diagram of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0024] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the concept or scope of this application. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.

[0025] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and all of them fall within the protection scope of the embodiments of this application.

[0026] Application scenarios

[0027] Cloud storage is a distributed cloud storage service that allows users to upload files to remote servers for storage, management, and sharing via the internet. It offers convenient file access and synchronization features, enabling real-time file synchronization and cross-platform access across different devices. In the digital age, cloud storage has become an important tool for users to store, share, and collaborate on information, and users' functional demands for cloud storage file systems are constantly increasing. Among these, knowledge base file systems based on cloud storage, as an efficient information management method, can help users categorize and organize massive amounts of documents and materials, facilitating quick searching and collaborative sharing, thereby improving work efficiency and effectively reducing repetitive work.

[0028] In related technologies, the workflow of a knowledge base file system typically includes: (1) users create a knowledge base; (2) users upload files to the knowledge base; (3) users create knowledge categories; and (4) users add files to the knowledge categories. This method requires users to manually upload files to the knowledge base, a process that is cumbersome and inefficient, especially in scenarios where files are frequently updated, requiring users to repeatedly upload files. In addition, when the same file needs to be associated with different knowledge bases, users usually need to manually create multiple copies of the file and place them in different knowledge bases. In subsequent use, users need to maintain copies of the file in different knowledge bases themselves. For example, in a shared collaboration scenario, users may build different knowledge bases based on different team organizations, and a file such as a project document may need to be added to multiple knowledge bases. At this time, users need to modify and manage the same file in multiple knowledge bases, which not only increases the cost of file maintenance and management but also easily leads to file version inconsistencies. Furthermore, when users add a large number of files to the knowledge base, they also need to manually categorize each file into a knowledge category, increasing the complexity of file categorization within the knowledge base.

[0029] Based on this, the embodiments of this application aim to provide a technical solution for managing knowledge base files, allowing users to seamlessly access and associate existing cloud storage files in the cloud storage file system without repeated uploads. Optionally, this technical solution allows individual files to be flexibly categorized into different knowledge bases, and file updates are promptly synchronized to all associated knowledge bases, ensuring information consistency and up-to-dateness. Optionally, this technical solution can automatically and intelligently classify files within the knowledge base, making information management more efficient and orderly.

[0030] First, combine Figure 1 This paper introduces the application scenarios of the technical solution presented in this application. Figure 1 This diagram illustrates the system architecture of the file system provided in an embodiment of this application. Figure 1 As shown, the file system includes a knowledge base file system 110 and a cloud storage file system 120. The knowledge base file system 110 includes a knowledge base server 111 and a client 112, and the cloud storage file system 120 includes a cloud storage server 121 and a storage layer 122.

[0031] In an exemplary scenario, a user can associate an uploaded cloud drive file in the cloud drive file system 120 with a knowledge base without having to upload the file again. Figure 2 The flowchart illustrates the interaction between the various executing entities in this scenario.

[0032] like Figure 1 and Figure 2 As shown, according to the technical solution of this application embodiment, the interaction process may include:

[0033] Step S201: The user can access the user interface provided by the knowledge base file system 110 through the client 112 and select to create a target knowledge base. This selection will trigger a creation request. The client 112 sends the creation request to the cloud storage server 121.

[0034] Step S202: The cloud storage server 121 responds to the creation request and returns a list of uploaded cloud storage files that the user can access to the client 112, based on the user's cloud storage file access permissions.

[0035] Step S203: Client 112 displays a list of uploaded cloud storage files on the user interface, allowing the user to select one or more uploaded cloud storage files as target cloud storage files from the list, and generates a list of target cloud storage files.

[0036] Step S204: The knowledge base server 111 creates the target knowledge base and requests the cloud storage server 121 to obtain the cloud storage file metadata of the target cloud storage file. The cloud storage file metadata includes, but is not limited to, cloud storage file identifier (ID), version information (such as version number or update time), and attribute information (such as name, file size, etc.).

[0037] Step S205: The cloud storage server 121 returns the cloud storage file metadata of the target cloud storage file.

[0038] Step S206: The knowledge base server 111 generates the first knowledge base file in the target knowledge base based on the metadata of the target cloud storage file, and returns the created target knowledge base to the client 112. The target knowledge base contains the first knowledge base file, wherein the first knowledge base file records the metadata of the target cloud storage file.

[0039] For example, if it is necessary to modify the target cloud drive file associated with the target knowledge base, the target cloud drive file can be reselected in step S203, and steps S204 to S206 can be further executed.

[0040] In another exemplary scenario, users can access cloud drive files within a knowledge base. Figure 3 This diagram illustrates the interaction flow between the various executing entities in this scenario. Figure 1 and Figure 3 As shown, according to the technical solution of this application embodiment, the interaction process may include:

[0041] Step S301: The user can access the user interface provided by the knowledge base file system 110 through the client 112 and select a knowledge base file in the knowledge base to perform corresponding operations. This operation may be an open operation (view operation), a download operation, or an edit operation. This knowledge base may be, for example, the target knowledge base created in steps S201 to S206, and this knowledge base file may be, for example, the first knowledge base file in steps S201 to S206. This will trigger an operation request for the first knowledge base file, and the client 112 will send the operation request to the knowledge base server 111.

[0042] Step S302: The knowledge base server 111 responds to the operation request and, based on the file metadata recorded in the first knowledge base file, requests the cloud storage server 121 to operate on the cloud storage file corresponding to the file metadata, i.e., the target cloud storage file in steps S201 to S206. For example, when the operation request is to open (view) the first knowledge base file, the knowledge base server 111 requests to open the target cloud storage file; when the operation request is to download the first knowledge base file, the knowledge base server 111 requests to download the target cloud storage file; when the operation request is to edit the first knowledge base file, the knowledge base server 111 requests to edit the target cloud storage file.

[0043] Step S303: The cloud storage server 121 returns the operation link of the target cloud storage file to the client 112.

[0044] In another exemplary scenario, when a file in a cloud drive is updated, the update is synchronized to all associated knowledge bases. Figure 4 This diagram illustrates the interaction flow between the various executing entities in this scenario. Figure 1 and Figure 4 As shown, according to the technical solution of this application embodiment, the interaction process may include:

[0045] Step S401: For the updated cloud storage file, the cloud storage server 121 sends a file update notification to the knowledge base server 111. The file update notification carries the cloud storage file metadata of the updated cloud storage file, which includes the cloud storage file ID and current version information (such as the current version number or update time). The update content of the updated cloud storage file may include, for example, an updated file name or updated file content.

[0046] Step S402: The knowledge base server 111 determines the knowledge base file (i.e., the second knowledge base file) that records the cloud drive file identifier based on the cloud drive file identifier of the updated cloud drive file. Since the updated cloud drive file can be associated with multiple knowledge bases, there can be multiple second knowledge base files.

[0047] Step S403: The knowledge base server 111 updates the second knowledge base file, that is, updates the version information recorded in the second knowledge base file to the current version information of the updated cloud drive file.

[0048] Based on this, when a user operates on the second knowledge base file again, the knowledge base server 111 can access the latest version of the updated cloud drive file based on the updated current version information.

[0049] Storage layer 122 is used to store cloud drive files, including the aforementioned target cloud drive files and updated cloud drive files. For example, storage layer 122 can be deployed as an object storage system, a distributed file system, a database system, etc.

[0050] For example, client 112 can be hardware, such as mobile phones, personal computers, tablets, wearable devices, and other electronic devices; it can also be an application (APP) or software module deployed on an electronic device. Cloud storage server 121 and knowledge base server 111 can be deployed on the same entity or on different entities. The entity can be an application, service, instance, functional module in the form of software, virtual machine, container, or cloud server, or a hardware device or hardware chip with data processing capabilities.

[0051] It should be noted that the application scenarios or examples provided in the embodiments of this application are for ease of understanding, and the embodiments of this application do not specifically limit the application of the technical solutions. In addition, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) 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, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0052] Example

[0053] The technical solution of this application and how it solves the aforementioned technical problems are described in detail below with specific embodiments. The listed specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0054] Figure 5 A flowchart illustrating a method for processing knowledge base files according to an embodiment of this application is provided. This method can be applied to a knowledge base server, for example, by... Figure 1 The knowledge base server 111 shown is executed. For example... Figure 5As shown, the method may include steps S501, S502 and S503.

[0055] Step S501: Determine the target cloud storage file from the uploaded cloud storage files in the cloud storage file system, wherein the target cloud storage file is the uploaded cloud storage file to be associated with at least one target knowledge base.

[0056] The files stored on the cloud drive can be documents in formats such as text, images, and videos, and are stored in the cloud drive's file system (e.g., [file name]). Figure 1 (referring to the cloud storage file system 120 in this application embodiment). In this embodiment, cloud storage file is a broad concept, that is, cloud storage file can be a file or a cloud storage folder.

[0057] The target cloud drive file is the file selected by the user from the uploaded files in the cloud drive's file system and is intended to be associated with the target knowledge base. The target knowledge base is the specific knowledge base used for storing, managing, and sharing the target cloud drive file; that is, the knowledge base that the user expects to associate the target cloud drive file with.

[0058] For example, when creating a target knowledge base, a user can select the target cloud drive file to be associated with the target knowledge base, such as... Figure 2 The steps are the same as those described above, S201 to S203. Alternatively, when modifying a target knowledge base, the user can reselect the target cloud drive file to be associated with that knowledge base. Alternatively, during the use of the knowledge base file system, the user can select one or more target knowledge bases and determine the target cloud drive files to be associated with those knowledge bases. Alternatively, different users can select the same target cloud drive file for association when creating different target knowledge bases.

[0059] Step S502: Obtain the target cloud drive file metadata in the cloud drive file system.

[0060] In other words, the metadata of the target cloud storage file is the metadata of the target cloud storage file in the cloud storage file system. The cloud storage file metadata includes, but is not limited to, the cloud storage file ID, version information (such as version number or update time), attribute information (such as name, file size, etc.).

[0061] For example, the cloud storage file system can proactively request the target cloud storage file's metadata from the cloud storage file system based on the target file's file information. For instance, the cloud storage file system can provide a list of uploaded cloud storage files, including file information for each uploaded file. The target cloud storage file can be selected from among these uploaded files. The knowledge base server requests the cloud storage file system to obtain the cloud storage file metadata corresponding to that file's information, i.e., the target cloud storage file's metadata, based on the target file's file information. Alternatively, the cloud storage file system can push the target cloud storage file's metadata to the knowledge base server. For example, when a user selects a target cloud storage file, the cloud storage file system proactively pushes the target cloud storage file's metadata to the knowledge base server. This application embodiment does not specifically limit the method of obtaining the target cloud storage file's metadata.

[0062] Step S503: Generate a first knowledge base file in the target knowledge base based on the file metadata of the target cloud storage file. The first knowledge base file records the file metadata of the target cloud storage file, which is used to enable the knowledge base server to respond to operation requests for the first knowledge base file and request operations on the target cloud storage file from the cloud storage file system based on the file metadata recorded in the first knowledge base file.

[0063] For example, after obtaining the metadata of the target cloud storage file, the knowledge base server will generate a corresponding knowledge base file (first knowledge base file) in the target knowledge base, that is, generate a file that records the metadata of the target cloud storage file as the first knowledge base file.

[0064] This allows a target cloud drive file to be associated with one or more target knowledge bases. When a user operates on a first knowledge base file within a target knowledge base, the knowledge base server will request the operation on the target cloud drive file from the cloud drive file system based on the cloud drive file metadata recorded in the first knowledge base file. For example, when the operation request is to open the first knowledge base file, the knowledge base server will request the knowledge base file system to open the target cloud drive file; when the operation request is to download the first knowledge base file, the knowledge base server will request the knowledge base file system to download the target cloud drive file; when the operation request is to edit the first knowledge base file, the knowledge base server will request the knowledge base file system to edit the target cloud drive file. See details in [link to documentation]. Figure 3 The interactive flow is shown in the figure.

[0065] According to the technical solution of this application embodiment, users can associate uploaded cloud storage files (target cloud storage files) in the cloud storage file system with one or more knowledge bases (target knowledge bases), thereby realizing the association function between cloud storage files and knowledge bases. Based on this, users can seamlessly access and associate existing cloud storage files in the cloud storage file system for knowledge bases without repeated uploading. Furthermore, since a cloud storage file can be associated with multiple knowledge bases, it is not necessary to create a copy of the cloud storage file in each knowledge base, nor is it necessary to repeatedly upload the cloud storage file to each knowledge base. This improves the management efficiency of the knowledge base file system and enhances the user experience.

[0066] In one implementation, determining the target cloud storage file from the uploaded cloud storage files in step S501 may include: determining the target cloud storage file from the uploaded cloud storage files in response to a creation request for the target knowledge base.

[0067] For example, such as Figure 6 As shown, users can select to create a target knowledge base in the user interface provided by the client, and select one or more cloud storage files, i.e., select one or more target cloud storage files to be associated. This selection operation triggers a creation request. The client sends the creation request to the knowledge base server. The knowledge base server responds to the creation request, creates the target knowledge base (create knowledge base), and uses the knowledge base synchronization program in the knowledge base server to read the cloud storage files, i.e., obtain the cloud storage file metadata of the target cloud storage files. Using the cloud storage file metadata of the target cloud storage files, it generates the first knowledge base file in the target knowledge base, i.e., generates the first knowledge base file, and writes the first knowledge base file into the target knowledge base (write knowledge base). The knowledge base server returns the created target knowledge base to the client, which contains the first knowledge base file.

[0068] In other words, when creating a target knowledge base, users can select the target file from the already uploaded cloud storage files without having to upload it again. This greatly improves the efficiency of knowledge base construction and overcomes the cumbersome process encountered by users, thus enhancing the user experience.

[0069] In one implementation, the aforementioned creation request is used to create a target knowledge base for a user, wherein the target cloud storage file is selected by the user from at least one uploaded cloud storage file, and the uploaded cloud storage file is determined by the cloud storage file system based on the user's cloud storage file access permissions.

[0070] Generally speaking, access permissions for knowledge bases, knowledge base files, and cloud storage files are all related to user permissions. Specifically, cloud storage file access permissions include, but are not limited to, user operation permissions on cloud storage files, such as open (view) permissions, download permissions, and edit permissions.

[0071] For example, a user can select to create a target knowledge base based on the user interface provided by the client. This selection triggers a creation request. The cloud storage server responds to the creation request by returning a list of uploaded cloud storage files that the user can access, based on their cloud storage file access permissions. The user then selects one or more uploaded cloud storage files from the list as the target cloud storage file.

[0072] Based on this, user access permissions to cloud storage files can be verified, thereby improving the data security of the knowledge base file system.

[0073] In one implementation, the metadata of the cloud storage file includes a cloud storage file identifier and version information. The method in this embodiment may further include: receiving a file update notification sent by the cloud storage file system, the file update notification being used to notify the knowledge base server that the cloud storage file identifier and current version information of the updated cloud storage file have been updated; determining at least one second knowledge base file based on the cloud storage file identifier of the updated cloud storage file, wherein the second knowledge base file is a knowledge base file that records the cloud storage file identifier of the updated cloud storage file; updating the version information recorded in the second knowledge base file to the current version information of the updated cloud storage file, wherein the version information recorded in the second knowledge base file is used to enable the knowledge base server to respond to an operation request for the second knowledge base file, requesting the cloud storage file system to operate on the updated cloud storage file based on the cloud storage file identifier and version information recorded in the second knowledge base file.

[0074] The file identifier, or file ID, is a unique identifier for a file within the cloud storage file system. Version information can be a version number or an update time. Current version information is used to determine the current version of the file. When a user edits a file in the cloud storage file system, the edited file becomes an updated file. Editing operations that can lead to file updates include, but are not limited to, changing the file name, editing the file content, and changing file access permissions.

[0075] For example, such as Figure 7As shown, when a user modifies a file, i.e., updates the file in the cloud drive, the modified file becomes the updated file. For the updated file, the cloud drive server can send a file update notification to the knowledge base server based on an event notification mechanism or a message notification mechanism. The file update notification carries the cloud drive file ID and current version information of the updated file. The knowledge base synchronization program in the knowledge base server will update the synchronized knowledge base. That is, based on the cloud drive file ID of the updated file, it will determine the second knowledge base file that records the cloud drive file ID and update the second knowledge base file, i.e., update the version information recorded in the second knowledge base file to the current version information of the updated file. Since the updated file can be associated with multiple knowledge bases, there can be multiple second knowledge base files. The knowledge base server will update the second knowledge base file in each knowledge base associated with the updated file.

[0076] Therefore, when a user operates on a second knowledge base file again, the knowledge base server, based on the version information recorded in the second knowledge base file, requests access to the updated cloud storage file system from the cloud storage file system, and can then access the current version of the updated cloud storage file. Since the knowledge base file records the cloud storage file identifier—a unique identifier for the cloud storage file within the cloud storage file system—even if an updated cloud storage file is associated with multiple knowledge bases, the knowledge base server can traverse each knowledge base based on the record information in the knowledge base file, obtain each associated knowledge base and its corresponding second knowledge base file, and update the version information of each second knowledge base file to the current version information of the updated cloud storage file. This synchronizes the update to each associated knowledge base, allowing the user to access the latest version of the updated cloud storage file. Therefore, after a user updates a cloud storage file, knowledge base maintenance operations are simplified, file maintenance and management costs are reduced, and file version inconsistencies are avoided.

[0077] In one embodiment, the processing method of this application may further include: requesting access to the corresponding cloud storage file to be classified from the cloud storage file system according to the cloud storage file metadata recorded in the third knowledge base file to be classified; determining a target classification label from the candidate classification labels based on the matching degree between the cloud storage file to be classified and at least one candidate classification label, wherein the target classification label is the knowledge classification label of the third knowledge base file.

[0078] The candidate category tags can be user-created knowledge categories used to categorize knowledge base files. The third knowledge base file is the knowledge base file to be categorized. Based on the metadata of the cloud storage file recorded in the third knowledge base file, the knowledge base server requests access to the corresponding cloud storage file to be categorized from the cloud storage file system and determines the matching degree between the cloud storage file to be categorized and the candidate category tags.

[0079] For example, keywords can be extracted from the files in the cloud storage to be categorized, and the matching degree between the files and the candidate category tags can be determined based on the matching degree between the keywords and the candidate category tags. Alternatively, a deep learning model can be pre-trained, and the files in the cloud storage to be categorized and the candidate category tags can be input into the deep learning model, which will then output the matching degree.

[0080] A matching threshold can be preset. If the matching degree between the candidate category tag and the file to be categorized reaches the threshold, the candidate category tag will be used as the target category tag. Alternatively, the matching degree between each candidate category tag and the file to be categorized can be determined, and the candidate category tag with the highest matching degree will be used as the target category tag. The target category tag is the knowledge category tag of the third-party knowledge base file in its knowledge base.

[0081] In one application example, a user can create knowledge category tags using a client provided by the knowledge base file system, adding one or more candidate category tags to a knowledge base. Further, the knowledge base server can automatically categorize the knowledge base files within it. For instance, for any knowledge base file (a third knowledge base file), the server accesses the corresponding cloud drive file (the file to be categorized) and determines the target category tag based on the match between the file and the candidate category tags. This target category tag is then used as the knowledge category tag for that knowledge base file. The knowledge base server adds knowledge category tags to each knowledge base file and returns them to the client.

[0082] In another application example, a user can select a knowledge base file (a third-party knowledge base file) using the client provided by the knowledge base file system. Further, the knowledge base server can automatically categorize this file. For instance, the server accesses the corresponding cloud drive file (the file to be categorized) and determines the target category label based on the match between the file and the proposed category labels. This target category label is then used as the knowledge category label for the knowledge base file. The server adds the knowledge category label to the file and returns it to the client. Based on this, the knowledge base file system can intelligently categorize knowledge base files, significantly reducing the burden of manual categorization for users and making file classification management more efficient and orderly.

[0083] In one implementation, determining a target category label from the candidate category labels based on the matching degree between the file to be categorized and the candidate category labels includes: inputting the file content of the file to be categorized and the candidate category labels into a large language model, wherein the large language model is used to determine a target category label from at least one candidate category label based on the matching degree between the file to be categorized and the candidate category labels; and obtaining the target category label output by the large language model.

[0084] Large Language Models (LLMs), often shortened to large models, are large-scale machine learning models used in Natural Language Processing (NLP) to understand or generate human language. LLMs are trained on very large text datasets using deep learning techniques, enabling them to capture the complex patterns and diversity of natural language.

[0085] For example, such as Figure 8 As shown, users can create knowledge categories by setting one or more candidate category tags and adding files to the knowledge base, such as uploading files to a cloud drive or associating cloud drive files with the knowledge base using the aforementioned method. The knowledge base server accesses the cloud drive file (i.e., the file to be categorized) and inputs its content into the intelligent categorization module. The intelligent categorization module can be an LLM (Limited Management Model), which determines the target category tag from the candidate category tags based on the matching degree between the file to be categorized and the candidate category tags. Further, the knowledge base server categorizes the file into knowledge categories, that is, it categorizes the third-party knowledge base file under the target category tag (i.e., the knowledge category tag).

[0086] Based on this, LLM can be used to classify knowledge base files, thereby improving classification accuracy. In addition, LLM technology is relatively mature, so it can improve classification efficiency and reduce R&D costs.

[0087] Figure 9 A flowchart illustrating a method for processing knowledge base files according to an embodiment of this application is provided. This method can be applied to a knowledge base server, for example, by... Figure 1 The knowledge base server 111 shown is executed. For example... Figure 9 As shown, the method may include:

[0088] Step S901: In response to an operation request for the first knowledge base file in the target knowledge base, obtain the cloud drive file metadata recorded in the first knowledge base file; wherein, the cloud drive file metadata is the metadata of the target cloud drive file in the cloud drive file system, and the first knowledge base file is generated based on the cloud drive file metadata when the target cloud drive file is associated with the target knowledge base;

[0089] Step S902: Based on the file metadata of the cloud drive file, request the target cloud drive file to be operated on.

[0090] The corresponding implementation methods and technical effects can be found above. Figure 3 and Figure 5 The relevant descriptions will not be repeated here.

[0091] Figure 10 A flowchart illustrating a method for processing knowledge base files according to an embodiment of this application is provided. This method can be applied to a client, for example, by... Figure 1 The client 112 shown is executed. (As shown) Figure 10 As shown, the method may include:

[0092] Step S1001: In response to the user's request to create a target knowledge base, display the file information of at least one uploaded file in the cloud storage file system, so that the user can select a target file from at least one uploaded file, wherein the target file is the uploaded file to be associated with the target knowledge base;

[0093] Step S1002: Forward a creation request to the knowledge base server. The creation request is used to request the knowledge base server to generate a first knowledge base file in the target knowledge base based on the file metadata of the target cloud storage file. The first knowledge base file records the file metadata of the target cloud storage file, which is used to enable the knowledge base server to respond to the operation request for the first knowledge base file and request the cloud storage file system to operate on the target cloud storage file based on the file metadata recorded in the first knowledge base file.

[0094] The corresponding implementation methods and technical effects can be found above. Figure 2 , Figure 5 and Figure 6 The relevant descriptions will not be repeated here.

[0095] Corresponding to the application scenarios and methods provided in the embodiments of this application, the embodiments of this application also provide a knowledge base file processing apparatus, applied to a knowledge base server. The apparatus includes: a target cloud drive file determination module, used to determine a target cloud drive file from uploaded cloud drive files in a cloud drive file system, wherein the target cloud drive file is an uploaded cloud drive file to be associated with at least one target knowledge base; a cloud drive file metadata acquisition module, used to acquire the cloud drive file metadata of the target cloud drive file in the cloud drive file system; and a first knowledge base file generation module, used to generate a first knowledge base file in the target knowledge base based on the cloud drive file metadata of the target cloud drive file, wherein the first knowledge base file records the cloud drive file metadata of the target cloud drive file, and is used to enable the knowledge base server to respond to an operation request for the first knowledge base file, and request operation on the target cloud drive file from the cloud drive file system based on the cloud drive file metadata recorded in the first knowledge base file.

[0096] In one implementation, the target cloud drive file determination module is specifically used to: in response to a creation request for the target knowledge base, determine the target cloud drive file from the uploaded cloud drive files.

[0097] In one implementation, the creation request is used to create the target knowledge base for a user, wherein the target cloud storage file is selected by the user from at least one uploaded cloud storage file, and the uploaded cloud storage file is determined by the cloud storage file system based on the user's cloud storage file access permissions.

[0098] In one embodiment, the cloud storage file metadata includes a cloud storage file identifier and version information; the device further includes: a file update notification receiving module, configured to receive a file update notification sent by the cloud storage file system, the file update notification being used to notify the knowledge base server that the cloud storage file identifier and current version information of the updated cloud storage file have been updated; a second knowledge base file determining module, configured to determine at least one second knowledge base file based on the cloud storage file identifier of the updated cloud storage file, wherein the second knowledge base file is a knowledge base file that records the cloud storage file identifier of the updated cloud storage file; and an update module, configured to update the version information recorded in the second knowledge base file to the current version information of the updated cloud storage file, wherein the version information recorded in the second knowledge base file is used to enable the knowledge base server to respond to an operation request for the second knowledge base file, and request operation on the updated cloud storage file from the cloud storage file system based on the cloud storage file identifier and version information recorded in the second knowledge base file.

[0099] In one embodiment, the apparatus further includes: an access request module, configured to request access to the corresponding cloud storage file to be classified from the cloud storage file system based on the cloud storage file metadata recorded in the third knowledge base file to be classified; and a target classification tag determination module, configured to determine a target classification tag from the candidate classification tags based on the matching degree between the cloud storage file to be classified and at least one candidate classification tag, wherein the target classification tag is the knowledge classification tag of the third knowledge base file.

[0100] In one implementation, the target classification label determination module is specifically used to: input the file content of the cloud storage file to be classified into a large language model, wherein the large language model is used to determine the target classification label from the candidate classification labels based on the matching degree between the cloud storage file to be classified and the candidate classification labels; and obtain the target classification label output by the large language model.

[0101] Corresponding to the application scenarios and methods provided in the embodiments of this application, the embodiments of this application also provide a knowledge base file processing device, applied to a knowledge base server. The device includes: a cloud drive file metadata acquisition module, used to acquire cloud drive file metadata recorded in the first knowledge base file in response to an operation request for a first knowledge base file in a target knowledge base; wherein, the cloud drive file metadata is the metadata of the target cloud drive file in the cloud drive file system, and the first knowledge base file is generated based on the cloud drive file metadata when the target cloud drive file is associated with the target knowledge base; and an operation request module, used to request an operation on the target cloud drive file from the cloud drive file system based on the cloud drive file metadata.

[0102] Corresponding to the application scenarios and methods provided in the embodiments of this application, the embodiments of this application also provide a knowledge base file processing device applied to a client. The device includes: a display module, used to display file information of at least one uploaded cloud storage file in a cloud storage file system in response to a user's creation request for a target knowledge base, so that the user can select a target cloud storage file from the at least one uploaded cloud storage file, wherein the target cloud storage file is an uploaded cloud storage file to be associated with the target knowledge base; and a creation request forwarding module, used to forward the creation request to a knowledge base server, the creation request being used to request the knowledge base server to generate a first knowledge base file in the target knowledge base based on the cloud storage file metadata of the target cloud storage file, wherein the first knowledge base file records the cloud storage file metadata of the target cloud storage file, so that the knowledge base server, in response to an operation request for the first knowledge base file, requests to operate on the target cloud storage file from the cloud storage file system based on the cloud storage file metadata recorded in the first knowledge base file.

[0103] The functions of each module in each device in the embodiments of this application can be found in the corresponding description in the above method, and they have corresponding beneficial effects, which will not be repeated here.

[0104] Figure 11 This is a block diagram of an electronic device used to implement embodiments of this application. For example... Figure 11 As shown, the electronic device includes a memory 1101 and a processor 1102. The memory 1101 stores a computer program that can run on the processor 1102. When the processor 1102 executes the computer program, it implements the method described in the above embodiments. The number of memories 1101 and processors 1102 can be one or more. In a specific implementation, the electronic device may also include a communication interface 1103 for communicating with external devices and performing data exchange and transmission.

[0105] In practical implementation, if the memory 1101, processor 1102, and communication interface 1103 are implemented independently, they can be interconnected via a bus to communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 11 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0106] Optionally, in a specific implementation, if the memory 1101, processor 1102, and communication interface 1103 are integrated on a single chip, then the memory 1101, processor 1102, and communication interface 1103 can communicate with each other through an internal interface.

[0107] This application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method provided in this application.

[0108] This application provides a computer program product, including a computer program that, when executed by a processor, implements the method provided in this application.

[0109] This application also provides a chip including a processor for calling and executing instructions stored in a memory, causing a communication device with the chip installed to perform the method provided in this application.

[0110] This application also provides a chip, including: an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in the application embodiment.

[0111] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting Advanced Reduced Instruction Set Machines (ARM) architecture.

[0112] Further, optionally, the aforementioned memory may include read-only memory and random access memory. The memory may be volatile memory or non-volatile memory, or may include both. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available. Examples include Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0113] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0114] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0115] Furthermore, the terms "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, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0116] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functionality involved.

[0117] The logic and / or steps described in the flowchart or otherwise herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0118] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware, the program being stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiments.

[0119] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a disk, or an optical disk, etc.

[0120] The above description is merely an exemplary embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope described in this application, and these should all be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing knowledge base files, applied to a knowledge base server, the method comprising: The target cloud storage file is determined from the uploaded cloud storage files in the cloud storage file system, wherein the target cloud storage file is an uploaded cloud storage file to be associated with at least one target knowledge base; Obtain the target cloud drive file's metadata in the cloud drive's file system; Based on the metadata of the target cloud storage file, a first knowledge base file is generated in the target knowledge base. The first knowledge base file records the metadata of the target cloud storage file, which is used to enable the knowledge base server to respond to operation requests for the first knowledge base file and request operations on the target cloud storage file system based on the metadata of the cloud storage file recorded in the first knowledge base file.

2. The method according to claim 1, wherein, The step of determining the target cloud drive file from the uploaded cloud drive files in the cloud drive file system includes: In response to the request to create the target knowledge base, the target cloud storage file is determined from the uploaded cloud storage files.

3. The method according to claim 2, wherein, The creation request is used to create the target knowledge base for the user, and the target cloud drive file is selected by the user from at least one of the uploaded cloud drive files, which is determined by the cloud drive file system according to the user's cloud drive file access permissions.

4. The method according to claim 1, wherein, The metadata of the cloud storage file includes the cloud storage file identifier and version information; the method further includes: Receive a file update notification sent by the cloud storage file system. The file update notification is used to notify the knowledge base server that the cloud storage file identifier and current version information of the cloud storage file have been updated. Based on the cloud drive file identifier of the updated cloud drive file, at least one second knowledge base file is determined, wherein the second knowledge base file is a knowledge base file that records the cloud drive file identifier of the updated cloud drive file; The version information recorded in the second knowledge base file is updated to the current version information of the updated cloud drive file. The version information recorded in the second knowledge base file is used to enable the knowledge base server to respond to operation requests for the second knowledge base file and request operation on the updated cloud drive file system according to the cloud drive file identifier and version information recorded in the second knowledge base file.

5. The method according to any one of claims 1 to 4, further comprising: Based on the metadata of the cloud storage files recorded in the third knowledge base file to be classified, request access to the corresponding cloud storage files to be classified from the cloud storage file system; Based on the matching degree between the file to be categorized on the cloud drive and at least one candidate category tag, a target category tag is determined from the candidate category tags, wherein the target category tag is the knowledge category tag of the third knowledge base file.

6. The method according to claim 5, wherein determining the target category tag from the candidate category tags based on the matching degree between the file to be categorized and the candidate category tags includes: The file content of the cloud storage file to be classified and the candidate category tags are input into a large language model, wherein the large language model is used to determine the target category tag from at least one candidate category tag based on the matching degree between the cloud storage file to be classified and the candidate category tags; Obtain the target classification label output by the large language model.

7. A method for processing knowledge base files, applied to a knowledge base server, the method comprising: In response to an operation request for a first knowledge base file in the target knowledge base, the file metadata of the cloud drive file recorded in the first knowledge base file is obtained; wherein, the file metadata of the cloud drive file is the metadata of the target cloud drive file in the cloud drive file system, and the first knowledge base file is generated based on the file metadata of the cloud drive file when the target cloud drive file is associated with the target knowledge base; Based on the file metadata of the cloud drive, request operations on the target cloud drive file from the cloud drive file system.

8. A method for processing knowledge base files, applied to a client, the method comprising: In response to a user's request to create a target knowledge base, the system displays file information of at least one uploaded file in the cloud storage file system, allowing the user to select a target file from the at least one uploaded file, wherein the target file is an uploaded file to be associated with the target knowledge base. The creation request is forwarded to the knowledge base server. The creation request is used to request the knowledge base server to generate a first knowledge base file in the target knowledge base based on the file metadata of the target cloud storage file. The first knowledge base file records the file metadata of the target cloud storage file. This is used to enable the knowledge base server to respond to the operation request for the first knowledge base file and request the cloud storage file system to operate on the target cloud storage file based on the file metadata recorded in the first knowledge base file.

9. A knowledge base file system, comprising: A knowledge base server, used to implement the method according to any one of claims 1 to 7; The client communicates with the knowledge base server and is used to implement the method described in claim 8.

10. A file system, comprising: Cloud drive file system; The knowledge base server communicates with the cloud storage file system and is used to implement the method of any one of claims 1 to 7; The client communicates with the knowledge base server and the cloud storage file system, and is used to implement the method described in claim 8.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory, wherein the processor, when executing the computer program, implements the method of any one of claims 1 to 8.

12. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method of any one of claims 1 to 8.

13. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 8.

Images