CN114048194A - Data management method and device and electronic equipment - Google Patents
Data management method and device and electronic equipment Download PDFInfo
- Publication number
- CN114048194A CN114048194A CN202210029591.XA CN202210029591A CN114048194A CN 114048194 A CN114048194 A CN 114048194A CN 202210029591 A CN202210029591 A CN 202210029591A CN 114048194 A CN114048194 A CN 114048194A
- Authority
- CN
- China
- Prior art keywords
- data model
- data
- managed
- field
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2291—User-Defined Types; Storage management thereof
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a data management method, a device and electronic equipment, the data management method only needs a user to create a data model to be managed in a dynamic data model configuration interface of a data weaving system and configure basic information and field information of the data model to be managed, the data weaving system can store the basic information and the field information of the data model to be managed in a global library and automatically create a data model instance table in a tenant library corresponding to the user, and then data is added in the data model instance table for data management in a manual creation or data import mode, the workload of data management is greatly simplified, service code development of data management is not needed, technical requirements on technicians are reduced, the information of the data model to be managed in the dynamic data model configuration interface is configured in a self-defining way, the flexibility is good.
Description
Technical Field
The present invention relates to the technical field of data management, and in particular, to a method and an apparatus for managing data, and an electronic device.
Background
With the continuous development of enterprises, various data needing to be managed and maintained, such as data of equipment models, product data, enterprise data and the like, can be continuously generated in the development process, and meanwhile, different organizations or sub-companies in the enterprises can have different management requirements on the same assets, so that the enterprise IT system needs to support the diversity and flexibility of the data, and the traditional IT system implementation mode cannot meet the market development of the enterprises for coping with the immense change.
The traditional method for managing data by an IT system (such as ERP) is to design enterprise data into a relational table structure, distinguish data of different departments of business in the relational table structure through simple fields, and then develop business codes for data management. For example, for management of excavator data, the a department needs to design a relational table structure (including data fields that the a department needs to manage), and then the a department develops service codes for data management; the B department also needs to design another relational table structure (including the data fields that the B department needs to manage), and then the B department develops the service code for data management. That is to say, enterprise data management needs repeated database model design (namely, relational table structure design) and development work, the workload is large, customized development needs to be carried out again according to the steps for newly proposed dynamic data resource management requirements of enterprises, and the flexibility is poor.
In summary, the existing data management method has the technical problems of large workload, high technical requirement threshold for technical personnel and poor flexibility.
Disclosure of Invention
In view of this, the present invention provides a data management method, a data management apparatus, and an electronic device, so as to alleviate the technical problems of the existing data management method, such as large workload, high technical requirement threshold for technicians, and poor flexibility.
In a first aspect, an embodiment of the present invention provides a data management method, which is applied to a data weaving system, and the method includes:
acquiring a data model to be managed, which is created in a dynamic data model configuration interface by a user of a target tenant, and configured basic information of the data model to be managed, wherein the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model;
storing the basic information of the data model to be managed to a global library, and creating an empty table with a table name in a tenant library to which the target tenant belongs according to the basic information of the data model to be managed;
acquiring field information of the data model to be managed, which is configured in the dynamic data model configuration interface by the user, wherein the dynamic data model configuration interface further comprises an area for configuring the field information of the data model;
storing the field information of the data model to be managed to the global library, and converting the empty table into a data model instance table according to the field information of the data model to be managed;
and adding data in the data model instance table by means of manual creation or data import.
Further, the region for configuring the field information of the data model includes: the method comprises the following steps that a plurality of optional field types, configurable field verification rules and field output configurations are adopted, and other data models can be used as fields of the data model to be managed to acquire field information of the data model to be managed configured in the dynamic data model configuration interface by the user, and the method comprises the following steps:
acquiring a first field added by the user;
if the first field is not a primary key field, prompting the user to add the primary key field, and configuring the primary key field, wherein the configuration comprises at least one of the following: configuring a field type and a field checking rule;
and after the configuration of the primary key field is completed, acquiring other field information added and configured by the user.
Further, adding data in the data model instance table by means of manual creation includes:
loading field information of a to-be-managed data model of the target tenant in the global library according to the manual creation mode selected by the user;
generating a field data form according to the field information of the data model to be managed;
acquiring data filled in the field data form by the user, and verifying the data according to a preset corresponding field verification rule;
if the verification is passed, storing the data into the data model instance table;
and if the verification fails, returning prompt information.
Further, adding data in the data model instance table in a data import manner includes:
generating a form template according to the data import mode selected by the user and the field information of the data model to be managed of the target tenant in the global library;
and acquiring batch data filled in the form template by the user, and importing the batch data in the form template into the data model instance table, wherein in the importing process, if the batch data does not pass the verification of the corresponding field verification rule configured in advance, an error prompt message is returned, and if the batch data passes the verification of the corresponding field verification rule configured in advance, the batch data is stored in the data model instance table.
Further, the method further comprises:
acquiring basic information of a data model to be managed and field information of the data model to be managed, which are modified in the dynamic data model configuration interface by the user;
and updating the corresponding basic information and field information in the global library according to the basic information of the data model to be managed modified by the user and the field information of the data model to be managed.
Further, the method further comprises:
acquiring a request for deleting the target data model triggered by the user;
determining whether the target data model has been used based on the request;
if the target data model is used, prompting that the target data model is not allowed to be deleted;
and if the target data model is not used, deleting the basic information of the target data model and the field information of the target data model in the global library, and deleting a data model instance table of the target data model in a tenant library corresponding to the target data model.
Further, the method further comprises:
acquiring a request for deleting a target field of a target data model triggered by the user;
judging whether a target field of the target data model has data or not based on the request;
if the data exists, prompting that the target field of the target data model is not allowed to be deleted;
and if no data exists, deleting field information of a target field of the target data model in the global library, and modifying a data model instance table structure of the target data model in a tenant library corresponding to the target data model.
In a second aspect, an embodiment of the present invention further provides a data management apparatus, which is applied to a data weaving system, and the apparatus includes:
the data model management system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a data model to be managed and configured basic information of the data model to be managed, which are created in a dynamic data model configuration interface by a user of a target tenant, and the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model;
the first storage unit is used for storing the basic information of the data model to be managed to a global library and creating an empty table with a table name in a tenant library to which the target tenant belongs according to the basic information of the data model to be managed;
a second obtaining unit, configured to obtain field information of the data model to be managed, configured in the dynamic data model configuration interface by the user, where the dynamic data model configuration interface further includes an area for configuring the field information of the data model;
the second storage unit is used for storing the field information of the data model to be managed to the global library and converting the empty table into a data model instance table according to the field information of the data model to be managed;
and the data adding unit is used for adding data in the data model instance table in a manual creation or data import mode.
In a third aspect, an embodiment of the present invention further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method according to any one of the above first aspects when executing the computer program.
In a fourth aspect, embodiments of the present invention also provide a computer-readable storage medium storing machine executable instructions, which when invoked and executed by a processor, cause the processor to perform the method of any of the first aspect.
In an embodiment of the present invention, a data management method is provided, which is applied to a data weaving system, and includes: acquiring a data model to be managed created in a dynamic data model configuration interface by a user of a target tenant and basic information of the configured data model to be managed, wherein the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model; storing the basic information of the data model to be managed to a global library, and creating an empty table with a table name in a tenant library to which a target tenant belongs according to the basic information of the data model to be managed; acquiring field information of a data model to be managed, which is configured in a dynamic data model configuration interface by a user, wherein the dynamic data model configuration interface also comprises an area for configuring the field information of the data model; storing the field information of the data model to be managed to a global library, and converting an empty table into a data model instance table according to the field information of the data model to be managed; and adding data in the data model instance table by means of manual creation or data import. According to the data management method, the data management system can store the basic information and the field information of the data model to be managed into the global library only by creating the data model to be managed and configuring the basic information and the field information of the data model to be managed in the dynamic data model configuration interface of the data weaving system, automatically create the data model instance table in the tenant library corresponding to the user, and further add data in the data model instance table in a manual creation or data import mode to manage the data, so that the workload of data management is greatly simplified, the service code development of the data management is not needed, the technical requirements of technical personnel are reduced, the information of the data model to be managed is configured in a self-defining manner in the dynamic data model configuration interface, the flexibility is good, and the problem that the existing data management method is large in workload and the field information is relieved, The technical problems of high technical requirement threshold and poor flexibility for technical personnel.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a data management method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for adding data to a data model instance table by manual creation according to an embodiment of the present invention;
FIG. 3 is a flowchart of a method for deleting a target data model according to an embodiment of the present invention;
FIG. 4 is a flowchart of deleting a field of a target data model according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a data management apparatus according to an embodiment of the present invention;
fig. 6 is a schematic diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the following embodiments, and it should be understood that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The existing data management method needs technicians to carry out repeated database model design (namely, relational table structure design) and development work, has large workload, needs to carry out customized development again according to the previous development flow for newly proposed dynamic data resource management requirements of enterprises, and has poor flexibility.
Based on this, the data management method of the invention only needs a user to create a data model to be managed in a dynamic data model configuration interface of the data weaving system and configure basic information and field information of the data model to be managed, the data weaving system can store the basic information and the field information of the data model to be managed to a global library, and automatically create a data model instance table in a tenant library corresponding to the user, and then add data in the data model instance table in a manual creation or data import mode to manage the data, thereby greatly simplifying the workload of data management, avoiding the need of developing service codes of data management, reducing the technical requirements of technicians, and performing custom configuration on the information of the data model to be managed in the dynamic data model configuration interface, and having good flexibility.
For the convenience of understanding the present embodiment, a detailed description will be given to a data management method disclosed in the present embodiment.
The first embodiment is as follows:
in accordance with an embodiment of the present invention, there is provided an embodiment of a method for managing data, it should be noted that the steps illustrated in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than that herein.
Fig. 1 is a flowchart of a data management method according to an embodiment of the present invention, as shown in fig. 1, the method includes the following steps:
step S102, acquiring a data model to be managed and basic information of the configured data model to be managed, which are created in a dynamic data model configuration interface by a user of a target tenant, wherein the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model;
in the embodiment of the present invention, the above data management method may be applied to a data weaving system, in which a dynamic data model configuration interface is provided, where the data model configuration interface includes a data model creation button and an area for configuring basic information of a data model.
In a specific implementation, when a target tenant (which may correspond to an enterprise or an enterprise, and the embodiment of the present invention does not specifically limit the relevant data in the jurisdiction area) wants to manage relevant data in the jurisdiction area, a user of the target tenant may log in the data weaving system, click a data model creation button in a dynamic data model configuration interface, thereby creating a data model to be managed, and then configure basic information of the data model to be managed in a basic information configuration area. The basic information may include: name information, identification information, description information, and the like. After the configuration of the basic information is completed, the user can click to save, and then the basic information of the data model to be managed can be saved to the global repository on the name of the target tenant (described in step S104 again).
When the data of another service needs to be managed, the data model can be created again, the user of the target tenant can continue to click the data model creating button, then a data model to be managed under the name of the target tenant is created, then the newly created data model to be managed is subjected to basic information configuration in the basic information configuration area and then stored, and therefore the two data models to be managed and the basic information of the two data models to be managed under the name of the target tenant are obtained in the global library. The two data models to be managed are only visible to users of the target tenant and are invisible to users of other tenants, that is, the data models are isolated through tenant fields (tenant IDs).
It should be noted that the identification information of the data model to be managed is unique, and after the user clicks and stores the identification information, if the data weaving system detects that the identification of the data model to be managed configured by the user is repeated, error prompt information with repeated identification is given, and then the user reconfigures the basic information according to the error prompt information until the identification is not repeated, thereby completing the creation of the data model to be managed.
Step S104, storing the basic information of the data model to be managed to a global library, and creating an empty table with a table name in a tenant library to which a target tenant belongs according to the basic information of the data model to be managed;
specifically, as in step S102, after the user clicks and saves, the basic information of the data model to be managed is saved to the global repository, and a corresponding empty table with a table name may be created in the tenant repository to which the target tenant belongs, where the table name may be an identifier of the data model to be managed.
Step S106, acquiring field information of a data model to be managed, configured in a dynamic data model configuration interface by a user, wherein the dynamic data model configuration interface also comprises an area for configuring the field information of the data model;
after the configuration of the basic information is completed, the system automatically jumps to a field information configuration area in the dynamic data model configuration interface (namely, jumps to a field addition interface), the user adds a field according to the prompt information and configures the field information, after the configuration of the field information is completed, the user clicks to store the field information, and the field information of the data model to be managed is stored to the global library under the name of the target tenant (step S108 is described again).
The region configured by the upper data field information comprises: and the other data models can be used as fields of the data model to be managed (so that the association among different data models is realized).
Step S108, storing the field information of the data model to be managed to a global library, and converting the empty table into a data model instance table according to the field information of the data model to be managed;
specifically, as in step S106, after the user clicks and saves, the field information of the data model to be managed is saved to the global repository, and the empty table created in the tenant repository to which the target tenant belongs is converted into the data model instance table. The data model instance table refers to a table without data added and with a field name as a header, for example, the fields added by the user in step S106 include: ID. Name and time, then the data model instance table is a table with ID, name and time as the header without specific data.
The process of creating the data model instance table may be obtained by adding corresponding fields to the empty table in the form of DDL statements.
It can be seen that, while the data model to be managed is created, a data model instance table is created in the tenant library of the corresponding creator for subsequent data management (including addition, modification and deletion of data).
Step S110, adding data in the data model instance table by means of manual creation or data import.
After the creation of the data model to be managed and the creation of the data model instance table are completed, data can be added into the data model instance table in a manual creation or data import mode to manage the data, and the process is described in detail below and is not described again.
In an embodiment of the present invention, a data management method is provided, which is applied to a data weaving system, and includes: acquiring a data model to be managed created in a dynamic data model configuration interface by a user of a target tenant and basic information of the configured data model to be managed, wherein the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model; storing the basic information of the data model to be managed to a global library, and creating an empty table with a table name in a tenant library to which a target tenant belongs according to the basic information of the data model to be managed; acquiring field information of a data model to be managed, which is configured in a dynamic data model configuration interface by a user, wherein the dynamic data model configuration interface also comprises an area for configuring the field information of the data model; storing the field information of the data model to be managed to a global library, and converting an empty table into a data model instance table according to the field information of the data model to be managed; and adding data in the data model instance table by means of manual creation or data import. According to the data management method, the data management system can store the basic information and the field information of the data model to be managed into the global library only by creating the data model to be managed and configuring the basic information and the field information of the data model to be managed in the dynamic data model configuration interface of the data weaving system, automatically create the data model instance table in the tenant library corresponding to the user, and further add data in the data model instance table in a manual creation or data import mode to manage the data, so that the workload of data management is greatly simplified, the service code development of the data management is not needed, the technical requirements of technical personnel are reduced, the information of the data model to be managed is configured in a self-defining manner in the dynamic data model configuration interface, the flexibility is good, and the problem that the existing data management method is large in workload and the field information is relieved, The technical problems of high technical requirement threshold and poor flexibility for technical personnel.
The foregoing briefly introduces the data management method of the present invention, and the details thereof are described in detail below.
In an optional embodiment of the present invention, the region for configuring the field information of the data model includes: the step S106 is to obtain field information of the data model to be managed configured in the dynamic data model configuration interface by the user, and specifically includes the following steps:
acquiring a first field added by a user; if the first field is not the primary key field, prompting a user to add the primary key field, and configuring the primary key field, wherein the configuration comprises at least one of the following: configuring a field type and a field checking rule; and after the configuration of the primary key field is completed, acquiring other field information added and configured by the user.
Specifically, when adding the field, the field added first is defaulted as a primary key, and the field added by the primary key can be added only after the field added by the primary key, and if the field added by the primary key is not added, the field added by the primary key is forced to be created first subsequently.
The above description describes the process of adding fields in detail, and the following description describes the specific process of adding data in detail.
In an optional embodiment of the present invention, referring to fig. 2, the step S110, adding data in the data model instance table in a manual creation manner, specifically includes the following steps:
step S201, loading field information of a data model to be managed of a target tenant in a global library according to a manual creation mode selected by a user;
step S202, generating a field data form according to the field information of the data model to be managed;
specifically, the form includes a plurality of preconfigured fields, field check rules, and default values of some preconfigured fields, and some fields in the form have no numerical values and need to be manually filled in by the user.
Step S203, acquiring data filled in the field data form by the user, and verifying the data according to a preset corresponding field verification rule;
specifically, after the user fills data in the field data form, the user clicks and saves the data, and the filled data is verified according to the preset corresponding field verification rule.
Step S204, if the verification is passed, storing the data into a data model instance table;
and step S205, if the verification fails, returning the prompt message.
Specifically, the user is prompted to refill the form.
In the above manual creation mode, data is stored in the data model instance table, and the embodiment of the present invention further provides a mode for importing batch data into the data model instance table.
In an optional embodiment of the present invention, adding data in the data model instance table by means of data import specifically includes the following steps:
generating a form template according to a data import mode selected by a user and field information of a to-be-managed data model of a target tenant in a global library; acquiring batch data filled in a form template by a user, and importing the batch data in the form template into a data model instance table, wherein in the importing process, if the batch data does not pass the verification of a corresponding field verification rule configured in advance, an error prompt message is returned, and if the batch data passes the verification of the corresponding field verification rule configured in advance, the batch data is stored in the data model instance table.
Specifically, the form template may be an excel template, in the excel template, the header is a name of each field, then, the user fills batch data in the form template (when the user fills in data, the data is filled according to the data generated by the device within the authority range of the user, the system of the present invention models the data generated by the device, and then further manages the data), and further, the batch data in the form template is imported into the data model instance table, wherein in the importing process, if the batch data does not pass the verification of the pre-configured corresponding field verification rule, an error prompt message is returned, the received document is prompted to be an error document, and if the batch data passes the verification of the pre-configured corresponding field verification rule, the batch data is stored in the data model instance table.
The user can also modify the created data model to be managed in the data weaving system of the invention. In an optional embodiment of the invention, the method further comprises:
acquiring basic information of a data model to be managed and field information of the data model to be managed, which are modified in a dynamic data model configuration interface by a user; and updating the corresponding basic information and field information in the global library according to the basic information of the data model to be managed modified by the user and the field information of the data model to be managed.
Specifically, in order to ensure the integrity of data, the modification of the basic information and the field information generally only can modify some auxiliary parameters, for example, the name of the field, the initial value of the field, the check rule of the field, fill/fill-unnecessary, whether to display, and the like can be modified. And after the basic information and the field information are modified, updating the corresponding basic information and the corresponding field information in the global library according to the modified basic information and the modified field information. For example, if the field check rule is modified, the new check rule is substituted for the old check rule in the global repository, and then the added data is checked according to the new check rule when the data is added later (because the field data form or the form template is generated according to the updated field information in the global repository when the data is added, the subsequent check is also checked according to the updated check rule), the data added before in the data model instance table is not adjusted, that is, the integrity of the previous data is not affected.
The user may also delete the created target data model in the data weaving system of the present invention. In an alternative embodiment of the present invention, referring to fig. 3, the method further comprises:
step S301, acquiring a request for deleting a target data model triggered by a user;
specifically, the target data model is a data model under the name of the tenant to which the user belongs, and the target data model is any data model under the name of the tenant to which the user belongs, which is selected by the user.
Step S302, judging whether the target data model is used or not based on the request;
specifically, whether the target data model has related data or not is judged, that is, whether the data is stored in the data model instance table of the target data model or not is judged, in addition, whether the target data model is referred by other data models or not is judged, and if the target data model is used as a field of other data models, the target data model is referred.
The data already stored in the data model instance table of the target data model or the target data model referenced is called the target data model.
Step S303, if the target data model is used, prompting that the target data model is not allowed to be deleted;
specifically, when the target data model is used, the target data model is not allowed to be deleted, so as to avoid loss and incompleteness of data.
And step S304, if the target data model is not used, deleting the basic information of the target data model and the field information of the target data model in the global library, and deleting the data model instance table of the target data model in the tenant library corresponding to the target data model.
The user may also delete fields of the target data model in the data weaving system of the present invention. In an alternative embodiment of the present invention, referring to fig. 4, the method further comprises:
step S401, acquiring a request for deleting a target field of a target data model triggered by a user;
specifically, the target data model is any data model selected by the user under the name of the tenant to which the target data model belongs.
Step S402, judging whether the target field of the target data model has data or not based on the request;
step S403, if data exist, prompting that the target field of the target data model is not allowed to be deleted;
specifically, when the target field of the target data model has data, the target field of the target data model is not allowed to be deleted, so as to avoid loss and incompleteness of the data.
And S404, if no data exists, deleting field information of a target field of the target data model in the global library, and modifying a data model instance table structure of the target data model in a tenant library corresponding to the target data model.
Specifically, deleting the target field in the data model instance table of the target data model does not affect the availability of the whole target data model and the integrity of data.
In conclusion, the invention provides the implementation method which has strong flexibility, is divided into the libraries according to the tenants and can autonomously increase the data management. The data weaving system provides a dynamic data model configuration interface, a user can create a data model and add data model fields in the interface, multiple types of model fields can be selected, each type of field can be set with related auxiliary parameters (check rules), such as default values, numerical value ranges and the like, and set field check rules, and when data records are added to a data model instance table, the recorded values (namely the data) can be checked according to the field check rules; according to the method, the data model and the data model instance table are divided into databases, a global database is used for recording data model data of each tenant, data such as data models, model fields, incidence relations and the like which are independently created by the tenant are stored in the global table, the data models are created according to the tenant, model data added by the tenant are stored in the respective tenant database, and therefore isolation of data between tenants is achieved; the method can realize compatibility of multiple data models, can adapt to multiple types of data models, can flexibly and autonomously create abstract models to achieve the final management of instantiated data, and simultaneously supports secondary development to realize the unified management of more complex data types; the data output dynamic configuration can be carried out, the output configuration of the data field is defined, personalized data model output is provided for different scenes, the output of dynamic configuration data is supported under the condition that the data is not influenced, and the data can be flexibly visually configured.
The data weaving system of the invention has the following characteristics: a visual data model establishing and configuring interface, wherein a user can establish a data model through related data types built in a system and freely configure verification and association management of data according to individual requirements; after the model is dynamically changed, the integrity of original data and the usability of the data model are ensured, the change of the model can be dynamically supported, the model field configuration and the field association are flexible, the management of various actual production data can be compatible, and the data can be individually managed in a visualized manner through the field configuration; the unified configuration format standard is provided for the modeling logic configuration of different data models, the configuration is visualized, the association of different models can be carried out in the same tenant, and the data can be better and completely displayed.
The method is based on the data model of the enterprise, serves the data management of the enterprise, enables a user to freely configure the data model according to individual requirements and flexibly manage the data, and achieves the equipment data management function of the cloud platform of the Internet of things. The enterprise data is dynamically modeled and maintained through an interface, the construction realization of an enterprise data model is quickly responded, the instance data is managed by tenants, and the data is safely isolated; the implementation method flexibly helps enterprises to perform personalized data management, safely guarantees the integrity and the safety of related data, can quickly establish data association and data management, and simultaneously supports secondary development to adapt to more complex data structures, and has strong universality and wide application range.
Example two:
the embodiment of the present invention further provides a data management device, where the data management device is mainly used to execute the data management method provided in the first embodiment of the present invention, and the following describes the data management device provided in the first embodiment of the present invention in detail.
Fig. 5 is a schematic diagram of a data management apparatus according to an embodiment of the present invention, and as shown in fig. 5, the apparatus mainly includes: a first acquiring unit 10, a first holding unit 20, a second acquiring unit 30, a second holding unit 40, and a data adding unit 50, wherein:
the data model management system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a data model to be managed and basic information of the configured data model to be managed, which are created in a dynamic data model configuration interface by a user of a target tenant, and the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model;
the first storage unit is used for storing the basic information of the data model to be managed to a global library and creating an empty table with a table name in a tenant library to which a target tenant belongs according to the basic information of the data model to be managed;
the second obtaining unit is used for obtaining field information of the data model to be managed, configured in the dynamic data model configuration interface by the user, wherein the dynamic data model configuration interface further comprises an area used for configuring the field information of the data model;
the second storage unit is used for storing the field information of the data model to be managed to the global library and converting the empty table into a data model instance table according to the field information of the data model to be managed;
and the data adding unit is used for adding data in the data model instance table in a manual creation or data import mode.
In an embodiment of the present invention, a data management apparatus is provided, which is applied to a data weaving system, and the method includes: acquiring a data model to be managed created in a dynamic data model configuration interface by a user of a target tenant and basic information of the configured data model to be managed, wherein the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model; storing the basic information of the data model to be managed to a global library, and creating an empty table with a table name in a tenant library to which a target tenant belongs according to the basic information of the data model to be managed; acquiring field information of a data model to be managed, which is configured in a dynamic data model configuration interface by a user, wherein the dynamic data model configuration interface also comprises an area for configuring the field information of the data model; storing the field information of the data model to be managed to a global library, and converting an empty table into a data model instance table according to the field information of the data model to be managed; and adding data in the data model instance table by means of manual creation or data import. According to the description, the data management device provided by the invention only needs a user to create the data model to be managed and configure the basic information and the field information of the data model to be managed in the dynamic data model configuration interface of the data weaving system, the data weaving system can store the basic information and the field information of the data model to be managed in the global library, and automatically create the data model instance table in the tenant library corresponding to the user, and then add data in the data model instance table in a manual creation or data import mode to manage the data, so that the workload of data management is greatly simplified, the service code development of the data management is not needed, the technical requirements of technical personnel are reduced, the information of the data model to be managed is configured in a self-defining manner in the dynamic data model configuration interface, the flexibility is good, and the workload of the existing data management method is relieved, The technical problems of high technical requirement threshold and poor flexibility for technical personnel.
Optionally, the region for configuring the field information of the data model includes: the second acquiring unit is further configured to: acquiring a first field added by a user; if the first field is not the primary key field, prompting a user to add the primary key field, and configuring the primary key field, wherein the configuration comprises at least one of the following: configuring a field type and a field checking rule; and after the configuration of the primary key field is completed, acquiring other field information added and configured by the user.
Optionally, the data adding unit is further configured to: loading field information of a data model to be managed of a target tenant in a global library according to a manual creation mode selected by a user; generating a field data form according to field information of a data model to be managed; acquiring data filled in a field data form by a user, and verifying the data according to a preset corresponding field verification rule; if the verification is passed, storing the data into a data model instance table; and if the verification fails, returning prompt information.
Optionally, the data adding unit is further configured to: generating a form template according to a data import mode selected by a user and field information of a to-be-managed data model of a target tenant in a global library; acquiring batch data filled in a form template by a user, and importing the batch data in the form template into a data model instance table, wherein in the importing process, if the batch data does not pass the verification of a corresponding field verification rule configured in advance, an error prompt message is returned, and if the batch data passes the verification of the corresponding field verification rule configured in advance, the batch data is stored in the data model instance table.
Optionally, the apparatus is further configured to: acquiring basic information of a data model to be managed and field information of the data model to be managed, which are modified in a dynamic data model configuration interface by a user; and updating the corresponding basic information and field information in the global library according to the basic information of the data model to be managed modified by the user and the field information of the data model to be managed.
Optionally, the apparatus is further configured to: acquiring a request for deleting a target data model triggered by a user; determining whether the target data model has been used based on the request; if the target data model is used, prompting that the target data model is not allowed to be deleted; and if the tenant database is not used, deleting the basic information of the target data model and the field information of the target data model in the global database, and deleting the data model instance table of the target data model in the tenant database corresponding to the target data model.
Optionally, the apparatus is further configured to: acquiring a request for deleting a target field of a target data model triggered by a user; judging whether a target field of the target data model has data or not based on the request; if the data exists, prompting that the target field of the target data model is not allowed to be deleted; and if no data exists, deleting field information of a target field of the target data model in the global library, and modifying a data model instance table structure of the target data model in a tenant library corresponding to the target data model.
The device provided by the embodiment of the present invention has the same implementation principle and technical effect as the method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the method embodiments without reference to the device embodiments.
As shown in fig. 6, an electronic device 600 provided in an embodiment of the present application includes: a processor 601, a memory 602 and a bus, wherein the memory 602 stores machine-readable instructions executable by the processor 601, when the electronic device runs, the processor 601 and the memory 602 communicate with each other through the bus, and the processor 601 executes the machine-readable instructions to execute the steps of the management method of the data.
Specifically, the memory 602 and the processor 601 can be general-purpose memories and processors, which are not specifically limited herein, and the processor 601 can execute the data management method when executing the computer program stored in the memory 602.
The processor 601 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 601. The Processor 601 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 602, and the processor 601 reads the information in the memory 602 and completes the steps of the method in combination with the hardware thereof.
Corresponding to the management method of the data, the embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores machine executable instructions, and when the computer executable instructions are called and executed by a processor, the computer executable instructions cause the processor to execute the steps of the management method of the data.
The management device of the data provided by the embodiment of the present application may be specific hardware on the device, or software or firmware installed on the device, etc. The device provided by the embodiment of the present application has the same implementation principle and technical effect as the foregoing method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the foregoing method embodiments where no part of the device embodiments is mentioned. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the foregoing systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
For another example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing an electronic device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the vehicle marking method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, the terms "first", "second", "third", etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the scope of the embodiments of the present application. Are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A data management method is applied to a data weaving system, and the method comprises the following steps:
acquiring a data model to be managed, which is created in a dynamic data model configuration interface by a user of a target tenant, and configured basic information of the data model to be managed, wherein the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model;
storing the basic information of the data model to be managed to a global library, and creating an empty table with a table name in a tenant library to which the target tenant belongs according to the basic information of the data model to be managed;
acquiring field information of the data model to be managed, which is configured in the dynamic data model configuration interface by the user, wherein the dynamic data model configuration interface further comprises an area for configuring the field information of the data model;
storing the field information of the data model to be managed to the global library, and converting the empty table into a data model instance table according to the field information of the data model to be managed;
and adding data in the data model instance table by means of manual creation or data import.
2. The method according to claim 1, wherein the region for configuring the field information of the data model comprises: the method comprises the following steps that a plurality of optional field types, configurable field verification rules and field output configurations are adopted, and other data models can be used as fields of the data model to be managed to acquire field information of the data model to be managed configured in the dynamic data model configuration interface by the user, and the method comprises the following steps:
acquiring a first field added by the user;
if the first field is not a primary key field, prompting the user to add the primary key field, and configuring the primary key field, wherein the configuration comprises at least one of the following: configuring a field type and a field checking rule;
and after the configuration of the primary key field is completed, acquiring other field information added and configured by the user.
3. The method of claim 2, wherein adding data in the data model instance table by way of manual creation comprises:
loading field information of a to-be-managed data model of the target tenant in the global library according to the manual creation mode selected by the user;
generating a field data form according to the field information of the data model to be managed;
acquiring data filled in the field data form by the user, and verifying the data according to a preset corresponding field verification rule;
if the verification is passed, storing the data into the data model instance table;
and if the verification fails, returning prompt information.
4. The method of claim 2, wherein adding data in the data model instance table by means of data import comprises:
generating a form template according to the data import mode selected by the user and the field information of the data model to be managed of the target tenant in the global library;
and acquiring batch data filled in the form template by the user, and importing the batch data in the form template into the data model instance table, wherein in the importing process, if the batch data does not pass the verification of the corresponding field verification rule configured in advance, an error prompt message is returned, and if the batch data passes the verification of the corresponding field verification rule configured in advance, the batch data is stored in the data model instance table.
5. The method of claim 1, further comprising:
acquiring basic information of a data model to be managed and field information of the data model to be managed, which are modified in the dynamic data model configuration interface by the user;
and updating the corresponding basic information and field information in the global library according to the basic information of the data model to be managed modified by the user and the field information of the data model to be managed.
6. The method of claim 1, further comprising:
acquiring a request for deleting the target data model triggered by the user;
determining whether the target data model has been used based on the request;
if the target data model is used, prompting that the target data model is not allowed to be deleted;
and if the target data model is not used, deleting the basic information of the target data model and the field information of the target data model in the global library, and deleting a data model instance table of the target data model in a tenant library corresponding to the target data model.
7. The method of claim 1, further comprising:
acquiring a request for deleting a target field of a target data model triggered by the user;
judging whether a target field of the target data model has data or not based on the request;
if the data exists, prompting that the target field of the target data model is not allowed to be deleted;
and if no data exists, deleting field information of a target field of the target data model in the global library, and modifying a data model instance table structure of the target data model in a tenant library corresponding to the target data model.
8. A data management device, which is applied to a data weaving system, the device comprising:
the data model management system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a data model to be managed and configured basic information of the data model to be managed, which are created in a dynamic data model configuration interface by a user of a target tenant, and the dynamic data model configuration interface comprises a data model creation button and an area for configuring the basic information of the data model;
the first storage unit is used for storing the basic information of the data model to be managed to a global library and creating an empty table with a table name in a tenant library to which the target tenant belongs according to the basic information of the data model to be managed;
a second obtaining unit, configured to obtain field information of the data model to be managed, configured in the dynamic data model configuration interface by the user, where the dynamic data model configuration interface further includes an area for configuring the field information of the data model;
the second storage unit is used for storing the field information of the data model to be managed to the global library and converting the empty table into a data model instance table according to the field information of the data model to be managed;
and the data adding unit is used for adding data in the data model instance table in a manual creation or data import mode.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the method of any of the preceding claims 1 to 7 are implemented when the computer program is executed by the processor.
10. A computer readable storage medium having stored thereon machine executable instructions which, when invoked and executed by a processor, cause the processor to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029591.XA CN114048194A (en) | 2022-01-12 | 2022-01-12 | Data management method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029591.XA CN114048194A (en) | 2022-01-12 | 2022-01-12 | Data management method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114048194A true CN114048194A (en) | 2022-02-15 |
Family
ID=80196305
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210029591.XA Pending CN114048194A (en) | 2022-01-12 | 2022-01-12 | Data management method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114048194A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115659940A (en) * | 2022-11-09 | 2023-01-31 | 北京白龙马云行科技有限公司 | Template adjusting method based on SaaS system, driver information obtaining method and device |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050216503A1 (en) * | 2001-11-30 | 2005-09-29 | Regis Charlot | Method for adaptive data management |
| CN104317974A (en) * | 2014-11-21 | 2015-01-28 | 武汉理工大学 | Reconfigurable multi-source data importing method in ERP system |
| CN106203810A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | CRM data processing method based on cloud platform |
| CN106209443A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | Client relation management method based on cloud computing |
| CN106202339A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | Enterprise CRM system date storage method |
| CN106933837A (en) * | 2015-12-29 | 2017-07-07 | 航天信息股份有限公司 | A kind of database table model and creation method |
| CN109933311A (en) * | 2019-03-20 | 2019-06-25 | 青岛叁壹信息科技有限公司 | A kind of information system creation method and relevant apparatus |
| CN111414739A (en) * | 2020-02-27 | 2020-07-14 | 北京中亦安图科技股份有限公司 | Excel data entry component, entry method and device |
| US20200233906A1 (en) * | 2019-01-21 | 2020-07-23 | Netapp, Inc. | Community generation based on a common set of attributes |
| CN112487006A (en) * | 2020-11-30 | 2021-03-12 | 山东浪潮通软信息科技有限公司 | Implementation method for dynamically editing data structure and generating database table |
| WO2021184571A1 (en) * | 2020-03-17 | 2021-09-23 | 平安国际智慧城市科技股份有限公司 | Dynamic form generation method, apparatus, computer device, and storage medium |
-
2022
- 2022-01-12 CN CN202210029591.XA patent/CN114048194A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050216503A1 (en) * | 2001-11-30 | 2005-09-29 | Regis Charlot | Method for adaptive data management |
| CN104317974A (en) * | 2014-11-21 | 2015-01-28 | 武汉理工大学 | Reconfigurable multi-source data importing method in ERP system |
| CN106933837A (en) * | 2015-12-29 | 2017-07-07 | 航天信息股份有限公司 | A kind of database table model and creation method |
| CN106203810A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | CRM data processing method based on cloud platform |
| CN106209443A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | Client relation management method based on cloud computing |
| CN106202339A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | Enterprise CRM system date storage method |
| US20200233906A1 (en) * | 2019-01-21 | 2020-07-23 | Netapp, Inc. | Community generation based on a common set of attributes |
| CN109933311A (en) * | 2019-03-20 | 2019-06-25 | 青岛叁壹信息科技有限公司 | A kind of information system creation method and relevant apparatus |
| CN111414739A (en) * | 2020-02-27 | 2020-07-14 | 北京中亦安图科技股份有限公司 | Excel data entry component, entry method and device |
| WO2021184571A1 (en) * | 2020-03-17 | 2021-09-23 | 平安国际智慧城市科技股份有限公司 | Dynamic form generation method, apparatus, computer device, and storage medium |
| CN112487006A (en) * | 2020-11-30 | 2021-03-12 | 山东浪潮通软信息科技有限公司 | Implementation method for dynamically editing data structure and generating database table |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115659940A (en) * | 2022-11-09 | 2023-01-31 | 北京白龙马云行科技有限公司 | Template adjusting method based on SaaS system, driver information obtaining method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105164660A (en) | Cloud based service design inheritance | |
| CN109032590B (en) | Configuration method, device, terminal and storage medium of visual development environment | |
| CN115993966B (en) | Application development system and method | |
| CN110764775A (en) | Application program integration method and device, storage medium and server | |
| CN111506579A (en) | Method, program and equipment for generating intelligent contract code | |
| CN114048194A (en) | Data management method and device and electronic equipment | |
| CN106708897B (en) | Data warehouse quality guarantee method, device and system | |
| CN115688715A (en) | Report generation method and device and computer readable medium | |
| CN115220697A (en) | API development management method, device, vehicle and storage medium | |
| CN111581183A (en) | Data migration method and device based on data model | |
| CN114564194A (en) | Form self-defining development method and system based on VUE framework | |
| CN115525534A (en) | Test case generation method and platform based on swagger interface test | |
| CN112561690A (en) | Method, system, equipment and storage medium for testing credit card staging service interface | |
| CN114124977B (en) | Cross-tenant data sharing method and device and electronic equipment | |
| CN108804401B (en) | Report template merging method and device | |
| CN110807185A (en) | System access method, device and server | |
| CN113076086B (en) | Metadata management system and method for modeling model object using the same | |
| CN115878643A (en) | Method, device and application for automatically checking multiple databases based on button | |
| CN112099879A (en) | Configuration information management method and device, computer equipment and storage medium | |
| CN111459907B (en) | Method, system and storage medium for configuring main data through model | |
| CN109117152B (en) | Service generation system and method | |
| CN114489674A (en) | Data verification method and device of dynamic data model | |
| CN112685400A (en) | Method and system for detecting quality of health medical data based on SDK rule engine | |
| CN112749159A (en) | Form generation method and device, electronic equipment and storage medium | |
| CN114556238A (en) | Method and system for generating digital representation of asset information in cloud computing environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220215 |