Enterprise knowledge base application method and device and electronic equipment

Abstract

The invention discloses an enterprise knowledge base application method and device and electronic equipment. The method comprises the following steps: determining a knowledge tree corresponding to an enterprise knowledge base, and determining knowledge entries and knowledge tags of the knowledge tree; knowledge item content is generated through a text editor; determining an auditing result of the knowledge item content, and issuing the corresponding knowledge item under the condition that the auditing result is that auditing is passed; under the condition that the knowledge entries are published successfully, querying the knowledge tree according to a received query request, and determining target knowledge entries corresponding to the query request; an embedded link corresponding to the target knowledge entry is obtained, the target knowledge entry is called in the internal application of the enterprise according to the embedded link, and the embedded link comprises the target knowledge entry ID and the access permission verification information. The technical problems of complicated enterprise knowledge management, difficult sharing, insufficient security and inaccurate authorization in related technologies are solved.

Description

Technical Field

[0001] This application relates to the field of information management, and more specifically, to a method, apparatus, and electronic device for applying an enterprise knowledge base. Background Technology

[0002] In modern enterprise operations, knowledge management has become a key element in improving organizational efficiency, ensuring business continuity, and enhancing decision-making capabilities. However, large and medium-sized enterprises in related technologies face challenges such as fragmented knowledge management, slow updates, and a lack of sharing mechanisms. Knowledge is typically distributed across various departments and individuals, taking on diverse forms and lacking unified standards. Coupled with high employee turnover, this makes it difficult to effectively transfer and utilize knowledge, experience, and information. Especially as enterprises expand and business complexity increases, the accurate transfer of knowledge becomes increasingly important, but traditional management models often cannot meet this demand. Furthermore, the security of enterprise knowledge sharing is becoming increasingly prominent. The lack of granular access control and effective tracking mechanisms makes sensitive information easily leaked, posing a potential threat to the enterprise.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a method, apparatus, and electronic device for applying an enterprise knowledge base, in order to at least solve the technical problems of complex enterprise knowledge management, difficulty in sharing, insufficient security, and inaccurate authorization in related technologies.

[0005] According to one aspect of the embodiments of this application, an application method for an enterprise knowledge base is provided, comprising: determining a knowledge tree corresponding to the enterprise knowledge base, and determining knowledge entries and knowledge tags in the knowledge tree, wherein the knowledge tree is used to reflect the directory structure and hierarchical relationship of the enterprise knowledge base, the knowledge entries are used to reflect the unit knowledge information of the enterprise knowledge base, and the knowledge tags are used to reflect the knowledge type of the knowledge entries; generating knowledge entry content through a text editor; determining the review result of the knowledge entry content, and publishing the corresponding knowledge entry if the review result is approved; if the knowledge entry is successfully published, querying the knowledge tree according to a received query request, and determining the target knowledge entry corresponding to the query request; obtaining an embedded link corresponding to the target knowledge entry, and calling the target knowledge entry in an internal enterprise application according to the embedded link, wherein the embedded link contains the target knowledge entry ID and access permission verification information.

[0006] Optionally, the knowledge tree corresponding to the enterprise knowledge base is determined, including: designating the homepage of the enterprise knowledge base as the zero-level root node; designating the "must-know" and "must-do" sections and the operation and maintenance manual of the enterprise knowledge base as the first-level root nodes, wherein the "must-know" sections are publicly visible to all operation objects, and the operation and maintenance manual is visible only after authorization by the operation object; designating the knowledge entries of the enterprise knowledge base as leaf nodes, and determining the knowledge tags corresponding to the leaf nodes, wherein the knowledge tags include at least the content category tag, applicable object tag, and application carrier tag of the knowledge entry; and generating the knowledge tree based on the zero-level root node, the first-level root node, the leaf nodes, and the knowledge tags.

[0007] Optionally, generating knowledge entry content via a text editor includes: without specifying an aggregated file to generate knowledge entry content, editing the first data content of a knowledge entry in the enterprise knowledge base using a text editor, wherein the aggregated file represents a file in the enterprise knowledge base that has passed review and is stored in a standard format, and the first data content includes at least one of the following: text information, directory information, hyperlink information, and image information in the knowledge entry; previewing the format of the first data content using a text editor, and if the first data content conforms to the preview format, writing the first data content into a leaf node in the knowledge tree to obtain the knowledge entry content; or if the first data content does not conform to the preview format, re-editing the first data content until it conforms to the preview format, and then writing the first data content into a leaf node in the knowledge tree to obtain the knowledge entry content.

[0008] Optionally, generating knowledge entry content via a text editor includes: when generating knowledge entry content from a specified aggregated file, identifying the aggregated file using an intelligent agent tool, and editing the second data content in the aggregated file using a text editor if the aggregated file meets the basic format requirements; previewing the format of the second data content using a text editor, and writing the second data content into a leaf node in the knowledge tree if the second data content conforms to the preview format, thus obtaining the knowledge entry content; or, if the second data content does not conform to the preview format, re-editing the second data content until it conforms to the preview format, and then writing the second data content into a leaf node in the knowledge tree, thus obtaining the knowledge entry content.

[0009] Optionally, determining the review result of the knowledge entry content and publishing the corresponding knowledge entry if the review result is approved includes: obtaining the knowledge entry content to be reviewed; receiving the review result obtained by the review object in sequentially reviewing the data content, knowledge entry naming, and knowledge tags of the knowledge entry content, wherein the review object has review permissions, and the review permissions include the review identifier used to review knowledge tree nodes; and publishing the knowledge entry storing the knowledge entry content if the review result is approved, wherein the published knowledge entry is used to provide a basis for querying.

[0010] Optionally, querying the knowledge tree based on the received query request includes: browsing the knowledge tree layer by layer from the query interface based on the query request, or querying the knowledge tree based on keywords in the query request, or querying the knowledge tree based on knowledge tags corresponding to the query request, to obtain the target knowledge entry corresponding to the query request; displaying the target knowledge entry and adding a digital watermark, wherein the digital watermark includes at least the employee number, IP address and timestamp information of the queried object.

[0011] Optionally, the method further includes: obtaining login logs corresponding to the operation object, query logs corresponding to the query object, and export logs corresponding to the knowledge entries; auditing the login logs, query logs, and export logs according to a preset time period to identify unauthorized authorization behavior.

[0012] According to another aspect of the embodiments of this application, an application device for an enterprise knowledge base is also provided, comprising: a determining module, configured to determine a knowledge tree corresponding to the enterprise knowledge base, and determine knowledge entries and knowledge tags of the knowledge tree, wherein the knowledge tree is used to reflect the directory structure and hierarchical relationship of the enterprise knowledge base, the knowledge entries are used to reflect the unit knowledge information of the enterprise knowledge base, and the knowledge tags are used to reflect the knowledge type of the knowledge entries; a generating module, configured to generate knowledge entry content through a text editor; a publishing module, configured to determine the review result of the knowledge entry content, and publish the corresponding knowledge entry if the review result is approved; a query module, configured to query the knowledge tree according to a received query request and determine the target knowledge entry corresponding to the query request if the knowledge entry is successfully published; and an application module, configured to obtain an embedded link corresponding to the target knowledge entry, and call the target knowledge entry in an internal enterprise application according to the embedded link, wherein the embedded link contains the target knowledge entry ID and access permission verification information.

[0013] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory and a processor, wherein the memory is used to store program instructions; and the processor is connected to the memory and used to execute the application method for implementing the above-mentioned enterprise knowledge base.

[0014] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, the non-volatile storage medium including a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned application method of the enterprise knowledge base by running the computer program.

[0015] According to another aspect of the embodiments of this application, a computer program product is also provided, including computer instructions, which, when executed by a processor, implement the above-described method for applying an enterprise knowledge base.

[0016] In this embodiment, a knowledge tree corresponding to the enterprise knowledge base is determined, along with knowledge entries and tags. The knowledge tree reflects the directory structure and hierarchical relationship of the enterprise knowledge base, knowledge entries reflect the unit knowledge information of the enterprise knowledge base, and knowledge tags reflect the knowledge type of the knowledge entries. Knowledge entry content is generated using a text editor. The review result of the knowledge entry content is determined, and the corresponding knowledge entry is published if the review result is approved. If the knowledge entry is successfully published, the knowledge tree is queried based on the received query request, and the target knowledge entry corresponding to the query request is determined. An embedded link corresponding to the target knowledge entry is obtained, and the target knowledge entry is invoked in the enterprise's internal applications based on the embedded link. The embedded link contains the target knowledge entry ID and access permission verification information. This achieves the goal of standardized management of internal enterprise knowledge resources, thereby realizing the technical effects of rapid retrieval, accurate authorization, and widespread application of internal enterprise knowledge. This solves the technical problems of complex enterprise knowledge management, difficult sharing, insufficient security, and inaccurate authorization in related technologies. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a hardware structure diagram of a computer terminal for implementing an application method of an enterprise knowledge base according to an embodiment of this application;

[0019] Figure 2 This is a flowchart of an application method for an enterprise knowledge base according to an embodiment of this application;

[0020] Figure 3 This is a structural diagram of an enterprise knowledge base application system according to an embodiment of this application;

[0021] Figure 4 This is a flowchart illustrating the planning of an enterprise knowledge base according to an embodiment of this application;

[0022] Figure 5 This is a flowchart illustrating the construction process of an enterprise knowledge base according to an embodiment of this application;

[0023] Figure 6 This is a flowchart illustrating the publishing process of an enterprise knowledge base according to an embodiment of this application;

[0024] Figure 7 This is a flowchart illustrating a query process for an enterprise knowledge base according to an embodiment of this application;

[0025] Figure 8This is an application flowchart of an enterprise knowledge base according to an embodiment of this application;

[0026] Figure 9 This is a security control flowchart for an enterprise knowledge base according to an embodiment of this application;

[0027] Figure 10 This is a structural diagram of an application device for an enterprise knowledge base according to an embodiment of this application. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] First, some nouns or terms that appear in the explanation of the embodiments of this application shall be interpreted as follows:

[0031] Knowledge Tree: A directory system that organizes enterprise knowledge according to a tree structure. It can clearly show the hierarchical relationship and classification structure of knowledge, facilitating knowledge retrieval, authorization, and management. Similar to an enterprise organizational structure, different departments or professional fields constitute different branches, and each knowledge entry is attached as a leaf node under its respective branch, supporting the creation and management of multi-level directories.

[0032] Knowledge tags: Effective classification and identification of knowledge. This application adds multiple maintainable tags in three categories—content category, applicable audience, and application medium—to all knowledge entries, facilitating rapid knowledge filtering and matching.

[0033] Markdown is a lightweight text markup language widely used for writing easy-to-read documents and facilitating conversion into HTML web page format. With its simple syntax, Markdown allows for the rapid creation of rich text elements such as headings, lists, links, and images, making it ideal for writing and formatting enterprise knowledge entries.

[0034] Knowledge aggregation refers to the process of organizing, summarizing, and formatting scattered knowledge held by various departments or individuals within an enterprise. By standardizing the structure and content of knowledge, its readability and usability are improved, laying the foundation for the construction of a knowledge base.

[0035] Intelligent agent: In this application, it specifically refers to a software program or algorithm used for automated processing, which can perceive the environment (such as collected knowledge files), perform tasks (such as automatically arranging knowledge content), learn and improve its own behavior to achieve a specific goal.

[0036] Digital watermarking: a covert information embedding technology used for copyright protection and information tracking. In this application, digital watermarking is mainly used to embed operational information, such as the operator's employee number, operation IP address, and operation time, at the visual level of knowledge documents to prevent illegal copying and distribution of knowledge documents, while facilitating the tracing of the history of knowledge usage.

[0037] Log auditing: The process of checking and verifying operational information recorded in system logs, aiming to ensure the compliance and security of system operations. In knowledge base management, log auditing can be used to confirm the legitimacy of login, query, and export behaviors, preventing unauthorized access and knowledge leakage.

[0038] MySQL (My Structured Query Language) is a popular open-source relational database management system used for storing and managing data. In this application, MySQL is used to store various data related to the enterprise knowledge base, including knowledge entries, approval status, operation logs, etc., supporting the backend data management and retrieval functions of the knowledge base.

[0039] To address the issue of poor application effectiveness of enterprise knowledge bases in related technologies, this application provides a method for applying an enterprise knowledge base, which can be run on... Figure 1 The computer terminal shown is described below.

[0040] The application method of the enterprise knowledge base provided in this application can be executed on a mobile terminal, computer terminal or similar computing device. Figure 1 A hardware block diagram of a computer terminal for implementing an enterprise knowledge base application method is shown. Figure 1As shown, the computer terminal 10 may include one or more processors (shown as 102a, 102b, ..., 102n in the figure) (the processor may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission module 106 for communication functions connected via wired and / or wireless networks. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, and a BUS bus. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0041] It should be noted that the aforementioned one or more processors and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be implemented wholly or partially as software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be wholly or partially integrated into any other element in the computer terminal 10. As involved in the embodiments of this application, the data processing circuits serve as processor control (e.g., selection of a variable resistor termination path connected to an interface).

[0042] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the application method of the enterprise knowledge base in this embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the above-mentioned application method of the enterprise knowledge base. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, enterprise intranets, local area networks, mobile communication networks, and combinations thereof.

[0043] The transmission module 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission module 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0044] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10.

[0045] It should be noted here that, in some optional embodiments, the above... Figure 1 The computer terminal shown may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium), or a combination of both hardware and software elements. It should be noted that... Figure 1 This is only one instance of a specific particular instance, and is intended to illustrate the types of components that may exist in the aforementioned computer terminal.

[0046] In the above operating environment, this application provides an embodiment of an application method for an enterprise knowledge base. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0047] Figure 2 This is a flowchart illustrating an application method for an enterprise knowledge base according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0048] Step S202: Determine the knowledge tree corresponding to the enterprise knowledge base, and determine the knowledge entries and knowledge tags of the knowledge tree. The knowledge tree is used to reflect the directory structure and hierarchical relationship of the enterprise knowledge base, the knowledge entries are used to reflect the unit knowledge information of the enterprise knowledge base, and the knowledge tags are used to reflect the knowledge type of the knowledge entries.

[0049] Step S204: Generate knowledge entry content using a text editor.

[0050] Step S206: Determine the review result of the knowledge entry content, and publish the corresponding knowledge entry if the review result is approved.

[0051] Step S208: If the knowledge entry is successfully published, query the knowledge tree based on the received query request and determine the target knowledge entry corresponding to the query request.

[0052] Step S210: Obtain the embedded link corresponding to the target knowledge entry, and call the target knowledge entry in the enterprise internal application based on the embedded link. The embedded link contains the target knowledge entry ID and access permission verification information.

[0053] Through the above steps S202 to S210, the goal of standardized management of internal enterprise knowledge resources is achieved, thereby realizing the technical effects of rapid retrieval, accurate authorization and wide application of internal enterprise knowledge, and thus solving the technical problems of complex enterprise knowledge management, difficult sharing, insufficient security and inaccurate authorization in related technologies.

[0054] Figure 3 This is a structural diagram of an enterprise knowledge base application system according to an embodiment of this application, such as... Figure 3 As shown, a comprehensive, multi-layered enterprise security knowledge base management system is intuitively outlined. Its functional modules are, in order, knowledge base planning, knowledge base construction, knowledge base publishing, knowledge base querying, and knowledge base application. The planning phase is responsible for building the knowledge tree architecture and defining knowledge attributes and authorization policies; the construction phase focuses on the creation and improvement of knowledge entries, using Markdown and intelligent agent recognition to improve efficiency; the publishing phase involves content and tag review to ensure the accuracy of knowledge and its accessibility to authorized users; the querying and application phases allow users to retrieve knowledge through tree structure or tag search, while watermarking and log auditing ensure the security of knowledge use, forming an innovative knowledge management process that covers the entire chain from knowledge planning to application and ensures security throughout.

[0055] The following combination Figure 3 The functional implementation logic described above provides a detailed explanation of steps S202 to S210.

[0056] In step S202 above, the aim is to design a knowledge tree framework that reflects the directory structure and hierarchical relationship of the enterprise knowledge base through the knowledge base planning module, and to clarify the knowledge entries and corresponding knowledge tags. The knowledge entries are used to represent each specific knowledge unit in the enterprise knowledge base, including its content, source and version, etc. The knowledge tags are used to describe the characteristics of the knowledge entries in detail, such as content theme, applicable group, application scenario, etc.

[0057] Optionally, the knowledge tree corresponding to the enterprise knowledge base is determined, including: designating the homepage of the enterprise knowledge base as the zero-level root node; designating the "must-know" and "must-do" sections and the operation and maintenance manual of the enterprise knowledge base as the first-level root nodes, wherein the "must-know" sections are publicly visible to all operation objects, and the operation and maintenance manual is visible only after authorization by the operation object; designating the knowledge entries of the enterprise knowledge base as leaf nodes, and determining the knowledge tags corresponding to the leaf nodes, wherein the knowledge tags include at least the content category tag, applicable object tag, and application carrier tag of the knowledge entry; and generating the knowledge tree based on the zero-level root node, the first-level root node, the leaf nodes, and the knowledge tags.

[0058] In this embodiment, the knowledge base is planned in a tree structure, similar to an enterprise organizational structure. Knowledge from different departments / professions serves as the first-level root node. For example, knowledge in the "must-know" and "must-do" categories and "operations manual" categories can both serve as first-level root nodes. "Must-know" and "must-do" categories are visible to all logged-in users, while "operations manual" categories require specific authorization. All knowledge entries serve as leaf nodes, which can be attached to their corresponding root nodes. To facilitate efficient searching of knowledge entries, three main categories of knowledge tags are added to the leaf nodes, covering dozens of specific dimensions such as content classification (e.g., consultation, problems, anomalies, configuration, analysis and improvement), applicable users (on-duty personnel, salespersons, account managers, mini-CEOs, installation and maintenance managers, etc.), and application carrier (centralized office platform, business system, backend database, privileged interface, etc.). The definition of knowledge tags facilitates knowledge searching and knowledge delivery in specific scenarios, and can be automatically identified by the application based on knowledge classification and specific content, and revised and confirmed by the creator and approver.

[0059] The specific steps for knowledge base planning are as follows:

[0060] S1: Construct the zero-level root node of the knowledge tree and name it the knowledge base homepage;

[0061] S2: Create a sub-root node (also called a first-level root node) under the knowledge base homepage. Shared knowledge within the enterprise is marked as "must-know" (access does not require additional authorization), while knowledge used within a department or profession is marked as "operation and maintenance manual" (access requires additional authorization).

[0062] S3: Under the first-level root node, if there is a real need, a second-level root node can be created, and so on. Alternatively, leaf nodes can be created directly and defined as knowledge entries.

[0063] S4: The root nodes at each level and the knowledge items attached to them are collectively referred to as the complete knowledge tree. The process of continuously expanding and maintaining the knowledge tree is the continuous deepening of knowledge base planning and application.

[0064] The overall process of knowledge base planning is as follows: Figure 4As shown, this process revolves around knowledge architecture planning and professional knowledge segmentation, aiming to establish an orderly and authorizable knowledge system that ensures reasonable knowledge classification and effective access control. First, the planning process begins by determining whether knowledge needs to be made public. If the knowledge content is suitable for public sharing, it is categorized as "must-know," meaning it will be visible to all enterprise portal users without additional authorization, promoting broad knowledge exchange and learning across the enterprise. Next, for knowledge that is not suitable for public sharing, it is inquired whether it needs further segmentation into professional knowledge areas. If so, the knowledge will be subdivided into knowledge items for specific professional fields, followed by professional planning, i.e., determining the professional affiliation of the knowledge and creating corresponding nodes for each professional field. Conversely, if professional segmentation is not required, node authorization is directly implemented, clarifying which roles or users can access the knowledge item, ensuring information security and relevance.

[0065] In step S204 above, the aim is to improve the content of knowledge entries through the knowledge base building module. For example, text editors such as Markdown are used to edit and format the content of knowledge entries, including but not limited to writing knowledge details, inserting charts, establishing links, and adding annotations, to ensure that knowledge entries present a good reading experience and information completeness.

[0066] In this embodiment, during the process of completing the knowledge tree planning and adding knowledge entries, one can choose to specify the collected files to automatically generate most of the content of the knowledge entries, or one cannot regenerate knowledge entries without specifying the collected files. The collected files refer to a collection of documents, materials, or information that has been collected, organized, and standardized within the enterprise. It is worth noting that regardless of whether collected files are specified, the final layout of the knowledge base page is completed using a Markdown tool.

[0067] Optionally, when not specifying the collected files to generate knowledge entry content, the process includes: editing the first data content of a knowledge entry in the enterprise knowledge base using a text editor, wherein the collected files represent files in the enterprise knowledge base that have passed review and are stored according to a standard format, and the first data content includes at least one of the following: text information, directory information, hyperlink information, and image information in the knowledge entry; previewing the format of the first data content using a text editor, and if the first data content conforms to the preview format, writing the first data content into a leaf node in the knowledge tree to obtain the knowledge entry content; or, if the first data content does not conform to the preview format, re-editing the first data content until it conforms to the preview format, and then writing the first data content into a leaf node in the knowledge tree to obtain the knowledge entry content. The specific steps are as follows:

[0068] S1: Use a Markdown tool to edit or copy the content of knowledge entries in the enterprise knowledge base, i.e., the first data content mentioned above.

[0069] S2: If necessary, use Markdown tools (for various headings) to mark the table of contents and subdirectories;

[0070] S3: If necessary, use Markdown tools (reference links) to mark hyperlinks;

[0071] S4: If necessary, use the Markdown tool (add image) to insert the prepared image;

[0072] S5: Use Markdown tools to process content in other formats;

[0073] S6: Use a Markdown tool (preview HTML) to display the first data content. If there is any content that does not conform to the preview format, repeat some of the above steps to re-edit it.

[0074] S7: Store the knowledge entry ID, Markdown edit content, HTML-formatted text, and other operation information in a MySQL database, mark it as pending review, and send an SMS to the relevant reviewers.

[0075] Optionally, when generating knowledge entry content from a specified aggregated file, the process includes: identifying the aggregated file using an intelligent agent tool, and editing the second data content in the aggregated file using a text editor if the aggregated file meets basic format requirements; previewing the format of the second data content using a text editor, and writing the second data content into a leaf node in the knowledge tree if the second data content conforms to the preview format, thus obtaining the knowledge entry content; or, if the second data content does not conform to the preview format, re-editing the second data content until it conforms to the preview format, and then writing the second data content into a leaf node in the knowledge tree, thus obtaining the knowledge entry content. The specific steps are as follows:

[0076] S1: Select the uploaded collected files, and use existing intelligent agent recognition tools (such as connecting to an AI intelligent agent platform) to determine whether the collected files meet the basic format requirements such as text and images. If they meet the requirements, edit the second data content; otherwise, report that it cannot be processed.

[0077] S2: Split the collected files into two types: text (including hyperlinks) and images (including tables). The text is placed directly in the Markdown editing area, and the recognized image files are uploaded to the specified directory on the FTP server and the path of each image is obtained.

[0078] S3: Place the image identifier in the relevant position in the markdown editing area based on the original position of each image;

[0079] S4: Use Markdown tools (as before) to format the table of contents, text, hyperlinks, images, etc.

[0080] S5: Display the second data content. If there is content that does not conform to the preview format, repeat some of the above steps to re-edit it.

[0081] S6: Use a Markdown tool (preview HTML) to display the second data content again. If there is any content that does not conform to the preview format, repeat some of the above steps to re-edit it.

[0082] S7: Store the knowledge entry ID, Markdown edit content, HTML-formatted text, and other operation information in a MySQL database, mark it as pending review, and send an SMS to the relevant reviewers.

[0083] The overall process of knowledge base construction is as follows: Figure 5 As shown in the flowchart, this process highlights the strategy of balancing intelligence and standardization in the knowledge entry arrangement process. First, the root node, leaf nodes, and knowledge entries are configured. Then, it determines whether the knowledge entry has been collected. For collected files, the process can be simplified by directly uploading and using an intelligent agent recognition tool to parse the content. For uncollected knowledge entries, the process shifts to manual editing, covering configuration of various aspects such as title text, forms, links, images / attachments, etc. Finally, after confirming the knowledge entry, it is sent to the knowledge entry review module.

[0084] In step S206 above, the purpose is to review the content and permissions of the edited knowledge entries through the knowledge publishing module, and also to revise and reconfirm the knowledge tags, and officially publish the approved knowledge entries for authorized users to access and call.

[0085] Optionally, the review result of the knowledge entry content is determined, and the corresponding knowledge entry is published if the review result is approved. This includes: obtaining the knowledge entry content to be reviewed; receiving the review result obtained by the review object in sequentially reviewing the data content, knowledge entry naming, and knowledge tags of the knowledge entry content, wherein the review object has review permissions, and the review permissions include review identifiers used to review knowledge tree nodes; and publishing the knowledge entry storing the knowledge entry content if the review result is approved, wherein the published knowledge entry is used to provide a basis for querying. The specific steps are as follows:

[0086] S1: Reviewers with review permissions (including review identifiers used to review knowledge tree nodes) can view the knowledge base review pending list in the enterprise portal after receiving a review reminder SMS.

[0087] S2: Use HTML formatted text to view the data content and knowledge entry naming display of the knowledge base. If you find any problems, write down the reasons and click "approved" to return to the knowledge entry editor for revision.

[0088] S3: If the knowledge base data content is verified to be correct, continue to check whether the selection of the three major categories of knowledge tags is appropriate. If not, adjustments or additions can be made.

[0089] S4: Once the knowledge base content and tags are confirmed, they can be approved and the corresponding knowledge entries can be published. The published knowledge can then be queried and accessed by third-party APIs.

[0090] The overall process of publishing a knowledge base is as follows: Figure 6 As shown, this process ensures that all knowledge entries undergo rigorous quality checks and access control before being made available to users. The process begins with a suitability assessment of the knowledge base entries, involving a thorough review of the entry's name, category tags, object tags, application tags, etc., to confirm whether they accurately represent the core elements and application scenarios of the knowledge. If each step passes the review, the knowledge entry moves to the next stage; if any issue arises at any stage, adjustments are made until the release standards are met. Furthermore, the appropriateness of user roles is considered, confirming which specific roles or users can access the knowledge entry. Finally, only after all suitability checks have passed is the knowledge entry officially released for authorized users to access.

[0091] In step S208 above, the aim is to search in the knowledge tree through the knowledge base query module. For example, a general browsing query can be performed based on the hierarchical browsing of the knowledge tree and the directory location of knowledge items. Alternatively, a search can be performed based on the selection of the three major categories of knowledge tags and the search of keywords, thereby locating the target knowledge item that best matches the query request.

[0092] Optionally, querying the knowledge tree based on the received query request includes: browsing the knowledge tree layer by layer from the query interface according to the query request, or querying the knowledge tree based on keywords in the query request, or querying the knowledge tree based on knowledge tags corresponding to the query request, to obtain the target knowledge entry corresponding to the query request; displaying the target knowledge entry and adding a digital watermark, wherein the digital watermark includes at least the employee ID, IP address, and timestamp information of the queried object. The specific steps are as follows:

[0093] S1: Construct an independent knowledge tree query interface, which displays the root and leaf nodes of the entire knowledge base that can be accessed based on the queryer's role permissions (combining role and account permissions);

[0094] S2: Users can click the root node to view the sub-knowledge base directory and click the page node to view the specific knowledge entry content as needed;

[0095] S3: If a specific knowledge base cannot be found through step S2, you can search directly by keywords. The search results will be highlighted and all knowledge items that meet the conditions will be displayed in a list. When you select a knowledge item to display the knowledge base, it will automatically locate the first position where the keyword appears.

[0096] S4: If you still cannot find a specific knowledge base or there are too many search results after step S3, you can combine the three major categories of knowledge tags for comprehensive filtering (if there are no results, you need to remove part or all of the keyword content) to finally get the target knowledge item you need.

[0097] S5: The display of target knowledge items uses native JavaScript methods to add an underlying digital watermark to the front-end interface. The digital watermark content includes the operator's employee ID (an operator ID does not exist if the user is not logged into the knowledge portal), IP address, and current time, etc. It is then displayed in parallel in multiple positions on the screen to effectively prevent unauthorized screenshots of information.

[0098] S6: Users who log in through the knowledge portal can bookmark the target knowledge items they find for easy access later. Before bookmarking, they can open the button to get the hyperlink address of the specified knowledge item.

[0099] S7: For a specific knowledge item, you can also save it as a knowledge document. The format can be PDF or WORD. All exported files will have a digital watermark added. For example, you can use methods such as html2canvas.js, jspdf.debug.js, and jquery.wordexport.js to generate files in the specified format.

[0100] The overall process of knowledge base query is as follows: Figure 7 As shown, this demonstrates how users can efficiently locate the information they need through different query methods. Overall, users can adopt a tree-based browsing approach, exploring the knowledge tree hierarchically. Whether browsing the knowledge tree from the top-level knowledge base homepage or delving into specific child nodes, targeted knowledge retrieval is possible. Furthermore, the system provides a tag-based browsing function, allowing users to filter and query according to three categories of tags (content category, target audience, and application carrier). Combining keyword selection and related person selection further refines the query results, ensuring accurate information matching. When the query results meet user needs, multiple utilization methods are provided, including direct viewing of the query results, saving the results as a document, bookmarking links for quick access later, and saving the results to personal learning materials, fully considering the combination of knowledge application and personal learning needs.

[0101] In step S210 above, the aim is to generate an embedded link containing the ID and access permission verification information for the located target knowledge entry through the knowledge base application module. Subsequently, users or internal enterprise applications can call the content of the knowledge entry through this link. The result of the call is completely consistent with the result of the knowledge base query, thereby realizing cross-application sharing of knowledge.

[0102] In this embodiment, an access interface for knowledge entries is provided externally via an HTTP GET request. This interface directly returns a string in MARKDOWN format, facilitating parsing and display by third-party systems. When calling the interface, the caller's employee ID information is required. The system verifies the caller's knowledge base access permissions based on the employee ID, ensuring that only authorized users can access specific knowledge. This mechanism not only strengthens knowledge security control but also simplifies the integration of the knowledge base with other enterprise service platforms, such as the enterprise's front-line service platform and digital task platform. Furthermore, the knowledge base is already organically integrated with the enterprise's front-line service platform and digital task platform. All systems use a unified employee ID login, meaning the knowledge base can seamlessly identify the caller's identity and automatically determine whether they have permission to access specific knowledge based on that identity information. Even without obtaining the employee ID, the system still allows access to publicly available knowledge entries marked as "essential knowledge," ensuring unimpeded sharing of basic knowledge while maintaining the security of the enterprise's core knowledge.

[0103] The overall process of knowledge base application is as follows: Figure 8 The diagram illustrates the process of accessing links to enterprise security knowledge base entries, as well as the verification and application of access permissions in different scenarios. First, the system retrieves the knowledge entry link and determines whether the user accesses the knowledge base through a unified knowledge portal account. For users with a unified account, the system obtains the account's knowledge role authorization, further confirming the user's role and corresponding knowledge access permissions to decide whether to display the specific knowledge content. If the user does not access the knowledge base through a unified account, the process assigns a general knowledge role and, after confirming whether authorization is required, displays the knowledge or explicitly informs the user that they do not have access permissions.

[0104] In this embodiment of the application, the security of the enterprise knowledge base mainly includes the following two aspects:

[0105] 1) Maintenance Authorization: Fine-grained access control is achieved through the combination of roles and knowledge tree nodes. Specifically, knowledge base maintainers must first possess a specific role, and then obtain authorization for the knowledge tree nodes under that role. This hierarchical authorization mechanism allows for customized settings of knowledge base maintenance and approval permissions, ensuring that each operation is performed only by personnel with the corresponding permissions, thereby achieving the principle of least privilege and enhancing the security of internal knowledge base management.

[0106] 2) Application Security: Differentiated access strategies are adopted for knowledge content of different natures. For general knowledge and skills, all enterprise portal users can access and collect it without additional authorization, promoting the free flow and sharing of knowledge. However, manuals related to internal operations and maintenance require strict authorization, either based on roles or directly assigned to specific users. To prevent the illegal leakage of knowledge content, the system automatically adds digital watermarks to knowledge query results, including the operator's employee ID, IP address, and operation time. In addition, all knowledge base query and export activities are recorded in detail, forming a log for subsequent log auditing and traceability, ensuring the legality and compliance of every access behavior.

[0107] Optionally, the above method further includes: obtaining login logs corresponding to the operation object, query logs corresponding to the query object, and export logs corresponding to the knowledge entries; auditing the login logs, query logs, and export logs according to a preset time period to identify unauthorized authorization behavior. The specific steps are as follows:

[0108] S1: Regardless of whether the client is logged into the knowledge base portal, as long as it accesses the knowledge tree, the corresponding IP, current time, terminal information, etc. are recorded. At the same time, the detection code deployed on the server side is used to confirm whether the client has the ability to connect to the internal and external networks (by requesting an external network resource via AJAX and judging whether the external network can be accessed based on whether the external network returns a status of 200) and the identifier is recorded. If the client logs in using an employee ID, the login employee ID is also recorded, forming a unified login log that is stored in MySQL.

[0109] S2: Unlogged users can only access the essential knowledge and skills section of the knowledge tree. Logged users, on the other hand, are granted access to knowledge tree nodes based on their employee ID role and directly authorized knowledge tree. If a knowledge item is accessed, the access status of that knowledge item is recorded and a unified query log is stored in MySQL.

[0110] S3: If the results of a knowledge entry are saved, the export status of that knowledge entry (including terminal IP, operator ID, operation time, file format docx, pdf, etc.) is recorded and a unified export log is stored in MySQL.

[0111] S4: Regularly and automatically audit the above three types of logs (login logs, query logs, and export logs). For IPs with internal and external network interconnection identifiers, a log list is generated monthly for manual confirmation by the cybersecurity department. The query and export of the dedicated operation / maintenance manual are classified by profession and are manually audited by the business or maintenance management department to confirm whether the scope and personnel of knowledge use are reasonable.

[0112] S5: For any unauthorized authorizations discovered during the audit, the authorizations can be revoked to ensure the necessity and minimum level of authorization.

[0113] The overall process of knowledge base application is as follows: Figure 9 The diagram illustrates the security control strategies implemented at different operational stages of the knowledge base. Security controls are integrated from the knowledge base planning stage, ensuring that the knowledge tree construction follows the principle of least privilege. Precise authorization of roles and nodes restricts who can edit or manage specific knowledge. During the knowledge base construction process, security controls are further refined, ensuring that uploaded collected knowledge meets security standards and embedding necessary security identifiers during content generation. Security controls during the knowledge base publishing stage focus on content review, ensuring that knowledge entries undergo rigorous examination, including the accuracy of the content, the applicability of tags, and reconfirmation of access permissions. During knowledge base queries, security controls add digital watermarks to the knowledge entry display interface and record operator information in real time, including employee ID, IP address, and operation time, effectively preventing unauthorized copying or screenshotting. Furthermore, the system records and audits query logs to ensure all access behaviors are traceable, further enhancing security. In the knowledge base application stage, security controls cover the recording and analysis of interface call logs and the regular auditing of important knowledge query logs, ensuring that the application of the knowledge base is within the authorized scope, and that any unauthorized access or improper use of the knowledge base can be detected and dealt with promptly.

[0114] This application innovatively proposes a method and application for constructing an enterprise knowledge base. Its core lies in designing a standardized knowledge management system based on a "knowledge tree," combined with intelligent tools and security control strategies. This effectively solves key problems encountered in traditional enterprise knowledge management, such as difficulties in sharing, chaotic authorization, slow updates, and weak security. Through the "knowledge tree" structure, clear classification and hierarchical management of knowledge are achieved, facilitating rapid retrieval and precise delivery. Utilizing Markdown markup language and intelligent agent recognition tools significantly improves the efficiency of knowledge entry creation and updating, reduces human error, and achieves intelligent arrangement of knowledge content. Furthermore, three types of knowledge tags are introduced, including content classification, applicable objects, and application carriers, providing multi-dimensional filtering criteria for knowledge retrieval and enhancing the usability and personalized services of the knowledge base.

[0115] In terms of security control, a dual authorization mechanism of roles and knowledge tree nodes is adopted to ensure the minimization and optimization of knowledge access permissions, preventing unauthorized access. The application of digital watermarking technology, along with automatic and manual auditing of logs, effectively enhances the security of the knowledge base, prevents the leakage of core corporate knowledge, and provides traceability measures after unauthorized use. Furthermore, knowledge base queries and applications are implemented through unique links and standardized interfaces, which not only facilitates knowledge retrieval and integration but also further strengthens access permission verification, ensuring the unity of widespread knowledge base utilization and secure control.

[0116] In summary, this application, through its unique knowledge management framework, intelligent editing tools, granular access control, and stringent security measures, provides an efficient, secure, and scalable solution for enterprise knowledge management. It significantly improves knowledge sharing efficiency, employee productivity, and enterprise information security, plays a major role in promoting the standardization and normalization of knowledge management within enterprises, and lays a solid foundation for building a smart enterprise.

[0117] According to embodiments of this application, an application apparatus for an enterprise knowledge base is provided. It should be noted that the application apparatus for the enterprise knowledge base in this application embodiment can be used to execute the application method for an enterprise knowledge base provided in this application embodiment. The application apparatus for the enterprise knowledge base provided in this application embodiment is described below.

[0118] Figure 10 This is a structural diagram of an application device for an enterprise knowledge base provided according to an embodiment of this application. For example... Figure 10 As shown, the device includes:

[0119] The determination module 1000 is used to determine the knowledge tree corresponding to the enterprise knowledge base, and to determine the knowledge entries and knowledge tags of the knowledge tree. The knowledge tree is used to reflect the directory structure and hierarchical relationship of the enterprise knowledge base, the knowledge entries are used to reflect the unit knowledge information of the enterprise knowledge base, and the knowledge tags are used to reflect the knowledge type of the knowledge entries.

[0120] Module 1002 is used to generate knowledge entry content through a text editor;

[0121] The publishing module 1004 is used to determine the review result of the knowledge entry content and publish the corresponding knowledge entry if the review result is approved.

[0122] The query module 1006 is used to query the knowledge tree based on the received query request and determine the target knowledge item corresponding to the query request when the knowledge item is successfully published.

[0123] Application module 1008 is used to obtain the embedded link corresponding to the target knowledge item and call the target knowledge item in the enterprise internal application based on the embedded link. The embedded link contains the target knowledge item ID and access permission verification information.

[0124] Through the determination, generation, publishing, query, and application modules in the aforementioned enterprise knowledge base application device, the goal of standardized management of internal enterprise knowledge resources is achieved. This enables the technical effects of rapid retrieval, accurate authorization, and widespread application of internal enterprise knowledge, thereby solving the technical problems of complex enterprise knowledge management, difficult sharing, insufficient security, and inaccurate authorization in related technologies.

[0125] In the enterprise knowledge base application device provided in this application embodiment, the determining module is further configured to determine the homepage of the enterprise knowledge base as the zero-level root node; determine the "should-know" and "should-be-known" sections and the operation and maintenance manual of the enterprise knowledge base as the first-level root nodes, wherein the "should-know" sections are publicly visible to all operation objects, and the operation and maintenance manual is visible only after authorization by the operation object; determine the knowledge entries of the enterprise knowledge base as leaf nodes, and determine the knowledge tags corresponding to the leaf nodes, wherein the knowledge tags include at least the content classification tag, the applicable object tag, and the application carrier tag of the knowledge entry; and generate a knowledge tree based on the zero-level root node, the first-level root node, the leaf nodes, and the knowledge tags.

[0126] In the enterprise knowledge base application device provided in this application embodiment, the generation module is further configured to edit the first data content of the knowledge entries in the enterprise knowledge base using a text editor without specifying the collected files to generate the knowledge entry content. The collected files represent files in the enterprise knowledge base that have passed review and are stored according to a standard format. The first data content includes at least one of the following: text information, directory information, hyperlink information, and image information in the knowledge entry. The first data content is previewed using a text editor, and if it conforms to the preview format, it is written into a leaf node in the knowledge tree to obtain the knowledge entry content. Alternatively, if the first data content does not conform to the preview format, the first data content is re-edited until it meets the preview format, and then written into a leaf node in the knowledge tree to obtain the knowledge entry content.

[0127] In the enterprise knowledge base application device provided in this application embodiment, the generation module is further configured to, when generating knowledge entry content from a specified collected file, identify the collected file using an intelligent agent tool, and, if the collected file meets the basic format requirements, edit the second data content in the collected file using a text editor; preview the format of the second data content using the text editor, and, if the second data content conforms to the preview format, write the second data content into the leaf node of the knowledge tree to obtain the knowledge entry content; or, if the second data content does not conform to the preview format, re-edit the second data content until it meets the preview format, and then write the second data content into the leaf node of the knowledge tree to obtain the knowledge entry content.

[0128] In the enterprise knowledge base application device provided in this application embodiment, the publishing module is further used to obtain the knowledge entry content to be reviewed; receive the review result obtained by the review object in sequence reviewing the data content, knowledge entry naming and knowledge tags of the knowledge entry content, wherein the review object has review authority, and the review authority includes the review identifier for reviewing knowledge tree nodes; if the review result is that the review is passed, publish the knowledge entry storing the knowledge entry content, wherein the published knowledge entry is used to provide a basis for querying.

[0129] In the enterprise knowledge base application device provided in this application embodiment, the query module is further used to browse and query the knowledge tree layer by layer from the query interface according to the query request, or to query the knowledge tree according to the keywords in the query request, or to query the knowledge tree according to the knowledge tags corresponding to the query request, to obtain the target knowledge entry corresponding to the query request; display the target knowledge entry and add a digital watermark, wherein the digital watermark includes at least the employee number, IP address and timestamp information of the query object.

[0130] The enterprise knowledge base application device provided in this application embodiment also includes an audit module 1010, which is used to obtain login logs corresponding to the operation object, query logs corresponding to the query object, and export logs corresponding to the knowledge entries; and to audit the login logs, query logs, and export logs according to a preset time period to identify unauthorized authorization behavior.

[0131] This application also provides an electronic device, including: a memory and a processor, wherein the memory is used to store program instructions; and the processor is connected to the memory and used to execute the application method for implementing the above-mentioned enterprise knowledge base.

[0132] It should be noted that the aforementioned electronic equipment is used to perform Figure 2 The application method of the enterprise knowledge base shown above also applies to this electronic device, and will not be repeated here.

[0133] This application also provides a non-volatile storage medium that includes a stored computer program, wherein the device containing the non-volatile storage medium executes the above-mentioned enterprise knowledge base application method by running the computer program.

[0134] It should be noted that the aforementioned non-volatile storage media is used for execution. Figure 2 The application method of the enterprise knowledge base shown above also applies to this non-volatile storage medium, and will not be repeated here.

[0135] This application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the above-described method for applying an enterprise knowledge base.

[0136] It should be noted that the above-mentioned computer program product is used to execute... Figure 2 The application method of the enterprise knowledge base shown above also applies to this computer program product, and will not be repeated here.

[0137] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0138] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0139] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0140] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0141] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0142] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0143] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for applying an enterprise knowledge base, characterized in that, include: A knowledge tree corresponding to the enterprise knowledge base is determined, and knowledge entries and knowledge tags of the knowledge tree are determined. The knowledge tree is used to reflect the directory structure and hierarchical relationship of the enterprise knowledge base, the knowledge entries are used to reflect the unit knowledge information of the enterprise knowledge base, and the knowledge tags are used to reflect the knowledge type of the knowledge entries. Generate knowledge entry content using a text editor; Determine the review result of the knowledge entry content, and publish the corresponding knowledge entry if the review result is approved; If the knowledge entry is successfully published, the knowledge tree is queried according to the received query request, and the target knowledge entry corresponding to the query request is determined. Obtain the embedded link corresponding to the target knowledge entry, and invoke the target knowledge entry in the enterprise internal application based on the embedded link, wherein the embedded link contains the target knowledge entry ID and access permission verification information.

2. The method according to claim 1, characterized in that, Determine the knowledge tree corresponding to the enterprise knowledge base, including: The homepage of the enterprise knowledge base is designated as the zero-level root node; The "should-know" and "should-be-skilled" knowledge base and the "operation and maintenance manual" are identified as first-level root nodes. The "should-know" and "should-be-skilled" knowledge base is publicly visible to all operation objects, and the "operation and maintenance manual" is visible only after authorization by the operation object. The knowledge entries in the enterprise knowledge base are identified as leaf nodes, and the knowledge tags corresponding to the leaf nodes are determined. The knowledge tags include at least the content category tag, the applicable object tag, and the application carrier tag of the knowledge entry. The knowledge tree is generated based on the zero-level root node, the first-level root node, the leaf nodes, and the knowledge tags.

3. The method according to claim 2, characterized in that, Generate knowledge entry content using a text editor, including: Without specifying an aggregated file to generate the knowledge entry content, the first data content of the knowledge entry in the enterprise knowledge base is edited using the text editor. The aggregated file is used to represent a file in the enterprise knowledge base that has been reviewed and stored in a standard format. The first data content includes at least one of the following: text information, directory information, hyperlink information, and image information in the knowledge entry. The first data content is previewed using the text editor, and if the first data content conforms to the preview format, the first data content is written into the leaf node of the knowledge tree to obtain the knowledge entry content. Alternatively, if the first data content does not conform to the preview format, the first data content is edited again until it meets the preview format, and then the first data content is written into the leaf node of the knowledge tree to obtain the knowledge entry content.

4. The method according to claim 3, characterized in that, Generate knowledge entry content using a text editor, including: When the knowledge entry content is generated from the specified collected file, the collected file is identified by the intelligent agent tool, and the second data content in the collected file is edited by the text editor if the collected file meets the basic format requirements. The second data content is previewed using the text editor, and if the second data content conforms to the preview format, the second data content is written into the leaf node of the knowledge tree to obtain the knowledge entry content. Alternatively, if the second data content does not conform to the preview format, the second data content is re-edited until it meets the preview format, and then the second data content is written into the leaf node of the knowledge tree to obtain the knowledge entry content.

5. The method according to claim 1, characterized in that, Determine the review result of the knowledge entry content, and publish the corresponding knowledge entry if the review result is approved, including: Retrieve the content of knowledge entries pending review; The system receives the review results obtained by the reviewing object sequentially reviewing the data content, knowledge entry name, and knowledge tag of the knowledge entry content. The reviewing object has review permissions, and the review permissions include a review identifier for reviewing the knowledge tree node. If the review result is approved, the knowledge entry storing the knowledge entry content is published, wherein the published knowledge entry is used to provide a basis for querying.

6. The method according to claim 1, characterized in that, Querying the knowledge tree based on the received query request includes: The query can be performed by browsing the knowledge tree layer by layer from the query interface according to the query request, or by querying the knowledge tree according to the keywords in the query request, or by querying the knowledge tree according to the knowledge tags corresponding to the query request, to obtain the target knowledge item corresponding to the query request. Display the target knowledge entry and add a digital watermark, wherein the digital watermark includes at least the employee ID, IP address and timestamp information of the queried object.

7. The method according to claim 1, characterized in that, The method further includes: Obtain the login log corresponding to the operation object, the query log corresponding to the query object, and the export log corresponding to the knowledge item; The login logs, query logs, and export logs are audited according to a preset time period to identify unauthorized authorization behaviors.

8. An application device for an enterprise knowledge base, characterized in that, include: The determination module is used to determine the knowledge tree corresponding to the enterprise knowledge base, and to determine the knowledge entries and knowledge tags of the knowledge tree. The knowledge tree is used to reflect the directory structure and hierarchical relationship of the enterprise knowledge base, the knowledge entries are used to reflect the unit knowledge information of the enterprise knowledge base, and the knowledge tags are used to reflect the knowledge type of the knowledge entries. The generation module is used to generate knowledge entry content using a text editor; The publishing module is used to determine the review result of the knowledge entry content, and publish the corresponding knowledge entry if the review result is approved; The query module is used to query the knowledge tree based on the received query request when the knowledge entry is successfully published, and to determine the target knowledge entry corresponding to the query request. The application module is used to obtain the embedded link corresponding to the target knowledge entry and to call the target knowledge entry in the enterprise internal application based on the embedded link, wherein the embedded link contains the target knowledge entry ID and access permission verification information.

9. An electronic device, characterized in that, include: A memory and a processor, wherein the memory is used to store program instructions; The processor, connected to the memory, is used to execute the application method for implementing the enterprise knowledge base according to any one of claims 1 to 7.

10. A non-volatile storage medium, characterized in that, The non-volatile storage medium includes a stored computer program, wherein the device containing the non-volatile storage medium executes the application method of the enterprise knowledge base according to any one of claims 1 to 7 by running the computer program.

11. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the application method of the enterprise knowledge base as described in any one of claims 1 to 7.

Images