CN111241082B

CN111241082B - Data correction method and device

Info

Publication number: CN111241082B
Application number: CN202010033977.9A
Authority: CN
Inventors: 王腾涛
Original assignee: Seashell Housing Beijing Technology Co Ltd
Current assignee: Seashell Housing Beijing Technology Co Ltd
Priority date: 2020-01-13
Filing date: 2020-01-13
Publication date: 2020-10-23
Anticipated expiration: 2040-01-13
Also published as: CN111241082A

Abstract

The embodiment of the invention provides a data correction method and device, and belongs to the technical field of computers. The method comprises the following steps: acquiring a data table aiming at data to be corrected, wherein the data table comprises one or more instances to be corrected, the content of the instances to be corrected comprises a correction value, a first field name corresponding to the correction value, and data items in a business list to which the first field name belongs; checking the content of the example to be corrected in the data table; and updating the field value corresponding to the first field name by using the correction value for the checked to-be-corrected example. The method and the device can realize batch modification of data needing to be modified, so that the error data can be rapidly modified without changing the service flow and the service state.

Description

Data correction method and device

Technical Field

The invention relates to the technical field of computers, in particular to a data correction method and device.

Background

Generally, when a business process is executed, business data needs to be recorded into a system. In the related art, generally, service data is manually input into an online system offline by a worker, and data input errors are inevitably caused. The error data in the online system is more and more after a long time, and the later data statistics, analysis and the like are influenced to a certain extent.

Disclosure of Invention

An object of the embodiments of the present invention is to provide a data correction method and apparatus, which are used to solve or completely solve the above technical problems.

In order to achieve the above object, an embodiment of the present invention provides a data correction method, where the data correction method includes: acquiring a data table aiming at data to be corrected, wherein the data table comprises one or more instances to be corrected, the content of the instances to be corrected comprises a correction value, a first field name corresponding to the correction value, and data items in a business list to which the first field name belongs; checking the content of the example to be corrected in the data table; and updating a field value corresponding to the first field name by using the correction value for the checked to-be-corrected example, wherein in the case that the data table is a data table of business backlog, the first field name is the first to-be-handled field name, and data items in a business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, ID to be handled and items to be handled; and/or in the case that the data table is a data table of business entity matters, the first field name is a first entity field name, and the data items in the business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, entity classification, entity ID and non-reporting module.

Optionally, when the data table is a data table of business backlogs, the checking the content of the to-be-corrected instance in the data table includes: checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table; in the case that the checking of the existence and the relevance of each item passes, checking the first to-do field name and the field type of the correction value includes: searching a to-be-handled field configuration corresponding to the to-be-handled ID and the to-be-handled item from a to-be-handled field configuration table, wherein the to-be-handled field configuration comprises a second to-be-handled field name and a field type of a field value corresponding to the second to-be-handled field name; judging whether the first to-be-handled field name is matched with the second to-be-handled field name; under the condition that the first to-be-handled field name is matched with the second to-be-handled field name, judging whether the field type of the corrected value is matched with the field type of the field value corresponding to the second to-be-handled field; and determining that the content of the example to be corrected passes the verification under the condition that the field type of the corrected value is matched with the field type of the field value corresponding to the second field to be handled.

Optionally, when the data table is a data table of business backlogs, the checking the content of the to-be-corrected instance in the data table includes: under the condition that the data table comprises a plurality of examples to be corrected, aiming at the plurality of examples to be corrected, the existence and the relevance of each item of which pass the verification, grouping the plurality of examples to be corrected, the existence and the relevance of which pass the verification, according to the ID to be handled; and carrying out batch verification on the first to-be-processed field name and the field type of the correction value according to the grouped group.

Optionally, in a case that the data table is a data table of business backlogs, the updating, by using the correction value, the field value corresponding to the first field name for the to-be-corrected instance that passes the verification includes: inquiring the name of the field to be handled from a field data table to be handled by using the ID to be handled; and under the condition that the name of the field to be handled is inquired, updating the field value corresponding to the name of the field to be handled into the corrected value.

Optionally, in a case that the data table is a data table of business entity matters, the checking the content of the to-be-corrected instance in the data table includes: checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table; and determining that the content of the instance to be corrected passes the verification if the existence and relevance of the items pass the verification.

Optionally, in a case that the data table is a data table of business entity matters, the updating, with respect to the to-be-corrected instance that passes the verification, the field value corresponding to the first field name by using the correction value includes: querying, from an entity table, configuration information for the first entity field name using the city ID and the first entity field name, the configuration information including a classification of the first entity field name, wherein the classification of the first entity field name includes one or more of: capital, house, business, personnel information; judging whether the classification of the first entity field name is the same as the entity classification; in a case where the classification of the first entity field name is the same as the entity classification, inquiring the first entity field name in a list corresponding to the entity classification using the business form ID for the classification of the money, the house, and the business, inquiring the first entity field name in a list corresponding to the entity classification using the entity ID for the classification of the person information; and updating the field value corresponding to the first entity field name to the correction value when the first entity field name is inquired.

Optionally, in a case that the data table is a data table of business entity matters, the updating, with respect to the to-be-corrected instance that passes the verification, the field value corresponding to the first field name by using the correction value includes: under the condition that the data table comprises a plurality of examples to be corrected, grouping the plurality of examples to be corrected according to the service list ID aiming at the plurality of examples to be corrected which pass the verification; and updating a field value corresponding to the first field name using the correction value according to the grouped group.

Optionally, the method further includes: carrying out duplicate removal processing on the system ID and the business list ID of the to-be-corrected example which has finished data correction; and notifying each set of system ID and service order ID after the deduplication processing to the service needing synchronization, wherein the service needing synchronization comprises a retrieval event and/or a visualization event.

Optionally, the method further includes: under the condition that each example to be corrected in the data table successfully completes data correction, sending a prompt about successful completion of data correction; and/or sending a prompt about the reason of the failure of data correction when the to-be-corrected example which does not successfully finish the data correction exists in the data table.

Correspondingly, an embodiment of the present invention further provides a data correction device, where the data correction device includes: the data processing device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a data table aiming at data to be corrected, the data table comprises one or more instances to be corrected, the content of the instances to be corrected comprises a correction value, a first field name corresponding to the correction value, and data items in a business list related to the first field name; the checking module is used for checking the content of the example to be corrected in the data table; and an updating module, configured to update, for the to-be-corrected instance that passes the verification, a field value corresponding to the first field name using the correction value, where, in a case that the data table is a data table of business backlog, the first field name is a first to-be-processed field name, and a data item in a business process to which the first field name belongs includes one or more of the following items: city ID, system ID, business order number, business order ID, ID to be handled and items to be handled; and/or in the case that the data table is a data table of business entity matters, the first field name is a first entity field name, and the data items in the business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, entity classification, entity ID and non-reporting module.

Optionally, when the data table is a data table of business backlogs, the verification module is configured to verify the content of the to-be-corrected instance in the data table according to the following steps: checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table; in the case that the checking of the existence and the relevance of each item passes, checking the first to-do field name and the field type of the correction value includes: searching a to-be-handled field configuration corresponding to the to-be-handled ID and the to-be-handled item from a to-be-handled field configuration table, wherein the to-be-handled field configuration comprises a second to-be-handled field name and a field type of a field value corresponding to the second to-be-handled field name; judging whether the first to-be-handled field name is matched with the second to-be-handled field name; under the condition that the first to-be-handled field name is matched with the second to-be-handled field name, judging whether the field type of the corrected value is matched with the field type of the field value corresponding to the second to-be-handled field; and determining that the content of the example to be corrected passes the verification under the condition that the field type of the corrected value is matched with the field type of the field value corresponding to the second field to be handled.

Optionally, in a case that the data table is a data table of business backlogs, the verification module is configured to: under the condition that the data table comprises a plurality of examples to be corrected, aiming at the plurality of examples to be corrected, the existence and the relevance of each item of which pass the verification, grouping the plurality of examples to be corrected, the existence and the relevance of which pass the verification, according to the ID to be handled; and carrying out batch verification on the first to-be-processed field name and the field type of the correction value according to the grouped group.

Optionally, in a case that the data table is a data table of business backlogs, the updating module is configured to update, for the to-be-corrected instance that passes the verification, the field value corresponding to the first field name by using the correction value according to the following steps: inquiring the name of the field to be handled from a field data table to be handled by using the ID to be handled; and under the condition that the name of the field to be handled is inquired, updating the field value corresponding to the name of the field to be handled into the corrected value.

Optionally, when the data table is a data table of business entity matters, the checking module is configured to check the content of the to-be-corrected instance in the data table according to the following steps: checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table; and determining that the content of the instance to be corrected passes the verification if the existence and relevance of the items pass the verification.

Optionally, in a case that the data table is a data table of business entity matters, the updating module is configured to update, for the to-be-corrected instance that passes the verification, the field value corresponding to the first field name by using the correction value according to the following steps: querying, from an entity table, configuration information for the first entity field name using the city ID and the first entity field name, the configuration information including a classification of the first entity field name, wherein the classification of the first entity field name includes one or more of: capital, house, business, personnel information; judging whether the classification of the first entity field name is the same as the entity classification; in a case where the classification of the first entity field name is the same as the entity classification, inquiring the first entity field name in a list corresponding to the entity classification using the business form ID for the classification of the money, the house, and the business, inquiring the first entity field name in a list corresponding to the entity classification using the entity ID for the classification of the person information; and updating the field value corresponding to the first entity field name to the correction value when the first entity field name is inquired.

Optionally, in a case that the data table is a data table of business entity items, the update module is configured to: under the condition that the data table comprises a plurality of examples to be corrected, grouping the plurality of examples to be corrected according to the service list ID aiming at the plurality of examples to be corrected which pass the verification; and updating a field value corresponding to the first field name using the correction value according to the grouped group.

Optionally, the apparatus further comprises: the duplication removing module is used for carrying out duplication removing processing on the system ID and the business list ID of the to-be-corrected example which is subjected to data correction; and a notification module, configured to notify each set of system ID and service order ID after the deduplication processing to a service requiring synchronization, where the service requiring synchronization includes a retrieval event and/or a visualization event.

Optionally, the apparatus further comprises: the first sending module is used for sending a prompt about successful completion of data correction under the condition that each to-be-corrected instance in the data table successfully completes the data correction; and/or the second sending module is used for sending a prompt about the reason of the failure of the data correction under the condition that the to-be-corrected example which does not successfully finish the data correction exists in the data table.

Accordingly, the embodiment of the present invention also provides a machine-readable storage medium, on which instructions are stored, and the instructions are used for causing a machine to execute the above data correction method.

Correspondingly, the embodiment of the invention also provides electronic equipment, which comprises at least one processor, at least one memory connected with the processor and a bus; the processor and the memory complete mutual communication through the bus; the processor is used for calling the program instructions in the memory so as to execute the data correction method.

By the technical scheme, the content of the example to be corrected of the data table of the data to be corrected is verified, and the field value corresponding to the field name in the example to be corrected which passes the verification is subjected to data correction, so that the data to be corrected can be corrected in batch, the error data can be corrected quickly, and the service flow and the service state do not need to be changed.

Additional features and advantages of embodiments of the invention will be set forth in the detailed description which follows.

Drawings

The accompanying drawings, which are included to provide a further understanding of the embodiments of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the embodiments of the invention without limiting the embodiments of the invention. In the drawings:

FIG. 1 is a flow chart diagram illustrating a data modification method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating a flow of checking the content of the to-be-corrected instance in a case that the data table is a data table of the business to-do item in an embodiment;

FIG. 3 is a schematic diagram illustrating a flow of updating using a correction value in the case where the data table is a data table of a business entity transaction in an embodiment;

fig. 4 is a block diagram showing a configuration of a data correction apparatus according to an embodiment of the present invention;

fig. 5 is a block diagram showing a configuration of a data correction apparatus according to another embodiment of the present invention;

fig. 6 is a block diagram showing a configuration of a data correction apparatus according to still another embodiment of the present invention; and

fig. 7 shows a block diagram of an electronic device according to an embodiment of the invention.

Detailed Description

The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating embodiments of the invention, are given by way of illustration and explanation only, not limitation.

Fig. 1 is a flow chart illustrating a data correction method according to an embodiment of the present invention. As shown in fig. 1, an embodiment of the present invention provides a data correction method, which may include steps S110 to S130.

In step S110, a data table for the data to be corrected is acquired.

The data table may be a data table uploaded by a user, or may be obtained from a local storage.

In practical application, a page related to the data correction tool may be set in the user management system, and the user may upload the data table through the page. It will be appreciated that only some specific users may be set to have rights to the data modification tool. After a user logs in the system, the rear end of the system acquires the authority point of a login person, and if the authority point contains the authority aiming at the data correction tool, the user can enter a page related to the data correction tool. For the user uploading the data table, whether the user has the authority for the data correction tool or not can be judged firstly, and if the user has the authority, the subsequent steps are executed. Otherwise, a relevant prompt can be sent out, so that the unauthorized user is prevented from executing the event.

Problematic traffic data may be derived using big data methods according to error data derivation rules, which may be, for example: the sum is more than 1 ten thousand yuan, the surface signing time is less than the current time, and the like. Data that does not satisfy these rules is derived as error data. The user can confirm the erroneous data and fill in the data table with the correct data values. When the error data relates to service data in a plurality of cities, the error data can be issued to a worker in charge of the service data of the corresponding city according to the city ID, the worker confirms the error data and provides a correct data value.

In some cases, when a user adjusts some data as needed, the data needed to be adjusted may be written into the data table.

In the embodiment of the present invention, the data correction method may be directed to two types of repair: business backlogs and business entity events. Templates of the data table can be respectively set for the two matters, the templates can be provided with the header, and then the templates are shared. For example, a template may be uploaded to a file storage service and a link to the template may be retrieved, which may be displayed in a page about a data correction tool. Through which the user can view or download the template. In addition, an instance may be provided in the template for further reference by the user. Table 1 shows exemplary templates for business backlogs in one embodiment, and table 2 shows exemplary templates for business entity transactions in one embodiment.

TABLE 1

TABLE 2

As can be seen from tables 1 and 2, the content of the to-be-corrected example includes the correction value, the first field name corresponding to the correction value, and the data item in the service ticket to which the first field name belongs. In the case that the data table is a data table of business backlogs, the first field name is a first backlog field name, and the data items in the business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, to-do ID and to-do item. One service list ID can correspond to a plurality of to-do IDs, one to-do ID can correspond to a plurality of to-do items, and one to-do item can correspond to a plurality of to-do field names. In the case that the data table is a data table of business entity matters, the first field name is a first entity field name, and the data items in the business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, entity classification, entity ID and non-reporting module. Wherein, the unreported modules are the upper-level types of the entity field names, but each unreported module can relate to a plurality of entity field names for further classification of entity classification. In the illustrative example of Table 2 above, the funds constructs are of a higher-level type of the entity field name QI _ TA _ DAI _ KUAN _ JIN _ E, but are of a further classification of the entity classification "funds". One service list ID can correspond to a plurality of entity classifications and a plurality of entity IDs, one entity classification can correspond to a plurality of unreported modules, one entity ID can also correspond to a plurality of unreported modules, and one unreported module can correspond to a plurality of entity field names.

In the embodiment of the present invention, the correction value is located in the last column of the table, and it is to be understood that the embodiment of the present invention is not limited thereto, and the correction value may be located in any column of the table or any other position.

The template may be stored in the form of an excel table, and correspondingly, the data table for the data to be corrected may also be in the form of an excel table. And aiming at the acquired data table, judging whether the file type of the data table is correct or not, if so, executing the subsequent steps, and otherwise, sending a corresponding prompt.

In some optional cases, the number of instances to be modified in the data table may also be limited to improve the operation efficiency of data modification. After the data table is obtained, whether the number of the to-be-corrected examples in the data table does not exceed a preset number or not can be judged, if not, the subsequent steps are executed, and otherwise, a corresponding prompt can be sent out.

In some optional cases, a formatting process may be performed on the contents in the retrieved data table to facilitate the execution of the subsequent steps. Furthermore, an identifier may be added to each formatted to-be-corrected instance, so as to facilitate subsequent query of the to-be-corrected instance.

In step S120, the content of the to-be-corrected instance in the data table is checked.

The content of each item in the example to be corrected can be checked, and when the content of each item passes the check, the example to be corrected is determined to pass the check, otherwise, the example to be corrected is determined not to pass the check.

In step S130, for the to-be-corrected instance that passes the check, the field value corresponding to the first field name is updated with the correction value.

The data correction method provided by the embodiment of the invention can be used for verifying the content of the example to be corrected of the data table of the data to be corrected and correcting the data of the example to be corrected which passes the verification, so that the data to be corrected can be modified in batch, the error data can be quickly corrected, and the service flow and the service state do not need to be changed.

The following describes an execution process for checking the contents of the to-be-corrected example in the data table, respectively for the business to-do item and the business entity item.

Fig. 2 is a schematic flow chart illustrating a process of checking the content of the to-be-corrected example in a case that the data table is a data table of the business to-do-things in an embodiment. As shown in fig. 2, in the case that the data table is a data table of business backlog, the checking the content of the to-be-corrected instance in the data table may include steps S210 to S220.

In step S210, the existence and association of each item in the data item in the business process to which the first field name belongs are checked from the corresponding storage table.

First, checking for presence is described. For example, a city ID storage table may be queried for whether the city ID is present, and if so, a check to determine the presence of a city ID passes, otherwise a prompt may be output regarding "city ID not found". A system ID storage table may be queried for the presence of the system ID, and if so, a check to determine the presence of the system ID is passed, otherwise a prompt may be output regarding "system ID not found". The service list number storage table may be queried whether the service list number exists, and if the service list number exists, the check of the existence of the service list number is determined to pass, otherwise, a prompt about "no service list number found" may be output. Whether the service list ID exists can be inquired in a service table, if yes, the verification of the existence of the service list ID is determined to pass, otherwise, a prompt of 'service list ID is not found' can be output. Whether the to-do ID exists can be inquired from the to-do table, if yes, the verification of the existence of the to-do ID is determined to be passed, and otherwise, a prompt about 'the to-do ID is not found' can be output. Whether the to-do item exists can be inquired from the to-do table, if yes, the checking of the existence of the to-do item is determined to be passed, otherwise, a prompt about 'no to-do item found' can be output. The tables corresponding to the respective items each store content relating to the corresponding item. The check of the existence of the items may be performed in sequence, and in case the check of the existence of one of the items fails, the check of the subsequent item may not be performed any more.

The checking for relevance is presented next. In the contents with the correction example in the data table about the business backlog, the city ID and the system ID have an association, and the system ID and the business form ID have an association. The city ID associated with the system ID may be searched in a system ID storage table, whether the city ID associated with the system ID in the system ID storage table is the same as the city ID in the example to be corrected is determined, if so, it is determined that the checking of the association between the city ID and the system ID is passed, otherwise, it is determined that the checking is not passed, and a prompt about "failure of association between the city ID and the system ID" may be output. The system ID associated with the service ticket ID may be queried in a service table, and it is determined whether the system ID associated with the service ticket ID in the service table is the same as the system ID in the to-be-corrected instance, if so, it is determined that the correlation check between the system ID and the service ticket ID passes, otherwise, it is determined that the check does not pass, and a prompt about "failure in correlation between the system ID and the service ticket ID" may be output. Similarly, the checking of associations may be performed in sequence, and in the event that one of the associations fails, the checking of the other associations may not be performed.

In step S220, if the existence and relevance of each item pass the verification, the first to-do field name and the field type of the correction value are verified. This may include steps S221 to S224.

In step S221, the to-do field configuration corresponding to the to-do ID and the to-do item is searched from the to-do field configuration table.

The to-do field configuration comprises a second to-do field name and a field type of a field value corresponding to the second to-do field name.

The to-do field configuration table stores to-do field configurations which are uniquely corresponding to the to-do IDs and the to-do items. The to-do field configuration may include one or more to-do field names and a field type of a field value corresponding to each to-do field name. That is, the second to-do field name may include one or more to-do field names.

In step S222, it is determined whether the first to-do field name matches the second to-do field name.

For example, in a case that the second to-do field name includes a to-do field name, it may be determined whether the first to-do field name and the second to-do field name are equal to each other, and if the first to-do field name and the second to-do field name are equal to each other, it is determined that the first to-do field name and the second to-do field name match each other, otherwise, it is determined that the first to-. When the second to-do field name includes a plurality of to-do field names, it may be determined whether the plurality of to-do field names included in the second to-do field name have the to-do field name equal to the first to-do field name, and if so, it is determined that the to-do field names match with each other, otherwise, it is determined that the to-do field names do not match with each other.

In the case where the first to-do field name and the second to-do field name do not match, the subsequent steps are not performed any more, and a prompt about "the first to-do field name is error data" may be output.

In step S223, when the first to-do field name matches the second to-do field name, it is determined whether the field type of the correction value matches the field type of the field value corresponding to the second to-do field.

For example, the field type of the field value corresponding to the second to-do field may be a date type, an amount type, or the like. For example, if the field type of the field value corresponding to the second to-do field is a date type, and the field type of the modified value is also a date type, it may be determined that the two match.

In the case where the field type of the correction value does not match the field type of the field value corresponding to the second to-do field, the subsequent steps are not performed any more, and a prompt about "field type error of correction value" may be output.

In step S224, in a case that the field type of the modification value matches the field type of the field value corresponding to the second to-do field, it is determined that the content checked by the to-be-modified instance passes.

The above steps may be performed in turn for each instance to be modified. After the content of the to-be-corrected example passes the verification, the to-be-corrected example can be determined to pass the verification, and the subsequent updating step can be executed.

In some optional embodiments, in the case that the data table is a data table of business backlogs, the data table may include a plurality of instances to be corrected. In this case, when the contents of the multiple instances to be corrected are checked, the existence and the relevance of each item in the data item in the business process to which the first field name belongs in each instance to be corrected may be checked in sequence. For the multiple to-be-corrected instances for which the existence and relevance checks of the items pass, the multiple to-be-corrected instances for which the existence and relevance checks of the items pass may be grouped according to the to-be-handled ID. The first to-do field name and the field type of the correction value may then be batch checked according to the grouped sets. For example, the to-do field configuration may be queried in batch from the to-do field configuration table by using the to-do ID and all the to-do items in the group for the to-do ID, and then the first to-do field name and the field type of the modification value belonging to the same group may be checked in batch according to the queried to-do field configuration, so that the execution efficiency may be improved.

In the case that the data table is a data table of business entity matters, when the content of the to-be-corrected instance in the data table is checked, the existence and the association of each item in the data item in the business process to which the first field name belongs may be checked from the corresponding storage table first.

First, checking for presence is described. For example, a city ID storage table may be queried for whether the city ID is present, and if so, a check to determine the presence of a city ID passes, otherwise a prompt may be output regarding "city ID not found". A system ID storage table may be queried for the presence of the system ID, and if so, a check to determine the presence of the system ID is passed, otherwise a prompt may be output regarding "system ID not found". The service list number storage table may be queried whether the service list number exists, and if the service list number exists, the check of the existence of the service list number is determined to pass, otherwise, a prompt about "no service list number found" may be output. Whether the service list ID exists can be inquired in a service table, if yes, the verification of the existence of the service list ID is determined to pass, otherwise, a prompt of 'service list ID is not found' can be output. A query may be made from the entity table as to whether the entity classification is present, and if so, a check may be passed to determine the presence of the entity classification, otherwise, a prompt may be output regarding "no entity classification found". An entity table may be queried as to whether the entity ID is present, and if so, a check to determine the presence of the entity ID passes, otherwise a prompt may be output regarding "entity ID not found". Whether the module which is not reported is available or not can be inquired from the entity table, if yes, the verification of the existence of the module which is not reported is determined to pass, otherwise, a prompt of 'module which is not reported to be available' can be output. A query may be made from the entity table as to whether the entity field name is present, and if so, a check to determine the presence of the entity field name passes, otherwise a prompt may be output regarding "entity field name not found". The tables corresponding to the respective items each store content relating to the corresponding item. The check of the existence of the items may be performed in sequence, and in case the check of the existence of one of the items fails, the check of the subsequent item may not be performed any more.

The checking for relevance is presented next. In the contents with correction example in the data table about the business entity matters, the city ID and the system ID have an association, and the system ID and the business order ID have an association. The city ID associated with the system ID may be searched in a system ID storage table, whether the city ID associated with the system ID in the system ID storage table is the same as the city ID in the example to be corrected is determined, if so, it is determined that the checking of the association between the city ID and the system ID is passed, otherwise, it is determined that the checking is not passed, and a prompt about "failure of association between the city ID and the system ID" may be output. The system ID associated with the service ticket ID may be queried in a service table, and it is determined whether the system ID associated with the service ticket ID in the service table is the same as the system ID in the to-be-corrected instance, if so, it is determined that the correlation check between the system ID and the service ticket ID passes, otherwise, it is determined that the check does not pass, and a prompt about "failure in correlation between the system ID and the service ticket ID" may be output. Similarly, the checking of associations may be performed in sequence, and in the event that one of the associations fails, the checking of the other associations may not be performed.

And in the case that the existence and relevance check on each item passes, determining that the content of the example to be corrected passes, and performing a subsequent updating step.

Next, an execution process of updating the field value corresponding to the first field name using the modification value is described for the business backlog and the business entity transaction, respectively.

And under the condition that the data table is a data table of business backlogs, for the to-be-corrected example passing the verification, querying the to-be-corrected field name in the to-be-corrected example from the to-be-corrected field data table by using the to-be-corrected ID in the to-be-corrected example. The to-do field data table stores the to-do field name for each to-do ID, however, not all the to-do field names for each to-do ID stored in the to-do field configuration table will appear in the to-do field data table, because in some cases, some of the to-do field names are not assigned, and these to-do field names that are not assigned will not appear in the to-do field data table. The to-do field data table is used for storing the to-do field name for the to-do ID and the corresponding field value of the to-do field name. And under the condition that the name of the field to be handled is inquired, updating the field value corresponding to the name of the field to be handled into the corrected value. In this manner, the updating of the data value is completed. By using the mode of first query and then update, the generation of deadlock in program operation can be avoided.

Fig. 3 is a schematic flow chart illustrating updating using a correction value in the case where the data table is a data table of a business entity transaction in the embodiment. As shown in fig. 3, in the case that the data table is a data table of business entity transactions, updating the field value corresponding to the first field name by using the correction value for the to-be-corrected instance passing the check may include steps S310 to S340.

In step S310, the city ID and the first entity field name are used to query configuration information of the first entity field name from an entity table.

The entity table may have stored therein configuration information unique to the city ID and the entity field name. The configuration information may include a classification of the first entity field name, wherein the classification of the first entity field name includes one or more of: capital, house, business, personnel information.

In step S320, it is determined whether the queried category of the first entity field name is the same as the entity category in the to-do instance.

If not, the subsequent steps may not be executed, and a prompt about "entity field name classification error" may be output.

In step S330, in the case that the classification of the first entity field name is the same as the entity classification, the first entity field name is queried in the list corresponding to the entity classification using the business form ID for the classification of the money, the house, and the business, and the first entity field name is queried in the list corresponding to the entity classification using the entity ID for the classification of the person information.

The list corresponding to the fund classification is a fund list, and a business form ID, each entity field name related to the fund for the business form ID, and a field value corresponding to each entity field name may be stored in the fund list. The list corresponding to the house classification is a house list, and the house list may store a service ticket ID, each entity field name related to a house corresponding to the service ticket ID, and a field value corresponding to each entity field name, which may be, for example, a house area, a house orientation, or the like. The list corresponding to the service classification is a service list, and the service list may store the service form ID, each entity field name related to the service for the service form ID, and a field value corresponding to each entity field name, where the entity field name may be, for example, a result of loan approval. The fund list, the house list, and the service list have information uniquely corresponding to the service ticket ID. Thus, the first entity field name is queried in a list corresponding to the entity classification using the business form ID for the classifications of the funds, the premises, and the business.

The list corresponding to the personnel information classification is a personnel information list, and the personnel information list stores entity IDs, entity field names related to the personnel aiming at the entity IDs, and field values respectively corresponding to the entity field names, wherein the entity field names comprise personnel names, personnel contact telephones and the like. The person information list stores information uniquely corresponding to the entity ID. Thus, the first entity field name is queried in a list corresponding to the entity classification using the entity ID for the classification of the person information.

In step S340, if the first entity field name is found, the field value corresponding to the first entity field name is updated to the modified value.

And inquiring the first entity field name, which is equivalent to checking the existence of the first entity field name, if the first entity field name is inquired, the existence check of the first entity field name is passed, and under the condition, updating the field value corresponding to the first entity field name into the corrected value. When updating field values in the fund list and the house list, if the correction value is an extension field, the old information and the correction value need to be merged and then updated.

In the case that the first entity field name is not queried, a prompt may be output regarding "query less entity field name". The mode of firstly inquiring and then updating is adopted, which is equivalent to that the existence of the first entity field name is checked, and the accuracy of data correction is ensured.

And under the condition that the data table is a data table of business entity matters, the data table can comprise a plurality of examples to be corrected, the examples to be corrected can be grouped according to the business single ID, and the field value corresponding to the first field name is updated in batch by using the correction value according to the grouped groups. For example, the first entity field name may be queried in bulk using a business form ID in a list (e.g., funds list, house list, business list) corresponding to the entity category. And then, updating the field value of the inquired first entity field name in batch, thereby improving the data correction efficiency. Optionally, for the update of the staff information, entity IDs may be used for grouping, the first entity field names belonging to the same entity ID are queried in batch in the staff information list, and then the field values of the queried first entity field names are updated in batch, so that the data correction efficiency is improved.

In an optional embodiment, the data modification method provided in the embodiment of the present invention may further include notifying a service requiring synchronization, including a retrieval event and/or a visualization event, of each set of system ID and service order ID of the to-be-modified instance for which data modification is completed. The retrieval event and the visual event are data corresponding to the business order ID read in batch through the system ID and the business order ID, so that the system ID and the business order ID with data correction only need to be notified to the retrieval event and the visual event respectively after the data correction is finished. Optionally, all the system IDs and service list IDs with data modification may be traversed, and the system IDs and service list IDs of the examples to be modified are subjected to deduplication processing, for example, if the system IDs and service list IDs of the two examples with data modification are the same, deduplication needs to be performed, so as to obtain non-duplicated system IDs and service list IDs. And sequentially notifying each group of system ID and business order ID to the retrieval event and/or the visual event, wherein after the group of system ID and business order ID are notified, a preset time period is set to separate, and then the next group of notification is performed, so that the time for reading the data corresponding to the business order ID in batch through the system ID and the business order ID is reserved for the retrieval event and/or the visual event. Wherein the preset time can be set to any suitable value according to the requirement, for example, can be set to 10 ms. The service needing synchronization is informed of the system ID and the service list ID with data change, so that the services can read correct data in time conveniently.

In an optional embodiment, the data correction method provided in the embodiment of the present invention may further include sending a prompt about successful completion of data correction when each to-be-corrected instance in the data table successfully completes data correction. The prompt can be sent in any suitable way, for example, the prompt can be sent to a terminal interface in a text message way, or can be sent in a mail and/or short message way, so that a user can know that the data correction is successfully completed in time.

In an optional embodiment, the data correction method provided in the embodiment of the present invention may further include sending a prompt about a reason why the data correction failed when there is an example to be corrected in the data table in which the data correction is not successfully completed. As previously described, each time a verification, query or match is performed without success, a corresponding prompt may be output. Or, in the case that each time the verification, the query, or the matching is not successful, the corresponding error reason may be recorded, for example, a table about error information may be established, and once an error occurs in a certain to-be-corrected instance, the content of the to-be-corrected instance in which the error occurs is extracted from the table, and a list of descriptions about the error reason is added. And after the data correction method is executed, outputting the form about the error information so as to facilitate the user to check and correct the examples.

Fig. 4 is a block diagram showing a configuration of a data correction apparatus according to an embodiment of the present invention. As shown in fig. 4, an embodiment of the present invention further provides a data correction apparatus, where the data correction apparatus may include: an obtaining module 410, configured to obtain a data table for data to be corrected, where the data table includes one or more instances to be corrected, where a content of the instance to be corrected includes a correction value, a first field name corresponding to the correction value, and a data item in a service ticket to which the first field name belongs; a checking module 420, configured to check the content of the to-be-corrected instance in the data table; and an updating module 430, configured to update, for the to-be-corrected instance that passes the verification, a field value corresponding to the first field name using the correction value, where, in a case that the data table is a data table of business backlogs, the first field name is a first to-be-handled field name, and a data item in a business process to which the first field name belongs includes one or more of the following items: city ID, system ID, business order number, business order ID, ID to be handled and items to be handled; and/or in the case that the data table is a data table of business entity matters, the first field name is a first entity field name, and the data items in the business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, entity classification, entity ID and non-reporting module. The data correction device provided by the embodiment of the invention can be used for verifying the content of the example to be corrected of the data table of the data to be corrected and correcting the data of the example to be corrected which passes the verification, so that the data to be corrected can be modified in batch, the error data can be quickly corrected, and the service process and the service state do not need to be changed.

In some optional embodiments, in a case that the data table is a data table of business backlogs, the checking module is configured to check the content of the to-be-corrected instance in the data table according to the following steps: checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table; in the case that the checking of the existence and the relevance of each item passes, checking the first to-do field name and the field type of the correction value includes: searching a to-be-handled field configuration corresponding to the to-be-handled ID and the to-be-handled item from a to-be-handled field configuration table, wherein the to-be-handled field configuration comprises a second to-be-handled field name and a field type of a field value corresponding to the second to-be-handled field name; judging whether the first to-be-handled field name is matched with the second to-be-handled field name; under the condition that the first to-be-handled field name is matched with the second to-be-handled field name, judging whether the field type of the corrected value is matched with the field type of the field value corresponding to the second to-be-handled field; and determining that the content of the example to be corrected passes the verification under the condition that the field type of the corrected value is matched with the field type of the field value corresponding to the second field to be handled. After the content of the to-be-corrected example passes the verification, it can be determined that the to-be-corrected example passes the verification, and a subsequent updating process can be executed.

In some optional embodiments, in a case that the data table is a service backlog data table, the checking module is configured to: under the condition that the data table comprises a plurality of examples to be corrected, aiming at the plurality of examples to be corrected, the existence and the relevance of each item of which pass the verification, grouping the plurality of examples to be corrected, the existence and the relevance of which pass the verification, according to the ID to be handled; and carrying out batch verification on the first to-be-processed field name and the field type of the correction value according to the grouped group. For example, the to-do field configuration may be queried in batch from the to-do field configuration table by using the to-do ID and all the to-do items in the group for the to-do ID, and then the first to-do field name and the field type of the modification value belonging to the same group may be checked in batch according to the queried to-do field configuration, so that the execution efficiency may be improved.

In some optional embodiments, in a case that the data table is a data table of business backlogs, the updating module is configured to update the field value corresponding to the first field name with the correction value for the to-be-corrected instance that passes the verification according to the following steps: inquiring the name of the field to be handled from a field data table to be handled by using the ID to be handled; and under the condition that the name of the field to be handled is inquired, updating the field value corresponding to the name of the field to be handled into the corrected value. By using the mode of first query and then update, the generation of deadlock in program operation can be avoided.

In some optional embodiments, in a case that the data table is a data table of business entity transactions, the checking module is configured to check the content of the to-be-corrected instance in the data table according to the following steps: checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table; and determining that the content of the instance to be corrected passes the verification if the existence and relevance of the items pass the verification. And in the case that the existence and relevance check of each item passes, determining that the content of the instance to be corrected passes, and performing a subsequent updating process.

In some optional embodiments, in a case that the data table is a data table of business entity transactions, the updating module is configured to update the field value corresponding to the first field name with the correction value for the to-be-corrected instance that passes the check according to the following steps: querying, from an entity table, configuration information for the first entity field name using the city ID and the first entity field name, the configuration information including a classification of the first entity field name, wherein the classification of the first entity field name includes one or more of: capital, house, business, personnel information; judging whether the classification of the first entity field name is the same as the entity classification; in a case where the classification of the first entity field name is the same as the entity classification, inquiring the first entity field name in a list corresponding to the entity classification using the business form ID for the classification of the money, the house, and the business, inquiring the first entity field name in a list corresponding to the entity classification using the entity ID for the classification of the person information; and updating the field value corresponding to the first entity field name to the correction value when the first entity field name is inquired. The mode of firstly inquiring and then updating is adopted, which is equivalent to that the existence of the first entity field name is checked, and the accuracy of data correction is ensured.

In some optional embodiments, in a case that the data table is a data table of business entity transactions, the update module is configured to: under the condition that the data table comprises a plurality of examples to be corrected, grouping the plurality of examples to be corrected according to the service list ID aiming at the plurality of examples to be corrected which pass the verification; and updating a field value corresponding to the first field name using the correction value according to the grouped group. For example, the first entity field name may be queried in bulk using a business form ID in a list (e.g., funds list, house list, business list) corresponding to the entity category. And then, updating the field value of the inquired first entity field name in batch, thereby improving the data correction efficiency.

Referring to fig. 5, in some optional embodiments, the apparatus may further comprise: a duplicate removal module 440, configured to perform duplicate removal processing on the system ID and the service ticket ID of the to-be-corrected instance that has completed data correction; and a notification module 450, configured to notify each set of system ID and service order ID after the deduplication processing to a service requiring synchronization, where the service requiring synchronization includes a retrieval event and/or a visualization event. The service needing synchronization is informed of the system ID and the service list ID with data change, so that the services can read correct data in time conveniently.

Referring to fig. 6, in some optional embodiments, the apparatus may further include a first sending module 460, configured to send a prompt about successful completion of data correction if each to-be-corrected instance in the data table successfully completes data correction. The prompt can be sent in any suitable way, for example, the prompt can be sent to a terminal interface in a text message way, or can be sent in a mail and/or short message way, so that a user can know that the data correction is successfully completed in time.

With further reference to fig. 6, in some optional embodiments, the apparatus may further include a second sending module 470, configured to send a prompt about a reason for a failure of data correction if there is a to-be-corrected instance in the data table for which data correction is not successfully completed. Each time a verification, query or match is performed unsuccessfully, a corresponding prompt may be output. Or, in the case that each time the verification, the query, or the matching is not successful, the corresponding error reason may be recorded, for example, a table about error information may be established, and once an error occurs in a certain to-be-corrected instance, the content of the to-be-corrected instance in which the error occurs is extracted from the table, and a list of descriptions about the error reason is added. And after the data correction method is executed, outputting the form about the error information so as to facilitate the user to check and correct the examples.

The specific working principle and benefits of the data correction device provided by the embodiment of the present invention are the same as those provided by the above-mentioned embodiment of the present invention, and will not be described herein again.

The data correction device may include a processor and a memory, where the modules are stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions.

The processor comprises a kernel, and the kernel calls the corresponding program unit from the memory. The kernel can be set to be one or more, and the data modification method according to any embodiment of the invention is executed by adjusting the kernel parameters.

The memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.

Accordingly, the embodiment of the present invention further provides a machine-readable storage medium, where the machine-readable storage medium has instructions stored thereon, and the instructions are used to enable a machine to execute the data correction method according to any embodiment of the present invention.

Correspondingly, an embodiment of the present invention further provides an electronic device, as shown in fig. 7, the electronic device 70 includes at least one processor 701, and at least one memory 702 and a bus 703, which are connected to the processor 701; the processor 701 and the memory 702 complete mutual communication through a bus 703; the processor 701 is configured to call program instructions in the memory 702 to execute the audio file processing method according to any embodiment of the present invention and/or the audio file playing method according to any embodiment of the present invention. The electronic equipment of the embodiment of the invention can be a server, a PC, a PAD, a mobile phone and the like.

The present application further provides a computer program product adapted to perform a program for initializing the steps of the method as described in any of the embodiments of the present application when executed on a data processing device.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.

The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data correction method, characterized in that the data correction method comprises:

acquiring a data table aiming at data to be corrected, wherein the data table comprises one or more instances to be corrected, the content of the instances to be corrected comprises a correction value, a first field name corresponding to the correction value, and data items in a business list to which the first field name belongs;

checking the content of the example to be corrected in the data table; and

updating a field value corresponding to the first field name using the correction value for the to-be-corrected instance that passes the check,

when the data table is a data table of business backlogs, the first field name is a first backlog field name, and the data items in the business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, ID to be handled and items to be handled; and/or

In the case that the data table is a data table of business entity matters, the first field name is a first entity field name, and the data items in the business process to which the first field name belongs include one or more of the following items: city ID, system ID, business order number, business order ID, entity classification, entity ID, non-reporting module,

wherein, in a case that the data table is a data table of business backlogs, updating, by using the correction value, the field value corresponding to the first field name for the to-be-corrected instance that passes the verification comprises:

inquiring the name of the field to be handled from a field data table to be handled by using the ID to be handled;

updating the field value corresponding to the to-do field name to the corrected value when the to-do field name is inquired,

and/or, in the case that the data table is a data table of business entity matters, the updating, by using the correction value, the field value corresponding to the first field name for the to-be-corrected instance that passes the check includes:

querying, from an entity table, configuration information for the first entity field name using the city ID and the first entity field name, the configuration information including a classification of the first entity field name, wherein the classification of the first entity field name includes one or more of: capital, house, business, personnel information;

judging whether the classification of the first entity field name is the same as the entity classification;

in a case where the classification of the first entity field name is the same as the entity classification, inquiring the first entity field name in a list corresponding to the entity classification using the business form ID for the classification of the money, the house, and the business, inquiring the first entity field name in a list corresponding to the entity classification using the entity ID for the classification of the person information; and

and updating the field value corresponding to the first entity field name to the correction value when the first entity field name is inquired.

2. The method according to claim 1, wherein in the case that the data table is a business to-do data table, the checking the content of the to-be-modified instance in the data table comprises:

checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table;

in the case that the checking of the existence and the relevance of each item passes, checking the first to-do field name and the field type of the correction value includes:

searching a to-be-handled field configuration corresponding to the to-be-handled ID and the to-be-handled item from a to-be-handled field configuration table, wherein the to-be-handled field configuration comprises a second to-be-handled field name and a field type of a field value corresponding to the second to-be-handled field name;

judging whether the first to-be-handled field name is matched with the second to-be-handled field name;

under the condition that the first to-be-handled field name is matched with the second to-be-handled field name, judging whether the field type of the corrected value is matched with the field type of the field value corresponding to the second to-be-handled field; and

and determining that the content of the example to be corrected passes the verification under the condition that the field type of the corrected value is matched with the field type of the field value corresponding to the second field to be handled.

3. The method according to claim 2, wherein in the case that the data table is a business to-do data table, the checking the content of the to-be-modified instance in the data table comprises:

under the condition that the data table comprises a plurality of examples to be corrected, aiming at the plurality of examples to be corrected, the existence and the relevance of each item of which pass the verification, grouping the plurality of examples to be corrected, the existence and the relevance of which pass the verification, according to the ID to be handled; and

and carrying out batch verification on the first to-be-processed field name and the field type of the correction value according to the grouped group.

4. The method according to claim 1, wherein in the case that the data table is a data table of business entity transactions, the checking the content of the to-be-modified instance in the data table comprises:

checking the existence and relevance of each item in the data item in the business process to which the first field name belongs from the corresponding storage table; and

and determining that the content of the example to be corrected passes the verification under the condition that the existence and relevance of the items pass the verification.

5. The method according to claim 1, wherein in the case that the data table is a data table of business entity transactions, the updating the field value corresponding to the first field name with the correction value for the to-be-corrected instance passing the check comprises:

under the condition that the data table comprises a plurality of examples to be corrected, grouping the plurality of examples to be corrected according to the service list ID aiming at the plurality of examples to be corrected which pass the verification; and

updating a field value corresponding to the first field name using the correction value according to the grouped group.

6. The method of claim 1, further comprising:

carrying out duplicate removal processing on the system ID and the business list ID of the to-be-corrected example which has finished data correction; and

and notifying each set of system ID and service list ID after the deduplication processing to the service needing synchronization, wherein the service needing synchronization comprises a retrieval event and/or a visualization event.

7. The method of claim 1, further comprising:

under the condition that each example to be corrected in the data table successfully completes data correction, sending a prompt about successful completion of data correction; and/or

And sending a prompt about a reason of failure of data correction when the data table has a to-be-corrected example which does not successfully finish the data correction.

8. A data correction apparatus, characterized in that the data correction apparatus comprises:

the data processing device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a data table aiming at data to be corrected, the data table comprises one or more instances to be corrected, the content of the instances to be corrected comprises a correction value, a first field name corresponding to the correction value, and data items in a business list related to the first field name;

the checking module is used for checking the content of the example to be corrected in the data table; and

an updating module, configured to update, for the checked to-be-corrected instance, a field value corresponding to the first field name using the correction value,

wherein, in the case that the data table is a data table of business backlogs, the updating module is configured to update, for the to-be-corrected instance passing the verification, the field value corresponding to the first field name with the correction value according to the following steps:

and/or, in the case that the data table is a data table of business entity matters, the updating module is configured to update, for the checked to-be-corrected instance, the field value corresponding to the first field name with the correction value according to the following steps:

9. The apparatus according to claim 8, wherein in the case that the data table is a business to-do data table, the checking module is configured to check the content of the to-be-modified instance in the data table according to the following steps:

10. The apparatus of claim 9, wherein in the case that the data table is a data table of business backlogs, the checking module is configured to:

11. The apparatus according to claim 8, wherein in the case that the data table is a data table of business entity transactions, the checking module is configured to check the contents of the to-be-modified instance in the data table according to the following steps:

12. The apparatus of claim 8, wherein in the case that the data table is a data table of business entity transactions, the updating module is configured to:

13. The apparatus of claim 8, further comprising:

the duplication removing module is used for carrying out duplication removing processing on the system ID and the business list ID of the to-be-corrected example which is subjected to data correction; and

and the notification module is used for notifying each set of system ID and service list ID after the deduplication processing to the service needing to be synchronized, wherein the service needing to be synchronized comprises a retrieval event and/or a visualization event.

14. The apparatus of claim 8, further comprising:

the first sending module is used for sending a prompt about successful completion of data correction under the condition that each to-be-corrected instance in the data table successfully completes the data correction; and/or

And the second sending module is used for sending a prompt about a reason of data correction failure when the data table has a to-be-corrected example which does not successfully finish data correction.

15. A machine-readable storage medium having stored thereon instructions for causing a machine to perform the data correction method of any one of claims 1 to 7.

16. An electronic device comprising at least one processor, at least one memory connected to the processor, and a bus; the processor and the memory complete mutual communication through the bus; the processor is configured to call program instructions in the memory to perform the data modification method of any one of claims 1 to 7.