JP2004133505A - File management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a file management system efficiently classifying and managing a document file or a drawing file created in business or the like. <P>SOLUTION: A specific folder (hereinafter called as 'a domain') is provided with a means holding list data registered with information of a folder and/or a file to be dealt as one present inside the domain. A folder and/or a file in another hierarchy can be registered into the list data in addition to the folder and/or the file actually under the domain in the hierarchical structure. An attribute of each the file is managed, and file operation is finely managed in each user. A similar file retrieval means is provided to search for a place to be present of a file stored in a false place. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a file management system, and more particularly to a file management system that efficiently classifies and manages document files and drawing files created in business or the like.
[0002]
[Prior art]
Conventionally, there is a folder or directory structure as a file management method of a computer system. This is a management method widely used in operating systems (hereinafter referred to as OS) such as Microsoft Windows (trade name) and Apple Computer's Mac OS (trade name). Is created, and document files and drawing files are stored and classified under it.
[0003]
In addition, when sharing a document file via a server, the client has a file utility that can perform classification, organization, and directory browsing of the document file according to a plurality of classification schemes, so as to improve the efficiency of file search. There is also a file sharing system (for example, Patent Document 1).
[0004]
In addition, the attributes of files and folders are registered in the management table so that other folders related to the selected folder or other folders containing files related to the files included in the folder can be easily searched. There is also a system (for example, Patent Document 2).
[0005]
[Patent Document 1]
JP 2000-268041 A (page 3-4)
[Patent Document 2]
JP 2001-167104 A
[Problems to be solved by the invention]
In a file management system usually included in an OS, a user can freely create folders and manage files. Therefore, the user creates a folder hierarchy according to business or purpose, classifies and stores files according to the hierarchy. However, the classification of the hierarchical structure by the folder may cause a problem with the passage of the date and the expansion of the business. This will be described below.
[0007]
For example, assume that a new business is started in a computer system operated by a company. When it is necessary to use existing document files and drawing files in this new business, those files may be scattered in a plurality of folder hierarchies accessed by the existing business and other business establishments. In this case, it is easy to create a new folder and move the necessary files for the new business, but it may be difficult to move the files in the existing business or operations of other business establishments. is there.
[0008]
It is also assumed that a business tie-up is made with an external company and that some files managed in the company are to be opened to the company. Also in this case, it may be troublesome that necessary files are scattered in a plurality of folder hierarchies in the in-house system and are moved without permission. In such a case, giving unnecessary file access rights to an external company is not preferable in terms of security, and it is inconvenient for the external company that files are scattered in various folder hierarchies.
[0009]
In view of such a problem, an object of the present invention is to provide a file management system capable of flexibly increasing or decreasing the classification according to the needs such as business expansion, on the premise of the file management based on the hierarchical structure that the OS generally has. I do.
[0010]
[Means for Solving the Problems]
In order to achieve this object, the present invention provides a file management system that manages folders storing data files in a hierarchical structure in a storage area of a computer system.
For a specific folder (hereinafter, referred to as a “domain”), there is provided a means for retaining list data in which information of folders and / or files to be treated as being in the domain is registered. It is characterized in that not only folders and / or files under the domain in the hierarchical structure but also folders and / or files in another hierarchy can be actually registered.
In the system of the present invention, file operations can be performed in folders (ie, domains) irrespective of the folder hierarchical structure, assuming the file management function of the OS, which is conventionally provided. .
[0011]
The file management system of the present invention further includes means for assigning an attribute to each data file in association with the data file. The attribute includes owner information indicating information of a person who created the file, and information on who the file is disclosed to. Public information indicating that copying of the file is permitted, deletion information indicating who is allowed to delete the file, and overwriting the original file when the file is updated or saving it as a new file It is preferable that at least one of update information indicating whether to perform the registration is registered.
By managing the attributes of each file in this way, it is possible to perform detailed management of file browsing, updating, deletion, and the like for each user.
[0012]
In this file management system, the attributes of each file include at least the public information, and the file management system further provides the user who has created a list of only the files published to the user in response to a file list request from the user. It is desirable to have a list creating means to provide.
[0013]
Further, when the file management system of the present invention receives a request to delete a folder or a file registered in the list data of an arbitrary domain (hereinafter, referred to as “1 domain”), the folder or the file is deleted from another list. Check whether it is registered in the list data of the domain, and if it is registered in the list data of another domain, delete the information of the folder or file from the list data of the one domain, and list the other domain It is desirable to have a deletion control means for deleting the folder or the file itself from the storage area of the computer system when the data is not registered in the data.
With this deletion control means, it is possible to prevent problems such as erasing files that are no longer needed in one domain but are required for other tasks.
[0014]
The file management system of the present invention further includes a similar file search unit, which extracts, for each file to be searched, actual data other than the control information used by the computer system or the application that handles the file. Then, it is desirable to extract a file whose similarity obtained by comparing the actual data is equal to or more than a reference value as a similar file.
This similar file search means can easily obtain information such as where a file stored in a place where it should not be should be moved, etc., and can facilitate file management.
[0015]
BEST MODE FOR CARRYING OUT THE INVENTION
Embodiments of the present invention will be described below with reference to the accompanying drawings. FIG. 1 is a diagram showing an embodiment of a file management system according to the present invention. As shown in FIG. 1, a plurality of client terminals 20 and a file server 30 are connected to a network 10 such as an in-house LAN. The file server 30 is a server for registering a document file and a drawing file used in business or the like, and includes a large-capacity storage unit 40.
[0016]
An OS (Operating System) 31 running on the file server 30 has a normal file management function, manages folders in the storage area 40 in a hierarchical structure, and stores data files in each folder. This example is shown in FIG. Folders F2, F3... Fn are created under the folder F1, document files B1 to B3 are registered in the folder F2, and drawing files P1 and P2 are registered in the folder F3. Note that a folder can be created under the folder F2 and the folder F3, and further under that folder. Where and what folders are created and which files are stored in which folders are determined as appropriate according to the business content, convenience of management, and the like.
[0017]
In the system of the present invention, the file server 30 further includes a domain registration unit 32, an attribute management unit 33, a list creation unit 34, a deletion control unit 35, and a similar file search unit 36. The domain registration unit 32 manages, for a specified folder, a list in which information of folders and / or files to be treated as being in the folder is registered. In this list, not only folders and / or files under the folder in the OS hierarchical structure but also folders and / or files in another hierarchy can be registered. A folder managed in this way is referred to as a “domain” in this specification. The list of each domain can be organized as files stored in the domain.
[0018]
FIG. 3 shows an example in which a domain D1 is created below the folder F1. In this case, a process is performed in which a new folder F4 is created below the folder F1 and is made a domain D1 (see FIG. 3B). That is, when there is a new folder creation request from the user, the domain registration unit 32 inquires the creator of "whether to make a normal folder or a domain", and if the domain is to be made, it is in the domain D1. Prompts you to specify folders and / or files that should be treated as such. The folder and / or file specified here is registered in the list of the domain D1 shown in FIG. FIG. 3 shows an example in which the entire folder F2 and the drawing file P2 in the folder F3 are registered in the domain D1.
[0019]
As shown in FIG. 3A, the list has at least a column for registering a folder name and a file name (or information such as a path). When the user specifies a folder or file that should belong to the domain D1, the folder or file name is registered in the list. If a folder is specified here, it is interpreted as specifying all files in that folder, and a special symbol (for example, “*. *”) Is registered in the file name column. It is also assumed that the document file B4 can be directly arranged under the domain D1 or another domain or folder can be created. This list can be specified not only at the time of creating the domain D1, but also at a later time.
[0020]
When a folder or a file belonging to the domain D1 is designated in this way, a relationship as shown in FIG. That is, in addition to the document file 4 under the domain D1, the entire folder F2 and the drawing file P2 are displayed under the domain D1, and these can be handled as folders and files under the domain D1. However, the original folder F2 remains under the folder F1, and the drawing file P2 remains under the folder F3, and can be used as it is at this location as before.
[0021]
That is, in this specification, a “domain” is a type of folder in a general computer system, under which folders and files can be stored as they are, and folders and files belonging to other layers are subordinate to the domain. It has a function that can be treated as. Domains are displayed like folders, and users can be treated like folders. While folders manage files in a hierarchical structure, domains can manage files, folders, and domains across other hierarchies. Therefore, in the file management system of the present invention, one data file can belong to a plurality of domains and can be used from each domain.
[0022]
Next, the attribute management unit 33 of the server 30 will be described. For each data file in the storage unit 40, the attribute management unit 33 determines the owner information indicating the information of the person who created the file, the public information indicating to whom the file is to be disclosed, and whether copying of the file is permitted. , The deletion information indicating who is permitted to delete the file, and the update information indicating whether to overwrite the original file or save it as a new file when the file is updated, as attributes. FIG. 4 shows the details of this attribute information.
[0023]
As shown in FIG. 4, the owner information indicates a person who first stores the data file by a name, an ID, or the like. The public information indicates to whom the data file is to be disclosed with which authority (for example, reference only, update permission, copy creation permission, etc.) by name, ID, or the like. Copy information refers to the owner of the copy, if the copy of the data file is allowed (whether the owner of the original file is inherited as the owner of the copy file, ). The deletion information indicates who (owner or arbitrarily designates) the right to delete the data file. The update information indicates whether to overwrite the original file or update the data file when updating the data file.
[0024]
The above attribute information is configured as control information of the data file and is incorporated in the file, is generated as an individual attribute information file for each data file, or one or more databases are created and registered in the entire system. Or you can. These attributes are specified by an authorized user when creating or updating a file, or are automatically given by a preset setting, and can be changed later by an authorized user. By managing the attribute information for each file in this manner, fine file management as described below is realized.
[0025]
(1) File browsing When there is a browsing request for an arbitrary data file managed by the server 30 from the client terminal 20, the attribute management means 34 refers to the public information of the attribute of the data file, and the user of the client terminal 20 It is confirmed whether or not the data file is to be disclosed, and if so, under what authority (updating, reference only, etc.) is possible. If the disclosure target person has the authority (for example, when the user is the owner), the use of the file is permitted. Otherwise, the use of the file is restricted.
[0026]
(2) File Copy When the client terminal 20 attempts to copy a file, the attribute management unit 33 refers to the file attribute copy information, and if the owner inheritance setting is set, the owner name of the original file is used as the owner information of the copy file. register. If the copy information is a copy person setting, the copy person is registered as copy file owner information.
[0027]
(3) When a file update request is received from the file update client terminal 20, the attribute management unit 33 refers to the update information of the file attribute and confirms whether the file can be overwritten. If overwriting is possible, the original file is overwritten. If overwriting is impossible, the user is notified to save the file as another file.
[0028]
(4) File Deletion When an arbitrary file deletion request is issued from the client terminal 20, the attribute management unit 33 refers to the file attribute deletion information and confirms whether the user of the terminal 20 has deletion authority. . If the user does not have delete authority, the user is notified that deletion is not possible.
[0029]
Next, the function of the list creation unit 34 will be described. In response to the file list request from the client terminal 20 shown in FIG. 1, the list creating unit 34 provides the user who has created a list of only the files published to the client terminal. FIG. 5 shows this processing flow. When the user of the client terminal 20 desires a file operation of the file server 30, a file list request is made to the server 30 (step S11). The list creation unit 34 recognizes the user from the ID of the client terminal 20 included in the request or by directly inquiring the user. Thereafter, one data file is taken out of the storage means 40 (step S12). If the data file exists (step S13: YES), the public information is referred to among the attributes (step S14).
[0030]
As described above, in the public information of the file attribute, the name or ID of the person to whom the file is to be released and with which authority is registered. Therefore, it is determined whether or not the user of the client terminal 20 making the request is the target of disclosure. A determination is made (step S15). If it is a disclosure target, the file information is added to the list, and the next file information is taken out (from step S16 to S12). If the user is not a file disclosure target, the next file information is taken out without adding the file information to the list (step S15: NO). In this way, a file list is created, and when the processing is completed up to the last file (step S13: NO), the file list is provided to the client terminal 20 (step S17). By this processing, the user is provided with a list of only files that have been released to the user, and can open the file by specifying from this list.
[0031]
Next, the deletion control means 35 will be described. Upon receiving a request to delete a file in the domain from the client terminal 20, the deletion control means 35 only releases reference from the domain depending on the relationship with another user or the like, or deletes the actual file itself. Is a means for determining FIG. 6 shows a processing flow of the deletion control means 35. When the client terminal 20 specifies a file from an arbitrary domain and issues a deletion request, the deletion control unit 35 detects this (step S21). The deletion control unit 35 refers to the list of each domain in the storage unit 40 and checks whether or not the file related to the deletion request is registered in the list of another domain (step S22). Here, when the file is registered in the list of another domain (step S23: YES), the information of the file is deleted from the list of the domain requested to be deleted (step S24). In this case, the original file is not deleted from the storage means 40, and only the file is not displayed in this domain.
[0032]
On the other hand, if the file requested to be deleted is not registered in the list data of another domain (step S23: NO), the file itself is deleted from the storage area of the computer system (step S25). In this case, of course, the deletion information of the file attribute is referred to confirm the deletion authority of the user of the client terminal 20. By performing deletion management in this manner, it is possible to prevent a file that is no longer needed in one domain from being deleted in another business or the like.
[0033]
Next, the similar file search means 36 will be described. Although the file management on the system can be flexibly performed by the above-described means, it is necessary for the user to perform the file classification and the hierarchical management itself according to the business contents and the like. In this case, if a file is saved as a separate file at the time of file copy or update in daily work, a file may be stored in an incorrect folder due to a determination error or an erroneous operation. In order to support the collection of such a situation, the file management system of the present application is provided with a similar file search means 36.
[0034]
The similar file search unit 36 is a unit that, when a search request specifying an arbitrary file is received, returns a file whose content is similar to the file. A data file created by a word processor or a CAD system can be divided into control information used by a computer system or an application, and character text or graphic data (actual data) required by other people. Therefore, it is possible to search for a similar file by comparing only the actual data.
[0035]
FIG. 7 shows a processing flow of the similar file search means 36. Upon receiving a similar file search request including designation of an arbitrary file from the client terminal 20 (step S31), the similar file search means 36 extracts actual data of the specified file (step S32). In this case, the similar file search means 36 has information in advance as to what kind of control information is stored in the file with respect to the storage format of the main application, and by excluding the control information based on this information, the actual file search is performed. Extract the data.
[0036]
Next, one data file in the search range is extracted, and the actual data is extracted in the same manner (steps S33 and S34). The actual data obtained by the above processing are compared with each other (step S35), and it is determined whether or not the similarity is equal to or greater than a set reference value. This similarity is determined based on how many identical data strings are included. If the similarity is equal to or greater than the reference value, the similarity is added to the list (step S36), the next data file is extracted, and the same processing is performed. When the last data file in the search target range ends (step S33: NO), the created file list is transmitted to the client terminal 20 (step S37). The reference value to be added to the list can be set by the user according to the purpose or the like.
[0037]
According to the similar file search means 36, it is possible to know where a similar file is stored for an arbitrary file. Therefore, when a file stored in a place that should not be originally found is found, it is possible to search where such a file should be stored and move it to a regular place.
[0038]
【The invention's effect】
As described above in detail, according to the file management system of the present invention, it is possible to handle folders and files in other hierarchies with the concept of a domain that does not depend on the hierarchical structure of existing folders. It is possible to manage the files to be spread more easily and flexibly. In addition, attributes are provided for each file so that processing such as disclosure, update, copy, and deletion can be restricted, so that file management of a file server that stores various business files can be performed finely.
[0039]
Further, since the storage location of the similar file can be grasped by using the similar file search means, it is possible to easily obtain information such as where the file stored in the place where it should not be should be moved. , For convenience of file management.
[Brief description of the drawings]
FIG. 1 is a diagram showing an entire file management system according to the present invention.
FIG. 2 is a diagram illustrating a file management method based on a file management function normally included in an OS.
FIG. 3 is a diagram for explaining a function of a domain registration unit shown in FIG. 1;
FIG. 4 is a diagram illustrating attribute information managed by an attribute management unit shown in FIG. 1;
FIG. 5 is a flowchart illustrating a process of a list creation unit shown in FIG. 1;
FIG. 6 is a flowchart illustrating processing of a deletion control unit illustrated in FIG. 1;
FIG. 7 is a flowchart illustrating processing of a similar file search stage illustrated in FIG. 1;
[Explanation of symbols]
Reference Signs List 10 network 20 client terminal 30 file server 31 operating system 32 domain registration means 33 attribute management means 34 list creation means 35 deletion control means 36 similar file search means 40 storage means

Claims (5)

In a file management system that manages folders storing data files in a hierarchical structure in a storage area of a computer system,
For a specific folder (hereinafter, referred to as a “domain”), a means is provided for holding list data in which information of folders and / or files to be treated as being in the domain is registered. A file management system capable of actually registering not only folders and / or files under the domain in the hierarchical structure but also folders and / or files in another hierarchy. 2. The file management system according to claim 1, wherein the system further comprises means for assigning an attribute in association with each data file, wherein the attribute includes owner information indicating information of a person who created the file, Public information that indicates to whom the file is made public, copy information that indicates that copying of the file is permitted, deletion information that indicates who is allowed to delete the file, and the original file when the file is updated A file management system, wherein at least one of update information indicating whether to overwrite or save as a new file is registered. 3. The file management system according to claim 2, wherein the attribute of each file includes at least the public information, and the file management system further generates a list of only files published to the user in response to a file list request from the user. A file management system, comprising: a list creating unit that provides the created user with the list. 4. The file management system according to claim 1, further comprising a request for deleting a folder or a file registered in list data of an arbitrary domain (hereinafter, referred to as "1 domain"). If received, it is checked whether the folder or file is registered in the list data of another domain. If the folder or file is registered in the list data of another domain, the folder or file is registered from the list data of the one domain. A file management system comprising: deletion control means for deleting file information and deleting the folder or the file itself from the storage area of the computer system when the file information is not registered in the list data of another domain. 5. The file management system according to claim 1, wherein said system further includes a similar file search unit, and said similar file search unit is, for each file to be searched, said computer system or an application handling said file. A file management system that extracts actual data other than control information used by the computer and extracts a file whose similarity obtained by comparing the actual data is equal to or greater than a reference value as a similar file.

Images