Data collection method, device, computer equipment and storage medium

Abstract

The present application relates to the field of data processing and discloses a data collection method, apparatus, computer equipment, and storage medium, including: when a setting operation for a data collection task is detected on a task configuration interface, generating a task configuration record and a task contact person record based on the setting operation; generating a task execution record based on the task configuration record, and generating a contact person execution record for each task contact person based on the task contact person record and the task execution record; if the current time reaches the task start time indicated in the task execution record, sending a task reminder message to the contact person terminal of each task contact person; receiving a reference data table sent by each contact person terminal of each task contact person, and merging the contents of each reference data table to obtain a summary data table. This can realize automated data collection and improve data collection efficiency. The present application relates to blockchain technology, and for example, the above data can be written into the blockchain for use in scenarios such as data collection.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a data collection method, apparatus, computer equipment, and storage medium. Background Art

[0002] In daily work, there is often a need to use Excel spreadsheets for data collection, such as collecting monthly reporting data from various institutions, the completion status of each person's daily tasks, and so on. Due to the variety of data forms collected, currently, the task initiator usually sends the data to the corresponding counterpart via email. The email contains a fixed template form. Then, the task counterpart downloads the template Excel spreadsheet, fills in the data to be collected according to the template, and then replies via email. The task initiator then manually summarizes the data in the task counterpart's Excel spreadsheet. This data collection method involves searching for Excel spreadsheets, opening Excel spreadsheets, extracting the content in Excel spreadsheets, and then summarizing the content in all Excel spreadsheets manually. This operation is quite cumbersome, time-consuming, and labor-intensive, and it is also easy to make mistakes during sorting, which cannot improve work efficiency. Summary of the Invention

[0003] The embodiments of the present application provide a data collection method, apparatus, computer equipment, and storage medium, which can realize automated data collection, solve tedious and error-prone manual operations, and improve work efficiency.

[0004] In a first aspect, an embodiment of the present application discloses a data collection method, the method comprising:

[0005] When a setting operation for a data collection task is detected on the task configuration interface, a task configuration record and a task contact person record of the data collection task are generated based on the setting operation, wherein the task contact person record is used to record contact person information of multiple task contact persons of the data collection task;

[0006] Generate a task execution record for the data collection task according to the task configuration record, and generate a contact person execution record for each task contact person based on the task contact person record and the task execution record;

[0007] If the current time reaches the task start time indicated in the task execution record, a task reminder message is sent to the counterpart terminal of each task counterpart, and the task reminder message is used to instruct each task counterpart to fill in the corresponding content in the data table template;

[0008] Receive the reference data tables sent by the counterpart terminals of each task counterpart, and merge the contents of each reference data table to obtain a summary data table. Any reference data table is a data table generated after filling in the content of the data table template.

[0009] In a second aspect, an embodiment of the present application discloses a data collection device, comprising:

[0010] A first generating unit is configured to, when detecting a setting operation for a data collection task on a task configuration interface, generate a task configuration record and a task contact person record for the data collection task based on the setting operation, wherein the task contact person record is used to record contact person information of multiple task contact persons for the data collection task;

[0011] A second generating unit is configured to generate a task execution record of the data collection task according to the task configuration record, and generate a contact person execution record for each task contact person based on the task contact person record and the task execution record;

[0012] a sending unit, configured to send a task reminder message to a terminal of each task counterpart if the current time reaches the task start time indicated in the task execution record, wherein the task reminder message is used to instruct each task counterpart to fill in the corresponding content in the data table template;

[0013] The merging unit is used to receive the reference data tables sent by the counterpart terminals of each task counterpart, and merge the contents of each reference data table to obtain a summary data table. Any reference data table is a data table generated after filling in the content of the data table template.

[0014] In a third aspect, an embodiment of the present application discloses a computer device comprising a processor and a memory, wherein the memory is used to store a computer program, the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the method of the first aspect above.

[0015] In a fourth aspect, an embodiment of the present application discloses a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the method of the first aspect mentioned above.

[0016] In an embodiment of the present application, when a setting operation for a data collection task is detected on a task configuration interface, a task configuration record and a task contact person record for the data collection task can be generated based on the setting operation; further, a task execution record for the data collection task can be generated based on the task configuration record, and a contact person execution record for each task contact person can be generated based on the task contact person record and the task execution record. If the current time reaches the task start time indicated in the task execution record, a task prompt message for each task contact person can be sent to the contact person terminal of each task contact person to instruct each task contact person to fill in the corresponding content in the data table template. Then, a reference data table generated after filling in the content in the data table template sent by each task contact person terminal can be received, and the contents of each reference data table can be merged to obtain a summary data table. By implementing the above method, automated data collection can be achieved, solving tedious and error-prone manual operations, improving work efficiency, and reducing the labor cost and maintenance cost caused by manual operations; by receiving the data tables submitted by each task contact person and then aggregating them, data isolation can also be achieved to improve data security and confidentiality. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0018] Figure 1 This is a flow chart of a data collection method provided in an embodiment of the present application;

[0019] Figure 2 This is a structural diagram of determining a task configuration record and a task contact person record provided by an embodiment of the present application;

[0020] Figure 3a This is a flow chart of a data collection method provided in an embodiment of the present application;

[0021] Figure 3b This is a flow chart of a data collection method provided in an embodiment of the present application;

[0022] Figure 3c This is a flow chart of a data collection method provided in an embodiment of the present application;

[0023] Figure 4 This is a structural diagram of a data collection device provided in an embodiment of the present application;

[0024] Figure 5It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0026] In order to collect data from multiple users using a data table, an embodiment of the present application provides a data collection method. The general principle of this data collection method is as follows: when a setting operation for a data collection task is detected on a task configuration interface, a task configuration record and a task contact person record for the data collection task can be generated based on the setting operation; further, a task execution record for the data collection task can be generated based on the task configuration record, and a contact person execution record for each task contact person can be generated based on the task contact person record and the task execution record. If the current time reaches the task start time indicated in the task execution record, a task prompt message can be sent to the contact person terminal of each task contact person to instruct each task contact person to fill in the corresponding content in the data table template. Then, a reference data table generated after filling in the content in the data table template sent by each task contact person terminal can be received, and the contents of each reference data table can be merged to obtain a summary data table. By implementing the above method, automated data collection can be achieved, eliminating tedious and error-prone manual operations, improving work efficiency, and reducing the labor and maintenance costs caused by manual operations. By receiving the data tables submitted by each task contact person and then aggregating them, data isolation can also be achieved to improve data security and confidentiality.

[0027] In a specific implementation, the execution subject of the above-mentioned data collection method can be a computer device, which can be a terminal or a server. The terminal mentioned here can be a device such as a smart phone, tablet computer, laptop computer, desktop computer, etc., and can also be a peripheral device such as a handle, touch screen, etc.; the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, etc.

[0028] The following is a detailed description of the implementation details of the technical solution of the embodiment of the present application:

[0029] See Figure 1 , Figure 1 : This is a flow chart of a data collection method provided in an embodiment of the present application. The data collection method can be executed by the computer device mentioned above, which can be a terminal or a server. For ease of explanation, the embodiment of the present application uses a computer device executing the data collection method as an example. The data collection method includes the following steps:

[0030] S101: When a setting operation for a data collection task is detected on a task configuration interface, a task configuration record and a task contact person record of the data collection task are generated based on the setting operation.

[0031] Among them, the data collection task may refer to a task that requires the use of a data table (such as an Excel table) to summarize data. For example, the data collection task may be a task to collect basic information of students, a task to collect the daily work completion status of employees, and so on. The task configuration record can be used to record the information required for the data collection task, such as the task start time, task end time, etc. The task contact person record can be used to record the contact person information of multiple task contact persons for the data collection task, such as the name of the task contact person, etc. The task contact person in this application may refer to a user. The task contact person may specifically refer to a user required to perform a task collection task, or a user who needs to fill in a data table corresponding to the data collection task. For information about task configuration records and task contact person records, please refer to the following detailed description.

[0032] In one implementation, the task initiator can perform relevant setting operations through the task configuration interface output by the terminal, so that the computer device can detect the setting operation for the data collection task on the task configuration interface, and generate a task configuration record and a task contact person record for the data collection task based on the setting operation. The task configuration interface can be used by the task initiator to configure the task information required for a data collection task. Among them, the task initiator in this application can refer to the user, specifically the user who created the data collection task. For example, see Figure 2As shown: the terminal used by the task initiator can display a task configuration interface on the terminal screen for the task initiator to configure the task information. The task configuration interface can include at least a task information setting area marked by 201, and a confirmation control marked by 202. If the task initiator needs to create a data collection task, the task information related to this data collection task can be entered in the task information setting area 201. For example, the task information setting area 201 may include the following setting items: task name setting item, start time setting item, end (deadline) time setting item, data table template setting item, task contact person setting item, information receiving method setting item, and may also include other setting items, which are not limited in this application.

[0033] Among them, the task name setting item is used for the task initiator to enter the task name (such as student information collection); the start time setting item is used for the task initiator to enter the task start time of the data collection task (such as 2020.1.1); the end time setting item is used for the task initiator to enter the task end time of the data collection task (such as 2020.1.5); the data table template setting item is used for the task initiator to enter the data table template (such as Template 5, which shows the data table template identifier. The data table identifier can refer to the name of the data table template or other display methods), so that the subsequent task counterpart can download the data table template and fill in the content; the task counterpart setting item is used for the task initiator to enter the task counterpart, for example, the task counterpart's name (such as Zhang San, Li Si, Wang Wu), work number, etc. can be entered; the information receiving method setting item is used for the task initiator to enter the information receiving method of the task counterpart's terminal, so that the task counterpart can use this information receiving method to send information to the task counterpart in the future, for example, the task counterpart's email address (such as 123xxx@qq.com), mobile phone number, etc.

[0034] Then, the task initiator can input the corresponding information in the various setting items mentioned above, and then perform a trigger operation (such as a click operation, a press operation, etc.) on the confirmation control 202, thereby triggering the terminal used by the task initiator to obtain the relevant task information in the task information setting area 201 and upload it to the computer device, so that the computer device can generate a task configuration record and a task contact person record for the data collection task based on the obtained task information.

[0035] Optionally, the task configuration record and task contact person record can be added to the existing task configuration table and task contact person table, respectively. It is understood that when a user needs to perform a data collection task, they can configure the required task information on the task configuration interface. Then, when the computer device detects the task information entered by the user, it can add corresponding records to the task configuration table and task contact person table, respectively, to achieve orderly and unified management of multiple data collection tasks.

[0036] For example, the task configuration table may record the task information to be configured for each data collection task, and the task configuration table may be as shown in Table 1:

[0037] Table 1

[0038] Task configuration identifier Task Name Data table template logo Start time End Time xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx 005 Student Information Collection Template 5 2020.1.1 2020.1.5

[0039] As shown in Table 1, the data in row 4 of the table may be a task configuration record for a data collection task, and the task configuration record may include a task configuration identifier, task name, data table template identifier, start time, and end time for a data collection task. The task name, data table template identifier, start time, and end time may be obtained based on the task information entered by the task initiator on the task configuration interface; the task configuration identifier may be an identifier for the current data collection task automatically generated by the computer device after obtaining the task information configured by the task initiator, and the identifier may be used to indicate the current data collection task. It is understandable that each task collection task has a corresponding unique task configuration identifier.

[0040] For example, the task contact person table can record the contact person information of each data collection task. The task contact person table can be shown in Table 2:

[0041] Table 2

[0042]

[0043] It should be noted that, for the task docking person table, it can be a task collection task associated with a task docking person table, or it can be multiple task collection tasks associated with a task docking person table, which is not limited in this application. Assuming that a task collection task is associated with a task docking person table as an example, the above Table 2 can be understood as the task docking person table corresponding to the current data collection task, and the data recorded in the task docking person table is the task docking person record corresponding to the current data collection task. The task docking person record includes a task configuration identifier for a data collection task, a task docking person identifier, and a method for receiving information from the task docking person. Among them, the task docking person identifier and the method for receiving information from the task docking person can be obtained based on the task information entered by the task initiator on the task configuration interface. For example, the task docking person identifier can specifically be the name of the task docking person (such as Zhang San, Wang Wu), and the method for receiving information can be an email address (such as 123xxx@qq.com). The task configuration identifier is consistent with the task configuration identifier in the task configuration record, so that the corresponding data collection task can be found based on the task configuration identifier.

[0044] As can be seen, by setting up the task configuration table and the task contact person table, different data collection tasks initiated by the task initiator (which can be the same user or different users) can be centrally managed. Usually, each data collection task can use a different data table template, have different task contact persons, and have different start and end times, etc. Therefore, through the task configuration table and the task contact person table, you can clearly understand the relevant information corresponding to each data collection task, which facilitates the management of multiple data collection tasks and facilitates subsequent information queries.

[0045] S102: Generate a task execution record for the data collection task according to the task configuration record, and generate a counterparty execution record for each task counterparty based on the task counterparty record and the task execution record.

[0046] Among them, the task execution record can be used to record the task progress of the data collection task, and the contact person execution record can be used to record the task progress of the task contact person.

[0047] In one implementation, a task execution record for a data collection task can be generated based on a task configuration record. The task execution record may include a task instance identifier, a task instance name, a task configuration identifier, a start time, an end time, a task status, a merged file identifier, and the like, and may also include other data, which is not limited in this application. The task instance identifier may be an identifier automatically generated by a computer device when it detects the creation of a data collection task, and is used to indicate the data collection task; the task instance name may also be automatically generated, or it may be the task name in the task configuration record; the task configuration identifier, the start time, and the end time may all be obtained from the task configuration record. The task status is used to indicate the task progress of the data collection task, and the task status may include not started, in progress, and ended. The initial state of the task status (i.e., the current time is the start time) may be not started. As the data collection task progresses, the task status may be automatically updated to in progress or ended according to the degree of progress of the task; the merged file identifier may be a file identifier generated based on the summary data table after the data collection task is completed, i.e., after the summary data table is generated.

[0048] In one implementation, the docking person execution record of each task docking person can be generated based on the task docking person record and the task execution record. For each task docking person's docking person execution record, the docking person's task execution record may include a subtask instance identifier, a task instance identifier, a task instance name, a task docking person identifier, a submission status, a submission file identifier, a submission time, etc., and may also include other data, which is not limited in this application. Among them, the subtask instance identifier can be an identifier automatically generated by a computer device when it detects the creation of a data collection task. The identifier can uniquely indicate each data collection task performed by the task docking person, that is, if a task docking person corresponds to multiple data collection tasks, then the task docking person corresponds to a unique subtask instance identifier for different data collection tasks. The task instance identifier and the task instance name can be obtained from the task execution record, and the task docking person identifier can be obtained from the task docking person record. The submission status indicates the task progress of the task coordinator. The submission status can be either "Submitted" or "Submitted." The initial submission status is "Unsubmitted." As the data collection task progresses, the submission status can be automatically updated to "Submitted" based on the task coordinator's progress. The submission file identifier can be a file identifier generated based on the reference data sheet after the task coordinator submits the reference data sheet (i.e., generated by filling in the corresponding information in the data sheet template). The submission time can refer to the time when the computer device receives the reference data sheet.

[0049] Optionally, task execution records and contact person execution records can be added to existing task execution tables and contact person execution tables, respectively. That is, after the computer device generates a task configuration record and a task contact person record for a data collection task, the task execution record and the contact person execution record can be added to the task execution table and the contact person execution table, respectively, based on the task configuration record and the task contact person record.

[0050] For example, the task execution table may record the data collection status corresponding to each data collection task, and the task execution table may be shown in Table 3:

[0051] Table 3

[0052]

[0053] As shown in Table 3, the data in the fourth row of the table may be a task execution record for a data collection task. The task instance name, task configuration identifier, start time, and end time in the task execution record may be obtained from the task configuration record, and the task instance identifier may be automatically generated. The task status corresponds to the state of not started when the task execution record is generated. Subsequently, as the task progresses, it may be automatically updated to in progress or ended. The merged file identifier is empty when the task execution record is generated (i.e., no data exists at the corresponding position), but is a file identifier that is generated after the summary data table is generated.

[0054] For example, a data collection task may include multiple task counterparts. The counterpart execution table may contain the counterpart execution records of all task counterparts. Each row in the counterpart execution table may be a record of the task execution status of each task counterpart. The counterpart execution table may be shown in Table 4:

[0055] Table 4

[0056]

[0057] As shown in Table 4, each row in the fourth row of the table can be a record of the task execution status of a task liaison in a task collection task, and the subtask instance identifier in the liaison execution record can be automatically generated; the task instance identifier and the task instance name can both be obtained from the task execution record, and these two information can be used to associate the data collection task performed by the task liaison with the current data collection task; the task liaison identifier can be obtained from the task liaison record; the submission status is unsubmitted when the liaison execution record is generated, and when it is detected that the task liaison has submitted the corresponding reference data table, the submission status can be updated to submitted. The submission file identifier can be empty when the liaison execution record is generated (that is, there is no data at the corresponding position). After the task liaison submits the corresponding reference data table, a file identifier can be automatically generated based on the reference data table. The submission time can also be empty when the liaison execution record is generated. After the reference data table is received, the receiving time can be filled into this position.

[0058] S103: If the current time reaches the task start time indicated in the task execution record, task prompt information is sent to the counterpart terminal of each task counterpart.

[0059] Among them, the task prompt information is used to instruct each task coordinator to fill in the corresponding content in the data table template.

[0060] In one implementation, if the current time reaches the task start time indicated in the task execution record (the above-mentioned start time), a task reminder message can be sent to the docking person terminal of each task docking person. Optionally, the task docking person record can include an information receiving method, wherein the information receiving method can refer to an email address, a mobile phone number, etc., and can also include other methods that enable the task docking person to receive information, which is not limited in this application. Based on this, it can be seen that if the current time reaches the task start time indicated in the task execution record, the information receiving method of each task docking person can be determined from the records of each task docking person, so as to send a task reminder message to the docking person terminal of each task docking person in accordance with the determined information receiving method.

[0061] Then, after receiving the task prompt information, the task liaison can download the data table template at the designated location (for example, the task liaison can log in to the data collection system to download the data table template from the system) and fill in the corresponding content in the data table template; after filling in, the task liaison can send the filled-in data table to the computer device through the corresponding liaison terminal, so that the computer device can receive the reference data tables sent by the liaison terminals of each task object person, and perform subsequent data table merging processing, where the reference data table can be understood as the data table template after data filling described above.

[0062] In one implementation, if the current time reaches the task start time indicated in the task execution record, the relevant information in the task execution record can also be updated. For example, the task status in the task execution record can be updated from the first task status to the second task status. Among them, the first task status is used to indicate that the task has not started, for example, the first task status in the task execution record can specifically be "not started"; the second task status is used to indicate that the task has started, for example, the second task status in the task execution record can specifically be "in progress". If the current time reaches the task end time indicated in the task execution record (the above-mentioned end time), the task status in the task execution record can be updated from the second task status to the third task status. Among them, the third task status is used to indicate that the task has ended, for example, the third task status in the task execution record can specifically be "ended". The first task status, the second task status and the third task status can also be other specific descriptions, which are not limited in this application.

[0063] For example, if the task start time is 2021-09-26 and the current time is 2021-09-27, the data collection task has started, and the task status in the task execution record can be updated from "Not Started" to "In Progress." For another example, if the task end time is 2021-09-29 and the current time is 2021-09-30, the data collection task has ended, and the task status in the task execution record can be updated from "In Progress" to "Completed."

[0064] S104: Receive reference data tables sent by the counterpart terminals of the respective task counterparts, and merge the contents of the respective reference data tables to obtain a summary data table.

[0065] Any reference data table may be a data table generated after filling in the content in the data table template.

[0066] In one implementation, after receiving the reference data tables sent by the counterpart terminals of the respective task counterparts, the contents of the respective reference data tables may be merged to obtain a summary data table corresponding to the data collection task.

[0067] Optionally, a specific implementation method for obtaining a summary data table based on each reference data table may be: when a first reference data table is received, the first reference data table may be used as a reference data table to fill the contents of each reference data table subsequently received into the reference data table, thereby obtaining a summary data table. The first reference data table may refer to the first reference data table received by the computer device. Then, when a second reference data table is received, the contents of the second data table may be filled into the first reference data table (i.e., the reference data table) to obtain the filled first reference data table, until the reference data tables sent by the docking person terminals of all task docking persons are received, and the contents of the reference data tables are filled into the reference data table in sequence, thereby obtaining a summary data table.

[0068] Optionally, the method of filling the content of the second reference data table into the reference data table (the first reference data table) may include: associating and acquiring each reference header (the header in the second reference data table may be referred to as a reference header) and the reference data under each reference header (the data corresponding to the reference header may be referred to as reference data) in the second reference data table, that is, when acquiring the reference data under the reference header, the reference header is also acquired. Then, each acquired reference header is sequentially matched with a reference header (the header in the reference data table may be referred to as a reference header) in the reference data table. If a reference header matches a reference header, the reference data corresponding to the reference header may be filled into the corresponding position of the reference header. It should be noted that because the reference data tables are obtained after the data table template is filled with content, the headers of each reference data table and the data table template are consistent, that is, each reference header mentioned above can be matched with a reference header. In one embodiment, when filling the content of the second reference data table into the reference data table, the content of the second reference data table is filled to the end of the current content in the reference data table. In the subsequent process of merging the contents in the received reference data table, the contents in the reference data table can also be filled into the benchmark data table in the above manner. Similarly, the contents in the reference data table received each time can also be filled into the end of the contents in the benchmark data table to ensure the orderliness of the contents in the final benchmark data table.

[0069] For example, assuming that the data collection task is a student information collection task, and the received first reference data table is as shown in Table 5:

[0070] Table 5

[0071]

[0072]

[0073] After receiving the first reference data table shown in Table 5, Table 5 can be used as a reference data table and used for subsequent merging processing. Assume that the received second reference data table is as shown in Table 6:

[0074] Table 6

[0075] Student Name Date of birth Home address Department Contact Li Si 2020.7.10 BB Street communication 125xxxx

[0076] After obtaining the second reference data table shown in Table 6, each reference header in Table 6 (such as student name, date of birth, home address, department, contact information) can be associated with the corresponding reference data (Li Si, 2020.7.10, BB Street, Communication, 125xxxx). After obtaining the content in Table 6, each reference header is matched with the benchmark header in Table 5 in turn. For example, the reference header (such as student name) can be matched with the benchmark header in Table 5. It can be seen that the reference header can be matched with the benchmark header for the student name, and the reference data associated with the reference header for the student name (ie Li Si) can be filled into the corresponding position in Table 6 where the benchmark header is the student name. After matching each reference header with the benchmark header in Table 5 in turn, the benchmark data table after content filling can be obtained. The filled benchmark data table can be shown in Table 7:

[0077] Table 7

[0078] Student Name Date of birth Home address Department Contact Zhang San 2020.1.1 AA Street communication 123xxxx Li Si 2020.7.10 BB Street communication 125xxxx

[0079] Optionally, the specific implementation method for obtaining the summary data table based on each reference data table can also be: a pre-created initial data table can be obtained, and the header in the initial data table is the same as the header in the data table template, so as to ensure that the data to be stored in the data table template in the summary data table finally obtained based on the initial data table is consistent. After obtaining the initial data table, the contents of each reference data table are then filled into the initial data table in sequence according to the order of the reception time of each reference data table to obtain the summary data table. Among them, the specific implementation method for filling the contents of each reference data table into the initial data table can refer to the above-mentioned method of filling the second reference data table into the benchmark data table, which will not be repeated here.

[0080] In one implementation, when a computer device merges the contents of each reference data table, it can merge the contents of each reference data table upon receipt. Alternatively, the computer device can populate the contents of each reference data table into the corresponding header of the baseline data table or initial data table, rather than merging the contents of each reference data table after receiving all reference data tables. This approach avoids cache insufficiency caused by excessive data tables and excessive content. It also speeds up data table merging, thereby improving data collection efficiency.

[0081] In one implementation, after receiving the reference data tables sent by the counterparty terminals of each task counterparty, the counterparty execution record of the task counterparty can also be updated so that the progress of data collection can be understood in real time based on the information in the counterparty execution record. In a specific implementation, for any of the multiple task counterparties, the submission status of the counterparty execution record corresponding to any task counterparty can be updated from a first submission status to a second submission status. The first submission status can be used to indicate that it has not been submitted, and the second submission status can be used to indicate that it has been submitted. In one embodiment, the time when the computer device receives the reference data table and the file identifier of the reference data table can also be saved in the counterparty execution record corresponding to the task counterparty.

[0082] In one implementation, the task initiator can also view the task progress to facilitate understanding of the task progress. Specifically, the task execution record corresponding to the current data collection task can be viewed to determine whether the data collection task has been completed. For example, the task execution record can be checked to see whether the task status is updated to "completed" or whether a summary data table indicator exists. If either of the above two conditions is confirmed, it indicates that the current data collection task has been completed. The task initiator can also download the final summary data table at any time from a designated location. The designated location can be pre-set.

[0083] In one implementation, if the task initiator finds that there are still task counterparts who have not submitted the reference data sheet when checking the task progress, the task initiator can also trigger the task to urge the task so that the task counterparts who have not submitted the reference data sheet can process the corresponding data collection task in a timely manner. Optionally, the task configuration interface can also include a urging control, so that the task counterpart can trigger the urging control, and when the computer device detects that the urging control is triggered, the submission status of each task counterpart can be obtained from the counterpart execution record of each task counterpart. Furthermore, the target task counterpart with a submission status of the first submission status (i.e., unsubmitted) can be determined from the submission status of each task counterpart, and a task prompt message can be sent to the counterpart terminal of the target task counterpart to instruct the target task counterpart to fill in the corresponding content in the data sheet template and upload it.

[0084] In an embodiment of the present application, when a setting operation for a data collection task is detected on a task configuration interface, a task configuration record and a task contact person record for the data collection task can be generated based on the setting operation; further, a task execution record for the data collection task can be generated based on the task configuration record, and a contact person execution record for each task contact person can be generated based on the task contact person record and the task execution record. If the current time reaches the task start time indicated in the task execution record, a task prompt message for each task contact person can be sent to the contact person terminal of each task contact person to instruct each task contact person to fill in the corresponding content in the data table template. Then, a reference data table generated after filling in the content in the data table template sent by each task contact person terminal can be received, and the contents of each reference data table can be merged to obtain a summary data table. By implementing the above method, automated data collection can be achieved, solving tedious and error-prone manual operations, improving work efficiency, and reducing the labor cost and maintenance cost caused by manual operations; by receiving the data tables submitted by each task contact person and then aggregating them, data isolation can also be achieved to improve data security and confidentiality.

[0085] To better understand the data collection method provided in the embodiment of the present application, Figure 3a-3c The process shown is further explained. In a specific implementation scenario, this application can be applied to application software such as a data collection system, and the application software can be used to implement the data collection scenario. The following is an example of applying this application to a data collection system. Figure 3a The process shown is mainly described from the perspective of the task initiator. Figure 3aAs shown, the task initiator can log in to the data collection system (or data collection platform) and create a data collection task in the data collection system. For example, the task information related to the task collection task is configured on the task configuration interface as described above, such as the task contact person's name, email address, data table template, start time, end time, etc. When a setting operation for the data collection task is detected on the task configuration interface, a task configuration record and a task contact person record for the data collection task can be generated based on the setting operation. For example, a task configuration record and a task contact person record can be added to the task configuration table and the task contact person table, respectively.

[0086] Furthermore, a task execution record of a data collection task can be generated based on the task configuration record. Similarly, the task execution record can be newly added to the task execution table. For the task status in the task execution record, if the current time has not reached the task start time indicated in the task execution record, the data collection system can set the initial state of the task status to the first task state (such as not started). As the data collection task proceeds, the data collection system can automatically determine the task status in the task execution record. For example, if the current time reaches the task start time, the data collection system can automatically update the task status in the task execution record from the first task state (such as not started) to the second task state (such as in progress). The docking person execution record of each task docking person can also be generated based on the task docking person record and the task execution record. The docking person execution record of each task docking person can be newly added to the docking person execution table. For the submission status in the docking person execution record of each task docking person, the initial state of the submission status can be unsubmitted.

[0087] After the task initiator successfully creates a data collection task on the data collection system, the data collection system can periodically poll each data collection task created on the data collection system to monitor the progress of each data collection task. Figure 3b As shown, the data collection system can periodically query the start and end times of each row in the task execution table to determine the task status of the task execution records included in the task execution table based on the current time and the queried time, and update the task status based on the determination result. For example, for a task execution record in the task execution table, if the current time reaches the task start time and the task status is not started, the task status can be automatically updated from not started to in progress. If the current time reaches the task end time, the task status can be automatically updated from in progress to ended.

[0088] When querying the start time and end time of each row in the task execution table, it is also possible to determine whether it is necessary to send a task reminder message to the task counterpart's terminal based on the current time and the queried time, so as to instruct the task counterpart to fill in the corresponding content in the data table template. For example, when the current time reaches the start time or the current time is close to the end time, the task reminder message can be sent to the task counterpart's terminal. For example, the task reminder message can be sent in the form of an email to remind the task counterpart to fill in the data table template.

[0089] After the task docking person receives the task prompt information (the task prompt information can be the information sent at the start time), the task docking person can log in to the data collection system and download the data table template corresponding to his or her own data collection task on the data collection system. After the task docking person successfully downloads, the corresponding information can be filled in the downloaded data table template to obtain a reference data table. Then, the task docking person can submit the reference data table on the data collection system. After the data collection system collects the reference data table submitted by the task docking person, the submission file identifier of the reference data table can be automatically generated and saved to the docking person execution record of the task docking person. The submission status in the docking person execution record of the task docking person can also be updated to submitted. After the data collection system receives the reference data tables submitted by all task docking persons in a data collection task, the contents of each reference data table can be merged to obtain a summary data table. After obtaining the summary data table, the file identifier of the summary data table can also be automatically generated and saved to the task execution record.

[0090] like Figure 3c As shown, the task initiator can log in to the data collection system at any time to view the task progress of the data collection task. The data collection system can automatically record the completion status of the data collection task based on the reference data table submitted by each task partner. For example, the completion status can be specifically reflected in the update of the task status in the task execution record and the update of the submission status in the partner execution record. When the task initiator finds that the data collection task has not been completed, he can click the reminder control on the task configuration interface. When the data collection system detects that the reminder control is triggered, it can send a task reminder message (such as an email) to the task partner who has not submitted the reference data table to remind the task partner to fill in the corresponding content in the data table template. After the data collection task is completed, the data collection system can store the corresponding summary data table in the designated location, and the task initiator can also download the summary data table at any time.

[0091] It can be seen that compared with the existing manual data collection solutions that consume a lot of manpower, the customized development and reporting system is not flexible, the cost is high, and the maintenance cost is high, this solution proposes an automatic data collection solution. This application can realize automated data collection and reduce labor costs and maintenance costs; compared with shared editing data, this application can also realize data isolation to improve data security and confidentiality.

[0092] See also Figure 4 , Figure 4 : is a structural diagram of a data collection device provided in an embodiment of the present application. The data collection device includes:

[0093] The first generating unit 401 is configured to, upon detecting a setting operation for a data collection task on a task configuration interface, generate a task configuration record and a task contact person record for the data collection task based on the setting operation, wherein the task contact person record is used to record contact person information of multiple task contact persons for the data collection task;

[0094] A second generating unit 402 is configured to generate a task execution record for the data collection task based on the task configuration record, and generate a contact person execution record for each task contact person based on the task contact person record and the task execution record;

[0095] The sending unit 403 is configured to send a task reminder message to a terminal of each task counterpart if the current time reaches the task start time indicated in the task execution record, wherein the task reminder message is used to instruct each task counterpart to fill in the corresponding content in the data table template;

[0096] The merging unit 404 is used to receive the reference data tables sent by the counterpart terminals of each task counterpart, and merge the contents of each reference data table to obtain a summary data table. Any reference data table is a data table generated after filling in the content of the data table template.

[0097] In one implementation, the merging unit 404 is specifically configured to:

[0098] When a first reference data table is received, the first reference data table is used as a reference data table, wherein the first reference data table is the first reference data table received;

[0099] When the second reference data table is received, the content in the second data table is filled into the reference data table to obtain a summary data table.

[0100] In one implementation, the merging unit 404 is specifically configured to:

[0101] Obtaining a pre-created initial data table, wherein the table header in the initial data table is the same as the table header in the data table template;

[0102] According to the order of receiving time of each reference data table, the contents of each reference data table are sequentially filled into the initial data table to obtain a summary data table.

[0103] In one implementation, the apparatus further includes an updating unit 405, specifically configured to:

[0104] For any one of the multiple task counterparts, updating the submission status of the counterpart execution record corresponding to the any one of the task counterparts from a first submission status to a second submission status;

[0105] The sending time and data table identifier of the reference data table sent by any task coordinator are stored in the coordinator execution record corresponding to any task coordinator.

[0106] In one implementation, the task configuration interface further includes a task urging control, and the device further includes a task urging unit 406, specifically configured to:

[0107] When it is detected that the urging control is triggered, the submission status of each task counterpart is obtained from the counterpart execution record of each task counterpart;

[0108] A target task counterpart whose submission status is the first submission status is determined from the submission statuses of the various task counterparts, and the task prompt information is sent to a counterpart terminal of the target task counterpart.

[0109] In one implementation, the contact person information includes an information receiving method; the sending unit 403 is specifically configured to:

[0110] Determining the information receiving method of each task counterpart from the task counterpart record;

[0111] The task prompt information is sent to the counterpart terminal of each task counterpart according to the information receiving method.

[0112] In one implementation, the updating unit 405 is further configured to:

[0113] Updating the task status in the task execution record from the first task status to the second task status;

[0114] If the current time reaches the task end time indicated in the task execution record, the task status in the task execution record is updated from the second task status to a third task status.

[0115] It is understandable that the functions of the various functional units of the data collection device described in the embodiment of the present application can be based on Figure 1 The specific implementation of the method in the method embodiment can be referred to Figure 1 The relevant description of the method embodiment will not be repeated here.

[0116] In an embodiment of the present application, when the first generating unit 401 detects the setting operation for the data collection task on the task configuration interface, it generates the task configuration record and the task contact person record of the data collection task based on the setting operation, and the task contact person record is used to record the contact person information of multiple task contact persons of the data collection task; the second generating unit 402 generates the task execution record of the data collection task according to the task configuration record, and generates the contact person execution record of each task contact person based on the task contact person record and the task execution record; if the current time reaches the task start time indicated in the task execution record, the sending unit 403 sends a task prompt information to the contact person terminal of each task contact person, and the task prompt information is used to instruct the each task contact person to fill in the corresponding content in the data table template; the merging unit 404 receives the reference data tables sent by the contact person terminals of each task contact person, and merges the contents in each reference data table to obtain a summary data table, and any reference data table is a data table generated after filling in the content in the data table template. By implementing the above method, automated data collection can be achieved, solving tedious and error-prone manual operations and improving work efficiency.

[0117] See also Figure 5 , Figure 5 5 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. The computer device includes: a processor 501, a memory 502, and a network interface 503. The processor 501, the memory 502, and the network interface 503 can exchange data.

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

[0119] The memory 502 may include a read-only memory and a random access memory, and provides program instructions and data to the processor 501. A portion of the memory 502 may also include a random access memory. When the processor 501 calls the program instructions, it is used to execute:

[0120] When a setting operation for a data collection task is detected on the task configuration interface, a task configuration record and a task contact person record of the data collection task are generated based on the setting operation, wherein the task contact person record is used to record contact person information of multiple task contact persons of the data collection task;

[0121] Generate a task execution record for the data collection task according to the task configuration record, and generate a contact person execution record for each task contact person based on the task contact person record and the task execution record;

[0122] If the current time reaches the task start time indicated in the task execution record, a task reminder message is sent to the counterpart terminal of each task counterpart, and the task reminder message is used to instruct each task counterpart to fill in the corresponding content in the data table template;

[0123] Receive the reference data tables sent by the counterpart terminals of each task counterpart, and merge the contents of each reference data table to obtain a summary data table. Any reference data table is a data table generated after filling in the content of the data table template.

[0124] In one implementation, the processor 501 is specifically configured to:

[0125] When a first reference data table is received, the first reference data table is used as a reference data table, wherein the first reference data table is the first reference data table received;

[0126] When the second reference data table is received, the content in the second data table is filled into the reference data table to obtain a summary data table.

[0127] In one implementation, the processor 501 is specifically configured to:

[0128] Obtaining a pre-created initial data table, wherein the table header in the initial data table is the same as the table header in the data table template;

[0129] According to the order of receiving time of each reference data table, the contents of each reference data table are sequentially filled into the initial data table to obtain a summary data table.

[0130] In one implementation, the processor 501 is further configured to:

[0131] For any one of the multiple task counterparts, updating the submission status of the counterpart execution record corresponding to the any one of the task counterparts from a first submission status to a second submission status;

[0132] The sending time and data table identifier of the reference data table sent by any task coordinator are stored in the coordinator execution record corresponding to any task coordinator.

[0133] In one implementation, the task configuration interface further includes a task reminder control, and the processor 501 is further configured to:

[0134] When it is detected that the urging control is triggered, the submission status of each task counterpart is obtained from the counterpart execution record of each task counterpart;

[0135] A target task counterpart whose submission status is the first submission status is determined from the submission statuses of the various task counterparts, and the task prompt information is sent to a counterpart terminal of the target task counterpart.

[0136] In one implementation, the contact person information includes an information receiving method; the processor 501 is specifically configured to:

[0137] Determining the information receiving method of each task counterpart from the task counterpart record;

[0138] The task prompt information is sent to the counterpart terminal of each task counterpart according to the information receiving method.

[0139] In one implementation, the processor 501 is further configured to:

[0140] Updating the task status in the task execution record from the first task status to the second task status;

[0141] If the current time reaches the task end time indicated in the task execution record, the task status in the task execution record is updated from the second task status to a third task status.

[0142] In a specific implementation, the processor 501 and the memory 502 described in the embodiment of the present application can execute the embodiment of the present application. Figure 1 The implementation method described in the data collection method provided can also be used to implement the embodiments of this application Figure 4 The implementation of the described data collection device will not be described in detail here.

[0143] In an embodiment of the present application, the processor 501 can, when detecting a setting operation for a data collection task on a task configuration interface, generate a task configuration record and a task contact person record for the data collection task based on the setting operation, the task contact person record being used to record the contact person information of multiple task contact persons of the data collection task; generate a task execution record for the data collection task based on the task configuration record, and generate a contact person execution record for each task contact person based on the task contact person record and the task execution record; if the current time reaches the task start time indicated in the task execution record, a task prompt message is sent to the contact person terminal of each task contact person, the task prompt message being used to instruct the each task contact person to fill in the corresponding content in the data table template; receive the reference data tables sent by the contact person terminals of each task contact person, and merge the contents in each reference data table to obtain a summary data table, any reference data table being a data table generated after filling in the content in the data table template. By implementing the above method, automated data collection can be achieved, tedious and error-prone manual operations can be solved, and work efficiency can be improved.

[0144] The embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores program instructions, and when the program is executed, it may include the following: Figure 1 Part or all of the steps of the data collection method in the corresponding embodiment.

[0145] It should be noted that for the aforementioned various method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0146] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0147] It should be emphasized that in order to further ensure the privacy and security of the above data, the above data can also be stored in a node of a blockchain. Among them, the blockchain referred to in this application is a new application model of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain is essentially a decentralized database. It is a string of data blocks generated by cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. The blockchain can include the blockchain underlying platform, the platform product service layer, and the application service layer.

[0148] The above is a detailed introduction to a data collection method, device, computer equipment and storage medium provided in the embodiments of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core ideas. At the same time, for those skilled in the art, according to the ideas of the present application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A data collection method, characterized in that: include: When a setting operation for a data collection task is detected on the task configuration interface, a task configuration record and a task contact person record of the data collection task are generated based on the setting operation, wherein the task contact person record is used to record contact person information of multiple task contact persons of the data collection task; Generate a task execution record for the data collection task based on the task configuration record, and generate a contact person execution record for each task contact person based on the task contact person record and the task execution record; the task execution record is used to record the task progress of the data collection task, and the contact person execution record is used to record the task progress of the task contact person; If the current time reaches the task start time indicated in the task execution record, a task reminder message is sent to the counterpart terminal of each task counterpart, and the task reminder message is used to instruct each task counterpart to fill in the corresponding content in the data table template; Receiving reference data tables sent by the counterpart terminals of the respective task counterparts, and merging the contents of the respective reference data tables to obtain a summary data table, wherein any reference data table is a data table generated after the contents of the data table template are filled in; After receiving the reference data tables sent by the counterparty terminals of the respective task counterparties, for any one of the plurality of task counterparties, updating the submission status of the counterparty execution record corresponding to the any one of the plurality of task counterparties from the first submission status to the second submission status; The first submission status is used to indicate that it has not been submitted, and the second submission status is used to indicate that it has been submitted; Saving the sending time and data table identifier of the reference data table sent by any task coordinator in the coordinator execution record corresponding to any task coordinator; When it is detected that the urging control in the task configuration interface is triggered, the submission status of each task counterpart is obtained from the counterpart execution record of each task counterpart; the target task counterpart whose submission status is the first submission status is determined from the submission status of each task counterpart, and the task prompt information is sent to the counterpart terminal of the target task counterpart.

2. The method according to claim 1, characterized in that The contents of each reference data table are merged to obtain a summary data table, including: When a first reference data table is received, the first reference data table is used as a reference data table, wherein the first reference data table is the first reference data table received; When the second reference data table is received, the content in the second reference data table is filled into the benchmark data table to obtain a summary data table.

3. The method according to claim 1, characterized in that The contents of each reference data table are merged to obtain a summary data table, including: Obtaining a pre-created initial data table, wherein the table header in the initial data table is the same as the table header in the data table template; According to the order of receiving time of each reference data table, the contents of each reference data table are sequentially filled into the initial data table to obtain a summary data table.

4. The method according to claim 1, wherein The contact person information includes an information receiving method; the sending of task prompt information to the contact person terminal of each task contact person includes: Determining the information receiving method of each task counterpart from the task counterpart record; The task prompt information is sent to the counterpart terminal of each task counterpart according to the information receiving method.

5. The method according to claim 1, wherein If the current time reaches the task start time indicated in the task execution record, the method further includes: Updating the task status in the task execution record from the first task status to the second task status; Among them, also include: If the current time reaches the task end time indicated in the task execution record, the task status in the task execution record is updated from the second task status to a third task status.

6. A data collection device, characterized in that: include: A first generating unit is configured to, when detecting a setting operation for a data collection task on a task configuration interface, generate a task configuration record and a task contact person record for the data collection task based on the setting operation, wherein the task contact person record is used to record contact person information of multiple task contact persons for the data collection task; A second generating unit is configured to generate a task execution record for the data collection task based on the task configuration record, and to generate a contact person execution record for each task contact person based on the task contact person record and the task execution record; the task execution record is used to record the task progress of the data collection task, and the contact person execution record is used to record the task progress of the task contact person; a sending unit, configured to send a task reminder message to a terminal of each task counterpart if the current time reaches the task start time indicated in the task execution record, wherein the task reminder message is used to instruct each task counterpart to fill in the corresponding content in the data table template; a merging unit, configured to receive reference data tables sent by respective task counterparts' terminals, and merge the contents of the respective reference data tables to obtain a summary data table, wherein any reference data table is a data table generated after the data table template is filled in with the contents; After receiving the reference data tables sent by the counterparty terminals of the respective task counterparties, for any one of the plurality of task counterparties, updating the submission status of the counterparty execution record corresponding to the any one of the plurality of task counterparties from the first submission status to the second submission status; The first submission status is used to indicate that it has not been submitted, and the second submission status is used to indicate that it has been submitted; Saving the sending time and data table identifier of the reference data table sent by any task coordinator in the coordinator execution record corresponding to any task coordinator; When it is detected that the urging control in the task configuration interface is triggered, the submission status of each task counterpart is obtained from the counterpart execution record of each task counterpart; the target task counterpart whose submission status is the first submission status is determined from the submission status of each task counterpart, and the task prompt information is sent to the counterpart terminal of the target task counterpart.

7. A computer device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions. When the program instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 5.

Images