JP4400254B2 - File management apparatus and file management program - Google Patents

Description

  The present invention relates to a file management system, method, and program for managing a file with a binder in which a plurality of files are bundled. In particular, the present invention enables access in a group unit to a binder in which a plurality of files are bundled. In particular, the present invention relates to a file management system, method, and program that enable multiple exclusive control in which exclusive control is performed on a file constituting a binder by a user belonging to a group that can access the binder.

  Generally, when a file is edited by a plurality of people, exclusive control is performed so that a plurality of users do not edit the file at the same time. Users other than this user cannot operate the corresponding file for which exclusive control is being performed. Even if the operation is permitted, updating / deleting, etc. cannot be performed, and it is limited to referencing.

  For this reason, while one user is editing, other users cannot edit, so the editing efficiency, operability, and interoperability cannot be satisfied.

  In view of this, there is a technique disclosed in Japanese Patent Application Laid-Open No. 2004-151620 as a prior art that allows partial editing control of a file to be edited and enables one person to edit one file.

  In the prior art disclosed in Patent Document 1, it is possible to maintain the consistency of information between the partial area of the editing target file to be changed and the related partial area not to be changed at the time of editing work.

  Further, as a conventional technique that enables exclusive control in units of pages, there is one disclosed in Patent Document 2.

In the prior art disclosed in Patent Document 2, the management apparatus can also notify all editing apparatuses that have opened the document file of information associated with the update.
JP 06-12310 A JP 08-16553

  However, in the prior art disclosed in Patent Document 1, there is a problem in that no restriction can be imposed on a document part that is not subjected to exclusive control, and anyone can perform editing.

  Further, the conventional technique disclosed in Patent Document 2 has a problem that no page can be restricted at all for a page that is not subjected to exclusive control, and anyone can edit it.

  Therefore, according to the present invention, the file is managed by the binder composed of a plurality of files, so that the exclusive control can be performed on the group to which the user belongs even if the user does not perform the exclusive control on the binder. In other words, even if the user does not intentionally perform exclusive control, the shared document in the binder can be controlled exclusively by users belonging to the group that exclusively controlled the binder, and exclusive control can be performed. The user can now perform exclusive control on the files that make up the controlled binder.

A file management apparatus and a file management program that can not only prevent editing by an unintended user but also improve operability when operating a file in cooperation with improvement of work efficiency. The purpose is to provide.

In order to achieve the above object, a first aspect of the present invention relates to a file management apparatus that manages a file with a binder in which a plurality of files are bundled, and associates a group ID for identifying a group to which a plurality of users belong to the binder. each file bundled by the binders exclusion and exclusion means for exclusive operations on each file bundled by the binders according to the user other than the user belonging to the group identified by the group ID, by the exclusive means by The file exclusive means owned by one user belonging to the group and the one user dedicated by the file exclusive means cancel the exclusive use of the file so that other users belonging to the group cannot operate File exclusive release means and the file An operation by a user belonging to a group other than the group identified by the group ID for each file bundled by the binder because all the files bundled by the binder are released by the exclusive release by the exclusive release means And an exclusive release means for enabling

According to a second aspect of the present invention, in the first aspect of the invention, the file exclusive means excludes the binder by the exclusive state confirming means for confirming the exclusive state of the file by the user and the exclusive means. A group ID obtaining unit for obtaining a group ID for identifying a group, and when the exclusive unit confirms the file bundled with the binder exclusive by the group, the exclusive state confirmation unit confirms the file The file is in a state in which the file has been released due to the exclusive state , and another user who wants to exclusively use the file belongs to a group identified by the group ID acquired by the group ID acquisition unit The file is exclusively used .

The invention according to claim 3 is the invention according to claim 1, wherein all files bundled by the binder exclusive by the group by the exclusion means are released exclusively by the file exclusive release means. characterized by including a version control means for versioning.

According to a fourth aspect of the present invention, a user belonging to a group identified by the group ID is obtained by associating a computer with a group ID identifying a group to which a plurality of users belong to a binder in which a plurality of files are bundled. Exclusion means for excluding operations on each file bundled by the binder by a user other than the above, so that other users belonging to the group cannot manipulate the operations of each file bundled by the binder exclusive by the exclusion means File exclusive means exclusive to one user belonging to the group, file exclusive release means for releasing exclusive use of the file by the one user exclusive to the file exclusive means, and the binder by releasing exclusive use of the file exclusive release means All bundled by By the file is released exclusively to function as an exclusive release means which can be operated by the user in the group other than the group identified by the group ID for each file bundled by the binder.

  According to the present invention, multiple exclusive control is performed such that exclusive access in units of groups is possible for a binder in which a plurality of files are bundled, and only users belonging to the group can exclusively access files that constitute the binder. As a result of this configuration, editing of multiple files that make up the binder can be performed in parallel by a limited number of users, and file versions can be managed by users editing files in the binder. The effect of becoming.

Hereinafter, an example based on an embodiment of a file management apparatus and a file management program according to the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a diagram showing a configuration of a file management system configured by applying a file management apparatus and a file management program according to an embodiment of the present invention.

  1, the file management system includes a client 100 that edits a file, a file control server 110 that performs exclusive control on a file that is edited by the client 100, and a file management database 120 that manages the file. Is done.

  In the file control server 110, an interface 111 that receives a file acquisition request from the client 100, a control unit 112 that controls the file, and a binder including a plurality of files are checked out in units of groups including a plurality of users. Binder control unit 113, group configuration in which binder is checked out for a plurality of files in the checked out binder File control unit 114 that allows user to exclusively lock and unlock, group in which binder is checked out Version management unit 115 that manages the version when the file is locked out by the configuration user of the file, locked by the configuration user of the group that checked out the configuration file of the binder that is exclusively controlled A detection unit 116 that detects a state, a table access unit 117 that accesses a table on the file management database 120 to check whether the binder or file can be exclusively controlled, and a file access unit 118 that accesses a real file to be exclusively controlled. It comprises.

  In the file management database 120, a file table management unit 121 that manages the lock state of a file as a database table, a binder table management unit 122 that manages a check-out state of a binder as a database table, and a user belonging to the checked-out group And a file storage unit 123 for storing files to be stored.

  Here, in response to the file acquisition request from the client 100, the file control server 110 checks the file control unit 114 in the control unit 112 in order to confirm whether the user has the access right to the file requested by the user. To the file table management unit 121 via the table access unit 117.

  In the file table management unit 121, the binder table management unit 122 confirms whether or not the binder of which the file is a component is checked out by the group to which the user who issued the acquisition request belongs, and performs the above check-out. If the requested file is not locked by another user, the file table management unit 121 permits the lock. If the file requested by the user is checked out by a group other than the group to which the user belongs, the file cannot be edited until it is checked in.

  Then, the file edited by the user is unlocked, and the check-in can be performed only when all of the binder configuration files that have been checked out are unlocked. As a result, version management can be performed in units of files by the user, and version management can be performed in units of binders by group.

FIG. 2 is an image diagram showing a file management process performed in a file management system configured by applying the file management apparatus and the file management program according to the embodiment of the present invention.

  In FIG. 2, a binder 200 that bundles a plurality of files that are not checked out, a file 201 (file 1), a file 202 (file 2), and a file 203 (file 3) grouped together by the binder. The binder 210 in the checked-out state of the binder 200 is shown.

  For example, the user A locks the file 201 (file 1) against the file 201 (file 1), file 202 (file 2), and file 203 (file 3) in the checked-out binder 210 (state 211). Subsequently, in a state where the file 202 (file 2) is locked by the user B (state 213), the file A (file 1) previously locked out is unlocked by the user A (state 212). 2) is a state in which the user B has unlocked (state 214) and the file 203 (file 3) has not been processed, and when all the constituent files of the binder are not locked. As long as the check-in of the binder is done by the checked-out group It is shown that it is.

FIG. 3 is a diagram (E-R diagram) showing a relationship between tables in a file management system configured by applying the file management apparatus and the file management program according to the embodiment of the present invention.

  FIG. 3 shows the relationship among the binder entity 301, the group entity 302, the file entity 303, and the user entity 304.

  In the example illustrated in FIG. 3, the binder entity 301 has “binder ID, binder name, creation date, creator, checkout flag, checkout group, remarks” as attributes. Further, the attribute indicates that the binder ID is a primary key.

  Further, the file entity 303 has “file ID, file name, lock flag, user ID, binder ID, checkout flag, group ID, remarks” as attributes, and indicates that the file ID is a primary key. The binder ID and the group ID are external keys.

  At this time, the relationship between the binder entity 301 and the file entity 303 has a “one-to-many” relationship. Exclusive control is realized by relating entities. Of course, in order to promote normalization of the table structure, the file entity 303 re-checks the checked-out state of the file in the binder entity 301 without holding the checkout flag or the group that has been checked out as an attribute. It may be configured.

FIG. 4 is a sequence diagram showing an example of binder access processing performed in the file management system configured by applying the file management apparatus and the file management program according to the embodiment of the present invention.

  FIG. 4 shows an example of a procedure for accessing the files A and B in the binder 1 from the users 1 and 2 belonging to the group A. In the example shown here, a checkout request (S401) is made to the binder 1 in which files are bundled by the group A, and the binder 1 that has received the checkout request confirms whether or not the checkout can be permitted. A confirmation process (S402) is performed on the binder table in which the check-out state is recorded.

  In the binder table, it is confirmed whether the requested binder 1 is in a state where the check-out can be permitted, and a response (S403) is returned to the binder 1. In response to the result, the binder 1 permits check-out to the group A (S404) and performs check-out.

  User 1 or user 2 belonging to group A makes a lock request (S405) to file A or file B in binder 1 because binder 1 is checked out, and checks by group A that has received the lock-out request. The file A in the binder 1 that has been checked is confirmed in the file table whether the lockout can be permitted (S406). In the file table, it is confirmed whether the lock can be permitted for the user 1 belonging to the group A (S407). )

  At this time, since the attribute of the file entity 303 in the ER diagram shown in FIG. 3 is configured to have a checkout flag indicating the checkout state and a group ID for identifying the group executing the checkout, Since it is not necessary to check the checkout state from the file table of the process of FIG. 4 to the binder table, the processing speed can be improved. Of course, it may be configured to promote normalization of the table structure in order to eliminate data redundancy and to ensure data consistency and consistency.

  Then, upon receiving the checkout permission response result, the file A permits the user 1 to lock out and locks (S408). By performing the above processing, the user 1 belonging to the group A can edit the file A in the binder 1.

  In addition, when the group B similarly requests a checkout process for the binder 1 in which the group A is in the checkout state by the above processing (S409), the binder 1 confirms whether the binder table is in a state where the checkout can be permitted. (S410) Since the binder table indicates that the checkout is performed by the group A, a response (S411) including the fact is sent to the binder 1 that has been confirmed. Upon receiving the response, the binder 1 rejects the checkout for the group B (S412).

  Therefore, the user 3 or the user 4 belonging to the group B cannot access the file A or the file B in the binder 1 by the exclusive lock that does not permit the reference as well as the update. At this time, a shared lock that cannot be updated but allows reference may be applied.

FIG. 5 is a sequence diagram showing an example of file access processing performed in the file management system configured by applying the file management apparatus and the file management program according to the embodiment of the present invention.

  FIG. 5 shows a processing example when the lockout request is directly sent to the document A before the group A to which the user 1 belongs performs the checkout process on the binder 1. Here, when the user 1 belonging to the group A directly sends a lock request (S501) to the file A in the binder 1, the file A confirms whether or not the user A can access the user 1 (S502). )I do.

  In the file table, when the check-out flag is blank due to the first access to the file A or the like, it is confirmed on the binder table whether the check-out is performed for the binder 1 that the file A configures (S503). Do.

  The binder table responds to the file table (S504), and returns a response (S505) from the file table to file A based on the result.

  In the file A, after confirming with the file table or the binder table, a lock response is made to the accessing user 1 (S506).

  Next, file management of this file management system will be described.

FIG. 6 is a flowchart showing a process of locking a file by a file management system configured by applying the file management apparatus and the file management program according to the embodiment of the present invention.

  In FIG. 6, the process is started when the user locks the binder configuration file, and it is determined whether the file to be locked is in a locked state (step 601). If the file is locked (YES in step 601). An error is displayed (step 608).

  If it is not locked (NO in step 601), the checkout state of the binder that bundles the files is acquired (step 602), and it is determined whether the binder is in the checkout state (step 603). If not (NO in step 603), an error is displayed (step 608). If it is in the checkout state (YES in step 603), the group or user that has checked out the binder is acquired (step 604).

  It is determined whether or not the binder is checked out in units of groups (step 605). If the group is not checked out (NO in step 605), an error is displayed (step 608).

When checking out in units of groups (YES in step 605), it is determined whether the user who locks the configuration file is included in the checked out group (step 606). If not (NO in step 606), an error is displayed (step 608). If the user is included in the group (YES in step 606), the process ends.

  These processing flows allow the user to lock the file.

  FIG. 7 is a flowchart showing the processing at the time of executing the check-in of the binder according to the present invention.

  In FIG. 7, the processing is started when the user checks in the binder, and the following processing (step 701 to step 704) is looped as many times as the number of the relevant binder configuration file in order to confirm the lock state of the file (step 701). ).

  The configuration file status of the binder is acquired (step 702), and it is determined whether the configuration file is locked (step 703). If the configuration file is locked (YES in step 703), the binder is checked. An error display to the effect that it cannot be performed is performed (step 706), and the process is terminated. If not in the locked state (NO in step 703), the process transitions to the next file.

FIG. 7 is a flowchart showing a flow of processing at the time of check-in of the binder in the file management system configured by applying the file management apparatus and the file management program according to the embodiment of the present invention.

  Through the above processing, in the file management system of the present invention, exclusive control can be performed on a binder composed of a plurality of files by a group to which a plurality of users belong, and exclusive control is performed on the files in the binder. Only users who belong to a group can perform exclusive control.

  In addition, after confirming the lock state of all users, the version can be managed by checking in the binder.

  This makes it possible for only a limited number of users to operate a binder consisting of multiple files, and denies access from users who do not belong to the group that checked out the binder without performing exclusive control on their own. Is possible.

  Therefore, by applying the present invention, it is possible to expect the effect that the editing of individual files constituting the binder can be performed in parallel while limiting the users who edit the target file. After confirming the lock state, by checking in the binder, it is possible to specify the location edited by the user, and the effect of improving the editing efficiency can be expected.

  The processing shown in the flowcharts of FIGS. 6 and 7 can also be realized by a file management program that can be executed by a computer.

  The present invention is not limited to the embodiments described above and shown in the drawings, and can be implemented with appropriate modifications within a range not changing the gist thereof.

  For example, in the above embodiment, the table structure is as shown in FIG. 3, but a plurality of table structures are provided for the purpose of improving processing efficiency and improving maintainability and productivity. It may be formed or constituted by one table structure.

  Moreover, although it has comprised so that a user may belong only to a specific group by hold | maintaining only one belonging group ID in the user entity of FIG. 3, it comprises so that a user may belong to several groups simultaneously, The relationship with the group entity may be a “many-to-many” relationship.

  The present invention can be applied to a file management system that performs simultaneous execution control (exclusive control) when a plurality of users edit a file at the same time, and can perform exclusive control in units of a group consisting of a plurality of files. Furthermore, since the group configuration user who can edit the binder can also perform exclusive control on the binder configuration file, the binder configuration file can be edited in parallel only by the group configuration user. It is effective for.

The figure which shows the structure of the file management system which applies and comprises the file management apparatus and file management program in embodiment of this invention. The image figure which shows the file management process performed with the file management system comprised by applying the file management apparatus and file management program in embodiment of this invention. The figure which shows the relationship between the tables in the file management system comprised by applying the file management apparatus and file management program in embodiment of this invention (E-R figure). The sequence diagram which shows an example of the binder access process performed with the file management system comprised by applying the file management apparatus and file management program in embodiment of this invention. The sequence diagram which shows an example of the file access process performed with the file management system comprised by applying the file management apparatus and file management program in embodiment of this invention. The flowchart which shows the process which locks a file with the file management system comprised by applying the file management apparatus and file management program in embodiment of this invention. The flowchart which shows the flow of a process at the time of the check-in execution of the binder in the file management system comprised by applying the file management apparatus and file management program in embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Client 110 File control server 111 Interface 112 Control part 113 Binder control part 114 File control part 115 Version management part 116 Detection part 117 Table access part 118 File access part 120 File management database 121 File table management part 122 Binder table management part 123 File Storage unit 200 Binder before checkout 201 Binder configuration file 1
202 Binder configuration file 2
203 Binder configuration file 3
210 Checked Out Binder 301 Binder Entity 302 Group Entity 303 File Entity 304 User Entity

Claims (4)

In a file management device that manages files with a binder that bundles multiple files,
By associating a group ID for identifying a group to which a plurality of users belong to the binder, an operation on each file bundled by the binder by a user other than the user belonging to the group identified by the group ID is excluded. Exclusion means,
A file exclusive means dedicated to one user belonging to the group so that other users belonging to the group cannot operate the operations of the files bundled by the binder exclusive by the exclusive means;
File exclusive release means for releasing exclusive use of the file by the one user exclusive to the file exclusive means;
A user who belongs to a group other than the group identified by the group ID for each file bundled by the binder because all the files bundled by the binder are released by the exclusive release by the file exclusive release means. A file management apparatus comprising: an exclusive release unit that enables an operation according to . The file exclusive means is:
Exclusive state confirmation means for confirming the exclusive state of the file by the one user;
Group ID acquisition means for acquiring a group ID for identifying a group that excludes the binder by the exclusion means;
Comprising
When the file bundled by the binder exclusive by the exclusive means is exclusively used, the file is in a state where the exclusive release is confirmed by the exclusive state of the file confirmed by the exclusive state confirmation means , and the file is exclusively used. 2. The file management apparatus according to claim 1 , wherein the other user is a user belonging to a group identified by the group ID acquired by the group ID acquisition means, and occupies the file. Version management means for performing version management of the binder when all the files bundled by the binder exclusive by the group by the exclusion means have been released exclusively by the file exclusive release means
The file management apparatus according to claim 1 , further comprising: Computer
Each file bundled by the binder by a user other than the user belonging to the group identified by the group ID by associating the group ID identifying the group to which the plurality of users belong to the binder bundled with the plurality of files. Exclusion means to exclude operations on,
A file exclusive means exclusively owned by one user belonging to the group so that other users belonging to the group cannot operate the operations of the files bundled by the binder exclusive by the exclusive means;
File exclusive release means for releasing exclusive use of the file by the one user exclusive to the file exclusive means;
A user who belongs to a group other than the group identified by the group ID for each file bundled by the binder because all the files bundled by the binder are released by the exclusive release by the file exclusive release means. Means for releasing exclusion
File management program to function as .

Images