An enterprise knowledge management system

Abstract

The present invention discloses an enterprise knowledge management system, including a knowledge precipitation subsystem, a document editing subsystem and a business collaboration subsystem; the knowledge precipitation subsystem is used to create and manage several knowledge bases under the team of the enterprise space; the document editing subsystem is used to monitor the document collaborative editing events initiated by users, and display the user information and document update information in real time on the hypertext editing page of each collaborative user; the business collaboration subsystem is used to monitor @ function initiation events and document marking events, store and / or push the @ information after processing, and record the marked document information. The present invention builds an exclusive team and an exclusive knowledge base to aggregate and precipitate the knowledge assets of the enterprise, thereby realizing the traceability and inheritance of knowledge; it enables users to collaboratively edit documents online in a browser; it enables in-depth collaborative collaboration through document information in the business process, real-time discussion, and cooperative office work, thereby improving office efficiency.

Description

Technical Field

[0001] The present invention belongs to the technical field of knowledge management, and in particular relates to an enterprise knowledge management system. Background Art

[0002] Knowledge is the information humans acquire through practice, understanding and describing the patterns and laws governing nature, society, and thought. It originates from human practice, feeds back into it, and guides it. Knowledge is a product of human practice in understanding time and transforming the world. Knowledge is a subset of information, encompassing the understanding, grasping, and describing the patterns and laws governing nature, society, and thought. Description is the key difference between knowledge and cognition: anything understood can be described. Once described, knowledge must be stored in a physical medium for circulation, accumulation, exchange, development, exploitation, and utilization. Knowledge management is defined as the process of building a quantitative and qualitative knowledge system within an organization. This system allows information and knowledge within the organization to continuously feed back into the knowledge system through processes such as acquisition, creation, sharing, integration, recording, storage, updating, and innovation. This creates a continuous cycle of accumulated individual and organizational knowledge, forming a cycle of organizational wisdom. This serves as intellectual capital for management and application within an organization, helping businesses make informed decisions and adapt to market changes. In short, knowledge management is the planning and management of knowledge, its creation process, and its application.

[0003] With the continuous development of enterprise information systems in my country and the continuous improvement of informatization, enterprises' ability to collect, transmit, and store information is also increasing. Vast amounts of information are stored in various databases. However, for the vast majority of enterprises, the ability of management information systems to utilize and process this information is still limited. While management information systems have expanded the scope of information collection and improved the efficiency and accuracy of management information transmission, which can improve the scientific level of enterprise management to a certain extent, they have failed to enhance enterprises' knowledge management, innovation, and decision-making capabilities. As a result, there is a phenomenon of abundant information but scarce knowledge. The main reasons for this phenomenon are: first, the serious problem of information silos: different teams in an enterprise may use different tools, resulting in abnormal information fragmentation. This makes it difficult for teams to quickly and effectively share information, making it difficult to effectively utilize knowledge; second, the serious problem of information fragmentation: much valuable information is generated in daily work meetings or group chats. This fragmented information makes it impossible to form a sound knowledge system, and users who do not participate in meetings or group chats cannot access this knowledge; third, the serious problem of information loss: in daily work, important enterprise documents may be lost along with events such as project completion and employee departure, resulting in the inability to continue subsequent work and a high level of repetitive work.

[0004] Therefore, in order to solve the above problems, it is urgent to propose an effective knowledge management system to improve the daily work efficiency of enterprises. Summary of the Invention

[0005] The purpose of the present invention is to provide an enterprise knowledge management system for solving at least one technical problem existing in the prior art.

[0006] In order to achieve the above object, the present invention adopts the following technical solutions:

[0007] The present invention provides an enterprise knowledge management system, which adopts a BS architecture. The client accesses the server through a browser, and the browser is embedded with a hypertext editor. The system includes a knowledge precipitation subsystem, a document editing subsystem, and a business collaboration subsystem.

[0008] The knowledge precipitation subsystem is used to create different enterprise spaces according to different business domains of the enterprise, create different business teams for each enterprise space, and create and manage several knowledge bases for each business team, wherein the knowledge base is used to classify and manage team knowledge;

[0009] The document editing subsystem is used to monitor the document collaborative editing events initiated by users using a hypertext editor, obtain user information and document update information of the document collaborative editor, and display the user information and document update information in real time on the hypertext editing page of each collaborative user to realize document collaborative editing;

[0010] The business collaboration subsystem is used to use the hypertext editor to monitor @ function initiation events and document marking events. When the @ function initiation event is monitored, the server side obtains the @ information and stores and / or pushes the @ information after processing. When the document marking event is monitored, the server side records the marked document information for other users to obtain and join the discussion of the document marking information.

[0011] In one possible design, the enterprise knowledge management system also includes a knowledge sharing subsystem, which is used to create a learning space. The learning space is used for course users to upload learning projects. The learning projects are configured with learning permissions and learning paths so that users with learning permissions can enter the learning space to study courses.

[0012] In one possible design, the enterprise knowledge management system further includes a knowledge application subsystem, which is used to extract and process required knowledge from the knowledge precipitation subsystem according to enterprise needs to generate knowledge application files.

[0013] In one possible design, the knowledge sedimentation subsystem includes a space creation module, a team creation module, and a knowledge base module;

[0014] The space creation module is used to classify the business domains of the enterprise and create corresponding enterprise spaces for different business domains;

[0015] The team creation module is used to create multiple business teams based on the organizational relationships under each enterprise space and manage team information;

[0016] The knowledge base module is used to create several knowledge bases for each business team, set knowledge base permissions, and classify and manage team knowledge based on the knowledge bases, wherein several documents are stored in the knowledge bases.

[0017] In a possible design, the document editing subsystem includes a monitoring module, a message receiving module, and a display module. The monitoring module and the display module are deployed in a browser, and the message receiving module is deployed on a server.

[0018] The monitoring module is used to monitor the document collaborative editing event initiated by the user using the hypertext editor, and send the event message to the message receiving module;

[0019] The message receiving module is used to receive event messages, record user information and / or document update information in the current event, and synchronize the user information and / or document update information to each user's client;

[0020] The display module is used to receive user document editing operations, user information and / or document update information using a hypertext editor, and display the user information and / or document update information on the user's hypertext editing page.

[0021] In one possible design, the monitoring module includes a first monitoring unit and a second monitoring unit;

[0022] The first monitoring unit is used to monitor the collaborative instance creation event using a hypertext editor, and when monitoring, sends the instance creation message to the message receiving module, so that the message receiving module creates a message record according to the instance and returns the current collaborative user information to the client where each user is located;

[0023] The second monitoring unit is used to monitor document content change events, and when monitored, sends a content change event message to the message receiving module, so that the message receiving module records and returns the input location information of the current collaborative user and the document update information to each user's client according to the content change event message.

[0024] In one possible design, the business collaboration subsystem includes a business request module and a business discussion module;

[0025] The service request module is used to monitor @ function initiation events using a hypertext editor. When a @ function initiation event is monitored, the service request module requests the server to obtain @ user list information and / or @ document information. The server stores the @ user list and context information and pushes them to the client of the @ user, or associates the @ document with the original document and stores it.

[0026] The business discussion module is used to use a hypertext editor to monitor document marking events. When a document marking event is monitored, the discussion area is activated so that the document marking user can enter the discussion area to discuss the document marking information. At the same time, the server records the document marking information and user discussion information so that other users can obtain and join the discussion of the document marking information.

[0027] In one possible design, the business collaboration subsystem also includes a document synchronization module, which is used for the second user to synchronize the first user's knowledge document to the knowledge base of the space to which the second user belongs, wherein the first user is a user of the first space and has created a knowledge document in the first knowledge base of the first space, and the second user is a user of the second space and has the authority to access the first knowledge base.

[0028] In one possible design, the business discussion module includes a document marking monitoring unit, a discussion area activation unit, and a document marking information storage unit;

[0029] The document mark monitoring unit is used to monitor the user's marking event on the current document, and when a marking event is monitored, a discussion button pops up at the marking position;

[0030] The discussion area activation unit is used to receive a user's click operation on the discussion button and send a discussion initiation pop-up window to the user's client, so that the user can enter the discussion area through the pop-up window to discuss the document markup information;

[0031] The document marking information storage unit is used to send the marked document ID, marked content and user's discussion information to the server for storage after the user publishes discussion information, so that other users can obtain the document discussion record on the server according to the document marking.

[0032] In a possible design, the document synchronization module is further configured to send a prompt message to the client where the first user is located when receiving comment information and / or discussion information of the knowledge document.

[0033] Beneficial effects:

[0034] The present invention creates different enterprise spaces through the knowledge precipitation subsystem, creates different business teams for each enterprise space, and creates and manages several knowledge bases for each business team. The knowledge base is used to classify and manage team knowledge, so that each team member can build a dedicated team and a dedicated knowledge base. The team knowledge is stored based on the knowledge base, and all knowledge can be shared and communicated online based on the browser, which greatly improves the convenience of users uploading, acquiring and sharing knowledge. At the same time, by storing knowledge documents in a dedicated knowledge base, the traceability and inheritance of knowledge can be achieved, preventing the loss of important files.

[0035] The document editing subsystem uses a hypertext editor to monitor document collaborative editing events initiated by users, obtains user information and document update information for collaborative editing, and displays the user information and document update information in real time on the hypertext editing page of each collaborative user, thereby realizing document collaborative editing. This eliminates the need for independent collaborative editing tools. At the same time, by synchronizing collaborative information and updating documents in real time, it can effectively achieve consistency in user operation intentions and improve the user's office experience.

[0036] The business collaboration subsystem uses a hypertext editor to monitor @ function-initiated events and document marking events. When an @ function-initiated event is monitored, the server obtains the @ information, processes the @ information, and stores and / or pushes it. When a document marking event is monitored, the server records the marked document information for other users to obtain and join in the discussion of the document marking information. This enables collaborative collaboration, real-time discussion, and cooperative office work through document information in the business process, thereby improving office efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 is a structural block diagram of the enterprise knowledge management system in this embodiment;

[0038] Figure 2 Schematic diagram of the architecture of the knowledge precipitation subsystem in this embodiment;

[0039] Figure 3 This is a working principle diagram of the service request module in this embodiment;

[0040] Figure 4 This is a working principle diagram of the business discussion module in this embodiment;

[0041] Figure 5 This is a working principle diagram of the document synchronization module in this embodiment;

[0042] Figure 6 is a working principle diagram of the knowledge sharing subsystem in this embodiment;

[0043] Figure 7 This is a working principle diagram of the knowledge application subsystem in this embodiment. DETAILED DESCRIPTION

[0044] To make the objectives, technical solutions, and advantages of the embodiments of this specification more clear, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by users of ordinary skill in the art without making any creative efforts are within the scope of protection of this invention.

[0045] Example

[0046] like Figure 1 As shown, this embodiment provides an enterprise knowledge management system, which adopts a BS (Browser-Server) architecture. The client accesses the server through a browser. The browser has a built-in hypertext editor. Preferably, the hypertext editor adopts a slate-react hypertext editor. The system includes a knowledge precipitation subsystem, a document editing subsystem, and a business collaboration subsystem.

[0047] The knowledge precipitation subsystem is used to create different enterprise spaces according to different business domains of the enterprise, create different business teams for each enterprise space, and create and manage several knowledge bases for each business team, wherein the knowledge base is used to classify and manage team knowledge;

[0048] The document editing subsystem is used to monitor the document collaborative editing events initiated by users using a hypertext editor, obtain user information and document update information of the document collaborative editor, and display the user information and document update information in real time on the hypertext editing page of each collaborative user to realize document collaborative editing;

[0049] The business collaboration subsystem is used to use the hypertext editor to monitor @ function initiation events and document marking events. When the @ function initiation event is monitored, the server side obtains the @ information and stores and / or pushes the @ information after processing. When the document marking event is monitored, the server side records the marked document information for other users to obtain and join the discussion of the document marking information.

[0050] Based on the above-disclosed content, this embodiment enables each team member to build an exclusive team and an exclusive knowledge base, and store team knowledge based on the knowledge base. All knowledge can be shared and communicated online based on the browser, which greatly improves the convenience of users uploading knowledge, acquiring knowledge and sharing knowledge. At the same time, by storing knowledge documents in a dedicated knowledge base, they are aggregated and precipitated into the company's knowledge assets, making knowledge traceable and inheritable. At the same time, there is no need to rely on independent collaborative document editing tools to achieve this. At the same time, by synchronizing collaborative information in real time and updating documents in real time, the consistency of user operation intentions can be well achieved, thereby improving the user's office experience. In addition, deep collaboration, real-time discussion, and collaborative work can be carried out through document information in business processes to improve office efficiency.

[0051] like Figure 2 As shown, in a possible design, the knowledge precipitation subsystem includes a space creation module, a team creation module and a knowledge base module;

[0052] The space creation module is used to classify the business domains of the enterprise and create corresponding enterprise spaces for different business domains;

[0053] It should be noted that the enterprise space is only a collection of several business domains, and several teams can be created under the same space. Of course, it is understandable that this embodiment can also create corresponding enterprise spaces according to different subsidiaries, without specific limitation.

[0054] The team creation module is used to create multiple business teams based on the organizational relationships under each enterprise space and manage team information;

[0055] It should be noted that each team includes several team members, so the team information management not only includes knowledge management, but also team personnel management, specifically including team basic information management, team member management, team authority management and team statistics viewing, etc., which are not limited here.

[0056] The knowledge base module is used to create several knowledge bases for each business team, set knowledge base permissions, and classify and manage team knowledge based on the knowledge bases, wherein several documents are stored in the knowledge bases.

[0057] It should be noted that each knowledge base can store multiple levels of documents, including but not limited to Word documents, Excel documents, hypertext documents, PPT documents, or PDF documents. Knowledge documents can be categorized and managed hierarchically, preferably supporting hierarchical management of five or more levels. Furthermore, knowledge documents can be stored in the knowledge base through hypertext creation and uploading of Office documents. Once the knowledge precipitation subsystem creates and imports a document, the document's metadata will be synchronously stored in the subsystem's database.

[0058] Specifically, if you create and edit an office document online, when creating an office document, the subsystem will save a blank office file and upload it to OSS (Object Storage Service), return the file path, associate the file path with the office document, and then return the file path to the front-end browser; the front-end performs online editing in the Office editing tool based on the file path, and after editing is completed, the document will be uploaded to OSS again, and the document will be loaded through the web to display the edited information content.

[0059] In one possible design, the document editing subsystem includes a listening module, a message receiving module, and a display module. The listening module and the display module are deployed in a browser, and the message receiving module is deployed on the server side. Preferably, the listening module and the display module are respectively connected to the message receiving module based on sokcet, and bidirectional message transmission is performed through the WebSocket protocol.

[0060] The monitoring module is used to monitor the document collaborative editing event initiated by the user using the hypertext editor, and send the event message to the message receiving module;

[0061] Specifically, the monitoring module includes a first monitoring unit and a second monitoring unit;

[0062] The first monitoring unit is used to monitor the collaborative instance creation event using a hypertext editor, and when monitoring, sends the instance creation message to the message receiving module, so that the message receiving module creates a message record according to the instance and returns the current collaborative user information to the client where each user is located;

[0063] It should be noted that the collaborative instance creation event is initiated by the collaborative user through the collaborative joining function in the editor. After the first monitoring unit monitors the collaborative instance creation event through the socket, it sends the user information to the message receiving module, and the server side records and forwards the user information to the terminals of all collaborative users.

[0064] The second monitoring unit is used to monitor document content change events, and when monitored, sends a content change event message to the message receiving module, so that the message receiving module records and returns the input location information of the current collaborative user and the document update information to each user's client according to the content change event message.

[0065] Among them, it should be noted that when the second monitoring unit monitors the content change event, it will call the handleSend Operations plug-in function to locate the user input position and place the user input position in the list to be sent. At the same time, it will call the get Edit Content plug-in function to obtain the user input content, so that the first socket end will send the user input content and the user input position in the list to be sent to the message receiving module, and the message receiving module will send the input position information of the current collaborative user in the document and the content change information of the document to each user's client.

[0066] The message receiving module is used to receive event messages, record user information and / or document update information in the current event, and synchronize the user information and / or document update information to each user's client;

[0067] The display module is used to receive user document editing operations, user information and / or document update information using a hypertext editor, and display the user information and / or document update information on the user's hypertext editing page.

[0068] It should be noted that when the display module receives the server user information and document update information, it will trigger the cursor instruction, so that the user input location information will be displayed through the cursor in the hypertext editor, where the cursor display content includes the user ID, so that other collaborative editing users can know in real time all user information and user location information of the current collaborative editing.

[0069] like Figure 3-Figure 5 As shown, in one possible design, the business collaboration subsystem includes a business request module and a business discussion module;

[0070] The service request module is used to monitor @ function initiation events using a hypertext editor. When a @ function initiation event is monitored, the service request module requests the server to obtain @ user list information and / or @ document information. The server stores the @ user list and context information and pushes them to the client of the @ user, or associates the @ document with the original document and stores it.

[0071] Specifically, users can initiate the @ function in any document, table, comment area or discussion area in this embodiment. Through the @ function, they can quote the document or notify other users to request interaction, so as to notify the @ user to check the message in time and reduce offline communication costs.

[0072] For example, when user A reads a document and needs a response from other users, he or she can @ the user. The system will remind the user being @ed that user A has @ed him or her in a document.

[0073] Specifically, when the user enters the @ symbol, the front-end listening event will be triggered, and then the server will be requested to obtain and display the user list information. The user selects the user to be @ed in the user list and pushes the @ed user as part of the text content to the server. The server parses the text content to obtain the @ed user list and the @ context information, and then splices the @ed user list and the @ context information and pushes the message to the terminal where the @ed user is located. At the same time, the message body will also carry the document connection and be stored in the database. When the @ed user clicks the message, it will quickly jump to the document interface for the user to view.

[0074] The business discussion module is used to use a hypertext editor to monitor document marking events. When a document marking event is monitored, the discussion area is activated so that the document marking user can enter the discussion area to discuss the document marking information. At the same time, the server records the document marking information and user discussion information so that other users can obtain and join the discussion of the document marking information.

[0075] Specifically, the business discussion module includes a document mark monitoring unit, a discussion area activation unit, and a document mark information storage unit;

[0076] The document mark monitoring unit is used to monitor the user's marking event on the current document, and when a marking event is monitored, a discussion button pops up at the marking position;

[0077] The discussion area activation unit is used to receive a user's click operation on the discussion button and send a discussion initiation pop-up window to the user's client, so that the user can enter the discussion area through the pop-up window to discuss the document markup information;

[0078] Among them, preferably, after the user enters the discussion area, the discussion is conducted in text form, which facilitates the server to record the discussion information. In addition, if the user needs to modify the published discussion content, he can click the "Edit" button in the discussion area to re-edit and modify the published content. After the editing is completed, click the "Modify" button to return to the discussion chat box; or click the "Cancel" button. If the input box content has been edited, it will return to the chat area while keeping the original content unchanged; if the input box content has not been edited, clicking the "Cancel" button will return to the chat area. After the user closes the discussion area, he can re-enter the discussion area by clicking the underlined part of the original document and re-discuss the content. After the user clicks "End Discussion", the discussion area disappears and the underlined part at the bottom of the original document also disappears. The user can enter and view the ended discussion record from the document function area.

[0079] The document marking information storage unit is used to send the marked document ID, marked content and user's discussion information to the server for storage after the user publishes discussion information, so that other users can obtain the document discussion record on the server according to the document marking.

[0080] It should be noted that the user's discussion information includes but is not limited to the user name, user avatar, time of posting the discussion information and specific discussion content; after the server stores the document ID, underlined content and previous discussion records, other users can obtain the previous discussion records and join the discussion by clicking on the underlined position when reading the document.

[0081] In one possible design, the business collaboration subsystem also includes a document synchronization module, which is used for the second user to synchronize the first user's knowledge document to the knowledge base of the space to which the second user belongs, wherein the first user is a user of the first space and has created a knowledge document in the first knowledge base of the first space, and the second user is a user of the second space and has the authority to access the first knowledge base.

[0082] It should be noted that document synchronization refers to a user adding documents from other spaces to his or her own space, that is, forming a synchronized document of the original document in his or her own space. At this time, the relationship between the original document and the synchronized document is a reference relationship, not a subordinate relationship.

[0083] For example, if user A creates document A in knowledge base A in space A and document synchronization is enabled for knowledge base A, user B, who has document access permissions for both space A and knowledge base A, can synchronize document A to space B, where user B is located, and generate document B in knowledge base B. After synchronization, if user A modifies document A, the content of document B will be synchronized to the modified content of document A, and user B will not have edit permissions for document B after synchronization.

[0084] In a possible design, the document synchronization module is further configured to send a prompt message to the client where the first user is located when receiving comment information and / or discussion information of the knowledge document.

[0085] For example: when a synchronized document receives comments or discussions, the system will send a prompt message to the terminal where user A is located, but user B will not receive the prompt message at this time, and user A can only jump to the original document A through the prompt message.

[0086] In one possible design, if other users receive a message prompting them to synchronize documents, and if the user does not have access rights to the first space, when the user jumps based on the prompt message, the system will prompt the user that they do not have access rights.

[0087] In addition, the ultimate ownership of the document belongs only to the original document owner. The synchronized user only synchronizes the document to his or her own space for display. Therefore, the synchronized user does not have the authority to delete or modify the document and can only cancel the synchronization. If the original document owner deletes the original document or cancels the synchronization of the original document, the synchronized document will also be deleted and canceled.

[0088] like Figure 6 As shown, in one possible design, the enterprise knowledge management system also includes a knowledge sharing subsystem, which is used to create a learning space. The learning space is used for course users to upload learning projects. The learning projects are configured with learning permissions and learning paths so that users with learning permissions can enter the learning space to study courses.

[0089] It should be noted that the learning rights include but are not limited to paid learning, free learning, etc., and are not limited here.

[0090] The application scenarios of the knowledge sharing subsystem in this embodiment include but are not limited to: (1) providing training programs that meet the different capacity development and practical training needs of core position personnel according to different business scenarios; (2) providing course developers with corresponding learning plans for training content according to business needs to achieve visual training effects; (3) relying on course development tools to help enterprises build their own course development teaching staff and complete knowledge production sedimentation; (4) providing training for new employees to quickly integrate into the team and be competent for their positions, and building a fast, efficient and reusable new employee production line for the enterprise; (5) supporting the construction of multiple types of question banks, flexible organization of tests and examinations, and combining with certificate management to complete integrated assessment and evaluation.

[0091] In addition, different learning paths can be designed according to the training plan of the company's employees. Multiple learning stages can be set in the learning path, and multiple knowledge points can be added to each stage. For example: online courses and exams can be added to the learning plan, and the start time and end time of each plan can be set; in addition, stage tasks can split the knowledge points, and the administrator can set the learning method of the stage (free learning, unlocked learning), and the learning method of the course within the stage (free learning, unlocked learning). After completing the settings, the administrator sets the unlocking time for the stage and the content of the stage. When the students meet the unlocking conditions, the system will send a message to notify the students in real time to study. In addition, stage tasks can not only add courses, but also add homework, exams, documents, practical operations, and designate a person in charge to supervise. After completing the study, the students and supervisors will score and evaluate each other online.

[0092] In one possible design, the enterprise knowledge management system further includes a knowledge application subsystem, which is used to extract and process required knowledge from the knowledge precipitation subsystem according to enterprise needs to generate knowledge application files.

[0093] The knowledge application files include, but are not limited to, help documents, FAQs (frequently asked questions), product manuals, help instructions, online Q&A, FAQs, technical support, and customer manuals. This can help companies export knowledge externally, enhance their brands, conduct learning and training, and build their culture, facilitating the upgrade of their digital knowledge management.

[0094] For example: set up a company's manual book, which is a collection of manuals and a collection of corporate knowledge deposits. It can be used as a site page for the company's external output, carrying the company's external cultural value output, and can be compared with offline corporate culture knowledge brochures; in addition, the manual book can also be used as a carrier of the company's external business. For example, the company's external contract docking and signing process can be deposited in the manual to support employees in external business output.

[0095] Finally, it should be noted that the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of protection of the present invention.

Claims

1. An enterprise knowledge management system, characterized in that: The system adopts BS architecture, and the client accesses the server through a browser, and the browser is embedded with a hypertext editor; the system includes a knowledge precipitation subsystem, a document editing subsystem and a business collaboration subsystem; wherein, The knowledge precipitation subsystem is used to create different enterprise spaces according to different business domains of the enterprise, create different business teams for each enterprise space, and create and manage several knowledge bases for each business team, wherein the knowledge base is used to classify and manage team knowledge; The knowledge precipitation subsystem includes a space creation module, a team creation module and a knowledge base module; The space creation module is used to classify the business domains of the enterprise and create corresponding enterprise spaces for different business domains; The team creation module is used to create multiple business teams based on the organizational relationships under each enterprise space and manage team information; The knowledge base module is used to create several knowledge bases for each business team, set knowledge base permissions, and classify and manage team knowledge based on the knowledge bases, wherein the knowledge bases store several documents; The document editing subsystem is used to monitor the document collaborative editing events initiated by users using a hypertext editor, obtain user information and document update information of the document collaborative editor, and display the user information and document update information in real time on the hypertext editing page of each collaborative user to realize document collaborative editing; The business collaboration subsystem is used to monitor @ function initiation events and document marking events using a hypertext editor. When an @ function initiation event is monitored, the server side obtains the @ed information, processes the @ed information, and stores and / or pushes it. When a document marking event is monitored, the server side records the marked document information so that other users can obtain it and join in the discussion of the document marking information. The business collaboration subsystem includes a business request module and a business discussion module; The service request module is used to monitor @ function initiation events using a hypertext editor. When a @ function initiation event is monitored, the service request module requests the server to obtain @ user list information and / or @ document information. The server stores the @ user list and context information and pushes them to the client of the @ user, or associates the @ document with the original document and stores it. The business discussion module is used to monitor document marking events using a hypertext editor. When a document marking event is monitored, a discussion area is activated so that the document marking user can enter the discussion area to discuss the document marking information. At the same time, the document marking information and user discussion information are recorded by the server so that other users can obtain and join the discussion of the document marking information. The business discussion module includes a document mark monitoring unit, a discussion area activation unit and a document mark information storage unit; The document mark monitoring unit is used to monitor the user's marking event on the current document, and when a marking event is monitored, a discussion button pops up at the marking position; The discussion area activation unit is used to receive a user's click operation on the discussion button and send a discussion initiation pop-up window to the user's client, so that the user can enter the discussion area through the pop-up window to discuss the document markup information; The document marking information storage unit is used to send the marked document ID, marked content and user's discussion information to the server for storage after the user publishes discussion information, so that other users can obtain the document discussion record on the server according to the document marking.

2. The enterprise knowledge management system according to claim 1, characterized in that: The enterprise knowledge management system also includes a knowledge sharing subsystem, which is used to create a learning space. The learning space is used for course users to upload learning projects. The learning projects are configured with learning permissions and learning paths so that users with learning permissions can enter the learning space to study courses.

3. The enterprise knowledge management system according to claim 1, characterized in that: The enterprise knowledge management system further includes a knowledge application subsystem, which is used to extract and process required knowledge from the knowledge precipitation subsystem according to enterprise needs to generate knowledge application files.

4. The enterprise knowledge management system according to claim 1, characterized in that: The document editing subsystem includes a monitoring module, a message receiving module and a display module, wherein the monitoring module and the display module are deployed in the browser, and the message receiving module is deployed on the server side; The monitoring module is used to monitor the document collaborative editing event initiated by the user using the hypertext editor, and send the event message to the message receiving module; The message receiving module is used to receive event messages, record user information and / or document update information in the current event, and synchronize the user information and / or document update information to each user's client; The display module is used to receive user document editing operations, user information and / or document update information using a hypertext editor, and display the user information and / or document update information on the user's hypertext editing page.

5. The enterprise knowledge management system according to claim 4, characterized in that: The monitoring module includes a first monitoring unit and a second monitoring unit; The first monitoring unit is used to monitor the collaborative instance creation event using a hypertext editor, and when monitoring, sends the instance creation message to the message receiving module, so that the message receiving module creates a message record according to the instance and returns the current collaborative user information to the client where each user is located; The second monitoring unit is used to monitor document content change events, and when monitored, sends a content change event message to the message receiving module, so that the message receiving module records and returns the input location information of the current collaborative user and the document update information to each user's client according to the content change event message.

6. The enterprise knowledge management system according to claim 1, characterized in that: The business collaboration subsystem also includes a document synchronization module, which is used for the second user to synchronize the first user's knowledge document to the knowledge base of the space to which the second user belongs, wherein the first user is a user of the first space and has created a knowledge document in the first knowledge base of the first space, and the second user is a user of the second space and has the authority to access the first knowledge base.

7. The enterprise knowledge management system according to claim 6, characterized in that: The document synchronization module is further configured to send a prompt message to the client where the first user is located when receiving the comment information and / or discussion information of the knowledge document.

Images