File management method and device, electronic equipment, storage medium and program product

Abstract

The invention provides a file management method and device, electronic equipment, a storage medium and a program product. The file management method comprises the following steps: in response to a user operation for associating a target file with a target object, associating the target file with the target object, so that the target file becomes an associated file of the target object; determining whether the target object meets a file archiving condition or not; and automatically moving all associated files of the target object to an archiving catalog under the condition of determining that the target object meets the file archiving condition. According to the file archiving method and device, the files can be archived and managed automatically through the incidence relation between the files and the things, and therefore the files can be searched and operated conveniently.

Description

Technical Field

[0001] The present disclosure generally relates to the field of computer technology, and more specifically, to a file management method, device, electronic device, storage medium, and program product. Background Art

[0002] In the process of using electronic devices (for example, in daily office work), it is inevitable to generate various directories and files. They may correspond to different work tasks, some urgent or some slow, or even just temporary files. As time goes by, it may be very troublesome to find a certain file again. Summary of the invention

[0003] An exemplary embodiment of the present disclosure provides a file management method, device, electronic device, storage medium and program product, which can automatically manage files through the association relationship between files and things to facilitate the search and operation of files.

[0004] According to a first aspect of an embodiment of the present disclosure, a file management method is provided, comprising: in response to a user operation of associating a target file with a target thing, associating the target file with the target thing so that the target file becomes an associated file of the target thing; determining whether the target thing satisfies a file archiving condition; and when it is determined that the target thing satisfies the file archiving condition, automatically moving all associated files of the target thing to an archiving directory.

[0005] Optionally, it also includes: when the target object meets the completion condition, updating the state of the target object to the completion state; in response to the target object entering the completion state, automatically switching the state of the target object from the completion state to the archive state, or, in response to a user operation of switching the completion state of the target object to the archive state, switching the state of the target object to the archive state; wherein the file archiving condition of the target object includes: the state of the target object is switched to the archive state.

[0006] Optionally, it also includes: automatically cleaning files in a preset directory that are not associated with anything at preset intervals; and / or, in response to a file cleaning trigger operation, cleaning files in the preset directory that are not associated with anything; wherein the preset directory is a directory that is pre-set by the user and needs to be cleaned regularly.

[0007] Optionally, the method further includes: when it is determined that the target transaction meets the file archiving condition, automatically generating a transaction report for tracing back the entire processing process of the target transaction; and saving the transaction report in the archiving directory.

[0008] Optionally, it also includes: in response to a user operation of displaying a thing management interface, displaying the thing management interface; wherein the thing management interface is used to manage things and display key information of things; wherein the key information of things includes: identification information of the thing and a file list entry for centralized management of all associated files of the thing, the file list of the thing lists: associated files saved in the thing directory of the thing and associated files not saved in the thing directory of the thing.

[0009] Optionally, the key information of the thing also includes at least one of the following items: the level of the thing, the progress of the thing, the time remaining for the thing, and the status of the thing; wherein the level of the thing is set by the user according to the urgency of the thing; the progress of the thing includes: the progress of each item of the thing, and / or the total progress of the thing calculated based on the progress of each item of the thing; the status of the thing includes: in progress, postponed, completed, archived, and cleaned up.

[0010] Optionally, the types of user operations for associating the target file with the target thing include: creating a new target file under the thing directory of the target thing; moving the created target file to the thing directory of the target thing; copying the created target file to the thing directory of the target thing; setting the associated thing identification information in the attribute information of the target file that is not in the thing directory of the target thing to: the identification information of the target thing.

[0011] Optionally, it also includes: in response to a user operation of generating a thing report, generating a thing report for describing the processing status of things; wherein the generated thing report includes at least one of the following items: a thing report for describing the processing status of all things involved on that day; a thing report for describing the processing status of all things that have not been actually completed; a thing report for describing the processing status of all things in a specified time period; a thing report for describing the processing status of a specified thing.

[0012] Optionally, it further includes: when the time remaining of the target object meets the reminder condition, applying a special display effect to the target object in the object management interface.

[0013] Optionally, the method further includes: determining whether the target object satisfies an object cleaning condition; and automatically cleaning all associated files of the target object if it is determined that the target object satisfies the object cleaning condition.

[0014] According to a second aspect of an embodiment of the present disclosure, a file management device is provided, comprising: an association unit, configured to associate a target file with a target thing in response to a user operation of associating the target file with the target thing, so that the target file becomes an associated file of the target thing; an archiving judgment unit, configured to determine whether the target thing satisfies a file archiving condition; and an archiving unit, configured to automatically move all associated files of the target thing to an archiving directory when it is determined that the target thing satisfies the file archiving condition.

[0015] According to a third aspect of an embodiment of the present disclosure, there is provided a computer-readable storage medium storing instructions, which, when executed by a processor of an electronic device, enables the electronic device to execute the file management method as described above.

[0016] According to a fourth aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: at least one processor; and at least one memory storing computer executable instructions, wherein the computer executable instructions, when executed by the at least one processor, prompt the at least one processor to execute the file management method as described above.

[0017] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising computer executable instructions, which, when executed by at least one processor, implement the file management method as described above.

[0018] According to the file management method, device, electronic device, storage medium and program product of the exemplary embodiments of the present disclosure, files are automatically managed systematically through the association relationship between files and things, so as to facilitate the search and operation of files.

[0019] In the following description, some aspects and / or advantages of the general inventive concept will be set forth, and some other aspects and / or advantages will be known through the following description or the implementation of the general inventive concept. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] These and / or other aspects and advantages of the present application will become clearer and easier to understand from the following detailed description of the embodiments of the present application in conjunction with the accompanying drawings, in which:

[0021] Figure 1 A flowchart showing a file management method according to an exemplary embodiment of the present disclosure;

[0022] Figure 2 An example of a thing management drawer according to an exemplary embodiment of the present disclosure is shown;

[0023] Figure 3An example of a new thing entry according to an exemplary embodiment of the present disclosure is shown;

[0024] Figure 4 An example of configuring a new thing according to an exemplary embodiment of the present disclosure is shown;

[0025] Figure 5 An example of a transaction panel according to an exemplary embodiment of the present disclosure is shown;

[0026] Figure 6 An example of a time margin calculation process according to an exemplary embodiment of the present disclosure is shown;

[0027] Figure 7 An example of showing progress of matters according to an exemplary embodiment of the present disclosure is shown;

[0028] Figure 8 An example of a file list showing a thing according to an exemplary embodiment of the present disclosure;

[0029] Fig. 9 An example of a file association transaction according to an exemplary embodiment of the present disclosure is shown;

[0030] Fig.10 Another example of a file list showing a thing according to an exemplary embodiment of the present disclosure;

[0031] Fig.11 An example of a function panel according to an exemplary embodiment of the present disclosure is shown;

[0032] Fig.12 An example of generating a transaction report according to an exemplary embodiment of the present disclosure is shown;

[0033] Fig.13 An example of generating a transaction report of a specific transaction according to an exemplary embodiment of the present disclosure is shown;

[0034] Fig.14 An example of the content of a transaction report according to an exemplary embodiment of the present disclosure is shown;

[0035] Fig.15 shows an example of a directory configuration according to an exemplary embodiment of the present disclosure;

[0036] Fig.16 An example of a thing state reversal rule configuration according to an exemplary embodiment of the present disclosure is shown;

[0037] Fig.17 An example of a transaction life cycle process according to an exemplary embodiment of the present disclosure is shown;

[0038] Fig.18 An example of a working time configuration according to an exemplary embodiment of the present disclosure is shown;

[0039] Fig.19 An example of a cleansing rule configuration according to an exemplary embodiment of the present disclosure is shown;

[0040] Fig. 20 An example of adding a cleanup whitelist according to an exemplary embodiment of the present disclosure is shown;

[0041] Fig.21 An example of an automatic cleaning process according to an exemplary embodiment of the present disclosure is shown;

[0042] Fig. 22 An example of a reminder rule configuration according to an exemplary embodiment of the present disclosure is shown;

[0043] Fig.23 A structural block diagram showing a file management device according to an exemplary embodiment of the present disclosure;

[0044] Fig.24 A structural block diagram of an electronic device according to an exemplary embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0045] Reference will now be made in detail to the embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like parts throughout. The embodiments will be described below with reference to the drawings in order to explain the present disclosure.

[0046] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0047] It should be noted that the phrase "at least one of the items" in the present disclosure includes three types of parallel situations: "any one of the items", "a combination of any number of the items", and "all of the items". For example, "including at least one of A and B" includes the following three parallel situations: (1) including A; (2) including B; (3) including A and B. Another example is "executing at least one of step 1 and step 2" which means the following three parallel situations: (1) executing step 1; (2) executing step 2; (3) executing step 1 and step 2.

[0048] In the process of using electronic devices (for example, daily office work), various files are inevitably generated. These files may be scattered throughout the electronic device, such as the desktop, download directory, screenshot directory, corporate WeChat automatic save directory, etc. As time goes by, it may be very troublesome to find a certain file. Even users create a new file, edit the content, and then close it. After waiting for a few hours, the user cannot locate the file location. If they can remember the file name, they can use the search tool to confirm the file location; if they don’t remember, they will keep traversing the commonly used and uncommon paths like decryption, and search with the naked eye. In addition, when enough files are accumulated, users want to clean up some files, and they will also worry about whether they are files that will be used later. If they open the file to confirm the content, the massive amount of files is enough to make people collapse.

[0049] In view of the above problems, this application proposes a method for multi-dimensional and multi-space management of files and things by associating files with things. Figures 1 to 24 Provide detailed explanation.

[0050] Figure 1 A flowchart illustrating a file management method according to an exemplary embodiment of the present disclosure is shown.

[0051] As an example, the file management method may be executed by an electronic device with data processing capabilities, such as a personal computer, a tablet computer, a mobile communication terminal, a digital multimedia player, or other electronic device, and the embodiments of the present disclosure are not limited to this.

[0052] As an example, the file management method can be implemented by a computer program. For example, the file management method can be executed by a file management application (eg, a file manager) installed in an electronic device, or by a function program implemented in an operating system of the electronic device.

[0053] Reference Figure 1 In step 101, in response to a user operation of associating a target file with a target thing, the target file is associated with the target thing so that the target file becomes an associated file of the target thing.

[0054] The target file is not limited to the system desktop file, and any type of file in any location in the electronic device can be used as the target file. The number of the target file can be one or more.

[0055] The target things can be various types of things such as work things, life things, study things, etc.

[0056] As an exemplary embodiment, the types of user operations for associating a target file with a target thing may include, but are not limited to: creating a new target file in the thing directory of the target thing; moving an already created target file to the thing directory of the target thing; copying an already created target file to the thing directory of the target thing; setting the associated thing identification information in the attribute information of the target file that is not in the thing directory of the target thing to: the identification information of the target thing, for example, Fig. 9 shown.

[0057] In step 102, it is determined whether the target transaction satisfies the filing condition.

[0058] As an exemplary embodiment, the file management method according to the exemplary embodiment of the present disclosure may also include: when the target object meets the completion condition, updating the status of the target object to a completion state; in response to the target object entering the completion state, automatically switching the status of the target object from the completion state to the archive state, or, in response to a user operation to switch the completion state of the target object to the archive state, switching the status of the target object to the archive state.

[0059] As an exemplary embodiment, the file archiving condition of the target object may include, but is not limited to: the state of the target object is switched to the archiving state.

[0060] In step 103, when it is determined that the target object meets the file archiving condition, all the associated files of the target object are automatically moved to the archiving directory.

[0061] As an exemplary embodiment, the file management method according to the exemplary embodiment of the present disclosure may also include: when it is determined that the target transaction meets the file archiving conditions, automatically generating a transaction report for tracing the entire processing process of the target transaction, and saving the transaction report in the archive directory.

[0062] As an exemplary embodiment, the file management method according to the exemplary embodiment of the present disclosure may further include: determining whether the target object meets the object cleaning condition; if it is determined that the target object meets the object cleaning condition, automatically cleaning all associated files of the target object. As an example, the object cleaning condition of the target object may include but is not limited to: the state of the target object is switched to the cleaning state.

[0063] As an exemplary embodiment, the file management method according to the exemplary embodiment of the present disclosure may further include: automatically cleaning up files that are not associated with anything in a preset directory at preset intervals, and / or, in response to a file cleaning trigger operation (e.g., a one-key cleaning operation), cleaning up files that are not associated with anything in a preset directory. The preset directory is a directory that is preset by the user and needs to be cleaned up regularly.

[0064] As an exemplary embodiment, the file management method according to the exemplary embodiment of the present disclosure may further include: displaying the transaction management interface in response to a user operation of displaying the transaction management interface.

[0065] As an exemplary embodiment, the thing management interface is used to manage things and display key information of things. As an example, managing things may include but is not limited to: creating new things, deleting things, configuring things, and thing life cycle management.

[0066] As an exemplary embodiment, the key information of a thing may include: identification information of the thing and a file list entry for centralized management of all associated files of the thing. As an example, the identification information of the thing may be the name of the thing. As an example, the file list of the thing may list: associated files saved in the thing directory of the thing and associated files not saved in the thing directory of the thing.

[0067] As an exemplary embodiment, the key information of the thing may further include, but is not limited to, at least one of the following items: the level of the thing, the progress of the thing, the time margin of the thing, and the status of the thing.

[0068] As an exemplary embodiment, the level of a thing may be set by a user according to the urgency of the thing.

[0069] As an exemplary embodiment, the progress of the transaction may include: the progress of each item of the transaction, and / or the total progress of the transaction calculated based on the progress of each item of the transaction.

[0070] As an exemplary embodiment, the status of a transaction may include, but is not limited to: in progress, postponed, completed, archived, and cleared.

[0071] As an exemplary embodiment, the file management method according to the exemplary embodiment of the present disclosure may further include: applying a special display effect to the target thing in the thing management interface when the time margin of the target thing meets the reminder condition, that is, providing a reminder function.

[0072] The following will be combined Figures 2 to 22 The above embodiments are described in detail.

[0073] As an exemplary embodiment, the transaction management interface may be Figure 2 The things management drawer form shown.

[0074] The thing management drawer is used for displaying and controlling things, and can be used to create new things, delete things, configure things, view things, track and control the life cycle of things, and centrally control the associated files of things. As an example, the thing management drawer can be located on the right side of the screen. As an example, the thing management drawer can be called out through the taskbar icon or shortcut keys. For example, the corresponding shortcut key can be Ctrl+Alt+z. When the thing management drawer is folded, click the shortcut key to expand the thing management drawer; when the thing management drawer is expanded, click the shortcut key to collapse the thing management drawer.

[0075] Figure 3 An example of a new transaction entry is shown. This function is used to create transactions. The main function entry is the "+" button in the upper left corner of the transaction management drawer. When a transaction is created, a pop-up window will automatically pop up to allow users to set specific transaction management rules. Figure 4 An example of configuring a new thing is shown.

[0076] Thing name (required): used to identify the thing, and will be displayed in the thing management drawer and when associating files.

[0077] The transaction management switch includes an off state and an on state.

[0078] In the closed state, the following specific thing configuration items are not displayed. Correspondingly, only the associated files need to be centrally managed, and there is no need to track and control the life cycle of the things.

[0079] In the on state:

[0080] Item Level (required): used to identify the urgency and importance of items, with Level A having the highest priority.

[0081] Transaction cycle (required): The start and end time of the scheduled transaction, which can be accurate to the hour and minute. The second value (i.e., the end time) must be greater than the first value (i.e., the start time). It can be used to control the life cycle and reminders of the transaction later.

[0082] Transaction details (required): used to manage specific matters of transactions, to support the progress display of transactions in the transaction management drawer, to generate transaction reports, and to assist in determining transaction completion conditions.

[0083] Proportion: The percentage of the expected workload, used to display the progress in the drawer, can be missing. If all items are missing, they can be evenly distributed according to the percentage. If only one item is filled in, the other unfilled items can be evenly distributed according to the remaining percentage. An error will be reported when the total value of the filled percentage exceeds 100%.

[0084] Matters: used to identify specific items that need to be completed, and can be displayed in the matter management drawer.

[0085] +Add item: Click to add an item. x: Click to delete an item that has been filled in.

[0086] As an exemplary embodiment, in the transaction management interface, key information of a transaction may be displayed through a transaction panel.

[0087] Figure 5 An example of a transaction panel in the transaction management interface is shown below. Figure 5 As shown, the transaction panel is mainly used to display: stateless transactions (i.e., transactions whose transaction management switches are in the closed state) and transactions whose states are in progress, postponed, and completed.

[0088] As an exemplary embodiment, stateless objects can be displayed at the top, and up to two instances can be displayed externally. If more than two instances are displayed, they will be collapsed and can be called out by clicking the "Expand More" button.

[0089] As an exemplary embodiment, regarding the display of stateful objects, the stateful objects may be sorted according to certain rules and displayed according to the sorting results. For example, if the object panel has level, time balance, and progress from left to right, the sorting priority may be: level> time balance> progress. That is, the order from left to right on the object panel may represent the sorting priority from high to low. The sorting priority can be adjusted by dragging the controls "level", "time balance", and "progress" to adjust the left and right order. In addition, for example, clicking on the specific level of a thing in the object panel can be edited and modified, and the modification may trigger the reordering of the things.

[0090] As an example, level: 4 levels are preset, corresponding to priorities A>B>C>D; time margin: the smaller the value, the higher the priority; progress: the larger the percentage, the higher the priority.

[0091] For example, the following priority relationship: Task 1 (Level A, time margin 1 day, progress 90%) < Task 2 (Level A, time margin 4 hours, progress 10%); Task 3 (Level A, time margin 1 day, progress 10%) < Task 4 (Level A, time margin 1 day, progress 90%).

[0092] As an exemplary embodiment, the time margin in the transaction panel is automatically calculated and displayed and cannot be modified directly. When the transaction is postponed, the displayed value will be automatically recalculated and updated.

[0093] As an example, the minimum granularity of different units of the time margin may be: D (day): 1D; H (hour): 0.5H; M (minute): 1M.

[0094] As an example, when different units (dimensions) are used to display the time margin, the data is processed differently, for example: D (day) dimension: only days are retained, such as 1D 5H is truncated to 1D; H (hour) dimension: if M is greater than or equal to 30, it is converted to 0.5H, such as 10H30M is converted to 10.5H; if M is less than 30, it is truncated, such as 10H 20M is truncated to 10H; M (minute) dimension: no processing is done, such as 30M, 30M is displayed.

[0095] As an example, the time margin can be displayed according to the corresponding numerical unit and color based on the change of the time margin: when it is greater than or equal to 2 days, the color is green, the unit is D (day), for example, 3D; when it is less than 2 days and greater than or equal to 1 day, the color is yellow, the unit is D (day), for example, 1D; when it is less than 1 day and greater than or equal to 1 hour, the color is red, the unit is H (hour), for example, 1.5H; when it is less than 1 hour, the color is red, the unit is M (minute), for example, 40M.

[0096] As an example, the calculation of time margin can be combined with the following variables: effective working hours of working days; effective working time period of working days; current annual working day statistics list. Figure 6 The time margin calculation method shown is used to calculate the time margin of a transaction.

[0097] As an exemplary embodiment, Figure 7 As shown, in response to a click on the progress control of a specific thing in the thing panel, a pop-up window can be triggered to display the progress of each item of the thing. The user can modify the progress of each item. For example, the modification can be achieved by selecting an operation through a drop-down box. The minimum granularity is 5%. After clicking the confirmation button, the pop-up window disappears, and the thing progress updates the displayed value based on the user's modification of the item progress.

[0098] As an example, the total progress of a thing (i.e., the progress of the thing) can be calculated based on the current progress of each item of the thing and the proportion of the items. For example, the calculation formula can be: Thing progress = (proportion of item 1 * current progress of item 1) + (proportion of item 2 * current progress of item 2) + (item 3...). For example, in Figure 7 In the scenario where the current progress of the marked item 1 is 100% and the current progress of the item 2 is 80%, the progress of the item is calculated using the formula: 0.8*1+0.2*0.8=0.96 (i.e. 96%). After clicking the confirmation button, the pop-up box disappears, and the progress of the item "Patent Document Writing" is updated to 96%.

[0099] As an exemplary embodiment, the file list entry of a thing is established when the thing is created, and is mainly used to manage and control the associated files of the thing. Figure 8As shown, the file list entry of an object can be in the form of a folder button, which can be clicked to call up the file list of the object. This function realizes cross-space access, management, and integration of files.

[0100] As an exemplary embodiment, the thing directory of a thing is created when the thing is created, and is used to store the associated files of the thing. As an example, the file list of the thing will list: the associated files saved in the thing directory of the thing and the associated files not saved in the thing directory of the thing. Figure 8 As shown, the file list of a thing is initially empty. After a file is associated with a thing, it will be displayed in the file list.

[0101] As an example, the way to associate a file with an object may include but is not limited to: moving / copying / creating a file (or folder) in the object directory; right-clicking a file (or folder), clicking the drop-down box in the "Associate Object" item in the properties and selecting the object to be associated, for example, Fig. 9 As shown in the figure, the drop-down box can only display the things whose status is neither archived nor cleaned. After the association is successful, the file will be displayed under the file list. Because it is a file outside the thing directory (that is, the thing home directory), it will be as follows Fig.10 The files shown are displayed separately from the files in the transaction directory.

[0102] For example, in the pop-up box that displays the file list, you can perform any operation on the file, such as opening, deleting, etc. In addition, clicking the "Archive" button will move the associated files that are not in the thing directory to the thing directory in one click. For example, Fig.10 As shown in the figure, the "test.sh" file is not in the home directory of the thing. By clicking the "Archive" button provided in the interface, the file can be easily moved to the home directory of the thing. If the file is in use and cannot be archived, a prompt will be given: Please save the file and close it and try again.

[0103] Fig.11 An example of a function panel in the transaction management interface is shown. Fig.11 As shown, the function panel is mainly used to display the entrance of common functions. Common functions may include: archiving directory function, deleting directory function, generating report function, manual cleaning function, and setting function.

[0104] The archive directory function is mainly used to call out the directory of archived items and view the detailed information of archived items. The directory path is the archive directory path in the archive rule configuration.

[0105] The delete directory function is mainly used to call out the directory of deleted things and to view the detailed information of delayed deleted things. The directory path is specifically the temporary directory path in the cleanup rule configuration.

[0106] The report generation function is a function that summarizes the information of things into text reports, mainly for things with status. As an example, there are two report mechanisms. The "Generate Report" button here triggers the manual generation mechanism. Here are the two mechanisms:

[0107] Manual Generation

[0108] As an exemplary embodiment, in response to a user operation of generating a transaction report, a transaction report for describing the transaction processing status may be generated. As an example, the generated transaction report may include, but is not limited to, at least one of the following items: a transaction report for describing the processing status of all transactions involved on the day; a transaction report for describing the processing status of all transactions that have not been actually completed; a transaction report for describing the processing status of all transactions in a specified time period; a transaction report for describing the processing status of a specified transaction. As an example, the processing status may include, but is not limited to, transaction item planning, progress status, extension status, life cycle, associated files, and other aspects.

[0109] As an example, Fig.12 As shown, you can click "Generate Report" in the function panel to trigger a pop-up window. The pop-up window is used to select data collection rules (that is, transaction report generation rules). After selecting the rules, click the confirmation button to automatically generate the corresponding transaction report and save it. You can select the report save path through the pop-up window.

[0110] As an example, the transaction report generation rules can specifically include 4 rules, which are briefly explained here. Rule 1: Generate reports for all transactions in the transaction panel on the day, regardless of status; Rule 2: Generate reports only for transactions that are currently in progress or postponed, that is, only generate reports for transactions that have not been actually completed; Rule 3: Filter transactions by time and generate reports for the filtered transactions, such as filtering all transactions executed last month; Rule 4: Generate reports for specific transactions. Click the drop-down box to display all transactions. You can check at least one transaction or search and check it. Finally, generate reports for all checked transactions. For example, Fig.13 shown.

[0111] Automatically generate

[0112] This mechanism can be automatically generated under the transaction directory when the transaction is completed and reversed to the archived state, so that it can be archived together with the transaction directory for subsequent transaction status tracing.

[0113] In addition, as an example, the file format of the thing report file can be in txt text format; the file can be uniformly named: timestamp+thing report.txt. For example, the file content shows that taking thing report generation rule 4 as an example, the reports of the two things generated, test thing and patent document writing thing, are as follows: Fig.14 shown.

[0114] The manual cleanup function is one of the two mechanisms (automatic cleanup and manual cleanup) of the cleanup function in this application. Both mechanisms perform cleanup actions based on the cleanup rule configuration. The difference is that the timing nodes for triggering the cleanup actions are different.

[0115] Manual cleanup: Clicking the "Manual cleanup" button in the function panel will immediately trigger the cleanup of files in the preset directory that are not associated with anything.

[0116] Automatic cleanup: Based on the time set in the cleanup rule configuration, the system automatically triggers the cleanup of files in the preset directory that are not associated with anything.

[0117] Setting function, through the value of the configuration item of this configuration menu, the management logic of things and files (for example, various operation rule configurations) can be controlled, and different configurations can be flexibly made according to different conditions and scenarios. The configuration menu will be displayed in categories below.

[0118] Directory configuration mainly focuses on two aspects: home directory configuration and archive directory configuration.

[0119] Home Directory: All the thing directories are under this home directory. When a thing is created, a corresponding thing directory will be automatically created under this home directory for thing association management. For example, Fig.15 The path shown in is the default value, which is the most frequently used desktop directory. You can click the Change button to modify it.

[0120] Archive Directory: After the status of a transaction is updated to the completed status, it can be reversed to the archived status. At this time, all associated files are automatically moved to the transaction directory, and then the transaction directory is transferred to the archive directory to complete the archive management. For example, Fig.15 The path shown in is the default value and can be modified by clicking the Change button.

[0121] The thing status reversal rule configuration mainly controls the completion conditions and state reversal of things.

[0122] The status of things may include but is not limited to the following five states: In progress: the thing is not completed; Completed: triggered according to the completion condition; Deferred: the thing is not actually completed after the completion node is triggered, and it can be reversed to this state, and the deadline needs to be reset; Archived: after the thing is completed, it can be reversed to this state, and after entering this state, the associated files of the thing are archived; Cleaned: after the thing is completed, it can be reversed to this state, and after entering this state, the thing is cleaned up.

[0123] Transaction completion condition configuration

[0124] As an example, one or more transaction completion conditions may be configured, for example, may be configured as: the time margin is 0 and / or all specific items of the transaction are completed.

[0125] like Fig.16 As shown, the time margin is 0: This option is checked by default and cannot be cancelled. The effect is that the event is triggered when the deadline of the event is reached. All specific events of the event are completed: This option is optional. If all the specific events corresponding to the event (specific events can be set when creating an event) are completed, the event can be triggered even if the time margin is not 0.

[0126] The state reversal configuration of things can be configured as manual reversal or automatic reversal.

[0127] Manual reversal: After the status of an item changes to the completed status, you need to manually reverse it to the next status in the item management drawer. Automatic reversal: After the status of an item changes to the completed status, it automatically reverses to the next status according to the configuration. It enters the archive status by default, and can be switched to the cleanup status.

[0128] When "Complete all specific items of the item" is checked in the item completion condition configuration, if the user manually sets the progress of all items to 100%, it will be automatically executed according to the specific configuration in the item status reversal configuration. For items with a completed status, if the item status reversal configuration is configured as manual reversal, an update button will be displayed after "Complete Status" in the item panel. Click it to choose to switch to the archive status or cleanup status.

[0129] As an example, Fig.17 An example of a transaction life cycle process is shown.

[0130] Working time configuration, working time is mainly used to calculate time, used in time margin calculation and reminder functions. For example, the default value is Fig.18 As shown, the morning / afternoon items can be modified by clicking on them, the second value must be greater than the first value, and the total item is automatically calculated and displayed and cannot be modified.

[0131] Cleanup rule configuration mainly controls two types of cleanup actions: Transaction cleanup: operations that respond to a transaction's state being reversed to a cleanup state; File cleanup: operations that respond to temporary files that are not associated with a transaction when an automatic cleanup node is triggered.

[0132] Reference Fig.19 As an example, a transaction cleanup rule may include: after the transaction state is turned into a cleanup state, directly delete or delay delete.

[0133] Direct deletion (default option): directly clean up the files associated with the transaction. The files cannot be retrieved after execution.

[0134] Delayed deletion: Move the associated files of the thing to a temporary directory (the user can modify the temporary directory path), and delete them after the set time (days). The files can be retrieved at any time before they are officially deleted.

[0135] As an example, if the automatic cleaning switch in the file cleaning configuration is turned off, automatic file cleaning will not be performed; if it is turned on, automatic file cleaning will be performed.

[0136] Cleanup frequency: The time interval for automatic cleanup, in days. The default value is 3 days and can be edited.

[0137] Cleaning methods include direct deletion and delayed deletion. Direct deletion: directly clean up the files. The files cannot be retrieved after execution. Delayed deletion (default option): move the files to a temporary storage directory and delete them after the set time (days). The files can be retrieved at any time before formal deletion.

[0138] Clean up directory configuration, automatic cleaning is only effective for the preset directory, which is the desktop directory and download directory where useless files are most likely to accumulate by default. Click the Add button at the end of the last line to expand the effective directory. As an example, the desktop directory can be specially processed to ignore two types of files: application icons and files with links (shortcuts).

[0139] Clean up the whitelist directory. By default, it is empty. Click the Add button at the end to expand the ignored directory. Clean up the whitelist file suffix. By default, it is empty. Click the Add button at the end to expand the ignored file type.

[0140] The cleaning mechanism mainly cleans up files that are not associated with anything under the preset directory (i.e., the cleaning directory). If the cleaning directory is empty, the "automatic cleaning switch" will be automatically turned off. The default deletion method is to delay deletion for 3 days. The delay number can be modified by clicking the input box.

[0141] The files of associated objects will be locked, and both manual and automatic cleanup functions will ignore the associated objects. Users can use the delete function or command provided by the system to delete them, and the object association will be automatically released after deletion.

[0142] Of course, there may be some directories or files that are not related to the matter and are stored in the cleanup directory. There are many ways to prevent them from being deleted, such as storing these directories or files outside the cleanup directory and sending links to the cleanup directory. The directories with links will be filtered out during the cleanup. Alternatively, store these directories or files in the cleanup directory, but add them to the cleanup whitelist. There are two ways to add them to the whitelist: Method 1: By Fig. 20 Method 2: Right-click the file or directory to be added and add it through the right-click menu. For example, Fig. 20 Right-click a file to add the file or its suffix; right-click a directory to add the directory.

[0143] As an example, Fig.21 An example of an automatic file cleanup process is shown.

[0144] As an exemplary embodiment, effective follow-up of things can be performed based on the attributes of things during their life cycle, reflecting the plans, completion rates, etc. of things, and reminders can be given at configured time nodes.

[0145] Reminder rule configuration mainly includes configuration of reminder nodes and methods.

[0146] Regarding the configuration of reminder nodes (i.e., reminder conditions), such as Fig. 22 As shown, you can select multiple options from the following options: Option 1: Remind when the time balance of the transaction is 0. This option is the default required option and cannot be unchecked. Option 2: Add additional reminders with days (D) as the dimension. Click the input box to edit. It will take effect after checking. Option 3: Add additional reminders with hours (H) as the dimension. Click the input box to edit. It will take effect after checking.

[0147] Regarding the reminder method configuration, you can select an option from the following options: Option 1: When the reminder node is triggered (that is, the reminder conditions are met), the drawer pops up automatically and the corresponding object flashes; Option 2: When the reminder node is triggered, a pop-up reminder appears at the top of the screen, and when the user subsequently expands the drawer, the corresponding object flashes; Option 3: Do not take any active reminder action, and only flash the corresponding object when the user expands the drawer.

[0148] In addition, if Fig. 22 As mentioned in the notes, the flashing action will become ineffective after only one exposure.

[0149] According to the exemplary embodiments of the present application, the technical problems to be solved include at least one of the following items: breaking the desktop limitations in traditional solutions and performing file management at any location in the system; in the case of scattered files, all files can be summarized with one click, and files can be centrally managed to avoid loss. For example, file A in the download directory, file B in the enterprise WeChat receiving file directory, and file C on the desktop can be concentrated in a unified directory set in advance with one click; for files in different locations of the system, spatial limitations can be broken, and files in different locations can be accessed and managed simultaneously without frequent directory switching; file cleaning can quickly determine file attributes for automatic cleaning. When faced with a large number of accumulated files, there is no need for manual heavy confirmation work, and multiple automatic cleaning paths and rules can be added according to needs; in response to manual archiving in the prior art, the present application can automatically archive and manage important files, and at the same time give files new object attributes, so that when searching for corresponding files based on a certain object in the later stage, rapid positioning can be achieved.

[0150] In addition to solving the above problems, the present application can also produce some additional beneficial effects: when archiving files, reports can be automatically generated based on the attributes of things, including information such as the life cycle of things, specific matters, related files, etc., which is helpful for tracing back problems later; during the life cycle of things, effective follow-up of things can be carried out based on the attributes of things, reflecting the plans, completion rates, etc. of things, and reminders can be given at the configured time nodes; according to the configuration, things can be automatically further processed at the end of their life cycle: archived or cleaned up.

[0151] According to the exemplary embodiments of the present application, the following beneficial effects can be achieved: file management can be performed based on the desktop or anywhere in the system, thereby improving user experience and breaking limitations; the thing drawer can be called up in any scene and page, making it more convenient and quick to use and follow up on files without interrupting the work on the current page; in response to the problem of scattered files and difficult management, the thing attributes of the files can be used to summarize all related files in one click, centrally manage them and avoid loss; in response to the tedious operation of frequently switching directories to access files in different locations, the thing attributes can be used to break the spatial limitations, and the thing directory can be called out with one click using the thing panel, so that files in multiple locations can be accessed and operated at the same time; in response to various subsequent derivative problems caused by improper management after the end of the thing life cycle, the things with different attributes can be automatically Files are archived and managed, and when searching for corresponding files based on a certain thing in different time periods, rapid positioning can be achieved; reports can be generated based on the attributes of things, including the life cycle of things, specific matters and other information, which is helpful for tracing back problems later; when faced with a large number of accumulated ordinary files, there is no need for manual heavy confirmation work, and the cleanup can be completed quickly based on the attributes of things, and multiple automatic cleanup paths and rules can be added as needed; based on the management logic of things through the attributes of things, the life cycle of things can be effectively followed up, reflecting the plan, completion rate and other information of the corresponding things, and through configuration, the current situation of things can be summarized and feedback can be completed through reports; important nodes are reminded according to the configured reminder method; rich configuration and interaction methods can meet the needs of different groups of people for file management and break the unchanging pattern.

[0152] Fig.23 A structural block diagram of a file management device according to an exemplary embodiment of the present disclosure is shown.

[0153] like Fig.23 As shown, the file management device according to the exemplary embodiment of the present disclosure includes: an associating unit 201 , a filing determination unit 202 , and a filing unit 203 .

[0154] Specifically, the associating unit 201 is configured to, in response to a user operation of associating a target file with a target thing, associate the target file with the target thing so that the target file becomes an associated file of the target thing.

[0155] The filing determination unit 202 is configured to determine whether the target object satisfies a file filing condition.

[0156] The archiving unit 203 is configured to automatically move all associated files of the target object to an archiving directory when it is determined that the target object meets the file archiving condition.

[0157] As an example, according to an exemplary embodiment of the present disclosure, the file management device may also include: a state switching unit (not shown), which is configured to update the state of the target object to a completed state when the target object meets the completion condition; in response to the target object entering the completed state, automatically switch the state of the target object from the completed state to the archived state, or, in response to a user operation to switch the completion state of the target object to the archived state, switch the state of the target object to the archived state.

[0158] As an example, the file archiving condition of the target object may include: the state of the target object is switched to an archiving state.

[0159] As an example, the file management device according to the exemplary embodiment of the present disclosure may further include: a cleaning unit (not shown), the cleaning unit being configured to automatically clean up files in a preset directory that are not associated with anything at a preset time interval; and / or, in response to a file cleaning trigger operation, clean up files in the preset directory that are not associated with anything. The preset directory is a directory that is preset by the user and needs to be cleaned up regularly.

[0160] As an example, according to an exemplary embodiment of the present disclosure, the file management device may also include: a report generation unit (not shown), which is configured to: when it is determined that the target thing meets the file archiving conditions, automatically generate a thing report for tracing the entire processing process of the target thing; and save the thing report in the archiving directory.

[0161] As an example, according to an exemplary embodiment of the present disclosure, the file management device may also include: an interface display unit (not shown), the interface display unit being configured to: display the thing management interface in response to a user operation of displaying the thing management interface; wherein the thing management interface is used to manage things and display key information of things; wherein the key information of things includes: identification information of the thing and a file list entry for centralized management of all associated files of the thing, the file list of the thing lists: associated files saved in the thing directory of the thing and associated files not saved in the thing directory of the thing.

[0162] As an example, the key information of a thing may also include at least one of the following items: the level of the thing, the progress of the thing, the time remaining for the thing, and the status of the thing; wherein the level of the thing is set by the user according to the urgency of the thing; the progress of the thing includes: the progress of each item of the thing, and / or the total progress of the thing calculated based on the progress of each item of the thing; the status of the thing includes: in progress, postponed, completed, archived, and cleaned up.

[0163] As an example, the types of user operations for associating the target file with the target thing may include: creating a new target file under the thing directory of the target thing; moving the created target file to the thing directory of the target thing; copying the created target file to the thing directory of the target thing; setting the associated thing identification information in the attribute information of the target file that is not in the thing directory of the target thing to: the identification information of the target thing.

[0164] As an example, the file management device according to an exemplary embodiment of the present disclosure may also include: a report generating unit (not shown), the report generating unit being configured to: in response to a user operation of generating a transaction report, generate a transaction report for describing the processing status of transactions; wherein the generated transaction report includes at least one of the following items: a transaction report for describing the processing status of all transactions involved on that day; a transaction report for describing the processing status of all transactions that have not been actually completed; a transaction report for describing the processing status of all transactions in a specified time period; a transaction report for describing the processing status of a specified transaction.

[0165] As an example, according to an exemplary embodiment of the present disclosure, the file management device may further include: a reminder unit (not shown), which is configured to: apply a special display effect to the target object in the object management interface when the time margin of the target object meets the reminder condition.

[0166] As an example, according to an exemplary embodiment of the present disclosure, the file management device may also include: a cleaning unit (not shown), which is configured to: determine whether the target thing meets the thing cleaning condition; if it is determined that the target thing meets the thing cleaning condition, automatically clean up all associated files of the target thing.

[0167] It should be understood that the specific processing performed by the file management device according to the exemplary embodiment of the present disclosure has been referred to. Figures 1 to 22 The details have been described in detail and will not be repeated here.

[0168] It should be understood that the various units in the file management device according to the exemplary embodiments of the present disclosure can be implemented as hardware components and / or software components. Those skilled in the art can implement the various units, for example, using a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) according to the processing performed by the defined various units.

[0169] An exemplary embodiment of the present disclosure provides a computer-readable storage medium storing instructions, which, when executed by a processor of an electronic device, enables the electronic device to perform the file management method as described in the above exemplary embodiments. The computer-readable storage medium is any data storage device that can store data read out by a computer system. Examples of computer-readable storage media include: read-only memory, random access memory, read-only optical disk, magnetic tape, floppy disk, optical data storage device, and carrier wave (such as data transmission through the Internet via a wired or wireless transmission path).

[0170] Fig.24 A structural block diagram of an electronic device according to an exemplary embodiment of the present disclosure is shown.

[0171] Reference Fig.24 According to an exemplary embodiment of the present disclosure, an electronic device includes: at least one processor 301 and at least one memory 302, wherein the at least one memory 302 stores computer executable instructions 303 and an operating system 304, and when the computer executable instructions 303 are executed by the at least one processor 301, the at least one processor 301 is prompted to execute the file management method as described in the above exemplary embodiment.

[0172] Processor 301 may include a central processing unit (CPU), a graphics processing unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller or a microprocessor. As an example and not limitation, processor 301 may also include an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, a network processor, etc.

[0173] In addition, the electronic device may also include a multimedia resource display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, a mouse, a touch input device, etc.) All components of the electronic device may be connected to each other via a bus and / or a network.

[0174] According to an exemplary embodiment of the present disclosure, a computer program product may also be provided, and instructions in the computer program product may be executed by at least one processor to implement the file management method as described in the above exemplary embodiment.

[0175] Although some exemplary embodiments of the present disclosure have been shown and described, it will be appreciated by those skilled in the art that modifications may be made to these embodiments without departing from the scope and spirit of the present disclosure as defined by the claims and their equivalents.

Claims

1. A file management method, characterized in that: include: In response to a user operation of associating a target file with a target thing, associating the target file with the target thing so that the target file becomes an associated file of the target thing; Determining whether the target thing meets the filing conditions; When it is determined that the target object meets the file archiving condition, all associated files of the target object are automatically moved to the archiving directory.

2. The file management method according to claim 1, characterized in that: Also includes: When the target object meets the completion condition, the state of the target object is updated to the completion state; In response to the target object entering a completed state, automatically switching the state of the target object from a completed state to an archived state, or, in response to a user operation of switching the completed state of the target object to an archived state, switching the state of the target object to an archived state; The file archiving condition of the target object includes: the state of the target object is switched to the archiving state.

3. The file management method according to claim 1, characterized in that: Also includes: Automatically clean up files in the preset directory that are not associated with anything at preset intervals; and / or, in response to a file cleaning trigger operation, cleaning files in the preset directory that are not associated with anything; The preset directory is a directory that is preset by the user and needs to be cleaned up regularly.

4. The file management method according to claim 1, characterized in that: Also includes: When it is determined that the target transaction meets the filing conditions, a transaction report for tracing back the entire processing process of the target transaction is automatically generated; The transaction report is saved in the archive directory.

5. The file management method according to claim 1, characterized in that: Also includes: In response to a user operation of displaying a transaction management interface, displaying the transaction management interface; The transaction management interface is used to manage transactions and display key information about transactions. Among them, the key information of the thing includes: the identification information of the thing and the file list entry used to centrally manage all associated files of the thing. The file list of the thing lists: the associated files saved in the thing directory of the thing and the associated files not saved in the thing directory of the thing.

6. The file management method according to claim 5, characterized in that: The key information of the thing also includes at least one of the following items: the level of the thing, the progress of the thing, the time margin of the thing, and the state of the thing; The level of things is set by the user according to the urgency and importance of the things; The progress of the matter includes: the progress of each item of the matter, and / or the total progress of the matter calculated based on the progress of each item of the matter; The status of things include: in progress, deferred, completed, archived, and cleaned up.

7. The document management method according to claim 1, characterized in that The types of user operations for associating the target file with the target thing include: Create a new target file in the object directory of the target object; Move the created target file to the object directory of the target object; Copy the created target file to the object directory of the target object; The associated object identification information in the attribute information of the target file which is not in the object directory of the target object is set to: the identification information of the target object.

8. The document management method according to claim 1, characterized in that Also includes: In response to a user operation of generating a transaction report, generating a transaction report for describing a transaction processing situation; The generated transaction report includes at least one of the following items: A transaction report describing the processing status of all transactions involved in the day; A transaction report describing the status of all transactions that were not actually completed; A transaction report describing the processing status of all transactions in a specified time period; A transaction report that describes the processing status of a specified transaction.

9. The document management method according to claim 5, wherein Also includes: When the time remaining of the target object meets the reminder condition, a special display effect is applied to the target object in the object management interface.

10. The document management method according to claim 1, wherein Also includes: Determine whether the target transaction meets the transaction cleanup condition; When it is determined that the target object meets the object cleaning condition, all associated files of the target object are automatically cleaned up.

11. A file management device, characterized in that: include: an associating unit, configured to, in response to a user operation of associating a target file with a target thing, associate the target file with the target thing so that the target file becomes an associated file of the target thing; A filing judgment unit, configured to determine whether the target thing meets the file filing condition; The archiving unit is configured to automatically move all associated files of the target object to an archiving directory when it is determined that the target object meets the file archiving condition.

12. A computer-readable storage medium for storing instructions, characterized in that When the instructions are executed by a processor of an electronic device, the electronic device is enabled to execute the file management method according to any one of claims 1 to 10.

13. An electronic device, characterized in that: The electronic device comprises: at least one processor; at least one memory storing computer executable instructions, Wherein, when the computer executable instructions are executed by the at least one processor, the at least one processor is prompted to execute the file management method according to any one of claims 1 to 10.

14. A computer program product, characterized in that The method comprises computer executable instructions, wherein when the computer executable instructions are executed by at least one processor, the file management method according to any one of claims 1 to 10 is implemented.

Images