CN111274464A

CN111274464A - Knowledge management system

Info

Publication number: CN111274464A
Application number: CN201911372386.8A
Authority: CN
Inventors: 张卫民
Original assignee: Tianjin Langtao Technology Co Ltd
Current assignee: Tianjin Langtao Technology Co Ltd
Priority date: 2019-12-27
Filing date: 2019-12-27
Publication date: 2020-06-12

Abstract

The invention provides a knowledge management system, comprising: the user information management module is used for storing the user registration information and matching and verifying the login request information of the user and the stored user registration information; the project management module is used for inquiring from the database according to the inquiry condition input by the user and returning a corresponding inquiry result; the program document management module is used for providing a data dictionary, an incidence relation and a user manual for the data stored in the database for a user; the file management module is used for providing file management and patent management functions aiming at the data stored in the database for a user; and the system management module is used for providing organization management, authority management and menu management for the data stored in the database for the user. The invention provides measures of data encryption, account management, service call authorization management, perfect log management and the like, and ensures higher security of the system.

Description

Knowledge management system

Technical Field

The invention relates to the technical field of data processing, in particular to a knowledge management system.

Background

Big data awareness has been driven into national and enterprise thinking. With the rapid development of big data basic settings, big data technologies and big data applications over several years, big data complexity, technical barriers and implementation difficulty are decreasing year by year, and data applications have many practices and face new challenges no matter from policy-oriented implementation or enterprise-level solutions: in the research and development process of the existing big data related software system, a general data management technology in the development process is lacked, so that technical developers often waste time and labor when needing to call and search documents and data, the data is deficient in perfect log management, and the efficiency is low.

Disclosure of Invention

The object of the present invention is to solve at least one of the technical drawbacks mentioned.

Therefore, the invention aims to provide a knowledge management system.

In order to achieve the above object, an implementation of the present invention provides a knowledge management system including: the user information management module is used for storing the user registration information, matching and verifying the login request information of the user and the stored user registration information, and allowing login to be used if the login request information of the user is consistent with the stored user registration information;

the database is used for storing data and collecting data of the target software system in the development process;

the project management module is used for inquiring from the database according to the inquiry condition input by the user and returning a corresponding inquiry result;

the program document management module is used for providing functions of a data dictionary, an incidence relation, a user manual, an API document, a server environment, user password management and template management aiming at data stored in a database for a user;

the file management module is used for providing file management and patent management functions aiming at the data stored in the database for a user;

and the system management module is used for providing the functions of organization management, authority management, menu management, log management and dictionary management for the data stored in the database for the user.

Furthermore, the user information management module is also used for providing a log viewing function so that a user can view the log information of the logging system each time.

Further, the project management module is also used for providing functions of adding, editing, deleting, submitting, invalidating and withdrawing project information for users.

Further, the program document management module performs data dictionary, association relation, user manual, API document, server environment, user password management and template management on the data, and includes functions of adding, editing, deleting, checking and historical version query and update.

Further, the file management module performs data management, including: according to the query condition input by the user, querying from the database and returning a corresponding query result; and providing the operations of uploading, deleting, previewing and historical recording.

Further, the patent management module is used for inquiring from the database according to the inquiry condition input by the user and returning a corresponding inquiry result; adding, editing and deleting operations are provided.

Further, the system management module provides an organization management function, including: inquiring from the database according to the inquiry condition input by the user, inquiring corresponding organizational structure and personnel information, and providing the functions of newly increasing a large area, newly increasing city departments, editing, enabling departments and forbidding departments for the organizational structure;

the system management module provides authority management functions, including: and inquiring from the database according to the inquiry condition input by the user to acquire the authority management information of the relevant buttons and the tree authority management information, and to have the functions of newly adding and editing the authority and inquiring the public node.

Further, the system management module provides menu management functions, including: displaying a menu page, newly adding nodes on the menu page, storing newly added menu information, and deleting nodes on the menu page.

Further, the system management module provides log management functions, including: and log information display and log information query functions of the operation log and the data log are provided.

Further, the system management module provides dictionary management functions, including: providing the functions of displaying, editing and inquiring service dictionary and system value.

The knowledge management system according to the embodiment of the invention supports timely warehousing of the existing files, picture files, business data and data in the whole system development process of a unit, and provides a flexible search function. And after the application system data dictionary, the association relation and the API interface are put into a warehouse, the data dictionary can be used as a later data engine and a visual basis.

1. The whole product adopts the J2EE technology, the platform is safe, stable and efficient, high cohesion and low coupling are realized among modules, and the cross-platform performance is good.

2. By adopting a Spring framework, a Hibernate framework and a DAO object are used by a data access layer, and the method is mature, stable and high in flexibility.

3. The platform design takes users as the leading factor, adopts the B/S framework, and ensures smooth and rich user experience.

4. The platform supports various mainstream operating system platforms such as Windows series and Linux series in an all-round manner, and has good cross-platform capability.

5. The use safety is as follows: data encryption, account management, service call authorization management, perfect log management and other measures ensure higher security of the system.

6. High availability of functions: the platform realizes the functions of network load balancing and session replication on the framework, and ensures the high availability of the system in multiple layers.

Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.

Drawings

The above and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

FIG. 1 is a block diagram of a knowledge management system according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of a home interface after a user logs in according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a journal viewing interface in accordance with an embodiment of the present invention;

FIG. 4 is a schematic diagram of a project management interface according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a select stakeholder interface according to an embodiment of the invention;

FIG. 6 is a schematic diagram of a data dictionary interface according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of an association interface according to an embodiment of the invention;

FIG. 8 is a diagram of a newly added association interface according to an embodiment of the invention;

FIG. 9 is a schematic diagram of a user manual interface according to an embodiment of the invention;

FIG. 10 is a schematic diagram of a new user manual interface according to an embodiment of the invention;

FIG. 11 is a schematic diagram of an API document interface in accordance with an embodiment of the present invention;

FIG. 12 is a schematic diagram of a server environment interface according to an embodiment of the invention;

FIG. 13 is a schematic diagram of a username password management interface in accordance with an embodiment of the present invention;

FIG. 14 is a schematic diagram of a newly added username password management interface in accordance with an embodiment of the present invention;

FIG. 15 is a schematic diagram of a template management interface according to an embodiment of the invention;

FIG. 16 is a diagram of a data management interface according to an embodiment of the invention;

FIG. 17 is a schematic view of a patent management interface according to an embodiment of the present invention;

FIG. 18 is a schematic view of an organizational management interface according to an embodiment of the invention;

FIG. 19 is a diagram of a button rights management interface according to an embodiment of the invention;

FIG. 20 is a diagram of a tree rights management interface according to an embodiment of the invention;

FIG. 21 is a schematic diagram of a common node page interface according to an embodiment of the present invention;

FIG. 22 is a schematic view of a role management interface in accordance with an embodiment of the present invention;

FIG. 23 is a schematic diagram of a menu management interface according to an embodiment of the invention;

FIG. 24 is an interface diagram of an oplog, according to an embodiment of the invention;

FIG. 25 is an interface diagram of a data log according to an embodiment of the invention;

FIG. 26 is an interface diagram of a service dictionary, according to an embodiment of the present invention;

fig. 27 is an interface diagram of system value setting according to an embodiment of the present invention.

Detailed Description

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative and intended to be illustrative of the invention and are not to be construed as limiting the invention.

As shown in fig. 1, the knowledge management system according to the embodiment of the present invention includes: the system comprises a user information management module, a database, a project management module, a program document management module, a file management module and a system management module.

And the user information management module is used for storing the user registration information, matching and verifying the login request information of the user and the stored user registration information, and allowing login to be used if the login request information of the user is consistent with the stored user registration information.

Specifically, the user information management module receives a user name and a password input by the user, and jumps to the interface shown in fig. 2 after clicking "login".

And after the login is successful for the first time, entering a main interface, wherein the left side of the page is a system menu, and the right side of the page is used for displaying a home page. And modifying the password at the upper right corner of the main page, displaying a modification page at the right side of the page, and performing password modification operation on the page by a user. And displaying the user information and exiting the login function on the page of the personal data. Specifically, the user information is used for displaying the related information of the current system login person. Logout is used for the current user to log out of the system.

The user information management module is also used for providing a password changing function for the user so that the user can modify the password according to the requirement.

In addition, the user information management module is also used for providing a log viewing function so that a user can view log information of logging in the system each time.

And the database is used for storing the data of the target software system in the development process and collecting the data. The invention can be applied to various software development systems and stores data and collected data in the development process.

And the project management module is used for inquiring from the database according to the inquiry condition input by the user, returning a corresponding inquiry result and providing functions of adding, editing, deleting, submitting, invalidating and withdrawing project information for the user.

FIG. 4 is a diagram of a project management interface according to an embodiment of the present invention. And inquiring the related information by filling the inquiry conditions in the inquiry area. The page operation of fig. 4 is described as follows:

newly adding: clicking a 'new' button, popping up a 'new/edit page' page, adding a new project, and inputting a new project name and a related party name. Wherein the name of the party may be selected through the menu interface shown in fig. 5.

Editing: clicking the 'editing' operation in the list operation column, popping up a 'new addition/editing page' page, and modifying the previously stored information.

And (3) deleting: and selecting a deleted column, clicking 'delete', and deleting the selected data.

Submitting: and selecting the submitted column, clicking 'price raising', submitting the selected data, and using the data by other modules after submission.

And (3) invalidation: select the column to invalidate, click "invalidate", invalidate the selected data, can't be used by other module after cancelling.

Withdrawing: and selecting a withdrawn column, clicking 'withdraw', withdrawing the selected data, and editing after withdrawing.

And the program document management module is used for providing functions of a data dictionary, an incidence relation, a user manual, an API document, a server environment, user password management and template management for the data stored in the database for a user.

Specifically, the program document management module performs data dictionary, association relation, user manual, API document, server environment, user password management, and template management on the data, including functions of adding, editing, deleting, checking, and querying and updating historical versions.

Data dictionary management

FIG. 6 is a diagram of a data dictionary interface, in accordance with an embodiment of the present invention. And inquiring the related information by filling the inquiry conditions in the inquiry area.

In fig. 6 the pages provide the following functions:

newly adding: clicking the 'new' button, popping up a 'new/edit page' page, and adding a data dictionary. Selecting items, filling in table names, filling in descriptions, filling in remarks, filling in contents (markdown format), adding contents through an insertion template, clicking to store, and storing data. And displaying and saving the data, and displaying the markdown text into html.

History version: clicking the 'history version', popping up a history version page, viewing the data editing history, and displaying the data modification history.

(2) Association relation

FIG. 7 is a diagram illustrating an association interface according to an embodiment of the invention. And selecting the relation of program document, data dictionary and association into the data association relation, as shown in figure 7. And inquiring the related information by filling the inquiry conditions in the inquiry area.

Through the interface in fig. 7, the following functions may be provided to the user:

newly adding: clicking the add button, popping up an add/edit page, adding the association relationship, filling and storing, as shown in fig. 8.

(3) User manual

FIG. 9 is a schematic diagram of a user manual interface according to an embodiment of the invention. Select [ program document-description document-user manual ] into the user manual dictionary page. And inquiring the related information by filling the inquiry conditions in the inquiry area.

Through the page shown in fig. 9, the following functions may be provided:

newly adding: clicking the 'new' button, popping up a 'new/edit page' page, and adding a user manual. As shown in fig. 10, when data is filled in, content (markdown format) can be added by inserting a template, and data is saved by clicking. And displaying and saving the data, and displaying the markdown text into html.

(4) API documents

FIG. 11 is a schematic diagram of an API document interface in accordance with an embodiment of the present invention. Select [ program document-description document-API document ] into the user manual dictionary page. And inquiring the related information by filling the inquiry conditions in the inquiry area.

Through the interface in FIG. 11, the following functions may be provided to the user:

newly adding: clicking the 'new' button, popping up a 'new/edit page' page, and adding an API document. And filling in data, wherein when filling in the content (markdown format), the content can be added through an insertion template, and the data is saved by clicking. And displaying the saved data, and displaying the markdown text as html.

(5) Environment of server

FIG. 12 is a schematic diagram of a server environment interface according to an embodiment of the invention. And (4) selecting [ program document-environment management-server environment ] to enter an environment page of the server. And inquiring the related information by filling in the inquiry conditions in the inquiry area.

Through the interface shown in FIG. 12, the following functions may be provided to the user:

newly adding: clicking a 'new' button, popping up a 'new/edit page' page, and adding the environment of the server. And filling and storing the data.

(6) Username password management

Fig. 13 is a schematic diagram of a username-password management interface according to an embodiment of the present invention. And (4) selecting [ program document-environment management-user name and password management ] to enter a user name and password management page. And inquiring the related information by filling the inquiry conditions in the inquiry area.

Through the interface in fig. 13, the following functions may be provided:

newly adding: clicking the add button, popping up an add/edit page, managing the user name and the password, filling in data and storing, as shown in fig. 14.

(7) Template management

FIG. 15 is a diagram illustrating a template management interface according to an embodiment of the invention. And (4) selecting program document, template management and template management, entering a template management page, filling data and storing. And inquiring the related information by filling the inquiry conditions in the inquiry area.

Through the interface in FIG. 15, the following functions may be provided to the user:

newly adding: clicking a 'newly added' button, popping up a 'newly added/edited page', managing a newly added template, and providing a function of viewing a template interface for a user.

Setting default: and after default setting, automatically adding a template when a service dictionary and an api document are newly added.

The file management module is used for providing file management and patent management functions aiming at the data stored in the database for a user.

Specifically, the file management module performs data management, including: according to the query condition input by the user, querying from the database and returning a corresponding query result; operations for uploading, deleting, previewing and history are provided as shown in fig. 16.

Referring to FIG. 16, select [ archive management-data management ] to enter the data management presentation. And inquiring the related information by filling in the inquiry conditions in the inquiry area.

Through the profile management interface in FIG. 16, the following functions may be provided to the user:

uploading: clicking the 'new' button, popping up an 'uploading page', selecting the type and uploading file, completing uploading after submitting, and managing the newly added data.

Previewing: and viewing the uploaded pictures.

History recording: and viewing the historical uploading files.

The patent management module is used for inquiring from the database according to the inquiry condition input by the user and returning a corresponding inquiry result; operations of addition, editing, and deletion are provided as shown in fig. 17.

Referring to fig. 17, select [ archive management-patent management ] to enter patent management page. And inquiring the related information by filling the inquiry conditions in the inquiry area.

Through the interface shown in FIG. 17, the following functions may be provided to the user:

newly adding: clicking a 'new' button, popping up a 'new/edit page' page, and managing new patents. For example: a claim type, a name, a version number, an authorization date, and an authorization number.

The system management module is used for providing organization management, authority management, menu management, log management and dictionary management functions for the data stored in the database for users.

Specifically, the system management module provides an organization management function, including: according to the query condition input by the user, the database is queried to obtain the corresponding organization and personnel information, and the organization structure is provided with the functions of adding a large area, adding a new department, editing, enabling the department and disabling the department, as shown in fig. 18.

Referring to fig. 18, select [ system management-organizational management ] to enter the organizational management page. The organization mechanism manages the page style to be tree structure on the left side and list format on the right side. The user can inquire the corresponding information of the organization and the personnel by filling in the inquiry condition in the inquiry area.

Through the interface shown in FIG. 18, the following functions may be provided to the user:

1) tree node operation:

newly adding a large area: and popping up a new augmentation area page. Newly adding a large area: filling in the names and the sequence numbers of the large areas (the sequence numbers cannot be repeated), filling in remarks (the remarks can not be filled), clicking the 'save' button to finish the new addition, and clicking the 'cancel' button to cancel the new addition.

Newly adding departments: and popping up a new augmentation area page. Newly adding departments: filling in the name of department, filling in the sequence number (the sequence number can not be repeated), filling in the remark (the remark can not be filled), clicking the 'save' button to complete the new addition, clicking the 'cancel' button to cancel the new addition.

Editing: and popping up different editing pages by judging the node hierarchy. Note: the root node may not be editable.

A. Editing a large area: and modifying the previously filled large area information (the sequence number cannot be repeated, and the remark cannot be filled), clicking a 'save' button to finish editing, and clicking a 'cancel' button to cancel the editing.

B. And (4) an editing department: and modifying the previously filled department information (the sequencing number cannot be repeated, and the remark cannot be filled), clicking a 'save' button to finish editing, and clicking a 'cancel' button to cancel the editing.

The starting department: the selected node is enabled, and the enabled node can be selected in the subsequent process.

And (4) forbidden departments: the selected node is disabled, and the disabled node cannot be selected in the subsequent flow.

2) List operation:

newly adding: and selecting the node on the left side, clicking a 'newly added' button, and popping up different newly added pages by judging the level of the selected node. And (4) adding a user: filling in the relevant log-in information of the user, selecting the department and role of the user, filling in the mobile phone, the mailbox and the job number (or not filling in), clicking the 'save' button to complete the new addition, and clicking the 'cancel' button to cancel the new addition.

Editing: clicking the 'edit' operation in the list and popping up an edit page. And (3) editing the user: and modifying the information filled before, clicking a 'save' button to finish editing, and clicking a 'cancel' button to cancel the editing.

Starting: the disabled data in the list is selected for enabling, after which it may continue to be selected in a subsequent flow.

And (3) disabling: the enabled data in the list is selected for disabling and may not be selected in subsequent processes after disabling.

Resetting the password: the selected user password may be reset to "111111".

The system management module provides authority management functions, including: according to the query condition input by the user, the database is queried to obtain the authority management information of the relevant buttons and the tree authority management information, and the functions of newly adding and editing the authority and querying the public node are realized.

(1) Button rights management

Select [ system management-rights management-button rights management ] to enter the button rights management page, as shown in fig. 19. And inquiring the related button authority management information by filling in the inquiry conditions in the inquiry area.

Through fig. 19, the following functions can be provided to the user:

newly adding: clicking the 'new adding' button, popping up a page shown by 'new adding/editing page', and adding a button authority. The button authority is newly added: filling in the code and name of the button authority, selecting the menu page where the button is located, clicking the 'save' button to complete the new addition, and clicking the 'cancel' button to cancel the new addition.

Button authority editing: and modifying the originally stored button authority name, clicking a 'storage' button to finish editing, and clicking a 'cancel' button to cancel the editing.

Editing: clicking 'edit' operation in the list operation column, popping up a page indicated by 'newly added/edited page', and modifying the previously stored button authority information.

(2) Tree authority management

And selecting basic management, authority management and tree authority management to enter a tree authority management page, as shown in fig. 20. And inquiring the related tree-shaped authority management information by filling the inquiry conditions in the inquiry area.

Through the interface shown in FIG. 20, the following functions may be provided to the user:

newly adding: clicking the 'new' button, popping up a page indicated by 'new addition/edition page', and adding a tree authority. Newly adding tree-shaped authority: filling in the code and name of tree authority, clicking the 'save' button to complete the new addition, and clicking the 'cancel' button to cancel the new addition.

Editing: clicking 'edit' operation in the list operation column, popping up a page indicated by 'newly added/edited page', and modifying the tree authority information stored before. Button authority editing: and modifying the originally stored tree authority name, clicking a 'storage' button to finish the editing, and clicking a 'cancel' button to cancel the editing.

(3) Common node

A common node: clicking the 'public node' operation in the list operation column, popping up a page shown as 'public node page' in fig. 21, and displaying the public node information for viewing the public node information of the tree-shaped authority.

The system management module further provides role management functions. Fig. 22 is an interface diagram of role management.

And selecting [ system management-authority management-role management ] to enter a role management page. And displaying the person role information of the current system.

Through the interface shown in FIG. 22, the following functions may be provided to the user:

newly adding: clicking the 'new adding' button, popping up a page shown by 'new adding/editing page', and adding a button authority. Role name: and filling the required data manually.

And (3) distributing the menus: clicking a 'menu distribution' button, popping up a page shown by a 'distribution menu page' diagram, and using a menu which can be used by a distribution role. And checking different menus through check boxes to distribute the menus to the users, finishing selection, and clicking a storage button to ensure that the role user obtains the corresponding menu use permission.

Button authority: clicking the button authority operation in the list operation column, popping up a page shown by a button authority page, and changing the role to use the button authority. And checking different button authorities through a check box to distribute the button authorities to the users, finishing selection, clicking a storage button, and obtaining corresponding authorities by the role users.

Tree authority: clicking the tree authority operation in the list operation column, popping up a page shown by a tree authority page, and changing the authority of the character to use the button. Clicking the operation of distributing the authority, popping up a page of selecting the authority, and distributing the authority by checking tree nodes.

The system management module provides menu management functions, including: displaying a menu page, adding a node on the menu page, saving the newly added menu information, and deleting a node on the menu page, as shown in fig. 23.

Through the interface shown in FIG. 23, the following functions may be provided to the user: the menu management page style is a tree page. The left side of the page displays the menu name of the current system, and the right side displays the related information of the menu. When the left node is clicked, the corresponding menu information is displayed on the right.

Newly adding: and performing new addition operation on the tree nodes on the left side.

And (3) storage: and storing the newly added menu information.

And (3) deleting: and deleting the selected left tree node.

The system management module provides log management functions and comprises: and log information display and log information query functions of the operation log and the data log are provided.

FIG. 24 is an interface diagram of an oplog, according to an embodiment of the invention. The operation log list page displays log information of various operations of the system personnel. And inquiring corresponding operation log information by filling the inquiry conditions in the inquiry box.

FIG. 25 is an interface diagram of a data log according to an embodiment of the invention. And the data log list page displays log information of various data flows of the system. And inquiring corresponding information by filling the inquiry conditions in the inquiry box.

The system management module provides dictionary management functions, including: providing the functions of displaying, editing and inquiring service dictionary and system value.

FIG. 26 is an interface diagram of a service dictionary, according to an embodiment of the present invention.

Through the interface provided in FIG. 26, the following functionality may be provided to the user:

and (4) selecting [ system management-dictionary management-service dictionary ] to enter a service dictionary page. The page style of the service dictionary is tree structure on the left side and list format on the right side. And displaying all service dictionaries and sub-item information of the service dictionaries in the system on the left side. And the right service dictionary detail page is default to be empty, and when the left node is selected, the related information of the node is displayed. And displaying all service dictionary information by default on the right service dictionary list page, and displaying the relevant information of the node when clicking the left node.

1. Tree node operation:

editing: and popping up different editing pages by judging the node hierarchy. Editing the dictionary type: modifying the type name and the ranking number, selecting whether the type name and the ranking number are visible or not, clicking a 'save' button to finish editing, and clicking a 'cancel' button to cancel the editing.

And (3) deleting: and deleting the selected node. Note: if the selected node has a child node, the child node is deleted first and then the parent node is deleted.

2. List operation:

adding a dictionary type: click the button "add dictionary type". Adding a dictionary type: filling in type code, type name and ranking number, selecting whether the type is visible or not, clicking a 'save' button to finish adding, and clicking a 'cancel' button to cancel the new adding.

Adding dictionary sub-items: and selecting the dictionary type on the left side, and clicking a 'newly added dictionary sub-item' button. Adding dictionary sub-items: filling in dictionary item code, dictionary item name and sequencing number, clicking the 'save' button to complete the addition, and clicking the 'cancel' button to cancel the addition.

Editing: select a piece of data in the list and click the "edit" button. Editing dictionary sub-items: and modifying the dictionary entry name and the sequencing number, clicking a 'save' button to finish editing, and clicking a 'cancel' button to cancel the editing.

And (3) deleting: one or more pieces of data in the list are selected, and a 'delete' button is clicked to delete the selected service dictionary.

And (4) selecting [ system management-dictionary management-system value ] to enter a system value page. And inquiring related system value information by filling in the inquiry conditions in the inquiry area.

Through the interface provided in FIG. 27, the following functionality may be provided to the user:

newly adding: clicking the 'newly added' button, popping up a 'newly added/edited page' page, and adding a system value newly.

Newly adding a system value: and filling in related information of the system value, clicking a 'save' button to finish the new addition, and clicking a 'cancel' button to cancel the new addition.

Editing: selecting a piece of data in the list, clicking an 'edit' button, popping up an 'addition/edit page' page, and modifying the previously stored system value information.

Editing a system value: and modifying the relevant information of the system value, clicking a 'save' button to finish editing, and clicking a 'cancel' button to cancel the editing.

Starting: selecting the disabled data in the list, clicking the "enable" button changes the system value state to enabled.

And (3) disabling: selecting the enabled data in the list, clicking the "disable" button changes the system value state to disabled.

The knowledge management system of the embodiment of the invention can be applied to the following fields:

(1) unit data management and control

Pictures and audio-visual data such as organization history, team activities, enterprise culture and the like are filed in different categories and can be extracted and used at any time, and the embarrassment that the data are stored disorderly and cannot be found when being used is thoroughly solved.

(2) Business data management and control

The related explanation materials and introduction of the business case, the understanding of business operators, the heart and the like are stored, the subsequent use is convenient, and the work efficiency is improved. And the case achievements are put in storage, and the team fully applies the existing accumulation, so that the situation is prevented from starting from zero forever, and the speed of completing the business is continuously accelerated.

(3) Technical data management and control

The software and hardware environment of the server, the user names and passwords of various systems, the data dictionary of various service systems, the API interface description, the operation manual and the like are stored, and emergency situations can be directly searched, and the basic support for carrying out subsequent analysis work can also be used.

(4) Data version management and control

The file data is recorded and checked from the first draft to the last version, the historical versions of the file data are recorded from the release of the knowledge, and the condition of each modified version can be inquired.

(5) Authority management and control

And permission distribution is carried out on the knowledge data according to different posts, levels, roles and the like, so that the knowledge data can be safely and efficiently checked.

In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made in the above embodiments by those of ordinary skill in the art without departing from the principle and spirit of the present invention. The scope of the invention is defined by the appended claims and equivalents thereof.

Claims

1. A knowledge management system, comprising:

the user information management module is used for storing the user registration information, matching and verifying the login request information of the user and the stored user registration information, and allowing login to be used if the login request information of the user is consistent with the stored user registration information;

2. The knowledge management system of claim 1, wherein the user information management module is further configured to provide a log viewing function for a user to view log information of the user logging into the system each time.

3. The knowledge management system of claim 1 wherein the project management module is further configured to provide a user with add, edit, delete, submit, invalidate, and revoke functions for project information.

4. The knowledge management system of claim 1 wherein the program document management module performs data dictionary, association, user manual, API document, server environment, user password management, template management, including adding, editing, deleting, viewing, and historical version query update functions on data.

5. The knowledge management system of claim 1, wherein the archive management module performs material management, comprising: according to the query condition input by the user, querying from the database and returning a corresponding query result; and providing the operations of uploading, deleting, previewing and historical recording.

6. The knowledge management system of claim 1, wherein the patent management module is configured to query from the database according to a query condition input by a user and return a corresponding query result; adding, editing and deleting operations are provided.

7. The knowledge management system of claim 1, wherein the system management module provides organizational management functions comprising: inquiring from the database according to the inquiry condition input by the user, inquiring corresponding organization and personnel information, and providing functions of newly increasing a large area, newly increasing departments, editing, enabling departments and forbidding departments for the organization structure;

8. The knowledge management system of claim 1, wherein the system management module provides menu management functions comprising: displaying a menu page, newly adding nodes on the menu page, storing newly added menu information, and deleting nodes on the menu page.

9. The knowledge management system of claim 1, wherein the system management module provides log management functions comprising: and log information display and log information query functions of the operation log and the data log are provided.

10. The knowledge management system of claim 1, wherein the system management module provides dictionary management functions comprising: providing the functions of displaying, editing and inquiring service dictionary and system value.