Method and apparatus for constructing master data of database, and computer device

Abstract

Disclosed in the present application are a method and apparatus for constructing master data of a database, and a computer device and a storage medium. Specifically, the method for constructing master data of a database comprises: establishing a data connection between a knowledge graph and a database, wherein the knowledge graph comprises first master data; establishing a data table structure on the basis of the database; and performing filling with the first master data in the knowledge graph according to the data table structure, so as to generate second master data of the database. In this way, master data can be conveniently interfaced to different databases by means of an intermediate medium, i.e., a knowledge graph in a unified manner, so as to automatically adapt to data formats and requirements of the different databases, thereby facilitating the update and maintenance of the master data itself.

Description

Method, device and computer equipment for constructing master data of database Technical Field

[0001] The present application relates to the field of knowledge graphs, and specifically, to a method, apparatus, computer equipment, and storage medium for constructing master data of a database. Background Art

[0002] When implementing industrial software, the source of the required master data may be an existing business system, a data dictionary, or even an external file. As the factory operates, master data will continue to change, such as the introduction of new products or materials, changes to supplier or customer information, adjustments to units of measurement, and optimization of inventory management strategies. There may also be adjustments to data attributes and relationships. To ensure the real-time and accuracy of this data, changes must be tracked and updated synchronously. Data directly affects the normal operation and production efficiency of the system. Industrial software master data is not easy to operate, requiring different initialization scripts to be written for different factories. Changes in industrial software master data lack version management, and there is a lack of mechanisms for data synchronization and updates.

[0003] Summary of the Invention

[0004] Based on this, the present application provides a method for constructing the master data of a database, which includes: establishing a data connection between a knowledge graph and a database, wherein the knowledge graph includes first master data; establishing a data table structure based on the database; filling the first master data in the knowledge graph according to the data table structure to generate the second master data of the database.

[0005] Through the above method, the master data can be conveniently connected to different databases through the intermediate medium of knowledge graph, automatically adapting to the data format and requirements of different databases, and facilitating the update and maintenance of the master data itself.

[0006] Furthermore, the filling of the first main data in the knowledge graph according to the data table structure to generate the second main data of the database includes establishing a mapping relationship between the first main data in the knowledge graph and the data table structure, and filling the first main data in the knowledge graph according to the data table structure based on the mapping relationship.

[0007] Through the above method, the data format and logical connection of the main data can be mapped from the knowledge graph to the corresponding data table structure, and then the instance data can be filled in the data table structure according to this mapping relationship to complete the data migration and transformation.

[0008] Furthermore, establishing a data connection between the knowledge graph and the database includes establishing a data connection between the structured first main data and the unstructured first main data in the knowledge graph and the database.

[0009] Through the above methods, a unified data connection framework can be used to connect different data sources, including structured and unstructured data, which greatly supports and expands different master data types.

[0010] Furthermore, before establishing a data connection between the knowledge graph and the database, it also includes publishing different versions of the knowledge graph according to different databases.

[0011] Through the above method, the knowledge graph can be adapted to different databases. When the database is updated, the master data can be easily updated, tracked and managed.

[0012] Furthermore, the present application also discloses a device for constructing master data of a database, which includes: a data connection module for establishing a data connection between a knowledge graph and a database, wherein the knowledge graph includes first master data; a structure establishment module for establishing a data table structure based on the database; and a data construction module for filling the first master data in the knowledge graph according to the data table structure to generate second master data of the database.

[0013] The present application also provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and wherein the processor implements the above method when executing the computer program.

[0014] The present application also provides a computer-readable storage medium having a computer program stored thereon, and the computer program implements the above method when executed by a processor.

[0015] The present application also provides a computer program product, which is tangibly stored on a computer-readable medium and includes computer-executable instructions. When the computer-executable instructions are executed, the computer-executable instructions cause at least one processor to perform the method described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Implementations of the present disclosure are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate the same or similar parts.

[0017] FIG1 is a schematic diagram of a process of a method for constructing master data of a database according to an embodiment of the present application.

[0018] FIG2 is a schematic diagram of a device for constructing master data of a database according to an embodiment of the present application.

[0019] FIG3 is a schematic diagram of a computer device for constructing master data of a database according to an embodiment of the present application.

[0020] The accompanying drawings are numerals as follows:

[0021] Steps S101-S103

[0022] 200: Installation

[0023] 201: Module

[0024] 202: Module

[0025] 203: Module

[0026] 204: Module

[0027] 205: Module

[0028] 206: Module

[0029] 300: Computer equipment

[0030] 302: Processor

[0031] 304: Memory DETAILED DESCRIPTION

[0032] In the following description, for the purpose of explanation, a large number of specific details are set forth. However, it is understood that the present invention can be implemented without these specific details. In other examples, well-known circuits, structures, and technologies are not shown in detail so as not to affect the understanding of the description.

[0033] References throughout this specification to "an implementation," "an implementation," "an exemplary implementation," "some implementations," "various implementations," etc., indicate that the implementations of the invention being described may include particular features, structures, or characteristics. However, it does not imply that every implementation must include those particular features, structures, or characteristics. Furthermore, some implementations may have some, all, or none of the features described for other implementations.

[0034] Initializing master data and basic data is a crucial step in implementing industrial software. First, let's briefly introduce the concept of master data. Master data refers to core data within an enterprise that is widely used, stable, and relevant to business processes. It is shared, persistent, and highly centralized data within an organization, used to describe and define important entities, objects, or business transactions within the enterprise. Master data is typically used across multiple systems and modules to maintain data consistency and accuracy. In intelligent manufacturing, master data can include data on key entities or objects, such as products, equipment, suppliers, customers, and process parameters. The management and maintenance of master data is crucial to achieving the overall performance and efficiency of intelligent manufacturing. Through unified master data management, enterprises can ensure data consistency across different departments and systems, promoting collaborative work and accurate decision-making.

[0035] In some embodiments, basic data refers to the fundamental information that forms part of master data and supports it. While basic data provides the reference and context necessary for master data, it does not inherently possess the importance or widespread applicability of master data. Basic data can include location information (such as warehouse, factory, or supplier address), units of measure, currency codes, and tax rates. It provides essential attributes and configuration information for master data, enabling it to be used and interpreted correctly within a specific context.

[0036] In summary, master data is the core data of intelligent manufacturing, used to describe and define key entities or objects to support business processes and decision-making. Basic data is part of master data and provides the reference and contextual information required by master data.

[0037] The solution mainly elaborated in the present invention is: by establishing a unified data connection framework, establishing a connection between the knowledge graph and the existing master data source and the newly implemented industrial software master data source, building an instance knowledge graph based on the existing master data source, and then initializing the master data to the newly implemented industrial software, there is no need to write different initialization scripts for different data sources, so only one knowledge graph is maintained, and it can be synchronized to each data source to establish the industrial software master data, and different versions of knowledge graphs can also initialize different master data.

[0038] Furthermore, specifically, the application scenario of this application is to use the knowledge graph to uniformly organize and maintain master data, and then connect the knowledge graph with different databases, establish different table structures according to different databases and fill in specific data, so as to achieve the effectiveness, convenience and uniformity of maintaining, managing and tracking master data in different databases in the industrial field. The knowledge graph is equivalent to an intermediary that connects existing master data and databases, making it convenient for industrial personnel to maintain, adjust and manage master data in different databases, thereby improving efficiency and reducing the cost of data management and conversion.

[0039] Based on this, the present application provides a method for constructing master data of a database, which includes:

[0040] S101, establishing a data connection between a knowledge graph and a database, wherein the knowledge graph includes first primary data;

[0041] In some embodiments, the knowledge graph represents a visual node connection diagram consisting of nodes and connecting lines. The nodes in the knowledge graph may include specific data, as well as definitions or attributes (entities) about the data. In the present application, the existing master data can be first constructed into a knowledge graph, wherein nodes of different levels are established according to the attributes, definitions and specific values ​​of the master data, and different nodes are connected according to logical relationships, reflecting the data logical relationships or other physical subordinate relationships within the currently existing master data. The so-called first master data refers to the currently existing master data. The process of establishing a data connection between the knowledge graph and the database can be through different drivers of the database, or according to the connection format requirements of different databases, to establish a data connection between the device or medium carrying the knowledge graph and the data interface of the database, thereby preparing for the subsequent data transmission and conversion of the knowledge graph.

[0042] S102, establishing a data table structure according to the database;

[0043] In some embodiments, different data table structures are established based on the different requirements and format requirements of each database for master data. The data table structure represents the attributes (entities) in the master data. The data table structure does not refer to the actual data, but rather extracts the attributes of the actual data, such as name, type, and other attributes, from the knowledge graph, thereby converting or constructing a corresponding data table structure in the database to facilitate subsequent filling of specific data. The data table structure can generate different data table structures based on the requirements of different databases. The generation of the data table structure can also be to convert the nodes related to the attribute (entity) category in the knowledge graph into the database, thereby initially forming a data table framework. It is emphasized here that the above-mentioned first master data, that is, the existing master data, will include attribute nodes and nodes related to the specific values ​​of these attributes. Constructing the data table structure is to convert these attribute nodes into a data table structure according to the requirements of the database, so as to facilitate the subsequent conversion or filling of specific data nodes into the corresponding data table.

[0044] Furthermore, different versions of the knowledge graph are released according to different databases.

[0045] In some embodiments, due to differences in databases, data table structures are also different. Therefore, different versions of knowledge graphs can be published or released for different databases. In different versions of knowledge graphs, the connection relationship of nodes and the classification of attribute nodes may be different, and the corresponding generated data table structures are also different. For example, in a new database, a new attribute of master data is added. Then for this attribute, there will be a corresponding field (filed) in the data table to fill in the specific data. Then the structure and form of this data table are different from those of the data tables of other databases.

[0046] In some embodiments, for the same database, due to changes and updates to master data over time, different versions of the knowledge graph can be published, including different attribute nodes and nodes for specific data instances. This will subsequently form different data table structures in the database, further forming different data tables. These different data tables also reflect the changes in master data over time in the same database, facilitating the tracing and management of master data in the database.

[0047] In some embodiments, the knowledge graph can establish multiple data table structures in the database. For example, the ID, name, and type attributes in the knowledge graph constitute the first data table structure, while the ID, field3, and field4 in the knowledge graph constitute the second data table structure. These different data table structures are all established and constructed to match the database's requirements for master data.

[0048] The idea behind the solution of this application is to use a knowledge graph to first meet the different forms of master data requirements of a single database, and then meet the different forms of master data requirements of multiple databases.

[0049] S103: Fill the first master data in the knowledge graph according to the data table structure to generate the second master data of the database.

[0050] In some embodiments, in the database, the master data already in the knowledge graph is populated with instance data in the data table according to the previously generated data table structure to generate master data that matches the database requirements. The second master data represents the master data that matches the database requirements.

[0051] Furthermore, a mapping relationship is established for the first main data in the knowledge graph according to the data table structure, and then based on the mapping relationship, the first main data in the knowledge graph is filled in according to the data table structure.

[0052] In some embodiments, a mapping relationship is first established between instance data (or specific data) in the knowledge graph and a data table structure. This mapping relationship can refer to a mapping relationship between specific instance data in the knowledge graph and certain fields in the data table structure under a certain attribute (entity). By establishing this mapping relationship, the actual data in the knowledge graph can then be populated into the data table structure.

[0053] When existing master data changes, corresponding changes can be made to the knowledge graph. If new master data attributes are added, nodes related to the data attributes are added to the knowledge graph, and then the nodes and attribute nodes of specific instance data are connected to the newly created attribute nodes. Accordingly, a new data table structure can be established in the database, which can include both old and new attributes. Furthermore, the corresponding instance data can be filled and improved in this new data table structure.

[0054] If only the value of the instance data changes, then update the value of the corresponding instance node in the knowledge graph, and further update the field of the corresponding mapping relationship in the data table structure.

[0055] In short, after establishing the corresponding mapping relationship, the existing master data of the knowledge graph is filled in the data table in the database to form the master data matched by the database.

[0056] Furthermore, a data connection is established between the structured first main data and the unstructured first main data in the knowledge graph and the database.

[0057] In some embodiments, a unified connectivity framework can be used to combine structured and unstructured data into a knowledge graph. Structured data includes Oracle and MySQL, and unstructured data includes MongoDB. Since the unified connectivity framework supports both forms of data, master data written in these forms can be converted into corresponding knowledge graphs, and then connected to the corresponding database to form master data that conforms to the corresponding database.

[0058] Furthermore, in the prior art, there are the following problems:

[0059] 1. When converting data models into data tables, there is no unified conversion method and the degree of customization is high. It is necessary to pre-set abstract functions for multiple database operations based on different data sources, or preset execution scripts for different data source operations.

[0060] 2. The data model and data table are independent of each other. After the data model is updated according to business needs, it cannot be updated to the data table in time, and the integrity and consistency of the data cannot be guaranteed.

[0061] 3. The data initialization method relies on external files (such as Excel), which is inconvenient to maintain. In addition, there is no version control management for the data model and instance data, which makes it difficult to track and manage changes in the data model.

[0062] Based on this, the present application provides a method for initializing the master data of industrial software based on an instance knowledge graph. The master data includes: materials, resources, plans, quality, warehousing, processes, etc. First, a unified data connection is established to construct the existing master data of the factory into an instance knowledge graph. The instance knowledge graph refers to a specific instantiation of the knowledge graph, that is, a graph that maps concepts and relationships into specific entities and association relationships. The instance knowledge graph is connected to different data sources through a unified data connection framework. After the connection is established, the instance knowledge graph can directly initialize the data model and data into the database of the newly implemented industrial software, and changes in the instance knowledge graph can directly synchronize the database. For different industry customers, the instance knowledge graph can establish different version management.

[0063] The knowledge graph, as a core service, connects to different data sources, including structured and unstructured data, through a unified data connection framework. The present invention converts existing master data sources into instance knowledge graphs, and then initializes them to the newly implemented industrial software master data. Initializing the master data involves converting knowledge graph entities and relationships into a data table structure, and then converting knowledge graph instance nodes into data in the table.

[0064] Among them, different versions of the instance knowledge graph correspond to different databases. The entity nodes and relationships of the instance knowledge graph are the data model part. The figure below shows that the present invention provides version management for the data model. Every time a version is released, the data model will create a new library, and the current entities and relationships will generate new tables in the new library. The instance data part will then be converted into industrial software master data.

[0065] The figure above shows a flow chart of the method for automatically constructing industrial software master data based on the instance knowledge graph of the present invention. The method may include the following steps:

[0066] 1. Create an instance knowledge graph: Convert existing factory master data into an instance knowledge graph;

[0067] 2. Establish data connection: Establish a connection between the instance knowledge graph and the newly implemented industrial software database;

[0068] 3. Data model conversion data table: The entity data part of the instance knowledge graph is the data model, including the attribute values ​​of the entity and the relationship between the entities, and generates a data table structure in the database;

[0069] 4. Map instance data to data tables: Based on the knowledge graph model, map instance data to specific data tables. Each data table should contain columns corresponding to entity attributes and columns corresponding to relationships between entities;

[0070] 5. Insert industrial software master data: Insert the mapped data into the corresponding data table to generate industrial software master data.

[0071] The application scenario is described as follows: When implementing a business system in a factory, such as a Manufacturing Operation Management (MOM) or Manufacturing Execution System (MES), a series of master data frequently used in factory operations must be prepared. Industrial software master data includes materials, resources, planning, quality, warehousing, and processes. This master data originates from existing business systems.

[0072] Initializing industrial software master data is a crucial step, as it directly impacts the system's normal operation and production efficiency. By connecting the knowledge graph to existing master data sources, existing factory master data is converted into an instance knowledge graph, and then the new industrial software master data is initialized and implemented.

[0073] If another factory implements the same business system but uses a different database, only the connection driver is replaced. The entity portion of the instance knowledge graph requires little or no change. Only the factory-specific instance data (such as equipment assets) is updated, allowing for rapid initialization of the industrial software master data.

[0074] As factories operate, industrial software master data can change at any time, such as with the introduction of new products or materials, changes to supplier or customer information, adjustments to units of measurement, and optimization of inventory management strategies. These changes need to be synchronized with the system in a timely manner to ensure that the system data remains consistent with actual conditions. This is achieved by publishing different versions of the instance knowledge graph, generating a new set of database tables for use, while retaining previous versions for easier tracking and management.

[0075] The technical features of the solution of this application are as follows: 1. Instantiation of knowledge graph of existing factory master data; 2. Connection to multiple data sources; 3. Version management of instance knowledge graph; 4. Synchronization and update mechanism of instance knowledge graph and database. The advantages based on the above technical features are as follows: 1. Connecting existing master data sources through a unified data connection framework to generate instance knowledge graphs; 2. Opening up the connection between the knowledge graph and various data sources through a unified data connection framework, there is no need to write different initialization scripts for different data sources when initializing data; 3. Only one knowledge graph is maintained, which can be synchronized to different data sources to establish industrial software master data; 4. Different versions of knowledge graphs can initialize different master data, which is conducive to data model tracking and management.

[0076] It should be understood that although the various steps in the flowchart of FIG1 are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in FIG1 may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0077] FIG2 provides a device 200 for constructing master data of a database. In the device 200, it includes:

[0078] A data connection module 201 is used to establish a data connection between the knowledge graph and the database, wherein the knowledge graph includes the first master data;

[0079] A structure establishment module 202 is used to establish a data table structure according to the database;

[0080] The data construction module 203 is used to fill the first master data in the knowledge graph according to the data table structure to generate the second master data of the database.

[0081] Furthermore, the data construction module 203 includes:

[0082] A data mapping module 204 is configured to establish a mapping relationship between the first primary data in the knowledge graph and the data table structure;

[0083] The data filling module 205 is used to fill the first main data in the knowledge graph according to the data table structure based on the mapping relationship.

[0084] Furthermore, the data connection module 201 is used to establish a data connection between the structured first master data and the unstructured first master data of the knowledge graph and the database.

[0085] Furthermore, it also includes a knowledge graph version module 206, which is used to publish different versions of the knowledge graph according to different databases.

[0086] It should be noted that the apparatus may include more or fewer modules to implement the described functionality. For example, at least one module in FIG. 2 may be further divided into a plurality of different submodules, each of which is configured to perform at least a portion of the operations described herein in conjunction with the corresponding module. Furthermore, in some examples, the apparatus 200 may further include additional modules for performing other operations already described in the specification. Furthermore, those skilled in the art will appreciate that the exemplary apparatus 200 may be implemented using software, hardware, firmware, or any combination thereof.

[0087] Figure 3 provides a computer device. According to one embodiment, the computer device 300 may include a processor 302, which executes a computer program stored in a memory 304. When the computer program is executed by the processor, the above method is implemented.

[0088] Those skilled in the art will understand that the structure shown in Figure 3 is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0089] Those skilled in the art will appreciate that all or part of the processes in the methods for implementing the above-mentioned embodiments can be accomplished by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include processes for the implementation of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the various embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0090] The present application also provides a computer-readable storage medium having a computer program stored thereon, which implements the above steps when the computer program is executed by a processor.

[0091] The present application also provides a computer program product, which is tangibly stored on a computer-readable medium and includes computer-executable instructions. When the computer-executable instructions are executed, the computer-executable instructions cause at least one processor to perform the above method.

[0092] Furthermore, the computer program can be stored and run in the cloud to perform the method. Furthermore, the components of the program can be deployed on multiple devices and the cloud. For example, the corresponding steps can be deployed and run on a local or local computer, or run on different cloud devices, and transmit signals through a communication connection, or can also be deployed and run on a local or local computer. This application does not limit the manner or method, and the corresponding technology can be flexibly deployed to make full use of equipment and technologies such as the cloud, big data, and supercomputing capabilities to execute and complete the method.

[0093] Some implementations of the present disclosure may include articles of manufacture. Articles of manufacture may include storage media for storing logic. Examples of storage media may include one or more types of computer-readable storage media capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and the like. Examples of logic may include various software units, such as software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols, or any combination thereof. In some implementations, for example, articles of manufacture may store executable computer program instructions that, when executed by a processor, cause the processor to perform the methods and / or operations described herein. Executable computer program instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Executable computer program instructions can be implemented according to a predefined computer language, method or syntax for commanding a computer to perform a specific function. The instructions can be implemented using any appropriate high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.

[0094] What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and / or methodologies, but those skilled in the art will appreciate that many other combinations and permutations are possible. Therefore, the novel architecture is intended to embrace all such alternatives, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims

1. A method for constructing master data of a database, wherein: include: Establishing a data connection between the knowledge graph and the database, wherein the knowledge graph includes first master data; According to the database, a data table structure is established; The first master data in the knowledge graph is filled in according to the data table structure to generate the second master data of the database.

2. According to the method of claim 1, the step of filling the first master data in the knowledge graph according to the data table structure to generate the second master data of the database comprises: Establish a mapping relationship between the first main data in the knowledge graph and the data table structure, According to the mapping relationship, the first main data in the knowledge graph is filled in according to the data table structure.

3. According to the method of claim 1, establishing a data connection between the knowledge graph and the database comprises: Establish data connection between the structured first master data and the unstructured first master data in the knowledge graph and the database.

4. The method according to claim 1, before establishing a data connection between the knowledge graph and the database, further comprising: Different versions of the knowledge graph are released according to different databases.

5. A device (200) for constructing master data of a database, wherein: include: A data connection module (201), used to establish a data connection between a knowledge graph and a database, wherein the knowledge graph includes first master data; A structure building module (202), used to build a data table structure according to the database; The data construction module (203) is used to fill the first master data in the knowledge graph according to the data table structure to generate the second master data of the database.

6. The device (200) according to claim 5, wherein: The data construction module (203) comprises: A data mapping module (204), used to establish a mapping relationship between the first main data in the knowledge graph and the data table structure; A data filling module (205) is used to fill the first main data in the knowledge graph according to the mapping relationship. Fill in the data table structure described above.

7. The device (200) according to claim 5, wherein: The data connection module (201) is used to establish a data connection between the structured first main data and the unstructured first main data in the knowledge graph and a database.

8. The device (200) according to claim 5, wherein: Also includes, The knowledge graph version module (206) is used to publish different versions of the knowledge graph according to different databases.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

11. A computer program product tangibly stored on a computer readable medium and comprising computer executable instructions which, when executed, cause at least one processor to perform the method according to any one of claims 1 to 4.

Images