JP2007011844A - File sharing system, file sharing method, and file sharing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a file sharing system, a file sharing method, and a file sharing program for transferring file ownership authority between users in accordance with the usage status on a file sharing service.
SOLUTION: File access frequency is managed as a history on a file sharing service, and the owner authority is accessed when a transfer condition set in advance between a user with ownership authority and a user with high access frequency is satisfied. A file sharing system, a file sharing method, and a file sharing program, which are transferred to a high-frequency user.
[Selection] Figure 3

Description

  The present invention relates to a file sharing system, a file sharing method, and a file sharing program for sharing a document file among a plurality of users.

Although sharing electronic document files is widespread, there is a growing need for ensuring security and there is a demand for finely maintaining access rights for individual files. However, as the use scale of file sharing increases, the maintenance load also increases, and a function for changing access authority in a batch to reduce the load has been proposed (for example, see Patent Document 1).
JP 2004-21450 A

  However, in many cases, it is necessary to change the access authority according to the usage status of each file, not for each file.

  There are many systems in which a new creator of a file automatically has file owner authority and is given file operation authority that can only be obtained by owner authority. For example, in a standard initial setting in many UNIX (registered trademark) OS environments, only the owner has the write authority, and only the read authority is given to the user group to which the owner belongs and further to the third party. Furthermore, the change of authority is restricted so that only owners or users with administrator authority can make changes.

  In such a file sharing system, the owner himself / herself does not recognize the necessity, but other users may desire to change the access authority. For example, when a supervisor uses a material file created by a subordinate, it is a common situation that minor corrections and modifications are required over time. Awareness that it is not enough to ask the subordinates or system administrators who are the owners of the file works, and it is often taken as a workaround to make a copy of the file and modify the copy.

  If such duplication is performed in a disorderly manner, the significance and effectiveness of managing access rights are lost in the first place, document management such as update management and version management cannot be performed, and there is a problem that the storage area is wasted. However, the operation of changing the access authority must be performed by the owner of the file, which is not required, and there is a problem that the load on the owner is increased.

  In order to solve the above-described problems, the present invention provides a file sharing system and file sharing that transfer file owner authority according to the usage status of the file without increasing the load on the file owner or system administrator. It is an object to provide a method and a file sharing program.

In order to solve the above problems, the present invention provides:
A file sharing means for realizing a file sharing service;
A history management means for collecting, storing, searching, and acquiring file access history on the file sharing service,
A file sharing system with
A means for storing user information accessed when a file is accessed in a history;
Means for obtaining access frequency information of the accessed file from the history management means;
Means for comparing and determining the acquired access frequency information based on a preset condition;
Means for transferring ownership of the file based on the determination result;
Or a means for notifying a plurality of users to transfer ownership authority, and granting the authority to change ownership of the file to the plurality of users only for a preset period;
Means for clearing access frequency information of the file;
Consists of

  According to the present invention, in the electronic document file sharing system, when a user who has the authority to own a file and a user who frequently uses the file deviate over time, the ownership right of the file is the current main use. File owners and system administrators are transferred without the involvement of the original owner or system administrator, so that file ownership and associated management rights are transferred to the appropriate user without increasing the load on the original owner or administrator. .

  In addition, when multiple users use it more frequently than the owner, candidates for transfer of ownership are shown to the system administrator, owner, and top multiple users, and transfer of ownership for a limited time When the authority is given, it is possible to determine the transfer destination between the parties without transferring to the system administrator and transfer the transfer destination.

  As a result, file ownership and management rights are always transferred to appropriate users without increasing the load on users and administrators in the entire file sharing system, and security is maintained by maintaining appropriate access rights. Can be maintained, and secondary effects such as optimization of document management and reduction of waste of storage capacity can be obtained.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a system configuration diagram of a file sharing system suitable for implementing the present invention.

  The file sharing server 100 and the clients 130a and 130b are connected to each other via the network 150.

  The server 100 and the clients 130a and 130b are each configured by an information processing device (computer). Details of each will be described later. The clients 130a and 130b have the same configuration, and are collectively referred to as the client 130 when it is not necessary to explicitly distinguish them. Further, depending on the usage pattern, the client 130a or 130b may be separated from the client 130a. Conversely, the server 100 may divide the function and configure the function with a plurality of information processing apparatuses.

  The network 150 includes a plurality of routers, switches, cables, and the like that satisfy a communication standard such as Ethernet (registered trademark). In the present invention, any communication standard, scale, and configuration can be used as long as communication between servers and clients can be performed without any problem. Therefore, the present invention can be applied from the Internet to a LAN (Local Area Network).

  FIG. 2 is a detailed block diagram of an information processing apparatus (computer) suitable for the server 100 and the client 130 described above.

  A CPU 200, a primary storage device 210, a secondary storage device 220, a user input / output I / F 230, and a network I / F 250 are connected to each other via an internal bus 260.

  Here, the primary storage device 210 is a high-speed writable storage device represented by a RAM, and is loaded with an OS, various programs, and various data, and is also used as a work area for the OS and various programs.

  The secondary storage device 220 is a non-volatile storage device represented by FDD, HDD, flash memory, CD-ROM drive, etc. In addition to being used as a permanent storage area for the OS, various programs, and various data. It is also used as a storage area for various short-term data. Details of various programs and the like placed in the primary storage device 210 and the secondary storage device 220 of the server 100 and the client 130 will be described later.

  The user input / output I / F 230 is an I / F for connecting a user input / output device 240 represented by a display, a keyboard, a mouse, and the like. In the server 100, the user input / output I / F 230 and the user input / output device 240 are not essential.

  A network I / F 250 is an I / F for connecting to the above-described network 150 and is responsible for communication with other information processing apparatuses via a communication medium such as Ethernet (registered trademark).

  FIG. 3 shows details of various programs and the like placed in the primary storage device 210 and the secondary storage device 220 of the file sharing server 100 (the CPU 200 and the like are not shown).

  Here, the OS 300, the HTTP server 310, the file sharing management program 320, and the history management program 330 are loaded on the primary storage device 210, and the electronic document file 340 to be shared by the user is stored on the secondary storage device 220. And history data 350 is stored.

  The HTTP server 310 manages communication with a browser 410 (see FIG. 4) on the client 130 described later via the network 150, and transfers data with the client 130 to the file sharing management program 320. In this embodiment, the communication protocol between the server and the client is HTTP, but a communication protocol other than HTTP may be used as long as there is no problem in data exchange described later.

  The file sharing management program 320 is a program that forms the basis of the present invention. The file sharing management program 320 manages the exchange of the file 340 with the client 130 and the management of the authentication, access authority, and owner authority, and the history management program 330 and the access history information. Communicate. Detailed operation will be described later.

  The history management program 330 records the access history for each user of the file 340 in the history data 350 based on the data from the file share management program 320 and answers the inquiry about the history data 350 from the file share management program 320. To do. Detailed operation will be described later. Details of the operation history data 350 will also be described later.

  FIG. 4 shows details of various programs and the like placed in the primary storage device 210 and the secondary storage device 220 of the client 130 (the CPU 200 and the like are not shown).

  Here, the OS 400 and the Web browser 410 are loaded on the primary storage device 210, and the electronic document file 430 to be exchanged with the file sharing server 100 is stored on the secondary storage device 220.

  The Web browser 410 controls communication with the HTTP server 310 on the server 100 via the network 150 and exchanges data, and also functions as a user interface with the user. That is, the page data 420 expressed in HTML or the like received from the HTTP server 310 is analyzed and displayed to the user, and an input requesting an operation selected by the user based on the content of the page data 420 is received. Request data is transmitted to a predetermined HTTP server 310. In this embodiment, the communication protocol between the server and the client is HTTP. However, if there is no problem in the data exchange described later, a communication protocol other than HTTP may be used, and a user interface is provided instead of a general-purpose Web browser. It may be a dedicated application program. Note that details of the communication with the page data 420 and the server 100 will be described in the detailed description of the operation of the server 100, and thus detailed description thereof will be omitted.

  Hereinafter, the operation of the present embodiment will be described with reference to FIGS. 5, 6, and 7. In the following description, five users from the first user User_1 to the fifth user User_5 are set in the file sharing system, and the file 340 on the file sharing server 100 is owned by the first user. It is assumed that the user authority is set, the read authority, the write authority, and the authority change authority are given, and only the read authority is given to the second to fifth users.

  First, the operation of the history management program 330 will be described with reference to FIGS.

  FIG. 6 is a flowchart showing an operation flow of the history management program 330.

  The history management program 330 receives a processing request and accompanying data from the file sharing management program 320 (step s600). For communication with the file sharing management program 320, inter-process communication such as socket communication or RPC (Remote Procedure Call) is used.

  The history management program 330 analyzes the received request, and if it is a history storage request (step s605), the received data is recorded in the history data 350 (step s615).

  An example of the history data 350 is shown in FIG.

  The data 700 records a field 710 that records the name of the file that has been accessed, a field 720 that records the accessed user, a field 730 that records the number of accesses for each user, and time information that the user last accessed. Field 740. The history data 350 on the secondary storage device 220 may be in an arbitrary format for storing the data 700, and may take, for example, a text file format or a database format.

  From the file sharing management program 320, the file name of the accessed file, the accessed user identification information, and the access time information are sent as accompanying data. In step s615, it is checked whether or not an entry consisting of the combination of the file name and the user already exists in the data 700. If not, a new entry is added, the access count of the corresponding entry is incremented, and the final Update access time information. The process in the case of a history saving request ends here.

  If it is not a history storage request but a history inquiry (step s610), access count information is acquired from the history data 350 (step s620). Specifically, the file name and user information are obtained from the accompanying data, the access count data of the entry determined from the combination is read, and the data is returned to the file sharing management program 320 (step s630). finish.

  If it is not a history inquiry, it is checked whether it is a request for resetting the access count data (step s625), and if it is not a reset request, the process ends as an error. If it is a reset request, the process proceeds to step s635, and the access count information of the history data 350 is reset to zero. Specifically, the file name is obtained from the accompanying data, the access count data of all entries corresponding to the file name is updated to 0, and the process is terminated.

  This is the end of the explanation of the operation of the history management program 330.

  Next, the operation of the file sharing management program 320 will be described with reference to FIG.

  FIG. 5 is a flowchart showing the operation flow of the history management program 320.

  The file sharing management program 320 receives the processing request from the client 130 and the accompanying data from the HTTP server 310 (step s500). User identification information, authentication information, and operation target file information are acquired from the accompanying data, and user authentication processing and access authority to the target file are confirmed (step s505). If user authentication fails or access authority is not given, the process ends as an error.

  If the authentication / authorization confirmation is successful, the process proceeds to step s510, the requested file operation is performed, the result is generated as page data 420, and the result is sent to the HTTP server 310, which is returned to the client 130. Next, the file access history is stored in the history data 350 (step s515). As described above, this is because the history storage request is sent to the history management program 330 together with the file name of the file accessed as the incidental data, the accessed user identification information, and the access time information.

  Next, the user who has the owner authority of the operated file is checked, and it is checked whether this is the same as the user who made the processing request (step s520). If they are the same user, the process ends. If they are different, the process proceeds to step s525, and a history inquiry is made to the history management program 330. Specifically, the file name of the file accessed as incidental data and the user identification information of the user who made the processing request, the file name of the accessed file, and the user who has the owner authority of the file An inquiry is made with each set of identification information, and information on the number of accesses to the file is acquired for each of the user who made the processing request and the user who has the authority to own the file.

  Next, whether or not to transfer the ownership authority by comparing the information on the number of accesses to the file of the user who made the acquired processing request and the user who has the ownership authority of the file according to a predetermined comparison condition It is determined whether or not (step s530). Here, the comparison condition is defined, for example, such that the access count of the user who has made the processing request is 10 times or more and exceeds 10 times the access count of the user having ownership authority. In the example shown in the data 700, the file foo. This condition is established between the number of accesses of the user User_1 who has the ownership authority to txt and the user User_2 who has made the processing request. If the condition is not satisfied, the process is terminated as it is.

  If the condition is satisfied, the file sharing management program 320 transfers the ownership authority of the file to the user who made the processing request (step s535). As a result, the write authority and authority change authority associated with the ownership authority are also transferred to the user who made the processing request, in the above example, the user User_2.

  Next, the transfer result is notified to the users User_1 and User_2 as the parties by a predetermined method (for example, e-mail) (step s540), and the history management program 330 is accessed to temporarily clear the comparison condition. A history reset request is sent (step s545). Specifically, a reset request is sent with the file name of the file to which ownership has been transferred as incidental data, the access count of the file is all reset to 0, and the process ends.

  Although the description of the operations of the file sharing management program 320 and the history management program 330 is finished as described above, conditions other than the number of file accesses can be added to the ownership transfer determination. For example, in addition to the number-of-times condition, it is also possible to add the last access time information such that a user having ownership authority has not accessed the file for more than three months. In this case, the history management server 330 requests history inquiry It is only necessary to return the last access time information in addition to the number of accesses when receiving the request.

  This is the end of the description of this embodiment.

  Next, another embodiment for carrying out the present invention will be described.

  This embodiment is a preferred form when a plurality of users other than the user having the authority to own a file make more accesses to the file and the number of accesses is competitive.

  The configuration of this embodiment is similar to that of the first embodiment. For this reason, the explanation will be focused on the differences while partially replacing the drawings.

  The system configuration suitable for the present invention is almost the same as that shown in FIGS. 1 to 4 described in the first embodiment. The file sharing management program 330 and the history management program 340 shown in FIG. 3 are specific to this embodiment, and will be described.

  Since the operation of the history management program 340 unique to the present embodiment is almost the same as the operation flow of the history management program described in the first embodiment, only the differences will be described by replacing FIG.

  If the request received in step s600 is not a history storage request but a history query (step s610), the process proceeds to step s620 'unique to the present embodiment, not step s620 of the first embodiment. In step s620 ', the history data 350 obtains all users who meet a preset condition, the access count information of the users, and the access count information of the users having ownership authority. Specifically, a file name is obtained from the accompanying data, and the access count data of all entries corresponding to the file name are compared under a preset condition. Here, the condition is, for example, the top three users in the number of accesses (in the example of the data 700 shown in FIG. 7, in the case of foo.txt, User_2, User_3, User_4 matches), or more than 70% of the maximum number of accesses A user with the number of accesses (similarly, User2 and User_4 match), and the like. Data in which the access count information of the user having the file ownership authority is added to this is returned to the file sharing management program 320 (step s630), and the process is terminated.

  The operations other than those described above are the same as the operations of the history management program of the first embodiment.

  Next, the operation of the file sharing management program 330 unique to the present embodiment will be described with reference to FIGS. 8A and 8B. The operation flow of the file sharing management program 330 specific to the present embodiment is the same as that of the file sharing management program of the first embodiment until the middle of the operation flow. Specifically, the operations from steps s800 to s820 are the same as the operations from steps s500 to s520, respectively, and thus description thereof is omitted.

  If the user who has the owner authority of the file operated in step s820 is different from the user who made the processing request, the process proceeds to step s825, and a history inquiry is made to the history management program 330. As described above, this history query is unique to the present embodiment. Specifically, the query is performed using the file name of the file accessed as incidental data, and all users who meet the conditions and the access of the user are checked. Get frequency information and access frequency information of users with ownership authority.

  Next, whether the maximum number of access times of the user meeting the above condition is compared with the number of access times of the user having the ownership right of the file according to a predetermined comparison condition, and the ownership right is transferred. It is determined whether or not (step s830). Here, the comparison condition is defined, for example, such that the number of accesses of a user who matches the condition is 10 times or more and exceeds 10 times the number of accesses of a user having ownership authority. If the condition is not satisfied, the process is terminated as it is.

  If the condition is satisfied, the process proceeds to step s835 to check whether the multiple execution prevention flag is set. This flag is realized by, for example, recording the file name in a text file (not shown) on the secondary storage device 220, and indicates whether or not the processing after step s845 is already being executed for the file. . If the flag has been set, the process ends. If not, the flag is set (step s840).

  Next, it is recommended that all users who meet the conditions and users who have ownership rights to the file should transfer the ownership rights of the file using a preset method (for example, e-mail). This is notified, and the user list that is the destination of the notification is presented as supplementary information (step s845). With this supplementary information, the user can know other users who should discuss ownership transfer.

  Next, the transfer deadline time is set and recorded by adding the preset transfer work allowable time to the current time (step s850). This is realized, for example, by using a text file that realizes a flag on the above-described secondary storage device 220 and adding the transfer deadline time to the file name.

  Next, the right to change the owner authority of the file is granted to all users who meet the conditions (step s855), and the process waits until the transfer deadline set in step s850 comes (step s860). That is, during this period, all users who meet the conditions can change the owner authority of the file.

  If the transfer deadline is reached, the process proceeds to step s865, where the authority to change the owner authority is deleted from a user other than the owner authority at that time, and the owner authority is transferred to the user who sent the notification in step s845. In addition to the owner and the administrator, the fact that the possible period has ended is notified (s870).

  Next, an access history reset request is sent to the history management program 330 to once clear the comparison condition (step s875). Specifically, a reset request is sent with the file name of the file as incidental data, the access count of the file is reset to 0, the flag set in step s840 is cleared (step s880), and the process ends.

  Although the description of the operations of the file sharing management program 320 and the history management program 330 is finished as described above, conditions other than the number of file accesses can be added to the ownership transfer determination. For example, in addition to the number-of-times condition, it is also possible to add the last access time information such as three people who have accessed the file within the last month or the last access time is closer to the present In this case, when the history management server 330 receives a history inquiry request, the last access time information may be returned in addition to the number of accesses.

  Further, the notification destination described in the description of step s845 is the minimum necessary, and an administrator of the file sharing server 100 may be included. In this case, since a plurality of notifications may be sent to the administrator at the same time, the administrator may be provided with a list of files for which transfer of ownership authority is recommended. For example, using a text file (not shown) on the secondary storage device 220, the file name and transfer work time limit information are added in the start notification process in step s845, and the information is added in the end notification process in step s870. It is realized by deleting. This file can be provided to non-administrator users.

  This is the end of the description of this embodiment, but this embodiment can be used in combination with the first embodiment. In that case, the process may be switched depending on the number of users who have a large number of accesses other than the user having the ownership authority in the access history inquiry process.

  The present invention can be applied not only to files but also to directories. In this case, the condition can be determined by, for example, totalizing the number of accesses for each user of files belonging to the target directory hierarchy or the total number of users having the largest number of accesses for each file.

  Furthermore, according to the present invention, it is possible to set conditions for each file, instead of determining conditions for the entire file managed by the file sharing system under the same conditions. In that case, for example, an attribute relating to ownership transfer is given to each file, and the file is referred to when determining the condition.

  FIG. 9 shows an example 900 of an attribute field for each file. Here, the field 910 indicates an attribute value indicating whether or not the ownership authority can be transferred, the field 920 indicates an attribute value indicating a user list preset as a candidate for transferring the ownership authority, and the field 930 indicates a use prohibiting the transfer of the ownership authority. An attribute value indicating a list set in advance as a person and a field 940 store an attribute value indicating a condition for performing ownership authority transfer determination, for example, the number of times of access is five times or more. By setting these attributes in an appropriate combination, detailed condition determination can be performed for each file.

System configuration diagram of a file sharing system for implementing the present invention Configuration diagram of an information processing apparatus constituting a file sharing system Program and data structure diagram of file sharing server Client program and data structure diagram The flowchart which shows the flow of operation | movement of the file sharing management program of 1st Example. The flowchart which shows the flow of operation | movement of a 1st log | history management program. Figure showing an example of historical data The flowchart which shows the flow of operation | movement of the file sharing management program of 2nd Example. The flowchart which shows the flow of operation | movement of the file sharing management program of 2nd Example. Figure showing examples of file attribute fields

Explanation of symbols

100 File sharing server 130a Client 130b Client 150 Network 200 CPU
210 Primary storage device 220 Secondary storage device 230 User input / output I / F
240 User I / O device 250 Network I / F
310 HTTP server 320 File share management program 330 History management program 350 History data 410 Browser 420 Page data 700 History data 900 File attribute field

Claims (14)

A file sharing means for realizing a file sharing service;
A history management means for collecting, storing, searching, and acquiring file access history on the file sharing service,
A file sharing system with
A means for storing user information accessed when a file is accessed in a history;
Means for obtaining access frequency information of the accessed file from the history management means;
Means for comparing and determining the acquired access frequency information based on a preset condition;
Means for transferring ownership of the file based on the determination result;
Means for clearing access frequency information of the file;
A file sharing system comprising:   The comparison determination means performs a comparison determination based on a preset condition between the file access count of the user having the file ownership authority and the user access count of the file access count being the maximum. 2. The file sharing system according to claim 1, wherein if the condition is satisfied, the ownership authority transfer means transfers the ownership authority of the file to a user who has the maximum number of accesses to the file.   The means for storing the accessed user information in the history further stores the time information at which the access was performed, the history acquisition means also acquires the time information accessed in addition to the access frequency information, and the comparison judgment means 3. The file sharing system according to claim 1, wherein access time information is used as a comparison condition in addition to access frequency information based on a preset condition. A file sharing means for realizing a file sharing service;
A history management means for collecting, storing, searching, and acquiring file access history on the file sharing service,
A file sharing system with
A means for storing user information accessed when a file is accessed in a history;
Means for obtaining access frequency information of the accessed file from the history management means;
Means for comparing and determining the acquired access frequency information based on a preset condition;
Means for notifying a plurality of users to transfer ownership authority, and granting authority to change the ownership authority of the file to the plurality of users only for a preset period;
Means for clearing access frequency information of the file;
A file sharing system comprising:   The plurality of users to be notified / authorized are users who have the authority to own the file and users who are selected based on conditions set in advance by the user who has the highest number of accesses to the file. The file sharing system according to claim 4, wherein the file sharing system is provided.   6. The file sharing system according to claim 5, wherein the file sharing system is also notified to a user who has management authority over the entire file sharing system.   7. The file sharing system according to claim 5, further comprising means for providing a list of the notified / authorized files for each user.   Furthermore, it has a means to set and acquire the individual conditions regarding transfer of ownership authority for every file, The said comparison judgment means judges also considering the individual conditions for every file, The one of Claim 1 thru | or 7 characterized by the above-mentioned. The file sharing system described in 1.   9. The file sharing system according to claim 8, wherein the individual condition for each file indicates whether or not ownership rights can be transferred.   The file sharing system according to claim 8 or 9, wherein the individual condition for each file is a list of users who are candidates for transfer of ownership authority.   11. The file sharing system according to claim 8, wherein the individual condition for each file is a list of users who are prohibited from transferring ownership.   12. The file sharing system according to claim 1, wherein a directory is also processed in addition to a file. File sharing process to realize file sharing service,
A history management process that collects, stores, retrieves, and retrieves the access history of files on the file sharing service;
A file sharing method with
Storing the user information accessed when the file is accessed in a history;
Obtaining access frequency information of the accessed file from the history management step;
Comparing the obtained access frequency information based on a preset condition;
Transferring ownership of the file based on the determination result;
Clearing the access frequency information of the file;
A file sharing method characterized by comprising: File sharing step to realize file sharing service,
History management step to collect, save, search, and retrieve file access history on file sharing service;
A file sharing program that executes file sharing with
Storing the user information accessed when the file was accessed in a history;
Obtaining access frequency information of the accessed file from the history management step;
Comparing and determining the acquired access frequency information based on a preset condition;
Transferring ownership of the file based on the determination result;
Clearing access frequency information of the file;
A file sharing program characterized by executing

Images