A group-level entity data management method and device, electronic equipment and medium

Abstract

The application provides a group-level entity data management method and device, electronic equipment and medium, comprising: in response to a login request for a data management platform, displaying a data management page corresponding to the login user's authority; in response to a model creation operation of the login user on the data management page, creating an initial entity model; in response to a configuration operation for a management requirement item, configuring requirement information and associating with the initial entity model; in response to a configuration operation for a model design item, configuring target entity data in the initial entity model to obtain a target entity model. In this way, the tenant mode and the role segmentation authorization meet the entity data management requirements of various levels of institutions within the group; the requirement information is configured and associated with the entity model, so that the model development has a basis and the randomness of model development is avoided; the target entity model can be quickly generated through a simple configuration operation of the model design item, improving the design speed and shortening the design cycle.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, device, electronic device, and medium for managing group-level entity data. Background Art

[0002] The construction of entity objects and relationships is a key node in business scenarios such as data governance, data development, and data applications. Existing technologies primarily rely on manual table-based maintenance and management of entity data. However, this manual table-based design approach is inefficient, has poor data maintainability, and only supports the design of independent entity structures. Therefore, in the current context of large-scale model applications and group-level data asset management, it cannot meet the entity data management needs of group-type organizations. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a group-level entity data management method, device, electronic device and medium, which meets the entity data management needs of institutions at all levels within the group with tenant models and role segmentation authorization; configure demand information and associate it with the entity model so that model development has a basis to rely on and avoids the arbitrariness of model development; through simple configuration operations on model design items, the target entity model can be quickly generated, which can improve the design speed of the entity model and shorten the design cycle.

[0004] This embodiment of the present application provides a method for managing group-level entity data. Organizations at all levels within the group operate in a tenant mode, and each level of the organization is configured as a tenant with corresponding permissions. The management method is applied to a data management platform and includes:

[0005] In response to a login request to the data management platform, displaying a data management page corresponding to the permissions of the logged-in user; wherein the permissions of the logged-in user are determined by the role of the logged-in user and the organization to which the logged-in user belongs;

[0006] In response to a model creation operation by the logged-in user on the data management page, creating an initial entity model;

[0007] In response to a configuration operation of the logged-in user on a management requirement item in the data management page, configuring requirement information and associating the requirement information with the initial entity model; wherein the requirement information is used as a design basis for the logged-in user to design the initial entity model;

[0008] In response to the configuration operation of the logged-in user on the model design item in the data management page, the target entity data in the initial entity model is configured to obtain a target entity model.

[0009] Furthermore, the model design item includes an entity data generation method item; and in response to the logged-in user's configuration operation on the model design item in the data management page, configuring the target entity data in the initial entity model to obtain the target entity model includes:

[0010] In response to a first configuration operation on the generation method item, determining a generation method for the target entity data; wherein the generation method includes at least one of the following: generation based on historical entity data resources, generation based on standard data management specifications, and generation through batch entry;

[0011] Displaying a generation page corresponding to the generation method;

[0012] In response to a second configuration operation on the entity data item in the generated page, generating the target entity data;

[0013] The target entity data is imported into the initial entity model to generate the target entity model.

[0014] Furthermore, when the generating method includes generating based on historical entity data resources, and the historical entity data resources include entity modeling templates; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes:

[0015] In response to the second configuration operation, a target entity modeling template is selected from predefined historical entity modeling templates, and data to be modeled is imported;

[0016] The target entity modeling template is used to organize the data to be modeled to form the target entity data.

[0017] Furthermore, when the generation method includes generation based on historical entity data resources, and the historical entity data resources include data tables in a metadata resource library; generating the target entity data in response to the second configuration operation on the entity data item in the generation page includes:

[0018] In response to the second configuration operation, connecting to a target metadata repository and displaying each data table in the target metadata repository;

[0019] In response to a selection operation on each of the data tables, a target data table is selected from the data tables and imported to obtain the target entity data.

[0020] Furthermore, when the generating method includes generating based on historical entity data resources, and the historical entity data resources include script files; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes:

[0021] In response to the second configuration operation, selecting a target script file and determining a database type of the target script file;

[0022] Parsing the target script file according to the database type, and displaying the parsed entity data in separate items; wherein the entity data includes entity table data, entity field data, and entity relationship data;

[0023] In response to a selection operation on each item of entity data, the target entity data is selected from the each item of entity data.

[0024] Furthermore, when the generating method includes generating based on historical entity data resources, and the historical entity data resources include other entity models stored in an entity model library; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes:

[0025] In response to the second tenant configuration operation, a reference entity model is selected from other entity models stored in the entity model library, and the target entity data is filtered out from the entity data included in the reference entity model.

[0026] Furthermore, when the generating method includes generating based on a standard data management specification; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes:

[0027] In response to the second configuration operation, selecting a target standard data management specification from the standard data management specifications;

[0028] The target standard data management specification is referenced to generate standard entities and standard entity attribute field information included in the target entity data.

[0029] Furthermore, after obtaining the target entity model, the management method further includes:

[0030] In response to the conversion operation on the target entity model, determining the adaptation database type and content generation mode of the script file to be generated corresponding to the target entity model; the content generation mode includes an incremental mode and a full mode;

[0031] The target entity model is converted into an executable script file according to the adaptation database type and the content generation mode.

[0032] Furthermore, the management method further includes:

[0033] During the generation process of the target entity model, in response to a version creation operation of the logged-in user on the target entity model, different versions of the target entity model are saved;

[0034] The target entity models of different versions are compared and analyzed to determine difference analysis results between the target entity models of different versions.

[0035] The present application also provides a management device for group-level entity data. Organizations at all levels within the group operate in a tenant mode, and each organization at each level is configured as a tenant with corresponding permissions. The management device is applied to a data management platform and includes:

[0036] A login module, configured to respond to a login request to the data management platform and display a data management page corresponding to the permissions of the logged-in user; wherein the permissions of the logged-in user are determined by the role of the logged-in user and the organization to which the logged-in user belongs;

[0037] A creation module, configured to create an initial entity model in response to a model creation operation of the logged-in user on the data management page;

[0038] a first configuration module, configured to configure requirement information and associate the requirement information with the initial entity model in response to a configuration operation of the logged-in user on a management requirement item in the data management page; wherein the requirement information serves as a design basis for the logged-in user to design the initial entity model;

[0039] The second configuration module is configured to configure the target entity data in the initial entity model in response to the configuration operation of the logged-in user on the model design item in the data management page to obtain a target entity model.

[0040] An embodiment of the present application also provides an electronic device, comprising: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of a group-level entity data management method as described above are performed.

[0041] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the above-mentioned method for managing group-level entity data are executed.

[0042] The embodiments of the present application provide a group-level entity data management method, device, electronic device, and medium, which meet the entity data management needs of institutions at all levels within the group through tenant models and segmented authorization of roles; configure demand information and associate it with the entity model, so that model development has a basis to rely on and avoids arbitrary model development; and quickly generate the target entity model through simple configuration operations on model design items, which can improve the design speed of the entity model and shorten the design cycle.

[0043] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0045] Figure 1 A flowchart of a method for managing group-level entity data provided by an embodiment of the present application is shown;

[0046] Figure 2 A schematic diagram of a data management page provided in an embodiment of the present application is shown;

[0047] Figure 3 (a)-(c) shows a schematic diagram of a solid modeling template provided in an embodiment of the present application;

[0048] Figure 4 A schematic diagram of generating target entity data based on a metadata resource library provided by an embodiment of the present application is shown;

[0049] Figure 5 A schematic diagram of generating target entity data based on a script file provided in an embodiment of the present application is shown;

[0050] Figure 6 A schematic diagram of generating target entity data based on other entity models stored in an entity model library provided by an embodiment of the present application is shown;

[0051] Figure 7 A schematic diagram of generating target entity data based on a standard data management specification provided by an embodiment of the present application is shown;

[0052] Figure 8 A schematic diagram of the structure of a data management platform provided in an embodiment of the present application is shown;

[0053] Figure 9 A schematic diagram showing the structure of a device for managing group-level entity data provided by an embodiment of the present application is shown;

[0054] Figure 10 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for which protection is claimed, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work falls within the scope of protection of the present application.

[0056] Research has found that the construction of entity objects and relationships is a key node in business scenarios such as data governance, data development, and data application. Existing technologies primarily rely on manual maintenance and management of entity data using tables. For example, table headers for information such as objects, object attributes, and object relationships are typically manually defined, and then object attribute data and other data are maintained in conjunction with business entity data.

[0057] The existing manual table design method is inefficient, has poor data maintainability, and only supports independent entity structure design. Therefore, it cannot achieve full-process control and coordination of data governance, development, and application. It also cannot meet the needs of the entity data management model of group-type institutions in the context of current large-scale model applications and group-level data asset management.

[0058] Based on this, the embodiments of the present application provide a group-level entity data management method, device, electronic device and medium, which meets the entity data management needs of institutions at all levels within the group with tenant models and segmented authorization of roles; configures demand information and associates it with the entity model, so that model development has a basis to rely on and avoids the arbitrariness of model development; through simple configuration operations on model design items, the target entity model can be quickly generated, which can improve the design speed of the entity model and shorten the design cycle.

[0059] In specific implementation, the management method provided by the embodiment of the present application can be applied to a data management platform running in a server. Among them, in the data management platform, institutions at all levels within the group operate in a tenant mode, and institutions at all levels (such as subsidiaries at all levels within the group) are configured as tenants with corresponding permissions, and each tenant may include multiple users. In tenant mode, the business logic of institutions at all levels within the group is isolated in a tenant manner to meet the requirements of group structure management and control. The application permissions of each tenant can be pre-defined by the administrator. For example, when configuring tenants, it is necessary to define the corresponding application permissions of the tenants, allocate the relevant function menus for each tenant, allocate the data sources that each tenant can use, and the tenant administrators of each tenant, etc., so as to realize the control of the tenant's functions, data, etc.

[0060] In this way, the management and maintenance of entity data are handled within each tenant, and the data between tenants is logically isolated, meeting the group-level entity structure management requirements of unified tool deployment and operation and maintenance, unified data storage, independent authorization and control, and independent management of entity modeling businesses.

[0061] In addition, to further refine and differentiate the management of user permissions within the group and avoid the tediousness of authorizing users one by one, users also have one or more roles. By authorizing roles, entity data operation permissions can be managed and controlled. For example, different roles can have operation permissions for different entity models, such as invisible, read-only, and edit. Therefore, users have corresponding operation permissions based on their roles.

[0062] See also Figure 1 , Figure 1 This is a flow chart of a group-level entity data management method provided in an embodiment of the present application. Figure 1 As shown in , the management method provided by the embodiment of the present application includes:

[0063] S101 . In response to a login request to the data management platform, display a data management page corresponding to the authority of the logged-in user.

[0064] In this step, the user sends a login request to the data management platform. The login request may include the user's login information (such as account number and password). The data management platform verifies the login information contained in the login request, determines the role and organization of the logged-in user, and then determines the logged-in user's permissions. It controls the permissions of the logged-in user and displays the data management page corresponding to their permissions. The data management page provides users with a variety of data management functions, such as business data tracking and entity data management. For entity data management, the data management page is equipped with controls corresponding to entity data management functions. By operating the controls, users can manage group-level entity data. For entity data management functions that the user does not have permissions for, the corresponding controls can be hidden on the page or rendered inoperable.

[0065] S102: In response to the logged-in user's model creation operation on the data management page, create an initial entity model.

[0066] See also Figure 2 , Figure 2 This is a schematic diagram of a data management page provided in an embodiment of the present application. Figure 2 As shown in , for the entity data management function, the data management page displays a model directory of the entity model. In step S102, the user can view the model directory where the entity model is stored in the entity model library and create a new initial entity model through a model creation operation under the model directory by operating the corresponding control in the data management page.

[0067] The directory structure of the model directory is predefined according to the management plan of the entity data, such as system classification, data warehouse layering and other different management plan definitions, to form a directory management system. More specifically, the directory structure is a multi-level storage structure, and the last level of the directory is used to add entity model information. Figure 2 As shown in , there are multiple levels of subdirectories under the root directory of the model directory, and the entity models abc, etc. are stored in the last level directory. The logged-in user defines the basic information of the entity model through the model creation operation, such as the storage level of the entity model in the directory structure, directory code, directory type, directory name, model name of the entity model, status, corresponding database type and operation permission data, etc., and creates the initial entity model through the model configuration operation that defines this series of information. At the same time, it is also possible to provide the entity model with role operation permissions (such as invisible, read-only, edit, etc.) for the model, and provide the association of the demand information based on the model design. It should be noted that the initial entity model created here is generally an empty entity model that does not include entity data. The user can add entity data under the initial entity model through the configuration operations in the subsequent steps according to the needs, and finally obtain the target entity model.

[0068] S103: In response to the logged-in user's configuration operation on the management requirement item in the data management page, configure requirement information and associate the requirement information with the initial entity model.

[0069] In this step, the logged-in user can configure the requirements section on the data management page. These configurations allow users to configure requirement information, such as the requirement code, title, details, urgency, submitter, and submission time. They can also upload requirement files. During configuration, users can review the newly added requirement information to ensure its validity as a modeling basis. If approved, the requirement information can be associated with the initial entity model based on the user's configuration. This allows other users, including the logged-in user, to directly access the requirement information from the data management platform when editing the associated initial entity model. In response to the user's access operation, the requirement information is displayed on the data management page when designing the initial entity model. This serves as a basis for user design (including new creation and modification operations), providing a reliable basis for model development and preventing arbitrariness. Furthermore, approved requirement information can be invalidated or refined. Invalidated requirement information cannot be reused, ensuring flexibility in requirement changes.

[0070] S104 : In response to the configuration operation of the logged-in user on the model design item in the data management page, the target entity data in the initial entity model is configured to obtain a target entity model.

[0071] The data management page of the data management platform offers a wide variety of model design options. Logged-in users can quickly retrieve desired target entity data from the massive amount of group-level entity data through simple configuration operations such as selection and input, importing it into the initial entity model and ultimately constructing the target entity model. This can speed up entity model design and shorten the design cycle. The following details the entity model design process using specific examples.

[0072] After the initial entity model is created in step S102, the user triggers the control corresponding to the initial entity model on the data management page, and the data management page can display various model design items corresponding to the initial entity model. In one possible embodiment, the model design items include the generation method of the entity data in the model; then step S104 may include:

[0073] S1041: In response to a first configuration operation on the generation method item, determine a generation method for target entity data.

[0074] In this step, the generation method option is displayed as a drop-down box control on the data management page. By triggering the drop-down box control and selecting the first configuration operation for the generation method from the displayed drop-down box, the user can determine the generation method for the target entity data. These generation methods include at least one of the following: generation based on historical entity data resources, generation based on standard data management specifications, and generation via batch entry. During the model design process, multiple generation methods can be used individually or in combination to achieve flexible design and rapid generation of entity models.

[0075] S1042: Display a generation page corresponding to the generation method.

[0076] In this step, since the content that users need to configure is different when generating entity data in different generation methods, the configurable entity data items displayed on the page are also not exactly the same. It is necessary to display the generation page corresponding to the generation method to guide users to configure the entity data step by step through the entity data items.

[0077] S1043: In response to a second configuration operation on the entity data item in the generated page, generate the target entity data.

[0078] Here, at least one entity data item is set in the generation page. Through simple configuration operations on the entity data item, the user can be guided to quickly configure the required target entity data.

[0079] S1044: Import the target entity data into the initial entity model to obtain the target entity model.

[0080] In this step, the configured target entity data is imported into the initial entity model to ultimately generate a structured target entity model.

[0081] The following specifically describes the implementation of generating the target entity data in response to the second configuration operation on the entity data item in the generation page in step S1043.

[0082] For generation based on historical entity data resources, the entity data items on the generation page include historical entity data resource items. Users can configure these items to select historical entity data resources for generating target entity data. Specifically, historical entity data resources include at least one of the following: entity modeling templates, data tables in the metadata repository, script files, and other entity models stored in the entity model repository.

[0083] In a specific implementation, when the generation manner comprises generation based on a historical entity data resource, and the historical entity data resource comprises an entity modeling template, the entity data item can further comprise an entity modeling template item and a data-to-be-modeled item; and step S1043 can comprise:

[0084] In response to the second configuration operation, a target entity modeling template is selected from the pre-defined historical entity modeling templates, and data-to-be-modeled is imported; the data-to-be-modeled is arranged using the target entity modeling template, to form the target entity data.

[0085] Here, the historical entity resource comprises a plurality of historical entity modeling templates pre-defined according to entity structure, entity relationship and other information. The user selects a target entity modeling template from the historical entity modeling templates selectable under the entity modeling template item through a second configuration operation, and imports data-to-be-modeled which needs to be subjected to entity modeling. Then, the data-to-be-modeled is arranged using the target entity modeling template, to arrange the target entity data therefrom. In this way, compared with the prior art in which the user fills in a form manually according to the data-to-be-modeled, which can result in a generated form that is not standardized and cannot be recognized, the standard entity modeling template pre-defined can automatically extract entity data from the data-to-be-modeled according to the user's demand, thereby improving the generation efficiency of the entity model.

[0086] Please refer to FIG. 3(a), FIG. 3(b) and FIG. 3(c), which are schematic diagrams of an entity modeling template provided by an embodiment of the present application. FIG. 3(a) is an entity field information template, FIG. 3(b) is an entity relationship information template, and FIG. 3(c) is a corresponding association field template in an entity relationship. As shown in FIG. 3(a)-(c), the entity modeling template (EXCEL template) is pre-defined according to entity structure information, relationship information and other entity data; in this way, in the management of entity data, a target entity modeling template and data-to-be-modeled can be selected and imported according to a configuration operation, and the design goal of quickly restoring the model structure of entities and entity relationships is achieved through the imported manner.

[0087] Alternatively, when the historical entity data resource comprises a data table in a metadata resource library, the entity data item can further comprise a metadata resource library item and a data table item; and step S1043 can comprise:

[0088] In response to the second configuration operation, a target metadata resource library is connected and each data table in the target metadata resource library is displayed; in response to a selection operation on the each data table, a target data table is selected from the each data table and imported, to obtain the target entity data.

[0089] Here, the user can select a target metadata resource library through a configuration metadata resource library item, and connect the target metadata resource library, to display each data table in the target metadata resource library under the data table item. Please refer toFigure 4 , Figure 4 This is a schematic diagram of generating target entity data based on a metadata resource library provided by an embodiment of the present application. Figure 4 As shown, a metadata repository stores multiple data tables, forming a structured list of data tables. The user's second configuration operation connects to the target metadata repository and displays the data tables stored therein. The user then selects the target data table to import from each data table by selecting the data table item. After confirmation, the import operation is performed to obtain the target entity data. This allows the design goal of rapidly restoring the model structure of entities and entity relationships by importing data tables from the metadata repository.

[0090] Alternatively, when the historical entity data resource includes a script file, the entity data item may further include a script file item, a database type item of the script file, and an entity data item; step S1043 may include:

[0091] In response to the second configuration operation, a target script file is selected and a database type of the target script file is determined; the target script file is parsed according to the database type, and the entity data obtained by the parsing is displayed item by item; wherein the entity data includes entity table data, entity field data and entity relationship data; in response to a selection operation for each item of entity data, the target entity data is selected from the each item of entity data.

[0092] Here, the user can select the target script file by configuring the script file item, and determine the database type of the target script file by configuring the database type item of the script file, so as to reversely parse the executable script file that adapts to the database type into entity data; then the parsed entity data is displayed according to type, such as entity table data, entity field data and entity relationship data; the user can select from the displayed entity data to obtain the target entity data.

[0093] See also Figure 5 , Figure 5 This is a schematic diagram of generating target entity data based on a script file provided in an embodiment of the present application. Figure 5As shown, according to the user's second configuration operation, the target script file (the format can be text types such as sql, txt, etc.) can be selected for upload and parsing. The user can manually enter or automatically identify the database type of the target script file; the target script file is reversely parsed according to the database type, and the entity data obtained by parsing is displayed item by item, such as entity table data, entity field data and entity relationship data, for the user to analyze and judge and choose to use; thereafter, according to the logged-in user's selection operation for each entity data, the target entity data is selected from the displayed entity data to generate a target entity model based on the target entity data. The design goal of quickly restoring the model structure of entities and entity relationships can also be achieved by importing.

[0094] Alternatively, when the historical entity data resource includes other entity models stored in an entity model library, the entity data item may further include an entity model item; step S1043 may include:

[0095] In response to the second tenant configuration operation, a reference entity model is selected from other entity models stored in the entity model library, and the target entity data is filtered out from the entity data included in the reference entity model.

[0096] Here, the data management platform is provided with an entity model library. Entity models generated by the data management platform can be stored in the entity model library for subsequent use. By configuring entity model items, users can select a reference entity model from other entity models stored in the entity model library and select the target entity data from the entity data included in the referenced entity model.

[0097] See also Figure 6 , Figure 6 This is a schematic diagram of generating target entity data based on other entity models stored in the entity model library provided by the embodiment of the present application. Figure 6 As shown, logged-in users can configure and select an entity model from other entity models stored in the model library. They can then filter the target entity from the entities included in the selected entity model and copy and import it to form a target entity model based on the target entity. This generation method is based on the concepts of data sharing and unified storage. When building a new entity model, if there is a need to reference entity information from other existing entity models in the data management platform, entities from other entity models in the entity model library can be selected and imported and copied. The structure can then be optimized and adjusted according to business requirements, which can also achieve the goal of quickly building a model structure for entities and entity relationships.

[0098] When the generating method includes generating based on a standard data management specification, the entity data item may further include a standard data management specification item; step S1043 may include:

[0099] In response to the second configuration operation, a target standard data management specification is selected from the standard data management specifications; the target standard data management specification is referenced to generate standard entities and standard entity attribute field information included in the target entity data.

[0100] The degree of standardization of entity models directly reflects the quality of model design, as well as the complexity and investment in subsequent data governance. For example, standard data management specifications can include data standards such as industry codes and account status. Therefore, when designing entity models, ensuring that basic data standards are adhered to through the configuration of model design items can improve model standardization, reduce subsequent data governance investment, increase data availability, and maximize data value.

[0101] See also Figure 7 , Figure 7 This is a schematic diagram of generating target entity data based on standard data management specifications provided in an embodiment of the present application. Figure 7 As shown, according to the tenant's configuration operation, the target standard data management specification can be selected from multiple standard data management specifications and referenced in batches, so as to obtain the entity attribute fields and other information of the standard entity as the target entity data, so as to quickly build a more standard target entity model.

[0102] In addition, the embodiment of the present application also provides a batch entry generation method. By batch adding entity table information and entity table field information, etc., even if there are currently no available historical entity data resources and standard data management specifications, the goal of quickly building an entity model can still be achieved through batch operations, thereby improving the efficiency and speed of model design.

[0103] Furthermore, after obtaining the target entity model in step S104, the management method further includes:

[0104] In response to the conversion operation on the target entity model, the adaptation database type and content generation mode of the script file to be generated corresponding to the target entity model are determined; the content generation mode includes an incremental mode and a full mode; according to the adaptation database type and the content generation mode, the target entity model is converted into an executable script file.

[0105] After completing the data structure design of the entity model, the embodiment of the present application can convert the design results into executable scripts that are adapted to different types of databases according to the user's conversion operations, so as to meet the application scenario requirements of free selection of library types, support for incremental / full mode of generation, and real-time script generation.

[0106] Furthermore, the management method further includes:

[0107] During the generation process of the target entity model, in response to the logged-in user's operation of creating a version of the target entity model, different versions of the target entity model are saved; and the different versions of the target entity models are compared and analyzed to determine the difference analysis results between the different versions of the target entity models.

[0108] Here, by saving different versions of data at different nodes during the generation process of the entity model, historical version data can be generated to provide data resource support for the analysis of the entity model's change process and the tracing of business evolution; when saving different versions of the target entity model, the full save method can be used to facilitate the comparison of different versions of the target entity model and display the difference analysis results between different versions.

[0109] Furthermore, the management method also includes: visually displaying the target entity model in an ER diagram mode to achieve a comprehensive browsing of the entity structure; another mode is to display the target entity model in a list format, displaying the entity table list, entity attribute list, etc. through the list, and at the same time, keyword search queries can be performed to assist in filtering and screening the entity structure.

[0110] The present invention provides a method for managing group-level entity data, which has the following beneficial effects:

[0111] (1) The entity data management needs of institutions at all levels within the group are met by using tenant models and role-based segmented authorization. The tenant functional authority segmented authorization enables multiple levels of units to share a set of tools and achieve the effect of unified data storage and logical isolation.

[0112] (2) Configure the demand information and associate it with the initial entity model in the development process, so that the entire process of model development has a basis to rely on and avoid the arbitrariness and uncontrollability of model development.

[0113] (3) The target entity model can be quickly generated by simply configuring the model design items, which can improve the design speed of the entity model and shorten the design cycle. Among them, the target entity data can be quickly generated through a variety of generation methods such as generation based on historical entity data resources, generation based on standard data management specifications, and generation through batch input. The target entity model can then be quickly generated by importing the target entity data into the initial entity model. The generation method based on standard data management specifications can implement standards in the entity model design process, solve the problem of standardization failure of the entity model, improve the standardization of the data structure, and reduce the investment in data governance in the later stage.

[0114] (4) In the physicalization stage of the structure, the script files are adapted to different types of databases, and the conversion from the logical structure definition of the business entity to the physical structure stored procedure is realized; in the two stages of logical and physical structure design, the default method is to automatically synchronize, reducing the problem of differential synchronization processing in the two stages.

[0115] (5) During the generation of the target entity model, the status of the structural design results at a certain historical point is retained through versions to achieve the goal of recording the entire design process; data storage records are performed separately to achieve the retention of historical data at each stage, providing original data resources for tracking the structural change process.

[0116] See also Figure 8 , Figure 8 A schematic diagram of the structure of a data management platform provided in an embodiment of the present application.

[0117] like Figure 7 As shown, in terms of tenant management: subsidiaries at all levels in the group are configured as tenants A, B, C, ... with corresponding application permissions.

[0118] In terms of standardized modeling, the data management platform supports naming rule management, root management, and standard management. The above management rules will be checked during the model design process to ensure the standardization of modeling.

[0119] In terms of model design: First, through catalog management, requirement association and model role authorization, the initial entity model is defined and associated with different subject domains, such as financial topics and personnel topics in the organization; the entity model hierarchy includes conceptual layer model, logical layer model and physical layer model; secondly, the data management platform provides multiple generation methods for rapid model design based on existing model resources, such as metadata import, DDL script parsing, model library import, ERWin file parsing, EXCEL templates and standard-based modeling; the logical layer model and the physical layer model can be automatically synchronized, that is, when the logical layer entity model is modified, the physical layer entity model is automatically modified accordingly; at the same time, the data management platform also provides functions such as converting ER diagrams / lists, batch adding tables, field reset, operation logs, adding tables / fields, find / replace, copying tables and custom properties; among them, when the modified data involves multiple tables, the data management platform also provides cascading synchronization functions for multiple tables with corresponding data to improve the convenience of entity model editing. Thirdly, when exporting, it supports generating scripts and exporting them to different types of databases. You can also store entity models in entity model libraries and export them to different types of databases, or export them as dictionaries or public interfaces, or export them to data development platforms to achieve multi-platform interoperability.

[0120] In terms of model management: it provides requirements management, version management, and backup and restore functions.

[0121] In terms of analytical applications: it provides workbench, model query, ER diagram browsing and version comparison functions.

[0122] See also Figure 9 , Figure 9 This is a schematic diagram of the structure of a group-level entity data management device provided in an embodiment of the present application. Figure 9 As shown in FIG, each level of the organization in the group operates in a tenant mode, and each level of the organization is configured as a tenant with corresponding permissions; the management device 800 includes:

[0123] Login module 810, for responding to a login request to the data management platform and displaying a data management page corresponding to the permissions of the logged-in user; wherein the permissions of the logged-in user are determined by the role of the logged-in user and the organization to which the logged-in user belongs;

[0124] A creation module 820 is configured to create an initial entity model in response to a model creation operation performed by the logged-in user on the data management page;

[0125] A first configuration module 830 is configured to configure requirement information and associate the requirement information with the initial entity model in response to a configuration operation of the logged-in user on a management requirement item in the data management page; wherein the requirement information serves as a design basis for the logged-in user to design the initial entity model;

[0126] The second configuration module 840 is configured to configure the target entity data in the initial entity model in response to the configuration operation of the logged-in user on the model design item in the data management page to obtain a target entity model.

[0127] Furthermore, the model design item includes an entity data generation method item; when the second configuration module 840 is used to configure the target entity data in the initial entity model in response to the logged-in user's configuration operation on the model design item in the data management page to obtain the target entity model, the second configuration module 840 is used to:

[0128] In response to a first configuration operation on the generation method item, determining a generation method for the target entity data; wherein the generation method includes at least one of the following: generation based on historical entity data resources, generation based on standard data management specifications, and generation through batch entry;

[0129] Displaying a generation page corresponding to the generation method;

[0130] In response to a second configuration operation on the entity data item in the generated page, generating the target entity data;

[0131] The target entity data is imported into the initial entity model to generate the target entity model.

[0132] Furthermore, when the generation method includes generation based on historical entity data resources, and the historical entity data resources include entity modeling templates; when the second configuration module 840 is used to generate the target entity data in response to the second configuration operation on the entity data item in the generation page, the second configuration module 840 is used to:

[0133] In response to the second configuration operation, a target entity modeling template is selected from predefined historical entity modeling templates, and data to be modeled is imported;

[0134] The target entity modeling template is used to organize the data to be modeled to form the target entity data.

[0135] Furthermore, when the generation method includes generation based on historical entity data resources, and the historical entity data resources include a data table in a metadata resource library; when the second configuration module 840 is used to generate the target entity data in response to the second configuration operation on the entity data item in the generation page, the second configuration module 840 is used to:

[0136] In response to the second configuration operation, connecting to a target metadata repository and displaying each data table in the target metadata repository;

[0137] In response to a selection operation on each of the data tables, a target data table is selected from the data tables and imported to obtain the target entity data.

[0138] Furthermore, when the generation method includes generation based on historical entity data resources, and the historical entity data resources include script files; when the second configuration module 840 is used to generate the target entity data in response to the second configuration operation on the entity data item in the generation page, the second configuration module 840 is used to:

[0139] In response to the second configuration operation, selecting a target script file and determining a database type of the target script file;

[0140] Parsing the target script file according to the database type, and displaying the parsed entity data in separate items; wherein the entity data includes entity table data, entity field data, and entity relationship data;

[0141] In response to a selection operation on each item of entity data, the target entity data is selected from the each item of entity data.

[0142] Furthermore, when the generation method includes generation based on historical entity data resources, and the historical entity data resources include other entity models stored in an entity model library; when the second configuration module 840 is used to generate the target entity data in response to the second configuration operation on the entity data item in the generation page, the second configuration module 840 is used to:

[0143] In response to the second tenant configuration operation, a reference entity model is selected from other entity models stored in the entity model library, and the target entity data is filtered out from the entity data included in the reference entity model.

[0144] Furthermore, when the generating method includes generating based on a standard data management specification; when the second configuration module 840 is used to generate the target entity data in response to the second configuration operation on the entity data item in the generating page, the second configuration module 840 is used to:

[0145] In response to the second configuration operation, selecting a target standard data management specification from the standard data management specifications;

[0146] The target standard data management specification is referenced to generate standard entities and standard entity attribute field information included in the target entity data.

[0147] Furthermore, the management device 800 further includes a conversion module; the conversion module is configured to:

[0148] In response to the conversion operation on the target entity model, determining the adaptation database type and content generation mode of the script file to be generated corresponding to the target entity model; the content generation mode includes an incremental mode and a full mode;

[0149] The target entity model is converted into an executable script file according to the adaptation database type and the content generation mode.

[0150] Furthermore, the management device 800 further includes a storage module; the storage module is configured to:

[0151] During the generation process of the target entity model, in response to a version creation operation of the logged-in user on the target entity model, different versions of the target entity model are saved;

[0152] The target entity models of different versions are compared and analyzed to determine difference analysis results between the target entity models of different versions.

[0153] See also Figure 10 , Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.Figure 10 As shown in FIG, the electronic device 900 includes a processor 910 , a memory 920 and a bus 930 .

[0154] The memory 920 stores machine-readable instructions executable by the processor 910. When the electronic device 900 is running, the processor 910 communicates with the memory 920 via the bus 930. When the machine-readable instructions are executed by the processor 910, the above-mentioned Figure 1 The steps of a method for managing group-level entity data in the method embodiment shown are described in detail. The specific implementation method can be found in the method embodiment and will not be repeated here.

[0155] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 The steps of a method for managing group-level entity data in the method embodiment shown are described in detail. The specific implementation method can be found in the method embodiment and will not be repeated here.

[0156] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0157] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. There may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some communication interface, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

[0158] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0159] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0160] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0161] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The scope of protection of the present application is not limited thereto. Although the present application has been described in detail with reference to the above-mentioned embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-mentioned embodiments within the technical scope disclosed in the present application, or perform equivalent replacements for some of the technical features thereof. These modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for managing group-level entity data, characterized in that: Each level of organization in the group operates in a tenant mode, and each level of organization is configured as a tenant with corresponding permissions; The management method is applied to a data management platform, and the management method includes: In response to a login request to the data management platform, displaying a data management page corresponding to the permissions of the logged-in user; wherein the permissions of the logged-in user are determined by the role of the logged-in user and the organization to which the logged-in user belongs; In response to the logged-in user's model creation operation on the data management page, creating an initial entity model by defining basic information of the entity model; In response to a configuration operation of the logged-in user on a management requirement item in the data management page, configuring requirement information and associating the requirement information with the initial entity model; wherein the requirement information is used as a design basis for the logged-in user to design the initial entity model; In response to a configuration operation of the logged-in user on a model design item in the data management page, configuring target entity data and importing the target entity data into the initial entity model to obtain a target entity model; The management method further comprises: When the user edits the initial entity model associated with the demand information, in response to the user's acquisition operation, the demand information is displayed on the data management page; After obtaining the target entity model, the management method further includes: In response to the conversion operation on the target entity model, determining the adaptation database type and content generation mode of the script file to be generated corresponding to the target entity model; the content generation mode includes an incremental mode and a full mode; The target entity model is converted into an executable script file according to the adaptation database type and the content generation mode.

2. The management method according to claim 1, characterized in that: The model design item includes an entity data generation method item; in response to the logged-in user's configuration operation on the model design item in the data management page, configuring target entity data and importing the target entity data into the initial entity model to obtain the target entity model, including: In response to a first configuration operation on the generation method item, determining a generation method for the target entity data; wherein the generation method includes at least one of the following: generation based on historical entity data resources, generation based on standard data management specifications, and generation through batch entry; Displaying a generation page corresponding to the generation method; In response to a second configuration operation on the entity data item in the generated page, generating the target entity data; The target entity data is imported into the initial entity model to generate the target entity model.

3. The management method according to claim 2, characterized in that: When the generating method includes generating based on historical entity data resources, and the historical entity data resources include entity modeling templates; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes: In response to the second configuration operation, a target entity modeling template is selected from predefined historical entity modeling templates, and data to be modeled is imported; The target entity modeling template is used to organize the data to be modeled to form the target entity data.

4. The management method according to claim 2, characterized in that: When the generating method includes generating based on historical entity data resources, and the historical entity data resources include data tables in a metadata resource library; The generating the target entity data in response to the second configuration operation on the entity data item in the generated page includes: In response to the second configuration operation, connecting to a target metadata repository and displaying each data table in the target metadata repository; In response to a selection operation on each of the data tables, a target data table is selected from the data tables and imported to obtain the target entity data.

5. The management method according to claim 2, characterized in that: When the generating method includes generating based on historical entity data resources, and the historical entity data resources include script files; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes: In response to the second configuration operation, selecting a target script file and determining a database type of the target script file; Parsing the target script file according to the database type, and displaying the parsed entity data in separate items; wherein the entity data includes entity table data, entity field data, and entity relationship data; In response to a selection operation on each item of entity data, the target entity data is selected from the each item of entity data.

6. The management method according to claim 2, characterized in that: When the generating method includes generating based on historical entity data resources, and the historical entity data resources include other entity models stored in an entity model library; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes: In response to the second tenant configuration operation, a reference entity model is selected from other entity models stored in the entity model library, and the target entity data is filtered out from the entity data included in the reference entity model.

7. The management method according to claim 2, characterized in that: When the generating method includes generating based on a standard data management specification; generating the target entity data in response to the second configuration operation on the entity data item in the generating page includes: In response to the second configuration operation, selecting a target standard data management specification from the standard data management specifications; The target standard data management specification is referenced to generate standard entities and standard entity attribute field information included in the target entity data.

8. The management method according to claim 1, characterized in that: The management method further comprises: During the generation process of the target entity model, in response to a version creation operation of the logged-in user on the target entity model, different versions of the target entity model are saved; The target entity models of different versions are compared and analyzed to determine difference analysis results between the target entity models of different versions.

9. A management device for group-level entity data, characterized in that: Each level of organization in the group operates in a tenant mode, and each level of organization is configured as a tenant with corresponding permissions; The management device is applied to the data management platform, and the management device includes: A login module, configured to respond to a login request to the data management platform and display a data management page corresponding to the permissions of the logged-in user; wherein the permissions of the logged-in user are determined by the role of the logged-in user and the organization to which the logged-in user belongs; A creation module, configured to create an initial entity model by defining basic information of the entity model in response to the model creation operation of the logged-in user on the data management page; a first configuration module, configured to configure requirement information and associate the requirement information with the initial entity model in response to a configuration operation of the logged-in user on a management requirement item in the data management page; wherein the requirement information serves as a design basis for the logged-in user to design the initial entity model; a second configuration module, configured to, in response to a configuration operation of the logged-in user on a model design item in the data management page, configure target entity data and import the target entity data into the initial entity model to obtain a target entity model; The management device further includes: a display module configured to display the demand information on the data management page in response to an acquisition operation of the user when the user edits the initial entity model associated with the demand information; The management device further includes a conversion module; the conversion module is configured to: In response to the conversion operation on the target entity model, determining the adaptation database type and content generation mode of the script file to be generated corresponding to the target entity model; the content generation mode includes an incremental mode and a full mode; The target entity model is converted into an executable script file according to the adaptation database type and the content generation mode.

Images