JP2008129730A - Shared file management method, shared file management program, and shared file management apparatus - Google Patents

Abstract

To realize shared file management with high security without inconvenience to the owner of a shared file.
A shared file management method for sharing a file by each user becoming an owner of the file, wherein the computer has an ownership relationship between the file and the owner, and each owner has the file Is stored in the storage unit, and the storage unit is referred to whether or not each owner having the ownership relationship needs a file based on the determination condition. According to the determination result, access is prohibited for a file that does not have an owner who needs the file.
[Selection] Figure 1

Description

  The present invention relates to a technique for a shared file management method, a shared file management program, and a shared file management apparatus.

A shared file system is a file system in which a plurality of users share one file. Conventionally, as described in Patent Document 1, the system extracts an unnecessary file in accordance with the use state of a shared file, and deletes the unnecessary file.
Japanese Patent Laid-Open No. 2002-278806

  In the conventional technology, even when there is a user who needs a shared file, if the system determines that the shared file is an unnecessary file, the shared file is deleted against the intention of the user who owns the shared file. For this reason, the user is inconvenienced.

  On the other hand, the user may copy the shared file to his / her hand so that the shared file may be deleted without permission. However, if a shared file is placed outside the system management target, the file may be leaked due to unauthorized access.

  SUMMARY OF THE INVENTION Accordingly, it is a primary object of the present invention to solve the above-described problems and realize shared file management with high security without inconvenience to the owner of the shared file.

  In order to solve the above problems, the present invention is a shared file management method for sharing a file by each user becoming the owner of the file, wherein the computer has an ownership relationship between the file and the owner, In addition, a determination condition for determining whether or not each owner needs a file is stored in the storage unit, and a file is required for each owner having the ownership relationship based on the determination condition. Whether to do so is determined with reference to the storage unit, and access is prohibited for a file that does not have an owner that needs the file, based on the determination result of the determination. Other means will be described later.

  According to the present invention, whether or not to delete a file is determined based on the determination condition set by the owner, so that the shared file is not deleted against the user's intention. In addition, access to files that the owner does not need is prohibited. As a result, the owner does not need to copy the file to his / her hand, and the file that is not used by anyone does not remain, so that shared file management with high security can be realized.

  Hereinafter, an embodiment of a shared file management system to which the present invention is applied will be described in detail with reference to the drawings.

  FIG. 1 is an explanatory diagram showing an outline of a problem to be solved by the present invention and a means for solving the problem regarding file sharing. FIG. 1A shows file registration, FIG. 1B shows file waiver in this embodiment, and FIG. 1C shows file waiver in the comparative example. In FIG. 1A, a user 101a registers a shared file 101d in a public folder 101e.

  First, in FIG. 1B, the user 101a gives up ownership of the file 101d registered by himself / herself. However, since the user 101b and the user 101c who are other file sharers still need the file 101d, the file is not deleted and can be accessed.

  On the other hand, in FIG.1 (c), the user 101a abandons ownership of the file 101d which he registered. By directly reflecting the will of the user 101a who is a registrant, the file 101d is immediately deleted. The user 101b who is another file sharer copies the file 101d to his / her private folder 101f before the file 101d is deleted. However, if the security management of the private folder 101f is insufficient, the copied file 101d becomes a target of unauthorized access. The user 101c who is another file sharer cannot access the file 101d after the file 101d is deleted, and is inconvenienced.

  FIG. 2 is a configuration diagram showing the shared file management system. Each server constituting the shared file management system is configured as a computer including at least a memory serving as a storage unit (storage unit) used when performing arithmetic processing and an arithmetic processing device that performs the arithmetic processing. The memory is constituted by a RAM (Random Access Memory) or the like. Arithmetic processing is realized by an arithmetic processing unit configured by a CPU (Central Processing Unit) executing a program on a memory.

  The shared file management system includes a shared file system management server 101, a file information processing server 111, a determination condition confirmation server 121, a file work processing server 141, an access prohibition processing server 151, a file display processing server 161, and a work history management server 171. Are connected by a network 131.

  The network 131 may be, for example, an open network such as the Internet, a local network such as an in-house network (intranet such as WAN or LAN), or a combination thereof.

  The number of computers constituting the shared file management system is not limited to the number shown in FIG. For example, a configuration may be adopted in which a plurality of components are assigned to one computer, or all the components may be assigned to one computer as a stand-alone system. In addition, each component may be configured not only in a single server but also in a plurality of servers via the network 131.

  The shared file system management server 101 includes a storage device 107, a main storage device 108, and a CPU 109. The CPU 109 reads the processes, threads, and the like of the shared file system management unit 106 into the main storage device 108 and executes them in accordance with an OS (Operating System) instruction. The storage device 107 stores a file information management table 102, a determination condition management table 103, a migration destination management table 104, and a user information management table 105.

  The file information processing server 111 is a server including the file information processing unit 112 and includes a main storage device 113 and a CPU 114. The CPU 114 reads the processes, threads, and the like of the file information processing unit 112 into the main storage device 113 and executes them in accordance with instructions from the OS.

  The determination condition confirmation server 121 is a server including a determination condition confirmation unit 122 and includes a main storage device 123 and a CPU 124. The CPU 124 reads the process, thread, and the like of the determination condition confirmation unit 122 into the main storage device 123 and executes them in accordance with an instruction from the OS.

  The file work processing server 141 is a server including a file work processing unit 142, and includes a main storage device 143 and a CPU 144, to which a file management unit 145 is connected. The CPU 144 reads the process, thread, and the like of the file work processing unit 142 into the main storage device 143 and executes them in accordance with an instruction from the OS, and stores the file data registered by the user in the file management unit 145.

  The access prohibition processing server 151 is a server including the access prohibition processing unit 152, and includes a main storage device 153 and a CPU 154, to which a migration destination file management unit 155 is connected. The CPU 154 reads the process, thread, and the like of the access prohibition processing unit 152 into the main storage device 153 and executes them in accordance with the instruction of the OS, and compresses the file data moved to the migration destination file management unit 155 as it is. Store.

  The file display processing server 161 is a server including a file display processing unit 162, and includes a main storage device 163 and a CPU 164, to which an input / output device 165 is connected. The CPU 164 reads the processes, threads, and the like of the file display processing unit 162 into the main storage device 163 and executes them in accordance with instructions from the OS. The input / output device 165 is an input device such as a keyboard and a mouse, a display device, and a printing device.

  The work history management server 171 is a server including a work history confirmation unit 172, and includes a main storage device 173 and a CPU 174, to which a work history management unit 175 is connected. The CPU 174 reads the process, thread, and the like of the work history confirmation unit 172 into the main storage device 173 and executes them in accordance with an instruction from the OS.

  FIG. 3 is an explanatory diagram showing the relationship between processing units and tables in the shared file management system, and the flow of control.

  The shared file system management unit 106 performs registration and acquisition of records stored in the tables for each management table. Details of each management table will be described below.

  The file information management table 102 in FIG. 4 associates the ownership relationship between the file and the owner and the determination condition for determining whether or not each owner needs the file as file information. Managed to storage means (storage unit).

  Each table in FIG. 4 and the like corresponds to each other using an ID as a key.

  “File ID” is an ID for uniquely identifying a file and its file information. “User ID” is an ID for uniquely identifying a user. Regarding the user ID, “owner” indicates the owner of the file, and “worker” indicates the person who works on the file. Regarding the work, “work type” indicates the work content performed by the user, and “work time limit” indicates the work content time limit. A plurality of “owners”, “workers”, and “work” can be set for one file information. When a plurality of “owners” are set, a plurality of people share one file.

  “Condition ID” is an ID for uniquely identifying a determination condition for determining whether or not a file is necessary. Regarding the determination information, “unnecessary” is set in the “determination flag” when it is determined that the file is unnecessary according to the determination conditions of all the owners of the file. “Unnecessary processing” indicates the processing content for prohibiting access to a file that is no longer required by the determination flag. Access prohibition is, for example, a process of moving a file, a process of moving and compressing a file, or a process of deleting a file. The disk ID is an ID for uniquely identifying the disk in which the file is stored. The “destination disk ID” indicates a destination at the time of moving in the unnecessary process.

  For example, the file indicated by the file ID “F004” is owned by two owners (userB, userC), and the determination condition indicated by the condition ID “C003” is set. At present, a determination flag indicating that a file is necessary is set according to this determination condition. However, when a file is no longer needed by two owners in the future, the file is set to the destination indicated by the disk ID “D001”. It will be moved and compressed.

  The file information management table 102 shows details of file information. For example, the file indicated by the file ID “F004” has a file size “107890 (bytes)”, a file name “file D”, and a storage destination disk ID “D013”.

表１に示す判定条件管理テーブル１０３は、ファイルの判定条件を管理する。「条件ＩＤ」で示される各判定条件は、条件となるプロパティとその値との組により表現される。プロパティは、ファイル情報管理テーブル１０２または、作業履歴管理テーブル１７６を構成する各パラメータである。

The determination condition management table 103 shown in Table 1 manages file determination conditions. Each determination condition indicated by “condition ID” is expressed by a set of a property that is a condition and its value. The property is each parameter constituting the file information management table 102 or the work history management table 176.

  As an example of using the parameter of the file information management table 102 as a property, for example, the determination condition “no worker” is expressed by a set of a property “worker” and a value “none”. Based on this determination condition, it is determined that the file is unnecessary when there is no file operator.

  As an example of setting the parameter of the work history management table 176 as a property, for example, a set of a property “work history” and a value “current date and time and last reference date is 30 days or more” is set. When the determination condition is set in this way, it is determined that the file is unnecessary if 30 days or more have passed since the date and time when the file was last referred to based on the work history.

  “Counter upper limit value” and “counter” are control parameters for realizing the trash can function. The trash function is not to delete files that are no longer needed, but to temporarily store them in a evacuation place called trash, and delete the files in the trash when they accumulate in the trash It is. With this trash box function, even if it is determined that the file is unnecessary at first, the file can be acquired from the trash box when it is necessary later, so that the necessary file can be acquired.

  The value of the “counter” is incremented by one each time the file information processing unit 112 determines that the file is unnecessary. At this time, the file determined to be unnecessary is moved to the trash box. Then, when the value of the “counter” exceeds the “counter upper limit value”, it is considered that the file has accumulated in the trash box, and each file that causes the addition of the value of the “counter” is deleted.

表２に示す移動先管理テーブル１０４は、ファイルの移動先の情報を管理する。「ディスクＩＤ」は、ファイルの移動先となるディスクを一意に識別するためのＩＤである。「ディスク名」は、ディスクＩＤに対応するディスクの名称である。移動先の「パス」は、ディスク名に対応するディスクにおける移動先の情報である。なお、移動先のパスをユーザが登録する場合は、移動先管理テーブル１０４のディスクＩＤおよびディスク名を表示し、ユーザにパスを直接入力してもらう。

The migration destination management table 104 shown in Table 2 manages file migration destination information. “Disk ID” is an ID for uniquely identifying a disk to which a file is to be moved. “Disk name” is the name of the disk corresponding to the disk ID. The “path” of the movement destination is information on the movement destination in the disk corresponding to the disk name. When the user registers the destination path, the disk ID and disk name in the destination management table 104 are displayed, and the user directly inputs the path.

表３に示すユーザ情報管理テーブル１０５は、ユーザＩＤで示されるユーザに関する詳細な情報を示す。各ユーザのユーザ情報は、例えば共有ファイル管理システムのシステム管理者が登録する。例えば、「ｕｓｅｒＡ」は、そのユーザ名が「ユーザＡ」、その所属組織が「総務」である。ユーザＡには、ディスクの使用許可サイズとして「５２４２８８００（ｂｙｔｅ）」が割り当てられており、そのうち、「１０５０６２４（ｂｙｔｅ）」を使用している。なお、使用済みサイズは、複数人で１つのファイルを所有している時は、そのファイルサイズを各所有者で等分される。

The user information management table 105 shown in Table 3 shows detailed information about the user indicated by the user ID. The user information of each user is registered by, for example, a system administrator of the shared file management system. For example, “userA” has a user name “user A” and its organization “general affairs”. The user A is assigned “524428800 (bytes)” as the disk use permission size, and among them, “1050624 (bytes)” is used. The used size is divided equally among the owners when the file is owned by a plurality of people.

表４に示す作業履歴管理テーブル１７６は、ユーザがどのファイルに対して作業したか一意に識別するための「ファイルＩＤ」、ユーザがいつファイルに対して作業したか示す「作業日時」、どのユーザがファイルを作業したか示す「ユーザＩＤ」、どの作業か示す「作業内容」を対応づけて管理する。

The work history management table 176 shown in Table 4 includes a “file ID” for uniquely identifying which file the user has worked on, a “work date” indicating when the user has worked on the file, and which user “User ID” indicating whether the file has been worked on, and “Work content” indicating which work is associated and managed.

  The work history confirmation unit 172 receives the work history performed by the user from the file work processing unit 142 and writes the work performed on the file to the work history management table 176. Specifically, the work history confirmation unit 172 receives a work history registration request from the file work processing unit 142 and writes the work history to the work history management table 176 stored in the work history management unit 175.

  The file work processing unit 142 performs work performed by the user and stores the file in the file management unit 145. The file management unit 145 stores file entities corresponding to file information managed by the file information management table 102.

  The file information processing unit 112 sets the file information designated by the user in the file information management table 102 from the shared file system management unit 106.

  When the user sets a plurality of file owners, the used size set for each owner is calculated in order to keep the file size equally divided by each owner, and the shared file system management unit 106 is used. Are set in the user information management table 105.

  The file work processing unit 142 performs file work according to work designated by the user. The file operation is performed via the file display processing unit 162. For example, when the user refers to the contents of a file, the corresponding file is acquired from the file management unit 145 via the file display processing unit 162, and the content is displayed.

  The file display processing unit 162 displays a file designated as a work target by the user based on the information in the file information management table 102 and the information in the user information management table 105.

  The file display processing unit 162 acquires the information set in the user information management table 105 and the file information management table 102 via the shared file system management unit 106, and retrieves the files for which the user is the owner and worker. indicate. The user performs work on the displayed file. In addition, when a file with a work deadline is displayed, if the user displays the target file and the work deadline is within one day, an alarm is displayed in a dialog box to indicate that. To do.

  Based on the determination condition, the determination condition confirmation unit 122 determines whether each owner having the ownership relationship needs a file with reference to a storage unit (storage unit). The file information processing unit 112 sets “unnecessary” to the determination flag of the file information management table 102 for a file for which there is no owner who needs the file. In addition, when there are no owners, this is an example in which there is no owner who needs a file.

  If “unnecessary” is set in the determination flag of the file information management table 102, the access prohibition processing unit 152 acquires the file from the file work processing unit 142 and then prohibits access to the file. For example, when moving a file, the migration destination is obtained from the file information management table 102, the migration destination information of the disk ID of the corresponding migration destination management table 104 is obtained, and the file is stored in the path setting value of the migration destination management table 104. Is stored. When compressing a file, the destination file management unit 155 stores the substance of the compressed file.

  Hereinafter, the operation of the shared file management system of this embodiment will be described with reference to flowcharts.

  FIG. 5 is a flowchart showing an operation for file information. The process of FIG. 5A calls the subroutine of FIG.

  The process of FIG. 5A will be described. The file display processing unit 162 receives a file designation and an operation input to the file information (S101). The designation of the file is realized by designating a file name or a file ID, for example. The operation on the file information is, for example, registration of a file, addition of an owner corresponding to an already registered file, or deletion of an owner.

  When registering a file, the file information registered in the file information management table 102 is received together with the file registered from the user. When performing the file registration operation, the file information processing unit 112 notifies the file work processing unit 142 that the file registration has been accepted, and the file work processing unit 142 registers the file. The file information processing unit 112 issues a file ID, registers the information received in S101 in the file information management table 102 in association with the issued file ID.

  When the file has already been registered, the file information processing unit 112 acquires the file information of the designated file from the file information management table 102. For example, when the owner “userB” of the file ID “F004” performs an owner deletion operation indicating that the owner is discarded, the file information processing unit 112 performs the corresponding operation in the file information management table 102. Remove the owner of the file from the owner of the file that destroys being the owner. For example, the file information processing unit 112 deletes “userB” from the owner of the file ID “F004” of the file information.

  The file information processing unit 112 calls and determines a subroutine (see FIG. 5B) for determining whether or not to operate the file information from the file size of the file specified in S101 (S102). As a result of S102, the file information processing unit 112 performs the operation on the specified file information if the operation on the file information is permitted (S103). When the operation on the file information is not permitted, a warning message is notified in the processing in the subroutine, so S103 is not executed.

  The process of FIG. 5B called in S102 will be described. An example in which an owner deletion operation indicating that the owner “userB” of the file ID “F004” is to be discarded will be described.

  The file information processing unit 112 acquires the (current) owner count before the operation of the file specified in S101. The file information processing unit 112 calculates the file size per owner before the operation by dividing the file size of the file specified in S101 by the acquired number of owners before the operation (S201). When the operation is “register file”, there is no file information before the operation, so the file size per owner before the operation is set to zero.

  For example, since the current owner of the file ID “F004” is “userB” and “userC”, the number of owners is “2”. The file size “107,890” (bytes) of the file ID “F004” is divided by the number of owners “2”, and the file size per owner is calculated as “53,945” (bytes).

  The file information processing unit 112 acquires the number of owners after the operation of the file specified in S101. The file information processing unit 112 calculates the file size per owner by dividing the file size of the file specified in S101 by the acquired number of owners after the operation (S202).

  For example, since the owner after the operation of the file ID “F004” is only “userC”, the number of owners is set to “1”. The file size “107,890” (bytes) of the file ID “F004” is divided by the number of owners “1”, and the file size per owner is calculated as “107,890” (bytes).

  For the file specified in S101, the file information processing unit 112 reflects the file size per owner calculated in S201 and S202 on the used size of each owner. The used size is calculated (S203).

  For example, the used size of the user information “userC” before the operation is “53, 990” (bytes). The file size “53,945” (bytes) per owner before operation is subtracted from the used size “53,990” (bytes), and the file size “107,890 per owner after operation” is subtracted. “(Byte)” is added to “107, 935” (byte). In other words, the used size increases from “53, 990” to “107, 935”.

  The file information processing unit 112 determines whether or not there is an owner whose used size after the operation exceeds the permitted use size (S204).

  When S204 is satisfied (S204, Yes), the process proceeds to S206. The file information processing unit 112 cancels the operation (S206). Specifically, the file information processing unit 112 notifies the file work processing unit 142 that the file cannot be operated, and the file work processing unit 142 notifies the user that the file cannot be operated. . The notified user, for example, executes the process from S101 again after the owner whose used size exceeds the permitted use size is no longer the owner of the file.

  When S204 is not satisfied (S204, No), the process proceeds to S205. For example, since the used size “107, 935” of the user “userC” is smaller than the permitted use size “52, 428, 800” (S204, No), the process proceeds to S205. The file information processing unit 112 updates the used size of the owner to the value after the operation calculated in S203 for the file specified in S101 (S205).

  FIG. 6 is a flowchart showing processing for prohibiting access to a file based on the counter. An example in which the file ID “F004” is determined will be described.

  The file information processing unit 112 acquires the determination condition of the determination condition management table 103 for each file of the file information management table 102 (S301). For example, the file information processing unit 112 acquires from the determination condition management table 103 that “there is no owner” that is the determination condition “C003” of the file ID “F004” of the file information management table 102.

  The file information processing unit 112 determines whether the file information in the file information management table 102 satisfies the acquired determination condition (S302). For example, since the owner of the file ID “F004” in the file information management table 102 is “userC”, the determination condition “no owner” is not satisfied, so the file with the file ID “F004” is still is needed.

  On the other hand, the file information processing unit 112 may determine whether the information in the work history management table 176 satisfies the acquired determination condition (S302). For example, if the property of the determination condition indicated by the condition ID “C001” is “work history” and the value thereof is “the current date and time and the last reference date are 30 days or more”, the work history management unit 172 selects the work history management table. The contents of 176 are checked to determine whether the current date and time and the last referenced date are 30 days or more.

  When the determination condition is satisfied, the file information processing unit 112 sets “unnecessary” to the determination flag of the file that satisfies the determination condition of the file information management table 102, and adds “1” to the counter of the determination condition management table 103. To update each (S303).

  The file information processing unit 112 refers to the determination condition management table 103 and determines whether there is a counter exceeding the upper limit value (S311). For example, the counter “21” of the condition ID “C002” in the file information management table 102 exceeds the counter upper limit value “20”. When there is a counter exceeding the upper limit (S311, Yes), the process proceeds to S312. When there is no counter (S311, No), the process ends.

  The file information processing unit 112 sets a file using the counter determination condition exceeding the upper limit as a file to be prohibited from access, and acquires file information of the file (S312). Then, the file information processing unit 112 prohibits access to the file (S313). The file using the determination condition of the condition ID “C002” is the file ID “F003”. Access is prohibited by “move this file to the destination”.

  Specifically, the access prohibition processing unit 152 refers to each table by using the file ID “F003” as a key, so that the file corresponding to the file ID “F003” is stored in the disk ID “D012”. And that the file C is moved to the destination path “D: ¥ source ¥ files” indicated by the disk ID “D001” and compressed. The access prohibition processing unit 152 moves the file to the destination according to the recognition and compresses the file.

  Note that files with the judgment flag “unnecessary” are moved to the destination and compressed, but not only the file data, but also work history information indicating the work history performed on the file. It is good also as compressing. Further, it may be configured such that a user who has worked in the work history is notified by mail of the fact that the file has been moved and compressed in cooperation with a mail system or the like and the destination of the file.

  The file information processing unit 112 deletes the file information of the file whose access is prohibited from the file information management table 102 (S314). Specifically, the file information processing unit 112 deletes the file information corresponding to the file ID “F003” in the file information management table 102. Then, the file information processing unit 112 initializes the counter of the determination condition “C002” that executed the access prohibition of the determination condition management table 103 to “0” (S315).

  FIG. 7 is a flowchart showing processing for displaying a file list as work on a file.

  The file information processing unit 112 that has received the file list display request from the file display processing unit 162 acquires the file information in which the user who displays the file is the owner or the worker from the file information management table 102 (S401).

  For example, in order to display the file “userD”, the file information processing unit 112 searches for “owner” and “worker” in the file information management table 102 using “userD”, and sets the file IDs “F001, F002”. F003 "file information is acquired.

  The file display processing unit 162 determines whether or not a work deadline for the acquired file information is set (S402). When the work deadline is not set (S402, No), the process of S405 is executed. For example, the file ID “F003” in the file information acquired in S401 is determined to be information for which a work deadline is set.

  If Yes in S402, the file information processing unit 112 determines whether the difference between the current date and time and the work deadline is within one day (S403). If it is not within one day (S403, No), the process of S405 is executed. For example, the file display processing unit 162 determines that it is within one day since the date and time to display is July 28, 2006, 09:00.

  If Yes in S403, the file display processing unit 162 displays a dialog indicating that the work deadline is within one day (S404). For example, when displaying the file with the file ID “F003”, the file display processing unit 162 displays a dialog indicating that the work deadline is within one day.

  Then, the file display processing unit 162 displays the file of the file information acquired in S401 (S405).

  In addition, when the file display processing unit 162 displays a file, it notifies that it is within one day, but in cooperation with the mail system or the like, if a file within one day is detected, It is good also as a structure notified by e-mail.

  FIG. 8 is a flowchart showing processing for referring to a file as work on the file. Hereinafter, an example of displaying “file B” will be described.

  The file display processing unit 162 accepts a work for referring to a file from the user, searches for a file ID in the file information management table 102, and obtains file information on the work target. Then, the file display processing unit 162 requests the file work processing unit 142 to refer to the file indicated by the file ID. The file work processing unit 142 displays the file (S501).

  Specifically, the file display processing unit 162 acquires the file information of the file information management table 102 corresponding to the file ID “F002” of “file B” that the user has worked on. Then, the file display processing unit 162 requests the file work processing unit 142 to refer to the file indicated by the file ID “F002”. The file work processing unit 142 displays a file.

  The work history confirmation unit 172 registers the work target file ID, work date and time, user ID, and work contents as work history information in the work history management table 176 as the work history of the file (S502). For example, the work history confirmation unit 172 registers the file ID “F002” to be worked, the work date and time “August 5, 2006 19:13:21 356”, the user ID “userD”, and the work content “reference”. .

  The file information processing unit 112 determines whether the worker of the file information management table 102 acquired in S501 matches the user who has worked on the file (S503). If they do not match (S503, No), the process ends.

  More specifically, when “userB” works on a file with the file name “file B”, the file information processing unit 112 indicates “userB” working on the file and the file ID “F002” of the file information management table 102. It is determined that the worker “userB” matches.

  In the case of Yes in S503, the file information processing unit 112 determines whether or not the work content of the file information management table 102 acquired in S501 matches the work content of the file (S504). If they do not match (S504, No), the process ends. Specifically, the work of “userB” is “reference”, and the file information processing unit 112 compares the work content “reference” of the worker “userB” acquired in S501 and determines that they match. .

  In the case of Yes in S504, the file information processing unit 112 deletes the worker determined in S504 and the work content from the file information management table 102 (S505). For example, the file information processing unit 112 deletes information on the worker “userB” and the work content “reference” in the file information.

  Hereinafter, screens displayed by the shared file management system of this embodiment will be described with reference to the drawings.

  FIG. 9A is a file list screen of userA. Clicking “Register” opens the screen shown in FIG. When “information” is clicked, a setting screen is opened with the screen layout of FIG. Clicking “Archive” opens the screen of FIG. The “folder” column is displayed by sorting by folder. The “file name” column displays a file list. The “role” column displays the role of the user corresponding to the file.

  FIG. 9B is a file information setting screen of “a.doc”. The “category” tab displays users classified according to their organization. Check the users you want to add as owners or workers. In the “search” tab, a user is searched from a keyword, and a user to be added to an owner or a worker is checked from a search result. FIG. 9D shows an example in which the “Search” tab is activated. When “add” in FIG. 9B is clicked, the user checked in the “classification” tab or the “search” tab is added to the “owner or worker editing area”.

  The “owner or worker edit area” column in FIG. 9B is a column for setting work, role, and time limit for each user. The “user” column displays the added user name. In the “work” column, work corresponding to the user is set in a pull-down menu. In the “role” column, a role corresponding to the user is set by pull-down. In the “Time Limit” field, a time limit for the user's work is set. When “Setting” is clicked, the screen of FIG. 9C is opened. FIG. 9C shows a calendar screen. Set the clicked date as the deadline.

  When “other file information” in FIG. 9B is clicked, the screen in FIG. 9A opens. When a registered file is selected, the same information as the file information of the file is displayed in the screen in FIG. 9B. Set to Clicking “OK” sets the specified file information. Click “Cancel” to close this window without setting the specified file information.

  FIG. 10A shows a file registration screen for registering a file “a.doc”. After registration of the file, this screen is displayed by changing the display items with the same layout as the screen name of the file setting screen. The items displayed for registration and setting will be described below.

  The “location” column in FIG. 10A displays a file to be registered (at the time of registration) or a registered file name. Clicking "Select" opens a screen for selecting a file from the user's local disk. Note that “Select” is not displayed after file registration. The “file information” column displays a list of set owners and operators. When “Setting” is clicked, the screen of FIG. 9B is opened.

  The “judgment condition” column in FIG. 10A displays the judgment condition name to be set. When the downward triangle icon on the right of the judgment condition name is clicked, the screen of FIG. 10B is displayed in this screen. When the screen of FIG. 10B is displayed, the “upward triangular icon” is displayed. When the “upward triangular icon” is clicked, the screen of FIG.

  The “operation when the determination condition is satisfied” field in FIG. 10A is selected in a pull-down format. The “movement destination” column displays the name of the movement destination. When the downward triangle icon on the right of the destination name is clicked, the screen of FIG. 11B is displayed in this screen. When the screen of FIG. 11B is displayed, the “upward triangular icon” is displayed, and when the “upward triangular icon” is clicked, the screen of FIG. 11B is not displayed.

  When “Register” in FIG. 10A is clicked, the file information is registered with the specified information. Clicking “Cancel” closes the screen without registering the file information.

  FIG. 10B is a determination condition list screen. Judgment conditions are classified for each property, and the values that the property can take are selected and displayed. When the check box on the right of each condition is checked and the “OK” button is clicked, the determination condition is set. Each determination condition name is an anchor, and when clicked, the screen in FIG. 11A is opened. Also, by dragging the icon of each determination condition name and dropping it on the file name in the file list, the determination condition can be set in the file.

  FIG. 11A is a determination condition setting screen. In the “Condition name” field, a judgment condition name is entered. The “Information as condition” column is selected from a pull-down menu. In the “condition value” column, a condition value corresponding to information to be used as a condition is selected from a pull-down menu. In addition, the value of this item changes according to the information used as conditions. For example, when “work history” is selected as the condition information, the condition values such as “no access for 30 days or more” and “no access for 20 days or more” are selected, and “work deadline” is selected as the condition information. In this case, “work deadline is 1 day passed”, “work deadline is 2 days passed”, etc.

  “Counter upper limit value” in FIG. 11A specifies a counter upper limit value. “Register” registers the determination condition with the specified information. “Cancel” closes the screen without registering the determination condition.

  FIG. 11B is a movement destination setting screen. Display a list of destinations. When the check box to the right of each destination is checked and the “OK” button is clicked, the destination is set.

It is explanatory drawing which shows the outline | summary of the file sharing regarding one Embodiment of this invention. It is a block diagram which shows the shared file management system regarding one Embodiment of this invention. It is explanatory drawing which shows the relationship between a process part and a table in the shared file management system regarding one Embodiment of this invention, and the flow of control. It is a block diagram which shows the file information management table regarding one Embodiment of this invention. It is a flowchart which shows operation to the file information regarding one Embodiment of this invention. It is a flowchart which shows the process which prohibits access to a file based on the counter regarding one Embodiment of this invention. It is a flowchart which shows the process which displays a file list as an operation | work to the file regarding one Embodiment of this invention. It is a flowchart which shows the process which refers a file as an operation | work to the file regarding one Embodiment of this invention. It is a screen figure which shows the file list screen regarding one Embodiment of this invention. It is a screen figure which shows the file registration screen regarding one Embodiment of this invention. It is a screen figure which shows the determination condition setting screen regarding one Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 102 File information management table 103 Judgment condition management table 104 Moving destination management table 105 User information management table 106 Shared file system management part 112 File information processing part 122 Judgment condition confirmation part 142 File work process part 145 File management part 152 Access prohibition process part 155 Destination file management unit 162 File display processing unit 172 Work history confirmation unit 175 Work history management unit 176 Work history management table

Claims (5)

A shared file management method for sharing files by each user becoming a file owner,
Computer
Stores the ownership relationship between the file and the owner, and the determination condition for determining whether each owner needs the file in the storage unit,
Based on the determination condition, determine whether or not a file is required for each owner having the ownership relationship, referring to the storage unit,
A shared file management method, wherein access is prohibited for a file for which there is no owner who needs the file according to the determination result of the determination.   The step of prohibiting access includes prohibiting access to the file by executing processing for deleting the file, processing for moving the file to the destination, or processing for moving and compressing the file to the destination. The shared file management method according to claim 1, wherein:   The determination condition is defined by a set of a property and a value that can be taken by the property, and when a property is selected, a display screen having an input means for selecting a candidate of a value that can be taken by the selected property is displayed. The shared file management method according to claim 1 or 2.   A shared file management program for causing a computer to execute the shared file management method according to any one of claims 1 to 3. A shared file management device for sharing a file by each user becoming a file owner,
A storage unit that stores an ownership relationship between the file and the owner, and a determination condition for determining whether or not each owner needs the file;
Based on the determination condition, a determination condition confirmation unit that determines whether or not a file is required for each owner having the ownership relationship with reference to the storage unit;
According to the determination result of the determination condition confirmation unit, an access prohibition processing unit that prohibits access to a file that does not have an owner that requires the file;
A shared file management apparatus comprising:

Images