JP3279136B2 - File management device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file management apparatus for managing files, and more particularly, a paper document, an electronic document created by a computer or a facsimile machine, and various media including moving images and audio information. File management device in a distributed office environment. In this specification, unless otherwise specified, the term file is used in a broad sense including electronic documents and the like.

[0002]

2. Description of the Related Art Conventionally, in order to manage files in a distributed environment, a directory or a drawer / folder or the like is freely created using a file server system or an optical file system on a network, and the files are stored therein. By storing it in a folder, it can be shared.

As an apparatus for managing files, for example, there is an apparatus described in Japanese Patent Application Laid-Open No. 4-188241. This apparatus has a function of simultaneously performing search and entity retrieval processing on different data via the data management server means, the entity server means, and the network means, thereby efficiently performing the data retrieval processing and the retrieval processing. It is executed at the same time to reduce the waiting state.

In Japanese Patent Application Laid-Open No. Hei 4-312140, location information of a folder to which a file should be classified is defined, and location information of a file for identifying a file that can be stored is defined in the folder.
A file management apparatus for automatically classifying files according to their location information is disclosed. In this file management device,
When storing a file, the file is automatically categorized according to the location information of the folder defined in the file, and if there is no corresponding folder,
Create a new folder.

Further, a structured document classifying apparatus described in Japanese Patent Laid-Open No. 5-89173 searches for a document based on the structural element information of the structured document, and classifies the searched document according to the specified structural element information. Thus, a plurality of structural element information can be specified, whereby a multi-stage classification structure can be created.

[0006]

However, a file management system using a file server system or an optical file system on a network has the following problems.

The file to be managed must depend on the function of the file system provided by the operating system on which the file server system or the optical file system operates. For this reason, when files are created by various types of workstations and personal computers, which are increasing in recent offices, a distributed system suitable for each is constructed, and a file server system or an optical file system is constructed for each system. Must be managed by establishing

When managing files on each file server system or optical file system, a drawer / folder name that can be understood by group members is created for each work group, and a file related to the drawer / folder name is created there. Will be stored and shared managed. Therefore, in order to classify and manage the files, naming of the drawer / folder that can understand the meaning and the complexity of creating the names will occur.

The purpose of a file management apparatus such as a shared file server system and an optical file system in a conventional distributed environment is to share and manage files. To use a shared file, you need to find the file and copy or move it to your workstation or personal computer, or convert the contents to a file that suits your environment. . So, while sharing files,
Only after the complicated operation as described above can the user actually use it.

Conventional file management apparatuses such as a shared file server system and an optical file system in a distributed environment can only handle attributes defined by a file system provided by an operating system on which they operate. In addition, it is not possible to perform meaningful management for each user or workgroup. In other words, a target file is found by tracing a predetermined drawer / folder, and a file existing under the intention of the user is classified by copying or moving to another drawer / folder for different management. Even in such a case, different file systems can only operate with a common file name. However, it is difficult to remember the contents only from the file name.

When various shared file server systems and optical file systems exist on a network in a distributed environment, there are communication means and access methods to the file systems that are suitable for the systems. Therefore, when a user accesses a file on the above-mentioned system in a plurality of different environments, the environment of each communication means and access method is prepared, and an authentication method and security suitable for the system are also supported. And user registration (user account registration) for a plurality of systems is required.

In the file management apparatus disclosed in Japanese Patent Application Laid-Open No. Hei 4-312140, data is stored in folders based on location information. Basically, a folder hierarchy must be created by a user. The location information as to whether or not to be classified into a folder is in a format for designating a folder on a one-to-one basis. For this reason, when files are classified in a multi-stage classification structure, for example, a file is first classified according to a file type such as “specifications” or “minutes”, and then further classified into, for example, “projects”. Corresponding location information must be created. In this file management device, if there is no corresponding location information,
A new folder is created, but the created folder is only listed in a flat manner because there is no specification of where to create the folder. As described above, the classification based on the location information of a file is one stage, and it is not possible to make detailed settings such as classifying the file into another folder under a certain folder. Also, if the attribute is changed or the document is deleted,
The only way to reflect the result in the classification structure is to perform reclassification. Moreover, there is no explicit description in this publication that a plurality of classifications are defined simultaneously.

Further, in the structured document classifying apparatus disclosed in Japanese Patent Application Laid-Open No. 5-89173, a classification structure based on folders is created based on structural element information of a structured document, and the documents are classified. Unlike the file management apparatus disclosed in JP-A-4-312140, a multi-level classification structure can be created by specifying a plurality of classification attributes. However, in the multi-stage classification, the folder classified by file type always has a structure that is classified as "project", for example, the "spec" is classified as "project", and the "minutes" You can not make detailed settings such as sorting by "date" below. When the attribute is changed or the document is deleted, the only way to reflect the result in the classification structure is to perform re-classification. Moreover, since only classification based on structural element information is provided, arbitrary hierarchical classification of a user in a normal file system cannot be performed.

[0014] The present invention has been made in view of the above points, and stores and retrieves a file according to a user's use method in an office environment that realizes distributed information processing constructed by various file creating apparatuses. It enables shared management of retrieval and storage of existing files on various existing file server systems and optical file systems, and accesses the stored information on existing networks. It is an object of the present invention to provide a file management device capable of accessing a file on a file server system or an optical file system.

Another object of the present invention is to provide a file management apparatus which classifies files including files on an existing file server system or optical file system existing on a network and can perform fine classification according to the purpose. And

Further, the present invention provides a file management apparatus which can classify files including existing files on an existing file server system or optical file system existing on a network and simultaneously perform different classifications according to purposes. The purpose is to do.

[0017]

According to a first aspect of the present invention, there is provided:
A file management device that manages files
Classification structure consisting of hierarchical structure of files,
Attributes, the node and the files classified immediately below the node.
Link information when a link was set between the
Storage means for storing the classification condition of each node (4 in FIG. 23)
10, 420) and the classification condition for the node is set.
Setting means (430 in FIG. 23) for performing
The value of the attribute as the classification attribute of the file is used as the value of the classification condition.
Value of the relevant classification attribute when there is no node in the classification structure
Create a node with
Creating means for associating with a related node (see FIG. 23)
440), the attribute of the file to be classified and the
Node to classify the file from
Link between the file and the determined node.
Automatic classification means (450 in FIG. 23).
ing.

[0018]

Further , the file management apparatus according to the second aspect of the present invention provides a classification structure having a hierarchical structure of nodes for classifying files, an attribute of a file to be classified, the node and files classified immediately below the node. Link information when a link is set between, the classification condition of each node, the classification target file management information for managing the classification target file, and the link between the classification target file management information and one or more of the classification structures. Storage means (610, 620 in FIG. 36) for storing link information when a link is set in a group; a classification condition for the node; and a link between the classification target file management information and one or more of the classification structures. The setting means (630 in FIG. 36) for performing the classification and the node having the value of the attribute as the classification attribute of the classification target file as the value of the classification condition Creating means for performing the creation of the node with the value of the classification attributes when not in concrete, and a relationship with a node associated with the node and the node created (6 in FIG. 36
40) determining a node of the one or more classification structures for classifying a file from the attribute of the file to be classified, the file management information of the classification target, and the classification condition of the node; The automatic classification structure means (650 in FIG. 36) for setting a link between them.

Further, in the file management apparatus according to the third invention, when a file is registered in the node with respect to the configuration of the first or second invention, among the attributes of the file, the user-set attribute is not set. Sometimes, at least a storage attribute setting unit that sets the value of the attribute of the classification condition of the node (FIG. 2)
3 (460 in FIG. 36 or 660 in FIG. 36). Preferably, the attribute values of the classification conditions of all higher-level nodes of the node are also set.

Further, in the file management apparatus according to a fourth aspect of the present invention, in the first or second aspect , the classification condition of the node comprises a classification attribute and a classification constraint. These are directories, drawers and folders, and the files to be classified are managed in cabinets.

Preferably, the links between the nodes, between the files and the nodes, and between the classification target file management information (for example, a part of the management information of the cabinet) and one or more of the classification structures are mutually linked. It is a two-way link by having an identifier.

[0023]

According to the file management device of the first invention, the setting
The means define, at each hierarchical level, the classification below it. Automatic
The classifying unit is configured to store the attribute of the file stored in the storage unit and
Classification conditions for nodes set by the setting means (for example,
Classify files based on the drawer / node)
Determine and classify nodes. At this time, the creation means is classified
Whether there is a node that has an attribute to be classified as a classification condition, etc.
Create / delete nodes according to. Classified nodes
Is stored in the storage means.
By classifying them according to the values of file attributes,
Existing file server system existing on the network
And the burden of managing files on the optical file system
Can be reduced.

[0024]

According to the file management apparatus of the second invention, classification target file management information (for example, cabinet management information) for managing classification target files is further stored in the storage means, and the setting means stores the classification target file management information. The classification target file management information (for example, a cabinet) and one or more classification structures (for example, a drawer as a top node)
By designating, it is possible to simultaneously execute a plurality of different classifications according to the purpose on files on the existing file server system or optical file system existing on the network.

Further, according to the third aspect , when a file is specified and stored in a node (for example, a folder) having a classification structure, for example, when a file is stored in a folder, the attribute value set by the user is not stored in that folder. At the time of setting, at least the attribute value of the classification condition of the folder, preferably the attribute value of the classification condition of the upper folder / drawer of the folder is set by the storage attribute setting means. No need to specify user attributes when registering.

According to the fourth aspect of the present invention, a classification condition of a node (for example, a drawer / node) is set by using a classification constraint together with a classification attribute. Since files having values can be classified into, for example, "other" folders, the classification can be performed efficiently.

[0028]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS First, an outline of a file management apparatus according to the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing the principle of a file management apparatus according to the present invention. The file management device receives a plurality of processing requests such as registration, search, and retrieval from a plurality of file creation devices (that is, client devices) 6a and 6b. Filing model control means 2 for performing basic filing operations and file classification, external file management means 3 for cooperating with different external file systems, and attribute content management means 4 for managing file attributes and contents. Have.

The file management device is connected to the file creation devices 6a and 6b via the network 5, and the file creation devices 6a and 6b request processing using a software interface for accessing the file management device. Is configured to normalize.
For this reason, the processing request receiving means 1 uses the file creation device 6
Since the processing requests are normalized in a and 6b, various information media can be received in the same row.

The filing model control means 2 performs basic filing operations, that is, generates, copies, and moves files. Further, using a filing model including a classification structure having a hierarchical structure of nodes, the files created by the file creation devices 6a and 6b are stored, and it is possible to simultaneously perform classification from one or a plurality of viewpoints.

The external file management means 3 has a communication means for accessing each of the external file systems 7a and 7b.
Various network file systems 7a and 7b existing in the distributed environment can be accessed. In addition, the external file management means 3 is provided with external file systems 7a, 7
Create a reference to access files residing b, allows to manage external file system 7a by using a file of this reference, the file 7b is managed as a file within the file system ing.

The attribute content management means 4 stores file attributes required for filing and stores actual contents as files of a file system depending on the operating system. When a plurality of file management devices according to the present invention are present on a network, the attribute content management means 4 centrally manages attribute information for exchanging files stored between the devices on the network. .

Hereinafter, embodiments of the file management apparatus of the present invention will be described in detail with reference to the drawings. FIG. 2 is a block diagram showing the configuration of an embodiment of the file management device according to the present invention.

The file management apparatus (hereinafter, abbreviated as “this apparatus”) of the present embodiment includes a processing request receiving unit 10 for receiving various processing requests, a filing model control unit 20 for performing basic filing operations, and a distributed environment. An external file system access control unit 30 for making available various existing network file systems, and an attribute content management unit 40 for managing the attributes and contents of files are provided. The external file system access control units 30 are respectively provided with external file system access units 32a, 32b,... Provided to access a plurality of external file systems 31a, 31b,.
.. Are accessible. The attribute content management unit 40 includes an attribute storage unit 41 for storing attributes required for filing, a document content storage unit 42 for storing the contents of a file (for example, a document file) as a file of a file system depending on the operating system, Attribute definition management unit 43 that manages attribute definitions
And connected to.

The present apparatus also includes an application management unit 50 for managing a user-created processing program (referred to as an application in the present embodiment), and a plurality of application processing units 51a for processing these applications.
51b,..., An additional function processing unit 60 that processes additional functions such as printing / mail requested from the printing / mail system 61 existing in the distributed environment, and controls and manages each unit in the apparatus. A server control management unit 70 and a resource information management unit 80 for managing resources on the network
And the resource information management unit 80 and the attribute definition management unit 43
And an object information management unit 90 for managing data handled by the object as an object.

Although not shown, a file creation device and a document input / output device on a network are connected to this device. These devices include image input / output devices (copiers, facsimile machines), workstations,
Personal computers and those equipped with a scanner device, etc., are applicable, such as inputting a paper document as an image, issuing processing requests such as file registration / deletion / search, and filing a stored file as a filing model. It is possible to issue a processing request for displaying a classification by using a print command, or for printing out a corresponding printout to a printing apparatus.

Here, the minimum unit to be managed, such as a document, is called a file, and the storage location of the file is called a cabinet, and the file always belongs to any one of the cabinets. It is also assumed that the drawer has a function of classifying a group of files in a designated cabinet using folders belonging to the drawer.

The processing request receiving unit 10 is basically an access point accessed from the various file creation devices 6a and 6b, and can handle a plurality of processing requests. Devices for accessing a file system or an optical filing system existing on a conventional network are mainly devices for creating electronic documents such as workstations and personal computers. These devices include:
A software interface for accessing the apparatus is provided to normalize processing requests, thereby accepting a paper document, a paper document from a remote place (that is, a document by a facsimile apparatus), and various information media. Becomes possible.

The filing model control unit 20 is a central part of file management provided by the present apparatus, and is a part for realizing a conceptual model of the filing function. The components (objects) of the filing model managed by the filing model control unit 20 include a file,
There are folders, drawers and cabinets. The file is
Each of which has its own content and attributes associated with it,
It is a unit of storage and retrieval. In this embodiment, the files are stored and managed in a cabinet, and in the cabinet, the files can be classified from a plurality of viewpoints simultaneously using a drawer and a folder. Further, the filing model control unit 20 has functions such as basic filing operations and associated automatic classification, arbitrary classification, and attribute search. Further, the filing model control unit 20 has a communication unit (C in FIG. 18) and an access method (that is, a communication function) with the attribute content management unit 40.
When a plurality of files exist in a distributed environment, it is possible for the user to perform basic filing operations without being aware of each other. This will be described later in detail with reference to FIG.

External file system access control unit 30
Are the external file system access units 32a, 32b,
, Through which the various network file systems existing in the distributed environment can be individually accessed, and the information of the files existing in the various network file systems is stored in the apparatus as reference information (also referred to as reference). It has a function of mapping information for creating necessary information for the user, and a function of searching for a file from the corresponding network file system and providing it to the user when the user tries to open the registered reference information. are doing. The user authentication when accessing the corresponding network file system from the external file system access control unit 30 is registered and managed in the resource information management unit 80 as user information necessary for accessing the external system. I have. As described above, the external file system access control unit 30 fetches the files that existed separately in the distributed environment and replaces the attributes with the attributes of the internal file format, or manages the information for the replacement and manages the external information. File is related to the internal file. As a result, the filing model control unit 20 classifies and manages the external files that existed separately and the internal files that are directly managed by the present apparatus in one system, that is, the present apparatus. It becomes possible to do.

The attribute content management unit 40 stores the file attributes required for filing defined by the apparatus in the attribute storage unit 41, and stores the actual contents of the file in the document content storage unit 42 in a file dependent on the operating system. Store as a system file. The attribute storage unit 41
Has a mechanism for supporting various storage systems, and includes various databases and file systems 41a.
It is possible to correspond to.

The attribute definition management unit 43 obtains attribute definitions used when a plurality of apparatuses exist on a network and performs classification using a filing model in each apparatus, and performs centralized management on the network. The function to provide For this reason, even if there are a plurality of the present apparatuses, the contents used in the attributes are the same. Therefore, when the user exchanges files stored between the apparatuses, the apparatus guarantees the definition of the attribute added to each file.

The application management unit 50 activates the application by a function for associating the application with the conceptual model of the filing function of the filing model control unit 20 and various defined triggers, and manages the processing result under the management of the apparatus. It provides a function that can be stored. Therefore, by incorporating various applications conventionally held by the user into the present apparatus, batch processing can be performed.

The additional function processing unit 60 requests a network printer to print files stored in various network file systems existing in a distributed environment, or transmits the files to a remote user by using e-mail or the like. Has a function. In such a case, in the related art, a file is once copied or moved to a user's workstation or personal computer, and a print request is made. However, in this apparatus, a print request and an e-mail transmission request (necessary for each Information must be added,
For example, when a print request is issued, the paper size and number of copies, and in the case of an e-mail, a destination and a copy, each communication means, etc.) are issued, and the requests are executed based on information managed in the apparatus. Can be.

The server control management section 70 controls the operation state / stop state of the apparatus, controls various management sections in the apparatus such as a test function, instructs status information in the apparatus, and executes software of each management section. And management of backup / restore instruction function of stored data. The resource information management unit 80 provides a grouping function for each user who accesses the apparatus and for each work group to be used.
It also has a function of registering / deleting / obtaining information. Further, it also has a function of associating an application program under the management of the application management unit 50 with a cabinet or drawer of a filing conceptual model defined by the present apparatus, or canceling the association.

The resource information management unit 80 performs name management (user / host name,
In addition to functions such as network address or authentication, the system comprehensively manages the entire system in which the apparatus exists. In addition to the name management function (user / group management, user authentication, server-related information, etc.) in the conventional network system, the location of the cabinet on the network, which is one of the conceptual models of the filing function, is managed. and so on. If the user has permission to use the distributed environment in which the apparatus is present, the user differs from the conventional network file system or optical file system (that is, the user specifies the host name to which they are connected). It is possible to access each stored file by registering and managing information on the cabinet of the conceptual model of filing. That is, the user can access only with the conceptual model of the filing function defined by the present apparatus.

The object information management unit 90 is a base of the resource information management unit 80 and the attribute definition management unit 43, and manages data handled by each as an object. An identifier is assigned to the object at the time of registration, and an operation is performed using the identifier.

The present apparatus preferably has a function of supporting a distributed environment as basic electronic document file management, a function of communicating with a remote facsimile apparatus, and an image processing function (registration / output) when an image is input. have. Furthermore, in order to allow the registered file to be accessed from various processing instruction devices or input devices in this device,
It has an image processing unit that generates a unified reduced display image at the time of registration, an application program for image generation, and a search unit that searches for necessary files from stored files (searching from attributes and full text Search).

Most of the conventional document management system and file system in a distributed environment depend on the file system of the operating system in which the document management system and file system are installed. Therefore, complicated and unnecessary man-hours are required to realize user-oriented management. This is necessary, and when the operating system or storage is changed, input of accumulated data (file) is required. However, the file management device according to the present invention realizes user-friendly and user-oriented management. It becomes possible.

It is also possible to mount the resource information management unit 80 including the object information management unit 90 and the attribute definition management unit 43 in a device different from the present device, and to avoid concentration of access traffic to the present device. Can be divided as needed. Basically, the management unit (resource information on the network such as the apparatus (server) information and the user / group) registered in the resource information management unit 80 is handled as one system. That is, if a plurality of separated resource information management units exist on the same network, a plurality of such systems can be constructed.

Further, a system similar to a file management system or a file server in a conventional distributed environment can be configured. That is, even if this apparatus is introduced into an existing distributed environment, there is no need to reconfigure the environment. In addition, a copying machine, a facsimile machine, and the like can be handled as input devices in exactly the same way as conventional handling, and there is no need for a gateway device or the like corresponding to each input device as in the prior art.

Here, registration, retrieval, retrieval, and external registration of an electronic document file (hereinafter, referred to as a document) input from a client device such as a file creation device on a network or a document input device for inputting a paper document as an image. Regarding reference registration, the processing contents of the present apparatus as a server will be sequentially described with reference to FIGS.
FIG. 3 is a flowchart showing the processing contents on the client device side in the case of document registration.

When there is a document registration processing request from the client device to the server (file management device), the client device first confirms that a user interface for accessing the server has been activated (step S1). The user name and password are entered on the activated user interface screen to log in to the server system (step S2). Next, information of a filing model (a cabinet including a cabinet for an external file) is obtained from the resource information management unit 80 (step S3). Here, the external file system 31a,
When the information is registered in 31b,..., The information of the cabinet for external use is selected. Next, a document to be registered is selected, and a registration instruction is issued to the corresponding filing model (cabinet, drawer / folder) (step S4). In the case of registration to the external file systems 31a, 31b,..., The drawer of the corresponding external file system is opened and a registration instruction is issued. Then, it is determined whether registration can be started by the instruction (step S5). If the instruction is incorrect, the process starts again with the selection of the document. If the instruction is correct, a necessary attribute is added to the document to be registered (step S6), and the document registration including the specified attribute for transfer is performed. Request processing, that is, normalization processing of a document to be transmitted is performed (step S7), a request for registration processing is issued to the server, and document registration processing is performed on the server side (step S8). Thereafter, if another document is to be registered subsequently, the process returns to step S4, and if there is no document to be registered, the process ends (step S9).

Next, in the registration processing in the server in step S8, detailed processing contents on the server side from reception of a registration processing request from a client to completion of registration will be described.

FIGS. 4 and 5 are flowcharts showing the contents of processing on the file management apparatus side when a document is registered. First, the processing request receiving unit 10 receives a registration processing request from the client device (step S11). The processing request receiving unit 10 accumulates the received registration processing request and stores the transferred data in the internal data. It is converted into a structure (step S12). Next, the registered document and the additional attribute are registered in the filing model control unit 20 (step S13). It is determined whether the document requested to be registered is of the internal file system or of the external file system (step S14). Here, the document requested to be registered is stored in the external file systems 31a, 31b,.
, A request is issued to the external file system access control unit 30 (step S15), and the document is registered in the external file systems 31a, 31b,... (Step S16). If the document requested to be registered belongs to the internal file system, the filing model control unit 20 determines whether a service application is registered in the corresponding filing model (step S17). It is determined whether the application is activated at the time of registration (step S18). When the service application is activated at the time of registration, a request is made to the application management unit 50 for processing (step S19), and the application management unit 50 activates the corresponding application (step S2).
0), and returns the processing result to the filing model control unit 20 (step S21). The determination in step S14 is at the position shown in the present example, but may be at a position after step S21.

If the service application is not registered in the corresponding filing model in the judgment in step S17, if the service application is not activated at the time of registration in the judgment in step S18, and if the filing model control unit 20 is If the processing result is returned to, next, various attributes are checked for the document for which registration has been requested (step S22).
Here, it is determined whether or not the corresponding filing model has an automatic classification designation (step S23). If so, the classification process is performed on the corresponding part of the filing model (step S24). If no automatic classification is specified,
Alternatively, when the classification process is completed, the attribute content management unit 40
Request the registration process (step S25), store the attributes and contents of the registered document in the attribute storage unit 41 and the document contents storage unit 42 (step S26), and end the process.

Next, a description will be given of the processing contents when the client device retrieves and searches the registered document from the server. FIGS. 6 and 7 are flowcharts showing the processing contents on the client device side in the case of extracting a registered document from a document.

When a client device requests a server (file management device) to retrieve a registered document, the client device first confirms that a user interface for accessing the server has been activated ( Step S31), and log in to the server system using the activated user interface screen (step S32). Next, filing model (cabinet) information is acquired from the resource information management unit 80 (step S33), the corresponding cabinet is opened, and lower-level filing model information is acquired from the server (step S34). It is determined whether or not the corresponding file is searched (step S35). If the file is searched, a search processing request is issued to the server (step S36).
Here, it is determined whether or not the information of the corresponding file has been obtained from the server (step S37). If not, it is determined again whether or not to perform the search process (step S38). If the search is to be performed again, the process returns to step S36. In step S37, when the information of the corresponding file can be obtained from the server, the filing model is sequentially opened to search for the corresponding file (step S39). Here, it is determined whether the corresponding file is found (step S40), and if not found, the process returns to step S33.

If the corresponding file is found in the determination in step S40, if the corresponding file is not searched in the determination in step S35, and if the search is not performed again in step S38, the server It is then determined whether or not acquisition of file contents is requested (step S41). When requesting acquisition of file contents, the server issues a contents acquisition processing request to the server to acquire file contents from the server (step S42). Subsequently, it is determined whether to request the server to change the attribute (step S4).
3). When the attribute change is requested, an attribute change processing request is issued to the server to change the attribute (step S44). Finally, it is determined whether or not to end the process of extracting the registered document (step S45). To continue, the process returns to step S34.

Next, the contents of the search processing in the server in step S36 will be described. FIGS. 8 and 9 are flowcharts showing processing contents on the file management apparatus side in the case of searching for a registered document.

When searching for a registered document, first, the processing request receiving unit 10 receives a search processing request from the client device (step S51), and the processing request receiving unit 10 stores the received search processing request. Then, this search processing request is converted into internal information (step S52). Next, a search request process is registered in the filing model control unit 20 (step S53). Here, it is determined whether the search processing request is an attribute search or a full-text search (step S54). In the case of the full text, a request for starting the full text search application is made to the application management unit 50 (step S55), and the application management unit 50 starts the full text search application and executes the full text search processing (step S56). In the case of an attribute search, a search condition is added to the attribute content management unit 40 to request a search process (step S57). The attribute content management unit 40 accepts the search process request (step S58), and executes the search process. Perform (step S59). Thereafter, a search result file is created by the application management unit 50 or the attribute content management unit 40 (step S60), and is passed to the filing model control unit 20 (step S61). Then, the filing model control unit 20 uses the search result file as a processing result for the search processing request as a processing result
(Step S62), the processing request receiving unit 10 creates response data for the search processing request, and returns it to the client (step S63).

Next, the flow of processing in the server for the content acquisition processing issued in step S42 of FIG. 7 will be described. FIGS. 10, 11 and 12 are flowcharts showing the processing contents on the file management apparatus side in the case of the contents acquisition processing.

When there is a request for content acquisition processing from the client device, first, the processing request receiving unit 10 receives a content acquisition processing request from the client device (step S).
71), the processing request receiving unit 10 accumulates the received content acquisition processing request, and converts the content acquisition processing request into internal information (step S72). Next, a content acquisition request process is registered in the filing model control unit 20 (step S73). Subsequently, it is determined whether the corresponding filing is a reference or a real electronic file (step S7).
4) If it is a reference, it is determined whether the reference is an internal reference or an external reference (step S75). Here, if the corresponding file is a real electronic file and is an internal reference, a content acquisition request process is registered in the attribute content management unit 40 (step S76). Next, the attribute content management unit 40 receives the content acquisition request (step S77), and based on the corresponding file information, stores the file in the filing model control unit 20.
(Step S78). The filing model control unit 20 returns the file to the processing request receiving unit 10 as a processing result for the content acquisition request processing (step S7).
9), the processing request receiving unit 10 creates response data for the content acquisition request and returns it to the client device (step S80).

On the other hand, if it is determined in steps S74 and S75 that the corresponding file is a reference and the file is an external reference, an information acquisition request process for the corresponding reference is registered in the attribute content management unit 40 (step S81). . Next, the result for the information acquisition request is passed to the filing model control unit 20 (step S82). The information acquisition request process is registered in the external file system access control unit 30 (step S8).
3). The corresponding external file systems 31a, 31b,
.. Are started (step S8).
4), the external file system access control unit 30 obtains information necessary for user authentication when logging on to the corresponding external file system from the resource information management unit 80 through the server control management unit 70 (step S8).
5). External file system 31 corresponding to this information
, 31b,..., and retrieves the corresponding file (step S86), and passes the result to the information acquisition request to the filing model control unit 20 (step S87). The filing model control unit 20 passes the processing result to the processing request receiving unit 10 (step S8).
8) Then, the process proceeds to step S80.

Next, a description will be given of the processing performed when the client device registers an external reference to the server. FIG. 13 and FIG. 14 are flowcharts of processing on the client device side at the time of external reference registration.

First, the client device confirms that the user interface for accessing the server has been activated (step S91), and logs in to the server system using the activated user interface screen (step S92). Next, the resource information management unit 8
0, the information of the filing model (cabinet) is obtained (step S93), and the external file system 31 is obtained.
It is determined whether there is a cabinet for accessing a, 31b,... (step S94), and if not, the process returns to step S93. External file system 31a,
If there is a cabinet for accessing 31b,..., A corresponding system is found from the external file system access cabinet, and a file for which a reference is to be created is searched (step S95). Here, for example, the system is a drawer unit. When searching for a file, the server obtains user information (authentication information; user name, password) for accessing the external file systems 31a, 31b,... From the resource information management unit 80. For example, the information is obtained from a correspondence table between the authentication information of the apparatus and the authentication information of the external file system corresponding to the user. The external file systems 31a, 31b,... Are accessed based on the user information. Then, a reference registration request processing request is issued to the server, and the processing result is obtained (step S96). Finally, it is determined whether the processing is completed (step S9).
7) If further registration processing is required, step S93
Return to

Next, the server-side processing of the reference registration request processing will be described. 15, 16, and 17
9 is a flowchart showing the reference registration request processing on the file management device side.

As described above, when the reference registration request processing request issuance processing is performed on the client device side, the processing request receiving unit 10 receives the reference registration request issued from the client device side (step S101). The processing request receiving unit 10 accumulates the processing request and converts the processing request into internal information (step S102). After performing the internal processing, the processing request receiving unit 10 registers the contents of the request in the filing model control unit 20 (step S103). Next, it is determined whether the file of the reference registration request is in the internal document storage unit or in the external file system (step S10).
4). Here, if the file of the reference registration request is in the internal document content storage unit 42, the filing model control unit 20 registers the processing request in the attribute content management unit 40 (step S105). Next, the attribute content management unit 40 receives a reference registration request (step S10).
6) The attribute content management unit 40 creates a file reference in the document content storage unit 42 and registers it in the attribute storage unit 41 (step S107). Then, the processing result of the registration processing is passed to the filing model control unit 20 (step S108). Next, the processing result for the reference registration request is returned from the filing model control unit 20 to the processing request receiving unit 10 (step S109), and the processing request receiving unit 1
From 0, response data to the reference registration request is created and returned to the client that issued the reference creation request (step S110).

On the other hand, according to the determination in step S104, the file for creating the reference is
.., The filing model control unit 20 registers a reference creation request process with the external file system access control unit 30 (step S111). Next, the external file system access control unit 30
a, 32b,..., the external file system is accessed, and information (server name, volume name, path name, etc.) necessary for accessing the corresponding file is obtained (step S112). The system access units 32a, 32b,... Obtain the external attribute information of the file and convert it to the internal attribute information. The external file system access control unit 30 creates the internal attribute information necessary for registration as a reference. The file is passed to the filing model control unit 20 (step S113). Then, the filing model control unit 20 registers a reference registration request in the attribute content management unit 40 (Step S114), and proceeds to Step S106.

Next, an example of a mutual access method between the present devices when a plurality of the present devices exist on one network in a distributed environment will be described with reference to FIG.
In FIG. 18, two file management apparatuses 100 and 200 according to the present invention are connected via a network 300. Each of the file management devices 100 and 200 has the same configuration, and includes processing request receiving units 110 and 210, filing model control units 120 and 220, attribute content management units 130 and 230, attribute storage units 140 and 240, respectively.
Operating system dependent file system 15
0,250.

Filing model control units 120 and 220
Has a communication means and an access method with the attribute content management units 130 and 230, and enables the user to perform the basic filing operation without being conscious of each other. For example, the filing model control unit 120 of the file management apparatus 100 can designate a file of information that refers to a file managed by the file management apparatus 200 as a file stored and managed in the cabinet. When a user other than the user who registered the file views the cabinet of the file management apparatus 100, the file of the file management apparatus 200 is accessed using the communication means C indicated by a broken line. Therefore, the user can use the file management device 200
There is no awareness that the file is being accessed.

Filing model control units 120 and 220
In, a file is managed by identifier information, and the identifier information includes reference information (having a file identifier) when the file is in another file management device (server). Therefore, for example, when the processing request receiving unit 110 of the file management apparatus 100 receives a processing request to open a specified file based on, for example, information of a file search result, the filing model control unit 120 stores identifier information of the specified file. Accordingly, it is determined whether the requested file is a file managed by the file management apparatus 100 or a file managed by the file management apparatus 200. If the target file is a file managed by the file management device 100, the filing model control unit 120 performs an open process on the file specified through the attribute content management unit 130, and the target file is a file managed by the file management device 200. , The communication path indicated by the broken line and the attribute content management unit 1
The process of accessing the file specified through the reference 30 by the file identifier of the reference information and opening the file is performed.

As described above, in a distributed environment, when a plurality of the present apparatuses exist on the same network, mutual access is performed between the present apparatuses, so that the user can determine on which apparatus the necessary electronic document or file exists. It is not necessary to consider the filing model and the classification defined by the present apparatus.

The reference information about the external file includes a part having all the attributes of the external file corresponding to the internal attribute of the file managed by the file management apparatus, and a part having only different attributes. There is. The latter part is managed in the form of a difference information file. Here, how to manage reference information of an external file, particularly, a difference information file will be described.

FIG. 19 is a block diagram showing another example of the configuration of the file management device. In the figure, the same blocks as those shown in FIG. 2 are denoted by the same reference numerals, and the parts not involved in the management of the difference information file are omitted. According to this figure, an operating system dependent file system 33 is connected to the external file system access control unit 30.

According to the management of the difference information file, at least the following two cases can be considered as storage locations of the difference information file. In any case, the reference information of the external file is stored in the file 1 of the apparatus.
The attribute “reference” is stored in the attribute content management unit 40.

As a first example, there is a case where the difference information file is stored in the operating system dependent file system 33. In this case, the external file system access control unit 30 manages the difference information file stored in the operating system dependent file system 33.

Further, information exchange occurs between the external file system access control unit 30 and the resource information management unit 80 for management / reference of the authentication information for accessing the external system.

The second example is a case where the difference information file is stored in the attribute content management unit 40. The external file system access control unit 30 directly controls the attribute content management unit 40 for managing the difference information file.

However, information exchange occurs between the external file system access control unit 30 and the resource information management unit 80 for management / reference of authentication information for accessing the external file system.

Reference information of an external electronic document or file is taken into the attribute content management unit 40 as a “reference”. The details of the processing will be described. FIG. 20 is a flowchart showing a detailed flow of processing after the filing model control unit for taking in external information (reference registration) receives a processing request.

First, when the filing model control unit 20 receives a reference creation processing request through the processing request receiving unit 10 (step S121), the filing model control unit 20 stores the reference creation file (source file) in the internal file ( It is determined whether the file is a local file or an external file (step S122). Here, if it is determined that the file is an external file, it is determined whether the system is the same system as the main device (of course, the device in the case of a single device) when there are a plurality of devices (step S12).
3) If the system is the same, the same processing as the internal file is performed. If it is determined in step S123 that the system is not the same as the main file management device,
The filing model control unit 20 requests the external file system access control unit 30 for processing, and the requested external file system access control unit 30 accesses the external file management system 31a or 31b through the external file system access unit 32a or 32b, The attribute information is obtained (step S124). Next, an attribute value that can be mapped to an internal attribute is converted (step S125), a portion having no corresponding attribute is written to a file as difference information (step S126), and a file in which the difference information is written (hereinafter referred to as a difference information file) )
To the operating system dependent file system 3
3 or stored in the attribute content management unit 40 (step S1).
27). Then, the filing model control unit 20 creates a reference in the attribute content management unit 40 based on the attribute information created by the external file system access control unit 30 (step S128).

In order to create a reference, it is necessary to provide information for identifying a reference destination file. Normally,
File identifier, but if external, the system name and file name of the external file (or information for accessing a file in the external file system such as a path name)
Is given. These pieces of information are used for external access and are set as reference attributes.

The attribute information to be set as the reference, including the difference information file name and the reference update date and time when the reference is created, is created by the external file system access control unit 30.

When accessing a file in the external file system, access is made through reference information. The details of the processing operation after the filing model control unit receives the processing request at this time will be described separately for the case of extracting the contents of the file and the case of extracting the attributes.

First, the processing for extracting the contents of a file will be described with reference to the flowchart of FIG. Filing model control unit 20 through processing request receiving unit 10
Receives the reference content acquisition processing request (step S131), the filing model control unit 20 acquires the value of the “system name” attribute of the reference from the attribute content management unit 40 (step S132). Here, the filing model control unit 20 determines whether the file (source file) whose content is to be acquired is an internal file or an external file from the acquired attribute values (step S1).
33). Here, when it is determined that the file is an external file, it is determined whether the file is the same system as the main apparatus (server) (step S134). Step S133
If it is determined in step S134 that the file is an internal file, or if it is determined in step S134 that the file is the same system, the content is accessed by accessing the attribute content management unit 40 of the corresponding server (step S135). On the other hand, if it is determined that the file is an external file and is not the same system as the main server, the filing model control unit 20 receives the authentication information for accessing the external file system from the resource information management unit 80 (step S13).
6) Access the external system to acquire the contents of the file (step S137).

Next, the process for acquiring the attribute value of a file will be described with reference to the flowchart of FIG. First, when the filing model control unit 20 receives a reference attribute acquisition processing request through the processing request receiving unit 10 (step S141), the filing model control unit 2
0 acquires the value of the "system name" attribute of the reference from the attribute content management unit 40 (step S142). Here, the filing model control unit 20 determines whether the file (source file) whose attribute is to be acquired is an internal file or an external file from the acquired attribute value (step S143). If it is determined that the file is an external file, it is determined whether the file is the same system as the main file management device (server) (step S14).
4). If it is determined in step S143 that the file is an internal file, or if it is determined in step S144 that the file is the same system, the server accesses the attribute content management unit 40 of the corresponding server to acquire the attribute (step S145). On the other hand, if it is determined that the file is an external file and is not the same system as the main server, the filing model control unit 20 receives the authentication information for accessing the external system from the resource information management unit 80 (step S146), The external file system is accessed to acquire the “update date and time” attribute (step S14)
7). Here, it is determined whether or not the internal information is old by comparing with the “update date and time” attribute stored internally (step S148). If the internal information is old, the external file system is accessed to acquire the attribute (step S149). If the internal information is the same, the attribute is acquired from the information in the difference information file and the information mapped to the reference (step S149). Step S150). In this way, when acquiring the attribute value of the file of the external system through the reference information, instead of simply acquiring the external attribute information, the reference destination update date and time when the reference information was created and the external file are stored in the external file. The date and time when the change was made are compared, and only when the information taken in is old, the outside is accessed to rewrite the attribute information. Next, a function of hierarchically classifying electronic documents and files according to their attribute values will be described with a focus on the filing model control unit. Before that, objects to be classified, that is, files, drawers /
A specific data format of the folder and the cabinet will be described.

First, a file is composed of contents and attributes. There are three types of attributes: basic attributes, extended attributes, and internal attributes. Basic attributes are attributes that are uniquely defined in advance in the system. Specifically, attribute values such as “identifier”, “title”, “creation date and time”, “creator”, “content size”, and file For example, there is a "belonging cabinet" representing a stored cabinet. Extended attributes are attributes that are additionally defined according to the purpose of the user. The attribute types are "character string", "integer", "date and time", "logical value (true / false)", and "byte string".
There is. These basic attributes and extended attributes are provided directly to the user and can be managed by the user. Internal attributes are attributes used in the system and are not disclosed to the user. A specific example of the internal attribute is a “folder list”, which is a list of drawer or folder identifiers into which files are classified.

The drawer / folder has no contents, and all necessary information is held as attributes. However, unlike files, the types of attributes are only basic attributes and internal attributes, and extended attributes cannot be defined. Specific examples of the basic attributes of the drawer / folder include "identifier", "title", "creation date", "creator", "classification condition", and the like. The internal attributes include a “file list”, which is a list of identifiers of files classified by the drawer / folder, a “folder list”, which is a list of identifiers of folders immediately below the drawer / folder, and a drawer / folder.
There is a "parent folder" representing the folder immediately above the folder, and a "cabinet list" representing the identifier of the cabinet to be classified. In the case of a drawer, since the drawer itself has the highest-level structure, the value of “parent folder” is not set.

The cabinet also has only the attribute types of the basic attribute and the internal attribute. Basic attributes include "identifier", "title", "creation date", and "creator". Internal attributes include "drawer list", which is a list of drawer identifiers for which cabinets are to be classified, and cabinets. There is a "file list" which is a list of identifiers of files belonging to.

Next, an example of the function of hierarchically classifying files by their attribute values, centering on the filing model control unit 20, will be described in detail. FIG. 23 is a block diagram showing a basic configuration of the document classification device in the file management device.

The document classification device includes a document storage unit 410, a classification structure storage unit 420, a classification condition setting unit 430, a classification structure creation unit 440, an automatic classification unit 450, and a control unit 46.
0 and a display unit 470. Here, the document storage unit 410 and the classification structure storage unit 420 correspond to the attribute content management unit 40 shown in FIG. 2, and the classification structure creation unit 440, the automatic classification unit 450, and the control unit correspond to the filing model control unit 20. The display unit 470 is a file creation device 6a, 6b or a file management device (server).
Corresponding to That is, for the display unit 470, based on the output of the file management device, the file creation device 6a,
6b, or when the file management device is operating alone, it is displayed on its own display unit.

The document storage unit 410 stores a document file
This is the part that stores the contents and attributes of a document.
The document storage unit 410 also stores link information to drawers / folders into which documents are classified.

The classification structure storage section 420 is a part for storing a classification structure composed of a drawer / folder, and also stores the classification conditions specified for the drawer / folder and the link information to the document classified immediately below. In this embodiment, the object at the top of the classification structure is particularly called a “drawer”.
Documents stored in the document storage unit are classified immediately below a drawer for which classification conditions are not specified. Note that a portion for creating a drawer is omitted here.

The classification condition setting section 430 sets classification conditions for the drawer / folder or changes the classification conditions that have already been set by designating the classification conditions. The minimum information required as a classification condition is “attribute used for classification”, and this attribute is called a classification attribute.

In the case of automatic classification, the classification structure creation section 440 creates a new folder according to the classification. That is, if there is no folder having the value of the classification attribute of the file to be classified, a folder is created. When the classification condition is changed, the corresponding existing folder structure is deleted.

The automatic classifying unit 450 determines the attribute of the document and the drawer /
A drawer / folder for classifying documents is determined from the folder classification conditions, and a link is established between the document and the drawer / folder to perform classification .

[0099] The control section 460 is a section for performing overall control of these components, and the display section 470 is a section for displaying the classification results. Here, an example of a classification structure when a classification condition is actually specified is shown. In the following example of the classification structure, the hierarchical structure of the drawer and the folder is indicated by a solid line, and the link relationship between the drawer / folder and the document is indicated by a dotted line.

FIG. 24 is a diagram showing an example of a classification structure when no classification condition is specified. In this figure, five documents 511 to 515 are classified immediately below the drawer 500.
These documents 511 to 515 are stored in the document storage unit 410. As described above, the classification condition is not set, and the drawer 5
A state in which all documents 511 to 515 to be classified are classified into 00 is set as an initial state. Of course, it is also possible to create a drawer by specifying classification conditions.

Here, it is assumed that the attributes and values of the documents 511 to 515 are as follows, for example. For the first document 511, the “document type” attribute is set to “specification”,
The “project” attribute is set to “filing”, the “document type” attribute is set to “specifications” for the second document 512, the “project” attribute is set to “printer”, and the third
For the document 513, the “document type” attribute is set to “specification”, the “project” attribute is set to “printer”, and the fourth
For the document 514, the “document type” attribute is “minutes” and the “monthly” attribute is “April”. For the fifth document 515, the “document type” attribute is “minutes” and “monthly”.
The attribute is “May”.

FIG. 25 is a diagram showing an example of the classification structure when the classification condition is specified in one step. When the classification condition setting unit 430 specifies and sets “document type” as the classification attribute in the drawer 500, the attribute values of the documents 511 to 515 classified immediately below the drawer 500 by the classification structure creation unit 440, here, These folders 521 and 522 are created according to the “specifications” and “minutes”, and the automatic classification unit 450 classifies the documents 511 to 515 into folders 521 and 522 corresponding to their attribute values.

FIG. 26 is a diagram showing an example of the classification structure when the classification condition is specified in two stages. "Specifications" folder 5
When the classification conditions are specified in the folder 21 and the “minutes” folder 522, a two-stage classification structure is created. According to the illustrated example, the “filing” folder 523 and the “printer” folder 524 are created by classifying the “specification” folder 521 under the “project” attribute. The “April” folder 525 and the “May” folder 526 are created by classifying by “monthly”.

The files hierarchically classified as described above are displayed on display unit 470 as follows, for example. FIG. 27 is a diagram illustrating a screen display example of the display unit displaying the classification result in the icon format.

According to the example shown in the figure, the file window 471 displayed on the display unit includes an area 472 for visually displaying the hierarchical structure, and a specific hierarchy in the hierarchical structure displayed in the area 472. An area 473 for displaying existing folders and files as icons is provided.
The illustrated hierarchical structure is a display example of the classification result shown in FIG. That is, there is a drawer at the top, and a “specification” folder and a “minutes” folder are created below the drawer. A “filing” folder and a “printer” folder are created under the “specifications” folder, and a “April” folder and a “May” folder are created under the “minutes” folder. Here, the “printer” folder is selected, and the files classified into the “printer” folder are displayed as icons in the display area 473 on the right side thereof.

FIG. 28 is a diagram showing another example of a screen display on the display unit displaying the classification results in a list format. In the illustrated example, the area 472 displaying the hierarchical structure is the same, but in the area 473 displaying the classified files, the files classified in the “printer” folder are displayed in a list. In this example, each file is displayed with attributes of “title”, “creator”, and “creation date and time”.

Here, the automatic classification unit 450 and the control unit 4
A description will be given of the process of classifying the document group in 60. FIG.
9 is a flowchart showing a flow of a document group classification process.

When the document group is classified, first, all the attribute values of the document immediately below the drawer / folder, that is, the document to be classified are checked (step S161). In this case, the attribute value is the value of the attribute specified in the classification condition. Next, it is determined whether a folder corresponding to the attribute value exists immediately below the operation target (step S162).
Here, if the corresponding folder does not exist, a folder corresponding to the attribute value is created immediately below the operation target, and thereby folders corresponding to all values are created (step S163). It should be noted that there can be a plurality of attribute values, and this is called a multi-valued attribute. If this multi-valued attribute is specified as a classification attribute, a folder is created for each value. Then, a drawer / folder to be classified is determined based on the attribute value (of the classification attribute) of the document. Next, a link is established between the document and the drawer / folder, that is, the document is placed below the determined drawer / folder (step S164). In the case of a multi-valued attribute, a document having the values of the plurality of attributes is classified into a plurality of drawers / folders corresponding to the values of the attributes. In the automatic classification, the documents are classified immediately below the drawer only in the initial state. However, in the case of “mixed with arbitrary classification” described later, the classification may be performed immediately below the drawer. And
The classified document is deleted from the classification target (step S16)
5) It is determined whether or not a document remains in the classification target (step S166). If there are no documents remaining in the classification target, the process is terminated, and if so, the remaining documents are checked for attribute values corresponding to the classification conditions (step S).
Return to 161.

The classification condition can be changed by the classification condition setting section 430. The processing content in that case will be described. FIG. 30 is a flowchart showing the flow of the process of changing the classification condition.

When the classification condition changing process is performed, first, documents classified in the lower structure of the drawer / folder whose classification condition has been changed are added to the classification target, and the documents and the change target drawer / folder are added. All links are disconnected (step S171). Next, it is determined whether there is a folder below the hierarchy to be changed (step S172). If there is a folder, the documents linked to the folder group under the hierarchy to be changed are added to the classification object, the link between them is cut (step S173), and the folder group under the hierarchy to be changed is deleted. (Step S174). As a result, all folder structures in the drawer / folder are discarded. Next, a new classification condition is set for the drawer / folder to be operated (step S175). Then, for the drawer / folder to be changed and the document to be classified, FIG.
9 "classification of document group" is performed (step S176).

FIG. 31 is an explanatory diagram showing a link relationship when the classification attribute is changed. The example of this figure shows a case where the classification attribute of the drawer in FIG. 26 is changed from “document type” to “project”.

In the process of changing the classification condition, at the stage where step S174 of FIG. 30 has been completed, in FIG.
The link relationship indicated by the dotted line between the drawer 500 and the documents 511 to 515 is broken, and the state is such that the links are separated. Here, a classification condition that sets the classification attribute to “project” is set in the drawer 500, and “classification of document group” is performed again on the documents that have been classified before the change. When the classification is completed, as shown in the figure, "Filing" folder 5
23 and a “printer” folder 524 are created, and a folder 527 called “other” is created for a document in which the value of the classification attribute “project” is not set.
I try to categorize them.

Next, the contents of the process of registering a document in the drawer by the control unit 460 will be described. FIG. 32 is a flowchart showing the flow of processing for registering a document in the drawer.

When registering a document in the drawer,
First, the document is stored in the attribute content management unit (step S1).
81). Subsequent steps determine to which drawer / folder the stored document is to be classified.
Next, the drawer is set as an operation target (step S182).
Next, it is determined whether or not the operation target has a classification attribute (step S183). If there is a classification attribute, an attribute value of a document corresponding to the classification attribute set in the drawer is obtained (step S184). Then, it is determined whether the folder corresponding to the attribute value is immediately below the drawer to be operated (step S185), and if so, the folder is set as the operation target (step S186). Then, step S
Returning to 183, the above processing is repeated. Here, if a folder is not included in the corresponding folder (if it is the lowest folder), the folder is a folder to be classified.

In step S185, if there is no folder in the drawer (the drawer in the initial state), the drawer itself becomes a drawer to be classified. If there is no folder corresponding to the attribute value, a new folder corresponding to the attribute value of the document is created (step S187). In this case, this folder is a folder to be classified.

A link is established between the drawer / folder to be classified and the document (step S188). Next, it is determined whether or not all the attribute values have been checked (step S189). If all the attribute values have been checked, the registration process is terminated. It returns to S185.

Note that registering a document directly in a folder is not permitted because the attribute to be classified by the folder and the attribute set in the document may be inconsistent. This solution will be described later in “Storage Attributes”.

Next, the process of re-classification by changing the attribute value of a document will be described. For example, if the attribute value of a document classified in the “April” folder is changed to “May”, the document must be moved from the “April” folder to the “May” folder, Reclassification is performed by changing the attribute value. In this case, the link to the drawer / folder that has already been classified is cut, and a link to a new classification location is established. At this time, a consistency check is performed to avoid useless cutting. In other words, the drawer / folder linked from the document (the place classified by the previous value) is checked to see if there is any inconsistency even in the new attribute value, and if there is any inconsistency, reclassification is performed. The consistency check also considers multi-valued attributes.

The re-classification is also required when a document is deleted. The contents of the process in the control unit 460 in this case will be described. FIG. 35 is a flowchart showing the flow of the re-classification process by deleting a document.

When deleting a document, first, the link between the document to be deleted and all drawers / folders related thereto is cut off, and the document is deleted (step S211). One of the drawers / folders in which the documents are classified (in-law parent, that is, the drawer / folder ahead of the disconnected link) is set as an operation target (step S212). It is determined whether the operation target is a folder (step S21).
3) If it is a folder, it is determined whether or not any documents remain in the folder (step S214). If the folder is empty, delete the folder (step S
215), the parent of the folder is set as an operation target (step S216), and the process returns to step S213.

If the operation target is not a folder in the judgment in step S213 and the folder is not empty in the judgment in step S214, it is judged whether or not all drawers / folders to which the documents are linked have been checked (step S217). , Unchecked drawer /
If there is a folder, the process returns to step S213, and if all drawers / folders have been checked, the process ends.

As described above, when deleting a document, the link to the drawer / folder into which the document is classified is cut, and when the classified folder becomes empty, the folder is deleted. .

According to the above-described document classification device, the classification structure based on the drawer / folder is automatically created, and the documents are automatically classified, so that the burden on file management is reduced. Further, by changing the classification method below each hierarchy, it is possible to perform fine classification according to the purpose. Furthermore, since only a part of the classification can be changed, such as changing the classification of each "project" into groups, maintenance when the classification structure needs to be changed is facilitated. That is,
In the case of a paper document, when the classification is changed, it is necessary to replace the document, but such an operation is not required.
Further, since the operation (attribute change or deletion) of the document can be reflected in the classification, it is easy to maintain and manage whether the classification is correctly performed.

In the above-described document classification apparatus, the case where one classification condition is set by the classification condition setting unit 430 to perform one-stage classification has been described as an example. Classification can be performed collectively. For example, in the classification condition of the drawer or the folder, the classification attribute of the first row is set as "document type", and the classification attribute of the second row is set as "project". According to the batch multi-stage classification, the classification structure creation unit 440 creates the multi-stage classifications collectively according to the settings in the classification condition setting unit 430. Specifically, when a plurality of classification conditions are specified, basically, the change of the classification conditions may be repeatedly applied a plurality of times. Thereby, the trouble of specifying the classification conditions one by one can be reduced.

In the classification condition setting section 430, an attribute value used for classification can be explicitly specified, or a range of the attribute value can be specified. Such conditions are called "classification constraints".
Call. For example, by setting the classification attribute of the drawer or folder to "document type" and the classification constraint to "specifications" and "minutes", only documents having the attributes of "specifications" and "minutes" are classified. , Documents having other values are collectively placed in the “other” folder, and similarly, the classification attribute is set to “year” and the classification constraint is set to “1994 or later”.
By performing the setting that means "from 1994 onwards"
It is possible to classify such that only the documents created in (1) are classified and all the other documents are put in the “other” folder.

The same classification attribute can be specified for the upper and lower folders. Of course, even when there is no classification restriction, the same classification attribute can be specified in the upper and lower folders, but it has no meaning as a classification. In combination with the classification constraint, it is possible to roughly perform the classification in the upper folder and to perform the detailed classification in the lower folder. For example, the same "Date created"
For the top and bottom folders with classification attributes of
The upper folder is classified by year by setting the upper folder classification constraint to "Yearly", and the lower folder is sorted by month by setting the lower folder classification constraint to "Monthly". Can be classified.

However, the same classification attribute /
When specifying a classification constraint, the classification constraint conditions must overlap. If there is no overlap, no documents are classified. For example, "before 1994" and "19
Since the condition "after 1995" is inconsistent, no document satisfies such condition.

As described above, by specifying the classification constraint or using it together with the classification attribute, the control of the classification can be realized, and unnecessary classification can be omitted. Here, the storage attributes will be described. By registering a document in a folder, attribute values required to be classified into the folder are automatically set in the classification structure storage unit 420. This is the control classification 46
This is performed by the storage attribute setting means at 0. For example, when a document is registered in a folder in which a document having a value of “specification” is classified, the value of the “document type” attribute of the document is automatically set to “specification”. This attribute value is called the “storage attribute” of the folder. The storage attribute is automatically set in the automatically generated folder and stored in the classification structure storage unit 420.

In the registered document, not only the storage attribute of the designated folder but also the storage attributes of all higher-order folders are set. When specifying the classification constraint, the storage attribute must be specified by the user. This storage attribute must be consistent with the classification constraint. When specifying the same classification attribute / classification constraint in the upper and lower folders, the storage attribute specified by the user needs to be consistent with all the classification constraints for the same classification attribute.

When the same classification attribute is specified in the upper and lower folders, the storage attributes set in the registered document (corresponding to the same classification attribute) are as follows. (A) When the classification attribute is a single-valued attribute The storage attribute value of the folder closest to the folder in which the document is registered is set. (B) When the classification attribute is a multi-valued attribute The storage attributes of all the folders above the folder in which the document is registered are set.

The storage attribute is applied not only at the time of registration of a document but also at the time of movement / transcription. Therefore, since the attribute is set by specifying the folder, the trouble of setting the attribute at the time of registration is reduced. Also, when a file that has already been classified is changed to another classification, the classification attribute is automatically changed, so that no inconsistency occurs.

FIG. 33 is a flowchart showing the flow of a process for registering a document in a folder. At the time of registering a document in a folder, first, all the storage attributes set in the designated folder and nodes higher than the designated folder are acquired (step S191). Next, the document is stored in the attribute content management unit (step S192). The previously acquired storage attribute is set in the document stored in the attribute content management unit (step S19).
3) A node for classifying the document is determined according to the attribute value of the document (including the value set as the storage attribute) (step S194). This processing is the same as the processing in steps S182 to S189 of document registration in the drawer in FIG.
However, "make the drawer an operation target" in step S182 becomes "make the designated folder an operation target". That is, among the nodes in the designated folder, the node to which the document is to be classified is determined.

Next, details of the process of acquiring the storage attribute information in step S191 in FIG. 33 will be described. FIG. 34 is a flowchart showing the flow of the storage attribute information acquisition process.

When acquiring the storage attribute information, first, it is determined whether or not the storage attribute is set for the target node (step S201). Here, if the storage attribute is set, the storage attribute is a single-valued attribute, and it is determined whether or not it is already recorded (step S2).
02) If not, the storage attribute is recorded (step S203). If the storage attribute has not been set in the determination of step S201,
If the storage attribute is recorded in the determination in step S202, and if the storage attribute is recorded in step S203, it is determined whether or not the parent of the node exists (step S204). Here, if the parent of the node does not exist, it has reached the drawer,
The node becomes a drawer, and this processing ends. If the parent of the node exists, the parent node is targeted (step S205), and the process returns to step S201. In this way, all the storage attributes set in the specified folder and the nodes higher than the specified folder are obtained.

In the classification condition setting section 430, it is also possible to mix the classification by the user in addition to the classification of the document by the attribute value. That is, if the classification is not specified, the document is classified immediately below the drawer / folder. The user creates a folder in such a folder, creates an arbitrary classification structure of the user, and classifies the document. be able to.
The classification by the user is called “arbitrary classification” with respect to the automatic classification based on the attribute value. In addition, a classification condition can be specified for a folder created in an arbitrary classification. Note that a classification change (file operation) unit is required for arbitrary classification, and this is provided in the control unit 460.

By mixing this arbitrary classification with the automatic classification based on the attribute value, it becomes possible to mix with the arbitrary classification of the user. Next, a description will be given of a function of hierarchically classifying electronic documents and files according to their attribute values, with a focus on the filing model control unit, and particularly a classification function capable of simultaneously performing different classifications according to purposes.

FIG. 36 is a block diagram showing a basic configuration of a document classification device in a file management device. The document classification device includes a document storage unit 610, a classification structure storage unit 620,
The classification condition setting unit 630, the classification structure creation unit 640, the automatic classification unit 650, the control unit 660, and the display unit 670 are provided, and reference numerals 410 to 470 in FIG.
Corresponding to the components. The difference from the apparatus in FIG. 23 is that a concept of a cabinet for storing and managing documents to be classified is introduced, and a group of documents managed by this cabinet can be automatically classified by a plurality of classification structures.

In this document classification device, the document storage unit 6
Reference numeral 10 denotes a portion for storing the contents and attributes of the document, and stores information on cabinets in which the document is stored and link information to the classified drawers / folders.

The classification structure storage section 620 is for storing a classification structure composed of drawers / folders. When storing the classification structure, the classification structure for the cabinet is specified. The classification structure storage unit 620 also stores the classification condition specified for each drawer / folder and the link information to the document classified immediately below. Here, in the drawer for which the classification condition is not specified, the document stored in the document storage unit 610 is classified immediately below. Note that a portion for creating a drawer is omitted here.

The classification condition setting section 630 is a part for specifying classification conditions for each drawer / folder. Further, the classification conditions that have already been set are also changed. The classification structure creation section 640 is a section for creating a new folder as needed. In addition, it has a function of deleting an existing unnecessary folder structure when the classification condition is changed.

The automatic classification unit 650 determines all the drawers / folders for classifying the document from the attributes of the document, the cabinet information, and the classification conditions of the drawer / folder, and classifies the document (link between the document and the drawer / folder). Part).

The control unit 660 includes the document storage unit 610, the classification structure storage unit 620, the classification condition setting unit 63
0, a section for performing overall control of the classification structure creation section 640 and the automatic classification section 650.

Here, an example of a classification structure when a plurality of classification structures are actually specified for the same document group will be described. FIG.
FIG. 7 is a diagram showing an example of a cabinet and a group of stored documents when a classification condition is not specified for a drawer / folder.

In this figure, a cabinet 700 is shown, and five documents 71 are stored in the cabinet 700.
1 to 715 are stored. These documents 711-71
5 is actually stored in the document storage unit 610. As described above, the documents 711 to 715 always belong to one of the cabinets, in this case, belong to the cabinet 700. If the classification condition is not set, the documents 711 to 715 are stored and managed together in the cabinet 700 without being classified. Have been.

Here, each of the documents 711 to 715 has a classification attribute such as “document type” and “project”.
And its attribute values are as follows, for example.

For the first document 711, the “document type” attribute is set to “specification” and the “project” attribute is set to “filing”. For the second document 712, the “document type” attribute is set to “specification”. , The “project” attribute is “printer”, the “document type” attribute is “specification”, the “project” attribute is “printer” for the third document 713, and the “document The “type” attribute is “minutes”, the “project” attribute is “filing”, and for the fifth document 715, the “document type” attribute is “minutes” and the “project” attribute is “copy”.

Next, the cabinet 7 is not classified.
An example of a classification structure in the case where the documents 711 to 715 stored in 00 are classified by a classification attribute of “document type” is shown below.

FIG. 38 is a diagram showing an example of a classification structure when a document group is classified by a certain classification attribute. According to this figure,
Drawer 721 specifying "document type" as a classification attribute
Is created, and this designation is performed by the classification condition setting unit 630. Folders 731 and 732 corresponding to attribute values are created below the drawer 721, and the documents 71 having the corresponding attribute values are stored in the respective folders 731 and 732.
1 to 715 are classified. That is, the documents 711, 712, and 713 having the attribute value “specification” are “specifications”
Documents 714 and 715 having the attribute value “minutes” classified into the folder 731 are classified into the “minutes” folder 732.

An example of a classification structure in the case where the documents 711 to 715 stored in the cabinet 700 in such a state are further classified by the classification attribute “project” is shown below.

FIG. 39 is a diagram showing an example of a classification structure in a case where a document group is further classified by another classification attribute. According to this figure, a drawer 722 in which “project” is further specified as a classification attribute is created. Under the drawer 722, folders 733, 732, and 735 corresponding to attribute values are provided.
Are created, and the respective folders 733, 732, 73
5, documents 711 to 715 having corresponding attribute values are classified. That is, the documents 711 and 714 having the attribute value “filing” are stored in the “filing” folder 7.
The document 71 classified into 33 and having the attribute value “printer”
2,713 are grouped in a “Printers” folder 734,
Documents 715 having the attribute value “copy” are classified into a “copy” folder 735.

In this way, one cabinet can be classified and a plurality of drawers can be designated. This makes it easier to perform maintenance when a change in the classification structure is required, because a change in a specific classification does not affect other classifications. Further, since the operation of the document (attribute change / deletion) can be reflected in a plurality of classifications, it is easy to maintain and manage whether the classification is performed correctly.

When the specified drawer is created,
By specifying an existing drawer, it can be created by imitating the classification structure. By setting a new classification by imitating the classification structure of an existing drawer, it is easy to create a classification structure.

Further, in the classification structure storage section 620,
It is possible to specify multiple cabinets from the drawer. This example is shown below. FIG. 40 is a diagram illustrating an example of a classification structure when different cabinets are classified by the same drawer.

According to this figure, a drawer 721 is created in which “year of creation” is specified as a classification attribute, and this specification is performed by the classification condition setting unit 630. This drawer 721
Below are folders 736, 737, 73 according to attribute values
8 are created, and the respective folders 736, 737, 7
38, documents 711 to 7 stored in the two cabinets 700 and 701 according to their corresponding attribute values.
17 are classified. This makes it possible to uniformly classify different file groups based on the same classification structure.

[0155]

As described above, in the file management apparatus of the present invention, the filing model control means performs basic filing operations, classifies electronic documents and files, and performs other operations.
Documents under different file systems outside can be handled as internal documents by external file management means, and attribute content management means manages attributes required for filing and actual document contents did.

For this reason, most document management systems and file systems in a conventional distributed environment depend on the file system of the operating system on which the document system is installed. When the operating system and storage were changed, it was necessary to input stored data (electronic documents and electronic files) .However, the present invention device is user-friendly and user-oriented. When the management can be realized and a plurality of the present invention devices are present on the same network, the user does not need to be aware of which device the necessary electronic document file exists, and the present invention device defines You only need to be aware of filing models and classifications.

Further, in the classification device in the file management device of the present invention, the classification under each hierarchy level, that is, in units of nodes (for example, folders) can be defined, and the classification structure by the folder corresponding to the attribute value is automatically determined. , Documents are automatically classified, and the correspondence between documents and classifications (folders) is managed. This reduces the burden on document management due to the automatic classification of documents based on attribute values, and allows fine-grained classification according to the purpose by changing the classification method under each layer, enabling classification to be performed according to the purpose. By changing only a part, maintenance when the classification structure needs to be changed becomes easier, and the operation (attribute change, deletion) of the document can be reflected in the classification. Maintenance is easier.

Further, the classification device in the file management device of the present invention enables a plurality of classifications to be set simultaneously for a file group having the same attribute information.
A group of files having the same attribute information is stored, for example, in a cabinet, and the classification structure based on the hierarchy of nodes (for example, drawers / folders) is managed, for example, at the highest node (drawer). A plurality of classifications can be set for the storage unit, and the same file group is classified by a plurality of methods at the same time. Also, by managing the correspondence relationship between a document and a plurality of classification structures (drawers / folders), when a document attribute change or deletion occurs, the result can be reflected in a plurality of classifications. As a result, a change in a specific classification does not affect other classifications, thereby facilitating maintenance when a change in the classification structure is required, and reflecting a document operation (attribute change or deletion) in multiple classifications. Because it is possible to perform the maintenance, it is easy to maintain whether the classification is performed correctly.

Further, when a file is stored in a node (for example, a folder) by the storage attribute setting means, the user attribute is automatically set in the file to be stored in accordance with the classification condition of the node. Can be omitted.

Further, as a node classification condition, a classification constraint can be set in addition to a classification attribute, and automatic classification can be performed according to the restriction, so that classification can be performed efficiently.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the principle configuration of an electronic document file management device according to the present invention.

FIG. 2 is a block diagram showing a configuration of an embodiment of an electronic document file management device according to the present invention.

FIG. 3 is a flowchart showing processing contents on the client device side in the case of document registration.

FIG. 4 is a flowchart (part 1) showing processing contents on the file management device side showing processing contents on the file management device side in the case of document registration.

FIG. 5 is a flowchart (part 2) showing processing contents on the file management device side showing processing contents on the file management device side in the case of document registration.

FIG. 6 is a flowchart (part 1) illustrating processing on the client device side in the case of extracting a registered document from a document.

FIG. 7 is a flowchart (part 2) illustrating the processing content on the client device side in the case of extracting a registered document from a document.

FIG. 8 is a flowchart (part 1) illustrating processing contents on the file management apparatus side in the case of searching for a registered document.

FIG. 9 is a flowchart (part 2) illustrating processing contents on the file management apparatus side in the case of searching for a registered document.

FIG. 10 is a flowchart (part 1) illustrating processing contents on the file management apparatus side in the case of content acquisition processing.

FIG. 11 is a flowchart (part 2) illustrating processing contents on the file management apparatus side in the case of content acquisition processing.

FIG. 12 is a flowchart (part 3) illustrating processing contents on the file management apparatus side in the case of content acquisition processing.

FIG. 13 is a flowchart (part 1) of processing on the client device side when registering an external reference.

FIG. 14 is a flowchart (part 2) of a process on the client device side at the time of external reference registration.

FIG. 15 is a flowchart (No. 1) illustrating a reference registration request process on the file management device side.

FIG. 16 is a flowchart (No. 2) illustrating the reference registration request processing on the file management device side.

FIG. 17 is a flowchart (part 3) of the reference registration request processing on the file management device side;

FIG. 18 is a diagram showing a mutual access method between the devices of the present invention.

FIG. 19 is a block diagram illustrating another configuration example of the electronic document file management device.

FIG. 20 is a flowchart illustrating a flow of a process of capturing external information.

FIG. 21 is a flowchart showing the flow of processing when extracting the contents of a file.

FIG. 22 is a flowchart showing the flow of processing when acquiring an attribute value of a file.

FIG. 23 is a block diagram illustrating a basic configuration of a document classification device in the file management device.

FIG. 24 is a diagram illustrating an example of a classification structure when a classification condition is not specified.

FIG. 25 is a diagram illustrating an example of a classification structure when a classification condition is specified in one step.

FIG. 26 is a diagram illustrating an example of a classification structure when a classification condition is specified in two stages.

FIG. 27 is a diagram illustrating a screen display example of a display unit displaying a classification result in an icon format.

FIG. 28 is a diagram showing another screen display example of the display unit displaying the classification results in a list format.

FIG. 29 is a flowchart illustrating a flow of a document group classification process.

FIG. 30 is a flowchart showing a flow of a classification condition changing process.

FIG. 31 is an explanatory diagram showing a link relationship when a classification attribute is changed.

FIG. 32 is a flowchart showing the flow of processing for registering a document in a drawer.

FIG. 33 is a flowchart showing the flow of a process for registering a document in a folder.

FIG. 34 is a flowchart illustrating the flow of a process of acquiring storage attribute information.

FIG. 35 is a flowchart showing the flow of a re-classification process by deleting a document.

FIG. 36 is a block diagram illustrating a basic configuration of a document classification device in the file management device.

FIG. 37 is a diagram illustrating an example of a cabinet and a group of stored documents when a classification condition is not specified for a drawer / folder.

FIG. 38 is a diagram illustrating an example of a classification structure when a document group is classified according to a certain classification attribute.

FIG. 39 is a diagram illustrating an example of a classification structure when a document group is further classified by another classification attribute.

FIG. 40 is a diagram illustrating an example of a classification structure when different cabinets are classified by the same drawer.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Processing request receiving means 2 Filing model control means 3 External file management means 4 Attribute content management means 5 Network 6a, 6b File creation device 7a, 7b External file system

──────────────────────────────────────────────────続 き Continuation of the front page (72) Inventor Masatomi Inagaki 3-2-1, Sakado, Takatsu-ku, Kawasaki City, Kanagawa Prefecture KSP R & D Business Park Building Inside Fuji Xerox Co., Ltd. (56) References JP-A-7-44573 (JP) , A) Japanese Patent Application Laid-Open No. 4-222036 (JP, A) Japanese Patent Application Laid-Open No. 7-84858 (JP, A) HELEN CUSTER, translated by Toshihiro Fukusaki, "INSIDE WINDOWS NT", ASCII, Inc., 1 (58) Field (Int.Cl. ⁷ , DB name) G06F 12/00 G06F 15/16

Claims (4)

(57) [Claims] 1. A classification function for classifying files hierarchically.
A file management device having a hierarchical structure of nodes for classifying the files.
Classification structure, attributes of the file to be classified,
Link between the file and the file classified immediately below the node
Link information at the time of setting, and classification rules of each node
Storage means for storing a case, setting means for setting a classification condition for the node , and an attribute value as a classification attribute of the file to be classified.
When the node having the value of the classification condition is not in the classification structure
Create a node with the value of the classification attribute and create the node
To associate a node with a node related to the node.
Generating means, attributes of the file to be classified and classification conditions of the node
Node to classify the file from
Classification that sets a link between the file and the determined node
File management apparatus comprising: 2. A classification function for classifying files hierarchically.
A file management device having a hierarchical structure of nodes for classifying the files.
Classification structure, attributes of the file to be classified,
Link between the file and the file classified immediately below the node
Link information at the time of setting, classification condition of each node, previous
Classification target file management that manages classification target files
Information and the classification target file management information and one or more
Link information at the time of setting a link with the classification structure
, A classification condition for the node, and a classification target file
Set a link between management information and one or more of the classification structures
Setting means for setting, and the attribute value as the classification attribute of the file to be classified
When the node having the value of the classification condition is not in the classification structure
Create a node with the value of the classification attribute and create the node
To associate a node with a node related to the node.
Generating means, attributes of the file to be classified and files to be classified
Classify files from management information and classification conditions of the node
The node of the one or more classification structure was determined to be, the file
Minutes to set a link between the file and the determined node
File management characterized by having a similar structure means
apparatus. 3. Registering a file in the node.
When the user setting attribute of the file
If not set, at least the attribute of the classification condition of the node
Storage attribute setting means for setting the value of
3. The file management device according to claim 1, wherein: 4. The classification condition of the node is a classification attribute
And a classification constraint, wherein the node is a directory
Or a drawer and a folder.
The target file is managed by the cabinet
The file management device according to claim 1.