File management system, file management method, and file management program

Abstract

To provide a file management system that prevents a certain user from monopolizing editing a shared file and allows a plurality of users to edit the shared file appropriately, a file management method, and a file management program.SOLUTION: A file management system includes: a reception processing unit that receives an edition request from a first client for a shared file accessible via a network from each of a plurality of clients; a lock processing unit that sets the shared file in a locked state where only the first client can edit the shared file; and a setting processing unit that notifies the first client of a candidate time of the lock time which is a period in the locked state based on operation history information related to past edition operation to the shared file and sets the lock time according to operation by the first client to the candidate time.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a file management system, a file management method, and a file management program. [Background technology]

[0002] Conventionally, a system for managing shared files stored on a server has been known (see, for example, Patent Document 1). For example, Patent Document 1 describes a system that reserves a shared file that has been locked based on a request from a client so that it can be edited by another client as soon as it is unlocked, and that forcibly unlocks the shared file if it has been locked for a long period of time. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5373723 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with conventional technology, the locked state of a shared file is not released until the file has been locked for a long time, which results in the problem that the shared file is monopolized by a specific user, preventing other users from editing the shared file for a long time.

[0005] An object of the present invention is to provide a file management system, a file management method, and a file management program that prevent a specific user from monopolizing the editing of a shared file and enable multiple users to edit the shared file appropriately. [Means for solving the problem]

[0006] A file management system according to one embodiment of the present invention is a system comprising: a reception processing unit that receives an edit request from a first client for a shared file that can be accessed by each of multiple clients via a network; a lock processing unit that sets the shared file to a locked state in which only the first client can edit the shared file; and a setting processing unit that notifies the first client of a candidate lock time, which is the period of the locked state, based on operation history information regarding past edit operations on the shared file, and sets the lock time in accordance with operations on the first client for the candidate time.

[0007] Another aspect of the file management method of the present invention is a method in which one or more processors execute the following steps: a receiving step in which one or more processors receive an edit request from a first client for a shared file that can be accessed by each of multiple clients via a network; a locking step in which the shared file is set to a locked state in which only the first client can edit the shared file; and a setting step in which the first client is notified of a candidate time for a lock time, which is the period of the locked state, based on operation history information regarding past edit operations on the shared file, and the lock time is set in accordance with operations on the first client for the candidate time.

[0008] A file management program according to another aspect of the present invention is a program for causing one or more processors to execute the following steps: a reception step for receiving an edit request from a first client for a shared file that can be accessed by each of multiple clients via a network; a lock step for setting the shared file to a locked state in which only the first client can edit the shared file; and a setting step for notifying the first client of a candidate time for a lock time, which is the period of the locked state, based on operation history information regarding past edit operations on the shared file, and setting the lock time in accordance with operations on the first client for the candidate time. [Effects of the Invention]

[0009] According to the present invention, it is possible to provide a file management system, a file management method, and a file management program that prevent a specific user from monopolizing the editing of a shared file and allow multiple users to edit the shared file appropriately. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a functional block diagram showing the configuration of a file management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram showing an example of a screen displayed on a user terminal according to an embodiment of the present invention. [Figure 3] FIG. 3 is a diagram showing an example of a screen displayed on a user terminal according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram showing an example of a screen displayed on a user terminal according to an embodiment of the present invention. [Figure 5] FIG. 5 is a diagram showing an example of a screen displayed on a user terminal according to an embodiment of the present invention. [Figure 6] FIG. 6 is a diagram showing an example of a screen displayed on a user terminal according to an embodiment of the present invention. [Figure 7] FIG. 7 is a diagram showing an example of a screen displayed on a user terminal according to an embodiment of the present invention. [Figure 8] FIG. 8 is a flowchart illustrating an example of a procedure of a file management process executed in the file management system according to an embodiment of the present invention. [Figure 9] FIG. 9 is a diagram showing an example of a screen displayed on a user terminal according to another embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example of a screen displayed on a user terminal according to another embodiment of the present invention. [Figure 11] FIG. 11 is a diagram showing an example of a screen displayed on a user terminal according to another embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. Note that the following embodiment is an example of the present invention, and does not limit the technical scope of the present invention.

[0012] [File Management System 10] FIG. 1 is a block diagram showing the configuration of a file management system 10 according to an embodiment of the present invention. The file management system 10 includes a management server 1 and a user terminal 2. The management server 1 and the user terminal 2 are connected to each other via a network N1 (e.g., the Internet, a LAN, etc.). The file management system 10 may include multiple user terminals 2. The user terminal 2 is an example of a client of the present invention.

[0013] In the file management system 10, the management server 1 manages files uploaded from the user terminal 2. The management server 1 also provides users with a file management service that manages files stored in the storage unit 12. For example, the management server 1 manages multiple files stored in the storage unit 12 so that each of the multiple user terminals 2 can access the files via the network N1. In other words, the management server 1 manages the files as shared files.

[0014] Each user of the multiple user terminals 2 uploads files such as document files created on his or her own user terminal 2 to the management server 1 using a predetermined application (file management application). Each user also uses the file management application to access the management server 1 and downloads shared files to the user terminal 2 for editing, viewing, etc. Each user also uploads the downloaded shared file to the management server 1 again after finishing editing it on the user terminal 2. The management server 1 overwrites and saves the edited shared file re-uploaded from the user terminal 2.

[0015] The file management system 10 is an example of the file management system of the present invention. The file management system of the present invention may be configured with the management server 1 alone.

[0016] [Management Server 1] 1, the management server 1 includes a control unit 11, a storage unit 12, an operation display unit 13, and a communication unit 14. The management server 1 may be configured as a personal computer, a NAS (Network Attached Storage), or the like.

[0017] The communication unit 14 is a communication interface that connects the management server 1 to the network N1 via a wired or wireless connection and executes data communication with the user terminal 2 via the network N1 in accordance with a predetermined communication protocol. The network N1 is configured, for example, by the Internet or a LAN.

[0018] The operation display unit 13 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays various information, and an operation unit such as a mouse, keyboard, or touch panel that accepts operations.

[0019] The storage unit 12 is a non-volatile storage unit such as a hard disk drive (HDD), a solid state drive (SSD), or a flash memory that stores various types of information. The storage unit 12 stores data such as shared files managed by the management server 1.

[0020] For example, a user launches the file management application on the user terminal 2 and uploads a desired file to the management server 1. The control unit 11 stores the shared file in a predetermined folder based on the user's operation. For example, as shown in FIG. 2, the management server 1 stores multiple shared files in a hierarchical structure for each folder. Each user terminal 2 can access the management server 1 via the network N1 to display the file list page (an example of a shared page of the present invention) shown in FIG. 2. The shared file may be stored in a device (such as a data server) different from the management server 1.

[0021] Furthermore, the storage unit 12 stores a file management program for causing the control unit 11 to execute a file management process (see FIG. 8) described below. For example, the file management program is non-temporarily recorded on a computer-readable recording medium such as a CD or a DVD, and is read by a reading device (not shown) such as a CD drive or a DVD drive provided in the management server 1 and stored in the storage unit 12. Note that the file management program may be distributed from another server and stored in the storage unit 12.

[0022] The control unit 11 has control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various types of arithmetic processing. The ROM stores in advance control programs such as a BIOS and an OS that cause the CPU to execute various types of processing. The RAM stores various types of information and is used as a temporary storage memory (work area) for the various types of processing executed by the CPU. The control unit 11 controls the management server 1 by having the CPU execute various control programs that are pre-stored in the ROM or the storage unit 12.

[0023] Specifically, the control unit 11 includes various processing units such as a reception processing unit 111, a lock processing unit 112, a setting processing unit 113, a file processing unit 114, an unlock processing unit 115, and a display processing unit 116. The control unit 11 functions as the various processing units by executing various processes in accordance with the file management program. Some or all of the processing units included in the control unit 11 may be configured with electronic circuits. The file management program may be a program for causing multiple processors to function as the various processing units.

[0024] The reception processing unit 111 receives various types of operation information from each user terminal 2. Specifically, the reception processing unit 111 receives a selection operation of a shared file from the user terminal 2 on a shared screen (shared page) displayed on the user terminal 2 by the display processing unit 116.

[0025] For example, the display processing unit 116 displays file information about the shared files on a shared page (a file list page shown in FIG. 2) that can be accessed from each of the multiple user terminals 2 via the network N1. The file list page shown in FIG. 2 lists multiple folders and multiple files c1 to c4 stored in a folder ("folder C" in this example) selected by user A on user terminal 2A (an example of a first client of the present invention). Here, when user A selects a specific shared file ("file c4") on the file list page (see FIG. 2) displayed on user terminal 2A, the reception processing unit 111 receives the selection operation.

[0026] The reception processing unit 111 also receives an edit request for a shared file from the user terminal 2. For example, when user A selects "file c4" and selects the edit download button B1 on the file list page (see FIG. 2) displayed on the user terminal 2A, the reception processing unit 111 receives the edit request. As another example, when user A selects "file c4" on the file list page (see FIG. 2) displayed on the user terminal 2A and performs an operation (drag-and-drop operation) to move the file to a folder or the like on the user terminal 2A, the reception processing unit 111 receives the edit request. The operation of selecting the edit download button B1 (edit download operation) and the drag-and-drop operation are examples of an edit request of the present invention. The edit request of the present invention is not limited to these operations and includes well-known edit operations. For example, the edit request may be an edit operation within a website.

[0027] Furthermore, the reception processing unit 111 accepts an upload operation of a shared file from the user terminal 2. For example, when user A edits and uploads a shared file ("file c4") downloaded to user terminal 2A, the reception processing unit 111 accepts the upload operation.

[0028] The lock processing unit 112 sets the shared file to a locked state so that only a specific user terminal 2 can edit the shared file. For example, when "file c4" is downloaded to user terminal 2A, the lock processing unit 112 sets "file c4" to a locked state. In this case, user terminal 2A can edit "file c4," but other user terminals 2 cannot edit "file c4." In other words, the lock processing unit 112 grants editing authority for the shared file to a specific user terminal 2. The lock processing unit 112 may also grant editing authority for the shared file to a user's login ID. Note that when "file c4" is set to a locked state, other user terminals 2 may be able to view "file c4."

[0029] The setting processing unit 113 sets a lock time, which is the period of the locked state, based on operation history information regarding past editing operations on the shared file. For example, the setting processing unit 113 sets the lock time based on information such as the type of the shared file and the total time (or average time) required to download, edit, and re-upload the shared file in the past.

[0030] In another embodiment, the setting processing unit 113 may set the lock time to a predicted time calculated based on the operation history information. For example, some shared files have a relatively long total time the first time they are edited, and the total time tends to decrease as the number of edits increases. In such a case, the setting processing unit 113 calculates a predicted time based on the change in the total time, and sets the calculated predicted time as the lock time.

[0031] In another embodiment, the setting processing unit 113 may set the lock time according to the user. For example, the operation history information is associated with identification information (user ID) of the user who performed the editing work. In this case, the setting processing unit 113 identifies the user who made the editing request, extracts the operation history information corresponding to the identified user, and sets the lock time based on the extracted operation history information.

[0032] Here, the operation history information is stored in association with each shared file stored in the storage unit 12. The control unit 11 accumulates operation history information regarding user editing operations for each shared file. For shared files that are not associated with the operation history information, the setting processing unit 113 may set the lock time based on the file attributes (name, update date and time, type, size, etc.), number of pages, etc.

[0033] Specifically, the setting processing unit 113 calculates a candidate time for the lock time based on the operation history information, and notifies the calculated candidate time to the user terminal 2. For example, when user A selects "file c4" and selects the edit download button B1 on the file list page (see FIG. 2) displayed on the user terminal 2A, the setting processing unit 113 calculates the average time (e.g., "10 minutes") of the total time required for downloading, editing, and re-uploading "file c4" in the past as a candidate time, and displays the calculated candidate time "10 minutes" on the user terminal 2A (see FIG. 3).

[0034] User A of user terminal 2A can change the candidate time on screen F1 shown in FIG. 3. When the setting processing unit 113 acquires a change time for the candidate time from user terminal 2A, it sets the change time to the lock time. For example, if user A changes the candidate time to "15 minutes" and presses the "Start" button, the setting processing unit 113 sets the lock time to "15 minutes." Note that, for example, if user A presses the "Start" button without changing the candidate time from "10 minutes," the setting processing unit 113 sets the lock time to "10 minutes."

[0035] 3, when the "Start" button is pressed, the file processing unit 114 executes the download process of the shared file. Here, the file processing unit 114 downloads "file c4" to the user terminal 2A. While the file processing unit 114 is executing the download process, it causes the user terminal 2A to display the progress status F2 of the download process, as shown in FIG.

[0036] The release processing unit 115 releases the locked state of the shared file (sets it to an unlocked state). For example, the release processing unit 115 releases the locked state of the shared file (for example, "file c4") when the lock time (for example, "10 minutes") has elapsed since the shared file was set to the locked state.

[0037] Furthermore, for example, the release processing unit 115 releases the locked state if editing of the shared file ("file c4") is completed before the lock time ("10 minutes") is reached. Specifically, when user A finishes editing "file c4" on user terminal 2A and performs an upload operation, the file processing unit 114 executes upload processing for "file c4." Furthermore, the file processing unit 114 overwrites and saves the edited "file c4" uploaded from user terminal 2, and the release processing unit 115 releases the locked state of "file c4."

[0038] When the lock state of "file c4" is released, each user terminal 2 becomes able to edit "file c4."

[0039] Here, the control unit 11 has a configuration that allows other users to recognize that a shared file is locked when the shared file is set to a locked state.

[0040] For example, when "file c4" is set to a locked state and the reception processing unit 111 receives access to "file c4" from the user terminal 2B (an example of a second client of the present invention), the display processing unit 116 displays lock information indicating that "file c4" is set to a locked state in association with "file c4" on the file list page (see FIG. 5). Specifically, as shown in FIG. 5, the display processing unit 116 displays a warning image M1 indicating that "file c4" is set to a locked state in association with the information on "file c4."

[0041] Furthermore, when user B places the mouse image Ms over the warning image M1 (performs a mouse-over operation) on user terminal 2B (see FIG. 6), the display processing unit 116 displays, on the file list page, the identification information (user ID, name, etc.) of user A who is editing "file c4" and lock time information related to the lock time. For example, as shown in FIG. 7, the display processing unit 116 displays a lock information screen F3 including information on the remaining time of the lock time ("10 minutes remaining"). In another embodiment, the display processing unit 116 may display the elapsed time since the lock state was set.

[0042] In this way, the lock information may include identification information of the user currently editing the shared file and lock time information regarding the lock time. The lock time information may also be information regarding the remaining time of the lock time or the elapsed time since the lock state was set.

[0043] In addition, when a shared file that has been set to a locked state is selected, the display processing unit 116 may change the edit download button B1 (see FIG. 2) to warning information M2 (see FIGS. 5 to 7) so that the shared file cannot be edited and downloaded.

[0044] According to the above-described configuration of the display processing unit 116, when user B attempts to edit "file c4", he or she can understand that "file c4" is being edited by user A.

[0045] [User device 2] 1, the user terminal 2 includes a control unit 21, a storage unit 22, an operation display unit 23, and a communication unit 24. The user terminal 2 is an information processing device such as a personal computer, a smartphone, or a tablet terminal.

[0046] The communication unit 24 is a communication interface for connecting the user terminal 2 to the network N1 by wire or wirelessly, and for executing data communication with an external device such as the management server 1 via the network N1 in accordance with a predetermined communication protocol.

[0047] The operation display unit 23 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays information such as various web pages, and an operation unit such as a mouse, keyboard, or touch panel that accepts operations.

[0048] The storage unit 22 is a non-volatile storage unit such as an HDD, SSD, or flash memory that stores various types of information. For example, the storage unit 22 stores a control program such as a browser program. Specifically, the browser program is a control program that causes the control unit 21 to execute communication processing with an external device such as the management server 1 in accordance with a communication protocol such as HTTP (Hypertext Transfer Protocol). The browser program may also be a dedicated application for executing communication processing with the management server 1 in accordance with a predetermined communication protocol.

[0049] The control unit 21 has control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various types of arithmetic processing. The ROM is a non-volatile storage unit that pre-stores control programs such as a BIOS and an OS that cause the CPU to execute various types of processing. The RAM is a volatile or non-volatile storage unit that stores various types of information and is used as a temporary storage memory (work area) for the various types of processing executed by the CPU. The control unit 21 controls the user terminal 2 by having the CPU execute various control programs pre-stored in the ROM or the storage unit 22.

[0050] Specifically, the control unit 21 functions as a browser processing unit by executing various processes in accordance with the browser program stored in the storage unit 22. The control unit 11 can execute browser processing to display a web page provided from the management server 1 via the network N1 on the operation display unit 23 and input operations for the operation display unit 23 to the management server 1. In other words, the user terminal 2 can function as an operation terminal for the management server 1 by the control unit 21 executing the browser program. Note that some or all of the processing units included in the control unit 21 may be configured with electronic circuits.

[0051] In the user terminal 2, when a user performs an operation to request access to a predetermined URL corresponding to a site of the file management service provided by the management server 1, the control unit 21 acquires the web page data of the site from the management server 1 and displays the web page of the site on the operation display unit 23. If a predetermined application (file management application) corresponding to the management server 1 is installed in the user terminal 2, the web page of the site is displayed on the operation display unit 23 when the user of the user terminal 2 performs an operation to launch the file management application.

[0052] In addition, in response to a user operation, the control unit 11 uploads a file stored in the user terminal 2 to the management server 1. In addition, in response to a user operation, the control unit 11 downloads a file stored in the management server 1 to the user terminal 2. In addition, in response to a user operation, the control unit 11 edits the file downloaded from the management server 1 and then re-uploads it to the management server 1.

[0053] Furthermore, the control unit 11 displays web pages such as file list pages (see FIGS. 2 to 7) on the operation display unit 23 of the user terminal 2. Furthermore, the control unit 11 accepts user operations on each file list page.

[0054] [File Management Processing] An example of the procedure of the file management process executed in the file management system 10 will be described below with reference to FIG.

[0055] The present invention can be understood as a file management method that executes one or more steps included in the file management process. One or more steps included in the file management process described herein may be omitted as appropriate. The steps in the file management process may be executed in a different order as long as the same operational effect is achieved. While the description here uses an example in which the control unit 11 of the management server 1 executes the steps in the file management process, in other embodiments, one or more processors may execute the steps in the file management process in a distributed manner.

[0056] As shown in the above example, it is assumed here that the management server 1 stores multiple shared files that can be accessed by each of the multiple user terminals 2 via the network N1. The file management process is executed in parallel in response to access from each of the multiple user terminals 2.

[0057] First, in step S1, the control unit 11 determines whether or not a selection operation for a shared file has been received from the user terminal 2. If the control unit 11 receives the selection operation for a shared file from the user terminal 2 (S1: Yes), the control unit 11 proceeds to step S2. The control unit 11 waits until the selection operation for a shared file is received from the user terminal 2 (S1: No). Here, user A selects "file c4" on the file list page displayed on the user terminal 2A, and the control unit 11 receives the selection operation for "file c4" from the user terminal 2A (see FIG. 2).

[0058] Next, in step S2, the control unit 11 determines whether or not an edit download operation for the shared file has been accepted from the user terminal 2. If the control unit 11 accepts the edit download operation for the shared file from the user terminal 2 (S2: Yes), the control unit 11 proceeds to step S3. The control unit 11 waits until it accepts the edit download operation for the shared file from the user terminal 2 (S2: No). Here, when user A selects "file c4" on the file list page displayed on the user terminal 2A and selects the edit download button B1, the control unit 11 accepts the edit download operation for "file c4" from the user terminal 2A (see FIG. 2).

[0059] Next, in step S3, the control unit 11 calculates a candidate lock time for locking the shared file. Specifically, the control unit 11 calculates the candidate time based on operation history information regarding past editing operations on the shared file. For example, the control unit 11 collects history information on the total time required to download, edit, and re-upload "file c4" in the past, and calculates the average of that total time as the candidate time.

[0060] Next, in step S4, the control unit 11 notifies the calculated candidate time to the user terminal 2. Here, the control unit 11 notifies the user terminal 2A of the candidate time ("10 minutes"). The control unit 11 causes the user terminal 2 to display a screen F1 that accepts an edit download operation, and causes the screen F1 to display the candidate time (see FIG. 3).

[0061] Next, in step S5, the control unit 11 determines whether or not a lock start operation for locking the shared file has been received. For example, when user A presses the "Start" button on screen F1 on the file list page displayed on the user terminal 2A, the control unit 11 receives the lock start operation from the user terminal 2A (see FIG. 3). Also, for example, when user A performs an operation on screen F1 to change the lock time from the candidate time ("10 minutes"), the control unit 11 receives a lock start operation including an operation to change the lock time from the user terminal 2A (see FIG. 3). If the control unit 11 receives the lock start operation from the user terminal 2A (S5: Yes), the control unit 11 proceeds to step S6. On the other hand, if the control unit 11 does not receive the lock start operation from the user terminal 2A (S5: No), the control unit 11 proceeds to step S51.

[0062] In step S51, the control unit 11 determines whether or not a cancel operation related to the edit download has been received from the user terminal 2. For example, when the "Cancel" button on screen F1 (see FIG. 3) is pressed, the control unit 11 receives the cancel operation from the user terminal 2A. If the control unit 11 receives the cancel operation from the user terminal 2 (S51: Yes), the control unit 11 shifts the processing to step S1. On the other hand, if the control unit 11 does not receive the cancel operation from the user terminal 2 (S51: No), the control unit 11 shifts the processing to step S5.

[0063] In step S6, the control unit 11 sets a lock time for locking the shared file and registers the lock time and the user who will edit the shared file. For example, the control unit 11 sets the lock time for "file c4" to "10 minutes" and registers the lock time and the identification information of user A who will edit "file c4" in the storage unit 12.

[0064] Next, in step S7, the control unit 11 sets the shared file to a locked state. For example, the control unit 11 grants editing authority for "file c4" only to the user terminal 2A, and prohibits editing operations by other user terminals 2.

[0065] Next, in step S8, the control unit 11 executes a process of downloading the shared file. For example, the control unit 11 downloads "file c4" to the user terminal 2A.

[0066] Next, in step S9, the control unit 11 determines whether the lock time has been reached. For example, the control unit 11 determines whether the lock time of 10 minutes has elapsed since the download process of "file c4" was started in the user terminal 2A. If the lock time has not been reached (S9: No), the control unit 11 shifts the process to step S10. On the other hand, if the lock time has been reached (S9: Yes), the control unit 11 shifts the process to step S12.

[0067] In step S10, the control unit 11 determines whether or not an upload operation for a shared file has been accepted. For example, if user A edits and uploads "file c4" downloaded to user terminal 2A, the control unit 11 accepts the upload operation. If the control unit 11 accepts an upload operation from user terminal 2A (S10: Yes), the control unit 11 shifts the process to step S11. On the other hand, if the control unit 11 does not accept an upload operation from user terminal 2A (S10: No), the control unit 11 shifts the process to step S101.

[0068] In step S101, the control unit 11 determines whether or not a selection operation on a shared file that has been set to a locked state has been received from a user terminal 2 other than the user terminal 2 to which editing authority has been granted. For example, when user B selects "file c4" that has been set to a locked state on user terminal 2B (see FIG. 5), the control unit 11 determines that the selection operation has been received. If the control unit 11 receives the selection operation (S101: Yes), the control unit 11 shifts the process to step S102. On the other hand, if the control unit 11 does not receive the selection operation (S101: No), the control unit 11 shifts the process to step S9.

[0069] In step S102, the control unit 11 displays lock information indicating that the shared file has been set to a locked state in association with the shared file. For example, as shown in Fig. 5, the control unit 11 displays a warning image M1 indicating that "file c4" has been set to a locked state in association with the information of "file c4" on the user terminal 2B.

[0070] Furthermore, when user B places the mouse image Ms over the warning image M1 on user terminal 2B (performs a mouse-over operation) (see FIG. 6), the control unit 11 displays, on the file list page, the identification information (user ID, name, etc.) of user A who is editing "file c4" and information about the remaining time of the lock time ("10 minutes remaining"), as shown on the lock information screen F3 in FIG. 7. After step S102, the control unit 11 causes the process to proceed to step S9.

[0071] If the lock time is reached in step S9 (S9: Yes), or if the upload process for the shared file is executed in step S11, the control unit 11 releases the lock state of the shared file in step S12. For example, if the lock time (10 minutes) has elapsed without user A uploading "file c4" that he downloaded to user terminal 2A (S9: Yes), the control unit 11 releases the lock state of "file c4." Furthermore, if user A edits and uploads "file c4" that he downloaded to user terminal 2A (S11), the control unit 11 overwrites and saves the edited "file c4" uploaded from user terminal 2, and releases the lock state of "file c4."

[0072] When the locked state of "file c4" is released, it becomes possible to edit and download "file c4" at each user terminal 2. After step S12, the control unit 11 returns to step S1 and repeats the above-described processing.

[0073] In this manner, the control unit 11 executes the file management process for each user terminal 2.

[0074] As described above, the file management system 10 according to this embodiment accepts an edit request from user terminal 2A (first client) for a shared file that is accessible to each of multiple user terminals 2 (clients) via network N1, and sets the shared file to a locked state in which only user terminal 2A can edit the shared file. Furthermore, the file management system 10 notifies user terminal 2A of candidate lock times, which are the duration of the locked state, based on operation history information regarding past editing operations on the shared file, and sets the lock time in accordance with the operation of user terminal 2A for the candidate times. Furthermore, the file management system 10 releases the locked state of the shared file when the lock time has elapsed since the shared file was set to the locked state.

[0075] In this way, when a shared file is being edited by a specific client, a lock time is set for the shared file according to the operation history information. As a result, the shared file is locked for the time required for past operations (for example, the average operation time), and the lock state is released after the time has elapsed, so other users do not have to wait a long time to edit the shared file.

[0076] Furthermore, when another user selects a shared file that is locked, the file management system 10 displays information indicating that the shared file is locked, information about the remaining time in the locked state, identification information of the user currently editing the file, etc. This allows the other user to easily understand the locked state of the shared file.

[0077] Therefore, the file management system 10 prevents a specific user from monopolizing editing of a shared file, and allows multiple users to edit the shared file appropriately.

[0078] The present invention is not limited to the above-described embodiment, but may be embodied as follows.

[0079] In another embodiment of the present invention, when the remaining time of the lock time reaches a predetermined time, the setting processing unit 113 may notify the user terminal 2 of an inquiry as to whether or not to extend the lock time. For example, in a case where the user terminal 2A has been granted editing authority for "file c4," when the remaining time of the lock time ("10 minutes") reaches a predetermined time ("1 minute"), the setting processing unit 113 causes the user terminal 2A to display an inquiry screen F4 as to whether or not to extend the lock time, as shown in FIG. 9.

[0080] Furthermore, when the setting processing unit 113 receives a request to extend the lock time from the user terminal 2A, it extends the lock time by a predetermined time. For example, when user A selects "Extend" on the inquiry screen F4 (see FIG. 9), the setting processing unit 113 extends the locked state of "file c4" by a predetermined time (for example, "5 minutes") from the time the selection operation is received. The setting processing unit 113 may also receive an input operation of an extension time from user A on the inquiry screen F4, and extend the locked state by the received time. In this case, an upper limit time (for example, "10 minutes") that can be input by the user may be set.

[0081] Furthermore, if another user selects a shared file after the lock status of the shared file has been extended, the display processing unit 116 displays the remaining time after the extension on the lock information screen F3, as shown in Fig. 10. This allows the user to know that the lock status has been extended, the remaining time until the lock status is released, etc.

[0082] In another embodiment of the present invention, the control unit 11 may be capable of accepting an operation on the lock information screen F3 (see FIGS. 7 and 10) to request notification when the locked state of a shared file has been released. For example, as shown in FIG. 11, the display processing unit 116 displays a "Notify Unlock" button on the lock information screen F3. When the "Notify Unlock" button is selected on user terminal 2B, for example, the control unit 11 notifies user terminal 2B of a message indicating that the locked state of "file c4" has been released or that "file c4" can be edited and downloaded. This allows user B of user terminal 2B to know that "file c4" can now be edited.

[0083] In another embodiment of the present invention, the control unit 11 may be capable of accepting an operation to select either an edit download (an example of an edit request) or a view download of a shared file. For example, when the control unit 11 accepts an edit download request for "file c4" from the user terminal 2A, the control unit 11 sets "file c4" to a locked state. In this case, the control unit 11 may be capable of accepting a view download request for "file c4" from the user terminal 2B. In this case, the control unit 11 grants only the view authority for "file c4" to the user terminal 2B, but not the edit authority. This allows user B to view "file c4." Furthermore, when "file c4" is displayed on the user terminal 2B and the locked state of "file c4" is released, the control unit 11 may notify the user terminal 2B that "file c4" can now be edited. [Explanation of symbols]

[0084] 1: Management Server 2: User device 10: File Management System 111: Reception processing unit 112: Lock processing section 113: Setting processing section 114: File processing section 115: Release processing unit 116: Display processing unit

Claims

1. a reception processing unit that receives an edit request from a first client for a shared file that can be accessed by each of a plurality of clients via a network; a lock processing unit that sets the shared file to a locked state in which only the first client can edit the shared file; a setting processing unit that notifies the first client of a candidate time for a lock time, which is a period of the locked state, based on operation history information regarding past editing operations on the shared file, and sets the lock time in accordance with an operation on the first client for the candidate time; A file management system comprising:

2. a release processing unit that releases the locked state of the shared file when the lock time has elapsed since the shared file was set in the locked state; The file management system according to claim 1 .

3. when the setting processing unit acquires a change time for the candidate time from the first client, the change time is set to the lock time.

3. The file management system according to claim 1.

4. a display processing unit that displays file information about the shared file on a shared page accessible from each of the plurality of clients via the network; when the reception processing unit receives an access request to the shared file from a second client while the shared file is set to the locked state, the display processing unit displays, on the shared page, lock information indicating that the shared file is set to the locked state, in association with the shared file. The file management system according to any one of claims 1 to 3.

5. The lock information further includes identification information of a user currently editing the shared file and lock time information regarding the lock time. The file management system according to claim 4 .

6. The lock time information is information about the elapsed time since the lock state was set or the remaining time of the lock time. The file management system according to claim 5 .

7. the setting processing unit notifies the first client of an inquiry as to whether or not to extend the lock time when the remaining time of the lock time reaches a predetermined time, and extends the lock time by the predetermined time when a request to extend the lock time is received from the first client; The file management system according to any one of claims 1 to 6.

8. the release processing unit releases the locked state when the first client finishes editing the shared file before the lock time is reached. The file management system according to claim 2 .

9. one or more processors, a receiving step of receiving an edit request from a first client for a shared file that can be accessed by each of the plurality of clients via a network; lockstep, which sets the shared file in a locked state so that only the first client can edit the shared file; a setting step of notifying the first client of a candidate time for a lock time, which is a period of the locked state, based on operation history information regarding past editing operations on the shared file, and setting the lock time in accordance with an operation on the first client for the candidate time; A file management method that performs

10. a receiving step of receiving an edit request from a first client for a shared file that can be accessed by each of the plurality of clients via a network; lockstep, which sets the shared file in a locked state so that only the first client can edit the shared file; a setting step of notifying the first client of a candidate time for a lock time, which is a period of the locked state, based on operation history information regarding past editing operations on the shared file, and setting the lock time in accordance with an operation on the first client for the candidate time; A file management program for executing on one or more processors.

Images