Multi-person collaborative data confirmation method and device based on task circulation and medium
Through the multi-person collaborative data confirmation method based on task flow, the problem of grassroots staff difficulty in tracking data sources and update time in data processing is solved, data quality improvement and efficiency improvement is achieved, the audit process is simplified, and data processing is enhanced. Transparency and credibility.
Patent Information
- Application Number
- CN202411176637.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-26
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-08-26
Smart Images

Figure CN119067604A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a multi-person collaborative data confirmation method, device and medium based on task flow. Background Art
[0002] In today's society, with the rapid development of new generation information technology, such as the widespread application of cloud computing, big data, artificial intelligence and other technologies, all walks of life have ushered in unprecedented changes. Especially in the field of grassroots work, these new technologies not only bring potential improvements in work efficiency, but also put forward new requirements for the working methods of grassroots staff. Data processing, as an important part of their daily work, is directly related to service quality and efficiency.
[0003] Traditionally, grassroots staff face many challenges when dealing with large amounts of data and information. On the one hand, they need to ensure the authenticity and accuracy of each piece of data, which is the basis for ensuring effective policy implementation and service quality; on the other hand, due to the lack of effective technical support, staff often find it difficult to quickly and accurately track the source and update time of data, resulting in the need to adopt full confirmation in actual operations, which is not only time-consuming and labor-intensive, but also greatly affects work efficiency. Summary of the invention
[0004] The embodiments of the present application provide a multi-person collaborative data confirmation method, device and medium based on task flow to solve the above technical problems.
[0005] On the one hand, an embodiment of the present application provides a multi-person collaborative data confirmation method based on task flow, including:
[0006] Receive raw data to be processed and determine the credibility of each data source; wherein the credibility of different data sources corresponding to the same data is different;
[0007] Marking the data fields to be confirmed in the original data, publishing the data fields to be confirmed in the form of tasks, and performing data comparison and marking on the designated information in the original data and the designated information in the platform;
[0008] Receive the data field to be confirmed, and coordinate the task corresponding to the data field to be confirmed to other personnel, so as to perform collaborative data confirmation on the data field with the specified mark;
[0009] Change the confirmation status corresponding to the confirmed data, and based on the task submission trigger, aggregate the confirmed data with the confirmation status as confirmed;
[0010] The aggregated confirmed data is sent to the corresponding task issuer, so that the task issuer can review the confirmed data and compare the differences between the original data and the confirmed data.
[0011] In one implementation of the present application, receiving raw data to be processed and determining the credibility of each data source specifically includes:
[0012] Receive the raw data to be processed uploaded by the task publisher, and record the data source and data update frequency corresponding to each data field in the raw data;
[0013] Set corresponding weight coefficients for data sources and data update frequencies respectively, and determine the data sources and data update frequencies corresponding to each data source to determine the credibility corresponding to each data source;
[0014] Among them, the data source corresponding to the data responsible department is the most trusted data source among the data sources, and the credibility is less than or equal to the unit length.
[0015] In one implementation of the present application, marking the data field to be confirmed in the original data so as to publish the data field to be confirmed in a task manner specifically includes:
[0016] The task issuer marks the data field to be confirmed in the original data, and determines the confirmation status corresponding to the marked data field to be confirmed; wherein the confirmation status includes no confirmation required, confirmation required, and confirmed;
[0017] Determine a data field in the original data whose confirmation status is to be confirmed, so as to distribute the data field in the original data whose confirmation status is to be confirmed as a task;
[0018] Determine whether the partition information in the data field to be confirmed matches the partition information of the recipient, and if so, receive the corresponding data through the recipient;
[0019] The data whose confirmation status is confirmed are aggregated, and the aggregated data whose confirmation status is confirmed overwrites the corresponding original data.
[0020] In one implementation of the present application, data comparison and marking of the specified information in the original data and the specified information in the platform specifically include:
[0021] Determine the number of data sources corresponding to the basic information and the business data in the original data respectively, so as to determine the trusted data source corresponding to the basic information or the business data according to the number of data sources;
[0022] Acquire basic information from a trusted data source of the basic information, and acquire business data from a trusted data source corresponding to the business data;
[0023] Determine the update time corresponding to the basic information and the business data in the original data respectively, and determine whether the basic information or the business data in the original data needs to be confirmed according to the relationship between the corresponding update time and the preset validity period;
[0024] The basic information and business data in the original data are compared with the basic information and business data in the corresponding trusted data source to determine whether the basic information and business data in the original data need to be confirmed, and marked according to the confirmation status.
[0025] In one implementation of the present application, respectively determining the number of data sources corresponding to the basic information and the business data in the original data, so as to determine the trusted data source corresponding to the basic information or the business data according to the number of data sources; obtaining the basic information from the trusted data source of the basic information, and obtaining the business data from the trusted data source corresponding to the business data, specifically includes:
[0026] Determine the number of data sources corresponding to the basic information and the business data in the original data, and when the number of data sources corresponding to the basic information and the business data is one, directly obtain the basic information and the business data from the corresponding data source;
[0027] If there are multiple data sources for the basic information and the business data, respectively determine the corresponding credibility data sources for the basic information and the business data from the multiple data sources, and obtain the basic information and the business data from the corresponding credibility data sources;
[0028] The trusted data source is the data source with the highest credibility among the multiple data sources.
[0029] In one implementation of the present application, the basic information and business data in the original data are compared with the basic information and business data in the corresponding trusted data source to determine whether the basic information and business data in the original data need to be confirmed, and marked according to the confirmation status, specifically including:
[0030] Determining whether the basic information and business data in the original data match the basic information and business data in the corresponding trusted data source;
[0031] If so, determining that the basic information and the business data do not need to be confirmed, and marking the basic information and the business data with a marking color corresponding to the need for confirmation;
[0032] If not, it is determined that the basic information and the business data need to be confirmed, and the basic information and the business data are marked with a mark color corresponding to the need for confirmation;
[0033] If the basic information and business data in the original data have no matching data in each data source, the basic information and the business data are marked with a specified color, so as to perform data confirmation on the basic information and the business data based on the specified color.
[0034] In one implementation of the present application, receiving the data field to be confirmed, and coordinating the task corresponding to the data field to be confirmed to other personnel to perform collaborative data confirmation on the data field with the specified mark, specifically includes:
[0035] Receive data confirmation tasks corresponding to the data fields to be confirmed through grassroots staff, and determine other personnel corresponding to the multi-person coordination of the data confirmation tasks, so as to coordinate the data confirmation tasks to the other personnel of the corresponding departments according to the zoning results corresponding to the data to be confirmed;
[0036] When performing data confirmation, the designated mark in the data confirmation task is determined, and the trusted data source corresponding to the mark color that does not need to be confirmed is determined; wherein the designated mark is used to indicate the designated color and the mark color corresponding to the one that needs to be confirmed;
[0037] Confirm the data to be confirmed with the designated mark through the original data and the trusted data source, and if the data in the original data and the trusted data source are both incorrect, manually enter the accurate data;
[0038] According to the entered accurate data, the data to be confirmed of the designated mark is confirmed to obtain the corresponding confirmed data.
[0039] In one implementation of the present application, changing the confirmation status corresponding to the confirmed data specifically includes:
[0040] In the multi-person collaboration interface, change the task status corresponding to the confirmed data to confirmed, and clear the mark color corresponding to the confirmed data;
[0041] When the mark colors corresponding to all the data to be confirmed in the original data are cleared, it is determined that the data confirmation in the original data is completed, and the confirmer and confirmation time corresponding to the confirmed data are displayed.
[0042] On the other hand, the embodiment of the present application further provides a multi-person collaborative data confirmation device based on task flow, the device comprising:
[0043] at least one processor;
[0044] and, a memory communicatively coupled to the at least one processor;
[0045] Among them, the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above-mentioned multi-person collaborative data confirmation method based on task flow.
[0046] On the other hand, an embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions, which, when executed, implements a multi-person collaborative data confirmation method based on task flow as described above.
[0047] The embodiment of the present application provides a multi-person collaborative data confirmation method, device and medium based on task flow, which at least includes the following beneficial effects:
[0048] By determining the credibility of each data source and marking the data fields to be confirmed, the uncertainty and errors in the data can be effectively identified and handled, thereby improving the overall data quality; the data fields to be confirmed are published in the form of tasks, and other personnel are coordinated to confirm the data, which promotes cooperation and communication among team members and improves data processing efficiency; the summary of confirmed data is triggered by task submission and sent to the task publisher for review, which simplifies the data review process and makes the review process more efficient and orderly; comparing and marking the specified information in the original data with the specified information in the platform helps to discover and resolve data inconsistencies and improve data consistency and accuracy; by comparing the differences between the original data and the confirmed data, you can clearly understand the changes in the data during the processing process, which facilitates the tracking and analysis of data differences; the entire data processing process, including data confirmation, status changes, data aggregation and review, is traceable and transparent, enhancing the transparency and credibility of data processing. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0050] Figure 1 A flowchart of a multi-person collaborative data confirmation method based on task flow provided in an embodiment of the present application;
[0051] Figure 2 A schematic diagram of the internal structure of a multi-person collaborative data confirmation device based on task flow provided in an embodiment of the present application. DETAILED DESCRIPTION
[0052] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.
[0053] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.
[0054] Figure 1 A flowchart of a multi-person collaborative data confirmation method based on task flow is provided in an embodiment of the present application.
[0055] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For the convenience of understanding and description, the following embodiments are described in detail by taking a server as an example.
[0056] It should be noted that the server may be a single device or a system consisting of multiple devices, that is, a distributed server, and this application does not make any specific limitation on this.
[0057] like Figure 1 As shown, a multi-person collaborative data confirmation method based on task flow is provided in an embodiment of the present application, including:
[0058] 101. Receive raw data to be processed, and determine the credibility of each data source; wherein the credibility of different data sources corresponding to the same data is different.
[0059] Specifically, in one embodiment of the present application, the server receives raw data to be processed and determines the credibility of each data source, specifically including:
[0060] Receive the raw data to be processed uploaded by the task publisher, and record the data source and data update frequency corresponding to each data field in the raw data;
[0061] Set corresponding weight coefficients for data sources and data update frequencies respectively, and determine the data sources and data update frequencies corresponding to each data source to determine the corresponding credibility of each data source;
[0062] Among them, the data source corresponding to the data responsible department is the most trusted data source among all data sources, and the credibility is less than or equal to the unit length.
[0063] In one embodiment, the credibility of each data source is set, and the credibility of the data sources of the same data cannot be the same. For example, basic population information exists in four data sources A, B, C, and D at the same time, then the data source shared by the data authority department is the most credible data source of the data, and the credibility of other data sources can be defined based on comprehensive indicators such as data source and update frequency. The credibility value is represented by R. The maximum value of R is 1.
[0064] The original data to be confirmed prepared by the task publisher includes basic information and business information. Taking population data as an example, the information to be confirmed includes regional information Q (q1, q2, q3, ... qn), basic population information and B (b1, b2, b3, ... bn), and business information Y (y1, y2, y3, ... yn).
[0065] In one embodiment, suppose the task publisher uploads a set of raw data about product sales, including data fields such as product name, sales volume, and sales date. The system records the data source and data update frequency corresponding to each data field. For example, the product name comes from the product management department and is updated once a week; the sales volume comes from the sales department and is updated once a day; the sales date comes from the finance department and is updated once a month.
[0066] Set corresponding weight coefficients for data sources and data update frequency. Assume that the weight coefficient of data source is 0.6 and the weight coefficient of data update frequency is 0.4. Calculate the credibility of each data source based on the weight coefficient and the data source and data update frequency corresponding to each data source. For example, the credibility of the data source of the product management department is 0.6 (data source weight) 1 (department weight) + 0.4 (update frequency weight) 0.5 (updated once a week) = 0.7; the credibility of the data source of the sales department is 0.61 + 0.41 (updated once a day) = 1; the credibility of the data source of the finance department is 0.61 + 0.40.25 (updated once a month) = 0.7. In this example, the data source of the sales department is the most credible data source because its credibility is the highest, which is 1.
[0067] 102. Mark the data fields to be confirmed in the original data, publish the data fields to be confirmed in the form of tasks, and compare and mark the specified information in the original data with the specified information in the platform.
[0068] Specifically, the server marks the data field to be confirmed in the original data, and publishes the data field to be confirmed in the form of a task, which specifically includes:
[0069] The task publisher marks the data field to be confirmed in the original data, and determines the confirmation status corresponding to the marked data field to be confirmed; the confirmation status includes no confirmation required, confirmation required, and confirmed;
[0070] Determine the data field to be confirmed whose confirmation status is to be confirmed in the original data, so as to distribute the data field to be confirmed whose confirmation status is to be confirmed as a task;
[0071] Determine whether the zone information in the data field to be confirmed matches the zone information of the recipient, and if so, receive the corresponding data through the recipient;
[0072] The data whose confirmation status is confirmed are summarized, and the corresponding original data are overwritten by the summarized data whose confirmation status is confirmed.
[0073] In one embodiment, the task publisher needs to mark the data fields that need to be confirmed. After marking the data fields, the system automatically records the confirmation status C of the corresponding data. When C=0, no confirmation is required, and when C=1, confirmation is required. When the staff confirms the data, the confirmation status C=2.
[0074] The original data snapshot is saved, which cannot be modified. At the same time, the original data is converted into data to be confirmed, which will be distributed as a task. At the same time, the confirmed data is aggregated and overwritten with the original data. The system compares the division information Q in the information to be confirmed with the division information Q1 of the recipient. If Q=Q1, the corresponding data is received. In this way, the recipient can only receive data from the division to which he belongs.
[0075] In one embodiment, suppose the task publisher uploads a set of raw data on sales performance in various regions across the country, including data fields such as region, sales, and sales date. The task publisher marks the sales data fields of some regions in the raw data as pending confirmation because these data may be questionable or require further verification. The system determines the confirmation status corresponding to the marked data fields to be confirmed. In this example, the confirmation status of the marked data fields is set to "need to be confirmed".
[0076] The system identifies the data fields to be confirmed in the original data with a confirmation status of "need to be confirmed" and distributes these fields as tasks. Each task contains the data fields to be confirmed and related context information so that the recipient can better understand the task and confirm it.
[0077] When assigning tasks, the system considers whether the region information in the data field to be confirmed matches the region information of the recipient. For example, if the data field to be confirmed is about the sales in Beijing, the system will assign this task to the recipient whose region is Beijing. After receiving the task, the recipient can check the data field to be confirmed and confirm it based on his knowledge and experience.
[0078] Once the recipient completes the data confirmation task, the system will update the confirmation status to "Confirmed". The system will summarize the data with the confirmation status of "Confirmed" and generate a new data set. This new data set will overwrite the corresponding part of the original data to be confirmed, thereby updating the entire data set and ensuring its accuracy. Finally, the system can provide the updated data set to the task issuer or other relevant personnel for further analysis or use.
[0079] In one embodiment of the present application, the server compares and marks the specified information in the original data with the specified information in the platform, specifically including:
[0080] Determine the number of data sources corresponding to the basic information and business data in the original data respectively, and determine the trusted data source corresponding to the basic information or business data according to the number of data sources;
[0081] Obtaining basic information from a trusted data source for basic information, and obtaining business data from a trusted data source corresponding to the business data;
[0082] Determine the update time corresponding to the basic information and business data in the original data respectively, and determine whether the basic information or business data in the original data needs to be confirmed based on the relationship between the corresponding update time and the preset validity period;
[0083] The basic information and business data in the original data are compared with the basic information and business data in the corresponding trusted data source to determine whether the basic information and business data in the original data need to be confirmed, and marked according to the confirmation status.
[0084] In one embodiment, assume that there is an e-commerce platform that needs to regularly update its product information, including basic product information (such as name, category, brand, etc.) and business data (such as sales, evaluation, inventory, etc.). In order to ensure the accuracy of the data, the platform uses a data confirmation system.
[0085] The platform first counted the number of data sources corresponding to basic information and business data. For example, product names may come from multiple data sources such as suppliers, product editing departments, and user feedback; while sales data mainly comes from the sales department and order system. Based on the number of data sources, the platform determined the trusted data sources corresponding to basic information and business data. For example, for product names, the data sources provided by suppliers are the largest and are considered to be the most accurate, so they are selected as trusted data sources; for sales data, the data source of the sales department is considered to be trusted.
[0086] After determining the trusted data source, the platform obtains the basic information of the product from the supplier data source, such as name, category, brand, etc. At the same time, the platform also obtains the business data of the product, such as sales, evaluation, inventory, etc., from the data source of the sales department.
[0087] The platform records the update time of basic information and business data in the trusted data source. For example, the supplier last updated the product name last Wednesday, and the sales department last updated the sales volume today. The platform sets a preset validity period, such as 7 days. For data updated within this validity period, the platform considers it accurate and does not need to be confirmed; for data updated after the validity period, the platform considers it may need to be confirmed. Based on this rule, the platform determines which basic information and business data need to be confirmed. For example, if the product name is updated for more than 7 days, then the name needs to be confirmed whether it is still accurate.
[0088] The platform compares the basic information and business data in the original data with the data in the corresponding trusted data source. For example, the platform compares whether the product name in the original data is consistent with the name in the supplier data source; and compares whether the sales volume in the original data is consistent with the sales volume in the sales department data source. Based on the comparison results, the platform marks the basic information and business data in the original data with the confirmation status. For example, if the product name is consistent, it is marked as "no confirmation required"; if the sales volume is inconsistent, it is marked as "need to be confirmed".
[0089] In one embodiment of the present application, the server determines the number of data sources corresponding to the basic information and the business data in the original data, respectively, to determine the trusted data source corresponding to the basic information or the business data according to the number of data sources; obtaining the basic information from the trusted data source of the basic information, and obtaining the business data from the trusted data source corresponding to the business data, specifically including:
[0090] Determine the number of data sources corresponding to the basic information and business data in the original data, and when the number of data sources corresponding to the basic information and business data is one, directly obtain the basic information and business data from the corresponding data source;
[0091] If there are multiple data sources for both basic information and business data, then corresponding trustworthy data sources for basic information and business data are determined from the multiple data sources, and the basic information and business data are obtained from the corresponding trustworthy data sources;
[0092] Among them, the trusted data source is the data source with the highest credibility among multiple data sources.
[0093] In one embodiment, it is assumed that a financial service platform needs to integrate its customers' basic information and transaction data. In order to ensure the accuracy and reliability of the data, the platform uses a data integration system that obtains data based on the number and credibility of data sources.
[0094] For the basic information of customers (such as name, ID number, contact information, etc.), the platform found that this data came from only one data source, that is, the information filled in by the customer when registering. Since there is only one data source for basic information, the platform directly obtained the basic information of customers from this data source without further credibility assessment.
[0095] For the customer's transaction business data (such as transaction amount, transaction time, counterparty, etc.), the platform found that this data comes from multiple data sources, including the customer's self-service transaction system, bank docking system, and third-party payment system. In this case, the platform needs to determine which data source is credible. By evaluating factors such as the historical accuracy, update frequency, and authority of the data source of each data source, the platform determined the bank docking system as the credible data source for transaction business data because its data accuracy and update frequency are relatively high. After determining the credible data source, the platform obtained the customer's transaction business data from the bank docking system.
[0096] The platform integrates the basic information and business data obtained to form a complete customer data file. This data is used in multiple business scenarios such as customer analysis, risk assessment, and transaction monitoring, providing strong support for the operation of the financial service platform.
[0097] In one embodiment of the present application, the server compares the basic information and business data in the original data with the basic information and business data in the corresponding trusted data source to determine whether the basic information and business data in the original data need to be confirmed, and marks them according to the confirmation status, specifically including:
[0098] Determine whether the basic information and business data in the original data match the basic information and business data in the corresponding trusted data source;
[0099] If so, it is determined that the basic information and business data do not need to be confirmed, and the basic information and business data are marked with a mark color corresponding to the mark color that does not need to be confirmed;
[0100] If not, it is determined that the basic information and business data need to be confirmed, and the basic information and business data are marked with the corresponding mark color for confirmation;
[0101] If the basic information and business data in the original data have no matching data in each data source, the basic information and business data are marked with a specified color to perform data confirmation on the basic information and business data based on the specified color.
[0102] In one embodiment, data comparison is performed to compare basic information B in the original data with basic information B1 in the platform, business data Y with Y1 in the business system interface connected to the platform, and the comparison results are marked.
[0103] Verify the data source of B1. If B1 has only one data source, directly obtain the data from that data source. If B1 exists in multiple data sources, then according to the credibility R of the data source, take the data source with the largest R value. Verify the update time of B1. Each field has the most recent update time D and the validity period V. Assuming the current time is D0, determine the relationship between D0-D and V. If D0-D≥V, mark it in orange. If D0-D<V, mark it in green. Green means no confirmation is required, and orange means confirmation is required. Compare the basic information B in the original data with the data value of the basic information B1 in the trusted data source. If B=B1, mark it in green. If B≠B1, mark it in red. Green means no confirmation is required, and red means confirmation is required.
[0104] Verify the data source of Y1. If Y1 has only one data source, directly obtain the data from that data source. If Y1 exists in multiple data sources, then according to the credibility R of the data source, select the data source with the largest R value. Verify the update time of Y1. Each field has the most recent update time D and the validity period V. Assuming the current time is D0, determine the relationship between D0-D and V. If D0-D≥V, mark it in orange. If D0-D<V, mark it in green. Green means no confirmation is required, and orange means confirmation is required. Compare the basic information Y in the original data with the data value of the basic information Y1 in the trusted data source. If Y=Y1, mark it in green. If Y≠Y1, mark it in red. Green means no confirmation is required, and red means confirmation is required.
[0105] If some data in the original data has no matching data in each data source, it will be marked in purple, and purple requires data confirmation. The above data is compared by polling, and the priority of each color mark is purple> red> orange> green. That is, if a piece of data is compared multiple times and the results include multiple colors, it will be displayed in the color with the highest priority. Data that does not need to be confirmed is marked in gray.
[0106] 103. Receive the data field to be confirmed, and coordinate the task corresponding to the data field to be confirmed to other personnel, so as to perform collaborative data confirmation on the data field with the specified mark.
[0107] Specifically, in one embodiment of the present application, the server receives the data field to be confirmed, and coordinates the task corresponding to the data field to be confirmed to other personnel, so as to perform collaborative data confirmation on the data field with the specified mark, specifically including:
[0108] Receive data confirmation tasks corresponding to the data fields to be confirmed through grassroots staff, and determine other personnel corresponding to the data confirmation tasks to coordinate the data confirmation tasks to other personnel in the corresponding departments according to the zoning results corresponding to the data to be confirmed;
[0109] When performing data confirmation, the designated mark in the data confirmation task is determined, and the trusted data source corresponding to the mark color that does not need to be confirmed is determined; wherein the designated mark is used to indicate the designated color and the mark color corresponding to the mark that needs to be confirmed;
[0110] Confirm the data to be confirmed with the specified mark through the original data and the trusted data source. If the data in both the original data and the trusted data source are incorrect, manually enter the accurate data;
[0111] According to the accurate data after input, confirm the data to be confirmed with the specified mark to obtain the corresponding confirmed data.
[0112] In one embodiment, when a grassroots staff member receives a data confirmation task, he or she can coordinate the task with other personnel to jointly confirm the data. When coordinating tasks, data is no longer distributed by region, that is, the full amount of coordinated data can be viewed.
[0113] When confirming data, grassroots staff only need to confirm the data marked with purple, red and orange. At the same time, the system will show the staff the color-marked trusted data sources, the specific data corresponding to the trusted data sources, and the update time. The staff can select an accurate data after verifying the original data and the data in the trusted data source. If the data in both the original data and the trusted data source are inaccurate after verification, the staff can manually enter the accurate data.
[0114] 104. Change the confirmation status corresponding to the confirmed data, and based on the task submission trigger, summarize the confirmed data with the confirmation status as confirmed.
[0115] Specifically, in one embodiment of the present application, the server changes the confirmation status corresponding to the confirmed data, specifically including:
[0116] In the multi-person collaboration interface, change the task status corresponding to the confirmed data to confirmed, and clear the mark color corresponding to the confirmed data;
[0117] When the mark colors corresponding to all the data to be confirmed in the original data are cleared, it is determined that the data confirmation in the original data is completed, and the confirmer and confirmation time corresponding to the confirmed data are displayed.
[0118] In one embodiment, assume that an e-commerce platform needs to regularly update its product information, including basic product information (such as name, category, brand, etc.) and business data (such as inventory, price, sales, etc.). In order to ensure the accuracy of the data, the platform uses a multi-person collaborative data confirmation system.
[0119] The platform provides a multi-person collaborative interface for product information update tasks, allowing employees from different departments to jointly participate in data confirmation. When an employee completes the confirmation of a piece of data, he / she can change the task status of the data to "confirmed" on the collaborative interface. At the same time, the system will automatically clear the mark color corresponding to the confirmed data to indicate that the data has completed the confirmation process.
[0120] When all the marked colors corresponding to the data to be confirmed in the original data are cleared, the system determines that the data confirmation work in this batch of original data has been completed. At this time, the system will display the confirmer and confirmation time corresponding to the confirmed data to track the data update history and confirmation responsibility.
[0121] Assume that a batch of new products are put on the e-commerce platform. The product information department enters the basic information and business data of these new products into the system and marks them as pending confirmation. Subsequently, employees from the product review department, price management department, and inventory management department log in to the multi-person collaboration interface to confirm the data they are responsible for. Whenever a department completes data confirmation, they will change the task status to "confirmed" on the collaboration interface and clear the corresponding mark color. When all the data to be confirmed are cleared, the system prompts that the product information update task is completed and displays the confirmer and confirmation time of each confirmed data.
[0122] 105. Send the aggregated confirmed data to the corresponding task issuer, so that the task issuer can review the confirmed data and compare the differences between the original data and the confirmed data.
[0123] When a worker submits a task, the confirmed data will be automatically aggregated to the task publisher. In a multi-person collaborative task, if one of them submits the task, the task is deemed submitted. The data in the submitted task cannot be confirmed.
[0124] The task publisher receives the confirmed data and supports reviewing the confirmed data. Data that fails the review can be marked as pending and rejected. After rejection, the task returns to the task release as it was submitted before. If rejection is not required, the task publisher can use the data comparison function to compare the difference between the original data snapshot and the confirmed data. This completes the data confirmation process.
[0125] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, the embodiment of this application also provides a multi-person collaborative data confirmation device based on task flow, and its structure is as follows: Figure 2 shown.
[0126] Figure 2 The internal structure diagram of a multi-person collaborative data confirmation device based on task flow provided in an embodiment of the present application. Figure 2 As shown, the device includes:
[0127] at least one processor;
[0128] and, a memory communicatively coupled to the at least one processor;
[0129] The memory stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable the at least one processor to:
[0130] Receive raw data to be processed and determine the credibility of each data source; wherein the credibility of different data sources corresponding to the same data is different;
[0131] Mark the data fields to be confirmed in the original data, publish the data fields to be confirmed in the form of tasks, and compare and mark the specified information in the original data with the specified information in the platform;
[0132] Receive data fields to be confirmed, and coordinate tasks corresponding to the data fields to be confirmed to other personnel to perform collaborative data confirmation on data fields with specified tags;
[0133] Change the confirmation status corresponding to the confirmed data, and based on the task submission trigger, aggregate the confirmed data with the confirmation status as confirmed;
[0134] The aggregated confirmed data is sent to the corresponding task issuer so that the task issuer can review the confirmed data and compare the differences between the original data and the confirmed data.
[0135] The present application also provides a non-volatile computer storage medium storing computer executable instructions. When the computer executable instructions are executed, they can:
[0136] Receive raw data to be processed and determine the credibility of each data source; wherein the credibility of different data sources corresponding to the same data is different;
[0137] Mark the data fields to be confirmed in the original data, publish the data fields to be confirmed in the form of tasks, and compare and mark the specified information in the original data with the specified information in the platform;
[0138] Receive data fields to be confirmed, and coordinate tasks corresponding to the data fields to be confirmed to other personnel to perform collaborative data confirmation on data fields with specified tags;
[0139] Change the confirmation status corresponding to the confirmed data, and based on the task submission trigger, aggregate the confirmed data with the confirmation status as confirmed;
[0140] The aggregated confirmed data is sent to the corresponding task issuer so that the task issuer can review the confirmed data and compare the differences between the original data and the confirmed data.
[0141] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.
[0142] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0143] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.
[0144] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0145] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0146] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0147] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0148] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0149] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0150] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0151] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0152] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. 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 multi-person collaborative data confirmation method based on task flow, characterized in that: The method comprises: Receive raw data to be processed and determine the credibility of each data source; wherein the credibility of different data sources corresponding to the same data is different; Marking the data fields to be confirmed in the original data, publishing the data fields to be confirmed in the form of tasks, and performing data comparison and marking on the designated information in the original data and the designated information in the platform; Receive the data field to be confirmed, and coordinate the task corresponding to the data field to be confirmed to other personnel, so as to perform collaborative data confirmation on the data field with the specified mark; Change the confirmation status corresponding to the confirmed data, and based on the task submission trigger, aggregate the confirmed data with the confirmation status as confirmed; The aggregated confirmed data is sent to the corresponding task issuer, so that the task issuer can review the confirmed data and compare the differences between the original data and the confirmed data.
2. According to the method of multi-person collaborative data confirmation based on task flow in claim 1, it is characterized in that: Receive the raw data to be processed and determine the credibility of each data source, including: Receive the raw data to be processed uploaded by the task publisher, and record the data source and data update frequency corresponding to each data field in the raw data; Set corresponding weight coefficients for data sources and data update frequencies respectively, and determine the data sources and data update frequencies corresponding to each data source to determine the corresponding credibility of each data source; Among them, the data source corresponding to the data responsibility department is the most trusted data source among the data sources, and the credibility is less than or equal to the unit length.
3. According to the method of multi-person collaborative data confirmation based on task flow in claim 1, it is characterized in that: Marking the data field to be confirmed in the original data to publish the data field to be confirmed in the form of a task, specifically including: The task issuer marks the data field to be confirmed in the original data, and determines the confirmation status corresponding to the marked data field to be confirmed; wherein the confirmation status includes no confirmation required, confirmation required, and confirmed; Determine a data field in the original data whose confirmation status is to be confirmed, so as to distribute the data field in the original data whose confirmation status is to be confirmed as a task; Determine whether the partition information in the to-be-confirmed data field matches the partition information of the recipient, and if so, receive the corresponding data through the recipient; The data whose confirmation status is confirmed are aggregated, and the aggregated data whose confirmation status is confirmed overwrites the corresponding original data.
4. According to the method of multi-person collaborative data confirmation based on task flow in claim 1, it is characterized in that: Comparing and marking the specified information in the original data with the specified information in the platform, specifically including: Determine the number of data sources corresponding to the basic information and the business data in the original data respectively, so as to determine the trusted data source corresponding to the basic information or the business data according to the number of data sources; Acquire basic information from a trusted data source of the basic information, and acquire business data from a trusted data source corresponding to the business data; Determine the update time corresponding to the basic information and the business data in the original data respectively, and determine whether the basic information or the business data in the original data needs to be confirmed according to the relationship between the corresponding update time and the preset validity period; The basic information and business data in the original data are compared with the basic information and business data in the corresponding trusted data source to determine whether the basic information and business data in the original data need to be confirmed, and marked according to the confirmation status.
5. The multi-person collaborative data confirmation method based on task flow according to claim 4 is characterized in that: Determine the number of data sources corresponding to the basic information and the business data in the original data respectively, so as to determine the trusted data source corresponding to the basic information or the business data according to the number of data sources; Acquiring basic information from a trusted data source of the basic information, and acquiring business data from a trusted data source corresponding to the business data, specifically includes: Determine the number of data sources corresponding to the basic information and the business data in the original data, and when the number of data sources corresponding to the basic information and the business data is one, directly obtain the basic information and the business data from the corresponding data source; If there are multiple data sources for the basic information and the business data, respectively determine the corresponding credibility data sources for the basic information and the business data from the multiple data sources, and obtain the basic information and the business data from the corresponding credibility data sources; The trusted data source is the data source with the highest credibility among the multiple data sources.
6. The multi-person collaborative data confirmation method based on task flow according to claim 4 is characterized in that: The basic information and business data in the original data are compared with the basic information and business data in the corresponding trusted data source to determine whether the basic information and business data in the original data need to be confirmed, and marked according to the confirmation status, specifically including: Determining whether the basic information and business data in the original data match the basic information and business data in the corresponding trusted data source; If so, determining that the basic information and the business data do not need to be confirmed, and marking the basic information and the business data with a marking color corresponding to the need for confirmation; If not, it is determined that the basic information and the business data need to be confirmed, and the basic information and the business data are marked with a mark color corresponding to the need for confirmation; If the basic information and business data in the original data have no matching data in each data source, the basic information and the business data are marked with a specified color, so as to perform data confirmation on the basic information and the business data based on the specified color.
7. The multi-person collaborative data confirmation method based on task flow according to claim 1 is characterized in that: Receiving the data field to be confirmed, and coordinating the task corresponding to the data field to be confirmed to other personnel, so as to perform collaborative data confirmation on the data field with the specified mark, specifically including: Receive data confirmation tasks corresponding to the data fields to be confirmed through grassroots staff, and determine other personnel corresponding to the multi-person coordination of the data confirmation tasks, so as to coordinate the data confirmation tasks to the other personnel of the corresponding departments according to the zoning results corresponding to the data to be confirmed; When performing data confirmation, the designated mark in the data confirmation task is determined, and the trusted data source corresponding to the mark color that does not need to be confirmed is determined; wherein the designated mark is used to indicate the designated color and the mark color corresponding to the one that needs to be confirmed; Confirm the data to be confirmed with the designated mark through the original data and the trusted data source, and if the data in the original data and the trusted data source are both incorrect, manually enter the accurate data; According to the entered accurate data, the data to be confirmed of the designated mark is confirmed to obtain the corresponding confirmed data.
8. The multi-person collaborative data confirmation method based on task flow according to claim 1 is characterized in that: Change the confirmation status of the confirmed data, including: In the multi-person collaboration interface, change the task status corresponding to the confirmed data to confirmed, and clear the mark color corresponding to the confirmed data; When the mark colors corresponding to all the data to be confirmed in the original data are cleared, it is determined that the data confirmation in the original data is completed, and the confirmer and confirmation time corresponding to the confirmed data are displayed.
9. A multi-person collaborative data confirmation device based on task flow, characterized in that: The device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; Wherein, the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a multi-person collaborative data confirmation method based on task flow as described in any one of claims 1-8.
10. A non-volatile computer storage medium storing computer executable instructions, characterized in that: When the computer executable instructions are executed, a multi-person collaborative data confirmation method based on task flow as described in any one of claims 1 to 8 is implemented.
Citation Information
Patent Citations
Data synchronization method and device based on update time and primary key and medium
CN114741401A
Comprehensive energy enterprise data governance method and system based on data indexes
CN115269578A
Multi-source heterogeneous data increment synchronization method and system, storage medium and electronic equipment
CN115757629A
Multi-platform message data calibration method, system and device and storage medium
CN116069520A
Government affair database management method and device and computer readable storage medium
CN117331909A
