File collection method and device, equipment, storage medium and program product

Abstract

The invention discloses a file collection method, device and equipment, a storage medium and a program product, a first client sends a first mail to at least one contact person, and the first mail is related to a first file collection task; receiving a first operation, and displaying a first file set; wherein the first file set is related to a first file collection task; the first file set comprises one or more first files contained in one or more second mails; the second mail is associated with the first mail and / or the first file collection task. By adopting the embodiment of the invention, the file is collected through the mail, the automation degree and efficiency of file collection can be improved, and the user experience is improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a document collection method, apparatus, device, storage medium, and program product. Background Technology

[0002] In the digital age, massive amounts of electronic documents have become crucial for business and work operations. A key challenge is how to efficiently and conveniently collect, summarize, classify, and retrieve these documents. Current mainstream document collection methods include email attachments, online form tools, and uploading to online storage services. Particularly in email applications, email interactions between senders and recipients often follow a one-way or one-to-one limitation. For example, when companies undertake cross-departmental collaborative projects, the project manager, as the sender, needs to collect project-related documents from multiple departments. They can only do so by sending individual emails to members of each department to request document submissions. When the sender needs to compile the documents from the recipients, they have to frequently check their inbox and manually integrate attachments. This process is time-consuming, significantly reducing document collection efficiency and negatively impacting the user experience. Summary of the Invention

[0003] The purpose of this invention is to provide a file collection method, apparatus, device, storage medium, and program product that can effectively improve the automation and efficiency of file collection and enhance user experience.

[0004] To achieve the above objectives, embodiments of the present invention provide a file collection method applied to a first client, the method comprising: Send a first email to at least one contact, the first email being related to the first document collection task; Receive a first operation and display a first file set; wherein the first file set is related to a first file collection task; the first file set contains one or more first files contained in one or more second emails; the second emails are associated with the first emails and / or the first file collection task.

[0005] As an improvement to the above solution, the second email is associated with the first email and / or the first document collection task, including: The second email is a reply to the first email; or the second email is a follow-up email to the first email after it has been forwarded one or more times, wherein the follow-up email is an email sent by one or more of the at least one contact to the sender of the first email or an email sent by a user other than the at least one contact to the sender of the first email.

[0006] As an improvement to the above solution, before sending the first email to at least one contact, the method further includes: The first file to be collected is configured for collection through configuration items, which include a first configuration item, a second configuration item, and / or a third configuration item.

[0007] As an improvement to the above solution, if there are multiple first files to be collected, the first files include a second file and a third file, and the configuration methods of the first configuration items of the second file and the third file are the same or different; and / or the configuration methods of the second configuration items of the second file and the third file are the same or different; and / or the configuration methods of the third configuration items of the second file and the third file are the same or different.

[0008] As an improvement to the above scheme, the first configuration item is used to configure the naming method for one or more files in the first file; The naming convention is used for configuration file names, and it includes one of the following: The first naming convention is to use the original filename as the configuration file name; The second naming method is based on one or more first name configuration file names configured by the user in the collection configuration; wherein the file name includes the contact information.

[0009] As an improvement to the above scheme, the second configuration item is used to restrict the file format of the first file.

[0010] As an improvement to the above scheme, the third configuration item is related to whether the corresponding first file must be transmitted.

[0011] As an improvement to the above solution, before sending the first email to at least one contact, the method further includes: Configure the fourth configuration item, which is related to the storage and / or display method of the first file. The storage and / or display method includes one of the following: A first storage and / or display method is used to store and / or display the first file in one or more file subsets, folders or directories according to the contact from which it comes, wherein the name of the file subset, folder or directory is related to the name of the corresponding contact. The second storage and / or display method is used to store and / or display the first file in a subset of files, folders, or directories associated with the first name, according to one or more first names configured by the user.

[0012] As an improvement to the above scheme, when the first contact among the at least one contacts sends two or more first files with the same file name as the one or more of the above, the first file set shall only include the first file sent latest for the two or more first files with the same file name.

[0013] As an improvement to the above solution, when the storage and / or display method is the second storage and / or display method, the editing interface related to the second email displays one or more first name options to associate the first file with the first name.

[0014] As an improvement to the above solution, before sending the first email to at least one contact, the method further includes: Configure the fifth configuration item, which is associated with one or more designated contacts; when configuring a designated contact, the first file set includes only files from the second emails sent by the designated contact that are associated with the first email and / or the first file collection task.

[0015] As an improvement to the above solution, the method further includes: When the contact successfully retracts the second email they sent, the first file set does not contain the first file contained in the successfully retracted second email.

[0016] As an improvement to the above solution, before sending the first email to at least one contact, the method further includes: Configure the sixth configuration item, which is related to the file collection deadline. When the user-set file collection deadline or the pre-configured file collection deadline reaches N seconds (N≥0), a third email is received from the system. This third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

[0017] As an improvement to the above solution, the first email displays the deadline for document collection.

[0018] As an improvement to the above scheme, after all the designated contacts configured in the fifth configuration item have sent the second email N seconds later, N≥0, the first client receives a third email automatically sent by the email system. The third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

[0019] As an improvement to the above solution, the method further includes: Receive a second operation to display a first email set; wherein the first email set includes only the first email and / or the second email associated with the first email and / or the first file collection task.

[0020] As an improvement to the above solution, the method further includes: Upon receiving the third operation, the task editing page for the first file collection task corresponding to the first file set is displayed.

[0021] As an improvement to the above solution, the method further includes: The first control item is displayed. The first control item is related to ending the first file collection task. When the first file collection task is ended through the first control item, files from emails received afterward will no longer be stored in the first file collection.

[0022] To achieve the above objectives, embodiments of the present invention also provide a file collection method applied to a second client, the method comprising: Receive a first email sent by a first client, the first email being related to a first file collection task; When the first client receives the first operation, it displays a first file set, which is related to the first file collection task. The first file set contains one or more first files contained in one or more second emails, and the second emails are associated with the first emails and / or the first file collection task.

[0023] As an improvement to the above solution, after receiving the first email sent by the first client, the method further includes: Upon receiving the fifth operation, the editing interface of the second email is displayed; wherein, the editing interface of the second email is the page that is redirected to after the reply function of the first email is triggered.

[0024] As an improvement to the above solution, the first email carries a file collection link related to the file collection task, and after receiving the first email sent by the first client, the method further includes: The sixth operation is received, and the file upload page is displayed; wherein, the file upload page is the page that is redirected to after the file collection link is triggered.

[0025] As an improvement to the above solution, the file upload page includes basic task information and a file upload area; wherein, when a user uploads a file in the file upload area, a prompt message is displayed, and the prompt message is one of the following: The first notification indicates that the current user is not a designated contact. A second notification indicates that the document collection task has been completed; The current file does not meet the upload format requirements (third notification). The fourth message indicating that the current file has been successfully submitted.

[0026] As an improvement to the above scheme, the file collection link is generated based on the first client's configuration settings for the first file to be collected.

[0027] As an improvement to the above scheme, the collection configuration includes a first configuration item, a second configuration item, and / or a third configuration item.

[0028] To achieve the above objectives, embodiments of the present invention also provide a file collection device, applied to a first client, the device comprising: The first email sending module is used to send a first email to at least one contact, the first email being related to the first document collection task; The first file set display module is used to receive the first operation and display the first file set; Wherein, the first file set is related to the first file collection task; the first file set contains one or more first files contained in one or more second emails; the second emails are associated with the first emails and / or the first file collection task.

[0029] To achieve the above objectives, embodiments of the present invention also provide a file collection device applied to a second client, the device comprising: The first email receiving module is used to receive the first email sent by the first client, and the first email is related to the first file collection task. When the first client receives the first operation, it displays a first file set, which is related to the first file collection task. The first file set contains one or more first files contained in one or more second emails, and the second emails are associated with the first emails and / or the first file collection task.

[0030] To achieve the above objectives, embodiments of the present invention also provide a file collection device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements the file collection method as described in any of the above embodiments.

[0031] To achieve the above objectives, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program, when running, controls the device where the computer-readable storage medium is located to execute the file collection method as described in any of the above embodiments.

[0032] To achieve the above objectives, embodiments of the present invention also provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the file collection method as described in any of the above embodiments.

[0033] Compared to existing technologies, the document collection method, apparatus, device, storage medium, and program products disclosed in this invention solve the limitations of the traditional email document collection mode's one-way, one-to-one interaction and the problem of low efficiency in manual document collection. By sending a first email related to the first document collection task to at least one contact, it is possible to initiate batch document collection tasks in a one-to-many manner, eliminating the need to send emails to each contact individually, thus reducing the operational costs in the task initiation phase. At the same time, by receiving the user's first operation, the first set of documents related to the task can be displayed, automatically integrating the first documents scattered in multiple second emails, replacing the tedious process of manually checking the inbox and manually collecting attachments, and realizing the automation and integrated management of document collection and summarization. Attached Figure Description

[0034] Figure 1 This is a schematic diagram of information interaction between a first client and a second client provided in an embodiment of the present invention; Figure 2 This is a flowchart of the first file collection method provided in the embodiments of the present invention; Figure 3 This is a schematic diagram illustrating the information interaction between terminals involved in the file collection method provided in this embodiment of the invention; Figure 4 This is a schematic diagram showing the first file set list provided in an embodiment of the present invention; Figure 5 This is a schematic diagram illustrating the collection task template provided in an embodiment of the present invention; Figure 6 This is a schematic diagram of the configuration page provided in an embodiment of the present invention; Figure 7This is another schematic diagram of the configuration page provided in an embodiment of the present invention; Figure 8 This is a first display schematic diagram of the first file set provided in the embodiments of the present invention; Figure 9 This is a second display diagram of the first file set provided in an embodiment of the present invention; Figure 10 This is a third display diagram of the first file set provided in the embodiments of the present invention; Figure 11 This is a fourth display diagram of the first file set provided in the embodiments of the present invention; Figure 12 This is a fifth display schematic diagram of the first file set provided in the embodiments of the present invention; Figure 13 This is a sixth display diagram of the first file set provided in the embodiments of the present invention; Figure 14 This is a schematic diagram showing the editing interface related to the second email provided in an embodiment of the present invention; Figure 15 This is a schematic diagram showing the collection status page provided in an embodiment of the present invention; Figure 16 This is a schematic diagram showing the submission details list provided in an embodiment of the present invention; Figure 17 This is a schematic diagram of the display of the prompt page provided in an embodiment of the present invention; Figure 18 This is a schematic diagram of the interactive interface when the targeted collection mode provided in this embodiment of the invention is triggered; Figure 19 This is a schematic diagram showing the third email provided in an embodiment of the present invention; Figure 20 This is a schematic diagram showing the first email set provided in an embodiment of the present invention; Figure 21 This is a schematic diagram showing the completion of a task according to an embodiment of the present invention; Figure 22 This is a schematic diagram of a link sharing page provided in an embodiment of the present invention; Figure 23 This is a flowchart of the second file collection method provided in the embodiments of the present invention; Figure 24 This is a schematic diagram of the file upload page provided in an embodiment of the present invention; Figure 25 This is a schematic diagram of the display of the first prompt information provided in an embodiment of the present invention; Figure 26 This is a schematic diagram of the display of the second prompt information provided in an embodiment of the present invention; Figure 27This is a schematic diagram of the display of the third prompt information provided in an embodiment of the present invention; Figure 28 This is a schematic diagram of the display of the fourth prompt information provided in an embodiment of the present invention; Figure 29 This is a structural block diagram of the first document collection device provided in the embodiments of the present invention; Figure 30 This is a structural block diagram of the second type of document collection device provided in the embodiments of the present invention; Figure 31 This is a structural block diagram of a file collection device provided in an embodiment of the present invention. Detailed Implementation

[0035] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0036] The document collection method described in this invention is applied in a document collection scenario and is implemented through information interaction between a first client and a second client. The first client can be a terminal device or application with document collection configuration, task management, and result reception functions, such as a smartphone, tablet, or personal computer with email clients / web interfaces, office collaboration software, etc. It acts as the initiator, responsible for creating and sending document collection tasks and receiving feedback information. The second client can be a terminal device or application that receives document collection tasks and uploads files, such as other smartphones, computers, or portable devices that have a communication connection with the first client. It acts as the responder, completing the file upload operation through the received document collection task, thus achieving information interaction with the first client.

[0037] See Figure 1 , Figure 1 This is a schematic diagram of information interaction between a first client and a second client provided in an embodiment of the present invention. The first client can interact with multiple second clients (corresponding to n contacts respectively). The first client can initiate file collection tasks to these contacts. Each second client can send files to the first client based on the relevant information provided by the first client (such as file collection task information, etc.), thereby realizing file collection and interaction between multiple terminals.

[0038] See Figure 2 , Figure 2This is a flowchart of a first file collection method provided in an embodiment of the present invention. The first file collection method is applied to a file collection terminal and includes steps S11-S12. See also... Figure 3 , Figure 3 The following is a schematic diagram of the information interaction between terminals involved in steps S11 to S12. Figure 3 Steps S11 to S12 are explained in detail.

[0039] S11. Send a first email to at least one contact, the first email being related to the first document collection task.

[0040] For example, the first email is used to convey information and operation entry points for the first document collection task to the contact person. The email content may include the task name, document collection requirements, task deadline, and operation instructions. A document collection task refers to a document collection work with a clear objective created by the task initiator based on actual needs, such as collecting employees' weekly or monthly reports. This task needs to be pre-configured with basic task information, file upload rules, collection mode, and other parameters, and is initiated by sending the first email to the contact person.

[0041] S12. Receive the first operation and display the first file set; wherein the first file set is related to the first file collection task; the first file set contains one or more first files contained in one or more second emails; the second emails are associated with the first emails and / or the first file collection task.

[0042] For example, the first operation refers to an interactive operation triggered by the user on the display interface of the first client to view the results corresponding to the first file collection task. For instance, clicking the "File Collection" operation bar on the client or web application displays the first file collection list. This operation is a query command initiated by the user to trigger the system to retrieve and display the collected file information related to the task. Figure 4 As shown, Figure 4 This is a schematic diagram showing the first file collection list provided in an embodiment of the present invention. The first file collection list includes category tags "Initiated by Me" and "Participated By Me." Under the "Initiated by Me" category, multiple first file collections are displayed. Each first file collection contains information such as the collection task name, task deadline, number of submitters, and number of files. It also includes operation buttons for creating a new file collection task, deleting, and editing, facilitating user management of file collection tasks. Furthermore, after a contact uploads a file, it is stored in the file collection server's database. Users can view information about these files in the first file collection on the first client, as well as view thumbnails or full images. When a download is triggered, the file collection server can download the file to the user's local machine.

[0043] For example, the second email refers to a feedback email generated by the email server that is directly associated with the first file collection task. The second email carries the first file uploaded by the contact. The first files contained in one or more second emails can be integrated to form a set of first files corresponding to the first file collection task.

[0044] Regarding steps S11-S12 above, the present invention provides the following embodiments: Collector A creates a first file collection task on the enterprise email web interface with integrated file collection function, and selects 10 contacts as collection targets. The client generates a first email according to the above configuration. At this time, the first email will be directly sent to the mailboxes of these 10 contacts, without the project leader needing to edit the email content one by one. After receiving the first email, the contacts reply to the first email, and then jump to the editing interface of the second email. The contacts can upload the corresponding files in the second email, and finally form the second email. The second email carries the first file from the contacts, and the first file will be automatically organized into the first file collection. When collector A needs to check the collection progress, he performs the first operation on the client, clicks the "File Collection" operation bar of the application on the web page, and displays the first file collection. The project leader can directly view all the collected files without having to check the inbox one by one.

[0045] In this embodiment of the invention, steps S11-S12 above can solve the inefficiency of traditional one-to-one email sending. In the traditional file collection process, the sender needs to edit and send emails one by one for file collection needs of multiple contacts. The number of operation steps is positively correlated with the number of contacts. When the number of contacts is large, the time cost is high and it is easy to miss or send the wrong email. This invention breaks through the limitations of traditional one-way, one-to-one interaction by creating a single file collection task and sending the first email in batches, realizing the initiation of batch tasks for one-to-many. In addition, this invention can also solve the tedious problem of manually collecting scattered files. In the traditional file collection process, the reply emails of contacts are scattered in the inbox. The sender needs to manually filter, download and classify attachments, which is not only time-consuming and laborious, but also easy to miss files due to the large number of emails. At the same time, manual summarization cannot intuitively show the overall progress of the task. This invention automatically integrates the second email into the first file set by associating it with the task, so that the first files scattered in different second emails are automatically associated with the corresponding first file collection task. File summarization can be completed without manual intervention, solving the technical pain point of low efficiency in manual file collection.

[0046] This invention enables batch file collection task initiation via a one-to-many mechanism by sending a first email related to a first file collection task to at least one contact. This eliminates the need to send emails to each contact individually, reducing operational costs during task initiation. Simultaneously, by receiving the user's first action, the invention displays the first set of files related to the task, automatically integrating files scattered across multiple second emails. This replaces the tedious process of manually checking inboxes and manually collecting attachments, achieving automated and integrated management of file collection and aggregation. This invention improves file collection efficiency in cross-departmental and multi-contact scenarios, reduces the time cost and error probability of manual operations, and, through the association between emails and file collection tasks, allows users to intuitively and conveniently view all collected files corresponding to a task, greatly optimizing the file collection experience. It provides a reliable solution for the efficient management of massive amounts of electronic documents in enterprise collaboration, project management, and other scenarios.

[0047] Furthermore, the second email is associated with the first email and / or the first document collection task, including: the second email is a reply email to the first email; or the second email is a follow-up email to the first email after it has been forwarded one or more times, wherein the follow-up email is an email sent by one or more of the at least one contact to the sender of the first email or an email sent by a user other than the at least one contact to the sender of the first email.

[0048] For example, collector A creates a first file collection task through a first client, generating a first email containing the file collection task. When the first email is sent to contact B, contact B can directly reply to the first email and upload the file. At this point, a second email is returned to collector A; this second email is a reply to the first email. Alternatively, there is another scenario where the first email has been forwarded. In this case, the contact's reply is a continuation email of the first email. There are two forwarding scenarios in this case: 1) Reply directly to the collector after forwarding; Employee B forwards the first email sent by A to Employee C, informing C to assist in uploading the file. After receiving the forwarded email, C replies to the first email and uploads the file. The system automatically generates a second email, which is sent directly to the collector A's client.

[0049] 2) After forwarding, the email is replied to by an intermediary contact; After employee B forwards the first email to employee C, C submits the file and sends the reply email containing the file to B. After B verifies that the file is correct, he forwards C's reply email to A. At this time, the system recognizes that the forwarded email is a follow-up email after the first email has been forwarded twice, and determines the email as the second email.

[0050] It should be noted that in the two scenarios described above, due to the forwarding of the first email and the involvement of non-initial contacts (such as employee B) in document submission, the correlation between the second email and the original first document collection task may weaken, leading to the inability to collect the documents. Therefore, the association between the second email and the first email and the first document collection task can be achieved by embedding a unified task association identifier in the email header, such as adding a unique task association identifier, like a Task-ID, to the email metadata. When collector A generates the first email, the system automatically binds a unique Task-ID to that email and sends it synchronously with the email content. Subsequent emails, whether directly replied to by contact B or generated after being forwarded by B to C, will automatically identify and inherit this Task-ID, ensuring that all emails related to this document collection task carry a unified identifier. Even if the email has been forwarded multiple times, as long as this association identifier is detected, it can be identified as the second email and automatically associated with the corresponding first document collection task, thereby achieving accurate document collection and source tracing.

[0051] In this embodiment of the invention, the above steps can solve the problem of the broken association between forwarded emails and the original collection task. In the traditional file collection process, after the first email is forwarded, subsequent reply or forwarded emails will be out of the context of the original task, and the system cannot identify that these emails are related to the initial file collection task. This invention can identify follow-up emails after the first email has been forwarded once or multiple times, ensuring that the association between emails and tasks is not interrupted in forwarding scenarios. No matter how many times an email is forwarded, as long as it is a follow-up email to the first email, the system can automatically identify and classify it through task association identifiers. Collectors do not need to manually filter forwarded emails to integrate all related files into the first file set, realizing automatic file association and aggregation in complex forwarding scenarios.

[0052] Furthermore, before performing step S11, the method further includes: S101. The first file to be collected is configured for collection through configuration items, the collection configuration including a first configuration item, a second configuration item and / or a third configuration item.

[0053] For example, when a collector needs to initiate a file collection operation, they can trigger the file collection start operation on an application or webpage. At this time, a collection task template will be displayed on the interface, such as... Figure 5 As shown, Figure 5This is a schematic diagram illustrating the collection task templates provided in this embodiment of the invention. The collection task templates include general templates and convenient templates. For example, general templates include templates for collecting files, while convenient templates include templates for collecting work materials, project documents, group building photos, and assignments. The display interface also shows a description of each collection task template; for example, the work materials template suggests "planning documents, work reports, etc., convenient for collection." Users can choose as needed, and the system further provides customization functionality. Users can set task-related information (such as task name, file type, deadline, etc.) to create their own custom file collection task templates based on their actual file collection needs. When a user selects any file collection template, the system redirects to the corresponding configuration page. For different file collection templates, some configuration information can be pre-filled in the configuration page. For example, in the work materials template, the task title (i.e., task name) and task description are pre-filled. It should be noted that this pre-filled content can be edited by the user; however, there are also blank configuration pages without pre-filled configuration information.

[0054] See Figure 6 , Figure 6 This is a schematic diagram of the configuration page provided in an embodiment of the present invention. This configuration page is displayed when configuring the collection of the first file. The configuration page is used to collect configuration information, including basic task information, file upload rules, and collection mode. Specifically, the configuration page collects the task title and task description, integrating them into the basic task information. The collection information bar collects the file name, file naming method (original file name or automatic renaming), specified format (one of all files, documents, images, videos, and audio), and whether related fields are mandatory. Simultaneously, the collection settings bar collects the task deadline (i.e., the file collection deadline; files cannot be uploaded after this time), file save path, and rules for creating folders in the first file collection (no folder creation, naming the folder according to the contact person's name and saving the files, or naming the folder according to the collected file name and saving the files). This information is synchronously integrated into the file upload rules. The collection settings bar also provides a collection mode: targeted collection mode or non-targeted collection mode. It should be noted that the targeted collection mode only allows a specified contact person to upload files, while the non-targeted mode does not specify a contact person; in this case, anyone can upload files.

[0055] Furthermore, if there are multiple first files to be collected, the first files include a second file and a third file, and the configuration methods of the first configuration items of the second file and the third file are the same or different; and / or the configuration methods of the second configuration items of the second file and the third file are the same or different; and / or the configuration methods of the third configuration items of the second file and the third file are the same or different.

[0056] For example, the second file and the third file refer to two different types of files that the collector needs to collect in parallel within the same file collection task. For instance, when collector A is collecting files, the first file to be collected includes the second file (weekly report) and the third file (monthly report). Both belong to this collection task, but the configuration methods of the first configuration item, the second configuration item, and the third configuration item may be the same or different.

[0057] In this embodiment of the invention, if a certain configuration item of the second file and the third file are configured in the same way, it means that the two types of files share the same set of basic task rules. This ensures the consistency of basic rules for different files under the same task, avoids management confusion caused by differences in basic task information, reduces the operational cost of repeated configuration for collectors, and improves task creation efficiency. If a certain configuration item of the second file and the third file are configured in different ways, it means that differentiated settings are made for the technical requirements of the two types of files. This can adapt to the collection needs of different types of files and solves the limitation of a single set of rules applicable to all files in the traditional collection mode.

[0058] Furthermore, the first configuration item is used to configure the naming method for one or more files in the first file, that is, the first configuration item is... Figure 6 The naming convention for files in the information collection section, used for configuration file names, includes one of the following: 1) First naming method: Configure the file name according to the original file name; For example, the first naming method means that after a file is uploaded, the system directly uses the original file name from the contact's local machine for storage, without modifying the naming rules. When using this method, the collector can select "Original File Name" in the file naming method option on the configuration page to complete the first configuration setting. For instance, when collector A initiates a monthly report collection task, and selects the first naming method on the configuration page, if contact B uploads a file with the local name "2025.12-User B Monthly Report" and contact C uploads a file with the local name "2025.12-User C Monthly Report," the system will directly retain the original names of these two files and store them in the corresponding first file collection. When the collector views the first file collection, the file names they see are completely consistent with the file names on the contact's local machine, allowing for intuitive identification of the original content and version information of the files. This naming method is suitable for scenarios where contacts have already standardized file naming and no further reorganization by the collector is required.

[0059] 2) A second naming method, based on one or more first name configuration file names configured by the user in the collection configuration; wherein the file name includes the contact information.

[0060] For example, the second naming method refers to the collector setting one or more standardized primary names in advance on the configuration page. For instance, when the collector wants to collect periodic work reports from employees in various departments, they can set the primary name to weekly report, monthly report, quarterly summary, etc., in the configuration interface. If the collector initiates a project data collection task, they can configure the primary name as technical solution, progress log, results report, risk assessment form, etc., depending on the data type. When the contact person submits the file, the system immediately concatenates the primary name and contact person information according to preset rules to generate the final file name. When using this naming method, the collector needs to first check "Automatic Rename" in the file naming method on the configuration page.

[0061] In this embodiment of the invention, by providing two flexible file naming configuration methods—preserving the original filename and automatic renaming—the problems of chaotic filenames, difficult classification, and unclear attribution in the traditional file collection process are solved, achieving a balance between personalization and standardization in file naming rules. For the first naming method, the original filename is directly used, which fully preserves the contact person's file naming logic and version information, avoiding file identification obstacles caused by renaming, and adapting to scenarios where contacts have already completed standardized file naming. For the second naming method, by pre-configuring a unified first name and supporting the embedding of contact information as needed, standardized file naming management is enforced, facilitating content-based retrieval by collectors, while also clearly identifying the file uploader, avoiding attribution confusion when multiple contacts submit similar files.

[0062] Furthermore, the second configuration item is used to restrict the file format of the first file.

[0063] For example, the second configuration item corresponds to Figure 6 The "Restrict File Formats" option allows for format constraints on the first file submitted by the contact person. This includes "All Files" (no format restrictions) or documents, images, videos, and audio files with format restrictions. For example, when collector A initiates a file collection task, they can select only image formats in the second configuration option. In this case, the first file collection can only include JPG, PNG, PSD, and other image files; document, video, and audio files cannot be categorized. If collector A needs to collect documents, videos, and audio materials simultaneously, they can select "All Files" in the second configuration option to achieve accurate collection of multiple types of compliant files.

[0064] Furthermore, the third configuration item is related to whether the corresponding first file must be transmitted.

[0065] For example, the third configuration item corresponds to Figure 6 The "required fields" option means that when this required field mode is selected, the contact person must upload the file when uploading files on the file upload page. For example, when collector A initiates a file collection task, they may set the third configuration field of the second file (such as a monthly report) as required, while the third configuration field of the third file (such as a weekly report) is not set as required. In this case, employees must upload the monthly report when operating on the upload page; otherwise, they cannot complete the submission. The weekly report, however, can be uploaded or not, depending on the employee's own situation; the system does not enforce this requirement.

[0066] In this embodiment of the invention, by setting whether a file is mandatory through a third configuration item, the uploader is forced to upload important files during the submission process. This ensures that the file collection obtained by the collector fully covers the task requirements, avoiding subsequent work stagnation or repeated communication for supplementary documents due to missing key files, thus reducing communication costs. For non-core files, a non-mandatory setting is retained, balancing the rigidity and flexibility of collection requirements. This avoids adding unnecessary submission burdens to the contact person, while also allowing the collector to obtain optional supplementary materials, improving the completeness and efficiency of file collection, and optimizing the user experience for both the collector and the recipient.

[0067] Furthermore, before performing step S11, the method further includes: S102. Configure the fourth configuration item, which is related to the storage and / or display method of the first file. The storage and / or display method includes one of the following: A first storage and / or display method is used to store and / or display the first file in one or more file subsets, folders or directories according to the contact from which it comes, wherein the name of the file subset, folder or directory is related to the name of the corresponding contact. The second storage and / or display method is used to store and / or display the first file in a subset of files, folders, or directories associated with the first name, according to one or more first names configured by the user.

[0068] It should be noted that, since the configuration page allows you to configure the naming method of the files to be collected, and to specify whether to create a folder to save the files uploaded by the contacts, different configuration methods will result in different ways of displaying the first file in the first file collection, as well as different storage locations for the first file in the first file collection.

[0069] For example, see Figure 7 , Figure 7This is another schematic diagram of the configuration page provided in an embodiment of the present invention. The configuration page provides file naming methods for files to be collected, folder configuration methods without creating folders, and folder naming methods when folders need to be created. The file naming methods include automatic renaming and using the original filenames. The folder naming methods include contact naming and user (i.e., collector) self-naming. Figure 7 As shown in the dashed box, the naming method includes two options: "Original Filename" and "Automatic Rename." Users can select one to set the naming rules after file upload. Selecting "Original Filename" means that the file name uploaded by the contact will not be changed and will directly use its original filename. Selecting "Automatic Rename" means that the file name uploaded by the contact will be changed. The specific renaming method can be determined according to the collected file name and / or the contact name, or the default mode, i.e., random naming, can be used. The folder creation method includes three options: "No need to create a folder," "Name the folder and save the files according to the name filled in by the contact (i.e., contact naming method)," and "Name the folder and save the files according to the filled-in collected file name (i.e., self-naming method)." Users can select the corresponding option to decide whether to create a storage folder for this file collection operation and to determine the specific naming basis of the folder, such as naming it based on the contact name or the collected file name.

[0070] Since the first configuration item has two filename configuration options and the fourth configuration item has three folder configuration options, there are a total of 6 configuration options when combined in pairs. These 6 configuration options correspond to the storage method of the first file in the first file set, as well as its location and name in the first file set. The configuration modes of the 6 scenarios are shown in Table 1.

[0071] Table 1 Configuration modes for 6 scenarios

[0072] 1) First file and folder configuration method: Collector A selects "Automatic renaming (i.e., second naming method)" and "Name folders and save files according to the collected file names filled in (i.e., second storage and / or display method)". The first file set includes at least one subset of files, folders or directories named by the second storage and / or display method, and the subset of files, folders or directories includes at least one file named by the second naming method.

[0073] For example, see Figure 8 , Figure 8This is a first display illustration of the first file set provided in this embodiment of the invention. Taking an example where the collector has configured the file collection names as "Weekly Report" and "Monthly Report" on the configuration page, and two contacts (Contact 111 and Contact 121) have uploaded files for the "Weekly Report" and "Monthly Report" file collection tasks respectively. Since the collector selected "Name folders and save files according to the entered collection file names" during configuration, the first file set contains two folders (or file subsets / directories). These two folders can be directly named using the file collection names entered by the collector, namely the Weekly Report folder and the Monthly Report folder. Each folder contains files based on the file collection name; for example, the Weekly Report folder contains files related to weekly reports, and the Monthly Report folder contains files related to monthly reports. When the user selects the Weekly Report folder, the page displays a list of files. Since the collector selected "Automatically rename," the file names are now generated using the collection file name plus the contact's name.

[0074] 2) Second file and folder configuration method: The collector selects "Automatic renaming (i.e., second naming method)" and "Name folders according to the names filled in by the contact person (i.e., first storage and / or display method)". At this time, the first file set includes at least one subset of files, folders or directories named by the first storage and / or display method, and the subset of files, folders or directories includes at least one file named by the second naming method.

[0075] For example, see Figure 9 , Figure 9 This is a second display illustration of the first file collection provided in this embodiment of the invention. Taking the collector configuring the file collection names "Weekly Report" and "Monthly Report" on the configuration page as an example, and two contacts (Contact 116 and Contact 126) uploading files for the "Weekly Report" and "Monthly Report" file collection tasks respectively. Since the collector selected "Name folders according to the names filled in by the contacts" during configuration, there are two folders in the first file collection. These two folders can be directly named using the names filled in by the contacts, namely folder 116 and folder 126. Each folder contains files based on the contact; for example, folder 116 contains all files uploaded by 116, and folder 126 contains all files uploaded by 126. When the user selects folder 116, the page displays a list of files. Since the collector selected "Automatically rename," the file names are now named using the collection file name + contact name.

[0076] 3) The third file and folder configuration method: When the collector selects "Automatic renaming (i.e. the second naming method)" and "No need to create folders", the first file collection will include at least one file named using the second naming method.

[0077] For example, see Figure 10 , Figure 10 This is a third display illustration of the first file collection provided in this embodiment of the invention. Taking the collector configuring the file collection names "Weekly Report" and "Monthly Report" on the configuration page as an example, and two contacts (Contact 117 and Contact 127) uploading files for the "Weekly Report" and "Monthly Report" file collection tasks respectively. Since the user selected "No need to create folders," there are no folders in the first file collection; instead, the files uploaded by the contacts are displayed directly. Because the collector selected "Automatic renaming," the file names are now formatted as the collection file name + the user's name.

[0078] 4) Fourth file and folder configuration method: The collector selects "Original file name (i.e., first naming method)" and "Name the folder and save the file according to the collected file name (i.e., second storage and / or display method)". At this time, the first file set includes at least one subset of files, folders or directories named by the second storage and / or display method, and the subset of files, folders or directories includes at least one file named by the first naming method.

[0079] For example, see Figure 11 , Figure 11 This is a fourth display illustration of the first file set provided in this embodiment of the invention. Taking the collector configuring the file collection names "Weekly Report" and "Monthly Report" on the configuration page as an example, and two contacts uploading files for the "Weekly Report" and "Monthly Report" file collection tasks respectively. Since the collector selected "Name folders and save files according to the entered collection file names" during configuration, there are two folders in the first file set. These two folders can be directly named using the file collection names entered by the collector, namely the Weekly Report folder and the Monthly Report folder. Each folder contains files based on the file collection name; for example, the Weekly Report folder contains files related to weekly reports, and the Monthly Report folder contains files related to monthly reports. When the user selects the Weekly Report folder, the page displays a list of files. Since the collector selected "Original File Name," the file names are directly used as their original names.

[0080] 5) Fifth file and folder configuration method: The collector selects "Original file name (i.e., first naming method)" and "Name the folder according to the name filled in by the contact person (i.e., first storage and / or display method)". At this time, the first file set includes at least one subset of files, folders or directories that are stored and / or displayed in the first method, and the subset of files, folders or directories includes at least one file named in the first method.

[0081] For example, see Figure 12 , Figure 12 This is a fifth display illustration of the first file collection provided in this embodiment of the invention. Taking the collector configuring the file collection names "Weekly Report" and "Monthly Report" on the configuration page as an example, and two contacts (Contact 113 and Contact 123) uploading files for the "Weekly Report" and "Monthly Report" tasks respectively. Since the collector selected "Name folders according to the names filled in by the contacts" during configuration, there are two folders in the first file collection. These two folders can be directly named using the names filled in by the contacts, namely folder 113 and folder 123. Each folder contains files based on the contact; for example, folder 113 contains files uploaded by contact 113, and folder 123 contains files uploaded by contact 123. When the user selects folder 113, the page displays a list of files. Since the collector selected "Original file name," the file names are directly using their original names.

[0082] 6) The sixth file and folder configuration method: When the collector selects "Original file name (i.e., the first naming method)" and "No need to create folder", the first file collection will include at least one file named using the first naming method.

[0083] For example, see Figure 13 , Figure 13 This is a sixth display illustration of the first file collection provided in this embodiment of the invention. Taking the collector configuring the file collection names "Weekly Report" and "Monthly Report" on the configuration page as an example, and two contacts uploading files for the "Weekly Report" and "Monthly Report" file collection tasks respectively. Since the user selects "No need to create folders," there are no folders in the first file collection; instead, the files uploaded by the contacts are directly displayed. Furthermore, since the collector selects "Original file name," the file names are directly based on their original names.

[0084] In this embodiment of the invention, users can pre-set the organization rules for files and folders during the task configuration stage through the naming options provided on the configuration page. This ensures the standardization of file storage and facilitates quick retrieval and management of different types of collected files by folder. Furthermore, not creating folders reduces storage levels, making the file list more concise and facilitating quick browsing of all submitted files.

[0085] Furthermore, when the storage and / or display method is the second storage and / or display method, the editing interface related to the second email displays one or more first name options to associate the first file with the first name.

[0086] For example, see Figure 14 , Figure 14 This is a schematic diagram showing the editing interface related to the second email provided in an embodiment of the present invention. Again, taking the example of the collector configuring file collection names "Weekly Report" and "Monthly Report" in the configuration page, and the collector selecting "Name the folder and save the file according to the entered collection file name" during configuration, the contact can directly reply to the first email upon receiving it, and then be redirected to the editing interface of the second email. When the contact submits the file in the second email, the file upload area of ​​the second email will display one or more first name options pre-configured by the collector, such as... Figure 14 The "Monthly Report" and "Weekly Report" dropdown options in the editing interface are standardized name tags set by the collector on the configuration page. When a contact needs to submit a file, they must first select the corresponding tag from the two primary name options, "Monthly Report" and "Weekly Report," in the dropdown options of this editing interface to complete the association and binding of the file with the primary name. After selecting the primary name, the system will automatically store the file in the corresponding primary file set (the primary file set contains the file subsets, folders, or directories corresponding to the weekly and monthly reports).

[0087] It should be noted that if the collector configures multiple primary names, the interface will simultaneously display all options for the contact to choose as needed, thereby achieving accurate classification and naming of different types of files.

[0088] In addition, the second email may also display a prompt message that informs the contact of the functions of "delete file" and "update file". If a file needs to be deleted, the contact can also withdraw the file that has been added to the first file set after successfully withdrawing the second email that has been sent (this process is described in step S14 below).

[0089] Furthermore, when the first contact among the at least one contact sends two or more first files with the same filename, the first file set only includes the first file sent most recently. That is, if a file needs updating, the contact can reply a second time to the original email for the same file collection task. In this case, the file set only retains the latest file version sent under the same contact and filename (this process corresponds to the automatic file overwriting or hiding process mentioned later). For example, if a contact uploads a file at a certain time and then uploads a modified file, the system will automatically identify that these two files belong to the same contact and have the same filename. In this case, the first file set will not display both files simultaneously, but will only retain the file sent most recently, automatically overwriting or hiding the earlier submitted file. This avoids retaining duplicate historical versions in the file set and prevents redundancy in the file list.

[0090] In this embodiment of the invention, the second email provides a visual display of the first name option and a design for associating contacts. This ensures that the files submitted by the contacts match the file type classification standards preset by the collector, and also makes the generation of file names more standardized and uniform, avoiding the problem of chaotic file names in the traditional mode.

[0091] Furthermore, after performing step S12, the method further includes: S13. In response to the user's selection operation on the first file set, a collection status page is displayed; wherein, when the collection mode is a targeted collection mode and at least one designated contact has uploaded a file, the collection status page provides a submission details list.

[0092] For example, the collection status page displays information such as the collection task name, task deadline, and number of submitters. If someone has already submitted a file, the collection status page also displays a file list, such as... Figure 15 As shown, Figure 15 This is a schematic diagram of the collection status page provided in this embodiment of the invention. The file list information is presented in folder format because the file collection terminal selected "Name and save files according to the names filled in by the contacts" in the configuration page. If the file collection terminal selects the targeted collection mode in the configuration page, the collection status page further displays a trigger button for the submission details list. The trigger button for the submission details list is displayed on the side of the number of people who have submitted, and the submission details list will be displayed regardless of whether any contacts have submitted files at this time. It should be noted that if the file collection terminal selects the non-targeted collection mode in the configuration page, the collection status page will not display the submission details list.

[0093] For example, see Figure 16, Figure 16 This is a schematic diagram of the submission details list provided in this embodiment of the invention. When the submission details list is selected, the display interface shows the file upload status of all specified contacts. The submission details list clearly presents the number of specified collectors and the number of submissions, and also lists the name, email address, and file upload status (e.g., uploaded or not uploaded) of each specified contact (e.g., contact 1 and contact 2). This allows users to intuitively and comprehensively understand the file upload progress of each specified contact, facilitating real-time monitoring and management of the file collection process. If no one has submitted a file yet, there will be no files in the first file collection. When the user selects this first file collection, a prompt page will be displayed, with the prompt text possibly stating, "There are no files in this folder yet. Share it with your friends again to collect files." See also... Figure 17 , Figure 17 This is a schematic diagram of the prompt page provided in an embodiment of the present invention. At this time, the prompt page can further display a trigger button for sharing again. If the user clicks the trigger button, the user will be redirected to the link sharing page.

[0094] In this embodiment of the invention, if the collection mode is targeted and a designated contact uploads files, the upload status of all designated contacts can be viewed through the submission details list. Users can conveniently view and manage each file collection task individually. Especially in targeted collection scenarios, it is possible to accurately and comprehensively grasp the upload progress of each designated contact, promptly understand which contacts have completed the upload and which have not yet uploaded, facilitate real-time tracking and supervision of the file collection process, and help with subsequent organization and statistics of the collected files, improving the manageability and transparency of the file collection work, making the file collection process clearer and more efficient. When no files are uploaded in the first file set, a prompt page is triggered by selecting the operation, clearly informing the user that no files have been submitted at present. This avoids misunderstandings such as operational errors or task configuration abnormalities caused by no files displayed on the interface, reducing unnecessary troubleshooting costs. At the same time, a button for sharing is directly provided, eliminating the need for users to return to the configuration page or search for the sharing function in the historical operation path. Users can jump to the link sharing page with one click, improving task sharing efficiency and optimizing user experience.

[0095] Furthermore, before performing step S11, the method further includes: S103. Configure the fifth configuration item, which is associated with one or more designated contacts; when configuring a designated contact, the first file set includes only files from the second emails sent by the designated contact that are associated with the first email and / or the first file collection task.

[0096] For example, when the collector configures the fifth configuration item in the configuration interface, they can manually add one or more designated contacts, such as specific email accounts, enterprise address book users, department groups, etc. The system will generate permission filtering rules based on this configuration. Only files submitted by users listed in the designated contact list and associated with the first email and the first file collection task in the second email will be included in the first file set. Users not listed in the designated contact list, even if they obtain the file collection task and submit files through forwarding or other means, will not have their files recognized and collected by the system, and may even be directly blocked from completing the upload operation. By configuring designated contacts, the list of contacts who can submit files to this file collection task can be accurately defined, thereby achieving control over the source of file collection.

[0097] For example, collector A initiates a file collection task, adding only 10 members as designated contacts in the fifth configuration item. If employee C is not among these 10 members, even if they receive the file collection task through forwarding and submit files, the system will refuse to include their files in the first file set because employee C is not on the designated contact list. Only files submitted by the 10 designated members will be collected into the first file set corresponding to the task. When collector A views the files, they will only see the submissions from these 10 designated contacts, ensuring the security and accuracy of file collection.

[0098] For example, the fifth configuration item is Figure 6 For configuration options after selecting the directional mode in the collection mode, please refer to [link / reference]. Figure 18 , Figure 18 This is a schematic diagram of the interactive interface when the targeted collection mode provided in this embodiment of the invention is triggered. At this time, the interactive interface displays the "Targeted Mode (Specified Contacts Can Upload)" trigger state and presents an interactive area for "Add Specified Contact." This area includes an input box for entering a mobile phone number or email address and a "Contacts" button. The interactive interface also presents an email notification button, which is selected. When this button is selected, it indicates that a first email needs to be sent to notify the specified contact. If the button is not selected, no first email needs to be sent. After the targeted collection mode is detected as triggered, the user can manually enter the mobile phone number or email address of the specified contact in the input box, or click the "Contacts" button to select a contact from the address book, etc., to determine the specified contact who can upload files in the targeted collection mode.

[0099] In this embodiment of the invention, when the targeted collection mode is triggered, an interactive interface for inputting a designated contact person is displayed. Based on the user's input on this interface, the designated contact person for the targeted collection mode is determined. This precisely limits the scope of personnel who can participate in file uploads, ensuring that file collection tasks are only open to specific contacts. This effectively guarantees the targeted nature and security of file collection, preventing unauthorized or malicious uploads. Simultaneously, it makes the file collection process more organized, facilitating subsequent management and traceability of collected files, and improving the overall efficiency and reliability of the file collection process.

[0100] Furthermore, the method also includes: S14. When the contact successfully retracts the second email they sent, the first file set does not include the first file contained in the successfully retracted second email.

[0101] For example, when a contact successfully recalls a second email related to the first document collection task via the recall function of an email client / web interface, the system will synchronize the recall operation in real time and dynamically update the first document set, removing the first document contained in the recalled second email from the first document set. For instance, collector A initiates a weekly report collection task, and contact B submits a second email containing the weekly report document. This weekly report is then included in the first document set. Subsequently, contact B discovers an error in the data in the weekly report and successfully recalls the second email via the email client. At this point, the system will detect the recall command and automatically delete contact B's weekly report from the first document set. When collector A views the first document set for this task, they will not see this erroneous weekly report. Only after contact B corrects the weekly report data and resubmits a new second email will the system reinstate the new document to the first document set.

[0102] In this embodiment of the invention, by supporting the dynamic linkage between email recall and file collection, the problem of erroneous files not being automatically removed after submission in traditional file collection methods, which easily leads to file version confusion, is solved. In this implementation, contacts can promptly recall emails upon discovering file errors, and the system synchronously removes the erroneous files. This avoids misjudgment or misuse by the collector due to the retention of erroneous files, ensuring the accuracy and validity of files within the first file collection, as well as the dynamic updating function of the first file collection. It eliminates the need for the collector to manually filter and delete erroneous files, reducing the collector's post-processing costs.

[0103] Furthermore, before performing step S11, the method further includes: S104. Configure the sixth configuration item, which is related to the file collection deadline; when the user-set file collection deadline or the pre-configured file collection deadline reaches N seconds, N≥0, a third email is received from the system. The third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

[0104] For example, the sixth configuration item corresponds to Figure 6 The configuration page includes options for setting the file collection deadline. When the collector operates on the sixth configuration item in the configuration interface, they must first set the deadline for this file collection task, such as December 30, 2025, at 24:00. The system also supports configuring a delay of N seconds after the deadline to send the summary notification. For example, N=0 means the third email will be sent immediately upon the deadline, and N=3600 means the third email will be sent one hour after the deadline. When the set file collection deadline is reached and N seconds have elapsed, the system will automatically generate and send the third email to the collector's client. This email is strongly associated with the first email and the first file collection task, and integrates the collected data from this task.

[0105] For example, when the first client triggers a file collection task, it sends the configuration information for this file collection operation to the mail server. The mail server can then know the file collection deadline and start a timer. After receiving the file collection task, the contact can upload a file by clicking on the task. After uploading the file, the contact will notify the mail server via email. The mail server records the collected file and the contact information of the person who sent the file, then checks the task deadline. If the deadline is reached, a third email is sent to the first client. See also... Figure 19 , Figure 19This is a schematic diagram of the third email provided in this embodiment of the invention. The third email displays information on the completion status of this file collection operation, including the number of contacts who sent the second email (e.g., 1 person submitted a file or 0 people submitted a file), the name of the contact who sent the second email (e.g., contact 1), the information of the first file contained in the second email (e.g., submission time and file information), and information related to downloading the first file (e.g., a button to download all files and / or the file name + file format displayed in the submitted file). It also provides a download path prompt for the collected files (e.g., you can download the collected files to your local computer by entering the "xxxx>xxxx>xxxx" folder). It should be noted that if no one submitted a file, the download path prompt and specific file information will not be displayed. In addition, the download link in the third email can be a one-click download button, such as the "Download All Files" button shown in the figure, allowing users to easily obtain all collected files. Alternatively, the download link can be a single download button for a specific file, such as the "File Name + File Format" button shown in the figure, allowing users to selectively choose which files to download. After the user selects the download link, a storage path editing page will be displayed, allowing the user to choose to download the file to a specified local folder.

[0106] In this embodiment of the invention, the third email is sent by the mail server when the file collection deadline is reached. This mechanism ensures that users obtain the final results of the file collection as soon as the task ends, eliminating the need for frequent manual checks on task progress and saving users time and effort. Since the third email contains complete information on the file collection, users are promptly and comprehensively informed of the final task status, facilitating subsequent organization and archiving of the collected files. Furthermore, the download links in the third email allow users to quickly initiate downloads and choose suitable local storage locations to meet personalized file storage needs, avoiding difficulties in finding downloaded files due to disorganized storage paths.

[0107] Furthermore, the first email displays the deadline for collecting the documents.

[0108] For example, the first email can display the deadline for file collection. This deadline is a task deadline set by the collector in the sixth configuration item. This information will be automatically integrated into the body of the first email or in a prominent position (such as the task information bar in the email header) and sent to all contacts simultaneously with the first email. After receiving the first email, the contacts can directly view the deadline from the email content without additional communication or inquiry, and clearly know the time requirement for file submission.

[0109] In this embodiment of the invention, by directly displaying the document collection deadline in the first email, all contacts can intuitively obtain the time point when they receive the task invitation, reducing late submissions or repeated inquiries caused by information asymmetry, and lowering the communication costs between the collector and the contacts.

[0110] Furthermore, after all the designated contacts configured in the fifth configuration item have sent the second email N seconds later, where N≥0, the first client receives a third email automatically sent by the email system. This third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

[0111] For example, if the sixth configuration item is not configured, i.e., no file collection deadline is set, the feedback node of the file collection task is no longer triggered by time, but by all designated contacts completing file submission. While recording each file upload information and corresponding contact information, the mail server will compare the list of designated contacts who have completed file uploads with the preset list of all designated contacts in real time. When the verification finds that all designated contacts have successfully uploaded files, there is no need to wait for the file collection deadline; the mail server will automatically generate a third email and send it to the first client N seconds after this condition is met. It should be noted that the feedback method triggered by all participants submitting and the feedback method triggered by the deadline can be chosen individually or coexist. If one is chosen, the collector can choose to wait for all participants to submit before summarizing or summarize at the deadline, depending on the nature of the task. If both coexist, the system will send a third email when either all participants submitting or the deadline is reached, providing double assurance that the collector receives the task results promptly.

[0112] In this embodiment of the invention, it is not necessary to rely on the deadline of a timer to trigger email feedback. Instead, the feedback node is obtained by verifying the submission status of all members in real time. This allows the file collection end to know the collection results as soon as the task is completed ahead of schedule, so as to quickly carry out subsequent file sorting, summarization and other work, and improve the overall task progress efficiency.

[0113] Furthermore, the method also includes: S15. Receive a second operation and display a first email set; wherein the first email set includes only the first email and / or the second email associated with the first email and / or the first file collection task.

[0114] For example, the second operation refers to an interactive operation triggered by the user on the first client to view all email correspondence related to the file collection task. For instance, clicking the "Associated Emails" button on the file collection task details page will automatically filter out all emails associated with the first email and the first file collection task, and integrate them into a first email set for display. This first email set contains only two types of emails: the first email that serves as the origin of the task (i.e., the file collection invitation email sent by the collector to the contact); and the second email generated after the contact submits the file (including submission emails that directly reply to the first email, follow-up submission emails generated through a forwarding link, etc.). See also Figure 20 , Figure 20 This is a schematic diagram of the first email set provided in an embodiment of the present invention. The first email set displays email entries related to the file collection operation. Each entry includes information such as recipient ID, collection task name, sending time, and email size.

[0115] It's important to note that this first email collection is specifically created for file collection operations. Regular emails sent by users are included in the general email address; the two are located in different functional areas within the email database. This distinction between the dedicated file collection email collection and the general email address is designed to improve the management efficiency of file collection-related emails. This is because file collection tasks often involve multiple rounds of communication and collaboration among multiple people. By categorizing these emails separately, users can quickly locate task-related emails without having to sift through a massive amount of regular emails, thus reducing search time.

[0116] In this embodiment of the invention, the information presented in the first email set makes it easy for users to quickly identify which contacts the emails were sent to by the first client, and which contacts responded to the emails. Furthermore, the information displayed in each email entry allows users to intuitively understand the basic situation of the corresponding file collection task, thereby efficiently managing emails related to file collection operations.

[0117] Furthermore, the method also includes: S16. Receive the third operation and display the task editing page of the first file collection task corresponding to the first file set.

[0118] For example, such as Figure 4 As shown, after displaying the list of first file sets, if the user selects any first file set, in addition to displaying the first file in that first file set, the user can also edit the first file collection task corresponding to that first file set again. That is, one or more configuration items from the first to the sixth configuration items can be re-edited, and then a new first file collection task is generated. It should be noted that even if the first file collection task is updated, the first file in that first file set remains unchanged.

[0119] In this embodiment of the invention, secondary editing of the created file collection task is supported. When the collection requirements change, the user can reconfigure the first to sixth configuration items through the task editing page without having to re-initiate a new task, which reduces the operational cost of task adjustment. Furthermore, the original file set remains unchanged after the task is updated, ensuring the stability of the collected files.

[0120] Furthermore, the method also includes: S17. Display the first control item, which is related to ending the first file collection task. When the first file collection task is ended through the first control item, files from emails received afterward will no longer be stored in the first file set.

[0121] For example, see Figure 21 , Figure 21 This is a schematic diagram showing the display when a task is terminated according to an embodiment of the present invention. When the collector manually triggers the instruction to terminate the first file collection task through the first control item, such as when the collector clicks the "Terminate Task" button, the system first pops up a prompt message. After the collector selects "OK", the file collection function corresponding to the task will be locked immediately. After that, regardless of whether the preset file collection deadline has been reached, and regardless of whether any contact continues to send a second email containing the first file, the files in these subsequent emails will no longer be included in the first file collection of the task. At the same time, the upload entry of the contact will also be closed simultaneously (if it is not closed, the uploaded file will be invalid). For example, if collector A initiates a file collection task, and after all the designated contacts have submitted reports and it has been verified that there are no omissions, collector A clicks the "Terminate Task" button (i.e., the first control item) on the interface, at this time, even if contact B sends a file the next day, the system will determine that the email belongs to the submission content after the task is completed, and will not include its file in the first file collection. When collector A views the first file collection, this delayed submission report will not appear.

[0122] In this embodiment of the invention, by setting a first control item to grant the collector the permission to manually end the file collection task, the collector can actively terminate the collection according to the actual task completion status, without having to passively wait for the deadline, which improves the flexibility and autonomy of the file collection task. After the task is completed, the subsequent submitted files are automatically intercepted, which can prevent lagging files from being mixed into the first set of files that have been sorted out, and reduce the cost of sorting out files for the collector.

[0123] Furthermore, the method also includes: S18. In response to the user's configuration completion operation, a sharing page containing the file collection task is displayed; wherein, the file collection task is generated after the first file to be collected is configured for collection through configuration items.

[0124] For example, this step corresponds to Figure 3 Steps 1.2 to 1.5 are described in the original text. The configuration is complete when the user clicks... Figure 6 This is triggered by clicking the "Complete" button on the configuration page. At this point, the first client sends the configuration information to the file collection server. The file collection server then generates a file collection task based on the configuration information. For example, the file collection server extracts key parameters such as the task identifier and file collection rules from the configuration information, processes and compresses these parameters using a specific hash algorithm or encoding rule, and generates a unique and concise string, such as "https: / / xxxxx.xxx". After generating the file collection task, the file collection server sends it to the first client, and the first client displays a sharing page containing the file collection task on its display interface. See also... Figure 22 , Figure 22 This is a schematic diagram of a sharing page provided in an embodiment of the present invention. The sharing page includes a QR code scanning section and a link sharing section. The QR code scanning section displays a QR code corresponding to the file collection task and indicates the validity period of the QR code. The link sharing section includes an introduction to this file collection operation and a file collection link, and also provides copy link and email share buttons, making it convenient for users to manually spread the file collection task and corresponding link to the target audience by copying the link or sharing it via email. If a user wants to notify a contact to upload a file by sending an email, they can click [button name missing]. Figure 22 The "Share Email" button in the settings will trigger the email sharing action and redirect you to the email editing page.

[0125] It's important to note that in both targeted and non-targeted collection modes, the recipient input field on the email editing page is blank. Alternatively, in targeted collection mode, the recipient input field is pre-filled with the email address of a specified contact person, making that contact the target. In non-targeted collection mode, the recipient input field is blank, and users can manually add a target contact. Furthermore, in targeted collection mode, users can select a specified contact when filling in the configuration information on the configuration page. If the target contact for the first email happens to be the specified contact, that contact can subsequently upload files; otherwise, they will not be able to upload files.

[0126] Additionally, during the configuration of the collection mode, if the email notification function is selected by default in the targeted collection mode, the designated contact may subsequently receive two first emails simultaneously. For example, if the designated contacts selected in the targeted collection mode include Contact 1 and Contact 2, when the configuration completion operation is detected, if the email notification function is triggered, the mail server will send the first email to Contact 1 and Contact 2. Simultaneously, when the configuration completion operation is detected, the sharing page is displayed. If the email sharing operation on the sharing page is triggered, and the user selects Contact 1 and Contact 3 as the target contacts in the email editing page, the mail server will send the first email to Contact 1 and Contact 3. In this case, Contact 1 receives two first emails, and Contacts 2 and 3 receive one first email, but only Contacts 1 and Contact 2 are eligible to upload files. However, in the non-targeted mode, users can send the first email to the target contacts through the email sharing operation on the sharing page. In this case, all users can upload files by replying to the first email.

[0127] In this embodiment of the invention, the file collection task is dynamically generated based on the collection task template and configuration information. This allows for precise binding of task naming rules, format requirements, deadlines, and other configurations, ensuring that files uploaded by contacts directly match the task's preset standards and preventing invalid submissions due to mismatched task information. Furthermore, the independent sharing page provides collectors with flexible distribution methods. In addition to email, links can be shared with one click to enterprise instant messaging tools, work groups, and other platforms, overcoming the limitations of single email distribution, adapting to multi-scenario collaboration needs, and improving the efficiency and scenario adaptability of file collection task initiation.

[0128] See Figure 23 , Figure 23 This is a flowchart of a second file collection method provided in an embodiment of the present invention. The second file collection method is applied to a second client and includes step S21.

[0129] S21. Receive a first email sent by a first client, the first email being related to a first file collection task; When the first client receives the first operation, it displays a first file set, which is related to the first file collection task. The first file set contains one or more first files contained in one or more second emails, and the second emails are associated with the first emails and / or the first file collection task.

[0130] It should be noted that the process of step S21 above can refer to the working process of the first client in the first file collection method described in the above embodiment, and will not be repeated here.

[0131] Furthermore, after performing step S21, the method further includes: S22. Receive the fifth operation and display the editing interface of the second email; wherein, the editing interface of the second email is the page that is redirected to after the reply function of the first email is triggered.

[0132] For example, after receiving the first email, the contact triggers the email reply function through the fifth action, such as clicking the reply button on the first email interface. Once the fifth action is triggered, the system automatically redirects to the editing interface of the second email, which is the reply email editing page associated with the first email. (See reference...) Figure 14 As shown, the second email carries the subject prefix of the first email by default, such as "RE: First File Collection Task". It also integrates functional controls related to this collection task, such as file upload area and first name option. Contacts can directly edit reply content and upload the first file to be submitted on this interface.

[0133] In this embodiment of the invention, by triggering the reply function to jump to the second email editing interface, the task reply and file submission are integrated into the same editing interface. The contact person does not need to switch back and forth between the email client and the file upload platform, which improves the efficiency of file submission.

[0134] Further, in step S21, the first email carries a file collection link related to the file collection task; after receiving the first email sent by the first client, the method further includes: S23. Receive the sixth operation and display the file upload page; wherein, the file upload page is the page that is redirected to after the file collection link is triggered, and the file collection link is generated based on the first client's collection configuration for the first file to be collected through configuration items.

[0135] For example, the sixth operation refers to the triggered action performed by the contact after receiving the first email from the first client, in response to the file collection link carried in the email, such as clicking the "Click to Upload File" link in the email body. When the sixth operation is triggered, the system will automatically redirect to the file upload page bound to this file collection task. The functional layout and file requirements of this page are generated based on the task information pre-configured by the collector. The process of generating the file collection link can be referred to the above description, and will not be repeated here.

[0136] In this embodiment of the invention, the file collection link is deeply integrated with the task configuration information. The uploaded page after redirection displays all file submission rules, allowing contacts to understand the operational requirements without repeatedly reviewing the email body, reducing invalid submissions due to unclear rules, and lowering communication costs. Furthermore, clicking the link directly leads to the upload page, eliminating the need for third-party tools or complex procedures, thus simplifying the file submission process for contacts.

[0137] Further, in step S23, the file upload page includes basic task information and a file upload area; wherein, when a user uploads a file in the file upload area, a prompt message is displayed, and the prompt message is one of the following: The first notification indicates that the current user is not a designated contact. A second notification indicates that the document collection task has been completed; The current file does not meet the upload format requirements (third notification). The fourth message indicating that the current file has been successfully submitted.

[0138] For example, see Figure 24 , Figure 24 This is a schematic diagram of a file upload page provided in an embodiment of the present invention. The file upload page displays the task title, collector information, and task deadline (e.g., October 14, 2025, 15:24). It also includes an input box for entering a nickname and a file upload area specifying the file format (e.g., document format), such as a "+" button for easy file addition. Furthermore, the file upload page provides options to save a draft and submit directly, allowing contacts to choose whether to temporarily save the uploaded file or directly submit a prepared file based on their needs.

[0139] Furthermore, when a contact needs to upload a file, the system will automatically trigger the pre-verification function, which will check the upload subject, task status, and file attributes in sequence according to the preset task configuration rules, and display the corresponding prompt information in real time based on the verification results, including the following four types.

[0140] 1) The first prompt is that the current user is not a designated contact; For example, if the collector sets a specified contact list in the fifth configuration item, the system will verify whether the identity of the currently uploading user is on the list. If the user is not a specified contact, the upload page will display the first prompt. See [link to configuration details]. Figure 25 , Figure 25 This is a schematic diagram of the display of the first prompt information provided in the embodiment of the present invention. For example, the first prompt is "You are not the contact person set for this task and cannot upload files", which informs the user of the reason why the upload cannot be made and blocks the upload operation.

[0141] 2) A second notification indicating that the document collection task has ended; For example, the system will check the status of the current file collection task. If the collector has manually ended the task through the first control item, or if the collector has configured a task collection deadline in the sixth configuration item, and the current time has reached the deadline, and the contact still attempts to upload the file, a second prompt will pop up on the page. See [link to relevant documentation]. Figure 26 , Figure 26This is a schematic diagram of the display of the second prompt information provided in the embodiment of the present invention. For example, the second prompt is "The file collection task has been completed", so as to avoid the delayed submission of files from interfering with the archived file collection.

[0142] 3) The current file does not meet the upload format requirements (third prompt); For example, contacts can select files to upload from local storage or cloud files on the file selection page. Once a file is selected, the system automatically retrieves its information (including file format, size, name, etc.) and verifies it based on pre-defined rules for the file collection task, such as allowed file formats being PDF and Word, and a single file size not exceeding 10MB. If verification fails, for example, if the file format is an unauthorized compressed file or the file size exceeds the limit, the system will prohibit the file from uploading and display a third-party prompt message on the display interface. See [link to relevant documentation]. Figure 27 , Figure 27 This is a schematic diagram of the display of the third prompt information provided in the embodiment of the present invention. For example, the third prompt information may be "Does not meet the upload format requirements". If the verification is successful, the system will allow the file to be uploaded, and at the same time, display the file's abbreviated information (such as file name, size, format icon, etc.) on the file upload page for the user to confirm whether the selected file is correct.

[0143] 4) The fourth notification that the current file has been successfully submitted.

[0144] For example, when the file upload page's collection completion operation is triggered and the file is successfully sent to the file collection server, the interface will redirect to a submission success page. See also Figure 28 , Figure 28 This is a schematic diagram of the display of the fourth prompt information provided in the embodiment of the present invention. For example, the fourth prompt is "Submission successful". At the same time, the storage path of the file is clearly marked. For example, a prompt is given that "A total of 1 file has been successfully submitted to the other party. You can view it from the path xxx-xxxx-xxxx". This makes it convenient for users to confirm that the file has been uploaded as expected and to know its storage location. If they need to view it again or perform additional operations, they can quickly locate it according to the path.

[0145] In this embodiment of the invention, the upload page synchronously displays basic task information, allowing the contact person to review the task requirements at any time when submitting the file, eliminating the need to repeatedly check via email and reducing operational errors caused by information asymmetry. Categorized prompts are set for verification nodes in the upload process, providing real-time feedback on operation results. This includes clearly reminding and blocking invalid operations such as uploads by unauthorized contacts, uploads after the task has ended, and incorrect formats, while also providing success confirmation for compliant submissions. This allows the contact person to clearly understand the success or failure of the operation and the reasons, reducing the time cost of repeated attempts.

[0146] See Figure 29 , Figure 29 This is a structural block diagram of a first file collection device 100 provided in an embodiment of the present invention. The file collection device 100 is applied to a first client and includes: The first email sending module 11 is used to send a first email to at least one contact, the first email being related to the first document collection task; The first file set display module 12 is used to receive the first operation and display the first file set; Wherein, the first file set is related to the first file collection task; the first file set contains one or more first files contained in one or more second emails; the second emails are associated with the first emails and / or the first file collection task.

[0147] Furthermore, the document collection device 100 also includes: Configuration module, used for: The first file to be collected is configured for collection using configuration items, the collection configuration including a first configuration item, a second configuration item, and / or a third configuration item; Configure the fourth configuration item, which is related to the storage and / or display method of the first file; Configure the fifth configuration item, which is associated with one or more specified contacts; Configure the sixth configuration item, which is related to the file collection deadline.

[0148] Furthermore, the document collection device 100 also includes: The first file set update module is configured to ensure that, when the contact successfully retracts the second email they sent, the first file set does not contain the first file contained in the successfully retracted second email.

[0149] Furthermore, the document collection device 100 also includes: The third email receiving module is configured to receive a third email automatically sent by the email system after all the specified contacts configured in the fifth configuration item have sent the second email N seconds later, where N≥0. The third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

[0150] Furthermore, the document collection device 100 also includes: The first email collection display module is used to receive the second operation and display the first email collection; wherein the first email collection includes only the first email and / or the second email associated with the first email and / or the first file collection task.

[0151] Furthermore, the document collection device 100 also includes: The task editing page display module is used to receive a third operation and display the task editing page of the first file collection task corresponding to the first file set.

[0152] Furthermore, the document collection device 100 also includes: The task end module is used to display the first control item, which is related to ending the first file collection task. When the first file collection task is ended through the first control item, files from emails received afterward will no longer be stored in the first file collection.

[0153] It is worth noting that the working process of each module in the file collection device 100 described in the embodiments of the present invention can refer to the working process of the first file collection method described in the above embodiments, and will not be repeated here.

[0154] See Figure 30 , Figure 30 This is a structural block diagram of a second file collection device 200 provided in an embodiment of the present invention. The file collection device 200 is applied to a second client and includes: The first email receiving module 21 is used to receive a first email sent by a first client, the first email being related to a first file collection task; When the first client receives the first operation, it displays a first file set, which is related to the first file collection task. The first file set contains one or more first files contained in one or more second emails, and the second emails are associated with the first emails and / or the first file collection task.

[0155] Furthermore, the document collection device 200 also includes: The file upload page display module 22 is used to receive the sixth operation and display the file upload page; wherein, the file upload page is the page that is redirected to after the file collection link is triggered.

[0156] Furthermore, the document collection device 200 also includes: The prompt message display module 23 is used in the file upload page, which includes basic task information and a file upload area; wherein, when a user uploads a file in the file upload area, a prompt message is displayed, and the prompt message is one of the following: The first notification indicates that the current user is not a designated contact. A second notification indicates that the document collection task has been completed; The current file does not meet the upload format requirements (third notification). The fourth message indicating that the current file has been successfully submitted.

[0157] Furthermore, the document collection device 200 also includes: The email editing page display module is used to receive the fifth operation and display the editing interface of the second email; wherein, the editing interface is the page that is redirected to after the reply function of the first email is triggered.

[0158] It is worth noting that the working process of each module in the file collection device 200 described in the embodiments of the present invention can refer to the working process of the second file collection method described in the above embodiments, and will not be repeated here.

[0159] See Figure 31 , Figure 31 This is a structural block diagram of a file collection device 300 provided in an embodiment of the present invention. The file collection device 300 includes a processor 31, a memory 32, and a computer program stored in the memory 32 and executable on the processor 31. When the processor 31 executes the computer program, it implements the steps in the above-described embodiments of the various file collection methods.

[0160] For example, the computer program may be divided into one or more modules / units, which are stored in the memory 32 and executed by the processor 31 to complete the present invention. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the file collection device 300.

[0161] The file collection device 300 may include, but is not limited to, a processor 31 and a memory 32. Those skilled in the art will understand that the schematic diagram is merely an example of the file collection device 300 and does not constitute a limitation on the file collection device 300. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the file collection device 300 may also include input / output devices, network access devices, buses, etc.

[0162] The processor 31 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor 31 is the control center of the document collection device 300, connecting all parts of the document collection device 300 via various interfaces and lines.

[0163] The memory 32 can be used to store the computer programs and / or modules. The processor 31 implements various functions of the file collection device 300 by running or executing the computer programs and / or modules stored in the memory 32 and calling the data stored in the memory 32. The memory 32 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 32 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0164] If the modules / units integrated in the file collection device 300 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by the processor 31, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0165] Furthermore, the present invention also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the document collection method as described in any of the above embodiments.

[0166] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A method for collecting documents, characterized in that, Applied to a first client, the method includes: Send a first email to at least one contact, the first email being related to the first document collection task; Receive a first operation and display a first file set; wherein the first file set is related to a first file collection task; the first file set contains one or more first files contained in one or more second emails; the second emails are associated with the first emails and / or the first file collection task.

2. The document collection method as described in claim 1, characterized in that, The second email is associated with the first email and / or the first document collection task, including: The second email is a reply to the first email; or the second email is a follow-up email to the first email after it has been forwarded one or more times, wherein the follow-up email is an email sent by one or more of the at least one contact to the sender of the first email or an email sent by a user other than the at least one contact to the sender of the first email.

3. The document collection method as described in claim 1, characterized in that, Before sending the first email to at least one contact, the method further includes: The first file to be collected is configured for collection through configuration items, which include a first configuration item, a second configuration item, and / or a third configuration item.

4. The document collection method as described in claim 3, characterized in that, If there are multiple first files to be collected, the first files include a second file and a third file, and the configuration methods of the first configuration items of the second file and the third file are the same or different; and / or the configuration methods of the second configuration items of the second file and the third file are the same or different; and / or the configuration methods of the third configuration items of the second file and the third file are the same or different.

5. The document collection method as described in claim 3, characterized in that, The first configuration item is used to configure the naming method for one or more files in the first file; The naming convention is used for configuration file names, Including the following: The first naming convention is to use the original filename as the configuration file name; The second naming method is based on one or more first name configuration file names configured by the user in the collection configuration; wherein the file name includes the contact information.

6. The document collection method as described in claim 3, characterized in that, Also includes: The second configuration option is used to restrict the file format of the first file.

7. The document collection method as described in claim 3, characterized in that, The third configuration item is related to whether the corresponding first file must be transmitted.

8. The document collection method as described in claim 1, characterized in that, Before sending the first email to at least one contact, the method further includes: Configure the fourth configuration item, which is related to the storage and / or display method of the first file. The storage and / or display method includes one of the following: A first storage and / or display method is used to store and / or display the first file in one or more file subsets, folders or directories according to the contact from which it comes, wherein the name of the file subset, folder or directory is related to the name of the corresponding contact. The second storage and / or display method is used to store and / or display the first file in a subset of files, folders, or directories associated with the first name, according to one or more first names configured by the user.

9. The document collection method as described in claim 8, characterized in that, When the storage and / or display method is the second storage and / or display method, the editing interface related to the second email displays one or more first name options to associate the first file with the first name.

10. The document collection method as described in claim 1, characterized in that, When the first contact among the at least one contact sends two or more first files with the same file name, for the two or more first files with the same file name, the first file set only includes the first file sent latest.

11. The document collection method as described in claim 1, characterized in that, Before sending the first email to at least one contact, the method further includes: Configure the fifth configuration item, which is associated with one or more designated contacts; when configuring a designated contact, the first file set includes only files from the second emails sent by the designated contact that are associated with the first email and / or the first file collection task.

12. The document collection method as described in claim 1, characterized in that, The method further includes: When the contact successfully retracts the second email they sent, the first file set does not contain the first file contained in the successfully retracted second email.

13. The document collection method as described in claim 1, characterized in that, Before sending the first email to at least one contact, the method further includes: Configure the sixth configuration item, which is related to the file collection deadline. When the user-set file collection deadline or the pre-configured file collection deadline reaches N seconds (N≥0), a third email is received from the system. This third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

14. The document collection method as described in claim 13, characterized in that, The first email shows the deadline for collecting the document.

15. The document collection method as described in claim 11, characterized in that, After all the designated contacts configured in the fifth configuration item have sent the second email, N seconds later (N≥0), the first client receives a third email automatically sent by the email system. The third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

16. The document collection method as described in claim 1, characterized in that, The method further includes: Receive a second operation to display a first email set; wherein the first email set includes only the first email and / or the second email associated with the first email and / or the first file collection task.

17. The document collection method as described in claim 1, characterized in that, After displaying the first set of files, the method further includes: Upon receiving the third operation, the task editing page for the first file collection task corresponding to the first file set is displayed.

18. The document collection method as described in claim 1, characterized in that, The method further includes: The first control item is displayed. The first control item is related to ending the first file collection task. When the first file collection task is ended through the first control item, files from emails received afterward will no longer be stored in the first file collection.

19. A method for collecting documents, characterized in that, Applied to a second client, the method includes: Receive a first email sent by a first client, the first email being related to a first file collection task; When the first client receives the first operation, it displays a first file set, which is related to the first file collection task. The first file set contains one or more first files contained in one or more second emails, and the second emails are associated with the first emails and / or the first file collection task.

20. The document collection method as described in claim 19, characterized in that, The second email is associated with the first email and / or the first document collection task, including: The second email is a reply to the first email; or the second email is a follow-up email to the first email after it has been forwarded one or more times, wherein the follow-up email is an email sent by one or more of the at least one contact to the sender of the first email or an email sent by a user other than the at least one contact to the sender of the first email.

21. The document collection method as described in claim 19, characterized in that, After receiving the first email sent by the first client, the method further includes: Upon receiving the fifth operation, the editing interface of the second email is displayed; wherein, the editing interface of the second email is the page that is redirected to after the reply function of the first email is triggered.

22. The document collection method as described in claim 19, characterized in that, The first email carries a file collection link related to the file collection task. After receiving the first email sent by the first client, the method further includes: The sixth operation is received, and the file upload page is displayed; wherein, the file upload page is the page that is redirected to after the file collection link is triggered.

23. The document collection method as described in claim 22, characterized in that, The file upload page includes basic task information and a file upload area; when a user uploads a file in the file upload area, a prompt message is displayed, which may be one of the following: The first notification indicates that the current user is not a designated contact. A second notification indicates that the document collection task has been completed; The current file does not meet the upload format requirements (third notification). The fourth message indicating that the current file has been successfully submitted.

24. The document collection method as described in claim 22, characterized in that, The file collection link is generated based on the first client's configuration settings for the first file to be collected.

25. The document collection method as described in claim 19, characterized in that, Before sending the first email to at least one contact, the first client configures the collection of the first file to be collected through configuration items, the collection configuration including a first configuration item, a second configuration item and / or a third configuration item.

26. The document collection method as described in claim 25, characterized in that, If there are multiple first files to be collected, the first files include a second file and a third file, and the configuration methods of the first configuration items of the second file and the third file are the same or different; and / or the configuration methods of the second configuration items of the second file and the third file are the same or different; and / or the configuration methods of the third configuration items of the second file and the third file are the same or different.

27. The document collection method as described in claim 25, characterized in that, The first configuration item is used to configure the naming method for one or more files in the first file; The naming convention is used for configuration file names, Including the following: The first naming convention is to use the original filename as the configuration file name; The second naming method is based on one or more first name configuration file names configured by the user in the collection configuration; wherein the file name includes the contact information.

28. The document collection method as described in claim 25, characterized in that, The second configuration option is used to restrict the file format of the first file.

29. The document collection method as described in claim 25, characterized in that, The third configuration item is related to whether the corresponding first file must be transmitted.

30. The document collection method as described in claim 19, characterized in that, Before sending the first email to at least one contact, the first client configures a fourth configuration item; wherein, the fourth configuration item is related to the storage and / or display method of the first file, and the storage and / or display method includes one of the following: A first storage and / or display method is used to store and / or display the first file in one or more file subsets, folders or directories according to the contact from which it comes, wherein the name of the file subset, folder or directory is related to the name of the corresponding contact. The second storage and / or display method is used to store and / or display the first file in a subset of files, folders, or directories associated with the first name, according to one or more first names configured by the user.

31. The document collection method as described in claim 30, characterized in that, When the storage and / or display method is the second storage and / or display method, the editing interface related to the second email displays one or more first name options to associate the first file with the first name.

32. The document collection method as described in claim 19, characterized in that, When the first contact among the at least one contact sends two or more first files with the same file name, for the two or more first files with the same file name, the first file set only includes the first file sent latest.

33. The document collection method as described in claim 19, characterized in that, Before the first client sends the first email to at least one contact, it configures a fifth configuration item; wherein the fifth configuration item is associated with one or more designated contacts; when a designated contact is configured, the first file set includes only files from a second email sent by the designated contact that is associated with the first email and / or the first file collection task.

34. The document collection method as described in claim 19, characterized in that, When the contact successfully retracts the second email they sent, the first file set does not contain the first file contained in the successfully retracted second email.

35. The document collection method as described in claim 19, characterized in that, Before sending the first email to at least one contact, the first client configures a sixth configuration item; wherein, the sixth configuration item is related to the file collection deadline; when the user-set file collection deadline or the pre-configured file collection deadline reaches N seconds, N≥0, a third email is received from the system, the third email being associated with the first email and / or the first file collection task, and including one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

36. The document collection method as described in claim 35, characterized in that, The first email shows the deadline for collecting the aforementioned documents.

37. The document collection method as described in claim 33, characterized in that, After all the designated contacts configured in the fifth configuration item have sent the second email, N seconds later (N≥0), the first client receives a third email automatically sent by the email system. The third email is associated with the first email and / or the first file collection task, and includes one or more of the following information: The name information of the contact who sent the second email; Information on the number of contacts who sent the second email; The second email contains the first file information; Information related to downloading the first file.

38. The document collection method as described in claim 19, characterized in that, The first client receives a second operation to display a first email set; wherein the first email set includes only the first email and / or the second email associated with the first email and / or the first file collection task.

39. The document collection method as described in claim 19, characterized in that, The first client receives the third operation and displays the task editing page of the first file collection task corresponding to the first file set.

40. The document collection method as described in claim 19, characterized in that, The method further includes: The first control item is displayed. The first control item is related to ending the first file collection task. When the first file collection task is ended through the first control item, files from emails received afterward will no longer be stored in the first file collection.

41. A document collection device, characterized in that, Applied to a first client, the device includes: The first email sending module is used to send a first email to at least one contact, the first email being related to the first document collection task; The first file set display module is used to receive the first operation and display the first file set; Wherein, the first file set is related to the first file collection task; the first file set contains one or more first files contained in one or more second emails; the second emails are associated with the first emails and / or the first file collection task.

42. A document collection device, characterized in that, Applied to a second client, the device includes: The first email receiving module is used to receive the first email sent by the first client, and the first email is related to the first file collection task. When the first client receives the first operation, it displays a first file set, which is related to the first file collection task. The first file set contains one or more first files contained in one or more second emails, and the second emails are associated with the first emails and / or the first file collection task.

43. A document collection device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the file collection method as described in any one of claims 1 to 40.

44. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the file collection method as described in any one of claims 1 to 40.

45. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the file collection method as described in any one of claims 1 to 40.

Images