History Management Device, Control Method, and Program

Abstract

This history management device (2000) acquires an operation log (50), which is a log of operations on a file (20) stored in a first storage unit (30). The history management device (2000) uses the operation log (50) to determine whether the file (20) has been edited, and if the file (20) has been edited, the history management device stores a copy file (60), which is a copy of the edited file (20), in a second storage unit (70). The history management device (2000) generates reference information (80) associating access information for accessing the copy file (60) stored in the second storage unit (70), and information relating to the operations performed on the file (20).

Description

Technical Field

[0001] This disclosure relates to a technique for managing the history of files.

Background Art

[0002] Techniques for managing the operation history of files have been developed. For example, Patent Document 1 discloses a technique for collecting keystroke information in a terminal that edits a file and storing it in a storage device of a server. According to this method, the editing history can be traced by comparing the file with the operation history.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the invention of Patent Document 1, it is necessary to collect keystroke information in a terminal that edits a file. The present invention has been made in view of this problem, and its object is to provide a new technique for managing the history of files.

Means for Solving the Problems

[0005] The history management device of this disclosure includes an acquisition unit that acquires an operation log representing a log of operations on a file stored in a first storage unit, a copy processing unit that determines whether the file has been edited using the operation log and stores a copy of the edited file in a second storage unit when the file has been edited, a reference information generation unit that generates reference information associating access information for accessing the copy of the file stored in the second storage unit with information regarding the operations performed on the file.

[0006] The control method of the present disclosure is executed by a computer. The control method includes an acquisition step of acquiring an operation log representing a log of operations on a file stored in a first storage unit, a copy process step of determining whether the file has been edited using the operation log, and storing a copy of the edited file in a second storage unit when the file has been edited; a reference information generation step of generating reference information associating access information for accessing the copy of the file stored in the second storage unit with information regarding the operations performed on the file.

[0007] The computer-readable medium of the present disclosure stores a program for causing a computer to execute the control method of the present disclosure.

Advantages of the Invention

[0008] According to the present disclosure, a new technique for managing the history of files is provided.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and redundant descriptions are omitted as necessary for clarity of explanation. Also, unless otherwise specified, predetermined values such as predetermined values and threshold values are stored in advance in a storage device accessible from the device that uses the value, such as a storage device. Further, unless otherwise specified, the storage unit may be implemented by one storage device or a plurality of storage devices. The storage device can be implemented by any medium such as a hard disk, SSD (Solid State Drive), or memory card.

[0011] FIG. 1 is a diagram illustrating an overview of the operation of the history management device 2000 according to Embodiment 1. Here, FIG. 1 is a diagram for facilitating understanding of the overview of the history management device 2000, and the operation of the history management device 2000 is not limited to that shown in FIG. 1.

[0012] The history management device 2000 generates reference information 80 that associates the operation log 50, which is a log of operations on the file 20 edited by the user, with access information to the copy file 60, which is a copy of the edited file 20. The file 20 is a file operated by the user and is stored in the first storage unit 30.

[0013] The first storage unit 30 is managed by the file management device 10. The first storage unit 30 is a storage device built into the file management device 10, a storage device (so-called external storage device) connected to the file management device 10 via an input / output interface, or a storage device (such as NAS (Network Attached Storage)) connected to the file management device 10 via a network.

[0014] The file management device 10 is, for example, a file server. In this case, the user operates the file 20 stored in the first storage unit 30 by accessing the file management device 10 using a directly operable terminal (hereinafter referred to as a user terminal). The user terminal is any terminal operable by the user, such as a PC (Personal Computer), a smartphone, or a tablet terminal. Note that various existing methods can be adopted for the method of operating the files managed by the file server using the user terminal.

[0015] The file management device 10 may be a user terminal. In this case, the user can directly access the file 20 stored in the first storage unit 30 from the user terminal without going through the file server.

[0016] The history management device 2000 acquires an operation log 50 indicating information regarding the operation in response to the file 20 stored in the first storage unit 30 being operated. The operation log 50 includes at least information that can identify whether the file 20 has been edited (whether the content of the file 20 has been changed). The operation log 50 is generated by the file management device 10. Here, existing technologies can be used for the technology of generating a log regarding an operation when a certain file is operated.

[0017] The history management device 2000 determines whether the file 20 has been edited using the operation log 50. If the file 20 has been edited, the history management device 2000 generates a copy of the edited file 20 (hereinafter referred to as a copy file 60) and stores it in the second storage unit 70. The second storage unit 70 is any storage device communicably connected to the history management device 2000. For example, a so-called cloud storage can be used as the second storage unit 70.

[0018] Furthermore, the history management device 2000 generates reference information 80 by associating an operation log 50 with access information for accessing a copy file 60 stored in the second storage unit 70. The access information indicates, for example, a path or a URL (Uniform Resource Locator) for accessing the copy file 60. Note that existing technologies can be used for the technology of realizing access to a file using a URL.

[0019] <An example of the effect> The history management device 2000 of the present embodiment acquires an operation log 50 that can grasp whether or not the file 20 has been edited, and determines whether or not the file 20 has been edited using the operation log 50. Then, when the file 20 has been edited, the history management device 2000 stores a copy file 60, which is a copy of the file 20, in the second storage unit 70. Furthermore, reference information 80 is generated by associating access information for accessing the copy file 60 with information regarding the operation performed on the file 20. Therefore, according to the history management device 2000, the editing history of the file 20 can be traced by viewing the copy file 60 using the reference information 80.

[0020] Here, according to the history management device 2000, unlike a version management system that involves processes such as checkout and commit by the user, the user does not need to perform complicated operations to manage the file history. Therefore, the file history can be easily managed. Also, as a method of recording the history of the file 20, a method of periodically recording a backup of the file 20 can be considered. However, in the case of a regular backup, the granularity of the history depends on the interval of the backup process. In this regard, according to the history management device 2000, a copy of the file 20 is recorded in response to the file 20 being edited. Therefore, the editing history of the file 20 can be managed with a more appropriate granularity.

[0021] Hereinafter, the history management device 2000 of the present embodiment will be described in more detail.

[0022] <Example of Functional Configuration> FIG. 2 is a block diagram illustrating the functional configuration of the history management apparatus 2000 according to Embodiment 1. The history management apparatus 2000 includes an acquisition unit 2020, a copy processing unit 2040, and a reference information generation unit 2060. The acquisition unit 2020 acquires the operation log 50. The copy processing unit 2040 determines whether or not the file 20 has been edited. Further, when the file 20 has been edited, the copy processing unit 2040 generates a copy file 60 for the file 20 and stores it in the second storage unit 70. The reference information generation unit 2060 generates reference information 80 in which information regarding the operation performed on the file 20 is associated with access information for accessing the copy file 60.

[0023] <Example of Hardware Configuration> Each functional component of the history management apparatus 2000 may be realized by hardware (e.g., a hard-wired electronic circuit, etc.) that realizes each functional component, or may be realized by a combination of hardware and software (e.g., a combination of an electronic circuit and a program that controls it, etc.). Hereinafter, the case where each functional component of the history management apparatus 2000 is realized by a combination of hardware and software will be further described.

[0024] FIG. 3 is a block diagram illustrating the hardware configuration of a computer 500 that realizes the history management apparatus 2000. The computer 500 is an arbitrary computer. For example, the computer 500 is a stationary computer such as a PC or a server machine. Additionally, for example, the computer 500 is a portable computer such as a smartphone or a tablet terminal. The computer 500 may be a dedicated computer designed to realize the history management apparatus 2000, or may be a general-purpose computer.

[0025] For example, by installing a predetermined application on computer 500, each function of history management device 2000 is realized on computer 500. The above application is composed of programs for realizing each functional component of history management device 2000. Note that the method of obtaining the above program is arbitrary. For example, the program can be obtained from a storage medium (such as a DVD disk or a USB memory) in which the program is stored. Among other things, for example, the program can be obtained by downloading the program from a server device that manages the storage unit in which the program is stored.

[0026] Computer 500 has a bus 502, a processor 504, a memory 506, a storage device 508, an input / output interface 510, and a network interface 512. Bus 502 is a data transmission path for processor 504, memory 506, storage device 508, input / output interface 510, and network interface 512 to transmit and receive data to and from each other. However, the method of connecting processor 504 and the like to each other is not limited to bus connection.

[0027] Processor 504 is various processors such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), or an FPGA (Field-Programmable Gate Array). Memory 506 is a main storage device realized using a RAM (Random Access Memory) or the like. Storage device 508 is an auxiliary storage device realized using a hard disk, an SSD (Solid State Drive), a memory card, or a ROM (Read Only Memory) or the like.

[0028] The input / output interface 510 is an interface for connecting the computer 500 and the input / output device. For example, an input device such as a keyboard and an output device such as a display device are connected to the input / output interface 510. The network interface 512 is an interface for connecting the computer 500 to a network. This network may be a LAN (Local Area Network) or a WAN (Wide Area Network). For example, the computer 500 is connected to the file management device 10 and the second storage unit 70 via the input / output interface 510 or the network interface 512.

[0029] The storage device 508 stores a program (a program for realizing the aforementioned application) for realizing each functional component of the history management device 2000. The processor 504 reads and executes this program in the memory 506 to realize each functional component of the history management device 2000.

[0030] The history management device 2000 may be realized by one computer 500 or by a plurality of computers 500. In the latter case, the configurations of the respective computers 500 do not have to be the same and can be different from each other.

[0031] <Flow of processing> FIG. 4 is a flowchart illustrating the flow of processing executed by the history management device 2000 according to Embodiment 1. The acquisition unit 2020 acquires the operation log 50 (S102). The copy processing unit 2040 determines whether the file 20 has been edited using the operation log 50 (S104). If the file 20 has been edited (S104: YES), the copy processing unit 2040 generates a copy file 60 for the edited file 20 and stores it in the second storage unit 70 (S106). The reference information generation unit 2060 associates the operation log 50 with the access information to the copy file 60 and generates reference information 80 (S108).

[0032] <Regarding the operation log 50> The operation log 50 is information regarding operations on the file 20. For example, the operation log 50 indicates the identification information of the user who operated on the file 20, the identification information of the file 20, and the type of operation (operation type) performed on the file 20. The identification information of the file 20 indicates, for example, the path for accessing the file 20 stored in the first storage unit 30. The operation type indicates, for example, either one of reference and editing. When the file 20 is edited, the operation type of the operation log 50 indicates "editing". On the other hand, when the file 20 is not edited, the operation type of the operation log 50 indicates "reference". Also, the operation log 50 may further indicate the time when the operation was performed (operation time).

[0033] FIG. 5 is a diagram illustrating the operation log 50 in a table format. The operation log 50 in FIG. 5 has four columns: user identification information 52, file identification information 54, operation type 56, and operation time 58. The operation log 50 in FIG. 5 represents that "user U1 edited the file 20 specified by the path P1 at time T1".

[0034] <Acquisition of the operation log 50: S102> The acquisition unit 2020 acquires the operation log 50 (S102). There are various methods for the acquisition unit 2020 to acquire the operation log 50. For example, the operation log 50 is transmitted from the file management device 10 to the history management device 2000. In this case, the acquisition unit 2020 acquires the operation log 50 by receiving the operation log 50. Additionally, for example, the operation log 50 is stored in a storage unit accessible from the history management device 2000. In this case, the acquisition unit 2020 acquires the operation log 50 by accessing that storage unit.

[0035] Here, when the acquisition unit 2020 actively acquires the operation log 50, in order to acquire the operation log 50 in response to the generation of the operation log 50, for example, the acquisition unit 2020 detects that the operation log 50 has been generated and acquires the operation log 50 in response to the detection. There are various methods for detecting that the operation log 50 has been generated. For example, the acquisition unit 2020 detects that the operation log 50 has been generated by receiving information indicating that the operation log 50 has been generated from the file management device 10. In addition, for example, the acquisition unit 2020 repeatedly accesses the storage unit where the operation log 50 is stored to repeatedly determine whether a new operation log 50 has been generated. By doing so, the acquisition unit 2020 can detect the existence of a new operation log 50 when it is generated.

[0036] <Determination of whether file 20 has been edited: S104> The copy processing unit 2040 determines whether file 20 has been edited using the operation log 50 (S104). For example, this determination can be realized by referring to the operation type indicated in the operation log 50. That is, when the operation type indicated in the operation log 50 is "edit", the copy processing unit 2040 determines that file 20 has been edited. On the other hand, when the operation type indicated in the operation log 50 is "reference", the copy processing unit 2040 determines that file 20 has not been referenced.

[0037] <Storage of copy file 60: S106> When it is determined that file 20 has been edited, the copy processing unit 2040 stores a copy file 60, which is a copy of the edited file 20, in the second storage unit 70. Here, the information capable of identifying the edited file 20 is indicated in the operation log 50. Specifically, the edited file 20 is the file 20 identified by the file identification information indicated in the operation log 50. The copy processing unit 2040 stores the copy file 60 for the file 20 identified by the file identification information in the second storage unit 70.

[0038] Note that the copy file 60 may be generated by the file management device 10 or by the copy processing unit 2040. In the former case, for example, the copy processing unit 2040 sends a request for generating the copy file 60 to the file management device 10. The request indicates the file identification information of the file 20 for which the copy file 60 is to be generated (the file identification information shown in the operation log 50). The file management device 10 generates the copy file 60 for the file 20 specified by the file identification information indicated in the received request and sends it to the history management device 2000. The copy processing unit 2040 receives the copy file 60 sent by the file management device 10 and stores it in the second storage unit 70.

[0039] On the other hand, when the copy processing unit 2040 generates the copy file 60, the copy processing unit 2040 accesses the file 20 via the file management device 10 to generate the copy file 60.

[0040] <Generation of reference information 80: S108> The reference information generation unit 2060 generates the reference information 80. The reference information 80 is information that associates the access information about the copy file 60 of the edited file 20 with the information about the editing operation performed on the file 20. The access information is information for accessing the copy file 60 stored in the second storage unit 70. For example, as described above, the access information indicates the path or URL of the copy file 60.

[0041] The information about the editing operation performed on the file 20 may be the operation log 50 itself, or information extracted from a part of the operation log 50, or information obtained by partially processing the operation log 50, etc.

[0042] <Output of reference information 80> The reference information generation unit 2060 outputs the reference information 80 in an arbitrary manner. For example, the reference information generation unit 2060 stores the reference information 80 in an arbitrary storage device. Additionally, for example, the reference information generation unit 2060 causes the reference information 80 to be displayed on a display device. Additionally, for example, the reference information generation unit 2060 may transmit the reference information 80 to another device.

[0043] Note that the history management device 2000 may also provide the user with not only the editing history of the file 20 but also the reference history of the file 20. In this case, when it is not indicated by the operation log 50 that the file 20 has been edited (that is, when it is indicated by the operation log 50 that the file 20 has been referenced), the history management device 2000 stores the operation log 50 in an arbitrary storage unit. Then, the history management device 2000 provides the user with the operation history of the file 20 by using the operation log 50 stored in the storage unit and the reference information 80.

[0044] FIG. 6 is a diagram illustrating the operation history of the file 20. On the screen 90 of FIG. 6, the operation history of each file 20 stored in the first storage unit 30 is shown. For any operation, the operation time, file name, operation type, and user name are shown. Further, for the file 20 on which an edit operation has been performed, a URL for accessing the copy file 60 is shown.

[0045] <Reduction of Copy Frequency> In the above example, the copy file 60 is generated each time the file 20 is edited. However, when the same file 20 is repeatedly edited by the same user within a relatively short period, instead of generating the copy file 60 for each of the multiple edits, the copy file 60 may be generated after those multiple edits have been performed. Thereby, since the generation frequency of the copy file 60 can be reduced, the processing load on the file management device 10 and the history management device 2000 can be reduced, or the usage amount of the recording area of the second storage unit 70 can be reduced.

[0046] Therefore, for example, the history management device 2000 controls the generation of the copy file 60 by setting a predetermined waiting time. The waiting time is set in association with a pair of the identification information of the edited file 20 and the identification information of the user who edited the file 20. After setting the waiting time, the history management device 2000 executes predetermined event processing in response to the elapse of the waiting time. The event processing is the creation of the copy file 60 and the generation of the reference information 80. That is, after setting the waiting time, even if the same file 20 is edited multiple times by the same user before the waiting time elapses, the copy file 60 is not generated during that period. For example, when the predetermined time is 10 minutes, even if the same user repeatedly edits the same file within 10 minutes, only one copy file 60 is generated for those multiple edits.

[0047] The setting of the waiting time is performed, for example, using a timer. The timer is activated in association with a pair of the identification information of the edited file 20 and the identification information of the user who edited the file 20. When the waiting time elapses after activating the timer, the above-described event processing is executed by the history management device 2000.

[0048] Hereinafter, the processing using the timer will be described more specifically. FIGS. 7 and 8 are diagrams illustrating the processing performed by the history management device 2000 using the timer. FIG. 7 is a flowchart showing the flow of processing executed by the history management device 2000 in response to obtaining the operation log 50 in a case where a timer is used. That is, in the case where a timer is used, instead of the flowchart of FIG. 4, the flowchart of FIG. 7 is executed. FIG. 8 is a flowchart illustrating the flow of processing performed by the history management device 2000 in response to the file 20 being opened.

[0049] First, FIG. 7 will be described. Note that S102 and S104 are the same as those shown in FIG. 4. In S104, when it is determined that the file 20 has been edited (S104: YES), the copy processing unit 2040 determines whether the timer corresponding to the edited file 20 (that is, the timer corresponding to the identification information of the file 20 indicated by the operation log 50) is operating (S202).

[0050] When the timer corresponding to the edited file 20 is not operating (S204: NO), the copy processing unit 2040 starts the timer in association with the pair of the identification information of the edited file 20 and the identification information of the user who edited the file 20 (that is, the pair of the file identification information and the user identification information indicated by the operation log 50) (S206). On the other hand, when the timer corresponding to the edited file 20 has already been started (S204: YES), the process of FIG. 7 ends.

[0051] When the flow of the process executed by the history management device 2000 is represented by the flowchart of FIG. 7, the processes shown in S106 and S108 of FIG. 4 are executed as the above-described event processes. That is, when a predetermined time has elapsed since the timer was started, the copy processing unit 2040 stores the copy file 60 in the second storage unit 70 (S106). Then, the reference information generation unit 2060 generates the reference information 80 (S108).

[0052] Here, when a timer is used and a single copy file 60 is generated by summarizing multiple edits, multiple operation logs 50 can correspond to one copy file 60. For example, it is assumed that a timer is started in association with a pair of "file P1, user U1" in response to obtaining an operation log A indicating that file P1 has been edited by user U1. Then, it is assumed that an operation log B indicating that file P1 has been edited by user U1 is further obtained before a predetermined time elapses. In this case, the copy file 60 stored in the second storage unit 70 by event processing is a copy of file P1 that reflects the edit operation indicated by operation log A and the edit operation indicated by operation log B.

[0053] In this case, for example, the copy processing unit 2040 associates information regarding a plurality of edit operations performed on file 20 with the access information for the copy file 60 in the reference information 80. For example, in the above example, the reference information generation unit 2060 associates the information regarding the file operation indicated by operation log A and the information regarding the file operation indicated by operation log B with the access information of the copy file 60. Additionally, for example, the reference information generation unit 2060 may use any one of these plurality of operation logs 50 for generating the reference information 80. For example, the reference information generation unit 2060 generates the reference information 80 by associating the information regarding the file operation indicated by the latest operation log (operation log B in the above example) among the plurality of operation logs with the access information of the copy file 60.

[0054] Next, FIG. 8 will be described. Here, assume that after a timer is activated in response to a file P1 being edited by a certain user U1, and before a predetermined time elapses, the file P1 is opened by another user U2. In this case, in order to prevent the editing operations by user U1 and user U2 from being combined into one, it is necessary to store a copy file 60 of the file P1 edited by user U1 in the second storage unit 70 before the file P1 is edited by user U2. FIG. 8 shows the process for realizing this.

[0055] As a premise, the file management device 10 detects that the open process of the file 20 has been executed and temporarily suspends the open process. Then, the file management device 10 transmits to the history management device 2000 a pair of the identification information of the file 20 for which the open process is suspended and the identification information of the user who is trying to open the file 20. Hereinafter, the information indicating this pair is referred to as file open information.

[0056] The acquisition unit 2020 receives the file open information (S302). The copy processing unit 2040 determines whether a timer corresponding to the file 20 for which the open process is suspended (that is, the timer corresponding to the identification information of the file 20 indicated by the file open information) is operating (S304). If the timer is not operating (S304), the copy processing unit 2040 transmits a notification permitting the open process to the file management device 10 (S306). In response to receiving the notification, the file management device 10 resumes the suspended open process.

[0057] When the above timer is operating (S304: YES), the copy processing unit 2040 determines whether the identification information of the user associated with the above timer matches the identification information of the user attempting to open the file (that is, the identification information of the user indicated in the file open information) (S308). If these identification information match (S308: YES), the copy processing unit 2040 sends a notification permitting the open to the file management device 10 (S306).

[0058] On the other hand, when these identification information do not match (S308: NO), the copy processing unit 2040 stops the above timer (S310). The copy processing unit 2040 stores the copy file 60 for the file 20 whose open processing is pending in the second storage unit 70 (S312). The copy processing unit 2040 sends a notification permitting the open processing to the file management device 10 (S314). The reference information generation unit 2060 generates reference information 80 (S316). For the generation of this reference information 80, one or more operation logs 50 regarding the editing operations performed by the user associated with the stopped timer are used.

[0059] As described above, the present invention has been described with reference to the embodiments, but the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0060] Note that, in the above example, the program can be stored using various types of non-transitory computer readable media and provided to a computer. The non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROM, CD-R, CD-R / W, semiconductor memories (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM). Also, the program may be provided to the computer by various types of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The transitory computer readable media can supply the program to the computer via wired communication paths such as electric wires and optical fibers, or wireless communication paths.

[0061] Some or all of the above embodiments may be described as follows in the appended claims, but are not limited thereto. (Appendix 1) An acquisition unit that acquires an operation log representing a log of operations on a file stored in the first storage unit; A copy processing unit that determines whether the file has been edited using the operation log, and when the file has been edited, stores a copy of the edited file in a second storage unit; A reference information generation unit that generates reference information associating access information for accessing a copy of the file stored in the second storage unit with information regarding an operation performed on the file. A history management device having the above components. (Appendix 2) The operation log indicates file identification information of the file and the type of operation performed on the file. The copy processing unit when the type of the operation indicated by the operation log indicates an editing operation, determines that the file has been edited, and stores a copy of the file specified by the file identification information indicated by the operation log in the second storage unit. The history management device according to Supplementary Note 1. (Supplementary Note 3) When a plurality of editing operations are performed on the same file by the same user within a predetermined time, the copy processing unit stores a copy of the file in the second storage unit after the plurality of editing operations are performed. The history management device according to Supplementary Note 1 or 2. (Supplementary Note 4) The operation log indicates the file identification information of the file and the user identification information of the user who operated the file. The copy processing unit in response to the acquisition of the operation log, determines whether a waiting time is set corresponding to the file identification information and the user identification information indicated in the operation log. When the waiting time is not set, the waiting time is set in association with the file identification information and the user identification information indicated in the operation log. After the waiting time is set, when the waiting time has elapsed, a copy of the file specified by the file identification information associated with the waiting time is stored in the second storage unit. The history management device according to Supplementary Note 3. (Supplementary Note 5) The acquisition unit acquires file open information indicating the file identification information of the file to be opened and the user identification information of the user who is about to open the file from the device that manages the file. The copy processing unit in response to the acquisition of the file open information, determines whether a waiting time set corresponding to the file identification information indicated by the file open information is set. The waiting time corresponding to the file identification information indicated by the file open information is set, and when the user identification information associated with the waiting time matches the user identification information indicated by the file open information, the setting of the waiting time is deleted, and a copy of the file specified by the file identification information indicated in the file open information is stored in the second storage unit. The history management device according to supplementary note 4. (Supplementary note 6) A control method executed by a computer, An acquisition step of acquiring an operation log representing a log of operations on a file stored in a first storage unit, Determining whether the file has been edited using the operation log, and when the file has been edited, a copy process step of storing a copy of the edited file in a second storage unit, A reference information generation step of generating reference information associating access information for accessing a copy of the file stored in the second storage unit with information regarding an operation performed on the file. A control method having the above steps. (Supplementary note 7) The operation log indicates the file identification information of the file and the type of operation performed on the file. In the copy process step, When the type of operation indicated by the operation log indicates an edit operation, it is determined that the file has been edited, A copy of the file specified by the file identification information indicated by the operation log is stored in the second storage unit. The control method according to supplementary note 6. (Supplementary note 8) In the copy process step, when multiple edit operations are performed on the same file by the same user within a predetermined time, after those multiple edit operations are performed, a copy of the file is stored in the second storage unit. The control method according to supplementary note 6 or 7. (Supplementary note 9) The operation log indicates the file identification information of the file and the user identification information of the user who operated the file, In the copy processing step, in response to the acquisition of the operation log, determine whether a waiting time is set corresponding to the file identification information and the user identification information indicated in the operation log, if the waiting time is not set, set the waiting time corresponding to the file identification information and the user identification information indicated in the operation log, After the waiting time is set, when the waiting time has elapsed, store a copy of the file specified by the file identification information associated with the waiting time in the second storage unit, the control method according to Supplementary Note 8. (Supplementary Note 10) In the acquisition step, acquire file open information indicating the file identification information of the file to be opened and the user identification information of the user who is trying to open the file from the device that manages the file, In the copy processing step, in response to the acquisition of the file open information, determine whether a waiting time is set corresponding to the file identification information indicated by the file open information, if the waiting time is set corresponding to the file identification information indicated by the file open information, and the user identification information associated with the waiting time matches the user identification information indicated by the file open information, delete the setting of the waiting time and store a copy of the file specified by the file identification information indicated in the file open information in the second storage unit, the control method according to Supplementary Note 9. (Supplementary Note 11) For a computer, an acquisition step of acquiring an operation log representing a log of operations on a file stored in a first storage unit, A copy processing step of determining whether the file has been edited using the operation log, and storing a copy of the edited file in a second storage unit when the file has been edited; A computer-readable medium storing a program that executes a reference information generation step of generating reference information associating access information for accessing a copy of the file stored in the second storage unit with information regarding an operation performed on the file. (Appendix 12) The operation log indicates file identification information of the file and a type of operation performed on the file. In the copy processing step, when the type of operation indicated by the operation log indicates an edit operation, it is determined that the file has been edited, A computer-readable medium according to Appendix 11, which stores a copy of the file specified by the file identification information indicated by the operation log in the second storage unit. (Appendix 13) In the copy processing step, when a plurality of edit operations are performed on the same file by the same user within a predetermined time, after those plurality of edit operations are performed, a copy of the file is stored in the second storage unit. The computer-readable medium according to Appendix 11 or 12. (Appendix 14) The operation log indicates file identification information of the file and user identification information of the user who operated the file. In the copy processing step, in response to the operation log being acquired, it is determined whether a waiting time is set corresponding to the file identification information and the user identification information indicated in the operation log, when the waiting time is not set, the waiting time is set corresponding to the file identification information and the user identification information indicated in the operation log. After the standby time is set, if the standby time has elapsed, a copy of the file specified by the file identification information associated with the standby time is stored in the second storage unit, the computer-readable medium according to appended note 13. (Appended note 15) In the acquisition step, file open information indicating the file identification information of the file to be opened and the user identification information of the user attempting to open the file is acquired from the device managing the file, In the copy process step, In response to the acquisition of the file open information, it is determined whether a standby time corresponding to the file identification information indicated by the file open information is set, If the standby time corresponding to the file identification information indicated by the file open information is set and the user identification information associated with the standby time matches the user identification information indicated by the file open information, the setting of the standby time is deleted, and a copy of the file specified by the file identification information indicated in the file open information is stored in the second storage unit, the computer-readable medium according to appended note 14.

Explanation of reference signs

[0062] 10 File management device 20 File 30 First storage unit 50 Operation log 52 User identification information 54 File identification information 56 Operation type 58 Operation time 60 Copy file 70 Second storage unit 80 Reference information 90 Screen 500 Computer 502 Bus 504 Processor 506 Memory 508 Storage device 510 Input / output interface 512 Network interface 2000 History management device 2020 Acquisition unit 2040 Copy processing unit 2060 Reference information generation unit

Claims

1. An acquisition unit that acquires an operation log representing a log of operations on a file stored in the first storage unit; A copy processing unit that determines whether the file has been edited using the operation log, and stores a copy of the edited file in a second storage unit when the file has been edited; A reference information generation unit that generates reference information associating access information for accessing a copy of the file stored in the second storage unit with information regarding an operation performed on the file, and has: The copy processing unit stores a copy of the file in the second storage unit after a plurality of edit operations have been performed on the same file by the same user within a predetermined time, a history management device.

2. The operation log indicates file identification information of the file and the type of operation performed on the file, The copy processing unit, When the type of operation indicated by the operation log indicates an edit operation, it is determined that the file has been edited, The history management device according to claim 1, wherein a copy of the file specified by the file identification information indicated by the operation log is stored in the second storage unit.

3. The operation log indicates file identification information of the file and user identification information of the user who operated the file, The copy processing unit, In response to the operation log being acquired, it is determined whether a standby time is set corresponding to the file identification information and the user identification information indicated in the operation log, When the standby time is not set, the standby time is set corresponding to the file identification information and the user identification information indicated in the operation log, After the standby time is set, when the standby time has elapsed, a copy of the file specified by the file identification information associated with the standby time is stored in the second storage unit, the history management device according to claim 1 or 2.

4. The acquisition unit acquires file open information indicating file identification information of the file to be opened and user identification information of the user who is trying to open the file from a device that manages the file, The copy processing unit, In response to the acquisition of the file open information, it is determined whether the waiting time corresponding to the file identification information indicated by the file open information is set. The history management device according to claim 3, wherein when the waiting time corresponding to the file identification information indicated by the file open information is set, and the user identification information associated with the waiting time matches the user identification information indicated by the file open information, the setting of the waiting time is deleted, and a copy of the file specified by the file identification information indicated by the file open information is stored in the second storage unit.

5. A control method executed by a computer, comprising: an acquisition step of acquiring an operation log representing a log of operations on a file stored in a first storage unit; a copy processing step of determining, using the operation log, whether the file has been edited, and when the file has been edited, storing a copy of the edited file in a second storage unit; a reference information generation step of generating reference information associating access information for accessing a copy of the file stored in the second storage unit with information regarding an operation performed on the file. The control method, wherein in the copy processing step, when a plurality of edit operations are performed on the same file by the same user within a predetermined time, after the plurality of edit operations are performed, a copy of the file is stored in the second storage unit.

6. The operation log indicates file identification information of the file and a type of operation performed on the file. In the copy processing step, when the type of operation indicated by the operation log indicates an edit operation, it is determined that the file has been edited; The control method according to claim 5, wherein a copy of the file specified by the file identification information indicated by the operation log is stored in the second storage unit.

7. The operation log indicates file identification information of the file and user identification information of a user who operated the file. In the copy processing step, In response to the acquisition of the operation log, it is determined whether a waiting time is set corresponding to the file identification information and the user identification information shown in the operation log. If the waiting time is not set, the waiting time is set in association with the file identification information and the user identification information shown in the operation log. After the waiting time is set, when the waiting time has elapsed, a copy of the file specified by the file identification information associated with the waiting time is stored in the second storage unit. The control method according to claim 5 or 6.

8. In the acquisition step, file open information indicating the file identification information of the file to be opened and the user identification information of the user attempting to open the file is acquired from the device managing the file. In the copy processing step, In response to the acquisition of the file open information, it is determined whether a waiting time is set corresponding to the file identification information indicated by the file open information. If the waiting time is set corresponding to the file identification information indicated by the file open information, and the user identification information associated with the waiting time matches the user identification information indicated by the file open information, the setting of the waiting time is deleted, and a copy of the file specified by the file identification information shown in the file open information is stored in the second storage unit. The control method according to claim 7.

9. Causing a computer to perform an acquisition step of acquiring an operation log representing a log of operations on a file stored in a first storage unit; a copy processing step of determining whether the file has been edited using the operation log, and storing a copy of the edited file in a second storage unit when the file has been edited; perform a reference information generation step of generating reference information associating access information for accessing a copy of the file stored in the second storage unit with information regarding an operation performed on the file. In the copy processing step, if a plurality of editing operations are performed on the same file by the same user within a predetermined time, after those plurality of editing operations are performed, a copy of the file is stored in the second storage unit. A program.

10. The operation log indicates file identification information of the file and the type of operation performed on the file. In the copy processing step, When the type of operation indicated by the operation log indicates an editing operation, it is determined that the file has been edited. The program according to claim 9, wherein a copy of the file specified by the file identification information indicated by the operation log is stored in the second storage unit.

11. The operation log indicates file identification information of the file and user identification information of the user who operated the file. In the copy processing step, In response to the acquisition of the operation log, it is determined whether a waiting time is set corresponding to the file identification information and the user identification information indicated in the operation log. If the waiting time is not set, the waiting time is set in association with the file identification information and the user identification information indicated in the operation log. After the waiting time is set, when the waiting time has elapsed, a copy of the file specified by the file identification information associated with the waiting time is stored in the second storage unit. The program according to claim 9 or 10.

12. In the acquisition step, file open information indicating file identification information of the file to be opened and user identification information of the user who is trying to open the file is acquired from a device that manages the file. In the copy processing step, In response to the acquisition of the file open information, it is determined whether a waiting time set corresponding to the file identification information indicated by the file open information is set. The waiting time corresponding to the file identification information indicated by the file open information is set, and when the user identification information associated with the waiting time matches the user identification information indicated by the file open information, the setting of the waiting time is deleted, and a copy of the file specified by the file identification information indicated in the file open information is stored in the second storage unit. The program according to claim 11.

Images