Schedule file processing method and device, equipment, medium and program product

Abstract

The invention discloses a schedule file processing method and device, equipment, a storage medium and a program product, and the method comprises the steps: displaying a management interface of a schedule; the management interface comprises a file display control; in response to a trigger operation for the file display control, displaying summary information of at least one first file; the first file is a file related to the schedule. According to the method, when the user views or creates the schedule, the file information related to the schedule can be visually obtained, switching between a calendar application and a file management application is not needed, and the continuity and convenience of user experience are greatly improved.

Description

Technical Field

[0001] The present application relates to the field of file management technology, and in particular to a schedule file processing method, apparatus, device, storage medium and program product. Background Art

[0002] With the prevalence of digital office work, schedule management has become an indispensable part of efficient operations for individuals and businesses. However, traditional schedule management systems tend to focus on displaying and editing timelines, and their support for managing documents closely related to schedules (such as meeting materials, project documents, etc.) is relatively weak. This results in users frequently switching between schedule management and document management applications when preparing or reviewing schedules, which not only reduces work efficiency but also affects the consistency and convenience of the user experience. Summary of the Invention

[0003] In view of this, embodiments of the present application at least provide a schedule file processing method, apparatus, device, storage medium, and program product.

[0004] The technical solution of the embodiment of the present application is implemented as follows:

[0005] In one aspect, an embodiment of the present application provides a schedule file processing method, the method comprising:

[0006] A management interface for displaying schedules; the management interface includes a file display control;

[0007] In response to a triggering operation on the file display control, summary information of at least one first file is displayed; the first file is a file related to the schedule.

[0008] On the other hand, an embodiment of the present application provides a schedule file processing device, the device comprising:

[0009] A first display module is used to display a schedule management interface; the management interface includes a file display control;

[0010] The second display module is configured to display summary information of at least one first file in response to a triggering operation on the file display control; the first file is a file related to the schedule.

[0011] On the other hand, an embodiment of the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, it implements some or all of the steps in the above method.

[0012] On the other hand, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which implements some or all of the steps in the above method when executed by a processor.

[0013] On the other hand, an embodiment of the present application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements some or all of the steps in the above method.

[0014] In an embodiment of the present application, since schedule management and file management are integrated into the same application (such as a calendar application), when viewing or creating a schedule, the user can seamlessly switch to the file interface related to the schedule without having to switch between the calendar application and the file management application, which greatly improves the consistency and convenience of the user experience.

[0015] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit the technical solutions of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and, together with the specification, are used to illustrate the technical solutions of the present application.

[0017] Figure 1 A schematic diagram of the implementation process of a schedule file processing method provided in an embodiment of the present application Figure 1 ;

[0018] Figure 2A A schematic diagram of the overall interface of a calendar application provided in an embodiment of the present application;

[0019] Figure 2B A schematic diagram of the overall interface of another calendar application provided in an embodiment of the present application;

[0020] Figure 2C A schematic diagram of a management interface for an online conference scenario provided in an embodiment of the present application;

[0021] Figure 2D A diagram of a target session interface provided in an embodiment of the present application;

[0022] Figure 3A Schematic diagram 2 of a method for processing a schedule file according to an embodiment of the present application;

[0023] Figure 3B A schematic diagram of an interface for summarizing information in a folder interface provided in an embodiment of the present application;

[0024] Figure 3CA schematic diagram of an interface for summarizing information as a file list provided in an embodiment of the present application;

[0025] Figure 4A Schematic diagram 3 of the implementation flow of a schedule file processing method provided in an embodiment of the present application;

[0026] Figure 4B A schematic diagram of a management interface including file names provided in an embodiment of the present application;

[0027] Figure 5A Schematic diagram 4 of a flow chart for implementing a method for processing a schedule file provided in an embodiment of the present application;

[0028] Figure 5B A schematic diagram of an interface of a management interface including a file import area provided in an embodiment of the present application;

[0029] Figure 6A Schematic diagram 5 of an implementation flow of a schedule file processing method provided in an embodiment of the present application;

[0030] Figure 6B A schematic diagram of a file collection and setting interface provided in an embodiment of the present application;

[0031] Figure 7 A schematic diagram of the structure of a schedule file processing device provided in an embodiment of the present application;

[0032] Figure 8 A schematic diagram of the structure of a schedule file processing device provided in an embodiment of the present application;

[0033] Figure 9 A hardware entity diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions of this application are further elaborated in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limiting this application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0035] In the following description, references to "some embodiments" describe a subset of all possible embodiments. However, it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict. The terms "first / second / third" are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It is understood that the specific order or sequence of "first / second / third" may be interchanged where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein are for the purpose of describing this application only and are not intended to limit this application.

[0037] When users need to prepare materials for upcoming meetings, review records of past events, or simply confirm documents associated with their schedules, they have to frequently switch between calendar apps and file management apps. This not only increases the complexity of operations, but may also lead to omissions or confusion of information, seriously affecting work efficiency and the consistency of user experience.

[0038] In order to solve the above problems, the present application proposes a schedule file processing method, which realizes the seamless connection between schedule and file by introducing a file display control as an important component of the management interface. When the user triggers the control, the system can quickly respond and display the summary information of at least one first file associated with the current schedule. This information helps the user to quickly identify and understand the content of the files related to the schedule. The method can be executed by a processor of a computer device. The computer device may refer to a server, a laptop, a tablet computer, a desktop computer, a smart TV, a set-top box, a mobile device (such as a mobile phone, a portable video player, a personal digital assistant, a dedicated messaging device, a portable gaming device), or other device with data processing capabilities.

[0039] Figure 1 A schematic diagram of the implementation process of a schedule file processing method provided in an embodiment of the present application Figure 1 ,like Figure 1 As shown, the method includes the following steps S101 to S102:

[0040] Step S101: Display a schedule management interface; the management interface includes a file display control.

[0041] In some embodiments, the management interface may be any interface of a calendar application. The management interface may be an interface that records schedule information or an interface for creating schedules. The management interface may also include a file display control.

[0042] In some embodiments, the calendar interface of the calendar application can simultaneously display a schedule management interface and a preview interface of the schedule in the calendar. The preview interface is used to at least display the distribution of the schedule in a preset time period (such as a day, a week, or a year). In some embodiments, the preview interface can also display schedule information for multiple accounts. The management interface is used to display relevant information about the schedule, including but not limited to the schedule name, schedule time, and user accounts participating in the schedule.

[0043] like Figure 2A As shown, Figure 2A The overall interface of the calendar application is shown. The calendar interface 210 may include a management interface 211 and a preview interface 212. The preview interface 212 displays the account's schedule. For example, on January 1, 2030, user A is "busy" from 9:00 to 10:00, user B is "busy" from 10:00 to 11:00, and user C is "busy" from 13:00 to 14:00. The management interface 211 displays schedule information. For example, when creating a schedule from 14:00 to 15:00 on January 1, 2030, the schedule information can be configured on the management interface 211. For example, the schedule name, schedule time, meeting minutes template, adding participants, adding meeting location, adding meeting materials, and reminder methods can be configured.

[0044] In some embodiments, the schedule is associated with at least two accounts; the at least two accounts associated with the schedule are accounts participating in the schedule. In response to a trigger operation for a target time interval in a calendar interface, a management interface based on the target time interval can be displayed. The target time interval in the calendar interface corresponds to a target schedule time and at least two accounts; the schedule time in the management interface is the target schedule time; and the accounts participating in the schedule include the two accounts corresponding to the target time interval.

[0045] For example, see Figure 2A In response to the triggering operation on the target time area 213 in the preview interface 212, the management interface 211 displays the schedule management interface corresponding to the target time area 213. Since the target time area 213 is between 14:00 and 15:00 on January 1, 2030, the "Schedule Time" in the management interface 211 is automatically filled with the above time information; similarly, since the target time area 213 corresponds to user A, user B and user C, the "Participants" in the management interface 211 are automatically filled with the above user A, user B and user C.

[0046] In other embodiments, the calendar interface of the calendar application may first display a preview interface of the schedule in the calendar, and in response to a triggering operation on the schedule, display a management interface of the schedule in a pop-up window.

[0047] like Figure 2B As shown, Figure 2B The overall interface of the calendar application is shown, and the calendar interface 220 may include a preview interface 221. The preview interface 221 may display calendar information, such as Figure 2B At the same time, the preview interface 221 also includes a "New Schedule" control 222. In response to the triggering operation of the "New Schedule" control 222, the management interface 223 is displayed in a pop-up window. In some embodiments, the management interface 223 also includes a "More Options" control 224. In response to the triggering operation of the "More Options" control 224, the user jumps to Figure 2A Calendar interface 210 is shown.

[0048] In some embodiments, a schedule can be associated with activities in a real scene; the activities that the schedule can be associated with may include, but are not limited to, at least one of the following: online activities; offline activities. The online activities may include, but are not limited to, at least one of the following: online meetings; online speeches; online interviews; online classes; online live broadcasts. The offline activities may include, but are not limited to, offline meetings, offline travel, offline speeches, offline interviews, offline classes, offline meetings, etc. Correspondingly, the at least two accounts associated with the schedule are accounts participating in activities in the real scene. Taking the activity as an online meeting as an example, the at least two accounts associated with the schedule are accounts used to participate in the online meeting. In order to fully illustrate the embodiments of the present application, the embodiments below will be described using the example of a schedule associated with an online meeting. This example does not limit the application scenario of the present application.

[0049] In some embodiments, the schedule management interface also includes an activity portal for online participation in the online activity referenced by the schedule. For example, if the online activity is an online meeting, the activity portal may be a link or meeting ID that calls an online meeting application to access the online meeting. For example, if the schedule displays an online meeting, it may be supported by the conferencing capabilities of a conferencing component or conferencing application. This conferencing component or conferencing application may be a third-party component or application.

[0050] In some embodiments, the schedule management interface also includes activity settings. Assuming the schedule is an online meeting, the management interface may support meeting settings, which may include setting the application used for the online meeting, setting the duration of the online meeting, setting the meeting number of the online meeting, etc.

[0051] See also Figure 2C, which shows a schematic diagram of the management interface in an online conference scenario. Figure 2C As shown, in addition to schedule-related information, the management interface 230 also includes an activity entry 231 and activity settings 232. In response to a trigger operation on the activity entry 231, the user can directly enter the video conference corresponding to the schedule through the conference component or conference application; in response to a trigger operation on the activity settings 232, the user can enter the conference settings interface and further set the application used for the online conference, the duration of the online conference, the meeting number of the online conference, etc.

[0052] In some embodiments, the schedule points to an online activity; during the online activity, the method further includes at least one of the following: displaying or playing the first file; distributing the first file to participating accounts participating in the activity; and collecting files after the participating accounts update the first file.

[0053] In the above embodiment, displaying or playing the first file means presenting the pre-prepared file (the first file) to the account participating in the activity in a visual or audible manner during the online activity. The first file can be, but is not limited to, a document, a picture, a video, an audio, or other forms of content. For example, taking the online activity as an online meeting, the first file can be a PPT document. The host can display the PPT document using the screen sharing function, and the participants can see and follow the explanation in real time.

[0054] In the above embodiment, distributing the first file means sending the file in electronic form to each account participating in the online activity, ensuring that they can view and use the first file at any time before, during, after, or when needed. For example, taking the online activity as an online interview, the first file can be interview materials. The interviewer can use the file transfer function of the online platform to package or send the files individually to the designated receiving end of each participating account (such as a conversation, mailbox, cloud disk link, etc.). Participants can read the background materials based on the first file to facilitate subsequent communication with the interviewer based on the first file.

[0055] In the above embodiment, collecting updated files means allowing and receiving a new version of the first file edited or modified by the participating account during or after the activity for integration or evaluation. For example, taking the online activity as an online interview, the first file can be a test question (Word document). The interviewer can use the file transfer function of the online platform to package or send the file separately to the designated receiving end of each participating account (such as a conversation, mailbox, cloud disk link, etc.). The participant can edit and answer the test question, and receive the new version of the first file edited by the participant after completion or after the time is up, so that the subsequent interviewer can evaluate the participating account based on the updated first file.

[0056] In some embodiments, the schedule management interface may also be used to display schedule information for the schedule. When creating schedule information for a schedule, the schedule information may include but is not limited to at least one of the following:

[0057] Create schedule information for the schedule based on the schedule creation template;

[0058] Access the text information input interface to create schedule information. This method can be used to quickly create schedules by importing information from third-party applications.

[0059] Establishing schedule information for a schedule based on one or more drop-down menus in a schedule creation dialog box;

[0060] The first account selects one or more time periods to create schedule information of a schedule on a schedule interface based on a schedule shared by one or more other accounts.

[0061] Step S102: In response to a triggering operation on the file display control, display summary information of at least one first file; the first file is a file related to the schedule.

[0062] In some embodiments, the management interface also includes a file display control. Upon receiving a trigger operation for the file display control, the corresponding folder or file can be opened, i.e., the user is redirected to a file interface. This file interface can be a folder interface or a file interface. The folder interface displays file information for one or more files. The file information displayed within the folder interface may include, but is not limited to, file images, file names, and / or file links.

[0063] In some embodiments, the trigger operation is any user operation or a device operation performed by the electronic device based on a pre-configured configuration. For example, the trigger operation may be an operation such as a user clicking operation or a sliding operation to display the summary information of at least one first file. Figure 2A The management interface 211 includes the file display control 214, namely the "Conference Materials" control. Figure 2B The management interface 223 includes the file display control 225, namely the "Conference Materials" control. Figure 2C The management interface 230 includes a file display control 233, namely a "meeting materials" control.

[0064] In an embodiment of the present application, since schedule management and file management are integrated into the same application (such as a calendar application), when viewing or creating a schedule, the user can seamlessly switch to the file interface related to the schedule without having to switch between the calendar application and the file management application, which greatly improves the consistency and convenience of the user experience.

[0065] In some embodiments, summary information refers to a method of centrally displaying information about at least one first file so that a user can quickly browse and obtain the required information. In a schedule management interface, the summary information may include file icons and file information for files related to the schedule. The summary information includes at least one of the following: a file icon for the at least one first file, and file information for the at least one first file.

[0066] The file icon can be used to indicate the file type of the first file. In the embodiment of the present application, different types of files (such as documents, pictures, videos, etc.) usually have different icons to facilitate users to quickly identify the nature and content of the file. The file information can include various data related to the file, including but not limited to the file name, file size, creation date, modification date, author, file type, etc. This file information helps users understand the basic properties and status of the file.

[0067] In some embodiments, the schedule is associated with at least two accounts; the method further includes: in response to a display event of a session interface of the target session, displaying the at least one first file in the session interface.

[0068] The target session includes the at least two accounts.

[0069] In some embodiments, the display event of the session interface of the target session may be generated in response to a trigger operation on a session management control in the management interface. The method further includes: entering the session interface of the target session in response to the trigger operation on the session management control in the management interface.

[0070] The management interface also includes a session management control. After receiving a trigger operation for the session management control, the user can enter the session interface corresponding to the target session. Alternatively, the target session can be created and the session interface corresponding to the target session can be entered. The accounts participating in the target session include the at least two accounts associated with the schedule. It is understood that the target session is a conversation or discussion directly related to the schedule, which may include discussion, preparation, and follow-up regarding the schedule.

[0071] For example, if the accounts associated with the schedule include "User A", "User B" and "User C", accordingly, in the process of entering the session interface of the target session in response to the trigger operation of the session management control in the management interface, the target session also includes "User A", "User B" and "User C", that is, "User A", "User B" and "User C" are also participating users of the target session.

[0072] In some embodiments, the calendar application can be any application that supports date display. In some embodiments, the calendar application itself can also support conversations, that is, the calendar application itself has both scheduling and conversation capabilities. This allows for the integration of conversations and schedules through the calendar application, enhancing the intelligence of the calendar application and the user experience. In this case, the calendar application may include a calendar component that supports scheduling and a conversation component that supports conversations. For example, this conversation capability may include, but is not limited to, instant messaging. In other embodiments, the calendar application may support the ability to call a conversation application. In this case, the conversation management control is more likely to be an application programming interface (API) that calls the conversation application.

[0073] In some embodiments, the conversation interface can be displayed in the calendar interface in the above embodiments; the conversation interface can also be other interfaces independent of the calendar interface, management interface or preview interface; the conversation interface can also be displayed in the form of a floating window on the calendar interface, management interface or preview interface, which is not limited in this application.

[0074] See also Figure 2D , which shows a schematic diagram of a conversation interface of a target conversation. Figure 2D As shown, the conversation interface 240 provides at least a conversation area 241 and a file display area 242 , wherein the conversation area 241 is used to display chat messages of accounts participating in the target conversation, and the file display area 242 is used to display the at least one first file.

[0075] In some embodiments, the method further includes: in response to a closing event of a session interface of the target session, adjusting the first file based on the collected session records for the first file.

[0076] The closing event is generated in response to the conversation interface being actively or automatically closed by the user.

[0077] In some embodiments, semantic analysis may be performed on the session record for the first file to generate a file adjustment instruction for the first file, and the first file may be adjusted using the file adjustment instruction.

[0078] During the target conversation, the conversation log of the target conversation can be checked periodically or in real time. The chat messages in the conversation log can be in the form of text, images, files, etc. A preset semantic recognition algorithm (such as a natural language processing and machine learning algorithm) is then used to identify discussion content related to operations on the first file (the file related to the schedule), such as "delete the nth file," "the newly added file should be placed on the first line," or "the newly added file should be placed in the first position." File adjustment instructions are then generated based on the conversation log, and the files related to the schedule are adjusted using the file adjustment instructions.

[0079] For example, while participating accounts in a target conversation were discussing a presentation document for the meeting, they exchanged suggestions for modifications to the presentation document through the chat interface, such as "delete the third presentation document" and "place the newly added presentation document in the first position." After the conversation interface was closed, the system automatically collected and parsed the conversation log. Based on the parsing results, the system generated corresponding file adjustment instructions and automatically updated the file count and location of at least one first file associated with the schedule.

[0080] In some embodiments, the method further includes: in response to an open event for a target first file among the at least one first file, displaying the file content of the target first file through the session interface; accepting an editing operation for the target first file, and updating the target first file based on the editing operation; and in response to a close event for the target first file, saving the updated target first file.

[0081] The open event is triggered by an interface operation of the current account, indicating that the current account wishes to view or edit the contents of the target first file. Correspondingly, the close event is triggered by an interface operation after the current account completes viewing or editing the file, indicating that the current account wishes to end the current file operation.

[0082] In some embodiments, when the current account triggers an open event, the current content of the target first file is displayed through the conversation interface for the user to view. During the display of the target first file, editing operations input by the current account are received, such as text input, image selection, table modification, etc.; according to the received editing operations, the content of the target first file is updated in real time; when the current account completes editing and triggers a close event, a file save operation is executed to save the updated target first file to a specified storage location. For example,

[0083] In the above embodiment, the file content is displayed and editing operations are received through the conversation interface, so that the user can intuitively see the current status of the file and make modifications, thereby improving the user experience; at the same time, the file is automatically saved when a close event occurs, and the file associated with the schedule can be updated in real time so that other accounts can obtain the latest first file.

[0084] Figure 3A This is a second flow chart of a method for processing a schedule file provided in an embodiment of the present application. This method can be executed by a processor of a computer device. Figure 1 , Figure 1 Step S102 in the above example can be updated to step S201 or step S202, which will be combined with Figure 3A The steps shown are explained.

[0085] Step S201: Displaying a folder interface of a first folder; the folder interface of the first folder displays a file icon of the at least one first file.

[0086] The folder interface is an area in a graphical user interface (GUI) for displaying folder contents (e.g., files, subfolders, etc.). Generally speaking, a folder interface may include information such as icons and names of files or folders, allowing users to browse and manage files visually.

[0087] In some embodiments, at least one first file associated with a schedule has been collected into a first folder, and an association relationship between the schedule and the first folder has been pre-established. Furthermore, the folder interface of the first folder can be opened and displayed through the address of the first folder.

[0088] In some embodiments, information of all files associated with the schedule can be retrieved from a database based on the identifier of the current schedule (such as an ID) and the established association between the schedule identifier and the first file; for each retrieved first file, the corresponding icon resource is called according to its file type, or an icon is dynamically generated according to the file extension; according to a preset folder interface layout, the file icon of at least one first file is placed in a folder interface in a certain order and arrangement; finally, the folder interface of the above-mentioned first folder is displayed to the user, and the user can see the icons of all files associated with the schedule in the interface.

[0089] See also Figure 3B , which shows a schematic diagram of an interface for summarizing information into a folder interface. Figure 3B As shown, the folder interface 320 is the folder interface of the first folder (schedule folder). There is a folder directory on the left side of the folder interface 320, which shows that the currently viewed file is the associated file of the "schedule folder". The right area 321 of the folder interface 320 is used to display the icons and brief descriptions of each first file in the first folder: Video 1 (the icon is a video player icon, and the file name or thumbnail is displayed near the icon), Folder 1 (the icon is a folder icon, and the folder name is displayed next to it. Click to expand and view sub-items, but it is not expanded in this example), Document 1 (the icon is a document icon, and the file name is displayed near the icon), Picture 1 (the icon is a picture icon, and the picture name is displayed near the icon), Music 1 (the icon is a music player icon, and the music name is displayed next to it).

[0090] Step S202: Display a file list; the file list includes file information of the at least one first file; the file information is used to open the first file.

[0091] Among them, the file list is used to display a list of at least one first file (file). This list can contain basic information such as the file name, size, type, modification date, etc. Unlike the above-mentioned folder interface, the purpose of the file list is to allow users to quickly browse and locate specific files without having to enter a deeper directory structure. The folder interface displays the hierarchical structure of the file system, that is, it allows users to organize and manage files through "folders" or "directories". In the folder interface, users can create new folders, move files from one folder to another, rename folders, etc.

[0092] In some embodiments, the file information of the first list includes: the file name of the first file and the file link of the first file.

[0093] The file link may include, but is not limited to, a link corresponding to a shortcut, a hard link, a directory link, a soft link, or a symbolic link.

[0094] See also Figure 3C , which shows a schematic diagram of an interface that summarizes information into a file list. Figure 3C As shown, interface 330 is a display interface for a file list (schedule file list). Among them, the file list 331 in interface 330 can be used to display the file name of each first file and possible other information (such as file size, modification date, etc.), but in this example, the file list mainly displays the file name and the link or address for opening the file. File list 331 displays: Video 1 and the corresponding address: E:\Richeng1\Video 1, Video 2 and the corresponding address: E:\Richeng1\Folder\1Video 2, Document 1 and the corresponding address: E:\Richeng1\Document 1, Picture 1 and the corresponding address: E:\Richeng1\Picture 1, Music 1 and the corresponding address: E:\Richeng1\Music 1. It can be seen that compared to Figure 3B The folder interface shown is Figure 3C The file system hierarchy is not displayed, and the file list directly displays the file information in the subfolders.

[0095] In some embodiments, the file list may be displayed in the management interface in the form of a floating window in response to a triggering operation on the file display control.

[0096] In some embodiments, filtering and sorting options are provided above or next to the file list, allowing users to dynamically filter and sort the file list based on conditions such as file name, type, size, modification date, etc. This approach can improve the efficiency of users finding files, especially when dealing with a large number of files.

[0097] In some embodiments, when the number of first files is too large, paging or scrolling can be used to display them. The paging method divides the file list into multiple pages, and the user needs to click different page numbers to browse different pages; the scrolling method allows the user to browse the entire file list by dragging the scroll bar.

[0098] In an embodiment of the present application, the file information of each first file is displayed in various lists or in a centralized display of file icons on the management interface, making it convenient for users to centrally view the file information of these files and / or select the files they want to view through the management interface.

[0099] In some embodiments, the method further comprises: collecting the at least one first file.

[0100] In some embodiments, collecting at least one first file may include but is not limited to at least one of the following: storing all files related to the schedule in the same folder; storing all files related to the schedule in a folder related to the schedule; and organizing the file information of files related to the schedule into an information table or summarized information entries.

[0101] In some embodiments, the at least one first file may be searched for through an established association between a schedule identifier and the first file; in other embodiments, a range of files related to a specific schedule may be determined, and the at least one first file may be searched for through a file manager or a search tool.

[0102] In some embodiments, storing all schedule-related files in the same folder includes: identifying all schedule-related files, and then moving them to a pre-set common folder using a file manager. It is understandable that after determining all the first files related to a specific schedule, regardless of their type, source or specific purpose, they are all stored in the same folder on a computer, cloud storage or any other storage medium. In this way, by placing all related files in the same location, users can easily find and access these files without having to search between multiple locations. For example, assuming that the above schedule is an online meeting, accordingly, the PPT, speech manuscripts, reference articles, etc. related to the online meeting can all be moved to a folder named "Online Meeting".

[0103] In some embodiments, storing all files related to the schedule in a folder related to the schedule may include: identifying all files related to the schedule, determining the schedule corresponding to each first file, and then storing the files in the folder where the corresponding schedule is located according to the schedule. That is, the same folder includes all the first files of the same schedule, and the folders of different schedules include different first files. For example, if there are multiple online meetings taking place at the same time, each online meeting has a series of related files. If there are multiple online meetings, a separate folder needs to be created for each online meeting, such as "Online Meeting A Folder", "Online Meeting B Folder", etc., and then the first files corresponding to each online meeting are stored in the corresponding folder.

[0104] In some embodiments, organizing the file information of files related to the schedule into an information table or summarized information entries includes: identifying all files related to the schedule, determining the file information (file name and file link) of each first file, and then organizing the obtained file information of each first file into an information table or summarized information entries.

[0105] In some embodiments, the collecting of at least one first file includes at least one of the following: storing the at least one first file in the first folder; the first folder is related to the schedule; writing the file information of the at least one first file into the file list; the file list is related to the schedule.

[0106] The first folder is a specially set folder related to the schedule. In some embodiments, when the at least one first file is stored in the first folder, the file can be automatically and intelligently classified based on the first file type (such as document, picture, audio, etc.), creation time, content keywords, or user-preset rules, and assigned an easily recognizable file name or label. This not only facilitates rapid file retrieval, but also keeps the folder neat and orderly.

[0107] The first list can be a table in various formats that summarizes the file information of the first files related to the schedule. In some embodiments, when writing file information to the schedule-related file list, in addition to the aforementioned file name and file link, a preview image, summary, or the first few paragraphs of the file can also be automatically extracted and displayed directly in the file list. This allows users to quickly understand the file content without opening the file, improving work efficiency.

[0108] Figure 4A This is a schematic diagram of the implementation flow of a schedule file processing method provided by an embodiment of the present application. The method can be executed by a processor of a computer device. Figure 1 The method may further include step S301, combining Figure 4A The steps shown are explained.

[0109] Step S301: Display the file name of at least one second file on the management interface; the file name is used to open the second file.

[0110] The at least one second file belongs to the at least one first file. That is, the second file is one or more files selected from the at least one first file and is displayed to the user as a file name on the management interface so that the user can perform further operations based on the file name, such as opening the file.

[0111] Among them, one or more second files are displayed on the management interface, which allows users to open the corresponding files directly based on the file name of the second file displayed on the management interface without entering the folder interface / file list, thereby further simplifying the path for users to find schedule-related files and improving the user experience.

[0112] For example, see Figure 4B, which shows a schematic diagram of an interface including a file name management interface. Figure 4B As shown, the management interface 410 may display the file name of at least one second file related to the schedule, and the at least one second file is displayed in area 411, such as "Video 1", "Video 2" and "File 1".

[0113] In some embodiments, the above-mentioned display of the file name of at least one second file on the management interface can be achieved through steps S3011 and S3012.

[0114] Step S3011: When the number of the at least one first file is less than or equal to a preset number threshold, the file names of all the first files are displayed on the management interface.

[0115] Step S3012: When the number of files of the at least one first file is greater than the preset number threshold, select the preset number threshold of first files from the at least one first file as the second files according to the file attributes of the at least one first file; and display the file names of the preset number threshold of second files on the management interface.

[0116] In the above embodiment, information about at least one first file can be obtained first, and it can be determined whether the number of the first files is less than or equal to a preset number threshold. If the number of files is less than or equal to the preset number threshold, the names of these files are directly displayed on the management interface. If the number of files is greater than the preset number threshold, the preset number threshold of files can be selected from all the first files based on file attributes (such as modification time, file type, file size, etc.) as second files, and the names of these second files are displayed on the management interface.

[0117] For example, assume that the preset number threshold is 4, and the current schedule has 20 first files related to the project. Among these files, 15 are document files and 5 are picture files; in step S301, it is determined that the total number of files (20) is greater than the preset number threshold (10). Then, in step S3012, the files can be sorted according to attributes such as file type or modification time, and the first 4 files can be selected as the second files for display. For example, if the files are sorted from recent to far according to modification time, the names of the 4 most recently modified files (which may be a combination of documents and pictures) will be displayed on the management interface. Assuming that the preset number threshold is 10, and the current schedule has 10 first files related to the project, the file names of all the first files will be directly displayed on the management interface.

[0118] In the above embodiment, considering the limited area of ​​the management interface, when the number of first files is less than or equal to a preset threshold, the file names of all first files are displayed, allowing the user to view the files they want without any operation. When the number of first files is greater than the preset threshold, a preset threshold number of first files are selected from the at least one first file based on the file attributes of the at least one first file as the second files, and the file names of the preset threshold number of second files are displayed on the management interface. That is, in some embodiments, when the number of first files is relatively large, the second files displayed on the management interface are selected according to the policy.

[0119] Among them, the file attributes can be any information that describes the first file, such as file name, file creation time, file update time, the degree of association between the file and the schedule, and other file-related attributes. Exemplarily, the file attributes may include the file creation time and the alphabetical order of the file name. Exemplarily, the file attributes can be sorted according to the account that created the file. Assuming that the sorting is based on the account that created the file, the files created with the same name will be displayed together, making it convenient for users of various accounts associated with the schedule to find their uploaded files in a relatively centralized location. Also exemplarily, the file attributes can also be sorted based on the file upload account. In this way, files uploaded through the same account will be displayed together, making it convenient for the uploading user to view. Of course, the above are just examples of file attributes, and the specific implementation is not limited to the above examples.

[0120] In some embodiments, selecting a preset threshold number of first files from the at least one first file as the second file according to the file attribute of the at least one first file includes at least one of the following:

[0121] selecting a preset threshold number of the first files from the at least one first file as the second files according to a time at which the at least one first file is associated with the schedule;

[0122] selecting, according to an update time of at least one first file, a preset threshold number of first files from the at least one first file as the second files;

[0123] According to the degree of association between at least one first file and the schedule, a preset threshold number of first files are selected from the at least one first file as the second files.

[0124] In some embodiments, the file attributes include the time at which the first file is associated with the schedule. The time at which the first file is associated with the schedule may include, but is not limited to, at least one of the following: the time at which the file is imported; the time at which the file is associated with the schedule. For example, all first files may be sorted by the time at which they are associated with the schedule (e.g., earliest to latest, or vice versa); and a predetermined threshold number of first files from the sorted list may be selected as the second files.

[0125] In some embodiments, the file attributes include the update time of the first file, which is the time when the file was last modified. Exemplarily, the first files can be sorted by update time (e.g., most recently updated to earliest updated, or vice versa), and a preset threshold number of first files are selected from the sorted list as the second files.

[0126] In some embodiments, the file attributes include a degree of association between the first file and the schedule. This degree of association characterizes the strength of the correlation between the file and the schedule. This degree of association can be determined based on a variety of factors, such as content, title, and tags. For example, the degree of association between each first file and the schedule can be evaluated first, and then sorted accordingly. The evaluation of the degree of association may be based on an analysis of information such as file content, title, and tags, and may also involve the user's historical behavior and preferences. After the sorting is completed, a preset threshold number of first files are selected from the list as second files.

[0127] In the above embodiment, by selecting and displaying files according to specific attributes, users can find information related to their current needs or concerns more quickly.

[0128] Figure 5A This is a fourth flow chart of a method for processing a schedule file provided in an embodiment of the present application. This method can be executed by a processor of a computer device. Figure 1 The management interface also includes a file import area; the method further includes steps S401 to S402, combining Figure 5A The steps shown are explained.

[0129] Step S401: In response to a trigger operation on the file import area, an imported file to be associated is obtained.

[0130] The file import area is a specific area on the management interface where users can upload or select files in order to associate them with schedules. Triggering operations on the file import area include, but are not limited to, clicking on the file import area, dragging files to the file import area, etc. Triggering operations on the file import area will trigger the system to treat the operated file as a file to be associated that needs to be imported. Accordingly, the file to be associated is a file imported through the file import area that has not yet been associated with any schedule.

[0131] For example, see Figure 5B , which shows a schematic diagram of an interface including a management interface of a file import area. Figure 5B As shown, in addition to displaying the summary information of the at least one first file, management interface 520 also displays a file import area 521. In some implementation scenarios, the user can click on file import area 521, which then displays a file selection interface in the file management system, allowing the user to select the file to be associated and imported. In other implementation scenarios, the user can also directly drag and drop the file to be associated and imported into file import area 521. The number of files to be associated can be one or more.

[0132] In some embodiments, during the importing of the file to be associated, corresponding permission information may be set for the file to be associated, and the permission information is used to determine an account that has management permission for the file to be associated. The method further includes: receiving a permission setting operation for the file to be associated from a management account; the permission setting operation is used to determine whether an account associated with the schedule has operation permission for the first file; and in response to the permission setting operation, determining the permission information for the file to be associated.

[0133] The management account is an account that has high-level management permissions for a specific file or system, such as the file owner (the account that imports the file to be associated), a system administrator, etc. During the process of the management account importing the file to be associated, a permission configuration area may also be displayed in the file import area, through which the management account's permission setting operations for the file to be associated are obtained.

[0134] In some embodiments, the permission setting operation for the file to be associated can be used to set permissions such as read, write, and delete. The permission setting operation can include a first permission setting operation and a second permission setting operation, wherein the first permission setting operation is used to set the account associated with the schedule to have operation permissions for the first file (including all permissions such as read, write, and delete); and the second permission setting operation is used to set the account associated with the schedule to not have operation permissions for the first file (including all permissions such as read, write, and delete).

[0135] In other embodiments, the above-mentioned permission setting operation may further include a third permission setting operation, which may be used to set each seed operation permission (each permission such as read, write, delete, etc.). For example, the third permission operation may set the account associated with the schedule to have read permission and write permission for the first file, but not have delete permission for the first file; the third permission operation may also set the account associated with the schedule to have read permission for the first file, but not have delete permission and write permission for the first file.

[0136] In some further embodiments, the above permission setting operation may also be used to determine an account that has the operation permission.

[0137] In the above embodiment, after receiving the permission setting operation of the management account for the file to be associated, it is possible to determine which accounts are authorized and which management operations they are authorized to perform on the file to be associated, thus obtaining permission information for the file to be associated. The permission information for the file to be associated includes a list of authorized accounts, permission types, etc. Based on this permission information, access control can be performed on the accounts associated with the schedule to ensure that only authorized accounts can perform corresponding operations on the file.

[0138] For example, after importing a file to be associated called "Project Report," the administrator sets permissions through the platform's interface, specifying that only the "Project Manager" and "Finance Director" have read and write access to the file, while "Ordinary Members" can only read the file. After completing the permissions setting, all access to the "Project Report" can be controlled based on the permissions.

[0139] In the above embodiment, by setting permission information for files, unauthorized access and operations are restricted, thereby enhancing the security of files and data.

[0140] In some embodiments, the method further includes: receiving a management operation of the current account on the first file; responding to the management operation if the current account has the operating authority for the first file; sending a permission allocation request to the management account of the first file if the current account does not have the operating authority for the first file; the permission allocation request is used to request obtaining the operating authority for the first file.

[0141] The current account is an account that is attempting to perform a management operation on the first file. The management operation is a series of control or modification actions, such as editing, deleting, moving, etc., that the current account requests to perform on the first file.

[0142] In an embodiment of the present application, it is necessary to first verify whether the current account has the authority to perform specific management operations on the first file. If the current account has the required authority, it is allowed to perform the management operation; if the authority is insufficient, the authority allocation request process is triggered. The authority allocation process includes: the current account requests authority from the management account through a authority allocation request, and the management account decides whether to grant authority based on the needs.

[0143] Taking the editing operation as an example of a management operation, an editing request for the first file from the current account is received; the permission information of the current account is checked to determine whether it has the permission to perform the editing operation on the first file; if the current account has the permission to perform the editing operation, the editing operation is allowed to be performed; if the current account does not have the permission to perform the editing operation, a permission allocation request is generated and sent to the management account of the first file; the management account receives the permission allocation request and evaluates the rationality of the request to decide whether to grant the current account the permission to perform the editing operation on the first file; if the current account is granted the permission to perform the editing operation on the first file, after updating the permission information (the current account obtains the required permission), the current account is allowed to perform the editing operation on the first file.

[0144] For example, suppose User A (the current account) attempts to edit a project plan file imported by User B (the account managing the first file). First, User A's permissions are checked and it is discovered that they do not have permission to edit the file. Therefore, a permission assignment request is generated and sent to User B. After evaluating the request, User B determines that User A needs to edit the file to advance the project, and grants editing permission. After updating the permissions information, User A is allowed to edit the project plan file.

[0145] In the above embodiment, through the permission verification and request process, only accounts with appropriate permissions can perform sensitive operations on files, preventing unauthorized access and modification. At the same time, it allows the current account to obtain the required permissions by requesting when the current permissions are insufficient, thereby improving the flexibility and adaptability of the system.

[0146] Step S402: Establish an association relationship between the file to be associated and the schedule.

[0147] The above association relationship is a connection or mapping relationship established between the file and the schedule, so that the user can quickly access the relevant files through the schedule. It can be understood that after the association relationship between the file to be associated and the schedule is established, the file to be associated is the first file in the above embodiment.

[0148] In some embodiments, after obtaining the file to be associated, the file to be associated can be associated with the schedule by modifying the internal data structure or updating the database record. Generally speaking, the association relationship can be expressed as a mapping between a file identifier and a schedule identifier.

[0149] Illustratively, based on the above example, after establishing the association relationship between the file to be associated and the schedule, the user can view the associated document 521 on the management page 520 of the “Annual Summary Meeting”.

[0150] In the above embodiment, by providing an intuitive file import area and trigger operations, the process of uploading files and preparing associations is simplified. In addition, by establishing an association between files and schedules, effective integration and quick access to information are achieved. Furthermore, users can directly find the required file information in schedule management without having to manually search or organize files.

[0151] Figure 6A This is a flowchart diagram of a method for processing a schedule file provided by an embodiment of the present application. The method can be executed by a processor of a computer device. Figure 1 , the management interface also includes a file collection control; the method further includes steps S501 to S502, combining Figure 6A The steps shown are explained.

[0152] Step S501: In response to a triggering operation on the file collection control, a file collection setting interface is displayed.

[0153] The file import area in the above embodiment of the file collection control is two independent interface elements. The triggering operation for the file collection control can be an operation performed by the user on the file collection control through clicking, touching or other interactive methods, and the operation can be responded to and the file collection setting interface can be displayed.

[0154] In some embodiments, when a user needs to collect files, by triggering a file collection control (such as clicking a "Collect Files" button), the system recognizes this operation and responds, loading and displaying a file collection setting interface, where the file collection setting interface includes all configurable collection parameter items.

[0155] Step S502: Receive collection parameters through the file collection setting interface, and use the collection parameters to collect the first file.

[0156] In some embodiments, collection parameters input by the user in the file collection setting interface can be received, file collection instructions or logic can be constructed based on these collection parameters, and then the file collection operation can be executed to obtain the first file that meets the requirements from a local or online server.

[0157] For example, see Figure 6B The interface diagram of the file collection setting interface is shown as Figure 6B As shown, the file collection setting interface 630 may include a parameter setting area 631, through which the collection parameters input by the user may be received. Thereafter, in response to a trigger event for the "Confirm" control, the first file may be collected based on the set collection parameters.

[0158] In some embodiments, the collection parameters include at least one of the following: collection object, collection time, collection method, and collection reminder.

[0159] Among them, the collection object is the account or session that needs to be paid attention to during the file collection process; the collection time is the time range or specific time point for file collection; the collection method includes storing the collected first file in the first folder, and writing the file information of the collected first file into the file list; the collection reminder is used to set a reminder mechanism for the collection object, including the reminder method, reminder time, etc. For example, through email, text message or system notification, etc., remind relevant personnel to submit or pay attention to the file collection progress in time.

[0160] For example, see Figure 6B The interface diagram of the file collection setting interface is shown. In the parameter setting area 631, you can enter the account or session to be collected in the "Submitter" field; enter the time range for file collection in the "Submission Time" field; select to collect to the first folder or write to the file list in the "Collection Method" field; and set the reminder time for the collection process in the "Reminder Time" field.

[0161] In some embodiments, the method further includes: in response to setting a collection object, sending a collection link to the collection object, so that the collection object can upload files through the collection link. The collection link can be sent in a manner including, but not limited to, instant messaging, email, etc. The collection link can be a network address (which can be a URL, i.e., a uniform resource locator) for receiving and storing files uploaded by the collection object.

[0162] The recipient of the collection can receive the collection link through instant messaging, email, or other channels. The collection link can point to a file upload page or include an upload form embedded in another page. On the upload page or form, the recipient can click "Select File" or a similar button to select the file to be uploaded from the device. After the file is selected, the recipient can click "Upload" or a similar button to initiate the file transfer process. After the file upload is complete, a confirmation message can be displayed to inform the recipient that the file has been successfully uploaded.

[0163] In some embodiments, the method further includes: displaying statistical information of file collection through the file collection setting interface.

[0164] The statistical information of file collection may include but is not limited to at least one of the following: the number of collected files; the number of files to be collected; the users who have submitted files; the users who have not submitted files; and the remaining submission time.

[0165] In some embodiments, the number of collected files is the number of files that have been successfully collected so far; the number of files to be collected is the number of files that need to be collected according to preset collection rules or goals; the submitted users is a list or number of users who have successfully submitted files; the unsubmitted users is a list or number of users who have not submitted files or have not submitted files as required; the remaining submission time is for time-limited file collection tasks, indicating how much time the user has left to complete the file submission.

[0166] For example, see Figure 6B The interface diagram of the file collection setting interface is shown. The file collection setting interface 630 also includes a statistical information display area 633. In the statistical information display area 633, it can be displayed "Number of collected files: 30 / 50 (30 logs have been collected, a total of 50 need to be collected); Number of files to be collected: 20 (there are still 20 logs not collected); Submitted users: list the user IDs of the submitted logs; Unsubmitted users: list the user IDs of the logs that have not been submitted; Remaining submission time: 2 days until the log deadline."

[0167] In the above embodiment, by displaying detailed file collection statistics, the user can clearly understand the current file collection progress and status.

[0168] Figure 7 This is a flowchart of a method for processing a schedule file provided by an embodiment of the present application. The method can be executed by a processor of a computer device. Figure 1 The method further comprises step S601, combining Figure 7 The steps shown are explained.

[0169] Step S601: In response to a triggering operation of a reading summary control for the first file, the information of the first file is processed and summarized by a large model and then displayed on the interface associated with the schedule.

[0170] Wherein, the above-mentioned reading summary control may be located in the above-mentioned management interface. In some embodiments, a reading summary control may be set for each of the first files, and in response to the triggering operation of the reading summary control for the first file, the information of the first file may be displayed on the interface associated with the schedule. In other embodiments, a reading summary control may be set for all first files, and in response to the triggering operation for the reading summary control, the information of all first files may be displayed on the interface associated with the schedule. In some further embodiments, a reading summary control may be set for all first files, and before the triggering operation for the reading summary control, the method may further include: receiving a selection operation for some of the first files in the at least one first file; and in response to the triggering operation for the reading summary control, displaying the information of some of the first files on the interface associated with the schedule.

[0171] In some embodiments, the information of the first file is generated by processing and aggregating the first files (which may be one first file, all first files, or some first files) using a large model. The large model is a machine learning model with powerful processing capabilities and a wide range of applications. It can process and analyze large amounts of data, including text, images, etc., and generate valuable information output, including but not limited to summaries, classifications, and translations.

[0172] In some embodiments, the aforementioned large model may be, but is not limited to, a Natural Language Processing (NLP) large model, a Computer Vision (CV) large model, and a multimodal large model. For example, the NLP large model may be a Generative Pre-trained Transformer (GPT) model or a Bidirectional Encoder Representations from Transformers (BERT) model; the CV large model may be a Vision Transformer (ViT) model; and the multimodal large model may be a Contrastive Language-Image Pre-Training (CLIP) model.

[0173] In some embodiments, the information of the first file may be pre-generated, i.e., generated before receiving a trigger operation for the reading summary control for the first file. After receiving the trigger operation for the reading summary control, the previously generated information of the first file is displayed. In other embodiments, after receiving a trigger operation for the reading summary control for the first file, the first file may be processed by the large model to obtain the information of the first file and then displayed.

[0174] In some embodiments, the information of the above-mentioned first file is displayed on the interface associated with the schedule, wherein the interface associated with the schedule can be the management interface of the above-mentioned schedule, or it can be the preview interface of the calendar application in the above-mentioned embodiment. When displayed in the preview interface, the area associated with the schedule can be displayed.

[0175] Through the above embodiment, users can quickly access the core content of schedule-related files without having to spend a lot of time reading all the files related to the schedule. This helps users make adequate preparations before starting a schedule and can also quickly understand the progress of the schedule after the schedule ends. This can improve the user experience of the schedule management software and enable users to more conveniently manage and use schedule-related information.

[0176] Based on the foregoing embodiments, an embodiment of the present application provides a schedule file processing device, which includes the various units included and the various modules included in each unit, and can be implemented by a processor in a computer device; of course, it can also be implemented by a specific logic circuit; in the implementation process, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA), etc.

[0177] Figure 8 A schematic diagram of the structure of a schedule file processing device provided in an embodiment of the present application is shown in FIG. Figure 8 As shown, the schedule file processing device 800 includes: a first display module 810 and a second display module 820, wherein:

[0178] The first display module 810 is used to display the schedule management interface; the management interface includes a file display control;

[0179] The second display module 820 is configured to display summary information of at least one first file in response to a triggering operation on the file display control; the first file is a file related to the schedule.

[0180] In some embodiments, the summary information includes at least one of the following: a file icon of the at least one first file, and file information of the at least one first file; the second display module 820 is also used for at least one of the following: displaying the folder interface of the first folder; displaying the file icon of the at least one first file in the folder interface of the first folder; displaying a file list; the file list includes the file information of the at least one first file; the file information is used to open the first file.

[0181] In some embodiments, the schedule file processing device 800 includes a collection module. The collection module is configured to collect the at least one first file, and the collection module includes at least one of the following: storing the at least one first file in the first folder; the first folder being associated with the schedule; writing file information of the at least one first file into the file list; and the file list being associated with the schedule.

[0182] In some embodiments, the schedule is associated with at least two accounts; the second display module 820 is further used to: in response to a display event of the session interface of the target session, display the at least one first file in the session interface; the target session includes the at least two accounts; in response to a closing event of the session interface of the target session, adjust the first file based on the collected session records for the first file.

[0183] In some embodiments, the second display module 820 is further used to: in response to an open event for a target first file in the at least one first file, display the file content of the target first file through the session interface; accept an editing operation for the target first file, and update the target first file based on the editing operation; in response to a close event for the target first file, save the updated target first file.

[0184] In some embodiments, the second display module 820 is further used to: display the file name of at least one second file on the management interface; the file name is used to open the second file; and the at least one second file belongs to the at least one first file.

[0185] In some embodiments, the second display module 820 is further used to: when the number of files of the at least one first file is less than or equal to a preset number threshold, display the file names of all the first files on the management interface; when the number of files of the at least one first file is greater than the preset number threshold, select a preset number threshold of the first files from the at least one first file as the second files according to the file attributes of the at least one first file; and display the file names of the preset number threshold of the second files on the management interface.

[0186] In some embodiments, the management interface further includes a file import area, and the schedule file processing device 800 includes an association module. The association module is configured to, in response to a trigger operation on the file import area, obtain an imported file to be associated, and establish an association relationship between the file to be associated and the schedule.

[0187] In some embodiments, the association module is further used to: receive a permission setting operation of a management account for the file to be associated; the permission setting operation is used to determine whether the account associated with the schedule has operation permissions for the first file; and determine permission information of the file to be associated in response to the permission setting operation.

[0188] In some embodiments, the schedule file processing device 800 includes a management module. The management module is configured to: receive a management operation on the first file from a current account; respond to the management operation if the current account has permission to operate the first file; and send a permission allocation request to the management account of the first file if the current account does not have permission to operate the first file; the permission allocation request is used to request permission to operate the first file.

[0189] In some embodiments, the management interface also includes a file collection control; the second display module 820 is also used to: display a file collection setting interface in response to a trigger operation on the file collection control; receive collection parameters through the file collection setting interface, and use the collection parameters to collect the first file.

[0190] In some embodiments, the second display module 820 is further configured to: in response to a triggering operation of a reading summary control for the first file, aggregate the information of the first file through a large model and display the aggregated information on the schedule-associated interface.

[0191] In some embodiments, the schedule points to an online activity; during the online activity, the second display module 820 is also used for at least one of the following: displaying or playing the first file; distributing the first file to participating accounts participating in the activity; and collecting files after the participating accounts update the first file.

[0192] The description of the above device embodiment is similar to the description of the above method embodiment and has similar beneficial effects as the method embodiment. In some embodiments, the functions or modules included in the device provided in the embodiments of the present application can be used to perform the methods described in the above method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0193] It should be noted that, in the embodiment of the present application, if the above-mentioned schedule file processing method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiment of the present application is not limited to any specific hardware, software or firmware, or any combination of hardware, software and firmware.

[0194] An embodiment of the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, some or all of the steps in the above method are implemented.

[0195] The embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements some or all of the steps in the above method. The computer-readable storage medium may be transient or non-transient.

[0196] An embodiment of the present application provides a computer program, including computer-readable code. When the computer-readable code is run in a computer device, a processor in the computer device executes some or all of the steps for implementing the above method.

[0197] An embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and when the computer program is read and executed by a computer, implements some or all of the steps in the above method. The computer program product can be implemented specifically by hardware, software, or a combination thereof. In some embodiments, the computer program product is embodied as a computer storage medium. In other embodiments, the computer program product is embodied as a software product, such as a software development kit (SDK), etc.

[0198] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between the various embodiments, and their similarities or similarities can be referenced to each other. The descriptions of the above device, storage medium, computer program, and computer program product embodiments are similar to the descriptions of the above method embodiments and have similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the description of the method embodiments of this application for understanding.

[0199] Figure 9 A hardware entity diagram of a computer device provided in an embodiment of the present application is shown as follows: Figure 9 As shown, the hardware entity of the computer device 900 includes: a processor 901 and a memory 902, wherein the memory 902 stores a computer program that can be run on the processor 901, and the processor 901 implements the steps of the method of any of the above embodiments when executing the program.

[0200] The memory 902 stores computer programs that can be run on the processor. The memory 902 is configured to store instructions and applications executable by the processor 901. It can also cache data to be processed or processed by the processor 901 and various modules in the computer device 900 (for example, image data, audio data, voice communication data, and video communication data). This can be implemented through flash memory (FLASH) or random access memory (RAM).

[0201] When the processor 901 executes the program, the steps of any of the above-mentioned schedule file processing methods are implemented. The processor 901 generally controls the overall operation of the computer device 900.

[0202] An embodiment of the present application provides a computer storage medium storing one or more programs. The one or more programs can be executed by one or more processors to implement the steps of the schedule file processing method of any of the above embodiments.

[0203] It should be noted that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

[0204] The processor may be at least one of an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a central processing unit (CPU), a controller, a microcontroller, and a microprocessor. It is understood that the electronic device that implements the functions of the processor may also be other electronic devices, which are not specifically limited in the embodiments of the present application.

[0205] The above-mentioned computer storage medium / memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); it can also be various terminals including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0206] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned steps / processes does not mean the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments.

[0207] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0208] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0209] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed across multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0210] In addition, the functional units in the embodiments of the present application can all be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the above-mentioned integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units. It can be understood by ordinary technicians in this field that all or part of the steps of the above-mentioned method embodiments can be completed by hardware related to program instructions, and the above-mentioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiments; and the above-mentioned storage medium includes: various media that can store program codes, such as mobile storage devices, read-only memories (ROMs), magnetic disks or optical disks.

[0211] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0212] The above is only an implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.

Claims

1. A schedule file processing method, characterized in that: The method comprises: A management interface for displaying schedules; the management interface includes a file display control; In response to a trigger operation on the file display control, summary information of at least one first file is displayed; the first file is a file related to the schedule.

2. The method according to claim 1, characterized in that The summary information includes at least one of the following: a file icon of the at least one first file, and file information of the at least one first file; the summary information of the first file includes at least one of the following: Displaying a folder interface of a first folder; a file icon of the at least one first file is displayed in the folder interface of the first folder; A file list is displayed; the file list includes file information of the at least one first file; and the file information is used to open the first file.

3. The method according to claim 2, characterized in that Collecting the at least one first file includes at least one of the following: storing the at least one first file in the first folder; the first folder is related to the schedule; Writing file information of the at least one first file into the file list; The file list is associated with the schedule.

4. The method according to any one of claims 1 to 3, characterized in that: The schedule is associated with at least two accounts; the method further includes: In response to a display event of a session interface of a target session, displaying the at least one first file in the session interface; the target session includes the at least two accounts; In response to a closing event of a session interface of a target session, adjusting the first file based on the collected session record for the first file.

5. The method according to claim 4, characterized in that The method further comprises: In response to an opening event for a target first file in the at least one first file, displaying file content of the target first file through the session interface; Accepting an editing operation on the target first file, and updating the target first file based on the editing operation; In response to a closing event for the target first file, the updated target first file is saved.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The file name of at least one second file is displayed on the management interface; the file name is used to open the second file; and the at least one second file belongs to the at least one first file.

7. The method according to claim 6, characterized in that The displaying the file name of at least one second file on the management interface includes: When the number of the at least one first file is less than or equal to a preset number threshold, displaying the file names of all the first files on the management interface; When the number of files of the at least one first file is greater than the preset number threshold, a preset number threshold of first files are selected from the at least one first file as the second files according to the file attributes of the at least one first file; and the file names of the preset number threshold of second files are displayed on the management interface.

8. The method according to any one of claims 1 to 7, characterized in that: The management interface also includes a file import area; the method also includes: In response to a trigger operation on the file import area, obtaining an imported file to be associated; An association relationship between the file to be associated and the schedule is established.

9. The method according to claim 8, characterized in that The method further comprises: Receive a permission setting operation of a management account for the file to be associated; the permission setting operation is used to determine whether the account associated with the schedule has the operation permission for the first file; In response to the permission setting operation, permission information of the file to be associated is determined.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: Receiving a management operation of the current account on the first file; If the current account has the operation authority for the first file, responding to the management operation; In the case that the current account does not have the operation authority for the first file, a permission allocation request is sent to the management account of the first file; the permission allocation request is used to request to obtain the operation authority for the first file.

11. The method according to any one of claims 1 to 10, characterized in that: The management interface also includes a file collection control; the method also includes: In response to a trigger operation on the file collection control, displaying a file collection setting interface; The collection parameters are received through the file collection setting interface, and the first file is collected using the collection parameters.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: In response to a triggering operation of a reading summary control for the first file, the information of the first file is summarized and processed by a large model and then displayed on the interface associated with the schedule.

13. The method according to any one of claims 1 to 12, characterized in that: The schedule refers to an online activity; during the process of performing the online activity, the method further includes at least one of the following: Displaying or playing the first file; Distributing the first file to participating accounts participating in the activity; Collect files after the participating accounts update the first file.

14. A schedule file processing device, characterized in that: The device comprises: A first display module, used to display a schedule management interface; the management interface includes a file display control; The second display module is used to display summary information of at least one first file in response to a trigger operation on the file display control; the first file is a file related to the schedule.

15. A computer device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, wherein: When the processor executes the program, the steps in the method according to any one of claims 1 to 13 are implemented.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps in the method according to any one of claims 1 to 13 are implemented.

17. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps in the method according to any one of claims 1 to 13 are implemented.

Images