Data relationship analysis method, system, computer device and readable storage medium

Abstract

The present application relates to a data relationship analysis method, system, computer device and computer-readable storage medium, wherein the data relationship analysis method includes: a configuration data mapping step, obtaining the configuration data of the entity object and using a mapping model to map the configuration data to the front-end UI component to obtain formatted data; a data encapsulation step, obtaining the formatted data and rendering it to the front-end UI page; a relationship analysis step, obtaining the trigger operation of the front-end UI page and sending the corresponding parameter object to a relationship analysis module according to the trigger operation, the relationship analysis module parses the parameter object and displays the relationship map; wherein the mapping model is established based on the parameter format provided by the relationship analysis module. Through this application, innovative business scenarios are realized, and the association and connection mechanism between entity objects and relationship analysis modules is realized to meet business needs.

Description

Technical Field

[0001] The present application relates to the field of knowledge graph technology, and in particular to data relationship analysis methods, systems, computer devices, and computer-readable storage media. Background Art

[0002] The wise system is an AI-driven data governance platform (including the structured data governance platform CONA, the unstructured text governance platform Raptor, and the associative knowledge mining product HARTS), which realizes the symbolization process of various structured and unstructured videos, images, texts and other multi-heterogeneous data. It completes data aggregation, fusion, reasoning and complex calculations through the knowledge graph database NEST, and the knowledge graph analysis platform SCOPA realizes second-level calculations and online analysis and mining.

[0003] In existing smart system products, the data model platform provides data configuration functions. According to these configuration items, different entity (schema) information will be dynamically generated. However, based on existing products, users cannot see the extended relationship of entity objects in the form of knowledge graphs. For such innovative business scenarios, the existing technology does not have a corresponding solution. Summary of the invention

[0004] The embodiments of the present application provide a data relationship analysis method, system, computer device and computer-readable storage medium, which realizes innovative business scenarios by obtaining corresponding data from entity objects and assembling them into parameter objects, and sending the parameter objects to the relationship analysis module through communication, and realizes the association and connection mechanism between entity objects and relationship analysis modules to meet business needs.

[0005] In a first aspect, an embodiment of the present application provides a data relationship analysis method, comprising:

[0006] The configuration data mapping step obtains the configuration data of the entity object and uses a mapping model to map the configuration data to the front-end UI component to obtain formatted data; specifically, in the configuration data mapping step, the front-end UI component needs to receive the configuration data returned by the back-end, but considering that the configuration data is dynamically configured, it is set to map the configuration data to the front-end UI component so that the front-end UI component can take a fixed value. In this way, even if the data key returned by the back-end changes, the front-end UI component does not need to be changed when rendering, and only needs to modify the mapping relationship of the mapping model.

[0007] The data encapsulation step obtains the formatted data through the props attribute and renders it to the front-end UI page, thereby converting the formatted data component into a parameter object; based on this, when the user moves the mouse into an entity object in the front-end UI page, a Popup component pops up, and the Popup component contains components that are independently implemented according to the front-end UI page. When the data is updated, the Popup component receives the props attribute update to trigger the update of the Popup component.

[0008] The relationship analysis step obtains the trigger operation of the front-end UI page and sends the corresponding parameter object to a relationship analysis module according to the trigger operation. The relationship analysis module parses the parameter object and displays the relationship graph. This step only requires sending the parameter object, which realizes the decoupling of the entity object and the relationship analysis module. Based on this, if there are other external modules that need to associate and connect the entity object, then the entity object only needs to be encapsulated as a parameter object according to the parameter object format given by the external module.

[0009] Wherein, the mapping model is established based on the parameter format provided by the relationship analysis module.

[0010] Based on the above steps, the embodiment of the present application obtains configuration data from the entity object and encapsulates it into a parameter object according to the parameter format provided by the relationship analysis module. When the event of the relationship analysis module is monitored to be triggered by a user operation, the parameter object in the event is sent to the relationship analysis module. The relationship analysis module receives the parameter object and parses the parameter object on a new page and displays the graph. By connecting the displayed entity object to the relationship analysis module, the user can clearly see the extended relationship of the entity object in the form of a knowledge graph, filling the solution gap under the business scenario requirements.

[0011] The embodiment of the present application takes into account that it is difficult for users to intuitively see entities and entity-related events, entity-related relationships, and relationships with other related entities when the entity objects returned by data are displayed in the canvas based on the existing knowledge graph. Therefore, a relationship analysis module is introduced. The function of this relationship analysis module is to present the related information of the entity objects to the user in a graphical manner, so that the user can understand the related information of the entity objects.

[0012] In some embodiments, the relationship analysis module includes:

[0013] The operation bar area is used to obtain entity object editing requests triggered by the user in the operation bar area, wherein the editing requests include one or any combination of entity multiple selection, entity positioning, map arrangement mode, entity removal, map clearing, entity automatic grouping, and entity display quantity setting;

[0014] A canvas area, which displays the relationship and status of the associated information of entity objects in the form of a knowledge graph through a graph analysis canvas, and obtains an information editing request issued by a user for a trigger operation on a certain entity object, wherein the information editing request includes one of condition extension, event extension, event recovery, and online relationship extension, or any combination thereof;

[0015] The statistics bar area counts the elements in the diagram canvas and displays the statistical information.

[0016] Furthermore, the relationship analysis module has built-in functional interactive operations to respond to user operations; users can trigger events in the relationship analysis module by clicking or selecting operations in the operation bar area, canvas area, or statistics bar area.

[0017] In some of the embodiments, the configuration data mapping step specifies parameters through a URL path of a relationship analysis module, and obtains corresponding configuration data from an entity object according to the URL path.

[0018] In some of the embodiments, the mapping model is stored in the form of a configuration file. Therefore, when the mapping relationship in the mapping model is modified, there is no need to repackage the deployment project, which facilitates development work.

[0019] In a second aspect, an embodiment of the present application provides a data relationship analysis system, including:

[0020] The configuration data mapping unit obtains the configuration data of the entity object and uses a mapping model to map the configuration data to the front-end UI component to obtain formatted data; specifically, in the configuration data mapping unit, the front-end UI component needs to receive the configuration data returned by the back-end, but considering that the configuration data is dynamically configured, it is set to map the configuration data to the front-end UI component so that the front-end UI component can take a fixed value. In this way, even if the data key returned by the back-end changes, the front-end UI component does not need to be changed when rendering, and only needs to modify the mapping relationship of the mapping model.

[0021] The data encapsulation unit obtains the formatted data through the props attribute and renders it to the front-end UI page, thereby converting the formatted data into a parameter object; based on this, when the user moves the mouse into an entity object in the front-end UI page, a Popup component pops up, and the Popup component contains components that are independently implemented according to the front-end UI page. When the data is updated, the Popup component receives the props attribute update to trigger the update of the Popup component.

[0022] The relationship analysis unit obtains the trigger operation of the front-end UI page and sends the corresponding parameter object to a relationship analysis module according to the trigger operation. The relationship analysis module parses the parameter object and displays the relationship graph. This unit only needs to send the parameter object, which realizes the decoupling of the entity object and the relationship analysis module. Based on this, if there are other external modules that need to associate and connect the entity object, then the entity object only needs to be encapsulated as a parameter object according to the parameter object format given by the external module.

[0023] Wherein, the mapping model is established based on the parameter format provided by the relationship analysis module.

[0024] Based on the above units, the embodiment of the present application obtains configuration data from the entity object and encapsulates it into a parameter object according to the parameter format provided by the relationship analysis module. When the event of the relationship analysis module is monitored to be triggered by a user operation, the parameter object in the event is sent to the relationship analysis module. The relationship analysis module receives the parameter object and parses the parameter object on a new page and displays the graph. By connecting the displayed entity object to the relationship analysis module, the user can clearly see the extended relationship of the entity object in the form of a knowledge graph, filling the solution gap under the business scenario requirements.

[0025] The embodiment of the present application takes into account that it is difficult for users to intuitively see entities and entity-related events, entity-related relationships, and relationships with other related entities when the entity objects returned by data are displayed in the canvas based on the existing knowledge graph. Therefore, a relationship analysis module is introduced. The function of this relationship analysis module is to present the related information of the entity objects to the user in a graphical manner, so that the user can understand the related information of the entity objects.

[0026] In some embodiments, the relationship analysis module includes:

[0027] The operation bar area is used to obtain entity object editing requests triggered by the user in the operation bar area, wherein the editing requests include one or any combination of entity multiple selection, entity positioning, map arrangement mode, entity removal, map clearing, entity automatic grouping, and entity display quantity setting;

[0028] A canvas area, which displays the relationship and status of the associated information of entity objects in the form of a knowledge graph through a graph analysis canvas, and obtains an information editing request issued by a user for a trigger operation on a certain entity object, wherein the information editing request includes one of condition extension, event extension, event recovery, and online relationship extension, or any combination thereof;

[0029] The statistics bar area counts the elements in the diagram canvas and displays the statistical information.

[0030] Furthermore, the relationship analysis module has built-in functional interactive operations to respond to user operations; users can trigger events in the relationship analysis module by clicking or selecting operations in the operation bar area, canvas area, or statistics bar area.

[0031] In some of the embodiments, the configuration data mapping unit specifies parameters through a URL path of a relationship analysis module, and obtains corresponding configuration data from an entity object according to the URL path.

[0032] In some of the embodiments, the mapping model is stored in the form of a configuration file. Therefore, when the mapping relationship in the mapping model is modified, there is no need to repackage the deployment project, which facilitates development work.

[0033] In a third aspect, an embodiment of the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the data relationship analysis method as described in the first aspect above is implemented.

[0034] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data relationship analysis method as described in the first aspect above.

[0035] Compared with related technologies, the data relationship analysis method, system, computer device and computer-readable storage medium provided in the embodiments of the present application relate to the field of knowledge graph technology. By connecting entity objects and relationship analysis modules, the problem that existing products cannot satisfy users' need to see the extended relationships of entity objects in the form of knowledge graphs is solved, thereby realizing innovative business scenarios and meeting innovative business needs.

[0036] Details of one or more embodiments of the present application are set forth in the following drawings and description to make other features, objects, and advantages of the present application more readily apparent. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0038] Figure 1 is a flow chart of a data relationship analysis method according to an embodiment of the present application;

[0039] Figure 2 is a schematic diagram of the regional distribution of the relationship analysis module according to an embodiment of the present application;

[0040] Figure 3It is a structural block diagram of a data relationship analysis system according to an embodiment of the present application. Description of the drawings:

[0042] 101. Configuration data mapping unit; 102. Data encapsulation unit; 103. Relationship analysis unit. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is described and illustrated below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments provided in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0044] Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. In addition, it can also be understood that although the efforts made in this development process may be complicated and lengthy, for ordinary technicians in this field related to the content disclosed in this application, some changes in design, manufacturing or production based on the technical content disclosed in this application are just conventional technical means, and should not be understood as insufficient content disclosed in this application.

[0045] Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those of ordinary skill in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0046] Unless otherwise defined, the technical terms or scientific terms involved in this application should be understood by people with ordinary skills in the technical field to which this application belongs. The words "one", "a", "a", "the" and the like involved in this application do not indicate a quantitative limitation, and may represent the singular or plural. The terms "include", "comprise", "have" and any of their variations involved in this application are intended to cover non-exclusive inclusions; for example, a process, method, system, product or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units that are not listed, or may also include other steps or units inherent to these processes, methods, products or devices. The words "connect", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "multiple" involved in this application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships, for example, "A and / or B" can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects before and after are in an "or" relationship. The terms "first", "second", "third", etc. involved in this application are only used to distinguish similar objects and do not represent a specific ordering of the objects.

[0047] React uses the concept of components to split the interface into reusable modules, each of which is a React component. A React application is composed of several components, and a complex component can also be composed of several simple components. Props are the properties of a react component. Once specified, they will not change during the life cycle of the specified component.

[0048] This embodiment provides a data relationship analysis method. Figure 1 is a flow chart of a data relationship analysis method according to an embodiment of the present application, such as Figure 1 As shown, the process includes the following steps:

[0049] In the configuration data mapping step S101, the configuration data of the entity object is obtained and a mapping model is used to map the configuration data to the front-end UI component to obtain formatted data; specifically, in the configuration data mapping step S101, the front-end UI component needs to receive the configuration data returned by the back-end, but considering that the configuration data is dynamically configured, the configuration data is fixedly mapped to the front-end UI component so that the front-end UI component can have a fixed value. In this way, even if the data key returned by the back-end changes, the front-end UI component does not need to be changed when rendering, and only the mapping relationship of the mapping model needs to be modified.

[0050] In the data encapsulation step S102, the formatted data is obtained through the props attribute and rendered to the front-end UI page, thereby converting the formatted data component into a parameter object; based on this, when the user moves the mouse into a certain entity object in the front-end UI page, a Popup component pops up, and the Popup component contains components that are independently implemented according to the front-end UI page. When the data is updated, the Popup component receives the props attribute update to trigger the update of the Popup component.

[0051] Relationship analysis step S103, obtain the trigger operation of the front-end UI page and send the corresponding parameter object to a relationship analysis module according to the trigger operation. The relationship analysis module parses the parameter object and displays the relationship map. This step only requires sending the parameter object, which realizes the decoupling of the entity object and the relationship analysis module. Based on this, if there are other external modules that need to be associated with the entity object, then the entity object only needs to be encapsulated as a parameter object according to the parameter object format given by the external module. Specifically, the relationship analysis module has built-in functional interactive operations to respond to user operations; users can trigger events in the relationship analysis module by clicking or selecting operations in the operation bar area, canvas area, and statistics bar area.

[0052] The mapping model is established based on the parameter format provided by the relationship analysis module.

[0053] Based on the above steps, the embodiment of the present application obtains configuration data from the entity object and encapsulates it into a parameter object according to the parameter format provided by the relationship analysis module. When the event of the relationship analysis module is monitored and triggered by a user operation, the parameter object in the event is sent to the relationship analysis module. The relationship analysis module receives the parameter object and parses the parameter object on a new page and displays the graph. By connecting the displayed entity object to the relationship analysis module, the user can clearly see the extended relationship of the entity object in the form of a knowledge graph, filling the solution gap under the business scenario requirements.

[0054] The embodiment of the present application takes into account that it is difficult for users to intuitively see entities and entity-related events, entity-related relationships, and relationships with other related entities when the entity objects returned by data are displayed in the canvas based on the existing knowledge graph. Therefore, a relationship analysis module is introduced. The function of this relationship analysis module is to present the related information of the entity objects to the user in a graphical manner, so that the user can understand the related information of the entity objects. Figure 2 is a schematic diagram of the regional distribution of the relationship analysis module according to an embodiment of the present application, with reference to Figure 2 As shown, the relationship analysis module includes:

[0055] The operation bar area obtains the entity object editing request triggered by the user in the operation bar area, and the editing request includes one or any combination of entity multiple selection, entity positioning, map arrangement mode, entity removal, map clearing, entity automatic grouping and entity display quantity setting; optionally, the operation bar area is set at the upper part of the front-end UI page; wherein, entity multiple selection can be achieved by selecting multiple entity objects in the operation bar area or holding down the Ctrl key to select multiple entity objects; entity positioning can quickly find entity objects by searching for entity objects, and optionally, the found entity objects can be highlighted in the canvas area in a selected state or in other ways; the map arrangement mode supports switching different entity object arrangement modes, such as tree structure or array structure; entity removal can directly remove the entity object and its associated information by right-clicking in the operation bar area and / or the canvas area; map clearing can clear all entity objects in the canvas area with one click; entity automatic grouping can be clustered according to the configuration data and associated information of the entity object, such as e-commerce category and news category, so that the entity objects are displayed in the canvas area according to the grouping; the entity display quantity setting is used to set a display quantity so that only the entity objects of the display quantity are displayed in the canvas area.

[0056] The canvas area displays the relationship and status of the associated information of the entity object in the form of a knowledge graph through the graph analysis canvas, and obtains the information editing request issued by the user for the trigger operation of a certain entity object, and the information editing request includes one or any combination of condition extension, event extension, event recovery, and online relationship extension; optionally, the canvas area is set in the middle of the front-end UI page; the information editing request can be set under a menu bar that pops up by right-clicking a certain entity object. By default, the knowledge graph only displays the first-degree relationship of the entity object, and based on the menu bar of this embodiment, the second-degree relationship of the entity object can be obtained by selecting condition extension, time extension, or online relationship extension and displayed in the canvas area.

[0057] The statistics bar area counts the elements in the diagram canvas and displays the statistical information. Optionally, the statistics bar is set on the right side of the front-end UI page. Specifically, when there is no selected element in the diagram canvas, the statistics bar area counts all the elements in the diagram canvas; if there is a selected element in the diagram canvas, statistics are counted for the selected element, and the statistical information can be divided into major categories and minor categories. When an element is selected, statistics are first performed by major category. Click the major category information on the right to drill down to the minor category statistics.

[0058] In some embodiments, the configuration data mapping step S101 specifies parameters through the URL path of the relationship analysis module, and obtains corresponding configuration data from the entity object according to the URL path. By way of example and not limitation, the URL path is "http: / / service deployment domain:service deployment port / front / graph / id / :id / groupId / docId"; the URL path uses the unique ID of the entity object as a request parameter and reflects the group ID and / or document ID of the entity object.

[0059] In some of the embodiments, the mapping model is stored in the form of a configuration file. Therefore, when the mapping relationship in the mapping model is changed, there is no need to repackage the deployment project, which facilitates development work.

[0060] It should be noted that the steps shown in the above process or the flowchart in the attached figure can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here. For example, step S101 and step S102 can also be executed after step S103 receives a trigger operation from the user.

[0061] This embodiment also provides a data relationship analysis system, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As used below, the terms "module", "unit", "subunit", etc. can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0062] Figure 3 is a structural block diagram of a data relationship analysis system according to an embodiment of the present application, such as Figure 3 As shown, the system includes:

[0063] The configuration data mapping unit 101 obtains the configuration data of the entity object and uses a mapping model to map the configuration data to the front-end UI component to obtain formatted data; specifically, in the configuration data mapping unit 101, the front-end UI component needs to be used to receive the configuration data returned by the back-end, but considering that the configuration data is dynamically configured, it is set to map the configuration data to the front-end UI component so that the front-end UI component can be fixed. In this way, even if the data key returned by the back-end changes, the front-end UI component does not need to be changed when rendering, and only the mapping relationship of the mapping model needs to be modified. Specifically, the configuration data mapping unit 101 specifies the parameters through the URL path of the relationship analysis module, and obtains the corresponding configuration data from the entity object according to the URL path. For example, but not limitation, the URL path is "http: / / service deployment domain: service deployment port / front / graph / id / :id / groupId / docId"; the URL path uses the unique ID of the entity object as a request parameter and reflects the group ID and / or document ID of the entity object. Specifically, the mapping model is stored in the form of a configuration file, so when the mapping relationship in the mapping model is changed, there is no need to repackage the deployment project, which is convenient for development work.

[0064] The data encapsulation unit 102 obtains formatted data through the props attribute and renders it to the front-end UI page, thereby converting the formatted data component into a parameter object; based on this, when the user moves the mouse into a certain entity object in the front-end UI page, a Popup component pops up, and the Popup component contains components that are independently implemented according to the front-end UI page. When the data is updated, the Popup component receives the props attribute update to trigger the update of the Popup component.

[0065] The relationship analysis unit 103 obtains the trigger operation of the front-end UI page and sends the corresponding parameter object to a relationship analysis module according to the trigger operation. The relationship analysis module parses the parameter object and displays the relationship graph. This unit only needs to send the parameter object, thereby realizing the decoupling of the entity object and the relationship analysis module. Based on this, if there are other external modules that need to associate and connect the entity object, then the entity object only needs to be encapsulated as a parameter object according to the parameter object format given by the external module.

[0066] The mapping model is established based on the parameter format provided by the relationship analysis module.

[0067] Based on the above units, the embodiment of the present application obtains configuration data from the entity object and encapsulates it into a parameter object according to the parameter format provided by the relationship analysis module. When the event of the relationship analysis module is monitored to be triggered by a user operation, the parameter object in the event is sent to the relationship analysis module. The relationship analysis module receives the parameter object and parses the parameter object on a new page and displays the graph. By connecting the displayed entity object to the relationship analysis module, the user can clearly see the extended relationship of the entity object in the form of a knowledge graph, filling the solution gap under the business scenario requirements.

[0068] The embodiments of the present application take into account that it is difficult for users to intuitively see entities and entity-related events, entity-related relationships, and relationships with other related entities when the entity objects returned by the data are displayed in the canvas based on the existing knowledge graph. Therefore, a relationship analysis module is introduced. The function of this relationship analysis module is to present the related information of the entity objects to the user in a graphical manner so that the user can understand the related information of the entity objects. Among them, the relationship analysis module has built-in functional interactive operations to respond to user operations; users can trigger events in the relationship analysis module by clicking or selecting operations in the operation bar area, canvas area, and statistics bar area. Specifically, refer to Figure 2As shown, the relationship analysis module includes: an operation bar area, obtaining an entity object editing request issued by a user triggering an operation in the operation bar area, the editing request including multiple entity selection, entity positioning, graph arrangement mode, entity removal, graph clearing, entity automatic grouping and entity display quantity setting or any combination thereof; wherein, entity multiple selection can be achieved by selecting multiple entity objects in the operation bar area or by holding down the Ctrl key to select multiple entity objects; entity positioning can quickly find entity objects by searching for entity objects, and optionally, the found entity objects can be highlighted in a selected state or in other ways in the canvas area; the graph arrangement mode supports switching different entity object arrangement modes, such as a tree structure or an array structure; entity removal can directly remove the entity object and its associated information by right-clicking in the operation bar area and / or the canvas area; graph clearing can clear all entity objects in the canvas area with one click; entity automatic grouping can be clustered according to the configuration data and associated information of the entity object, such as e-commerce and news, so that the entity objects are displayed in the canvas area according to the grouping; the entity display quantity setting is used to set a display quantity so that only the entity objects of the display quantity are displayed in the canvas area. The canvas area displays the relationship and status of the associated information of the entity object in the form of a knowledge graph through the graph analysis canvas, and obtains the information editing request issued by the user to trigger an operation on a certain entity object. The information editing request includes one or any combination of conditional expansion, event expansion, event recovery, and online relationship expansion; the information editing request can be set under a menu bar that pops up by right-clicking an entity object. By default, the knowledge graph only displays the first-degree relationship of the entity object, and based on the menu bar of this embodiment, the second-degree relationship of the entity object can be obtained and displayed in the canvas area by selecting conditional expansion, time expansion or online relationship expansion. The statistics bar area counts the elements in the graph analysis canvas and displays the statistical information. Optionally, the operation bar area is set at the upper part of the front-end UI page; the canvas area is set in the middle of the front-end UI page; the statistics bar is set on the right side of the front-end UI page. When there is no selected element in the diagram analysis canvas, the statistics bar area will perform statistics on all elements in the diagram analysis canvas; if there is a selected element in the diagram analysis canvas, statistics will be performed on the selected element, and the statistical information can be divided into major categories and minor categories. When an element is selected, statistics will be performed by major category first. Click the major category information on the right to drill down to the minor category statistics.

[0069] It should be noted that the above modules can be functional modules or program modules, and can be implemented by software or hardware. For modules implemented by hardware, the above modules can be located in the same processor; or the above modules can be located in different processors in any combination.

[0070] In addition, combined Figure 1The data relationship analysis method described in the embodiment of the present application can be implemented by a computer device. The computer device may include a processor and a memory storing computer program instructions.

[0071] Specifically, the processor may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0072] Among them, the memory may include a large capacity memory for data or instructions. By way of example and not limitation, the memory may include a hard disk drive (HDD), a floppy disk drive, a solid state drive (SSD), a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory may include a removable or non-removable (or fixed) medium. Where appropriate, the memory may be inside or outside the data processing device. In a specific embodiment, the memory is a non-volatile memory. In a specific embodiment, the memory includes a read-only memory (ROM) and a random access memory (RAM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (Programmable Read-Only Memory, PROM for short), an erasable PROM (Erasable Programmable Read-Only Memory, EPROM for short), an electrically erasable PROM (Electrically Erasable Programmable Read-Only Memory, EEPROM for short), an electrically alterable ROM (Electrically Alterable Read-Only Memory, EAROM for short) or a flash memory (FLASH) or a combination of two or more of these. Under appropriate circumstances, the RAM can be a static random access memory (SRAM) or a dynamic random access memory (DRAM), wherein the DRAM can be a fast page mode dynamic random access memory (FPMDRAM), an extended data output dynamic random access memory (EDODRAM), a synchronous dynamic random access memory (SDRAM), etc.

[0073] The memory may be used to store or cache various data files required for processing and / or communication, as well as possible computer program instructions executed by the processor.

[0074] The processor implements any one of the data relationship analysis methods in the above embodiments by reading and executing computer program instructions stored in the memory.

[0075] In addition, in combination with the data relationship analysis method in the above embodiments, the present application embodiment can provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any one of the data relationship analysis methods in the above embodiments is implemented.

[0076] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0077] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A data relationship analysis method, characterized in that: include: Configuration data mapping step, obtaining configuration data of the entity object and mapping the configuration data to the front-end UI component using a mapping model to obtain formatted data, using the front-end UI component to receive the configuration data returned by the back-end, setting the configuration data to be fixedly mapped to the front-end UI component so that the front-end UI component can have a fixed value; The data encapsulation step is to obtain the formatted data through the props attribute and render it to the front-end UI page, and to compose the formatted data into a parameter object, wherein when the user moves the mouse into a certain entity object in the front-end UI page, a Popup component independently implemented according to the front-end UI page pops up, and when the data is updated, the Popup component receives the props attribute update to trigger the update of the Popup component; The relationship analysis step is to obtain the trigger operation of the front-end UI page and send the corresponding parameter object to a relationship analysis module according to the trigger operation. The relationship analysis module parses the parameter object and displays the relationship map. The relationship analysis module has built-in functional interactive operations for responding to user operations. The user can click or select an operation in the operation bar area, canvas area, and statistics bar area to trigger an event of the relationship analysis module. The configuration data is the data corresponding to the parameters specified by the URL path of the relationship analysis module and obtained from the entity object according to the URL path; Wherein, the mapping model is established based on the parameter format provided by the relationship analysis module; Wherein, the relationship analysis module includes: The operation bar area obtains the entity object editing request issued by the trigger operation, wherein the editing request includes one or any combination of entity multiple selection, entity positioning, map arrangement mode, entity removal, map clearing, entity automatic grouping and entity display quantity setting; A canvas area, which displays the associated information of entity objects in the form of a knowledge graph through a graph analysis canvas, and obtains an information editing request issued by a trigger operation on a certain entity object, wherein the information editing request includes one of condition extension, event extension, event recovery, and online relationship extension, or any combination thereof; The statistics bar area counts the elements in the diagram canvas and displays the statistical information.

2. The data relationship analysis method according to claim 1, characterized in that: The mapping model is stored in the form of a configuration file.

3. A data relationship analysis system, characterized in that: include: A configuration data mapping unit is configured to obtain configuration data of an entity object and map the configuration data to a front-end UI component using a mapping model to obtain formatted data, receive the configuration data returned by the back-end using the front-end UI component, and set the configuration data to be fixedly mapped to the front-end UI component so that the front-end UI component can take fixed values; A data encapsulation unit, which obtains the formatted data through the props attribute and renders it to the front-end UI page, and composes the formatted data into a parameter object, wherein when the user moves the mouse into a certain entity object in the front-end UI page, a Popup component independently implemented according to the front-end UI page pops up, and when the data is updated, the Popup component receives the props attribute update to trigger the update of the Popup component; A relationship analysis unit, which obtains the trigger operation of the front-end UI page and sends the corresponding parameter object to a relationship analysis module according to the trigger operation. The relationship analysis module parses the parameter object and displays the relationship map. The relationship analysis module has built-in functional interactive operations for responding to user operations. The user can click or select an operation in the operation bar area, canvas area, and statistics bar area to trigger an event of the relationship analysis module. The configuration data is the data corresponding to the parameters specified by the URL path of the relationship analysis module and obtained from the entity object according to the URL path; Wherein, the mapping model is established based on the parameter format provided by the relationship analysis module; Wherein, the relationship analysis module includes: The operation bar area obtains the entity object editing request issued by the trigger operation, wherein the editing request includes one or any combination of entity multiple selection, entity positioning, map arrangement mode, entity removal, map clearing, entity automatic grouping and entity display quantity setting; A canvas area, which displays the associated information of entity objects in the form of a knowledge graph through a graph analysis canvas, and obtains an information editing request issued by a trigger operation on a certain entity object, wherein the information editing request includes one of condition extension, event extension, event recovery, and online relationship extension, or any combination thereof; The statistics bar area counts the elements in the diagram canvas and displays the statistical information.

4. The data relationship analysis system according to claim 3, characterized in that: The mapping model is stored in the form of a configuration file.

5. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the data relationship analysis method according to claim 1 or 2 is implemented.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the data relationship analysis method as claimed in claim 1 or 2 is implemented.

Images