Data model establishment method and device, equipment and medium

Abstract

The invention discloses a data model establishing method and device, equipment and a medium, and the method comprises the steps: obtaining an entity object selected by a user and model information set by the user, and generating a data model according to the entity object and the model information; calling an ID generation interface according to an entity node corresponding to the entity object to generate a model ID and an account ID corresponding to the data model; determining a node position relationship of the entity node in a main channel path table according to an entity object ID table corresponding to the model ID, an entity object account table corresponding to the account ID and the main channel path table; and mapping the node position relationship with the data model to complete establishment of the data model. According to the method and the system, the establishment of the model is simple and efficient, the security and uniqueness of the data model are ensured, and the effective management of the data model is realized.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of data model technology, and in particular to a data model establishment method, apparatus, device, and medium. Background Art

[0002] In traditional data management and modeling, building data models that meet business needs typically requires specialized database knowledge and technical expertise. Traditional database modeling involves writing complex SQL statements and designing database structures, which poses a high learning and operational barrier for non-technical personnel. Furthermore, data models created using traditional methods often lack flexibility in managing relationships between models and defining the model lifecycle, resulting in high costs for use and maintenance.

[0003] To address this issue, a number of low-code and no-code platforms have emerged, attempting to simplify operations for business personnel through visualization and configuration tools. However, these tools often have limited functionality when handling complex business scenarios and cannot effectively meet the personalized and dynamic data management needs of enterprises. Furthermore, existing tools still have shortcomings in data model lifecycle management, entity relationship processing, and performance optimization in distributed environments. Summary of the Invention

[0004] The embodiments of the present invention provide a data model establishment method, apparatus, device and medium, aiming to solve the problems of complex establishment and low security of existing data models.

[0005] In a first aspect, an embodiment of the present invention provides a method for establishing a data model, comprising: Acquire the entity object selected by the user and the model information set by the user, and generate a data model based on the entity object and the model information; Calling an ID generation interface according to the entity node corresponding to the entity object to generate a model ID and an account ID corresponding to the data model; Determine the node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID, and the main channel path table; The node position relationship is mapped to the data model to complete the establishment of the data model.

[0006] In a second aspect, an embodiment of the present invention further provides a data model establishment device, comprising: an acquisition and generation unit, configured to acquire an entity object selected by a user and model information set by the user, and generate a data model according to the entity object and the model information; Call generation, for calling an ID generation interface according to the entity node corresponding to the entity object to generate a model ID and an account ID corresponding to the data model; a determining unit, configured to determine a node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID, and the main channel path table; A mapping unit is used to map the node position relationship with the data model to complete the establishment of the data model.

[0007] In a third aspect, an embodiment of the present invention further provides a computer device, comprising a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the above method when executing the computer program.

[0008] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program can implement the above method when executed by a processor.

[0009] The embodiment of the present invention provides a method, device, equipment and medium for establishing a data model. Among them, the method includes: obtaining the entity object selected by the user and the model information set by the user, generating a data model according to the entity object and the model information; calling the ID generation interface according to the entity node corresponding to the entity object to generate the model ID and account ID corresponding to the data model; determining the node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID and the main channel path table; mapping the node position relationship with the data model to complete the establishment of the data model. The technical solution of the embodiment of the present invention can generate a data model according to the entity object selected by the user and the set model information, so that the establishment of the model is simple and efficient; generating a model ID and account ID representing the data model to ensure the security and uniqueness of the data model; and mapping the node position relationship with the data model to facilitate the call of the data model, thereby realizing the effective management of the data model. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0011] Figure 1A flowchart of a method for establishing a data model provided by an embodiment of the present invention; Figure 2 A schematic diagram of a sub-process of a data model establishment method provided by an embodiment of the present invention; Figure 3 A schematic diagram of another sub-process of a data model establishment method provided by an embodiment of the present invention; Figure 4 A schematic diagram of another sub-process of a data model establishment method provided by an embodiment of the present invention; Figure 5 A schematic block diagram of a data model establishment device provided by an embodiment of the present invention; Figure 6 A schematic block diagram of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0012] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0013] It will be understood that when used in this specification and the appended claims, the terms “comprises” and “comprising” indicate the presence of described features, integers, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0014] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the present invention. As used in the specification and appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise.

[0015] It should be further understood that the term "and / or" used in the present description and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0016] As used in this specification and the appended claims, the term “if” can be interpreted as “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [described condition or event] is detected” can be interpreted as meaning “upon determination” or “in response to determining” or “upon detection of [described condition or event]” or “in response to detecting [described condition or event],” depending on the context.

[0017] See also Figure 1 , Figure 1 1 is a flow chart of a method for establishing a data model according to an embodiment of the present invention. The method for establishing a data model is described in detail below. Figure 1 As shown, the method includes the following steps S110-S140.

[0018] S110: Acquire an entity object selected by a user and model information set by the user, and generate a data model according to the entity object and the model information.

[0019] In this embodiment, the user selects an entity object and sets the model information on the general industry data model service tool (hereinafter referred to as the digital model editor). After completion, the digital model editor obtains the entity object selected by the user and the model information set by the user, and generates a data model based on the entity object and the model information, wherein the model information includes name, date, purpose and attribute information.

[0020] In one embodiment, if Figure 2 As shown, step S110 may specifically include steps S111-S116: S111. Identify the type of the entity object; S112: If the entity object is an organization entity object, call the organization model from the database, and generate the data model according to the organization model and the model information; S113: If the entity object is a role entity object, calling a role model from the database, and generating the data model according to the role model and the model information; S114: If the entity object is a spatial entity object, calling a spatial model from the database, and generating the data model according to the spatial model and the model information; S115. If the entity object is an element entity object, call the element model from the database, and generate the data model according to the element model and the model information; S116: If the entity object is an active entity object, call the active model from the database, and generate the data model according to the active model and the model information.

[0021] In this embodiment, the types of entity objects include organizations, roles, spaces, elements, and activities, and organizations are represented by O, roles are represented by P, spaces are represented by S, elements are represented by E, and activities are represented by A. In the database, there are stored organization models, role models, space models, element models, and activity models. Therefore, according to the type of entity object, the corresponding model is called from the database, and the data model can be generated according to the called model and model information. It should be noted that in this embodiment, in addition to generating models, model relationships can also be generated. The model relationship is the relationship between the data model and other data models stored in the database. It should also be noted that through the above steps S111-S116, in a code-free manner, users can easily build data models of five entity dimensions including organizations, roles, spaces, elements, and activities without having a deep technical background.

[0022] S120 : Calling an ID generation interface according to the entity node corresponding to the entity object to generate a model ID and an account ID corresponding to the data model.

[0023] In this embodiment, each entity node in the main channel path table corresponds to a metadata table, and the metadata table is divided into libraries according to the preset logic and classified according to organization, role, space, element and activity. The data model is developed according to the preset logic. Specifically, the preset logic is the 0-1-2-3 tool logic, and the 0-1-2-3 tool logic refers to: 0-0 layer tool developer organization, 1-1 layer industry developer organization, 2-2 layer organization instantiation, 3-3 layer organization operation, and the data model is developed according to the preset logic. Specifically, first develop layer 0, then there is layer 1, and with layer 1, there are layer 2, and with layer 2, there are layer 3. It should be noted that in this embodiment, the entity nodes include organization entity nodes, role entity nodes, space entity nodes, element entity nodes and activity entity nodes, and the ID generation interface includes organization ID generation interface, role ID generation interface, space ID generation interface, element ID generation interface and activity ID generation interface. It should also be noted that in this embodiment, the uniqueness and security of the data model in operation and management are ensured through the model ID and account ID. The digital model editor not only manages the entire lifecycle of data models, but also optimizes cross-model data flow and relationship management, improving data interoperability and consistency. This greatly simplifies the data modeling process and increases the flexibility and efficiency of enterprise data management.

[0024] In one embodiment, if Figure 3 As shown, step S120 may specifically include steps S121-S125: S121. If the entity node corresponding to the entity object is the organization entity node, calling the organization ID generation interface to generate the model ID and the account ID corresponding to the data model; S122: If the entity node corresponding to the entity object is the role entity node, calling the role ID generation interface to generate the model ID and the account ID corresponding to the data model; S123: If the entity node corresponding to the entity object is the space entity node, calling the space ID generation interface to generate the model ID and the account ID corresponding to the data model; S124. If the entity node corresponding to the entity object is the element entity node, calling the element ID generation interface to generate the model ID and the account ID corresponding to the data model; S125: If the entity node corresponding to the entity object is the active entity node, call the active ID generation interface to generate the model ID and the account ID corresponding to the data model.

[0025] In this embodiment, the organization ID generation interface includes an organization ID generation sub-interface, and step S121 specifically includes: if the entity node corresponding to the entity object is the organization entity node, then identifying the organization type of the organization entity node; setting the organization type reference field in the input parameter of the organization ID generation sub-interface according to the organization type; calling the organization ID generation sub-interface according to the input parameter after setting to generate the model ID and the account ID corresponding to the data model. It should be noted that, in this embodiment, the organization type of the organization entity node includes personal organization, corporate organization, family organization, government organization and social organization. The input parameters of the organization ID generation interface are shown in Table 1, and the output parameters of the organization ID generation interface are shown in Table 2. It should also be noted that, in this embodiment, the input of the organization ID generation sub-interface is different from the input parameters of the organization ID generation interface, except for the value description of the orgType field. Specifically, "Op" is an individual organization; "Of" is a family organization; "Oe" is a corporate organization; "Os" is a social organization; and "Og" is a government organization. The output of the organization ID generation sub-interface is the same as the output parameters of the organization ID generation interface. The input of the role ID generation interface is different from the input parameters of the organization ID generation interface, except for the roleType field. The roleType field indicates the organization role type code. Value description: "Rx" is the organizational role; "Ro" is the owner; "Rp" is the operator; "Rm" is the manager; "Re" is the executor; and "Rv" is the evaluator. The output of the role ID generation interface is different from the output parameters of the organization ID generation interface, except for the topseaID field indicating the role TOPSEA ID. Compared with the input parameters of the organization ID generation interface, the input of the spatial ID generation interface has two different fields, namely industrialType and admDivision. The industrialType field indicates the industry type. Value description: refer to the industry coding standard table; the admDivision field indicates the administrative division classification code. Value description: refer to the administrative division standard table; the output of the spatial ID generation interface is compared with the output parameters of the organization ID generation interface, and the topseaID field is represented as the spatial TOPSEA ID. Compared with the input parameters of the element ID generation interface, the input of the element ID generation interface is different from the input parameters of the organization ID generation interface, namely industrialType and elementType. The industrialType field indicates the industry type. Value description: refer to the industry coding standard table; the elementType field indicates the element type code. Value description: refer to the CPC product type standard table. Compared with the output parameters of the element ID generation interface and the organization ID generation interface, the topseaID field is represented as the element TOPSEA ID.The input parameters of the Activity ID Generation API differ from those of the Organization ID Generation API in only two fields: industrialType and activityType. The industrialType field indicates the industry type. Value Description: Refer to the industry coding standard table. The activityType field indicates the activity type code. The output parameters of the Activity ID Generation API differ from those of the Organization ID Generation API in that the topseaID field indicates the activity's TOPSEA ID.

[0026] Table 1

[0027] Table 2

[0028] S130. Determine the node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID, and the main channel path table.

[0029] In this embodiment, if Figure 4 As shown, step S130 may specifically include steps S131-S133: S131, associating the entity object ID table corresponding to the model ID with the entity object account table corresponding to the account ID through the ID account association table; S132, associating the model ID in the entity object ID table with the data relationship table corresponding to the entity object, wherein the main channel path table stores the predecessor model ID and the successor model ID corresponding to the predecessor entity node and the successor entity node of the entity node in the main channel path table; S133, associating the entity object ID table with the entity node to obtain the node position relationship of the entity node in the main channel path table. It should be noted that, in this embodiment, the entity object ID table is shown in Table 3; the ID account association table stores the model ID, account ID and the mapping relationship between them; the entity object account table is shown in Table 4. It should also be noted that, in the present embodiment, during the process of establishing the data model, an entity object data relationship table will also be generated. The entity object data relationship table is shown in Table 5. Various tables can be generated through the entity object data relationship table. Specifically, an entity object template main table, an entity object sub-template main table, an entity object template slave table, an entity object sub-template slave table, an entity object sub-template extended slave table, an entity object sub-template extended attribute table, an entity object sub-template attribute table, an entity object template attribute table, an entity object instance dynamic main table, an entity object instance dynamic extension table, and an entity object instance dynamic main table can be generated.

[0030] Table 3 Field Name type Remark id int Database primary key opsea_id varchar ID of OPSEA (Organization O, Role P, Space S, Element E, Activity A) entity_type varchar Object type: Organization [corporate organization, family organization, personal organization, social organization, government organization], Role [organizational role, activity role, role responsibilities / rights / benefits], Space, Elements, Activities, Image, Communication path text Main channel path table path status int Default value is 1, which means enabled; 0 means disabled

[0031] Table 4

[0032] Table 5

[0033] S140: Map the node position relationship with the data model to complete the establishment of the data model.

[0034] In this embodiment, the node position relationship is mapped to the data model. After the data model is established, the model can be published and packaged. All tables involved in the data model can be added, deleted, modified and queried. Not only that, the tables can also be packaged and published.

[0035] It should be noted that, in this embodiment, after the data model builder constructs the data model, it designs the model, for example, defines the model life cycle, defines the model relationship, defines the table attributes, etc., and then publishes the model to the resource library; the data model operator obtains the latest data model version from the resource library, and reviews the latest data model version. After the review is passed, the latest data model version is published to the digital model mall; the data model demander views the data model details from the digital model mall, obtains the data model to the organization's resource library, and the data model demander creates an activity model, designs the activity model, and adds the data model to the activity model.

[0036] It should also be noted that, in this embodiment, in the main channel path table, if a preset call instruction is received, the data model is called according to the preset call instruction.

[0037] For ease of understanding, taking logistics management as an example, the traditional practice is that the product manager conducts demand research and design, and then the architect does technical design, such as sorting out through domain model design, writing outline design documents, domain division, life cycle, defining behavior, events, etc., and programmers do detailed design, interface definition, etc. The data model establishment method in this embodiment can greatly lower the threshold. Business experts or senior business personnel who have a better understanding of the business can define the data model, the relationship between models, table definitions, table relationships, etc., and finally form an ER diagram, define the life cycle, business processes, etc., and complete the tasks originally completed by multiple roles such as product managers / architects / programmers by themselves, and can reuse them.

[0038] In summary, the data modeling method in this embodiment: 1. Lowers the technical barrier to entry. Traditional data modeling tools typically require users to possess in-depth database knowledge and technical skills, making it difficult for non-technical personnel to participate in model design and management, limiting the effective utilization of business personnel by enterprises. This method, through codeless configuration, provides an intuitive user interface, allowing users to directly define and manage data models within business scenarios, significantly lowering the technical barrier to entry. 2. Enhances the flexibility of relationship management. In complex business environments, data models have multiple levels of relationships and dependencies, and existing solutions often lack flexibility and scalability in handling these relationship chains. This method, through the structural setting of five entity dimensions (organization, role, space, element, and activity), enables users to easily construct relationships between models and dynamically manage and transfer them through activities. 3. Improves lifecycle management. Existing technologies generally lack systematic management support for the data model lifecycle, making it difficult to automate and intelligently manage model creation, use, and retirement. This method provides comprehensive lifecycle management, allowing users to define multiple stages and sub-stages of a model and enable transfers between stages through activities, reducing the maintenance burden and improving management effectiveness. 4. Provide unified identity management. Traditional identity (ID) management in distributed systems often leads to data confusion and conflicts. The lack of a unified identifier affects data uniqueness and traceability. This approach uses model IDs and account IDs to ensure data consistency, security, and reliability, especially in cross-system environments. 5. Cross-dimensional business scenario management. For complex business scenarios, traditional methods struggle to achieve cross-dimensional integration and management. This approach, through the TOPSEA dimension (T time / O organization / P role / E element / A activity) architecture, provides a multi-dimensional and flexible integration solution for industry business scenarios, effectively supporting the business needs of all industries. 6. Optimize the user experience. The user interfaces of many existing tools lack intuitiveness and ease of use, resulting in complex and inefficient user operations. This approach uses a code-free graphical interface and configuration tools to enable users to intuitively model and operate databases, simplifying processes, reducing errors, and improving the overall user experience.

[0039] Figure 5 FIG is a schematic block diagram of a data model building device 200 provided by an embodiment of the present invention. Figure 5 As shown, corresponding to the above data model establishment method, the present invention also provides a data model establishment device 200. The data model establishment device 200 includes a unit for executing the above data model establishment method, and the device can be configured in a computer device. Specifically, please refer to Figure 5 The data model building device 200 includes an acquisition and generation unit 201, a calling unit 202, a determination unit 203 and a mapping unit 204.

[0040] Among them, the acquisition generation unit 201 is used to obtain the entity object selected by the user and the model information set by the user, and generate a data model based on the entity object and the model information; the calling unit 202 is used to call the ID generation interface according to the entity node corresponding to the entity object to generate the model ID and account ID corresponding to the data model; the determination unit 203 is used to determine the node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID, and the main channel path table; the mapping unit 204 is used to map the node position relationship with the data model to complete the establishment of the data model.

[0041] In some embodiments, such as the present embodiment, the acquisition generation unit 201 is specifically used to identify the type of the entity object; if the entity object is an organizational entity object, the organizational model is called from the database, and the data model is generated based on the organizational model and the model information; if the entity object is a role entity object, the role model is called from the database, and the data model is generated based on the role model and the model information; if the entity object is a spatial entity object, the spatial model is called from the database, and the data model is generated based on the spatial model and the model information; if the entity object is an element entity object, the element model is called from the database, and the data model is generated based on the element model and the model information; if the entity object is an activity entity object, the activity model is called from the database, and the data model is generated based on the activity model and the model information.

[0042] In some embodiments, such as the present embodiment, the calling unit 202 is specifically used to call the organization ID generation interface to generate the model ID and the account ID corresponding to the data model if the entity node corresponding to the entity object is the organization entity node; call the role ID generation interface to generate the model ID and the account ID corresponding to the data model if the entity node corresponding to the entity object is the role entity node; call the space ID generation interface to generate the model ID and the account ID corresponding to the data model if the entity node corresponding to the entity object is the space entity node; call the element ID generation interface to generate the model ID and the account ID corresponding to the data model if the entity node corresponding to the entity object is the element entity node; call the activity ID generation interface to generate the model ID and the account ID corresponding to the data model if the entity node corresponding to the entity object is the activity entity node.

[0043] In certain embodiments, such as the present embodiment, the calling unit 202 is further used to identify the organization type of the organization entity node if the entity node corresponding to the entity object is the organization entity node; set the organization type reference field in the input parameter of the organization ID generation sub-interface according to the organization type; and call the organization ID generation sub-interface according to the input parameter after setting to generate the model ID and the account ID corresponding to the data model.

[0044] In some embodiments, such as the present embodiment, the determination unit 203 is specifically used to associate the entity object ID table corresponding to the model ID with the entity object account table corresponding to the account ID through an ID account association table; associate according to the model ID in the entity object ID table with the data relationship table corresponding to the entity object, wherein the main channel path table stores the predecessor model ID and the successor model ID corresponding to the predecessor entity node and the successor entity node of the entity node in the main channel path table; associate the entity object ID table with the entity node to obtain the node position relationship of the entity node in the main channel path table.

[0045] The above-mentioned data model building device can be implemented in the form of a computer program. The computer program can be used in Figure 6 Runs on the computer equipment shown.

[0046] See also Figure 6 , Figure 6 3 is a schematic block diagram of a computer device provided by an embodiment of the present invention. The computer device 300 is a device with a data model building function.

[0047] See Figure 6 The computer device 300 includes a processor 302 , a memory, and a network interface 305 connected via a system bus 301 , wherein the memory may include a non-volatile storage medium 303 and an internal memory 304 .

[0048] The non-volatile storage medium 303 may store an operating system 3031 and a computer program 3032. When the computer program 3032 is executed, the processor 302 may execute a data model building method.

[0049] The processor 302 is used to provide computing and control capabilities to support the operation of the entire computer device 300.

[0050] The internal memory 304 provides an environment for the operation of the computer program 3032 in the non-volatile storage medium 303. When the computer program 3032 is executed by the processor 302, the processor 302 can execute a data model establishment method.

[0051] The network interface 305 is used to communicate with other devices through the network. Figure 6 The structure shown in the figure is merely a block diagram of a portion of the structure related to the solution of the present invention, and does not constitute a limitation on the computer device 300 to which the solution of the present invention is applied. The specific computer device 300 may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0052] The processor 302 is configured to run a computer program 3032 stored in a memory to implement any embodiment of the above-mentioned data model establishment method.

[0053] It should be understood that in this embodiment, the processor 302 may be a central processing unit (CPU), and may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0054] Those skilled in the art will appreciate that all or part of the steps in the method of the above-described embodiment can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the steps in the method of the above-described embodiment.

[0055] Therefore, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program. When executed by a processor, the computer program causes the processor to perform any embodiment of the above-mentioned data model establishment method.

[0056] The storage medium may be any computer-readable storage medium that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk.

[0057] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the composition and steps of each example according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0058] In the several embodiments provided herein, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the various units is merely a logical functional division, and actual implementation may employ other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0059] The steps in the methods of the embodiments of the present invention may be adjusted in order, combined, or deleted as needed. The units in the devices of the embodiments of the present invention may be combined, divided, or deleted as needed. Furthermore, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit.

[0060] If this integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes a number of instructions for causing a computer device to execute all or part of the steps of the method described in various embodiments of the present invention.

[0061] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0062] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, to the extent such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to encompass such changes and modifications.

[0063] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and such modifications or substitutions are intended to be within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be subject to the scope of protection of the claims.

Claims

1. A data model establishment method, applied to data model construction, characterized in that: include: Acquire the entity object selected by the user and the model information set by the user, and generate a data model based on the entity object and the model information; Calling an ID generation interface according to the entity node corresponding to the entity object to generate a model ID and an account ID corresponding to the data model; Determine the node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID, and the main channel path table; The node position relationship is mapped to the data model to complete the establishment of the data model.

2. The method according to claim 1, characterized in that Generating a data model according to the entity object and the model information includes: Identifying the type of the entity object; If the entity object is an organization entity object, calling the organization model from the database, and generating the data model according to the organization model and the model information; If the entity object is a role entity object, calling a role model from the database, and generating the data model according to the role model and the model information; If the entity object is a spatial entity object, calling a spatial model from the database, and generating the data model according to the spatial model and the model information; If the entity object is an element entity object, calling the element model from the database, and generating the data model according to the element model and the model information; If the entity object is an active entity object, an active model is called from the database, and the data model is generated according to the active model and the model information.

3. The method according to claim 1, characterized in that The entity nodes include organization entity nodes, role entity nodes, space entity nodes, element entity nodes, and activity entity nodes. The ID generation interface includes an organization ID generation interface, a role ID generation interface, a space ID generation interface, an element ID generation interface, and an activity ID generation interface. The calling of the ID generation interface according to the entity node corresponding to the entity object to generate the model ID and account ID corresponding to the data model includes: If the entity node corresponding to the entity object is the organization entity node, calling the organization ID generation interface to generate the model ID and the account ID corresponding to the data model; If the entity node corresponding to the entity object is the role entity node, calling the role ID generation interface to generate the model ID and the account ID corresponding to the data model; If the entity node corresponding to the entity object is the space entity node, calling the space ID generation interface to generate the model ID and the account ID corresponding to the data model; If the entity node corresponding to the entity object is the element entity node, calling the element ID generation interface to generate the model ID and the account ID corresponding to the data model; If the entity node corresponding to the entity object is the active entity node, the active ID generation interface is called to generate the model ID and the account ID corresponding to the data model.

4. The method according to claim 3, characterized in that The organization ID generation interface includes an organization ID generation sub-interface. If the entity node corresponding to the entity object is the organization entity node, calling the organization ID generation interface to generate the model ID and the account ID corresponding to the data model includes: If the entity node corresponding to the entity object is the organization entity node, identifying the organization type of the organization entity node; Setting the organization type reference field in the organization ID generation sub-interface input parameter according to the organization type; The organization ID generation sub-interface is called according to the input parameters after setting to generate the model ID and the account ID corresponding to the data model.

5. The method according to claim 1, wherein The determining the node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID, and the main channel path table includes: Associating the entity object ID table corresponding to the model ID with the entity object account table corresponding to the account ID through the ID account association table; Associating the model ID in the entity object ID table with the data relationship table corresponding to the entity object, wherein the main channel path table stores the predecessor model ID and the successor model ID corresponding to the predecessor entity node and the successor entity node of the entity node in the main channel path table; The entity object ID table is associated with the entity node to obtain the node position relationship of the entity node in the main channel path table.

6. The method according to any one of claims 1 to 5, characterized in that All tables involved in the data model can be added, deleted, modified and queried.

7. The method according to any one of claims 1 to 5, characterized in that The entity node corresponds to a metadata table, the metadata table is divided into libraries according to a preset logic, and is classified according to organization, role, space, element and activity, and the data model is developed according to the preset logic.

8. A data model building device, applied to data model building, characterized in that: include: an acquisition and generation unit, configured to acquire an entity object selected by a user and model information set by the user, and generate a data model according to the entity object and the model information; Call generation, for calling an ID generation interface according to the entity node corresponding to the entity object to generate a model ID and an account ID corresponding to the data model; a determining unit, configured to determine a node position relationship of the entity node in the main channel path table according to the entity object ID table corresponding to the model ID, the entity object account table corresponding to the account ID, and the main channel path table; A mapping unit is used to map the node position relationship with the data model to complete the establishment of the data model.

9. A computer device, characterized in that: The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and when the computer program is executed by a processor, the computer program can implement the method according to any one of claims 1 to 7.

Images