JPH0934769A - File managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a file managing device with which required file information excepting for a file identifier is also recorded as the retrieved result when a file is retrieved. SOLUTION: This device is provided with a retrieving processing means 20 for possessing the retrieved result containing the file information designated by a user by retrieving a retrieval object file 11 stored in a file storage device 10 and a retrieved result preserving processing means 30 for preserving that retrieved result. The file information designated by the user is the attribute and contents of the file 11 and this is stored in the file storage device 10 as retrieved result information 12. Thus, since the attribute and contents of the file are added to the retrieved result information 12 only composed of the identifier of the file and the retrieved result information 12 is accessed, the attribute and contents of the file can be provided without performing access to the file based on the file identifier of the retrieved result information 12.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file management device, and more particularly, to a file search according to a file search request from a client machine via a network, save the search result, and access right information to the saved search result file. The present invention relates to a file management device in a file server for setting the.

[0002]

2. Description of the Related Art In recent years, a client / server system has become widespread in which a plurality of clients and a plurality of servers which can be constituted by workstations or personal computers are connected to each other by a local area network. There is.
In the system, in particular, a file server manages files shared on the network.

FIG. 18 is a schematic system configuration diagram of a client / server system. According to the configuration diagram shown,
The client / server system is composed of a plurality of clients 1 and 2 and a file server 3, each of which has a communication function and is connected to each other by a computer network 4 such as a local area network (LAN). The clients 1 and 2 are for the user to request the server to process through the computer network 4, and the file server 3 is for actually processing the file. Although only one file server is shown in the figure, a plurality of file servers may exist.

For file management in the file server 3,
DFR (Docume) defined by the International Organization for Standardization (ISO)
filing protocols such as nt Filing and Retrieval) are used, and files are managed by contents that are actual data of files and attributes that are additional information such as titles and keywords. Also, this DFR
Then, when searching for a file, the result of the search previously performed by the client is displayed as “SearchResultL
It defines the function of recording in a special type of file called "ist". The outline is shown below.

FIG. 19 is an explanatory diagram of a method of storing search results in DFR. In the figure, a file group 5 managed by a file server is a search target, and information of files satisfying the search condition is obtained by performing a search (search) on the file group 5 within a specified range and condition. Is recorded in the file 6 as a search result. In the DFR, the list information of file identifiers (which are called UPI (Unique Permanent Identifier) in the DFR) found as a result of the search operation on the file group 5 is changed to “SearchResultLi
It is defined to be recorded in a special type of file 6 called "st". Therefore, in this file 6, the start time, the end time, the search range, the search condition, and the identifier list of the found file are recorded as the search information. Below, "Searchresul" in DFR
A search result recorded as a file such as “tList” will be referred to as search result storage information.

As described above, the conventional search result storage information includes
Since only the identifier information of the searched file is stored, the search result storage information is not always correct. For example, "X
After searching with the keyword "XX" and creating the search result saved information, one of the searched files is "XX
When the keyword "X" is changed to another keyword "YYY", the changed file is included in the search result as it is, although it should not be included in the search result storage information. I will end up. Also, when the searched file is deleted, similarly, a situation where the search result is not consistent occurs.

In such a case, some processing is required to maintain the consistency of the search result storage information.
Then, there is no regulation for automatically maintaining the consistency of the search results, and the search result storage information is recreated only when the user explicitly requests the update.

On the other hand, in the prior art, for example, Japanese Patent Laid-Open No.
The techniques described in Japanese Patent Laid-Open No. 243170 and Japanese Patent Laid-Open No. 6-251063 are known. According to these publications, there is disclosed a method for efficiently recovering the consistency when the information included in the search result becomes inconsistent due to the modification of the searched file.

[0009]

However, the search result storage information does not always have to be the latest. In some cases, it may be desirable that the information at the time of the search remains intact. In the DFR, since information other than file identifiers cannot be recorded as search result storage information on the server side, information including information other than identifiers such as attributes and contents of each file is recorded as search results. To do this, the user must access the files found as a result of the search and collect the information.

In a large-scale file server that manages tens of thousands of files, it may be difficult for the individual level to know where the target file is recorded.
In addition, even in a small file server with a level of hundreds to thousands, each person arbitrarily records and updates files, so in such a case, the procedure of searching for the target file must be obtained. I don't get. Therefore, it is useful if not only the file identifier but also necessary information can be recorded in the search result storage information at the time of searching.

However, if important attributes such as titles and keywords are recorded as search results in addition to the file identifier, it is likely that unnecessary attributes are also recorded, and the effective data recording area is effective. There is an aspect that it is not used, which goes against the intention of the user to record only the information that he wants to record.

Further, not only the attribute but also the content, for example, a request to record the content of the first page so that the content of the file can be easily discriminated can be considered, and can be recorded in the search result storage information. There is good reason to do so.

Further, in the DFR, an access list can be set in each file in order to control access from the user. The access list is information recording which user has what access right (read right, write right, etc.) to the file. However, regarding each file information included in the search result storage information created as a result of the search, only the file identifier information is provided, and the access right cannot be set. Therefore, the result of the search performed by the client first is recorded as the search result storage information, and the client refers to it when performing a narrowed search later. Access control to each file information included in the save information is to be performed by an access list set in the file of the search result save information and the access right of the file that is the source of each file information. Therefore, even if the file of the search result storage information has the access right, if the file body does not have the access right, the file information cannot be accessed through the search result storage information. This is not considered appropriate from the intention of widely sharing search results by putting search result storage information in a file server, and improvement is desired.

The present invention has been made in view of the above point, and it is possible to specify from the client the attribute or the type of content to be recorded as a search result, and only the attribute that will be required later will be searched. An object is to provide a file management device that provides a client with a framework that can be recorded in result storage information.

The present invention does not always record the attributes and contents as a search result when a search is performed, but when the frequency of updating / deleting a file is not so high, the present invention can be performed when necessary. An object of the present invention is to provide a file management device that records only attributes and contents as a search result and effectively uses a data recording area.

The present invention uses the information already recorded in the search result storage information as the search condition and the search range that must be designated every time when the routine work must be performed at regular intervals. In addition, it is an object of the present invention to provide a file management device that can reduce complexity during work and prevent human error.

Further, according to the present invention, since access right cannot be set to each file information included in the search result saving information, if the file information cannot be accessed through the search result saving information, it is included in the search result saving information. The access right can be set individually for each file information included in the search result saved information, whereas the access right must be set again for the file body to be changed, and the access right of the file body can be changed. It is an object of the present invention to provide a file management device capable of accessing file information through search result storage information.

[0018]

In order to solve the above-mentioned problems, in the first invention, as shown in FIG. 1, a plurality of files 11 each of which is stored in the file storage device 10 and has contents and attributes are provided. In a file management device to be managed, search processing means 20 for searching the file 11 of the file storage device according to a search request based on the attribute of the file, file search information by the search processing means is designated with file identification information and the file. The file management apparatus is provided with a search result storage processing unit 30 that stores and manages the search result information 12 based on the content or the attribute.

Further, in the second invention, the file management device holds management information 41 for managing the content or attribute type of the file to be stored in the search result information of the file at the time of the search by the search processing means 20. Then, when the file searched by the search processing unit 20 is updated or deleted, the type held in the management information 41 is acquired from the file and the search result information managed by the search result storage processing unit 30. The search result update processing means 40 to be recorded in 12 is further provided.

Further, in the third invention, the search result update processing means 40 is based on the search condition and the search range information recorded in the search result information 12 in response to the update request of the search result information 12. A condition information acquisition unit 42 for requesting a search from the search processing unit 20 is provided.

According to the fourth aspect of the invention, as shown in FIG. 2, in a file management device that manages a plurality of files 11 each of which is stored in the file storage device 10 and has contents and attributes, a search request based on the attributes of the file. According to the search processing means 20 for searching the file 11 of the file storage device, and the search result of the file executed by the search processing means 20 as the search result information 12 together with the file identification information and the type information including the file attributes and contents. The access right information 12a is stored for each file searched for the search result information 12 stored in the file storage device 10 and for each type of information.
And a search result storage processing unit 35 for setting, and access according to the access right information 12a when at least one of the information recorded for each type of the search result information 12 and the file via the search result 12 is accessed. An access control unit 45 for performing the above is provided.

[0022]

According to the first aspect of the invention, in the configuration of FIG. 1, when the search processing means 20 receives a search request, a plurality of files 11 to be searched, which are stored in the file storage device 10,
A search is performed on the search result to obtain information of a file that satisfies the search condition, and the search result is stored as the search result storage processing means 3
Notify 0. The search result storage processing unit 30 receives the file information, that is, the file identifier, the attribute, and the content, and stores it in the file storage device 10 as the search result information 12. As a result, the attributes and contents of the file are added to the search result information 12 that was only the file identifier, and the attributes and contents of the file are added without accessing the file based on the file identifier of the search result information 12.
It can be obtained by referring to the search result information 12.

Further, in the second invention, by further comprising the search result update processing means 40, the record of the search result is kept as the file identifier only as before, and the type of the attribute and the content of the file is management information. Hold at 41. When there is a file update or deletion notification, the attributes and contents of the file to be recorded in the search result information 12 are acquired from the file based on the type held in the management information 41, and the search result is obtained. It is recorded in the search result information 12 by the maintenance update means 40.

In the third invention, the search result update processing means 4
The search result information 12 includes the search condition and the search range that have to be designated each time an update request is made to the search result information 12 by including the condition information acquisition unit 42.
It is possible to obtain the information from the information recorded in (1) and request the search to the search processing means 20 based on this, and it is possible to simplify the routine work of updating the search result.

In the fourth aspect of the invention, in the configuration of FIG. 2, when the search processing means 20 receives a search request, it executes a search for the search target file 11 stored in the file storage device 10 and sets the search condition. The information of the satisfying file is acquired, and the search result is notified to the search result storage processing means 35. The search result saving processing unit 35 receives the file information, that is, the identification information (ID) of the file and stores it as the search result information 12 in the file storage device 10. The search result storage processing unit 35 can also set the access right information 12a for the search result information 12, and in the access right information 12a, each file searched and the attribute or content recorded for each type of the file. The access right is set for each item of information. Here, search result information 1
Access to information by type 2 or search result information 12
When there is a request for access to the file through the access control means 45, the access control means 45 can access the information or the file for each type according to the access right information 12a. By prioritizing the access right set in the access right information 12a over the access right set in the file 11,
The file information can be accessed through the search result information 12 without changing the access right set in the file 11.

[0026]

Embodiments of the present invention will be described below with reference to the accompanying drawings. FIG. 3 is a block diagram showing an embodiment of the file management device according to the present invention.

In this figure, the file management apparatus according to the present invention is provided in the file server 3 and is configured to process various requests concerning files from users of the clients 1 and 2 through the computer network 4. The request receiving unit 5 receives requests from the clients 1 and 2.
Performed at 0.

A search processing unit 60 is connected to the request receiving unit 50, and the search processing unit 60 is configured to be able to access the file 71 stored in the file storage device 70. The search result storage processing unit 80 is configured to receive a search result storage request from the search processing unit 60 and an access request for the stored search result from the request receiving unit 50. Further, the search result storage processing unit 80 stores the search result in the file storage device 70 as the search result storage information 72 or stores the search result storage information 7 stored therein.
2 is configured to be accessible. The search result storage information 72 is recorded in the file storage device 70 in the form of a file each time the search process is performed.

The request receiving unit 50 receives a request from a client, and if the request is a search request, requests the search processing unit 60 to perform processing. The search processing unit 60 receives the search request from the request receiving unit 50, searches the file 71 managed by the server according to the search range and the search condition given by the client, and acquires necessary file information.
Upon receiving the search result storage request from the search processing unit 60, the search result storage processing unit 80 records the search result executed by the search processing unit 60 in the file storage unit 70 as the search result storage information 72. Further, when the search result storage processing unit 80 receives a request to access the search result storage information 72 from the request receiving unit 50, the search result storage processing unit 80 returns the recorded result to the request receiving unit 50. The search result storage information 72 is
Not only the identifier information ID of the found file but also the attribute A or the content C designated by the client is recorded.

The search result storage processing unit 80 further has a storage information setting registration unit 81, and the type of information to be recorded in the search result storage information 72 can be set and registered as a default. That is, the search result is stored as the search result storage information 72.
As for the type of information to be recorded in, the attributes and contents are made to comply with the client's designation in addition to the file identifier information. However, when the client's explicit information type is not designated, the saved information setting registration unit 81 Search result saved information 7
Record in 2. As a result, it is possible to save the trouble of specifying the type of information to be stored in the search result storage information 72 each time.

In this way, since the information at the time of the search can be left as it is with respect to the attributes / contents of the file,
For example, it can be used for creating a list of files updated during a certain period. That is, the title of the file and the person who changed the file are specified as the type of information, a file included in the range of the past one month, for example, is searched by the date and time when the file was last changed, and the search result is recorded as search result storage information. As a result, by accessing the search result storage information file, it is possible to obtain information on a list of files that have been changed in one month. Also,
A list of recently added files can be created by creating the search result storage information by searching under the condition that the creation date and time is within two weeks. Furthermore, for example, every week, a file whose attribute of approval status is "undecided" is searched,
By creating the search result storage information, it is possible to obtain a list of the approval status of documents and use it as a material for managing the progress of work.

FIG. 4 is a flow chart showing the flow of processing at the time of search by the search processing section. When the search request is received from the request receiving unit 50, the request receiving unit 50 receives the information necessary for the search, that is, the search range, the search condition, and the type of information of the attribute or the content to be stored in the search result storage information 72, and the search is performed. The result storage processing unit 80 is notified of the start of the search processing (step S1). When the client does not specify the type of the attribute or content information to be stored in the search result storage information 72, the stored information setting registration unit 81 of the search result storage processing unit 80 sets the default information type. Get the value of. Next, one of the unexamined files included in the search range is selected as a search target (step S2). When selecting a file, it is determined whether or not there is an unexamined target file (step S
3). If the target file exists, it is determined whether or not the file matches the search condition (step S
4). Here, if the target file matches the search condition, the attribute / content for accessing the target file and recording it in the search result storage information is acquired, and the result is notified to the search result storage processing unit. Request recording (step S5). Generally, when accessing a file, it is more efficient to successively obtain the related attributes and contents because the process such as file opening is performed once. Therefore, the search processing unit 60 is configured to continuously obtain the information to be recorded for those that match the condition after accessing the file for the condition determination. When the process of step S5 ends, or in step S4,
If it is determined that the target file does not match the search condition, the process returns to step S2 to proceed to the selection of the next unexamined file. In this way, when the investigation is completed for all the files within the search range, there are no target files, so the search result storage processing unit is notified of the end of the search processing (step S6).

FIG. 5 is a flow chart showing the flow of processing at the time of searching by the search result storage processing section. The search result storage processing unit 80 first determines the notification content from the search processing unit 60 (step S11). Here, when the search processing unit 60 notifies the start of the save processing, the search result save information 72
Is created, and the search range and search conditions specified by the client are recorded in the search result storage information 72 (step S
12). If it is determined in step S11 that the search processing unit 60 has requested the recording of the search results, the identifier of the searched file in the search result storage information 72,
The corresponding attributes and contents are recorded (step S1).
3). It should be noted that, in this record, the attributes and contents specified by the client are recorded in the search result storage information 72 together with the file identifier. In step S11,
If it is determined that the search processing unit 60 has notified the end of the storage processing, recording in the search result storage information 72 is ended, and processing for closing the file of the search result storage information 72 is performed (step S14).

If any abnormality occurs in the search processing unit 60 during the process, the search result saving processing unit 80 is notified of the cancellation of the process. In such a case, although not shown, the search result storage processing unit 80 stops recording in the search result storage information 72 and deletes the search result storage information whose results are being recorded.

FIG. 6 is a block diagram showing another embodiment of the file management device. In this figure, the request receiving unit 50
A search processing unit 60 is connected to the search processing unit 60 so that a search target file 71 stored in the file storage device 70 can be accessed in response to a search request from the request receiving unit 50. The search result storage processing unit 80 is configured to receive a search result storage request from the search processing unit 60. Further, the search result storage processing unit 80 is configured to store the search result in the file storage device 70 as the search result storage information 72. The search result storage processing unit 80 further includes a storage information setting registration unit 81 that can set and register the type of information to be recorded in the search result storage information 72 as a default. The search result update processing unit 90 is configured to receive a search result from the search processing unit 60, and to receive a file update or deletion notification from the request receiving unit 50. The search result update processing unit 90 has management information 91 in the form of a table that holds information about the attributes or contents of files to be recorded with respect to the search result storage information 72 of the file storage device 70. The search result storage information 72 is configured to be updated according to a file update or deletion notification.

In response to a search request from the request receiving unit 50,
The search processing unit 60 performs the search process and requests the search result storage processing unit 80 to record the search result. Upon receiving the search result storage request, the search result storage processing unit 80 records the identifier of the file in the search result in the file storage unit 70 as the search result storage information 72.

Further, the search result of the search processing unit 60 is notified to the search result update processing unit 90 and held in the management information 91. Upon receiving a notification of file update or deletion from the request receiving unit 50, the search result update processing unit 90 refers to the management information 91 and requests the search processing unit 60 to obtain information before updating or deleting the file. The search processing unit 60 accesses the target file and acquires necessary information, and the search result update processing unit 90 updates the search result storage information 72. An example of this management information 91 is shown below.

FIG. 7 is a diagram showing an example of management information. According to the illustrated example, the management information 91 is configured in a table format, and has items of a target file, a search result storage information identifier, and a stored attribute / content type. The item of the target file contains the identifier of the searched file, and the item of the attribute / content type to be saved specifies the attribute or content of the file that must be recorded, and the item of the search result saved information identifier The identifier of the search result storage information 72 in which the designated attribute or content should be recorded is entered in the field. Note that the search result storage information 72 is created for each search process, so the types of attributes / contents stored for the same file may be recorded in different search result storage information 72. In that case, the search result storage information 72 is stored. A search result storage information identifier is specified to identify the information 72.

The table of the management information 91 is realized by a known method such as a hash method using a target file as a key or a binary tree in consideration of processing efficiency. The management information 91 is updated when the search processing unit 60 performs a search process in response to a search request from the client and the search result storage processing unit 80 creates the search result storage information 72. The processing is shown below.

FIG. 8 is a flow chart showing the processing flow of the search result update processing unit during the search processing. Search processing unit 6
When the search processing is performed under the condition that 0 creates the search result storage information 72, first, from the search processing unit 60, the search result storage information identifier, the attribute / content type to be recorded, and the searched file identifier string. A request for processing is received together with the information (step S21). Then, for each searched file, the search result storage information identifier and the recorded attribute / content type are added to the management information 91 as a pair (step S22).

FIG. 9 is a flow chart showing the processing flow of the search result update processing unit when updating a file. When the client updates or deletes the file, the search result update processing unit 90 first receives a file update / delete notification from the request receiving unit 50 (step S31). Then, the management information 91 is checked to determine whether or not the file is registered in the management information 91 as a target file (step S32). That is, the item of the target file of the management information 91 is checked using the notified file as a key. If the target file does not exist, the process ends as it is, and if there is, the search processing unit 60 is requested to access the target file, obtain the information that should be recorded in each search result storage information 72, and store the search result. The information is recorded in the corresponding portion of the search result storage information 72 based on the information identifier (step S33). Then, all the lines corresponding to the file are deleted from the management information 91 (step S34).

According to the above processing method, when the information not recorded in the search result storage information 72 is updated, the information is always recorded in the search result storage information 72. However, depending on the changed contents, it may not always be necessary to record the information in the search result storage information 72. For example, if only one attribute of a file is changed, the other attributes of that file are also managed by the management information 9
If it is registered as 1, the other attributes that do not need to be recorded are also stored in the result storage information 72. However, this method is efficient because it only checks whether the notified file is included in the management information 91 as a target file, but the file storage device 70 is wasted to some extent.

FIG. 10 is a block diagram showing another embodiment of the file management device. In this figure, the request receiving unit 5
0 is configured to notify the search result update processing unit 90a of a search result update request from the client. The search result update processing unit 90a includes a condition information acquisition unit 92 that acquires information on the search condition and search range recorded in the search result storage information 72 of the file storage device 70, and the acquired search condition and search range information. The search processing unit 60 is configured to request the search processing based on the above. The search processing unit 60 is configured to request the search result storage processing unit 80 to store a search result. The search processing unit 60 also
The file 71 of the file storage device 70 is configured to access for search, and the search result storage processing unit 80 is configured to newly create or update the search result storage information 72. The search result save processing unit 80 has a save information setting registration unit 81 capable of setting and registering the type of information to be recorded in the search result save information 72 as a default.

The search result update processing section 90a is the request receiving section 5
When the search result update request is received from 0, the condition information acquisition unit 92 acquires the search condition and the search range information from the search result storage information 72, and uses this to request the search processing unit 60 to perform the search processing. . The search processing unit 60 passes the search result to the search result storage processing unit 80 and requests a storage request. The search result storage processing unit 80 records the search results, and at this time, creates new search result storage information or reuses existing search result storage information, that is, updates existing search result storage information. It can be selected by the instruction of the client.

FIG. 11 is a flow chart showing the processing flow of the search result update processing unit when a search result update request is issued.
First, when the search result update processing unit 90a receives an update request for the search result storage information 72 from the request receiving unit 50 (step S41), the condition information acquisition unit 92 retrieves the search condition and search range from the specified search result storage information 72. Information is acquired (step S42). Next, the search result update processing unit 90a notifies the search result storage processing unit 80 of the start of processing, specifies the acquired search condition and search range, and requests the search processing unit 60 for the search processing (step S43). After that, the search process by the search processing unit 60 and the recording process of the search result by the search result storage processing unit 80 are performed (step S44). When the search processing unit 60 executes the search process to the end, the search processing unit 60 performs the process. Is completed to the search result update processing unit 90a and the search result storage processing unit 80, and the search result update processing unit 90a notifies the request receiving unit 50 of the end of the processing.

As a preferred embodiment, the embodiment of FIG. 6 and the embodiment of FIG. 10 can be combined. That is, the file storage device 70 of the search result storage information 72
In order to save the recording area in the search, only the file identifier is recorded in the search result, and the attributes and contents set in advance when necessary are recorded, and when the search result is updated, it is searched as the information necessary for the search process. This is a combination with the case of using the information of the search condition and the search range recorded in the result storage information 72. A configuration example of the file management device in this case is shown below.

FIG. 12 is a block diagram showing another embodiment of the file management device. In this figure, the request receiving unit 5
0 is connected to the search processing unit 60 and the search result update processing unit 90b, and the search processing unit 60 is connected to the search result update processing unit 90b.
It receives the search request from the search result storage processing unit 80 and the search result update processing unit 90b, and passes the search result obtained from the file 71. The search result save processing unit 80 has a save information setting registration unit 81 capable of setting and registering the type of information to be recorded in the search result save information 72 as a default, and the search result update processing unit 90.
b is management information 91 that holds information about the attributes or contents of files to be recorded in the search result storage information 72 of the file storage device 70, and search condition and search range information recorded in the search result storage information 72. And a condition information acquisition unit 92 for acquiring

Upon receiving the search request from the request receiving unit 50, the search processing unit 60 searches the file 71 of the file storage device 70 under the specified search condition and search range, and stores the search result in the search result storage process. It is passed to the unit 80 and the search result update processing unit 90b. Search result storage processing unit 80
Then, the search result storage information 72 is created, and the search condition and the search range and the identifier of the target file are recorded therein, and the file attributes or contents are in accordance with the client's designation, or if there is no client's designation, the storage information is stored. It is recorded according to the default set in the setting registration unit 81. On the other hand, the search result update processing unit 90b receives the search result from the search processing unit 60, and records the information about the attribute or the content of the file to be recorded in the search result storage information 72 in the management information 91.

When the request receiving unit 50 notifies that the target file is updated or deleted, the search result update processing unit 90b checks the management information 91,
If there is a corresponding file and the attribute or content of the file to be recorded in the search result storage information 72 is requested, the search processing unit 60 is requested to acquire the attribute or content to be recorded from the file and the search result is obtained. The information is recorded in the storage information 72, and the recorded information is deleted from the management information 91.

When an update request is made from the client to the search result storage information 72 stored in the file storage device 70 through the request receiving unit 50, the search result update processing unit 90b first starts from the management information 91 managed by itself. The location of the target search result storage information 72, that is, the identifier of the target search result storage information and the type of attribute / content to be stored is extracted and recorded in the target search result storage information 72 by the condition information acquisition unit 92. Acquire information on the search conditions and search range that are set. Based on the acquired information, the search processing unit 60 is requested to perform processing, the obtained search results are passed to the search result update processing unit 90b, and the search result storage processing unit 80 updates the search result storage information 72 to perform the search. The result update processing unit 90b adds new information to the management information 91.

FIG. 13 is a block diagram showing another embodiment of the file management device. In this figure, the requests from the clients 1 and 2 are the request receiving unit 50 of the file server 3.
Is configured to be accepted at. Request reception part 5
The search processing unit 60, which receives a search request from 0, is configured to access the file 71 stored in the file storage device 70. The search result storage processing unit 80 is configured to receive a search result storage request from the search processing unit 60 and store the search result as the search result storage information 72 in the file storage device 70. The search result save processing unit 80 may be configured to save not only the file identifier but also the file information regarding the attribute of the file when saving the search result. Further, the search result storage processing unit 80 receives the request from the request receiving unit 50 and grants the access right to the access list 72a added to the search result storage information 72 for each file or for each information type of each file. It has an access list setting / changing unit 82 for setting. Further, a search result storage access unit 93 that receives an access request from the request reception unit 50 is provided.
Upon receiving an access request from the request receiving unit 50 through the search result storage information 72, the search result storage access unit 93 can access the file 71 according to the access right set in the access list 72a of the search result storage information 72. it can.

The search result save processing unit 80 creates search result save information 72 in the file storage device 70, and an access list 72a is added to the created search result save information 72. Here, as an example of the configuration, only the file identifier (ID) is stored in the search result storage information 72, and the access right is set for each file.

When a client makes an access request through the search result storage information 72, the search result storage access unit 93 accesses the access list 72a assigned to the search result storage information 72 and determines whether or not the file has an access right. If there is an access right, the access to the file is given priority over the access right provided for the file itself.

It should be noted that when accessing the file through the search result storage information 72, it may not be desirable to disclose all the information. For example, information such as a title and keywords may be disclosed, but there may be a case where the content of the file itself or a personal memorandum is not disclosed. Therefore, the access right can be set not only in individual file units but also in individual information units. A configuration example of the access list 72a in this case is shown below.

FIG. 14 is a diagram showing an example of the structure of the access list. According to the illustrated example, the search result storage processing unit 80
An access list 72a is added to the search result storage information 72 that has been stored by the access list 72a. The access list 72a includes an "file identifier (ID)" and an "information type" that represents file information such as file attributes / contents. "When,
Each item such as "who is allowed access" indicating who can access is set.

Here, the file 7 by the search processing unit 60
1, the file identifier “File
If five files having “1 to 5” are found, the search result saving information 72 recorded by the search result saving processing unit 80 records the identifier of the found file. Corresponding to these files, access rights are set in the access list 72a for each file and for each information type. For example, the search result storage information 72
If you access the file through
The title attribute of the file "e1" is (Every
One) value can be seen, but the keyword can be seen only by the administrator (Manager). Also, the file with the identifier “File3” is designed so that anyone can see all the information (All), and the file with the identifier “File5” indicates whether or not all the information can be accessed in the file body (Origina).
It is specified to comply with the access right rules set in l).

The default is used when no access right is set for the file information.
In this example, the search result storage information 72 also includes a file with the identifier "File4".
access list 72 for access to files
Since there is no definition in a, it will be controlled by the default value. By allowing the defaults to be defined in this way, it becomes possible to save the trouble of setting the access right for each file.

Further, in the default information type in the access list 72a, "Other" is
It is used for other information for which the access right is not set. For example, if there is an attribute of the creator other than the title and the keyword, the access right is not set for the creator. Anyone will be able to see the information.

Further, when accessing the attributes or contents for each information type stored in the search result storage information 72, it depends on the access right set for each information type.

FIG. 15 is a flow chart showing the processing flow of the access list setting / changing unit when updating the access list. When the search result storage processing unit 80 receives a request to update the access right to the search result storage information 72 from the request receiving unit 50, the access list setting / changing unit 82 first determines whether the request is an update request to the default (step S51). . If it is determined that the access right update request is for the default, the default value is updated and the process ends (step S5).
2). In the determination of step S51, if the access right update request is not for the default, an entry corresponding to the specified file is searched for in the already recorded access list 72a (step S53). Next, it is judged whether or not there is a corresponding entry (step S54), and if there is not, an entry of the access right corresponding to the specified file is created (step S5).
5). Then, for the found entry or created entry, the specified information type or “Other” is set.
Information of the access right corresponding to (step S5
6). For information types for which access rights have already been set, the access rights are updated by overwriting the access rights information.

FIG. 16 is a flow chart showing the processing contents of the search result storage access unit when acquiring the list of file information through the search result storage information. When a user of a certain client makes a request for acquisition of file information through the search result storage information 72, the request receiving unit 50 issues an access request instruction to the search result storage access unit 93. Then, the search result storage access unit 93 extracts one file identifier from the specified search result storage information 72 (step S61) and determines whether or not there is a file identifier (step S62). If there is a file identifier, the information type of the file in the access list 72a is accessed to check whether the user has the access right to the requested information type (step S63). Next, as a result of the check, it is determined whether or not there is an access right (step S64). If there is an access right, the file is accessed and the value of the information type designated by the user is obtained (step S65). Step S6
In the judgment of No. 4, if there is no access right and after the necessary information of the file is acquired in step S65, the process returns to step S61 and the next file identifier is extracted. If there is no file identifier in step S62, the information acquired thus far is returned to the user (step S66).

In addition to acquiring list information, 1
You can also get information about one file. In this case, the file identifiers are extracted one by one from the search result storage information, and when the requested identifier is obtained, it is next checked whether the user has the access right to the requested information type, and the access is performed. If the user has the right, the file is accessed, the information of the specified information type is acquired, the result is returned to the user, and the processing ends. Note that in the access list 72a illustrated in FIG. 14, as an example, anyone (EveryOn
Although only e) and the administrator (Manager) are described as accessible persons, it is also possible to designate individual users or other groups.

Further, considering the general usage pattern of the search result storage information 72, here mainly the acquisition of file information using the search result storage information 72 is considered, but access in the access list 72a is permitted. It is also possible to subdivide the columns of users' terms into those whose values can be obtained and those whose values can be changed.

FIG. 17 is a diagram showing another example of the structure of the access list. According to the example of the access list 72a shown in the figure, the items of persons who are permitted to access are divided into “read access” which allows acquisition of a value and “write access” which allows modification of the value. In this way, by further setting the right of write access to the person who is permitted to access, the file can be changed using the search result storage information 72.

Finally, the file management apparatus of the present invention makes it possible to actually access a file that is not permitted to be accessed by actually accessing the file using the search result storage information. Therefore, in terms of security, it is necessary to allow the creation of search result storage information only to those who have certain rights. For example, it is preferable that only the owner of the file body can set / change the access list of the search result saved information, or only the person who has the administrator right can create the search result saved information.

[0066]

As described above, according to the present invention, the file attributes or contents other than the file identifier can be recorded as a file search result. It is not necessary to access the file one by one based on the searched file identifier to reacquire the attribute or content of the file, and the attribute or content of the file can be acquired only by referring to the search result storage information.

Further, since the access right which gives priority to the access right of the file body can be set in the file information saved as the search result of the file, it is an ordinary file which is the access control by the access right attached to the file body. In addition to access control, file access control through search result information becomes possible. Furthermore, in addition to setting the access right to each file information included in the search result information, it is possible to set the access right to a part of each file information such as the attribute and contents of the file, so that it can be made more precise. Fine file access management is possible.

[Brief description of drawings]

FIG. 1 is a block diagram showing a basic configuration of a file management device according to the present invention.

FIG. 2 is a block diagram showing the basic configuration of another file management device according to the present invention.

FIG. 3 is a block diagram showing an embodiment of a file management device according to the present invention.

FIG. 4 is a flowchart showing a flow of processing at the time of search by a search processing unit.

FIG. 5 is a flowchart showing a flow of processing at the time of a search by a search result storage processing unit.

FIG. 6 is a block diagram showing another embodiment of the file management device.

FIG. 7 is a diagram showing an example of management information.

FIG. 8 is a flowchart showing a processing flow of a search result update processing unit at the time of search processing.

FIG. 9 is a flowchart showing a processing flow of a search result update processing unit when updating a file.

FIG. 10 is a block diagram showing another embodiment of the file management device.

FIG. 11 is a flowchart showing a processing flow of a search result update processing unit when a search result update request is issued.

FIG. 12 is a block diagram showing another embodiment of a file management device.

FIG. 13 is a block diagram showing another embodiment of the file management device.

FIG. 14 is a diagram showing a configuration example of an access list.

FIG. 15 is a flowchart showing a processing flow of an access list setting / changing unit when updating an access list.

FIG. 16 is a flowchart showing processing contents of a search result storage access unit when acquiring a list of file information through search result storage information.

FIG. 17 is a diagram showing another configuration example of an access list.

FIG. 18 is a schematic system configuration diagram of a client / server system.

FIG. 19 is an explanatory diagram of a method for storing search results in DFR.

[Explanation of symbols]

 10 file storage device 11 file 12 search result information 12a access list 20 search processing means 30 search result storage processing means 35 search result storage processing means 40 search result update processing means 41 management information 42 condition information acquisition means

Claims (4)

[Claims] 1. A file management device for managing files stored in a file storage device, each of which has a content and an attribute, and search processing means for searching a file in the file storage device according to a search request according to the attribute of the file, And a search result storage processing unit that stores and manages the search result of the file by the search processing unit as search result information based on the file identification information and the designated content or attribute of the file. Management device. 2. The management information for managing the content or the type of attribute of the file to be stored in the search result information of the file at the time of the search by the search processing means is held, and the file searched by the search processing means is updated. Further, when it is deleted, it further comprises search result update processing means for acquiring the type held in the management information from the file and recording it in the search result information managed by the search result storage processing means. The file management device according to claim 1. 3. The search result update processing unit requests the search processing unit to perform a search based on the search condition and search range information recorded in the search result information in response to a search result information update request. 3. The file management device according to claim 2, further comprising a condition acquisition unit for performing the operation. 4. A file management device for managing files stored in a file storage device, each of which has contents and attributes, and search processing means for searching for a file in the file storage device in accordance with a search request based on the attributes of the file. The search result of the file executed by the search processing means is stored in the file storage device as the search result information together with the file identification information and the type information including the attributes and contents of the file, and the stored search result information is searched. Search result storage processing means for setting access right information to each file and information for each type thereof, and at least the file recorded through the search result information and the information recorded for each type of the search result information When accessing one, access according to the access right information A file management device comprising: an access control unit that performs the access control.