Data management method and device, computer equipment and storage medium

Abstract

The invention discloses a data management method and device, computer equipment and a storage medium, and the method comprises the steps: obtaining to-be-managed dimension data which comprises a to-be-managed dimension name and a corresponding to-be-managed dimension value name, carrying out the feature analysis of the to-be-managed dimension data, determining a feature tag to which the to-be-managed dimension data belongs, and storing the feature tag to the to-be-managed dimension data; according to a coding rule corresponding to the feature tag, coding the to-be-managed dimension name to obtain a standard dimension code, according to the coding rule and the standard dimension code, coding the to-be-managed dimension name to obtain a standard dimension code, and mapping the to-be-managed dimension name and the standard dimension code to obtain a standard dimension code; the to-be-managed dimension value name and the standard dimension value code are mapped to obtain a management mapping table, and the management mapping table is used for conducting standard code management on the to-be-managed dimension value name and the to-be-managed dimension value name. And effective management and standardization of the dimension data are realized.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a data management method, device, computer equipment and storage medium. Background Art

[0002] With the development of big data technology, enterprises often need to analyze massive data to adapt to development trends, extract valuable information from it, and formulate and adjust corresponding development strategies accordingly. The angle used to analyze data is the dimension, which represents a certain attribute or feature of the data. The specific value or instance on the dimension is the dimension value of the corresponding dimension. For example, in the insurance field, the dimensions of insurance data analysis can include insurance product type, risk level and employee type, etc. The dimension values ​​under the corresponding dimension can be life insurance, low risk and customer service personnel, etc. However, in the process of dimension management and actual use, many problems are often encountered. For example, in the same dimension category, the same dimension value name may correspond to multiple dimension names and dimension codes, and the same dimension value name may correspond to multiple different dimension value codes. This may cause ambiguity when retrieving data, so that the correct dimension information cannot be accurately located, and when integrating data, the data may not be accurately matched, thus affecting the quality of data integration.

[0003] Therefore, how to effectively manage and standardize dimensional data has become an urgent problem to be solved. Summary of the invention

[0004] Based on this, a data management method, apparatus, computer device and storage medium are provided to solve the problem of how to effectively manage and standardize dimensional information.

[0005] In a first aspect, an embodiment of the present invention provides a data management method, including: Acquire the dimension data to be managed, wherein the dimension data to be managed includes the dimension name to be managed and the corresponding dimension value name to be managed; Performing feature analysis on the dimension data to be managed to determine feature tags to which the dimension data to be managed belongs; According to the encoding rule corresponding to the feature tag, the name of the dimension to be managed is encoded to obtain a standard dimension code, and according to the encoding rule and the standard dimension code, the name of the dimension value to be managed is encoded to obtain a standard dimension value code; The dimension name to be managed is mapped with the standard dimension code, and the dimension value name to be managed is mapped with the standard dimension value code to obtain a management mapping table, which is used to perform standard coding management on the dimension name to be managed and the dimension value name to be managed.

[0006] In a second aspect, an embodiment of the present invention provides a data management device, including: A data acquisition module, used to acquire dimension data to be managed, wherein the dimension data to be managed includes a name of the dimension to be managed and a corresponding name of the dimension value to be managed; A feature analysis module, used to perform feature analysis on the dimension data to be managed, and determine feature tags to which the dimension data to be managed belongs; An encoding module, used to encode the name of the dimension to be managed according to the encoding rule corresponding to the feature tag to obtain a standard dimension code, and to encode the name of the dimension value to be managed according to the encoding rule and the standard dimension code to obtain a standard dimension value code; The first management module is used to map the dimension name to be managed with the standard dimension code, and to map the dimension value name to be managed with the standard dimension value code to obtain a management mapping table, and the management mapping table is used to perform standard coding management on the dimension name to be managed and the dimension value name to be managed.

[0007] In a third aspect, an embodiment of the present invention provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the data management method of the first aspect when executing the computer program.

[0008] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the data management method of the first aspect is implemented.

[0009] The technical effect achieved by the present invention is different from that of the prior art solutions: the present invention obtains the dimension data to be managed, the dimension data to be managed includes the dimension name to be managed and the corresponding dimension value name to be managed, performs feature analysis on the dimension data to be managed, determines the feature label to which the dimension data to be managed belongs, encodes the dimension name to be managed according to the encoding rule corresponding to the feature label to obtain a standard dimension code, encodes the dimension value name to be managed according to the encoding rule and the standard dimension code to obtain a standard dimension value code, maps the dimension name to be managed with the standard dimension code, and maps the dimension value name to be managed with the standard dimension value code to obtain a management mapping table, and the management mapping table is used to perform standard encoding management on the dimension name to be managed and the dimension value name to be managed.

[0010] Among them, by uniformly encoding the dimension value of the management dimension data, a standard dimension value encoding is obtained, and a management mapping table is obtained based on the standard dimension value encoding. Based on the management mapping table, the dimension data can be effectively managed and standardized, so that when data exchange, data sharing and data integration are carried out between different systems, platforms and tools, related operations can be performed directly based on the management mapping table, avoiding the risk of data loss or errors caused by incompatible data formats, enhancing data compatibility and interoperability, and improving data processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0012] Figure 1 This is a schematic diagram of an application environment of a data management method provided by Embodiment 1 of the present invention; Figure 2 is a flow chart of a data management method provided in Embodiment 2 of the present invention; Figure 3 is a flowchart of a data management method provided in Embodiment 3 of the present invention; Figure 4 is a flowchart of a data management method provided by Embodiment 4 of the present invention; Figure 5 is a flowchart of a data management method provided in Embodiment 5 of the present invention; Figure 6 is a flowchart of a data management method provided by Embodiment 6 of the present invention; Figure 7 is a flowchart of a data management method provided by Embodiment 7 of the present invention; Figure 8 is a structural diagram of a data management device provided by Embodiment 8 of the present invention; Fig. 9 It is a structural diagram of a computer device provided in Embodiment 9 of the present invention. DETAILED DESCRIPTION

[0013] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0014] It should be understood that the order of execution of the steps in the following embodiments does not imply a precedence of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0015] A data management method provided in the first embodiment of the present invention can be applied in the following aspects: Figure 1 In the application environment, the server communicates with the client, the server provides data management services, and the client triggers data management tasks to the server. The client includes but is not limited to PDAs, desktop computers, laptops, ultra-mobile personal computers (UMPCs), netbooks, cloud computing devices, personal digital assistants (PDAs), and other devices. The computer device corresponding to the server can be implemented with an independent server or a server cluster consisting of multiple servers.

[0016] like Figure 2 FIG. 1 is a flow chart of a data management method provided in Embodiment 2 of the present invention, comprising the following steps: Step S201: Acquire the dimension data to be managed.

[0017] Step S202: performing feature analysis on the dimension data to be managed, and determining feature tags to which the dimension data to be managed belongs.

[0018] In this embodiment, dimension may refer to the angle from which data can be analyzed, which represents a certain attribute or feature of the data. Dimension value may refer to the specific value of the corresponding dimension. The dimensional data to be managed includes the name of the dimension to be managed and the corresponding name of the dimension value to be managed. Feature label may refer to a label representing the application field of the dimensional data to be managed, wherein the feature label can be divided into cross-domain general type and domain-specific type. The cross-domain general type indicates that the dimensional data to be managed is applicable to general business scenarios, and the domain-specific type indicates that the dimensional data to be managed is only applicable to specific business scenarios.

[0019] For example, the names of the dimensions to be managed may be insurance type and employee type, the names of the dimension values ​​to be managed corresponding to the insurance types may be life insurance and health insurance, etc., and the names of the dimension values ​​to be managed corresponding to the employee types may be customer personnel and sales personnel, etc. Then, the feature labels of the dimension data to be managed corresponding to the insurance types, life insurance and health insurance may be domain-specific, which is only applicable to the insurance field, while the feature labels of the dimension data to be managed corresponding to the employee types, customer personnel and sales personnel may be cross-domain general, which can be applicable to a variety of general business scenarios.

[0020] Step S203: Encode the name of the dimension to be managed according to the encoding rule corresponding to the feature tag to obtain a standard dimension code, and encode the name of the dimension value to be managed according to the encoding rule and the standard dimension code to obtain a standard dimension value code.

[0021] In this embodiment, the encoding rule may refer to the pre-set rule for encoding the dimension data to be managed, the standard dimension encoding may refer to the name of the dimension to be managed encoded according to the encoding rule corresponding to the feature tag, and the standard dimension value encoding may refer to the name of the dimension value to be managed encoded according to the encoding rule corresponding to the feature tag.

[0022] Specifically, if the characteristic label of the dimension data to be managed is a cross-domain general type, the corresponding dimension encoding rule is matched based on the dimension code and the cross-domain general type label, and the matched dimension encoding rule is used to encode the name of the dimension to be managed to obtain the standard dimension code, and based on the dimension value code and the cross-domain general type label, the corresponding dimension value encoding rule is matched, and the matched dimension value encoding rule is used to encode the name of the dimension value to be managed to obtain the standard dimension value code.

[0023] Correspondingly, if the feature label of the dimension data to be managed is domain-specific, the corresponding dimension encoding rule is matched based on the dimension code and the domain-specific label, and the matched dimension encoding rule is used to encode the name of the dimension to be managed to obtain the standard dimension code, and the corresponding dimension value encoding rule is matched based on the dimension value code and the domain-specific label, and the matched dimension value encoding rule is used to encode the name of the dimension value to be managed to obtain the standard dimension value code.

[0024] Step S204: Map the name of the dimension to be managed with the standard dimension code, and map the name of the dimension value to be managed with the standard dimension value code to obtain a management mapping table.

[0025] In this embodiment, the management mapping table can be used to perform standard coding management on the names of dimensions to be managed and the names of dimension values ​​to be managed.

[0026] Specifically, a mapping relationship is formed between the name of the dimension to be managed and the standard dimension code, and a mapping relationship is formed between the name of the dimension value to be managed and the standard dimension value code, and the two are written into a pre-created mapping table to obtain a management mapping table.

[0027] In this embodiment, a standard dimension value code is obtained by uniformly encoding the dimension value of the management dimension data, and a management mapping table is obtained based on the standard dimension value code. Based on the management mapping table, the dimension data can be effectively managed and standardized, so that when data is exchanged, shared and integrated between different systems, platforms and tools, related operations can be performed directly based on the management mapping table, avoiding the risk of data loss or errors caused by incompatible data formats, enhancing data compatibility and interoperability, and improving data processing efficiency.

[0028] like Figure 3 As shown, it is a flow chart of a data management method provided by Embodiment 3 of the present invention. In the above step S203, according to the encoding rule corresponding to the feature label, the name of the dimension to be managed is encoded to obtain the standard dimension code, which may include the following steps: Step S301: If the characteristic tag to which the dimension data to be managed belongs is a cross-domain general type, then determine the dimension type code to which the dimension name to be managed belongs, and determine the dimension name code corresponding to the dimension name to be managed.

[0029] Step S302: concatenate the dimension type code and the dimension name code to obtain a standard dimension code.

[0030] In this embodiment, the dimension type code may refer to a preset dimension category code, and the dimension name code may refer to a preset dimension name code.

[0031] For example, the dimensions can be divided into the following categories: location category (Where), content category (What), object category (Who), time category (When), and method category (How). The dimension type codes corresponding to each dimension category and the codes of each dimension name under each dimension category can be: Location (Where): dimensions such as area, organization, channel, country, and school. The dimension type code for this dimension category is we. Content category (What): product (prod), target (tag), sector (sec), insurance type (ply), currency (ccy) and other dimensions. The dimension type code corresponding to this dimension category is wt; Object class (Who): employee type (emp), customer type (cust), competitor (comp), customer group (custg), claims team (claim), etc. The dimension type code corresponding to this dimension category is wo; Time category (When): day, week, month, quarter, year and other dimensions. The dimension type code corresponding to this dimension category is wn. How: statistical method (view), charging model (chg), consumption method (cons), insurance method (insu), etc. The dimension type code corresponding to this dimension category is hw.

[0032] If the name of the dimension to be managed is a statistical method, dimension encoding is performed on it, and the dimension type code HW and the dimension name code VIEW are concatenated, and the obtained standard dimension code may be HW_VIEW.

[0033] In this embodiment, by uniformly encoding the cross-domain universal dimensional data to be managed, a standard dimensional code is obtained, which improves the standardization and uniformity of dimensional data management and facilitates the storage and analysis of dimensional data.

[0034] like Figure 4 As shown, a flow chart of a data management method provided by Embodiment 4 of the present invention is shown. In the above step S203, according to the encoding rule and the standard dimension encoding, the name of the dimension value to be managed is encoded to obtain the standard dimension value encoding, which may include the following steps: Step S401: If the characteristic label to which the dimension data to be managed belongs is a cross-domain general type, a demand analysis is performed on the dimension value name to be managed to determine the analysis level corresponding to the dimension value name to be managed.

[0035] Step S402: concatenate the standard dimension code and the analysis level to obtain a standard dimension value code.

[0036] In this embodiment, the analysis level may refer to the level of the dimension value of the dimension value name to be managed. For a single-level dimension value, pipeline coding may be used. For a multi-level dimension value, the upper-level dimension value includes the lower-level dimension value, and the lower-level dimension value inherits the upper-level dimension value. The number of bits in each level may be reserved based on the evaluation of the number of dimension values. For example, the dimension value name for the location type may be divided into three levels: province, city, and district. Since a province may include a city and a district, and a city may include a district, a province may be divided into the first level, a city may be divided into the second level, and a district may be divided into the third level. The first level may be recorded as 01, the second level may be recorded as 0101, and the third level may be recorded as 010101.

[0037] For example, if the name of the dimension value to be managed is South District, which is the second level, and the standard dimension code of the dimension name to be managed corresponding to South District is WE_AREA, then the standard dimension code WE_AREA and the second level 0101 are concatenated, and the obtained standard dimension value code corresponding to South District can be WE_AREA_0101.

[0038] Optionally, the standard dimension value code may be obtained according to the national standard / industry standard and the standard dimension code corresponding to the dimension data to be managed.

[0039] In this embodiment, by uniformly encoding the cross-domain universal dimension value data to be managed, a standard dimension value code is obtained, thereby improving the standardization and uniformity of dimension value data management and facilitating the storage and analysis of dimension value data.

[0040] like Figure 5 As shown, it is a flowchart of a data management method provided by Embodiment 5 of the present invention. In the above step S203, the name of the dimension to be managed is encoded according to the encoding rule corresponding to the feature label to obtain the standard dimension code, and the following steps may also be included: Step S501: If the feature tag to which the dimension data to be managed belongs is domain-specific, the source information code corresponding to the data to be managed is obtained, and the dimension type code to which the dimension name to be managed belongs and the dimension name code corresponding to the dimension name to be managed are determined.

[0041] Step S502: concatenate the dimension type code, dimension name code and source information code to obtain a standard dimension code.

[0042] In this embodiment, the source information code may refer to a code that identifies the source of the data to be managed.

[0043] For example, in the insurance field, if the name of the dimension to be managed is insurance institution, the source information of the dimension data to be managed may include property insurance and life insurance, etc. The corresponding code for property insurance may be CX, and the code for life insurance may be SX. According to the contents of steps S301 to S302 above, it can be determined that the dimension type code of the insurance institution is WE, and the dimension name code is REGION. If the source information corresponding to the insurance institution is life insurance, the dimension type code WE, the dimension name code REGION and the source information code SX are concatenated, and the corresponding standard dimension code for the insurance institution is WE_SX_REGION.

[0044] In this embodiment, by uniformly encoding the domain-specific dimensional data to be managed, a standard dimensional code is obtained, which improves the standardization and uniformity of dimensional data management and facilitates the storage and analysis of dimensional data.

[0045] like Figure 6As shown, it is a flowchart of a data management method provided by Embodiment 6 of the present invention. In the above step S203, the name of the dimension value to be managed is encoded according to the encoding rule and the standard dimension code to obtain the standard dimension value code, and the following steps may also be included: Step S601: If the feature label to which the dimension data to be managed belongs is domain-specific, then the source dimension value code corresponding to the dimension value name to be managed is obtained.

[0046] Step S602: concatenate the source dimension value code and the standard dimension value code to obtain the standard dimension value code.

[0047] In this embodiment, the source dimension value code may refer to the source code corresponding to the dimension value name to be managed.

[0048] For example, if the name of the dimension value to be managed is life insurance institution, its corresponding source dimension value code is sx01. According to the contents in the above steps S501 to S502, it can be determined that the standard dimension code of the insurance institution corresponding to the dimension name to be managed of the life insurance institution is WE_SX_REGION. Then, the source dimension value code sx01 and the standard dimension code WE_SX_REGION are concatenated, and the obtained standard dimension value code corresponding to the life insurance institution is WE_SX_REGION_sx0.

[0049] In this embodiment, by uniformly encoding the domain-specific dimensional value data to be managed, a standard dimensional value code is obtained, thereby improving the standardization and uniformity of dimensional value data management and facilitating the storage and analysis of dimensional value data.

[0050] like Figure 7 FIG. 1 is a flow chart of a data management method provided in Embodiment 7 of the present invention. The data management method may further include the following steps: Step S701: Acquire the data set to be managed.

[0051] Step S702: Determine the standard dimension name corresponding to the dimension name to be managed of each dimension data to be managed in the data set to be managed, and the standard dimension value name corresponding to the dimension value name to be managed.

[0052] Step S703: Map the name of the dimension to be managed, the name of the standard dimension and the standard dimension code, and map the name of the dimension value to be managed, the name of the standard dimension value and the standard dimension value code to obtain a management mapping table.

[0053] In this embodiment, the data set to be managed includes N dimension data to be managed, where N is an integer greater than 1, the standard dimension name may refer to a preset standard dimension name, and the standard dimension value name may refer to a preset standard dimension value name.

[0054] Specifically, determine the standard dimension name corresponding to the dimension name to be managed of each dimension data to be managed in the data set to be managed, as well as the standard dimension value name corresponding to the dimension value name to be managed. For any standard dimension name, if it corresponds to a single dimension name to be managed, the dimension name to be managed, the standard dimension name and the standard dimension code are directly mapped to form a relationship. Accordingly, for any standard dimension value name, if it corresponds to a single dimension value name to be managed, the dimension value name to be managed, the standard dimension value name and the standard dimension value code are directly mapped to form a relationship.

[0055] For any standard dimension name, if it corresponds to multiple dimension names to be managed, then all dimension names to be managed with the same standard dimension name in the data set to be managed will form a dimension set to be managed, and the dimension set to be managed, standard dimension names and standard dimension codes will form a mapping relationship. Correspondingly, for any standard dimension value name, if it corresponds to multiple dimension value names to be managed, then all dimension value names to be managed with the same standard dimension value name in the data set to be managed will form a dimension value set to be managed, and the dimension value set to be managed, standard dimension value names and standard dimension value codes will form a mapping relationship.

[0056] For example, if there are three dimension data to be managed in the data set to be managed, the dimension data to be managed can be (1) dimension name to be managed: statistical frequency, dimension value name to be managed: monthly accumulation; (2) dimension name to be managed: statistical method, dimension value name to be managed: monthly accumulation; (3) dimension name to be managed: statistical type, dimension value name to be managed: annual accumulation. If the statistical method is the standard dimension name, and the monthly accumulation and annual accumulation are the standard dimension value names, then the statistical frequency, statistical method and statistical type of the dimension names to be managed in (1), (2) and (3) are formed into a dimension set to be managed, the monthly accumulation and monthly accumulation of the dimension value names to be managed in (1) and (2) are formed into a dimension value set to be managed, the dimension set to be managed, the standard dimension name (statistical method) and the standard dimension code are formed into a mapping relationship, and the dimension value set to be managed, the standard dimension value name (monthly accumulation, annual accumulation) and the standard dimension code are formed into a mapping relationship, and the management mapping table is obtained.

[0057] In this embodiment, a management mapping table is obtained according to the standard dimension value coding. Based on the management mapping table, the dimensional data can be effectively managed and standardized, so that when data exchange, data sharing and data integration are performed between different systems, platforms and tools, relevant operations can be performed directly based on the management mapping table, avoiding the risk of data loss or errors caused by incompatible data formats, enhancing data compatibility and interoperability, and improving data processing efficiency.

[0058] like Figure 8As shown, a data management device provided in Embodiment 8 of the present invention is provided, and the data management device corresponds to the data management method in the above embodiment. The data management device includes a data acquisition module 81, a feature analysis module 82, an encoding module 83 and a first management module 84. Each functional module is described in detail as follows: The data acquisition module 81 is used to acquire the dimension data to be managed, wherein the dimension data to be managed includes the name of the dimension to be managed and the name of the corresponding dimension value to be managed; A feature analysis module 82 is used to perform feature analysis on the dimension data to be managed, and determine feature tags to which the dimension data to be managed belongs; The encoding module 83 is used to encode the name of the dimension to be managed according to the encoding rule corresponding to the feature tag to obtain a standard dimension code, and to encode the name of the dimension value to be managed according to the encoding rule and the standard dimension code to obtain a standard dimension value code; The first management module 84 is used to map the dimension name to be managed with the standard dimension code, and to map the dimension value name to be managed with the standard dimension value code to obtain a management mapping table, and the management mapping table is used to perform standard coding management on the dimension name to be managed and the dimension value name to be managed.

[0059] Optionally, the encoding module 83 includes: A first determining unit is used to determine the dimension type code to which the dimension name to be managed belongs, and determine the dimension name code corresponding to the dimension name to be managed if the feature tag to which the dimension data to be managed belongs is a cross-domain general type; The first code forming unit is used to concatenate the dimension type code and the dimension name code to obtain the standard dimension code.

[0060] Optionally, the encoding module 83 includes: A second determining unit is configured to perform a demand analysis on the name of the dimension value to be managed and determine an analysis level corresponding to the name of the dimension value to be managed if the characteristic tag to which the dimension data to be managed belongs is the cross-domain general type; The second code forming unit is used to concatenate the standard dimension code and the analysis level to obtain the standard dimension value code.

[0061] Optionally, the encoding module 83 further includes: A third determining unit is used for obtaining a source information code corresponding to the data to be managed if the feature tag to which the dimension data to be managed belongs is domain-specific, and determining a dimension type code to which the dimension name to be managed belongs and a dimension name code corresponding to the dimension name to be managed; The third code forming unit is used to concatenate the dimension type code, the dimension name code and the source information code to obtain the standard dimension code.

[0062] Optionally, the encoding module 83 further includes: A fourth determining unit is used to obtain a source dimension value code corresponding to the name of the dimension value to be managed if the feature label to which the dimension data to be managed belongs is the domain-specific type; The fourth code forming unit is used to concatenate the source dimension value code and the standard dimension code to obtain the standard dimension value code.

[0063] Optionally, the data management device further includes: A data set acquisition module, used to acquire a data set to be managed, wherein the data set to be managed includes N dimensional data to be managed, where N is an integer greater than 1; A fifth determining module, used to determine the standard dimension name corresponding to the to-be-managed dimension name of each to-be-managed dimension data in the to-be-managed data set, and the standard dimension value name corresponding to the to-be-managed dimension value name; The second management module is used to map the name of the dimension to be managed, the name of the standard dimension and the standard dimension code, and to map the name of the dimension value to be managed, the name of the standard dimension value and the standard dimension value code to obtain the management mapping table.

[0064] Optionally, the second management module includes: a forming unit, configured to form a dimension set to be managed by forming all dimension names to be managed that have the same standard dimension name in the data set to be managed, and to form a dimension value set to be managed by forming all dimension value names to be managed that have the same standard dimension value name in the data set to be managed; A mapping unit is used to map the dimension set to be managed, the standard dimension name and the standard dimension code, and to map the dimension value set to be managed, the standard dimension value name and the standard dimension value code to obtain the management mapping table.

[0065] For the specific definition of the data management device, please refer to the definition of the data management method above, which will not be repeated here. Each module in the above data management device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0066] Fig. 9 This is a schematic diagram of the structure of a computer device provided in Embodiment 9 of the present invention. Fig. 9As shown, the computer device of this embodiment includes: at least one processor ( Fig. 9 Only one is shown in the figure), a memory, and a computer program stored in the memory and executable on at least one processor, wherein when the processor executes the computer program, the steps in any of the above-mentioned data management method embodiments are implemented.

[0067] The computer device may include, but is not limited to, a processor and a memory. Those skilled in the art will appreciate that Fig. 9 This is merely an example of a computer device and does not constitute a limitation on the computer device. The computer device may include more or fewer components than those shown in the figure, or a combination of certain components, or different components. For example, it may also include a network interface, a display screen, and an input device.

[0068] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0069] The memory includes a readable storage medium, an internal memory, etc., wherein the internal memory may be the memory of a computer device, and the internal memory provides an environment for the operation of the operating system and computer-readable instructions in the readable storage medium. The readable storage medium may be a hard disk of a computer device, and in other embodiments, it may also be an external storage device of the computer device, for example, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the computer device. Further, the memory may also include both an internal storage unit of the computer device and an external storage device. The memory is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of a computer program, etc. The memory may also be used to temporarily store data that has been output or is to be output.

[0070] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention. The specific working process of the units and modules in the above-mentioned device can refer to the corresponding process in the above-mentioned method embodiment, which will not be repeated here. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned method embodiment can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device capable of carrying computer program code, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0071] The present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by a computer program product. When the computer program product runs on a computer device, the computer device can implement the steps in the above-mentioned method embodiment when executing.

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

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

[0074] In the embodiments provided by the present invention, it should be understood that the disclosed devices / computer equipment and methods can be implemented in other ways. For example, the device / computer equipment embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0076] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments can still be modified, or some of the technical features can be replaced by equivalents, and these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A data management method, characterized in that: include: Acquire the dimension data to be managed, wherein the dimension data to be managed includes the dimension name to be managed and the corresponding dimension value name to be managed; Performing feature analysis on the dimension data to be managed to determine feature tags to which the dimension data to be managed belongs; According to the encoding rule corresponding to the feature tag, the name of the dimension to be managed is encoded to obtain a standard dimension code, and according to the encoding rule and the standard dimension code, the name of the dimension value to be managed is encoded to obtain a standard dimension value code; The dimension name to be managed is mapped with the standard dimension code, and the dimension value name to be managed is mapped with the standard dimension value code to obtain a management mapping table, which is used to perform standard coding management on the dimension name to be managed and the dimension value name to be managed.

2. The data management method according to claim 1, characterized in that: The step of encoding the dimension name to be managed according to the encoding rule corresponding to the feature tag to obtain a standard dimension code includes: If the characteristic tag to which the dimension data to be managed belongs is a cross-domain general type, determining the dimension type code to which the dimension name to be managed belongs, and determining the dimension name code corresponding to the dimension name to be managed; The dimension type code and the dimension name code are concatenated to obtain the standard dimension code.

3. The data management method according to claim 2, characterized in that: The step of encoding the dimension value name to be managed according to the encoding rule and the standard dimension code to obtain the standard dimension value code includes: If the characteristic tag to which the dimension data to be managed belongs is the cross-domain general type, a demand analysis is performed on the dimension value name to be managed to determine the analysis level corresponding to the dimension value name to be managed; The standard dimension code and the analysis level are concatenated to obtain the standard dimension value code.

4. The data management method according to claim 1, characterized in that: The step of encoding the dimension name to be managed according to the encoding rule corresponding to the feature tag to obtain a standard dimension code further includes: If the feature tag to which the dimension data to be managed belongs is domain-specific, then the source information code corresponding to the data to be managed is obtained, and the dimension type code to which the dimension name to be managed belongs and the dimension name code corresponding to the dimension name to be managed are determined; The dimension type code, the dimension name code and the source information code are concatenated to obtain the standard dimension code.

5. The data management method according to claim 4, characterized in that: The encoding of the dimension value name to be managed according to the encoding rule and the standard dimension code to obtain the standard dimension value code also includes: If the characteristic tag to which the dimension data to be managed belongs is the domain-specific type, then obtaining the source dimension value code corresponding to the dimension value name to be managed; The source dimension value code and the standard dimension code are concatenated to obtain the standard dimension value code.

6. The data management method according to claim 1, characterized in that: The data management method further comprises: Acquire a data set to be managed, wherein the data set to be managed includes N dimensional data to be managed, where N is an integer greater than 1; Determine the standard dimension name corresponding to the dimension name to be managed of each dimension data to be managed in the data set to be managed, and the standard dimension value name corresponding to the dimension value name to be managed; The management mapping table is obtained by mapping the dimension name to be managed, the standard dimension name and the standard dimension code, and mapping the dimension value name to be managed, the standard dimension value name and the standard dimension value code.

7. The data management method according to claim 6, characterized in that: The mapping of the dimension name to be managed, the standard dimension name and the standard dimension code, and mapping the dimension value name to be managed, the standard dimension value name and the standard dimension value code to obtain the management mapping table includes: All the dimension names to be managed that have the same standard dimension names in the data set to be managed form a dimension set to be managed, and all the dimension value names to be managed that have the same standard dimension value names in the data set to be managed form a dimension value set to be managed; The management mapping table is obtained by mapping the dimension set to be managed, the standard dimension name and the standard dimension code, and mapping the dimension value set to be managed, the standard dimension value name and the standard dimension value code.

8. A data management device, characterized in that: include: A data acquisition module, used to acquire dimension data to be managed, wherein the dimension data to be managed includes a name of the dimension to be managed and a corresponding name of the dimension value to be managed; A feature analysis module, used to perform feature analysis on the dimension data to be managed, and determine feature tags to which the dimension data to be managed belongs; An encoding module, used to encode the name of the dimension to be managed according to the encoding rule corresponding to the feature tag to obtain a standard dimension code, and to encode the name of the dimension value to be managed according to the encoding rule and the standard dimension code to obtain a standard dimension value code; The first management module is used to map the dimension name to be managed with the standard dimension code, and to map the dimension value name to be managed with the standard dimension value code to obtain a management mapping table, and the management mapping table is used to perform standard coding management on the dimension name to be managed and the dimension value name to be managed.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the data management method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the data management method according to any one of claims 1 to 7 is implemented.

Images