Data management method and device, equipment and storage medium

Abstract

The invention discloses a data management method, belongs to the field of data processing, and is used for performing unified management on disordered data. The method comprises the steps that multiple pieces of preset main data field information and label template information corresponding to the main data field information are obtained, the main data field information is used for representing set information of main data with the same features, and the label template information is used for representing feature information of the main data included in the main data field information; first main data and first label information sent by the first person are received, the first label information is determined based on label template information corresponding to first domain information, and the first domain information is main data domain information determined based on data features of the first main data; determining the first main data and the first label information as to-be-managed data, and storing the to-be-managed data; and receiving a management instruction sent by the second person for the to-be-managed data, and performing data management on the to-be-managed data based on the management instruction.

Description

Technical Field

[0001] This application belongs to the field of data processing, and particularly relates to a method, apparatus, device, and storage medium for analyzing application system failures. Background Art

[0002] In the process of business operation, many enterprises need to use a large amount of public data, which often involves various fields, with a large and messy amount of data. For example, in the insurance industry, data such as exchange rates, administrative divisions, and institutions are required for business operations. These data are often collected by each system independently and stored in the databases of each enterprise system to provide technical services for business operations. Each system stores public data on its own without a unified standard, which may lead to interaction problems due to data inconsistency during system interaction. Moreover, due to the lack of management, the data may be randomly modified or deleted, resulting in problems when the system provides technical services for business.

[0003] Therefore, a data management method capable of uniformly managing messy data is needed. Summary of the Invention

[0004] An embodiment of this application provides a data management method that can uniformly manage messy data.

[0005] In a first aspect, an embodiment of this application provides a data management method, which includes: obtaining a plurality of preset master data domain information and corresponding tag template information for each of the master data domain information, where the master data domain information is used to represent the set information of master data with the same characteristics, and the tag template information is used to represent the characteristic information of the master data included in each of the master data domain information; receiving a first master data and first tag information sent by a first person, where the first master data is the master data to be managed, and the first tag information is determined based on the tag template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data; determining the first master data and the first tag information as data to be managed, and storing the data to be managed; receiving a management instruction sent by a second person for the data to be managed to perform data management on the data to be managed based on the management instruction. Second aspect, an embodiment of the present application provides a data management device, which includes: a first acquisition module, configured to acquire a plurality of preset master data domain information and label template information corresponding to each of the master data domain information, where the master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information; a first receiving module, configured to receive a first master data and first label information sent by a first person, where the first master data is the master data to be managed, and the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data; a first storage module, configured to determine the first master data and the first label information as data to be managed, and store the data to be managed; a first management module, configured to receive a management instruction sent by a second person for the data to be managed, so as to perform data management on the data to be managed based on the management instruction.

[0006] Third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0007] Fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0008] Fifth aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the method described in the first aspect.

[0009] In an embodiment of the present application, by obtaining a plurality of preset master data domain information and label template information corresponding to each of the master data domain information, the master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information; receiving first master data and first label information sent by a first person, the first master data is the master data to be managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data; determining the first master data and the first label information as data to be managed, and storing the data to be managed; receiving a management instruction sent by a second person for the data to be managed, and performing data management on the data to be managed based on the management instruction, so as to be able to uniformly manage messy data. Description of the Drawings

[0010] Figure 1 is a schematic flowchart of a data management method provided by an embodiment of the present application; Figure 2 is a schematic diagram showing master data domain information provided by an embodiment of the present application; Figure 3 is a schematic flowchart of a second data management method provided by an embodiment of the present application; Figure 4 is a schematic flowchart of a third data management method provided by an embodiment of the present application; Figure 5 is a schematic flowchart of a fourth data management method provided by an embodiment of the present application; Figure 6 is a schematic diagram of the structure of a data management device provided by an embodiment of the present application; Figure 7 is a schematic diagram of the structure of a data management device provided by an embodiment of the present application. Detailed Embodiments

[0011] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0012] The terms "first", "second", etc. in the description and claims of this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of this application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are usually of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the description and claims means at least one of the connected objects, and the character " / ", generally represents an "or" relationship between the associated objects before and after.

[0013] The following will combine the accompanying drawings and through specific embodiments and their application scenarios to elaborate in detail on the data management method provided by the embodiments of this application.

[0014] Figure 1 An embodiment of the present invention provides a data management method, which can be executed by an electronic device. The electronic device may include: a server and / or a terminal device, where the terminal device may be, for example, a vehicle-mounted terminal or a mobile phone terminal, etc. In other words, this method can be executed by software or hardware installed in the data management device. The method includes the following steps: Step 102: Obtain a plurality of preset master data domain information and label template information corresponding to each of the master data domain information.

[0015] Among them, the master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information.

[0016] The data management system obtains a plurality of preset master data domain information and label template information corresponding to each master data domain information. Among them, the master data domain information is used to represent the set information of a plurality of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each master data domain information. That is to say, the data management system first determines a plurality of master data with the same characteristics, and then determines the master data domain information based on the plurality of master data with the same characteristics. That is, the master data domain information can include or be used to store a plurality of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data with the same characteristics included in each master data domain, that is, the label template information is used to represent the characteristic information of the plurality of master data with the same characteristics included in or used to store in each master data domain information.

[0017] Specifically, the master data domain information is used to represent the collective information of master data with the same characteristics, that is, the master data domain information can be used to represent master data information of the same type, such as master data related to customers, master data related to funds, or master data related to the customer service department. The label template information, on the other hand, is used to represent the characteristic information of multiple master data included in the same master data domain information, that is, the label template information can also be used to represent the characteristic information of master data of the same type. For example, the label template information corresponding to master data related to customers may include user characteristic information, etc.; the label template information corresponding to master data related to funds may include fund numerical information, etc.; and the label template information corresponding to master data related to the customer service department may include customer service department ID information, etc.

[0018] More specifically, when the data management system determines the master data domain information, it can classify according to the usage of the master data and / or the department to which the master data belongs, so as to determine each master data domain information. For example, when determining each master data domain information according to the usage of the master data, it can be determined that each master data domain information is customer-related data, bank-related data, channel-related data, extended warranty-related data, fund-related data, etc. When determining each master data domain information according to the department to which the master data belongs, it can be determined that each master data domain information is data of the science and technology department, data of the customer service department, data of the property department, and data of the claims department, etc. Each master data domain corresponds to a type of master data, and the structure and format of the master data stored in each master data domain can be dynamically adjusted according to the content of the label template information. For example, Figure 2 Shown is a schematic diagram of the display of master data domain information shown in this application. Such as Figure 2 The master data domain information shown is the master data domain determined according to different management departments. The data domain information can not only not include information such as the name of the management department, the Chinese name of the data domain, and the English name of the data domain, but can also include attribute information of the master data domain such as the effective date, expiration date, and master data classification of the master data domain.

[0019] Furthermore, the master data stored in different master data domain information can be stored in the form of data segments. When the master data is stored in the form of data segments, the label template information can also be used to represent the characteristic information of the master data segments stored in different master data domain information, such as the characteristic information of each part of the master data segment corresponding to the customer service department data. Among them, the characteristic information of each part of the master data segment corresponding to different master data domain information is different.

[0020] Furthermore, when constructing the information management system, the master data is divided into different master data domains according to its business attributes and functional scopes. Each master data domain focuses on a specific business area, such as institutional information, catastrophe coding information, etc. Inside each master data domain, it is further subdivided according to the specific business process requirements or specific attributes of the data to form a secondary level, which represents the refined classification of the master data in different business scenarios. For example, under the institutional information domain, it can be further divided into provincial institutional information, separately listed city institutional information, etc. Further, according to the business complexity and data management needs, a tertiary level is divided on the basis of the secondary level to achieve more refined management of the data. This hierarchical division method ensures the clarity, logic, and scalability of the master data structure, and helps to improve the efficiency and accuracy of data management.

[0021] Step 104: Receive the first master data and the first label information sent by the first person.

[0022] Among them, the first master data is the master data that needs to be managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data.

[0023] After determining multiple master data domain information and the label template information corresponding to each master data domain information, the data management system receives the first master data and the first label information sent by the first person. Among them, the first person is the operator who performs the master data storage operation, the first master data is the master data that needs to be stored and managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data, that is, the first label information is determined based on the label template information corresponding to the master data domain information to which the data characteristics of the first master data belong.

[0024] Specifically, the first person determines the master data domain information to which the first master data belongs based on the data characteristics of the first master data (such as data of the customer service department), and then determines the first label information corresponding to the first master data based on the label template information corresponding to the master data domain information (such as the characteristic information of each part of the first master data data segment). That is to say, the first person determines the label information of the first master data based on the first master data and the label template information corresponding to the master data domain information to which the first master data belongs, that is, the first label.

[0025] Step 106: Determine the first master data and the first label information as the data to be managed, and store the data to be managed.

[0026] After receiving the first master data and the first tag information sent by the first person, the data management system determines the first master data and the first tag information as data to be managed, and stores the determined data to be managed. That is to say, the data management system determines the master data to be managed and the tag information corresponding to the master data as data to be managed, and stores the data to be managed.

[0027] Specifically, the data management system can use the first master data and the first tag information as two components of the data to be managed (i.e., the data to be managed consists of the first master data and the first tag information), and then inputs the data to be managed composed of the first master data and the first tag information into a pre-set database for storage.

[0028] Step 108: Receive the management instruction sent by the second person for the data to be managed, and perform data management on the data to be managed based on the management instruction.

[0029] After storing the data to be managed, the data management system receives the management instruction sent by the second person for the data to be managed, and performs data management on the data to be managed based on the management instruction. Here, the second person is the person who performs data management, and the first person and the second person can be the same person or not. That is to say, the management instruction sent by the second person includes the management operations that the second person needs to perform. After receiving the management instruction of the second person, the data management system can perform data management on the data to be managed according to the management operations included in the management instruction.

[0030] Specifically, the management instruction can be a data browsing instruction, a data deletion instruction, etc. for the master data. After the data management system receives the data browsing instruction and / or data deletion instruction sent by the second person, it can perform relevant data management according to the data browsing instruction and / or data deletion instruction. For example, when the management instruction is a data browsing instruction, it can display the data to be managed requested by the second person to browse. When the management instruction is a data deletion instruction, it can delete the data to be managed requested by the second person to delete.

[0031] The data management method provided by the embodiments of the present invention obtains a plurality of preset master data domain information and label template information corresponding to each of the master data domain information. The master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information; receives the first master data and the first label information sent by the first person. The first master data is the master data to be managed, and the first label information is determined based on the label template information corresponding to the first domain information. The first domain information is the master data domain information determined based on the data characteristics of the first master data; determines the first master data and the first label information as the data to be managed, and stores the data to be managed; receives the management instruction sent by the second person for the data to be managed, and performs data management on the data to be managed based on the management instruction, so as to uniformly manage the messy data.

[0032] In one implementation, the step of receiving the management instruction sent by the second person for the data to be managed and performing data management on the data to be managed based on the management instruction (step 108) can execute steps A1 - A2: Step A1: Receive the data change request sent by the second person for the data to be managed.

[0033] Wherein, the data change request is used to request to change the data to be managed.

[0034] The data management system can receive the data change request sent by the second person for the data to be managed, and this data change request is used to request to change the data to be managed. That is to say, when the second person needs to modify the stored data to be managed, the data management system can be sent a data change request, so as to request the data management system to change the data to be managed.

[0035] Step A2: Change the data to be managed based on the data change request to perform data management on the data to be managed.

[0036] After the data management system receives the data change request sent by the second person, the data management system changes the data to be managed based on the change operation in the data change request, so as to complete the data management of the data to be managed.

[0037] Specifically, after the data management system receives the data change request (or data modification request) sent by the second person, the data management system can perform identity verification based on the identity identification information in the data change request (or data modification request), and execute the management operation included in the data change request (or data modification request) after the identity verification passes.

[0038] In one implementation, before receiving the first master data and the first tag information sent by the first person (step 102), steps B1 - B2 may also be executed: Step B1: Obtain the first identity identifier of the first person, and determine whether the first person has data storage permission based on the first identity identifier.

[0039] Before the data management system receives the first master data and the first tag information sent by the first person, the data management system can also obtain the first identity identifier of the first person, and then determine whether the first person has data storage permission based on the first identity identifier. That is, before storing the first master data and the first tag information sent by the first person, the data management system can first authenticate the first person to verify whether he has the permission for data input and storage. Among them, the data management system pre - stores the permission information corresponding to multiple identity identifiers, so as to be able to determine the corresponding permission information according to the identity identifier of the first person, and further determine whether the first person has data storage permission.

[0040] Step B2: If so, receive the first master data and the first tag information sent by the first person.

[0041] After the data management system obtains the first identity identifier of the first person and determines that the first person has the storage permission for data input according to the first identity identifier, the data management system receives the first master data and the first tag information sent by the first person. After the data management system determines that the first person does not have the storage permission for data input according to the first identity identifier, the data management system does not receive the first master data and the first tag information sent by the first person.

[0042] Before receiving the management instruction sent by the second person for the data to be managed (step 108), steps B3 - B4 may also be executed: Step B3: Obtain the second identity identifier of the second person, and determine whether the second person has data management permission based on the second identity identifier.

[0043] Before the data management system receives the management instruction sent by the second person for the data to be managed, the data management system can also obtain the second identity identifier of the second person, and then determine whether the second person has the data management authority based on the second identity identifier. That is to say, before sending the management instruction sent by the second person and performing management operations based on the management instruction, the data management system can first authenticate the second person to verify whether he has the authority to manage data. Among them, the data management system pre-stores the management authority information corresponding to multiple identity identifiers, so that the data management system can determine the corresponding identity authority information according to the identity identifier of the second person, and then determine whether the second person has the data management authority.

[0044] Step B4: If so, receive the management instruction sent by the second person for the data to be managed.

[0045] After the data management system obtains the second identity identifier of the second person and determines that the second person has the data management authority according to the second identity identifier, the data management system then receives the management instruction sent by the second person for the data to be managed, and then performs data management on the data to be managed according to the management operations included in the management instruction. After the data management system determines that the second person does not have the data management authority according to the second identity identifier, the data management system does not receive the management instruction sent by the second person for the data to be managed.

[0046] In one implementation manner, the step of determining the first master data and the first tag information as the data to be managed and storing the data to be managed (step 106) can execute steps C1-C2: Step C1: Send the data to be managed to the terminal device of the first reviewer, so that the first reviewer can perform review processing on the data to be managed.

[0047] After the data management system determines the data to be managed according to the first master data and the first tag information, the data management system sends the determined data to be managed to the terminal device of the first reviewer, so that the first reviewer can perform review processing on the data to be managed, that is, the first reviewer is the person who reviews the data to be managed.

[0048] Specifically, the number of first reviewers can be one or more. When the number of first reviewers is more than one, the review order of each first reviewer can be determined first (for example, first reviewed by the first-level reviewer, and then reviewed by the second-level reviewer after the first-level reviewer's review is passed), and then the data to be managed is reviewed according to the preset review order.

[0049] More specifically, in a data management system, the division of roles and responsibilities is crucial for ensuring data security, integrity, and efficient management. Role configuration can be maintained through a page to achieve more refined permission management. The following are common roles and their responsibilities in the data management system: Ordinary users can log in to the system to view the main data center page and basic menus, and can also perform operations such as creating and submitting application forms; The operator is the first person in each department to handle an application form during the process of each application form's transfer, and is the person responsible for the initial review of the application form; The first-level review is the person in each department who conducts a re-review of the approval form after the initial review is passed; The second-level review is the person in each department who conducts the final approval of the approval form after the re-review is passed.

[0050] Step C2: After the first reviewer determines that the data to be managed passes the review, store the data to be managed.

[0051] After sending the data to be managed to the first reviewer and the first reviewer determines that the data to be managed passes the review, the data management system stores the data to be managed that is determined to have passed the review.

[0052] That is to say, when the first person applies to add main data domain information, an application needs to be submitted and determined by the reviewer. Specifically, the first person first needs to submit application form information, add the main data domain information to be added, and then submit it for processing. Through process management, after the approval is passed, the main data information is successfully added. The approval process for adding main data domains and main data can be dynamically adjusted according to different business scenarios; If the department in need of data maintenance and the management department are the same department, then the approval process does not require internal review by the department in need; For special main data domains and main data, the special main data process is initiated by the provincial company and can pass through internal review.

[0053] Receiving the management instruction sent by the second person for the data to be managed to perform data management on the data to be managed based on the management instruction (step 108) can execute steps C3 - C4: Step C3: Send the management instruction to the terminal device of the second reviewer so that the second reviewer can review and process the management operations included in the management instruction.

[0054] After the data management system receives the management instruction sent by the second person for the data to be managed, the data management system sends the received management instruction to the terminal device of the second reviewer so that the second reviewer can review and process the management operations included in the management instruction, that is, the second reviewer is the person who reviews the management operations. Among them, the first reviewer and the second reviewer can be the same person or not the same person.

[0055] Step C4: After the second reviewer determines that the management operation has passed the review, perform data management on the data to be managed based on the management operation included in the management instruction.

[0056] After sending the management operation corresponding to the management instruction to the second reviewer and the second reviewer determines that the management operation corresponding to the management instruction has passed the review, the data management system performs data management on the data to be managed based on the management operation included in the management instruction.

[0057] Figure 3 It is a schematic flowchart of the second data management method provided by an embodiment of this specification. As Figure 3 shown, the schematic diagram includes: Step 302: Obtain a plurality of preset master data domain information and label template information corresponding to each of the master data domain information.

[0058] Among them, the master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information.

[0059] Step 304: Obtain the first identity identifier of the first person, and determine whether the first person has data storage permission based on the first identity identifier.

[0060] Step 306: If so, receive the first master data and the first label information sent by the first person.

[0061] Among them, the first master data is the master data that needs to be managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data.

[0062] Step 308: Determine the first master data and the first label information as the data to be managed, and send the data to be managed to the terminal device of the first reviewer, so that the first reviewer performs review processing on the data to be managed.

[0063] Step 310: After the first reviewer determines that the data to be managed has passed the review, store the data to be managed.

[0064] Step 312: Obtain the second identity identifier of the second person, and determine whether the second person has data management permission based on the second identity identifier.

[0065] Step 314: If so, receive the data change request sent by the second person for the data to be managed.

[0066] Among them, the data change request is used to request a change to the data to be managed.

[0067] Step 316: Send the data change request to the terminal device of the second reviewer, so that the second reviewer can review and process the data change operation included in the data change request.

[0068] Step 318: After the second reviewer determines that the data change operation is approved, change the data to be managed based on the data change request, so as to manage the data to be managed.

[0069] In this embodiment, by presetting a plurality of master data domain information and label template information corresponding to each master data information, the master data can be classified and standardized, ensuring that the same type of data has a consistent format and definition; through the first reviewer and the second reviewer to review the data to be managed, during the classification process, the data can be verified and cleaned, incorrect values can be corrected, and the accuracy of the data can be improved.

[0070] In one implementation manner, after determining the first master data and the first label information as the data to be managed (step 106), steps D1 - D3 may further be executed: Step D1: Obtain the second master data and the second label information in the first database.

[0071] The first database is a database for storing master data that needs to be managed. The second master data is the master data that has been stored and needs to be managed. The second label information is determined based on the label template information corresponding to the second domain information, and the second domain information is the master data domain information determined based on the data characteristics of the second master data.

[0072] The data management system obtains the second master data and the second label information prestored in the first database. Among them, the first database is a database for storing master data that needs to be managed. The second master data is the master data that has been stored in the first database and needs to be managed. The second label information is the label information corresponding to the second master data and determined based on the label template information corresponding to the second domain information. The second domain information is the master data domain information determined based on the data characteristics of the second master data. That is to say, the second master data is the master data that needs to be stored and has been stored in the database, and the second label information is the label information corresponding to the master data and stored in the database.

[0073] Step D2: Determine the third label information from the first database based on the first label information.

[0074] The third tag information is the second tag information whose similarity to the first tag information is greater than a preset threshold.

[0075] After obtaining the second master data and the second tag information in the first database, the data management system determines the third tag information from the second tag information in the first database based on the first tag information, where the third tag information is the second tag information whose similarity to the first tag information in the second tag information is greater than a preset threshold.

[0076] That is to say, the data management system determines the similarity between the first tag information and each second tag information, and then determines that the second tag information with a similarity greater than the preset threshold is the third tag information. Further, the number of second tag information that meets the preset conditions may be one or multiple. When the number of second tag information that meets the preset conditions is one, the data management system can directly determine this second tag information as the third tag information. The data management system can also, when the number of second tag information that meets the preset conditions is multiple, sort them in descending order of similarity values, and determine the first preset number (such as two or three) of second tag information before sorting as the third tag information.

[0077] Step D3: Determine the second master data corresponding to the third tag information as associated data.

[0078] Wherein, the associated data is the master data having an association relationship with the first master data.

[0079] After determining the third tag information, the data management system can determine the second master data corresponding to the third tag information as associated data, where the associated data is used to represent the master data having an association relationship with the first master data.

[0080] Specifically, the data management system can determine the second master data corresponding to the second tag information whose similarity to the first tag information is greater than a preset threshold as associated data, that is, determine the second master data corresponding to the second tag information whose similarity to the first tag information is greater than a preset threshold as the data related to or having an association relationship with the first master data.

[0081] More specifically, after the data management system determines that the second master data corresponding to the first master data and the third tag information is data with an associated relationship, the data association system can set the associated relationship and display it to the second person, so that the second person can determine the data associated with the second master data based on the associated relationship, that is, the associated relationship is used to represent the master data associated with the first master data. After determining the associated data of the first master data, the management system can set an associated foreign key in the first master data, and the associated foreign key is used to establish a connection between the first master data domain and the associated data, so that the second person can determine the relevant information of the data (i.e., the associated data) related to the first master data based on the associated foreign key.

[0082] Furthermore, the data management system can not only determine that the second master data with a similarity greater than a preset threshold to the first master data is associated data, but also determine the similarity between each master data domain information and determine two master data with a similarity exceeding the preset threshold as data domains with an associated relationship. Among them, the preset threshold can be the same as or different from the preset threshold when determining the associated data. After determining two data domains with an associated relationship (i.e., associated data domains), the data management system sets foreign key information in each associated data domain, and the foreign key information can be used to connect to another associated data domain. The second person can manage another associated data domain through the foreign key information. For example, the domain information included in the general code table and the general code insurance type comparison table domain establish a close associated relationship through product insurance type related data. A foreign key is set in the general code insurance type comparison table domain, pointing to the corresponding entry in the general code table. In this way, when the second person queries insurance type information, they can quickly associate with the standard data item in the general code table through the foreign key.

[0083] In one implementation, steps E1 - E2 can also be executed: Step E1: Receive a tag change request sent by a third person.

[0084] Among them, the tag change request is used to request the data management system to change the tag template information.

[0085] The data management system can also receive a tag change request sent by a third person. Among them, the third person can be the same person as the first person or the second person, or not the same person. The tag change request is used to request the data management system to change the data tag template corresponding to each master data domain information.

[0086] That is to say, when the third person needs to modify the tag template information corresponding to any master data domain information, they can generate a tag change request and send the generated tag change request to the data management system to request the data management system to change the tag template information.

[0087] Step E2: Modify the label template information based on the label change request, so that the first person can determine the first label information based on the modified label template information.

[0088] After receiving the label change request sent by the third person, the data management system can modify the label template information based on the label change request, so that the first person can determine the first label information based on the modified label template information.

[0089] Furthermore, after receiving the label change request sent by the third person, the data management system can obtain the third identity identifier of the third person, and then authenticate the third person based on the third identity identifier to verify whether the third person has the permission to modify the label template information. Furthermore, after determining that the third person has the permission to modify the label template information, the data management system can modify the label template information based on the label change request.

[0090] Specifically, after modifying the label template information, the first person can determine the label information of the first master data (i.e., the first label information) based on the modified label template information, so that the label information of the master data can be determined according to the real-time situation, ensuring that the data management system can manage the first master data according to the updated first label information, improving the accuracy and convenience of master data management.

[0091] Figure 4 It is a schematic flowchart of the third data management method provided by the embodiments of the present application. As Figure 4 shown, the schematic diagram includes: Step 402: Obtain a plurality of preset master data domain information and the label template information corresponding to each master data domain information.

[0092] Among them, the master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each master data domain information.

[0093] Step 404: Receive the first master data and the first label information sent by the first person.

[0094] Among them, the first master data is the master data that needs to be managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data.

[0095] Step 406: Determine the first master data and the first label information as the data to be managed, and store the data to be managed.

[0096] Step 408: Obtain the second master data and the second tag information in the first database.

[0097] Among them, the first database is a database storing the master data that needs to be managed, the second master data is the stored master data that needs to be managed, the second tag information is determined based on the tag template information corresponding to the second domain information, and the second domain information is the master data domain information determined based on the data characteristics of the second master data.

[0098] Step 410: Determine the third tag information from the first database based on the first tag information.

[0099] Among them, the third tag information is the second tag information whose similarity to the first tag information is greater than a preset threshold.

[0100] Step 412: Determine the second master data corresponding to the third tag information as associated data.

[0101] Among them, the associated data is the master data having an association relationship with the first master data.

[0102] Step 414: Receive a management instruction sent by a second person for the data to be managed, and perform data management on the data to be managed based on the management instruction.

[0103] Step 416: Receive a tag change request sent by a third person.

[0104] Among them, the tag change request is used to request the data management system to change the tag template information.

[0105] Step 418: Change the tag template information based on the tag change request, so that the first person determines the first tag information based on the changed tag template information.

[0106] In the embodiments of the specification, by presetting the second master data and the second tag information, after receiving the first master data and the first tag information sent by the first user, the associated data of the first master data can be determined by determining the second tag information whose similarity to the first tag information is greater than a preset threshold, which can facilitate the second user to manage the similar data of the first master data. By receiving the tag change request sent by the third person and changing the tag template information according to the tag change request, the tag template information corresponding to each master data domain information can be continuously updated according to the actual situation, so that the first user determines the first tag information based on the continuously updated tag template information, improving the timeliness and accuracy of the determined first tag information.

[0107] In one implementation, steps F1 - F2 may also be executed: Step F1: Receive a data acquisition request sent by the first system.

[0108] Wherein, the data acquisition request is used to request the data management system to send the data to be managed to the first system.

[0109] The data management system can also receive a data acquisition request sent by the first system. Here, the first system is an external system that can obtain the data to be managed stored in the data management system and display it to the user. The data acquisition request is a request sent by the first system to request the data management system to send the data to be managed to the first system.

[0110] That is to say, when the user in the first system needs to obtain the data to be managed in the data management system, the user can send a data acquisition request to the data management system through the first system to request the data management system to send the data to be managed to the first system, so that the first system can display the obtained data to be managed to the user.

[0111] Step F2: Send the data to be managed to the first system so that the first system can display the data to be managed.

[0112] After the data management system receives the data acquisition request sent by the first system, the data management system sends the data to be managed to the first system so that the first system can display the data to be managed.

[0113] Specifically, the data management system can support the message queue method to enable the surrounding systems to obtain the data related to the master data domain. Through mq and kafka, it can not only undertake a large number of traffic requests but also improve the stability of this system. It improves the speed at which the third-party system (i.e., the first system) obtains data. This data management system also supports providing interfaces externally. After the third-party system (i.e., the first system) applies for using the interface through the page, the administrator will conduct an approval. If the approval is passed, the third-party system (i.e., the first system) can obtain data by calling the externally provided interface. The interfaces of the data management system support multiple request and response modes, supporting both json and xml formats, ensuring the consistency and unity of the same data used by other third parties.

[0114] Figure 5 It is a schematic flow diagram of the fourth data management method provided by an embodiment of this specification. As Figure 5 shown, this schematic diagram includes: Step 502: Obtain a preset plurality of master data domain information and the label template information corresponding to each of the master data domain information.

[0115] Among them, the master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information.

[0116] Step 504: Receive the first master data and the first label information sent by the first person.

[0117] Among them, the first master data is the master data that needs to be managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data.

[0118] Step 506: Determine the first master data and the first label information as the data to be managed, and store the data to be managed.

[0119] Step 508: Receive the management instruction sent by the second person for the data to be managed, so as to perform data management on the data to be managed based on the management instruction.

[0120] Step 510: Receive the data acquisition request sent by the first system.

[0121] Among them, the data acquisition request is used to request the data management system to send the data to be managed to the first system.

[0122] Step 512: Send the data to be managed to the first system, so that the first system can display the data to be managed.

[0123] In this embodiment, by receiving the data acquisition request sent by the first system, the data to be managed is sent to the first system, so that the user can not only perform data management on the data to be managed through the data management system, but also perform browsing and management operations on the data to be managed through a preset other system.

[0124] It should be noted that for the data management method provided in the embodiment of the present application, the execution subject may be a data management device, or a control module in the data management device for executing the data management method. In the embodiment of the present application, taking the data management device executing the data management method as an example, the data management device provided in the embodiment of the present application is described.

[0125] Figure 6 is a schematic structural diagram of a data management device according to an embodiment of the present invention. As Figure 6 shown, the data management device includes: a first acquisition module 602, a first reception module 604, a first storage module 606, and a first management module 608.

[0126] The first acquisition module 602 is configured to acquire a plurality of preset master data domain information and label template information corresponding to each of the master data domain information. The master data domain information is used to represent the set information of master data with the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information.

[0127] The first receiving module 604 is configured to receive first master data and first label information sent by a first person. The first master data is the master data to be managed, and the first label information is determined based on the label template information corresponding to the first domain information. The first domain information is the master data domain information determined based on the data characteristics of the first master data.

[0128] The first storage module 606 is configured to determine the first master data and the first label information as data to be managed, and store the data to be managed.

[0129] The first management module 608 is configured to receive a management instruction sent by a second person for the data to be managed, and perform data management on the data to be managed based on the management instruction.

[0130] The data management device in the embodiments of the present application may be a device, or a component, an integrated circuit, or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a handheld computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc. The embodiments of the present application do not make specific limitations.

[0131] The data management device in the embodiments of the present application may be a device with an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems. The embodiments of the present application do not make specific limitations.

[0132] The data management device provided in the embodiments of the present application can implement Figures 1 to 5 each process implemented in the method embodiments. To avoid repetition, it will not be described in detail here.

[0133] Based on the same inventive concept, an embodiment of the present application further provides an electronic device, which is used to execute the above data management method. Figure 7 FIG. Figure 7 is a schematic structural diagram of an electronic device for implementing various embodiments of the present application. The electronic device may vary greatly due to configuration or performance differences, and may include a processor 702, a communication interface 704, a memory 706, and a communication bus 708. Among them, the processor 702, the communication interface 704, and the memory 706 communicate with each other through the communication bus 708. The processor 702 can call a computer program stored in the memory 706 and executable on the processor 702 to perform the following steps: In one implementation, receiving a management instruction sent by a second person for the data to be managed, and performing data management on the data to be managed based on the management instruction includes: Receiving a data change request sent by the second person for the data to be managed, where the data change request is used to request to change the data to be managed; Changing the data to be managed based on the data change request to perform data management on the data to be managed.

[0134] In one implementation, before receiving the first main data and the first tag information sent by the first person, the method further includes: Obtaining a first identity identifier of the first person, and determining whether the first person has data storage permission based on the first identity identifier; If so, receiving the first main data and the first tag information sent by the first person; Before receiving the management instruction sent by the second person for the data to be managed, the method further includes: Obtaining a second identity identifier of the second person, and determining whether the second person has data management permission based on the second identity identifier; If so, receiving the management instruction sent by the second person for the data to be managed.

[0135] In one implementation, determining the first main data and the first tag information as the data to be managed, and storing the data to be managed includes: Sending the data to be managed to the terminal device of the first reviewer, so that the first reviewer performs a review process on the data to be managed; After the first reviewer determines that the data to be managed passes the review, storing the data to be managed; Receiving a management instruction sent by a second person for the data to be managed, and performing data management on the data to be managed based on the management instruction, including: Sending the management instruction to the terminal device of a second reviewer, so that the second reviewer reviews the management operation included in the management instruction; After the second reviewer determines that the management operation passes the review, performing data management on the data to be managed based on the management operation included in the management instruction.

[0136] In one implementation, after determining the first master data and the first tag information as the data to be managed, the method further includes: Obtaining second master data and second tag information in a first database, where the first database is a database storing master data that needs to be managed, the second master data is the master data that has been stored and needs to be managed, the second tag information is determined based on tag template information corresponding to second domain information, and the second domain information is the master data domain information determined based on the data characteristics of the second master data; Determining third tag information from the first database based on the first tag information, where the third tag information is the second tag information whose similarity to the first tag information is greater than a preset threshold; Determining the second master data corresponding to the third tag information as associated data, where the associated data is the master data having an association relationship with the first master data.

[0137] In one implementation, the method further includes: Receiving a tag change request sent by a third person, where the tag change request is used to request the data management system to change the tag template information; Changing the tag template information based on the tag change request, so that the first person determines the first tag information based on the changed tag template information.

[0138] In one implementation, the method further includes: Receiving a data acquisition request sent by a first system, where the data acquisition request is used to request the data management system to send the data to be managed to the first system; Sending the data to be managed to the first system, so that the first system displays the data to be managed.

[0139] The above structure of the electronic device does not limit the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements. For example, the input unit may include a Graphics Processing Unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit includes at least one of a touch panel and other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, which will not be elaborated here.

[0140] The memory can be used to store software programs and various data. The memory mainly includes a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area can store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory can include volatile memory or non-volatile memory, or the memory can include both volatile and non-volatile memory. Among them, the non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM) and a Direct Rambus RAM (DRRAM).

[0141] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor may not be integrated into the processor either.

[0142] The embodiments of the present application further provide a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor, it implements each process of the above-mentioned data management method embodiment and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0143] Among them, the processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc, etc.

[0144] The embodiments of the present application further provide a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement each process of the above-mentioned data management method embodiment and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0145] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system chip, a chip system, or a system-on-chip, etc.

[0146] It should be noted that in this article, the term "including", "comprising", or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article, or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article, or device. Without more limitations, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article, or device including that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be executed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, the features described with reference to certain examples may be combined in other examples.

[0147] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of the present application.

[0148] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific implementation manners. The above specific implementation manners are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them belong to the protection scope of the present application.

Claims

1. A data management method, applied to a data management system, comprising: Acquire a plurality of preset master data domain information and label template information corresponding to each of the master data domain information, wherein the master data domain information is used to represent the collection information of master data having the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information; receiving first master data and first label information sent by a first person, wherein the first master data is master data to be managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on data features of the first master data; Determine the first master data and the first tag information as data to be managed, and store the data to be managed; A management instruction sent by a second person for the data to be managed is received, so as to perform data management on the data to be managed based on the management instruction.

2. The method according to claim 1, wherein receiving a management instruction sent by a second person for the data to be managed, so as to perform data management on the data to be managed based on the management instruction, comprises: receiving a data change request sent by the second person for the data to be managed, wherein the data change request is used to request to change the data to be managed; The data to be managed is modified based on the data modification request to perform data management on the data to be managed.

3. The method according to claim 1, before receiving the first master data and the first tag information sent by the first person, the method further comprises: Obtaining a first identity identifier of the first person, and determining whether the first person has data storage permission based on the first identity identifier; If yes, receiving the first master data and the first tag information sent by the first person; Before receiving the management instruction sent by the second person for the data to be managed, the method further includes: Obtaining a second identity identifier of the second person, and determining whether the second person has data management authority based on the second identity identifier; If so, receiving a management instruction sent by the second person for the data to be managed.

4. The method according to claim 1, wherein determining the first master data and the first tag information as data to be managed and storing the data to be managed comprises: Sending the data to be managed to a terminal device of a first auditor, so that the first auditor can perform an audit on the data to be managed; After the first reviewer determines that the data to be managed has passed the review, the data to be managed is stored; The receiving a management instruction sent by a second person for the data to be managed, so as to perform data management on the data to be managed based on the management instruction, includes: Sending the management instruction to a terminal device of a second auditor, so that the second auditor can audit the management operation included in the management instruction; After the second auditor determines that the management operation is approved, data management is performed on the data to be managed based on the management operation included in the management instruction.

5. The method according to claim 1, after determining the first master data and the first tag information as data to be managed, the method further comprises: Acquire second master data and second label information in a first database, wherein the first database is a database storing master data to be managed, the second master data is stored master data to be managed, the second label information is determined based on label template information corresponding to second domain information, and the second domain information is the master data domain information determined based on data features of the second master data; Determine third label information from the first database based on the first label information, where the third label information is the second label information whose similarity with the first label information is greater than a preset threshold; It is determined that the second main data corresponding to the third tag information is associated data, and the associated data is main data that has an associated relationship with the first main data.

6. The method according to claim 1, further comprising: Receiving a label change request sent by a third person, wherein the label change request is used to request the data management system to change the label template information; The label template information is changed based on the label change request, so that the first person determines the first label information based on the changed label template information.

7. The method according to claim 1, further comprising: receiving a data acquisition request sent by the first system, wherein the data acquisition request is used to request the data management system to send the to-be-managed data to the first system; The data to be managed is sent to the first system, so that the first system displays the data to be managed.

8. A data management device, comprising: A first acquisition module is used to acquire a plurality of preset master data domain information and label template information corresponding to each of the master data domain information, wherein the master data domain information is used to represent the set information of master data having the same characteristics, and the label template information is used to represent the characteristic information of the master data included in each of the master data domain information; A first receiving module is used to receive first master data and first label information sent by a first person, wherein the first master data is master data to be managed, the first label information is determined based on the label template information corresponding to the first domain information, and the first domain information is the master data domain information determined based on the data characteristics of the first master data; A first storage module, configured to determine the first master data and the first tag information as data to be managed, and store the data to be managed; The first management module is used to receive a management instruction sent by a second person for the data to be managed, so as to perform data management on the data to be managed based on the management instruction.

9. A computer device, characterized in that: The device comprises: Processor; and A memory arranged to store computer executable instructions, the executable instructions being configured to be executed by the processor, the executable instructions comprising instructions for performing the steps in the method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is used to store computer-executable instructions, and the executable instructions enable a computer to execute the method according to any one of claims 1 to 7.

Images