JPH0447366A - Document retrieving method - Google Patents

Abstract

PURPOSE:To enable a user to recall details of past memory by reproducing the state of a data base for the occurrence of an event based on history information of events, and obtaining document information where details of the event are memorized. CONSTITUTION:A data base management mechanism is used which has the function which acquires operation history information required for reproducing of a data structure at the time of updating document information to reproduce the data structure at an arbitrary part time, and history information of events such as device use conditions of various operation information, communication information, etc., to the data base is aqcuired and is stored together with link information to the data base management mechanism. History information of an event is retrieved by a retrieval request, and the data structure of the data base management mechanism at the time of the occurrence of the even is reproduced based on link information to the data base management mechanism indicated by retrieved history information, and document information related to the even is obtained by the reproduced data structure. Thus, forgotton events can be recalled.

Description

DETAILED DESCRIPTION OF THE INVENTION (Field of Industrial Application) The present invention relates to a document retrieval method for user-friendly retrieval of document information in a document retrieval device that stores and retrieves document information.

(Conventional technology) Conventionally, various computer systems such as switching equipment and information systems collect various historical information such as failure information and communication information, and experts such as system administrators can grasp the failure status of equipment. , and is used to deal with complaints from customers.

Personal terminals such as PCs and facsimiles also acquire histories such as failure information and communication information, although the scale of information acquired varies, and experts at equipment manufacturers use this information for equipment maintenance and management. ing.

(Problem to be solved by the invention) As mentioned above, in the past, the proprietary base of devices and systems was
History information is only used for equipment maintenance and customer countermeasures, and the users and targets of use are limited, and general users are not in a situation where they can effectively use history information.

Therefore, especially in personal document retrieval devices,
Obtain the operation history, communication history, etc. of the device and use it later.
It is possible to search for documents using historical information, such as knowing details of past events, such as what kind of documents were registered, who received and received what kind of documents, etc. (Objective of the Invention) The object of the present invention is to solve the drawbacks of the conventional document retrieval methods described above, and to provide a user-friendly retrieval method based on historical information of events such as device usage status. be.

(Means for Solving the Problems) In order to achieve the above object, the present invention provides a document retrieval device that stores and searches document information. management, and executes update and search processing in response to update and search requests.Furthermore, when document information is updated, it acquires the reproduction history information necessary to reproduce the data structure, and when the document information is updated, it acquires the reproduction history information required to reproduce the data structure. a database management means having a function of reproducing a data structure at any point in the past based on the information;
The history information management means has a function of acquiring history information of events such as device usage status, storing it together with link information to the database management means, and searching the contents of the history information of events as key information, Based on the link information to the database management means indicated by the history information of the event obtained from the search result by the information management means, the data structure at the time of occurrence of the event is reproduced, and further, the data structure related to the event is reproduced by the reproduced data structure. It is characterized by obtaining document information.

(Function) The present invention acquires operation history information necessary for reproducing the data structure when updating document information.

Using a database management mechanism that has the function of reproducing the data structure at any point in the past, we acquire historical information on events such as various operation information for the database, device usage status such as communication information, and link it to the database management mechanism. In response to a search request from a user, the history information of the event is searched, and based on the link information to the database management mechanism indicated by the searched history information, the database management mechanism is stored at the time of occurrence of the event. The data structure is migrated, and document information related to the event is obtained using the reproduced data structure. Therefore, it is possible to obtain document information that stores detailed information at the time of occurrence from the history information of the event, and it is possible to remember what you have forgotten, allowing you to effectively use the history information for your own benefit. I can do it.

(Embodiment) FIG. 1 is a block diagram showing an example of a document retrieval device in which the method of the present invention is implemented. In the figure, 1 is an input unit having input devices such as a mouse, keyboard, scanner, tablet, etc., and code conversion and encoding processing functions; 2 is an information center;
A communication unit exchanges document information with external devices such as a personal computer and a facsimile; 3 is a display unit that displays search results of document information; and 4 stores document information input from the input unit 1 and the communication unit 2. 5 is an enlargement of one document information in order to display the document information on the display section 3;

an image processing section having a function of performing image processing such as reduction, scrolling, encoding/decoding processing at high speed; 6 a bus for transferring document information; 7 a transfer control section controlling transfer of the bus 6; is a control unit that controls the entire device and performs execution control of the present invention.

Next, the operation of this embodiment will be described in accordance with the operation flowchart of the control section 8 shown in FIG. 2, and shown in FIG. 5 is a diagram showing an example of a management table for managing the correspondence between the node number indicating the node indicated and the file number of document information stored in the storage unit 4; and a diagram showing an example of operation history information for reproducing the data structure shown in FIG. , 6th Wi will be described below using a diagram showing an example of history information of events shown in Wi.

First, the database update operation and reproduction operation in the database management mechanism of the control unit 8 will be explained.

Document information in the database management mechanism is managed using a data structure as shown in FIG. In the example in Figure 3, document information is managed using a three-level hierarchical structure (Heading 1. Heading 2. Title), and the nodes (circles in Figure 3) corresponding to the key information in each hierarchy are Corresponding attribute information (square part in Figure 3) and link information between nodes (
Links between different hierarchies and links within the same hierarchies).

In addition, regarding the title node, as attribute information,
Document entity and other attribute information (e.g. source of document, etc.)
It consists of Each node is assigned a node number that corresponds one-to-one with the node.

In this way, the data structure generally includes, for each node, a node number, corresponding attribute information, and link information (
The update operation of the data structure such as adding, changing, or deleting document information can be performed by updating any of the above three pieces of information. be exposed.

Also, regarding attribute information (including document entity).

The files are stored in the storage unit 4 shown in FIG. 1, and files in the storage unit are managed by file numbers assigned in one-to-one correspondence with the files. As mentioned above, attribute information needs to be associated with the storage location of the storage unit, and this is done by associating node numbers and file numbers.Node numbers and file numbers do not necessarily have a one-to-one correspondence. ,for example.

For a title node, for one node number,
The file number of the document entity corresponds to the file number of other attribute information. In this way, multiple file numbers correspond to one node number, so as shown in Figure 4,
In addition to the node number 40 and file number 41, the type 42 of attribute information (document entity, other attributes, etc.) corresponding to the file is also managed at the same time.

In the above database management mechanism, in order to reproduce the database, the contents of the data structure are changed during update operations such as adding, changing, and deleting document information, so the operations necessary for reproduction are necessary every time the update operation is performed. By acquiring information sequentially, tracing the operation information in the reverse direction when reproducing, and sequentially executing operations opposite to the operation information (delete operation in case of add operation, add operation in case of delete operation), past data can be restored. Reproduce the structure.

Furthermore, in order to restore the current data structure from the reproduced past data structure, the operation information is sequentially traced in the direction of the current time, and the same operations as the operation information are sequentially executed to restore the current data structure.

In this way, it is necessary to acquire, as operation information, information necessary not only to reproduce the past but also to return to the present moment. For example, in the case of a node addition operation, in order to return to the state before addition, you can obtain only the node number as operation information and perform a node deletion operation using this node number, but if you want to return to the current state requires additional operations and the information for that needs to be obtained.

Therefore, the operation information for adding a node requires the type of addition (addition of a node), the node number, the file number of the attribute information, the type of attribute information, the node number of the additional light, and the link type. The information obtained during update operations is based on the type of update operation (addition, change, etc.).

Deletion) and the operation target (node, attribute information, link information), but generally, as shown in FIG. 5, the operation number 50. Operation type 51. Operation target 52. Information 53 related to the data structure is required for reproducing the database.

Note that since the change operation can be realized by a combination of a deletion operation and an addition operation, the change operation is not necessary as the operation type 51. Further, in FIG. 5, an operation number 50 is a number assigned to an update operation, and is used as link information with event history information to be described later.

When the control section 8 receives an update request for adding, changing, or deleting a database from the input section 1 or the communication section 2, the database management mechanism of the control section 8 updates the database in accordance with the update request.

In addition, update requests add attribute information (including document entity),
If a change is involved, the attribute information is stored in the storage section 4, and the table is updated for the corresponding material of the node number 40 and file number 41 shown in FIG. When the database update operation is completed as described above, the database management mechanism assigns an operation number and operation information (operation type) necessary for database reproduction.

information related to the operation target and data structure) are stored in chronological order along with the operation number.

In addition, in the case of a deletion operation, instead of deleting all document information from the data structure, in order to be able to reproduce the deletion situation, the document information at the time of reproduction is created taking into account the amount of data, importance, etc. For example, in order to make effective use of the storage unit 4, attribute information with a large amount of data, such as the document entity, is deleted, and instead, attribute information with a small amount of data,
Treatment status information (storage optical information of document information to be deleted, reason for deletion, etc.) that is effective as history information is used as document information at the time of reproduction.

Then, the created document information is stored in the storage unit, as in the case where attribute information is added or changed as described above, and the correspondence between the node number 40 and the file number 41 shown in FIG. 4 is updated.

When the control unit 8 detects a request to reproduce the data structure from the input unit 1 or the communication unit 2, the database management mechanism of the control unit 8 creates a time-series data structure to reproduce the data structure shown in FIG. 5 based on the reproduction request. Search the table of operation history stored in , and find the current point again.

Furthermore, the operation history up to the present time is sequentially read out from the present time in the past direction, and the operation opposite to the operation history is executed to reproduce the data structure.

Furthermore, in conjunction with the update of the data structure, the correspondence management table between the node number 40 and file number 41 shown in FIG. 4 is updated.

Further, when the control unit 8 detects a data structure reproduction request again from the input unit 1 or the communication unit 2, the database management mechanism searches the operation history based on the reproduction request to obtain the new current point, as described above. If the current point in time is in the past than the previous point in time, the operation history is sequentially traced back in the same direction as described above. If the current point in time is closer to the current point than the previous point in time, the operation information is sequentially read in the current direction, the same operation as in the operation history is executed, and the data structure is reproduced. Similarly, in this case,
In conjunction with the update of the data structure, the correspondence management table between the node number 40 and file number 41 shown in FIG. 4 is updated.

Based on the above-mentioned database update and reproduction operations, we will discuss the events associated with the use of the document retrieval device. These events include events related to updating document information (when, by what means, from whom the document information was obtained and stored, etc.), and events related to retrieval of document information (when, by what means, by whom, etc.). There are events that are related to document information, such as whether the document information was used for a given device, and events that are not related to document information, such as events that relate to the entire device (such as when and what type of injury occurred).

Events not related to document information can be treated as events related to document information by setting the details of the event to document information. In this way, an event can be represented by basic information that concisely represents the event and document information related to the event.

As will be described later, the basic information is information mainly used to search for events from the user, and the zero document information stored in the order of occurrence is managed by the database management mechanism mentioned above. Related by link information. As the link information, a node number corresponding to the document information is used.

In addition to the information on the content of the event mentioned above, the information necessary to remember the event also requires information to reproduce the data structure at the time of the event. This is achieved by link information to the reproduction operation history table shown in the table. As the link information, the operation number 50 shown in FIG. 5 is used.

Based on the memorization method based on the historical information of the above events.

The event acquisition operation will be described in detail.

In the case of events related to updating document information (20 in Figure 2)
0 to 203) are generated by update operations such as adding, changing, and deleting document information from the input section 1 or the communication section 2 in FIG. Since the database update process in the database management mechanism at the time of update and the acquisition process for reproducing the data structure have already been described, the acquisition process of event history information will be described.

Database update process associated with update operation (20 in Figure 2)
0), and when the process of acquiring operation history information for reproducing the data structure is completed (201 in Figure 2), basic information that concisely represents the event is acquired as event history information (201 in Figure 2).
202 in Figure 2).

Basic information includes event type 60 (update) and input/output means 61 (scanner/memo manual/personal computer/information center/facsimile/printer, etc.) as illustrated in FIG.
, communication partner 622 date 63, etc. are acquired. Note that the basic information overlaps with the attribute information of the document information, and when storing the attribute information in the database update process, it is also possible to remove the basic information from the attribute information and store it, thereby making effective use of the storage unit 4. be.

Next, as link information to the database management mechanism, the node number 40 of the document information that is the target of the update operation and the operation number 50 corresponding to the operation history for reproducing the data structure stored along with the update operation are added as described above. It is stored together with the basic information (203 in FIG. 2).

In the case of events related to retrieval of document information (20 in Figure 2)
4 to 207) occur due to the operation of outputting search results to the display unit 3 or communication unit 2 in response to a document information search request from the input unit 1 or communication unit 2 in FIG.

When a search request is input from the input unit 1 or the communication unit 2,
The database management mechanism of the control unit 8 executes a search process in response to a search request (204 in FIG. 2).As for search requests, since the data structure is not changed, history information for reproducing the database is No collection will take place.

The control unit 8 reads the document information from the storage unit 4 based on the file number 41 of the document information obtained as a search result in the database management mechanism, and displays it on the display unit 3 (205 in FIG. 2). . As described above, a normal search operation consists of repeatedly displaying search results on the display unit 3, and if the history of the usage status resulting from the search operation is collected for each search, the amount will be enormous.

Furthermore, not all search operations are important events that should be remembered, so history information is acquired depending on the type of search operation, such as acquiring history information only when an important document is retrieved. . In addition, when transferring search results to other devices (information center, personal computer, facsimile, printer, etc.) via the communication unit 2, the frequency of the search operation is not as high as that of a search operation that is displayed on a normal display unit. Since it can be effectively used as history, it is acquired as history information.

When acquiring history information, the control unit 8 collects basic information, link information to the database management mechanism (node number,
(operation number) is acquired and stored as history information (206 and 207 in FIG. 2).

As the node number of the link information to the database management mechanism, the node number of the document information of the search result is set, and as the operation number, the operation number of the latest operation history is set.

In addition, basic information includes event type 60 (search),
Input/output means 61 (scanner/PC/information center/facsimile/printer, etc.), communication partner 629 date, etc. 63
etc. are obtained.

As an example of an event related to the entire device, if an injury occurs (
208 to 211) in FIG. 2 will be described below.

When the control unit 8 detects an injury to the device, the detailed information about the injury (name of the injured device, detailed error information, etc.) is edited (208 in Fig. 2), and the database management mechanism records events related to the update of document information. As in the above case, the detailed information on the injury is registered in the database as document information, the node number and the file number are associated, and the database is updated and registered (209 in FIG. 2).

Furthermore, basic information and link information to the database management mechanism (node number, operation number) are acquired and stored as history information (210 and 211 in FIG. 2).

Node number 40 of link information to database management mechanism
, a node number corresponding to detailed injury information is set, and as operation number 50, an operation number of the latest operation history is set. In addition, as basic information, event type 6
0 (injury), injury device name 61, date, etc. 63, etc. are acquired.

As described above, the history information of events varies slightly depending on the type of event, but in summary, information as shown in FIG. 6 is stored.

When the control unit 8 detects a search request for event history information from the input unit 1 or the communication unit 2 (212 in FIG. 2), it searches the contents of the event history information using the input search key information and performs the search. History information matching the conditions is searched and retrieved (213 in FIG. 2).

As search key information, the event type 60 shown in FIG.
．． One or more of the stored history information contents such as input/output means 612, communication partner 622, date 63, etc. are used. As a method of specifying history information, in addition to using the search key described above, the contents of the history information of stored events are edited in a format that is easy to understand for the user, and displayed on the display unit 3, and the history information that the user wants to search is displayed. There is also a way to specify information directly.

The database management mechanism of the control unit 8 searches the operation history table for reproduction shown in FIG. 5 using the operation number of the recorded history information, performs operations until the operation number 50 matches, and sequentially updates the operation history information. Take it out, reproduce the data structure, and add node number 40 and file number 4.
The correspondence is updated to 1 (214 in FIG. 2).

When the database management mechanism completes the database reproduction operation, the control unit 8 sends a search request to the database management mechanism based on the node number of the event history retrieved as a search result. , node number 40 and file number 41 shown in FIG.
The file number corresponding to the node number is determined from the correspondence management table , and the document information corresponding to the file number is read out from the storage section 4 and displayed on the display section 3 (215 and 216 in FIG. 2).

In the above, if there is more than one piece of history information that matches the search key, display a menu of the corresponding pieces of history information for the user to select, or choose from among the pieces of history information closest to the current point in time. (Effects of the Invention) As explained above, according to the present invention, it is possible to present desired historical information and document information that is detailed information to the user by displaying the desired historical information sequentially in the direction of the user. In addition, it is possible to reproduce the state of the database at the time of the event and obtain document information that stores the details of the event, making it easier to recall the details of past memories and making it more familiar to people. It has the advantage of providing an easy document search method.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing an example of a document retrieval device in which the method of the present invention is implemented, FIG. 2 is an operation flowchart of the control section 8 of FIG. 1, and FIG. 3 is a database mechanism of the control section 8 of FIG. 1. FIG. 4 is a diagram showing an example of the data structure of document information managed in the storage unit 4, and FIG. 4 manages the correspondence between the node number indicating the node in FIG. FIG. 5 is a diagram showing an example of the management table, FIG. 5 is a diagram showing an example of operation history information for reproducing a data structure, and FIG. 6 is a diagram showing event history information. 1...Input section, 2...Communication section, 3...
Display unit, 4...Storage unit, 5...Image processing unit,
6...Bus, 7...Transfer control unit. 8...Control unit. Patent Applicant Nippon Telegraph and Telephone Corporation Agent Koji Hoshino Figure Figure Figure Figure

Claims (1)

[Claims] In a document search device that stores and searches document information,
It manages the data structure of document information and the files on the storage device where document information is stored, executes update and search processing in response to update and search requests, and is also necessary to reproduce the data structure when updating document information. A database management means that has the function of acquiring historical information for reproduction, and reproducing the data structure at any point in the past based on the historical information for reproduction upon request for reproduction of the data structure, and a history of events such as device usage status. It has a history information management means that has a function of acquiring information, storing it together with link information to the database management means, and searching the content of the history information of the event as key information. The data structure at the time of occurrence of the event is reproduced based on the link information to the database management means indicated by the history information of the event, and document information related to the event is obtained from the reproduced data structure. document search method.