Automatic data issuing and summarizing method, system and device with task file as carrier and medium

Abstract

The invention discloses an automatic data issuing and summarizing method, system and device with task files as carriers and a medium, belongs to the technical field of computers, and aims to solve the technical problem of how to consider office file use formats, automatically receive and send summarized files and meet office requirements. According to the technical scheme, the method comprises the following steps of: generating a task: setting a task template required by a user by taking the task as a unit; wherein the task template comprises a task attribute and a distribution file; the tasks are distributed, personnel and organizations are gathered in places where the distributed tasks are used, an organization personnel tree is formed, and the tasks are distributed to multiple users or multiple organizations; the method comprises the following steps: taking a distribution file as a source part, copying a copy as a file template, copying the file template in a distribution process, and generating an independently operated file for each receiving object; and submitting the task: submitting, passing, rejecting and withdrawing the file by operating the list on the basis of submitting the file list by distributing the file.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, system, device and medium for automatically sending and summarizing data using task files as carriers. Background Art

[0002] Collaborative editing means that multiple people edit the same document at the same time, and all participants can see each other's edits in real time. This editing method allows team members to collaborate in real time, improving work efficiency and collaboration. Currently, collaborative editing can be achieved in many ways, such as using special collaborative editing tools, Tencent Document, Song Document, etc., but this method allows all participants to see and modify the edits of others, which is not friendly to data confidentiality and security, and the edited content cannot be reviewed and rejected according to personal dimensions.

[0003] At present, offices and other places still send and receive summary documents by sending Excel or Word documents, which are then sent back to the distributor after completion. The distributor will then review and summarize the document contents. This method is cumbersome, time-consuming and inefficient.

[0004] Therefore, how to take into account the file usage format of the office space and automatically send and receive summary files to meet office needs is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The technical task of the present invention is to provide a method, system, device and medium for automatically sending and summarizing data with task files as carriers, so as to solve the problem of how to take into account the file usage format of office places and automatically send and receive summary files to meet office needs.

[0006] The technical task of the present invention is achieved in the following way: a method for automatically sending and summarizing data using task files as carriers, the method is specifically as follows:

[0007] Generate tasks: Set task templates based on user needs based on tasks; task templates include task attributes and distribution files;

[0008] Distribute tasks: Group the personnel and organizations in the place where the tasks are distributed to form an organizational personnel tree. The tasks are distributed to multiple users or multiple organizations. The distribution file is used as the source file, and a copy is made as a file template. During the distribution process, the file template is copied to generate a separate operation file for each recipient.

[0009] Submission task: Based on the distribution file submission list, the submission, approval, rejection and withdrawal of files are realized through the operation list.

[0010] Preferably, the task attributes include task ID, task name, task requirements, task summary method, whether to submit in a delayed manner, task description, task attachments and task files.

[0011] As a preferred method, during the task generation process, fill in the task attributes according to the requirements and generate the corresponding tasks; tasks are divided into periodic tasks and one-time tasks;

[0012] Among them, periodic tasks refer to the realization of daily, weekly and monthly periodic file distribution;

[0013] A single task refers to a one-time file distribution.

[0014] As a preferred option, the distribution tasks are as follows:

[0015] At the start of the distribution task, a copy of the distribution file is used as the original file template. During the distribution process, the distribution file template is copied to generate a fill-in file for the file recipient, so that everyone can operate on an independent file, ensuring data security and privacy. At the same time, the distribution history from_doc_id and to_doc_id are recorded;

[0016] For periodic tasks, set a scheduled task. After the deadline for filling in, copy the distribution file template to generate a new distribution file and a new filling file. The new distribution file and the new filling file form a superior-subordinate relationship. For example, if the deadline for filling in the task is Tuesday, the filling file for the next cycle will be generated at midnight on Wednesday.

[0017] For the needs of issuing documents involving multiple levels of personnel, after the first-level task is issued, the task recipient will forward the task with his or her own filled-in document as the distribution document and send it to the personnel at the next level; the task requirements can be set to cross-level submission or level-by-level submission to achieve multi-level file aggregation.

[0018] Preferably, the submission tasks are as follows:

[0019] Get the file parent according to the distribution record, and insert the submitted content into the parent file;

[0020] Record the submission list of the distributed documents, with the submission list as the summary basis;

[0021] Each time submission is made, the distribution file template and the files in the submission file list are read and inserted into the distribution file for aggregation;

[0022] If a file is rejected, the rejected file will be removed from the list, and the distribution file template and the files in the submitted file list will be re-aggregated, and the content of the rejected file will be removed.

[0023] A data automatic distribution and aggregation system using task files as carriers, the system comprising:

[0024] The task generation module is used to set the task template required by the user based on the task; wherein the task template includes task attributes and distribution files;

[0025] The task distribution module is used to group the personnel and organizations of the places where the tasks are distributed to form an organizational personnel tree. The tasks are distributed to multiple users or multiple organizations. The distribution file is used as the source file, and a copy is made as a file template. During the distribution process, the file template is copied to generate a separate operation file for each receiving object.

[0026] The task submission module is used to submit the file list based on the distribution file, and implement the submission, approval, rejection and withdrawal of the file through the operation list.

[0027] Preferably, the task attributes include task ID, task name, task requirements, task summary method, whether to submit in a delayed manner, task description, task attachments and task files;

[0028] The task generation module fills in the task attributes according to the requirements and generates the corresponding tasks; tasks are divided into periodic tasks and one-time tasks;

[0029] Among them, periodic tasks refer to the realization of daily, weekly and monthly periodic file distribution;

[0030] A single task refers to a one-time file distribution.

[0031] Preferably, when the task distribution module is in the initial state of the distribution task, a distribution file is copied as the original file template; during the distribution process, the distribution file template is copied to generate a fill-in file for the file recipient, so that everyone can operate on an independent file, ensuring the security and privacy of the data; at the same time, the distribution history from_doc_id and to_doc_id are recorded;

[0032] For periodic tasks, set a scheduled task. After the deadline for filling in, copy the distribution file template to generate a new distribution file and a new filling file. The new distribution file and the new filling file form a superior-subordinate relationship. For example, if the deadline for filling in the task is Tuesday, the filling file for the next cycle will be generated at midnight on Wednesday.

[0033] For the needs of document distribution involving multiple levels of personnel, after the first-level task is issued, the task recipient will forward the task with his / her own filled-in document as the distribution document to the personnel at the next level; the task requirements can be set to cross-level submission or level-by-level submission to achieve multi-level document aggregation;

[0034] The working process of the task submission module is as follows:

[0035] ①According to the distribution record, the superior of the file is obtained, and the submitted content is summarized and inserted into the superior file;

[0036] ② Record the submission list of the distributed files, with the submission list as the basis for summary;

[0037] ③ Each time submission is made, the distribution file template and the files in the submission file list are read and inserted into the distribution file for summary;

[0038] ④ If a file is rejected, the rejected file will be removed from the list, and the distribution file template and the files in the submitted file list will be re-aggregated, and the content of the rejected file will be removed.

[0039] An electronic device comprising: a memory and at least one processor;

[0040] Wherein, the memory stores a computer program;

[0041] The at least one processor executes the computer program stored in the memory, so that the at least one processor executes the above-mentioned method for automatically sending and summarizing data using the task file as a carrier.

[0042] A computer-readable storage medium stores a computer program, which can be executed by a processor to implement the above-mentioned method for automatically sending and summarizing data using task files as carriers.

[0043] The method, system, device and medium for automatically sending and summarizing data using task files as carriers of the present invention have the following advantages:

[0044] (i) The present invention uses task files as carriers to send data to multiple people or organizations, and automatically summarizes them in the original file after submission, which helps multiple people send and receive files;

[0045] (ii) The present invention uses tasks as attribute carriers to control the effects of task issuance and implementation, and uses Excel, Word and other files as data carriers to perform functions such as data submission, aggregation, and rejection;

[0046] (III) The present invention takes into account the automatic distribution of file formats in office spaces and automatically summarizes them after submission, thereby improving the efficiency of sending and receiving files;

[0047] (iv) The document recipient of the present invention fills in an independent document, which is beneficial to the privacy and security of the data;

[0048] (V) The present invention is flexible to use. The summary content of the file can be submitted or rejected by individuals, and the tasks support periodic issuance;

[0049] (VI) The present invention uses tasks as attribute carriers to control the effects of task issuance and implementation, and uses Excel, Word and other files as data carriers to perform functions such as data submission, aggregation, and rejection;

[0050] (VII) The copy source file of the present invention generates a template to record the initial state of the data to prevent confusion of the file content in subsequent data aggregation; each receiving object operates a separate template to copy the file to ensure data privacy and security;

[0051] (VIII) The present invention performs operations such as file submission, rejection and withdrawal by modifying the submitted file list, aggregating it with the file template data, and overwriting the source file content. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The present invention is further described below in conjunction with the accompanying drawings.

[0053] Attached Figure 1 This is a schematic diagram of task distribution;

[0054] Attached Figure 2 This is a schematic diagram of multiple levels of personnel involved in document distribution;

[0055] Attached Figure 3 A schematic diagram of submitting a task. DETAILED DESCRIPTION

[0056] The method, system, device and medium for automatically sending and summarizing data with task files as carriers of the present invention are described in detail below with reference to the drawings and specific embodiments of the specification.

[0057] Embodiment 1:

[0058] This embodiment provides a method for automatically sending and aggregating data using task files as carriers. The method is specifically as follows:

[0059] S1. Generate tasks: Set task templates based on user needs in units of tasks; task templates include task attributes and distribution files; task attributes include task ID, task name, task requirements, task summary method, whether to submit in a delayed manner, task description, task attachments and task files; as shown in the following table:

[0060] Task properties describe Task id Task ID Task Name Name of the task Requirements Including the submission cycle and deadline of the task Task summary method Data aggregation, file aggregation Whether to submit late Is it allowed to submit after the deadline? Mission Statement Description of the task Task attachments Explanatory Annex Task File The files that need to be distributed

[0061] S2. Distribute tasks: Group the personnel and organizations in the places where the tasks are distributed to form an organizational personnel tree. The tasks are distributed to multiple users or multiple organizations. The distribution file is used as the source file, and a copy is made as a file template. During the distribution process, the file template is copied to generate a separate operation file for each recipient.

[0062] S3. Submission task: Based on the distribution file submission list, the submission, approval, rejection and withdrawal of files are realized through the operation list.

[0063] In the process of generating tasks in step S1 of this embodiment, the task attributes are filled in according to the requirements to generate the corresponding tasks; the tasks are divided into periodic tasks and single tasks;

[0064] Among them, periodic tasks refer to the realization of daily, weekly and monthly periodic file distribution;

[0065] A single task refers to a one-time file distribution.

[0066] The distribution tasks in step S2 of this embodiment are as follows:

[0067] As attached Figure 1 As shown, in the initial state of the distribution task, a distribution file is copied as the original file template; during the distribution process, the distribution file template is copied to generate a fill-in file for the file recipient, so that everyone can operate on an independent file, ensuring the security and privacy of the data; at the same time, the distribution history from_doc_id and to_doc_id are recorded;

[0068] For periodic tasks, set a scheduled task. After the deadline for filling in, copy the distribution file template to generate a new distribution file and a new filling file. The new distribution file and the new filling file form a superior-subordinate relationship. For example, if the deadline for filling in the task is Tuesday, the filling file for the next cycle will be generated at midnight on Wednesday.

[0069] As attached Figure 2 As shown, for the needs of document distribution involving multiple levels of personnel, after the first-level task is distributed, the task recipient will forward the task with his or her own filled-in document as a distribution document to the personnel at the next level; the task requirement is set to cross-level submission or level-by-level submission to achieve multi-level file aggregation.

[0070] As attached Figure 3 As shown, the submission task in step S3 of this embodiment is specifically as follows:

[0071] S301, obtain the file parent according to the distribution record, and summarize the submitted content and insert it into the parent file;

[0072] S302, recording a submitted file list of the distributed files, with the submitted file list as a summary basis;

[0073] S303, each time submission is made, the distribution file template and the files in the submission file list are read, inserted into the distribution file, and summarized;

[0074] S304: If a file is rejected, the rejected file is removed from the list, and the distributed file template and the files in the submitted file list are reassembled, and the content of the rejected file is removed.

[0075] Embodiment 2:

[0076] This embodiment provides a data automatic distribution and aggregation system using task files as carriers, the system comprising:

[0077] The task generation module is used to set the task template required by the user based on the task; the task template includes task attributes and distribution files; the task attributes include task id, task name, task requirements, task summary method, whether to submit in a delayed manner, task description, task attachments and task files;

[0078] The task distribution module is used to group the personnel and organizations of the places where the tasks are distributed to form an organizational personnel tree. The tasks are distributed to multiple users or multiple organizations. The distribution file is used as the source file, and a copy is made as a file template. During the distribution process, the file template is copied to generate a separate operation file for each receiving object.

[0079] The task submission module is used to submit the file list based on the distribution file, and implement the submission, approval, rejection and withdrawal of the file through the operation list.

[0080] The task generation module in this embodiment fills in the task attributes according to the requirements and generates the corresponding tasks; the tasks are divided into periodic tasks and single tasks;

[0081] Among them, periodic tasks refer to the realization of daily, weekly and monthly periodic file distribution;

[0082] A single task refers to a one-time file distribution.

[0083] As attached Figure 1 As shown, when the task distribution module in this embodiment is in the initial state of the distribution task, a distribution file is copied as the original file template; during the distribution process, the distribution file template is copied to generate a fill-in file for the file recipient, so that everyone can operate on an independent file, ensuring the security and privacy of the data; at the same time, the distribution history from_doc_id and to_doc_id are recorded;

[0084] For periodic tasks, set a scheduled task. After the deadline for filling in, copy the distribution file template to generate a new distribution file and a new filling file. The new distribution file and the new filling file form a superior-subordinate relationship. For example, if the deadline for filling in the task is Tuesday, the filling file for the next cycle will be generated at midnight on Wednesday.

[0085] As attached Figure 2As shown in the figure, for the needs of multi-level personnel involved in file distribution, after the first-level task is distributed, the task recipient forwards the task with his / her own filled-in document as the distribution document to the personnel at the next level; the task requirement is set to cross-level submission or level-by-level submission to achieve multi-level file aggregation;

[0086] As attached Figure 3 As shown, the working process of the task submission module in this embodiment is as follows:

[0087] ①According to the distribution record, the superior of the file is obtained, and the submitted content is summarized and inserted into the superior file;

[0088] ② Record the submission list of the distributed files, with the submission list as the basis for summary;

[0089] ③ Each time submission is made, the distribution file template and the files in the submission file list are read and inserted into the distribution file for summary;

[0090] ④ If a file is rejected, the rejected file will be removed from the list, and the distribution file template and the files in the submitted file list will be re-aggregated, and the content of the rejected file will be removed.

[0091] Embodiment 3:

[0092] This embodiment also provides an electronic device, including: a memory and at least one processor;

[0093] Wherein, the memory stores computer-executable instructions;

[0094] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the method for automatically sending and summarizing data using task files as carriers in any embodiment of the present invention.

[0095] The processor 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, discrete hardware components, etc. The processor may be a microprocessor or any conventional processor, etc.

[0096] The memory can be used to store computer programs and / or modules. The processor realizes various functions of the electronic device by running or executing the computer programs and / or modules stored in the memory, and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created according to the use of the terminal, etc. In addition, the memory can also include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), a secure digital (SD) card, a flash memory card, at least one disk storage period, a flash memory device, or other volatile solid-state storage devices.

[0097] Embodiment 4:

[0098] This embodiment also provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions are loaded by a processor, so that the processor executes the method for automatically sending and summarizing data with task files as carriers in any embodiment of the present invention. Specifically, a system or device equipped with a storage medium can be provided, on which a software program code that implements the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device reads and executes the program code stored in the storage medium.

[0099] In this case, the program code itself read from the storage medium can realize the function of any one of the above-mentioned embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.

[0100] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RYM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer via a communication network.

[0101] In addition, it should be clear that the functions of any of the above embodiments can be implemented not only by executing the program code read by the computer, but also by enabling an operating system operating on the computer to complete part or all of the actual operations based on instructions from the program code.

[0102] In addition, it can be understood that the program code read from the storage medium is written to a memory provided in an expansion board inserted into the computer or written to a memory provided in an expansion unit connected to the computer, and then based on the instructions of the program code, a CPU installed on the expansion board or the expansion unit is enabled to perform part or all of the actual operations, thereby realizing the functions of any of the above-mentioned embodiments.

[0103] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for automatically sending and summarizing data using task files as carriers, characterized in that: The method is as follows: Generate tasks: Set task templates based on user needs based on tasks; task templates include task attributes and distribution files; Distribute tasks: Group the personnel and organizations in the place where the tasks are distributed to form an organizational personnel tree. The tasks are distributed to multiple users or multiple organizations. The distribution file is used as the source file, and a copy is made as a file template. During the distribution process, the file template is copied to generate a separate operation file for each recipient. Submission task: Based on the distribution file submission list, the submission, approval, rejection and withdrawal of files are realized through the operation list.

2. The method for automatically sending and collecting data using task files as carriers according to claim 1 is characterized in that: Task attributes include task ID, task name, task requirements, task summary method, whether to submit in a delayed manner, task description, task attachments and task files.

3. The method for automatically sending and collecting data using task files as carriers according to claim 1 is characterized in that: During the task generation process, fill in the task attributes according to the requirements and generate the corresponding tasks; tasks are divided into periodic tasks and one-time tasks; Among them, periodic tasks refer to the realization of daily, weekly and monthly periodic file distribution; A single task refers to a one-time file distribution.

4. The method for automatically sending and collecting data using task files as carriers according to claim 1 is characterized in that: The distribution tasks are as follows: At the start of the distribution task, a distribution file is copied as the original file template. During the distribution process, the distribution file template is copied to generate a fill-in file for the file recipient, so that everyone can operate on an independent file. At the same time, the distribution history from_doc_id and to_doc_id are recorded. For periodic tasks, set a scheduled task. After the filling deadline, copy the distribution file template to generate a new distribution file and a new filling file. The new distribution file and the new filling file form a superior-subordinate relationship. For the needs of issuing documents involving multiple levels of personnel, after the first-level task is issued, the task recipient will forward the task with his or her own filled-in document as the distribution document and send it to the personnel at the next level; the task requirements can be set to cross-level submission or level-by-level submission to achieve multi-level file aggregation.

5. The method for automatically sending and aggregating data using task files as carriers according to any one of claims 1 to 4, characterized in that: The submission tasks are as follows: Get the file parent according to the distribution record, and insert the submitted content into the parent file; Record the submission list of the distributed documents, with the submission list as the summary basis; Each time submission is made, the distribution file template and the files in the submission file list are read and inserted into the distribution file for aggregation; If a file is rejected, the rejected file will be removed from the list, and the distribution file template and the files in the submitted file list will be re-aggregated, and the content of the rejected file will be removed.

6. A data automatic distribution and aggregation system based on task files, characterized in that: The system includes: The task generation module is used to set the task template required by the user based on the task; wherein the task template includes task attributes and distribution files; The task distribution module is used to group the personnel and organizations of the places where the tasks are distributed to form an organizational personnel tree. The tasks are distributed to multiple users or multiple organizations. The distribution file is used as the source file, and a copy is made as a file template. During the distribution process, the file template is copied to generate a separate operation file for each receiving object. The task submission module is used to submit the file list based on the distribution file, and implement the submission, approval, rejection and withdrawal of the file through the operation list.

7. The data automatic distribution and aggregation system based on task files as the carrier according to claim 6 is characterized in that: Task attributes include task ID, task name, task requirements, task summary method, whether to submit in a delayed manner, task description, task attachments and task files; The task generation module fills in the task attributes according to the requirements and generates the corresponding tasks; tasks are divided into periodic tasks and one-time tasks; Among them, periodic tasks refer to the realization of daily, weekly and monthly periodic file distribution; A single task refers to a one-time file distribution.

8. The data automatic distribution and aggregation system using task files as carriers according to claim 6 or 7 is characterized in that: When the task distribution module is in the initial state of the distribution task, a distribution file is copied as the original file template; during the distribution process, the distribution file template is copied to generate a fill-in file for the file recipient, so that everyone can operate on an independent file; at the same time, the distribution history from_doc_id and to_doc_id are recorded; For periodic tasks, set a scheduled task. After the filling deadline, copy the distribution file template to generate a new distribution file and a new filling file. The new distribution file and the new filling file form a superior-subordinate relationship. For the needs of document distribution involving multiple levels of personnel, after the first-level task is issued, the task recipient will forward the task with his / her own filled-in document as the distribution document to the personnel at the next level; the task requirement can be set to cross-level submission or level-by-level submission to achieve multi-level document aggregation; The working process of the task submission module is as follows: ①According to the distribution record, the superior of the file is obtained, and the submitted content is summarized and inserted into the superior file; ② Record the submission list of the distributed files, with the submission list as the basis for summary; ③ Each time submission is made, the distribution file template and the files in the submission file list are read and inserted into the distribution file for summary; ④ If a file is rejected, the rejected file will be removed from the list, and the distribution file template and the files in the submitted file list will be re-aggregated, and the content of the rejected file will be removed.

9. An electronic device, characterized in that: include: memory and at least one processor; Wherein, the memory stores a computer program; The at least one processor executes the computer program stored in the memory, so that the at least one processor executes the method for automatically sending and aggregating data using task files as carriers as described in any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which can be executed by a processor to implement the method for automatically sending and aggregating data using task files as carriers as described in any one of claims 1 to 5.

Images