JPH07121425A - Filing system - Google Patents

Abstract

PURPOSE:To provide a filing system which can manage files in plural management forms and manage files stored in the other devices connected to a network. CONSTITUTION:A client access part 11a receives an access request from clients 12a-12d, and a schema management part 11b selects a schema corresponding to the access request. The storage position of the file is checked in accordance with the schema selected by a file operation part 11c by using a reference pointer. A server access part accesses data and makes a response to the client.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a filing system, and more particularly to a filing system capable of managing multimedia data and the like in a plurality of management modes having different attribute items.

[0002]

2. Description of the Related Art Recent progress in information processing technology has been remarkable, and not only document data but also various data such as image data and video data (hereinafter referred to as "multimedia data") have flooded the office. There is.

Therefore, various file servers and databases have been used in the past in order to efficiently manage such multimedia data.

For example, Japanese Patent Laid-Open No. 2-3871 discloses that
Disclosed is an image information filing apparatus which adds content description information to document image data and stores it in a storage medium, efficiently manages a large amount of document image data using this content description information, and improves search efficiency. There is.

Further, in Japanese Patent Laid-Open No. 4-344956, the related information disc management means manages related information between the image information management part and the code information management part,
An electronic filing apparatus has been disclosed which manages image information and code information in a combined manner by automatically associating both information with each other using the related information.

[0006]

However, the conventional techniques represented by the above techniques are intended to manage only the files stored in the respective devices, and improve the overall file management function in the network system. is not.

That is, although a filing system for improving the file management function of the entire system is required, such a function is lacking in the conventional filing system.

Specifically, considering a file management function as a total system, how to perform integrated management of files managed by each filing apparatus becomes an important issue.

That is, if the files are individually managed in each filing device, it is impossible to avoid storing the same file in a plurality of filing devices.
In addition, since it is not possible to easily check which filing device manages a desired file, there is a problem in terms of storage capacity pressure and search efficiency.

Further, in the conventional filing apparatus, one file management mode (hereinafter referred to as “schema”) that can satisfy the request of the client is determined, and the apparatus is configured so that the schema can be realized. There is a limit to the required performance that can be satisfied by this filing apparatus, and it is also an important issue to construct a filing system having a filing apparatus that can respond to the client's request in different management modes.

Therefore, the present invention solves the above problems and problems, and manages files in a plurality of management modes having different attribute items, and also manages files and the like stored in other devices connected to the network. It aims at providing the filing system which can be performed.

[0012]

In order to achieve the above object, a client access unit that receives requests from a plurality of types of clients and returns a response, and a plurality of schemas that define items of internal attribute information are stored, and Schema management means for associating the attribute information of the file described in the system with the internal attribute information defined by the schema specified by the client, and the index management for associating the attribute information of the internal system with the physical storage position of the data Means and a data access means for accessing the data to the physical storage position of the data associated by the index management means.

[0013]

According to the present invention, requests from a plurality of types of clients are accepted by the client access means, the accepted requests are converted into internal position information and attribute information using the schema management means, and the index management means is also provided. A physical storage position is associated with the position information and attribute information of the internal system, the data is accessed from the physical storage position using the data access means, and the accessed data is used by the client using the data access means. Respond to.

Thus, the file can be managed in a plurality of management modes having different attribute items, and the files stored in other devices connected to the network can also be managed together.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the filing system according to the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the overall structure of a filing system.

As shown in FIG. 1, this filing system includes a client controller 11 and each client 1
2a-12d and each server 13a-13c.

Here, the clients 12a to 12d are
Each is a client that handles a workstation (WS) or the like, and is connected to the client control unit 11.

The clients 12a to 12d can perform file registration, search and retrieval requests for the servers 13a to 13c and the client control unit 11, and access requests to any of the servers can be made.
This is done via the client control unit 11.

The servers 13a to 13c are file servers that manage the files registered by the clients 12a to 12d, and are connected to the client control unit 11, respectively.

The client control unit 11, which is the subject of the present invention, is provided between each client 12a to 12d and each server 13a to 13d, and has a client access unit 11a, a schema management unit 11b, and a file operation unit 11c. , A server access unit 11d and a local disk 11e. The client control unit 11 also functions as a file server that manages files using the local disk 11e.

The client access unit 11a accepts file registration, search and retrieval requests from the clients 12a to 12d, and the request is received by the schema management unit 11b.
And the search result and the like received from the schema management unit 11b to the requesting client.

The client access unit 11a is equipped with an existing protocol used by various clients in addition to the standard protocol suitable for exhibiting the functions of this system.

That is, before using the client control unit 11, each client 12a to 12d equips the client access unit 11a with the existing protocol used with the servers 13a to 13c.

The schema management unit 11b is a management unit that manages a plurality of schemas having different attribute items. That is, the client control unit 11 is configured so that the local disk 11e can be described in a plurality of forms using a plurality of schemas, and the schema management unit 11b manages the plurality of schemas.

The file operation unit 11c manages and operates a file of multimedia data using content data (hereinafter referred to as "content") and attribute information. Specifically, the schema corresponding to the requested search condition or the like is selected, and the file operation is performed using the reference pointer.

The reference pointer is a kind of address pointer indicating the storage location of the contents, and is an extension of the concept of the address pointer used conventionally.

That is, in the conventional address pointer,
Although the inside of the local disk 11e is used as a target range to indicate the file storage location, this reference pointer is not limited to the inside of the local disk 11e, and the other servers 13a to 13c are also targeted.

The reference pointer does not target only the storage medium for storing the file, but also the physical position. Specifically, printed matter and books can be managed, and a library or a bookshelf where these books and the like are located can be pointed by using a reference pointer.

The server access section 11d is a section that controls the interface between the client control section 11 and the servers 13a to 13c. Like the client access section, various servers 13a to 13 other than the standard protocol are used.
It is equipped with the existing protocol used by c.

By using the client control unit 11 having the above configuration and also functioning as a server, the server 13
The client control unit 11 as an upper server of a to 13c
The filing system can be realized by integrating the file management functions of each server.

Next, a file storage / retrieval procedure using the filing system having the above configuration will be described with reference to FIG.

First, the client 12a to the server 13
The case of storing a document file in b will be described.

When the client 12a makes a storage request for a document file to the server 13b using the existing protocol (S201), the client access unit 11a accepts this request and outputs it to the schema management unit 11b (S202). Upon receipt of the storage request, the schema management unit 11b selects a schema based on the attribute data of the document file and confirms the storage position of the document file in the schema. Then, the document file is output to the file operation unit 11c together with the storage location (S2).
03).

Then, the file operation unit 11c creates attribute information for file management based on the attribute data of the document file, stores this attribute information in a predetermined storage location, and stores the document file in the server access unit 11d. It is sent (S204).

The attribute information created here is the attribute data of the document file added with a reference pointer indicating the storage location of the document file. In this case, the information corresponding to the server 13b is the reference pointer. Used as.

Then, the server access unit 11d transmits the document file to the server 13b using the existing protocol (S205), and the document file is stored in the server 13b.

When the server 13b completes the storage of the document file, a storage completion notification is sent to the server access unit 1.
It is transmitted to 1d (S206). Then, the storage completion notification is sequentially transferred to the file operation unit 11c, the schema management unit 11b, and the client access unit 11a (S207), and stored in the client 12a that has issued the document file storage request from the client access unit 11a. The completion notice is output by the existing protocol (S208).

By performing the above-mentioned storage processing, the document file is transferred to the server 13b according to the request of the client 12a.
The document file is stored in the server 13
The file operation unit 11c can recognize that the file is stored in b.

The client 12a and the server 13
In b, since the file can be transferred and received by the conventional procedure using the existing protocol, the client control unit 11 is transparent (transparent) without the need for modification accompanying the introduction of the client control unit 11. Can be regarded as.

Next, a processing procedure when a file search request is issued from the client 12b to the client controller 11 will be described.

When the client 12b makes a file search request to the client control unit 11 using the standard protocol (S211), the client access unit 11a accepts this request and outputs it to the schema management unit 11b (S212). Then, the schema management unit 11b that has received the search request selects a schema that matches the search condition and outputs it to the file operation unit 11c together with the search condition (S213).

Then, in the file operation section 11b,
Attribute information that matches the search condition is searched according to the schema, and information about the corresponding file is output to the schema management unit 11b as a search result (S214).

At this time, since each attribute information is provided with a reference pointer indicating the storage location of the file, the storage location of the file that matches the search condition can be included in the search result.

Then, the search result is output to the client 12b using the standard protocol via the schema management unit 11c and the client access unit 11a (S215, S216).

By performing the above-mentioned search processing, it is possible to search and output a file that matches the search request of the client 12a not only in the client control unit 11 but also in the servers 13a to 13c.

The outline configuration and processing outline of the filing system according to the present invention have been described above. Therefore, in the following, a second embodiment will be used in the case where each client, each server and the client controller are connected to the network. This will be specifically described.

FIG. 3 is a block diagram showing the system configuration of the filing system in the second embodiment.

As shown in FIG. 3, in the second embodiment, the clients 12a to 12c respectively equipped with a workstation (WS), a personal computer (PS) and a scanner (Scan) are LAN21 (local area network). Via a fax (FAX) client via fax line means,
Each is connected to the client control unit 11.

The client control unit 11 is a LAN
It is connected to the external servers 13a and 13b via 22. It should be noted that this external server is a file server that manages files, as in the previous example.

In this embodiment, the LAN 21 and the LAN 22 are provided separately for convenience of explanation, but they may be connected to the same LAN.

The client control unit 11 has a client access unit 11a, a schema management unit 11b, a file operation unit 11c, and a server access unit 11 as in the previous embodiment.
d and the local disk 11e.

Here, in this embodiment, the client access unit 11a is replaced by the local media access unit A.
1, a network access unit A2, and a FAX line access unit A3.

The local medium access unit A1 receives a file registration request or the like from a local medium such as a floppy disk device (not shown) provided in the client control unit 11.

The network access unit A2 is the LAN2
Each client 12a-12 connected via 1
The access request from c is accepted.

The FAX line access unit A3 receives an access request from a client that accesses the client control unit 11 by using the FAX line unit. In this case, the FA line unit uses the FAX line unit.
The access request from the X client 12d is the FA
It is accepted by the X-line access unit A3.

The access parts A1 to A3 are
It is possible to equip each with a plurality of protocols, and an existing protocol or the like can be used in addition to the standard protocol for the client control unit.

Further, the schema management unit 11b manages a plurality of schemas such as the schema B1 and the schema B2. When storing a file, for example, the attribute of the file is referred to and the schema matching the attribute is selected. Will be selected. The contents of this schema will be described later.

Next, the file operation section 11c is composed of a content processing section C1 and an attribute processing section C2. In the present embodiment, a case will be described in which a file is divided into contents and attributes, the contents are stored in a predetermined server, and the attributes are handled in the file operation unit 11c.

The content processing unit C1 processes the contents of the file. Specifically, the content processing unit C1 instructs the server access unit 11c to determine the storage location for storing the content and store the content in the storage location. It is an instruction. As a result, the contents of the file are stored in the server 13a or 13b or the local disk 11e. When the client designates an external server to store, it follows the designation of the external server.

The attribute processing unit C2 adds an attribute using the storage location determined by the content processing unit C1 as a reference pointer, and stores the attribute and the like in a management table (not shown) corresponding to the schema. Note that this management table is provided for each schema.

Next, the server access unit 11d comprises a local disk access unit D1 and a network access unit D2.

The local disk access unit D1 is used when the client control unit 11 functions as a server, and accesses the local disk 11e.

The network access unit D2 is the LAN2
It is used when accessing the external server 13a or 13b via the server 2. The network access unit D2 can be equipped with an existing protocol in addition to the standard protocol.

Next, the file registration, search, and retrieval processing performed by the client control unit 11 having the above configuration will be specifically described.

FIG. 4 shows the client control unit 1 shown in FIG.
It is a flowchart which shows the flow of the file registration process of No. 1.

As shown in FIG. 4, when a file registration request is received from a client using a predetermined protocol,
The protocol is interpreted (S401), requests are received from the corresponding access units A1 to A3, and the schema management unit 11
output to b.

Then, the schema management section 11b extracts attributes and contents from the file for which the registration request has been received (S4).
02), the consistency between the information required for each schema management structure (hereinafter referred to as “schema information”) and the attribute of the file is checked (S403), and if there is no corresponding schema,
After sending an error end notification to the client (S40
4), the process ends. At this time, it is also possible to newly construct a schema corresponding to the file.

On the other hand, when the schema corresponding to the attribute of the file exists, the schema is confirmed and then the contents and attributes of the file are sent to the file operation unit 11c.

Then, in the file operation section 11c, the content processing section C1 first determines the storage location for storing the content of the file, and notifies the attribute processing section C2. If the client specifies the storage destination server, the specification is followed.

Upon receiving this notification, the attribute processing unit C2 adds the storage location of the content data to the attribute as a reference pointer, adds it to a predetermined position of the schema, and stores it in a management table (not shown) (S405). ).

Next, it is confirmed whether or not the storage of this attribute is normally completed (S406). If the storage is normally completed,
The server access unit 11d is instructed to store the content of the file in the determined storage location.

Then, the server access unit 11d uses the local disk access unit D1 when the storage location is a local disk, and uses the external server access unit D2 when the storage location is the external server 13a or 13b. The contents of the file are stored using (S40
7).

Then, it is confirmed whether or not the contents of this file are normally stored (S408). If the contents are normally stored, the client is notified of the normal end (S409), and then the processing is performed. To finish.

If the processing is not normally completed in S406 and S408, an error end notification is sent to the client (S404), and the processing is ended.

Next, the file search processing will be described with reference to the flowchart shown in FIG.

FIG. 5 shows the client control unit 1 shown in FIG.
It is a flow chart which shows the flow of the 1st file search processing.

As shown in FIG. 5, the clients 12a ...
When the search request is received from 12d, the client access unit 11a interprets the protocol as in the above registration process (S501), receives the search request from the corresponding access unit, and sends it to the schema management unit 11b.

Then, the schema management section 11b extracts the search range and the search condition from the search request (S50).
2) It is checked whether or not there is a schema corresponding to the search condition or the like by collating with each schema information (S503).

If there is no schema that matches the search conditions, the search result is notified to the client that there is no corresponding file (S506), and the process is terminated.

On the other hand, when the corresponding schema exists, the search conditions and the like are sent to the file operation unit 11c.

In the file operation unit 11c, the attribute processing unit C2 is used to search for a file having an attribute that matches the search condition (S504), and the search results are totaled (S505). The client is notified (S506) and the process ends.

Next, the file extracting process will be described with reference to the flowchart shown in FIG.

FIG. 6 shows the client control unit 1 shown in FIG.
6 is a flowchart showing a flow of a file fetching process of No. 1.

As shown in FIG. 6, the clients 12a ...
If you receive a file extraction request from 12d,
Similar to the registration process, the client access unit 11a
In step S601, the protocol is interpreted, a fetch request is accepted from the corresponding access unit, and the fetch request is sent to the schema management unit 11b.

Then, in the schema management section 11b,
Information corresponding to the attribute of the file to be extracted is extracted from the extraction request (S602) and collated with each schema information (S603).

As a result, if there is no corresponding schema, an error end notification is sent to the client (S604), and the process is ended.

On the other hand, if the corresponding schema exists, the file fetch request is output to the file operation unit 11c.

The file operation unit 11c that has received this extraction request uses the attribute processing unit C2 to extract the attributes that match the extraction request (S605).

Then, it is confirmed whether or not the extraction of this attribute has been completed normally (S606), and if it has been completed normally, the reference pointer is extracted from the attributes,
Check the storage location of the file.

Then, the contents are extracted from the storage location pointed to by the reference pointer (S607), and if the extraction is normally completed (S608), the contents and attributes are transferred to the client (S609), and the process is terminated.

As described above, by performing the file storage, search and retrieval processes, the external servers 13a and 13b are not distinguished from the local disk 11e.
You will be able to manage files.

Next, the structure of each schema used in the schema management unit 11b will be described.

FIG. 7 is a conceptual diagram showing the structure of the schema.

As shown in FIG. 7, the schema management section 11b.
Has a plurality of schemas such as schema B1 and schema B2.

Each schema manages each attribute in a tree structure. For example, the attribute 71 and the attribute 72 are arranged under the schema B1, and the attribute 71a and the attribute 71b are arranged under the attribute 71. Of.

As described above, by using the tree-structured schema, a schema with high search efficiency can be realized.

The schema that can be handled by the present invention is not limited to the tree structure, and schemas having various structures can be used.

Further, in the schema management section 11b,
It is possible to freely add and delete schemas.

Next, a specific example of the schema managing section 11b will be described with reference to FIG.

As shown in FIG. 8, the schema management section 11b.
Suppose that the schema B1 and the schema B2 are inherent.

Here, the schema B1 is characterized by a creation date whose type is year / month / day, a creator whose type is a character string, and schema information B10 which has a document format whose type is a number. And schema B
Reference numeral 2 is a schema characterized by schema information B20 having as an item an issue date whose date is a type, a slip type whose number is a type, and a customer whose type is a character string.

[0103] Further, the attributes constituting each schema have specific values for each component of the schema information. For example, "930824" is created in the attribute 81 arranged in the schema B1 as the creation date. "Yamaguchi" is stored as the creator and "1" is stored as the document format.

Further, as the attribute, for example, a reference pointer indicating the storage location of the content is stored, as in the case where the content pointer 810a is added to the attribute 81.

This reference pointer is not limited to simply pointing to the address in the local disk of the server, but may include an external server and a physical archive.

That is, in the conventional database or the like, one schema is set for one database, but in the present invention, the schema management unit 11b manages a plurality of schemas having different attribute items. In addition, in the conventional address pointer, the storage location in the local disk was indicated, whereas in the present invention, a reference pointer capable of pointing to an external server, a physical archive, etc. is provided in the attribute. Of.

Next, the relationship between the management mode in the schema management section 11b and the display screen of the WS client will be described with reference to FIG.

As shown in FIG. 9, the schema management section 11b.
Drawers 91 and 92 are displayed on the screen of the WS client for each of the schemas B1 and B2 owned by.

The attribute 8 arranged in the schema B1
1, 82 are displayed as cabinets in the drawer 91, and attributes 81a and 81b arranged under the attribute 81 are displayed as documents, respectively.

Thus, a drawer is provided for each schema,
By arranging the attributes corresponding to the folders and documents in the drawer, the structure of each schema can be displayed on the workstation and can be designated by the client.

As described above, in the present embodiment, the schema management unit 11b is configured to manage a plurality of schemas, so that file management can be performed using a plurality of management structures.

Further, in the file operation section 11c, the reference pointer is used to point not only to the files in the local disk 11e but also to the external servers 13a to 13c, the bookshelves, etc., so that the files to be stored in the external server etc. are integratedly managed. can do.

Further, the client access unit 1 receives the access request input from the clients 12a to 12d.
Since 1a is configured to accept using a plurality of protocols, it is possible to make an access request using an existing protocol as well as a standard protocol.

In this embodiment, the file server is used as the external server, but the present invention is not limited to this, and can be applied to various devices such as databases and mail servers that manage files. Is possible.

[0115]

As described above in detail, according to the present invention, the schema management means is configured to manage a plurality of schemas having different attribute items, so that file management can be performed using a plurality of management structures. It becomes possible to do.

Further, in the index processing means, the physical storage positions of other servers are pointed to by the reference pointer, so that the files stored in various servers can be integratedly managed.

Furthermore, since the client access means can receive requests input from a plurality of types of clients using a plurality of protocols, the requests can be received using a plurality of protocols such as existing protocols. Becomes

[Brief description of drawings]

FIG. 1 is a block diagram showing the overall configuration of a filing system according to a first embodiment of the present invention.

FIG. 2 is a diagram showing a file storage and file search procedure of the filing system shown in FIG.

FIG. 3 is a block diagram showing an overall configuration and a detailed configuration of a client control unit in a second embodiment of the filing system according to the present invention.

FIG. 4 is a flowchart showing a file registration procedure of the client control unit shown in FIG.

5 is a flowchart showing a file search procedure of the client control unit shown in FIG.

FIG. 6 is a flowchart showing a file extraction procedure of the client control unit shown in FIG.

7 is a conceptual diagram showing the structure of a schema handled by the schema management unit shown in FIG.

FIG. 8 is a diagram showing an example of a specific configuration of a schema.

FIG. 9 is a diagram showing a correspondence relationship between a schema and a screen display.

[Explanation of symbols]

11 client control unit, 11a client access unit, 11b schema management unit, 11c file operation unit, 11d server access unit, 11e local disk, 12a to 12d clients, 13
a-13c server, 21-22 LAN, 3 LA
N A1 local media access part, A2 network access part, A3 FAX line access part, B1
~ B2 schema, C1 content processing unit, C2 attribute processing unit, D1 local disk access unit, D2 external server access unit

Claims (1)

[Claims] 1. A client access unit that receives requests from a plurality of types of clients and returns a response, and a plurality of schemas that define items of attribute information of an internal system are held, and the attribute information of a file described in the client system is stored in the client. Schema management means for associating the internal attribute information defined by the schema specified by, index management means for associating the internal attribute information with the physical storage location of data, and the index management means. And a data access means for accessing the data to a physical storage position of the data.