Data verification method and device, computer equipment, storage medium and program product

Abstract

The invention relates to a data verification method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps that a metadata verification request is received, the metadata verification request comprises a form identifier of a metadata change list, and the metadata change list corresponds to multiple pieces of change metadata; obtaining the change metadata according to the form identifier, and obtaining preset standard metadata; and according to a preset compliance verification rule and the standard metadata, performing compliance verification on each change metadata to obtain a compliance verification result corresponding to the metadata verification request. By adopting the method, the efficiency and accuracy of data management can be improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data verification method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the digital transformation of enterprises, data management has become a key link in the control and management of enterprise project development. During the project development process, metadata, as data describing the data, can explain the meaning, structure, source, and other information of the data, and plays a vital role in data management.

[0003] Traditional metadata management methods rely on manual review and management of metadata, which has problems such as heavy workload, cumbersome information filling, and lagging verification rules, seriously affecting the efficiency and accuracy of data management. Summary of the Invention

[0004] Based on this, it is necessary to provide a data verification method, device, computer equipment, computer-readable storage medium and computer program product that can improve the efficiency and accuracy of data management in order to address the above technical problems.

[0005] In a first aspect, the present application provides a data verification method. The method comprises:

[0006] receiving a metadata verification request, the metadata verification request including a form identifier of a metadata change order, the metadata change order corresponding to a plurality of changed metadata;

[0007] Acquire each of the change metadata according to the form identifier, and acquire preset standard metadata;

[0008] Compliance verification is performed on each of the changed metadata according to preset compliance verification rules and the standard metadata to obtain a compliance verification result corresponding to the metadata verification request.

[0009] In one embodiment, the change metadata includes multiple verification change fields, the compliance verification rules include local verification rules and global verification rules, and the compliance verification is performed on each of the change metadata according to the preset compliance verification rules and the standard metadata to obtain a compliance verification result corresponding to the metadata verification request, including:

[0010] For each of the change metadata, determining, according to the local verification rule, whether there are target change fields identical to the verification change fields in the standard metadata;

[0011] In the case that each target change field exists in the standard metadata, character verification is performed on each verification change field according to the global verification rule and each target change field to obtain a compliance verification result.

[0012] In one embodiment, performing character verification on each verification change field according to the global verification rule and each target change field to obtain a compliance verification result includes:

[0013] Determining whether attribute information of each verification change field is consistent with attribute information of each target change field, wherein the attribute information includes at least one of a field name, field annotation information, and field identification information;

[0014] If the attribute information of each verification change field is consistent with the attribute information of each target change field, the compliance verification result is determined to be verification passed.

[0015] In one embodiment, performing character verification on each verification change field according to the global verification rule and each target change field to obtain a compliance verification result includes:

[0016] Determining whether field information of each verification change field is consistent with field information of each target change field, wherein the field information includes at least one of a field code, a field type, and a field length;

[0017] If the field information of each verification change field is consistent with the field information of each target change field, the compliance verification result is determined to be verification passed.

[0018] In one embodiment, the method further comprises:

[0019] The changed metadata and the standard metadata are stored according to a preset tree structure storage format.

[0020] In one embodiment, the method further comprises:

[0021] Displaying an information viewing control and a verification result export control in the display interface; wherein the information viewing control is used to display the compliance verification result, and the verification result export control is used to export the verification result document;

[0022] In response to a user triggering operation on the display information viewing control and / or the verification result exporting control, the compliance verification result is displayed in the display interface and / or the compliance verification result is exported.

[0023] In a second aspect, the present application further provides a data verification device. The device comprises:

[0024] A receiving module, configured to receive a metadata verification request, wherein the metadata verification request includes a form identifier of a metadata change order, and the metadata change order corresponds to a plurality of changed metadata;

[0025] An acquisition module, configured to acquire each of the change metadata and preset standard metadata according to the form identifier;

[0026] The verification module is used to perform compliance verification on each of the changed metadata according to preset compliance verification rules and the standard metadata, and obtain a compliance verification result corresponding to the metadata verification request.

[0027] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method described in the first aspect when executing the computer program.

[0028] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect.

[0029] In a fifth aspect, the present application further provides a computer program product, comprising a computer program that, when executed by a processor, implements the steps of the method described in the first aspect.

[0030] In the above-mentioned data verification method, apparatus, computer device, computer-readable storage medium, and computer program product, the server first receives a metadata verification request, the metadata verification request including a form identifier of a metadata change order, the metadata change order corresponding to multiple change metadata, then obtains each change metadata and preset standard metadata based on the form identifier, and then performs compliance verification on each change metadata based on preset compliance verification rules and standard metadata to obtain a compliance verification result corresponding to the metadata verification request. Because multiple change metadata corresponding to the metadata change order are accurately obtained through the form identifier during the compliance verification process, the multiple change metadata can be automatically verified separately based on the compliance verification rules and standard metadata. Compared with manual verification, this verification method can quickly and accurately obtain the compliance verification result of each change metadata, thereby quickly obtaining the compliance verification result corresponding to the metadata verification request, realizing the automation and intelligence of metadata compliance verification, ensuring the efficiency and accuracy of metadata verification, and thereby improving the efficiency and accuracy of data management. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0032] Figure 1 A diagram showing an application environment of a data verification method in one embodiment;

[0033] Figure 2 1 is a flow chart of a data verification method according to an embodiment;

[0034] Figure 3 203 is a flow chart of step 203 in one embodiment;

[0035] Figure 4 302 is a flowchart of an embodiment;

[0036] Figure 5 is a flow chart of step 302 in another embodiment;

[0037] Figure 6 Schematic diagram of a flow chart of a data verification method in another embodiment;

[0038] Figure 7 A structural block diagram of a data verification device in one embodiment;

[0039] Figure 8 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0041] With the digital transformation of enterprises, data has become a core element in enhancing their competitiveness. Massive and complex data is generated within enterprises, making effective data management and utilization a rigid requirement. In data management, metadata, as a description of data, can describe information such as the source, creator, creation time, data format, and data relationships. Therefore, efficient metadata management can significantly improve data management efficiency.

[0042] Traditional metadata management methods rely primarily on manual entry, collection, and review processes. However, due to the enormous workload involved in metadata, the required information and the complexities of the related materials involved are extremely complex. Manual entry is not only time-consuming and labor-intensive, but also extremely inefficient, failing to meet the demands of modern enterprises for efficient operations. During metadata review, due to the complex interrelationships between metadata, manual review may fail to effectively reveal data structures and patterns, hindering the effective use of various data types. Furthermore, the lack of effective monitoring and early warning mechanisms during manual review can prevent timely detection of audit errors, leading to frequent rework and wasted time and resources. Furthermore, due to the limitations of manual operation, highly complex and specialized metadata may not be accurately and comprehensively reviewed, impacting the quality and effectiveness of metadata management as a whole.

[0043] Based on this, this application proposes a data verification method to perform compliance verification on the changed metadata to improve the efficiency and accuracy of data management.

[0044] The data verification method provided in the embodiment of the present application can be applied to Figure 1 In the illustrated implementation environment, the implementation environment includes a server, which can be implemented as an independent server or a server cluster consisting of multiple servers. A data storage system can store data that the server needs to process. The data storage system can be integrated on the server or placed on a cloud or other network server. The server first receives a metadata verification request, which includes a form identifier of a metadata change order. The metadata change order corresponds to multiple change metadata. Then, based on the form identifier, the server obtains each change metadata and obtains preset standard metadata. Then, based on the preset compliance verification rules and the standard metadata, the server performs a compliance verification on each change metadata to obtain a compliance verification result corresponding to the metadata verification request.

[0045] In other possible implementations, the data verification method provided in the embodiments of the present application can also be applied to terminals, which may include but are not limited to various personal computers, laptops, smartphones, tablet computers, IoT devices, and portable wearable devices. IoT devices may include smart speakers, smart TVs, smart air conditioners, smart car devices, etc. Portable wearable devices may include smart watches, smart bracelets, head-mounted devices, etc.

[0046] In an exemplary embodiment, Figure 2 As shown, a data verification method is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the server in the example:

[0047] Step 201: receiving a metadata verification request, wherein the metadata verification request includes a form identifier of a metadata change order, and the metadata change order corresponds to a plurality of changed metadata.

[0048] Among them, the metadata verification request refers to an instruction to verify the metadata after it has been changed. It is understandable that during the operation of the business system, if data is added, deleted, modified, or the table structure in the database is adjusted, for example, adding fields, modifying field types, or the file format changes, business rules change, the system environment changes, etc., all of these will cause the metadata to change. In the process of metadata changes, there may be errors or non-standardization in the changed metadata, resulting in the inability to accurately determine the data based on the changed metadata when the changed metadata is subsequently used. Therefore, the changed metadata needs to be verified. For example, the compliance of the changed metadata is verified.

[0049] It is understandable that the metadata verification request may include a form identifier of the metadata change form, and may also include the changed metadata to be verified, verification rules, standard metadata, etc.

[0050] Among them, the metadata change form is a form used to store the changed metadata. Each form corresponds to a unique form identifier, which can be an ID. The metadata change form can be in a table form, or it can be in a document form, or it can be in a graphical interface form. Each metadata change form can correspond to multiple changed metadata, and each changed metadata refers to the content of multiple specific metadata items involved in a metadata change process. For example, when modifying the employee information table, the data type of the field "Age" is changed from "Integer" to "Decimal", and for the field "Job Entry Time", its data type is set to "Date", and it is the system default value. Among them, the data type of the field "Age" and the definition of the field "Job Entry Time" (including field name, data type, default value) are multiple changed metadata.

[0051] It should be noted that the server can store metadata information for multiple business systems. The metadata for each business system can be stored in a metadata change information table. For example, the metadata change information table may include the system name, system ID, version name, associated version number, creation time, and most severe status. Each business system can correspond to multiple business objects, and the metadata change information for each business object can be stored in a metadata change form. For example, the metadata change form may include the table name, table code, table comment, table validation status, business object ID, first-level function ID, second-level function ID, third-level function ID, fourth-level function ID, and change request form ID. Each metadata change form can be stored in a different database.

[0052] In this embodiment, the server may receive a metadata verification request sent by other devices through a network, and obtain a form identifier of the metadata change order included in the metadata verification request by parsing the received metadata verification request.

[0053] Step 202: Acquire each change metadata according to the form identifier, and acquire preset standard metadata.

[0054] The preset standard metadata refers to metadata that complies with metadata specifications and has passed verification. Optionally, the standard metadata can be in table form or document form. For example, the standard metadata can be a Product Data Management File (PDM), which is used to store and manage data related to various stages of product design, development, and manufacturing. The metadata of the PDM file (such as file name, file type, creation time, modification time, etc.) can be stored in a database, and the content of the PDM file can be stored in a storage space.

[0055] In this embodiment, the server can obtain the data table corresponding to the form identifier from the database corresponding to the server based on the form identifier, and obtain the standard metadata corresponding to the data table from the database and / or storage space, and then determine the various data fields included in the data table as various change metadata.

[0056] Step 203 : Perform compliance verification on each changed metadata according to preset compliance verification rules and standard metadata, and obtain a compliance verification result corresponding to the metadata verification request.

[0057] The compliance verification rules are rules for verifying whether the changed metadata complies with the specification. Optionally, the compliance verification rules may include data type verification, data format verification, uniqueness verification, integrity verification, legal value range verification, semantic verification, etc., which are not limited in this embodiment. For example, if the data type corresponding to a field is an integer type, the data type stored in the metadata of the field is "integer". If the data type of the changed metadata is non-integer, it can be determined that the changed metadata does not comply with the compliance verification rules.

[0058] The compliance verification result refers to the compliance verification result of each metadata change. For example, the compliance verification result corresponding to the metadata verification request can be determined based on the compliance verification results of each metadata change using a logical OR operation.

[0059] In this embodiment, the server can compare the data in each change metadata that matches the compliance verification rules with the corresponding comparison data in the standard metadata according to the compliance verification rules, and then determine the compliance verification result corresponding to the metadata verification request based on the comparison result.

[0060] In the above data verification method, the server first receives a metadata verification request, which includes a form identifier of a metadata change order. The metadata change order corresponds to multiple change metadata. Then, each change metadata is obtained according to the form identifier, as well as the preset standard metadata. Then, each change metadata is compliance-verified according to the preset compliance verification rules and standard metadata to obtain a compliance verification result corresponding to the metadata verification request. Since multiple change metadata corresponding to the metadata change order are accurately obtained through the form identifier during the compliance verification process, the multiple change metadata can be automatically verified according to the compliance verification rules and standard metadata. Compared with manual verification, this verification method can quickly and accurately obtain the compliance verification results of each change metadata, thereby quickly obtaining the compliance verification results corresponding to the metadata verification request, realizing the automation and intelligence of metadata compliance verification, ensuring the efficiency and accuracy of metadata verification, and thereby improving the efficiency and accuracy of data management.

[0061] In an exemplary embodiment, Figure 3 As shown, the change metadata includes multiple verification change fields, and the compliance verification rules include local verification rules and global verification rules. This embodiment relates to how the server performs compliance verification on each change metadata according to preset compliance verification rules and standard metadata to obtain a compliance verification result corresponding to the metadata verification request. The above step 203 includes:

[0062] Step 301 : for each changed metadata, determine whether there are target changed fields identical to the checked changed fields in the standard metadata according to the local check rule.

[0063] Local validation rules refer to the rules for validating the fields included in the metadata changes. Understandably, when performing metadata changes, errors such as data inconsistency, data loss, data permission errors, data compatibility errors, and data semantic errors may occur. Therefore, when performing metadata compliance verification, the fields in the metadata changes can be verified based on local validation rules.

[0064] In this embodiment, a process of performing compliance verification on the changed metadata according to the verification rules is described in detail by taking a changed metadata as an example.

[0065] The verification change field refers to the field in the change metadata, and the target change field refers to the field in the standard metadata that is identical to the verification change field. Alternatively, the target change field can be a field with the same field identifier as the verification change field, or a field with the same field code as the verification change field, or a field with the same source as the verification change field.

[0066] In this embodiment, the server can compare each verification change field in the change metadata with each field in the standard metadata according to the local verification rules. If there is a field with the same comparison result, the field is determined as the target change field corresponding to the verification change field.

[0067] As a possible implementation method, the server can determine that the local verification rule of the change metadata is passed when each verification change field in the change metadata has a corresponding target change field, so that the change metadata can be globally verified according to all verification rules; if a verification change field in the change metadata does not have a corresponding target change field, it can be determined that the local verification rule of the change metadata is failed, and thus the compliance verification result corresponding to the metadata verification request can be determined as failed.

[0068] Step 302 : When target change fields exist in the standard metadata, character verification is performed on each verification change field according to the global verification rule and each target change field to obtain a compliance verification result.

[0069] Among them, the global verification rule refers to the rule for character verification of the verification change field in the change metadata and the target change field in the standard metadata, that is, the content, format, and attributes of each character in the verification change field are compared with the content, format, and attributes of the corresponding character in the target change field.

[0070] In this embodiment, when there are target change fields in the standard metadata, the server can compare each character in the verification change field with the character in the corresponding target change field for each verification change field to obtain a comparison result, and then obtain a compliance verification result corresponding to each change data based on each comparison result, and then obtain a compliance verification result of the metadata verification request based on the compliance verification result corresponding to each change data.

[0071] As a possible implementation method, if the change metadata and the standard metadata are both in the format of data tables, the table code, table name, and table comments of the change metadata can be verified according to the global verification rules to see whether they are consistent with the standard metadata, and the field name, field type, field length, and field precision of the verification change field in the change metadata can be verified to see whether they are consistent with the standard metadata.

[0072] In this embodiment, the server first determines, for each change metadata, whether there are target change fields that are the same as the verification change fields in the standard metadata based on local verification rules. Then, if the target change fields exist in the standard metadata, the server performs character verification on the verification change fields based on the global verification rules and the target change fields to obtain the compliance verification result of each change metadata, thereby obtaining the compliance verification result corresponding to the metadata verification request. Due to the combination of local verification rules and global verification rules, the change metadata can be subjected to compliance verification rules from different dimensions, thereby improving the accuracy of the obtained compliance verification results.

[0073] It should be noted that when verifying according to global verification rules, you can verify the attribute information of the verification change field in the change metadata and the target change field in the standard metadata, or you can verify the field information. The verification process of the two global verification rules is described below:

[0074] First, in an exemplary embodiment, Figure 4 As shown, this embodiment relates to how the server performs character verification on each verification change field according to the global verification rules and each target change field to obtain a compliance verification result. The above step 302 includes:

[0075] Step 401: Determine whether the attribute information of each verification change field is consistent with the attribute information of each target change field.

[0076] The attribute information includes at least one of a field name, a field annotation information, and a field identification information.

[0077] Among them, attribute information refers to the definition and characteristics of the field, the attribute information of the verification change field refers to the information used to describe the definition and characteristics of the field in the change metadata, and the attribute information of the target change field refers to the information used to describe the definition and characteristics of the field in the standard metadata.

[0078] The field name refers to the name of the field. For example, the field name can be a data type. Field annotation information is information used to explain the meaning of the field. For example, the field annotation information can be the data type used to represent metadata for the field. Field identification information is information used to uniquely identify the field. For example, field identification information can be the field ID 1122.

[0079] In this embodiment, the server can compare the attribute information of each verification change field with the attribute information of each corresponding target change field, and determine whether the attribute information of each verification change field is consistent with the attribute information of each target change field based on the comparison result.

[0080] Step 402: If the attribute information of each verification change field is consistent with the attribute information of each target change field, then the compliance verification result is determined to be verification passed.

[0081] In this embodiment, the server can determine that the attribute information of each verification change field is consistent with the attribute information of each target change field when it is determined that the attribute information of each verification change field is the same as the attribute information of the corresponding target change field, thereby determining that the compliance verification result of the metadata verification request is verification passed.

[0082] In this embodiment, the server determines whether the attribute information of each verification change field is consistent with the attribute information of each target change field. When the attribute information of each verification change field is consistent with the attribute information of each target change field, the server can determine that the compliance verification result is passed. Since the attribute information includes at least one of the field name, field annotation information, and field identification information, by determining whether the attribute information is consistent, the compliance of the verification change field can be verified from multiple dimensions, thereby improving the accuracy of the determined compliance verification result.

[0083] Second, in another exemplary embodiment, as Figure 5 As shown, this embodiment relates to how the server performs character verification on each verification change field according to the global verification rules and each target change field to obtain a compliance verification result. The above step 302 includes:

[0084] Step 501: Determine whether the field information of each verification change field is consistent with the field information of each target change field.

[0085] The field information includes at least one of a field code, a field type, and a field length.

[0086] The field information refers to information that provides a detailed explanation of each field. For example, the field information may include the field length, field precision, whether the field can store null values, the value range of the field, etc.

[0087] The field code refers to the specific name or identifier used to identify and reference a field. The field type refers to the storage type of the data corresponding to the metadata. For example, field types can include numeric, character, date, binary, etc. The field length refers to the storage length of the data corresponding to the metadata. For example, the storage length can be 4 bytes, 8 bytes, etc.

[0088] In this embodiment, the server can compare the field information of each verification change field with the field information of each corresponding target change field, and determine whether the field information of each verification change field is consistent with the field information of each target change field based on the comparison result.

[0089] Step 502: If the field information of each verification change field is consistent with the field information of each target change field, then the compliance verification result is determined to be verification passed.

[0090] In this embodiment, the server can determine that the field information of each verification change field is consistent with the field information of each target change field when it is determined that the field information of each verification change field is the same as the field information of the corresponding target change field, thereby determining that the compliance verification result of the metadata verification request is verification passed.

[0091] In this embodiment, the server determines whether the field information of the target change field is consistent with the field information of the verification change field. When the field information of the target change field is consistent with the field information of the verification change field, the server can determine that the compliance verification result is passed. Since the field information includes at least one of the field code, field type, and field length, the compliance of the verification change field can be verified from multiple dimensions, thereby improving the accuracy of the determined compliance verification result.

[0092] In an exemplary embodiment, this embodiment relates to a process of how a server stores change metadata and standard metadata corresponding to metadata. The above method further includes: storing each change metadata and standard metadata according to a preset tree structure storage format.

[0093] A tree structure is a data structure that organizes and manages data in a hierarchical manner. It should be noted that storing change metadata and standard metadata in a tree structure can reflect the relationship between data and facilitate compliance verification.

[0094] In this embodiment, the server may store the change metadata and the standard metadata according to the hierarchical relationship between the metadata change order and the change metadata, and between the metadata change order and the standard metadata.

[0095] For example, a business system is used as the root node, multiple business objects corresponding to a business system are first-level child nodes, multiple metadata change orders and standard metadata corresponding to each business object are second-level child nodes, and multiple change metadata corresponding to each metadata change order are third-level child nodes. The change metadata and standard metadata are stored in a structured manner.

[0096] In this embodiment, the server stores each change metadata and standard metadata according to a preset tree structure storage format, which not only improves storage efficiency and space utilization, but also reflects the relationship between each change metadata through the tree structure, thereby facilitating compliance verification of each change metadata and standard metadata, improving the efficiency of compliance verification, and thus improving the efficiency of data management.

[0097] In an exemplary embodiment, Figure 6 As shown, this embodiment relates to a process of how a server visually displays a metadata change verification process. The above method further includes:

[0098] Step 601: Display an information viewing control and a verification result export control in a display interface.

[0099] The information viewing control is used to display the compliance verification results, and the verification result export control is used to export the verification result document.

[0100] The display interface can be the interface displayed on the display screen of a server or terminal device where the data verification system is deployed. The information viewing control is a component used to display and view metadata management pages. For example, by triggering the information viewing control on the display interface or clicking the information viewing control with a mouse, the server can display the corresponding information to the user. The verification result export control is a component used to display the compliance verification results of the metadata to be verified.

[0101] In this embodiment, the server can display an information viewing control and a verification result export control to the user in the display interface. For example, after the user opens the data verification system, the information viewing control can be displayed in the upper left corner of the display interface, and after the compliance verification results are generated, the verification result export control can pop up in the display interface.

[0102] Step 602: In response to a user's control for viewing display information and / or a triggering operation, the compliance verification result is displayed in the display interface and / or the compliance verification result is exported.

[0103] In this embodiment, the server can receive the user's trigger operation for the display information viewing control through the display interface and display the target inspection results, or receive the user's trigger operation for the verification result export control through the display interface and export the compliance verification results in the form of a document.

[0104] In this embodiment, the server displays an information viewing control and a verification result export control in a display interface; wherein the information viewing control is used to display the compliance verification results, and the verification result export control is used to export the verification result document. In response to the user's triggering operation for displaying the information viewing control and / or the verification result export control, the server can display the compliance verification results and / or export the compliance verification results in the display interface, thereby providing the user with visual data management, allowing the user to intuitively view the metadata and / or compliance verification results, thereby improving the quality of data management.

[0105] To facilitate understanding by those skilled in the art, the data verification method provided by this application is described in detail below. The method may include:

[0106] S1. Store the changed metadata and standard metadata corresponding to the metadata change order according to a preset tree structure storage format.

[0107] S2: Receive a metadata verification request, where the metadata verification request includes a form identifier of a metadata change order.

[0108] S3, obtain each change metadata according to the form identifier, and obtain preset standard metadata.

[0109] S4: For each changed metadata, determine, based on the local verification rule, whether there are target changed fields in the standard metadata that are identical to the verification changed fields.

[0110] S5. When the target change fields exist in the check change field, it is determined whether the attribute information of the check change field is consistent with the attribute information of the target change field.

[0111] S6. If the attribute information of each verification change field is consistent with the attribute information of each target change field, the compliance verification result is determined to be verification passed.

[0112] S7: When each target change field exists in the standard metadata, it is determined whether the field information of each verification change field is consistent with the field information of each target change field.

[0113] S8. If the field information of each verification change field is consistent with the field information of each target change field, the compliance verification result is determined to be verification passed.

[0114] S9, displaying an information viewing control and a verification result export control on the display interface.

[0115] S10 , in response to a user triggering operation on a display information viewing control and / or a verification result exporting control, displaying the compliance verification result in a display interface and / or exporting the compliance verification result.

[0116] It should be noted that for the descriptions in S1-S10 above, reference can be made to the relevant descriptions in the above embodiments, and the effects are similar, so this embodiment will not be repeated here.

[0117] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0118] Based on the same inventive concept, the present application also provides a data verification device for implementing the aforementioned data verification method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more data verification device embodiments provided below can be found in the above-mentioned limitations of the data verification method and will not be repeated here.

[0119] In one embodiment, Figure 7 As shown, a data verification device is provided, including: a receiving module 701, an acquisition module 702 and a verification module 703, wherein:

[0120] The receiving module 701 is configured to receive a metadata verification request, wherein the metadata verification request includes a form identifier of a metadata change order, and the metadata change order corresponds to a plurality of changed metadata;

[0121] The acquisition module 702 is used to acquire each change metadata according to the form identifier, and acquire preset standard metadata;

[0122] The verification module 703 is configured to perform compliance verification on each changed metadata according to preset compliance verification rules and standard metadata, and obtain a compliance verification result corresponding to the metadata verification request.

[0123] The data verification device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here.

[0124] In one embodiment, the change metadata includes multiple verification change fields, and the compliance verification rules include local verification rules and global verification rules. The verification module 703 includes:

[0125] a determination unit configured to determine, for each change metadata, based on a local verification rule, whether the standard metadata contains target change fields that are identical to the verification change fields;

[0126] The verification unit is used to perform character verification on each verification change field according to the global verification rules and each target change field when each target change field exists in the standard metadata, so as to obtain a compliance verification result.

[0127] The data verification device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here.

[0128] In one embodiment, the verification unit is specifically configured to:

[0129] Determine whether the attribute information of each verification change field is consistent with the attribute information of each target change field, where the attribute information includes at least one of a field name, field annotation information, and field identification information;

[0130] If the attribute information of each verification change field is consistent with the attribute information of each target change field, the compliance verification result is determined to be verification passed.

[0131] The data verification device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here.

[0132] In one embodiment, the verification unit is specifically configured to:

[0133] Determine whether the field information of each verification change field is consistent with the field information of each target change field, where the field information includes at least one of a field code, a field type, and a field length;

[0134] If the field information of each verification change field is consistent with the field information of each target change field, the compliance verification result is determined to be verification passed.

[0135] The data verification device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here.

[0136] In one embodiment, the apparatus further comprises:

[0137] The storage module is used to store the changed metadata and the standard metadata according to a preset tree structure storage format.

[0138] The data verification device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here.

[0139] In one embodiment, the apparatus further comprises:

[0140] A display module is used to display information viewing controls and verification result export controls in the display interface; the information viewing controls are used to display compliance verification results, and the verification result export controls are used to export verification result documents;

[0141] The trigger module is used to display the compliance verification results and / or export the compliance verification results in the display interface in response to the user's trigger operation on the display information viewing control and / or the verification result export control.

[0142] The data verification device provided in this embodiment can execute the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here.

[0143] Each module in the above-mentioned data verification device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module 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 corresponding operations of each module.

[0144] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 8 As shown. The computer device includes a processor, a memory, an input / output interface (I / O) and a communication interface. The processor, memory and input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store metadata change metadata. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a data verification method is implemented.

[0145] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0146] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0147] receiving a metadata verification request, the metadata verification request including a form identifier of a metadata change order, where the metadata change order corresponds to a plurality of changed metadata;

[0148] Obtain each change metadata according to the form identifier, as well as the preset standard metadata;

[0149] Perform compliance verification on each change metadata according to the preset compliance verification rules and standard metadata, and obtain the compliance verification result corresponding to the metadata verification request.

[0150] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0151] For each change metadata, determine whether the target change fields that are identical to the verification change fields exist in the standard metadata according to the local verification rules;

[0152] When target change fields exist in the standard metadata, character verification is performed on each verification change field according to the global verification rules and each target change field to obtain a compliance verification result.

[0153] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0154] Determine whether the attribute information of each verification change field is consistent with the attribute information of each target change field, where the attribute information includes at least one of a field name, field annotation information, and field identification information;

[0155] If the attribute information of each verification change field is consistent with the attribute information of each target change field, the compliance verification result is determined to be verification passed.

[0156] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0157] Determine whether the field information of each verification change field is consistent with the field information of each target change field, where the field information includes at least one of a field code, a field type, and a field length;

[0158] If the field information of each verification change field is consistent with the field information of each target change field, the compliance verification result is determined to be verification passed.

[0159] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0160] The changed metadata and standard metadata are stored according to the preset tree structure storage format.

[0161] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0162] An information viewing control and a verification result export control are displayed on the display interface; the information viewing control is used to display the compliance verification results, and the verification result export control is used to export the verification result document;

[0163] In response to a user triggering operation on a display information viewing control and / or a verification result exporting control, the compliance verification result is displayed in the display interface and / or the compliance verification result is exported.

[0164] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0165] receiving a metadata verification request, the metadata verification request including a form identifier of a metadata change order, where the metadata change order corresponds to a plurality of changed metadata;

[0166] Obtain each change metadata according to the form identifier, as well as the preset standard metadata;

[0167] Perform compliance verification on each change metadata according to the preset compliance verification rules and standard metadata, and obtain the compliance verification result corresponding to the metadata verification request.

[0168] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0169] For each change metadata, determine whether the target change fields that are identical to the verification change fields exist in the standard metadata according to the local verification rules;

[0170] When target change fields exist in the standard metadata, character verification is performed on each verification change field according to the global verification rules and each target change field to obtain a compliance verification result.

[0171] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0172] Determine whether the attribute information of each verification change field is consistent with the attribute information of each target change field, where the attribute information includes at least one of a field name, field annotation information, and field identification information;

[0173] If the attribute information of each verification change field is consistent with the attribute information of each target change field, the compliance verification result is determined to be verification passed.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0175] Determine whether the field information of each verification change field is consistent with the field information of each target change field, where the field information includes at least one of a field code, a field type, and a field length;

[0176] If the field information of each verification change field is consistent with the field information of each target change field, the compliance verification result is determined to be verification passed.

[0177] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0178] The changed metadata and standard metadata are stored according to the preset tree structure storage format.

[0179] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0180] An information viewing control and a verification result export control are displayed on the display interface; the information viewing control is used to display the compliance verification results, and the verification result export control is used to export the verification result document;

[0181] In response to a user triggering operation on a display information viewing control and / or a verification result exporting control, the compliance verification result is displayed in the display interface and / or the compliance verification result is exported.

[0182] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0183] receiving a metadata verification request, the metadata verification request including a form identifier of a metadata change order, where the metadata change order corresponds to a plurality of changed metadata;

[0184] Obtain each change metadata according to the form identifier, as well as the preset standard metadata;

[0185] Perform compliance verification on each change metadata according to the preset compliance verification rules and standard metadata, and obtain the compliance verification result corresponding to the metadata verification request.

[0186] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0187] For each change metadata, determine whether the target change fields that are identical to the verification change fields exist in the standard metadata according to the local verification rules;

[0188] When target change fields exist in the standard metadata, character verification is performed on each verification change field according to the global verification rules and each target change field to obtain a compliance verification result.

[0189] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0190] Determine whether the attribute information of each verification change field is consistent with the attribute information of each target change field, where the attribute information includes at least one of a field name, field annotation information, and field identification information;

[0191] If the attribute information of each verification change field is consistent with the attribute information of each target change field, the compliance verification result is determined to be verification passed.

[0192] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0193] Determine whether the field information of each verification change field is consistent with the field information of each target change field, where the field information includes at least one of a field code, a field type, and a field length;

[0194] If the field information of each verification change field is consistent with the field information of each target change field, the compliance verification result is determined to be verification passed.

[0195] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0196] The changed metadata and standard metadata are stored according to the preset tree structure storage format.

[0197] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0198] An information viewing control and a verification result export control are displayed on the display interface; the information viewing control is used to display the compliance verification results, and the verification result export control is used to export the verification result document;

[0199] In response to a user triggering operation on a display information viewing control and / or a verification result exporting control, the compliance verification result is displayed in the display interface and / or the compliance verification result is exported.

[0200] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the above-described method embodiments. Any reference to a memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processors (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), data processing logic devices based on quantum computing, and the like.

[0201] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0202] The above embodiments merely illustrate several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art may make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A data verification method, characterized in that: The method comprises: receiving a metadata verification request, the metadata verification request including a form identifier of a metadata change order, the metadata change order corresponding to a plurality of changed metadata; Acquire each of the change metadata according to the form identifier, and acquire preset standard metadata; Compliance verification is performed on each of the changed metadata according to preset compliance verification rules and the standard metadata to obtain a compliance verification result corresponding to the metadata verification request.

2. The method according to claim 1, characterized in that The change metadata includes multiple verification change fields, and the compliance verification rules include local verification rules and global verification rules. The compliance verification is performed on each of the change metadata according to the preset compliance verification rules and the standard metadata to obtain a compliance verification result corresponding to the metadata verification request, including: For each of the change metadata, determining, according to the local verification rule, whether there are target change fields identical to the verification change fields in the standard metadata; In the case that each target change field exists in the standard metadata, character verification is performed on each verification change field according to the global verification rule and each target change field to obtain the compliance verification result.

3. The method according to claim 2, characterized in that The performing character verification on each verification change field according to the global verification rule and each target change field to obtain the compliance verification result includes: Determining whether attribute information of each verification change field is consistent with attribute information of each target change field, wherein the attribute information includes at least one of a field name, field annotation information, and field identification information; If the attribute information of each verification change field is consistent with the attribute information of each target change field, the compliance verification result is determined to be verification passed.

4. The method according to claim 2, characterized in that The performing character verification on each verification change field according to the global verification rule and each target change field to obtain a compliance verification result includes: Determining whether field information of each verification change field is consistent with field information of each target change field, wherein the field information includes at least one of a field code, a field type, and a field length; If the field information of each verification change field is consistent with the field information of each target change field, the compliance verification result is determined to be verification passed.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The changed metadata and the standard metadata are stored according to a preset tree structure storage format.

6. The method according to claim 1, characterized in that The method further comprises: Displaying an information viewing control and a verification result export control in the display interface; wherein the information viewing control is used to display the compliance verification result, and the verification result export control is used to export the verification result document; In response to a user triggering operation on the display information viewing control and / or the verification result exporting control, the compliance verification result is displayed in the display interface and / or the compliance verification result is exported.

7. A data verification device, characterized in that: The device comprises: A receiving module, configured to receive a metadata verification request, wherein the metadata verification request includes a form identifier of a metadata change order, and the metadata change order corresponds to a plurality of changed metadata; An acquisition module, configured to acquire each of the change metadata and preset standard metadata according to the form identifier; The verification module is used to perform compliance verification on each of the changed metadata according to preset compliance verification rules and the standard metadata, and obtain a compliance verification result corresponding to the metadata verification request.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images