JPH0512405A - Image information memory retrieving device - Google Patents

Abstract

PURPOSE:To manage update history for the unit of a document without increasing file capacity at the image information memory retrieving device to record/ read document images. CONSTITUTION:An update history processing part 14 updates update history information when document image data are updated, and storage/read processing control is executed to the document image data corresponding to a desired edition based on the update history information. An update history storage part 15 stores the update history information of the image document data in a storing means 12 corresponding to the document, and an update history read part 17 reads the update history information onto a memory 6 as an update history management table 13. Thus, since the update history is stored and managed corresponding to the document, only source document image data and the document image data of updated pages are stored as the document image data, and the increase of the file capacity can be suppressed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention sequentially stores image information such as documents in a storage device, and retrieves required image information from each image information stored in the storage device as required. The present invention relates to an image information storage / retrieval device for reading by reading.

[0002]

2. Description of the Related Art In recent years, image information storage / retrieval devices have begun to become popular due to the increase in capacity of media and the decrease in price. These image information storage / retrieval devices have a function of retaining document image data before update as update history when updating already registered document image data.

[0003]

However, in the conventional configuration, since the update history is held only in page units, there is a problem that the update history in document units cannot be known. This problem will be explained in detail. Since the revision history of the related art has been performed page by page, for example, by updating one page, 1-
If the second version is the second edition and the third page is updated to be the third edition, the third version is the third edition, and the first edition is 1, 2, 3, 4,
At 5, the second edition becomes 1-2, 2, 3-2, 4, 5. However, it is desirable that the history in this case is originally managed as follows. The first edition is 1, 2, 3, 4, 5,
The second edition is 1-2, 2, 3, 4, 5, and the third edition is 1-2,
2, 3-2, 4, and 5.

An object of the present invention is to provide an image information storage / retrieval apparatus which solves the above-mentioned problem of history management without increasing the file capacity by double management of document image data.

[0005]

An image information storage / retrieval apparatus of the present invention includes an update history storage unit for storing update history information of document image data in a storage unit corresponding to a document, and an update for reading the update history information. A history reading section, and an update history processing section that updates the update history information in accordance with the update of the document image data, and stores / reads the document image data corresponding to a desired version based on the update history information. Is provided.

[0006]

According to this structure, the documents to be stored are the original document and the updated part of the document, and the desired version of the document image data can be read only by storing the update history information in correspondence with these documents. I can put it out. Therefore, it is possible to manage the update history on a document-by-document basis without increasing the file size by double management of the document image data.

[0007]

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

FIG. 1 is a block diagram of the present invention, FIG. 2 is a flowchart thereof, and FIGS. 3 to 6 are structural diagrams of an update history management table. In FIG. 1, the solid line portion shows the means added by the present invention, and the dotted line portion shows the means that the image information storage / retrieval apparatus conventionally has.

In step S1 of FIG. 2, the input processing section 2 sends the processing designated by the keyboard 1 to the main control section 3, and if the processing is "registration", step S2 is performed.
If "search", the process proceeds to step S7, and if "end", the process ends.

In step S2, the designation of the attribute of the document image data is received from the input processing unit 2. In step S3, when the main control unit 3 instructs the document image data capturing unit 4 to capture the document image data, the scanner 5
The document set in the
Is taken in as. In step S4, the main control unit 3 instructs the document image data display unit 8 to display the document image data 7 on the memory 6, and the content of the data is displayed on the display 9.

In step S5, the main control section 3 gives an instruction to the registration processing section 10 to store the document image data 7 in the storage means 12. In response to this, the registration processing unit 10 stores the document image data 7 and the attributes of the document image data specified in step S2 in the storage unit 12 through the document image data / attribute storage unit 11. Step S6
In step S3, that is, if the next original exists, the process returns to step S3. If not, the process advances to step S7.

In step S7, the main control section 3 instructs the registration processing section 10 to end the registration processing. In response to this, the registration processing unit 10 causes the update history processing unit 14 to store the content of the update history management table 13 as an update history in the storage unit 12 through the update history storage unit 15, and returns to step S1.

In step S8, the main control section 3 receives the search condition from the input processing section 2. In step S9, the main control unit 3 instructs the search processing unit 16 to search the document image data that matches the search condition from the storage unit 12. In step S10, the search processing unit 16 instructs the update history processing unit 14 to read the update history management table from the storage unit 12 through the update history reading unit 17 and set it in the memory 6.

In step S11, the main controller 3
It is determined whether or not the old version display of the document image data has been designated. If it is designated, the process proceeds to step S12, and if not, the process proceeds to step S13. Step S
At 12, the main control unit 3 instructs the search processing unit 16 to read the specified version of the document image data, and the storage unit 12 through the document image data / attribute reading unit 18.
The data of the corresponding version is read from and is set in the memory 6.

In step S13, the main control section 3 instructs the retrieval processing section 16 to read the latest version of the document image data, and reads the latest version of the document image data from the storage means 12 through the document image data / attribute reading section 18. ,
Set on the memory 6. In step S14, the main control unit 3 instructs the document image data display unit 8 to display the document image data 7 on the memory 6, and the display 9
The content of the data is displayed in.

In step S15, the input processing section 2 sends the processing designated by the keyboard 1 to the main control section 3,
According to the processing content, if the version of the document image data to be displayed is changed, the process proceeds to step S16, if the display document is updated, the process proceeds to step S21, and if it is the display of the next page, the process proceeds to step S19. ..

In step S16, the update history processing section 14 receives the instruction from the search processing section 16 and checks the update history management table 13 in the memory 6 to obtain the address of the document image data corresponding to the designated version. Step S
In 17, the document image data / attribute reading unit 18 reads the designated version of the document image data from the storage unit 12 based on the address, sets it in the memory 6, and returns to step S15. In step S18, the main control unit 3 instructs the document image data display unit 8 to display the document image data 7 on the memory 6, and the content of the data is displayed on the display 9.

In step S19, the search processing unit 16
Reads the document image data corresponding to the next page from the storage unit 12 through the document image data / attribute reading unit 18 and sets it on the memory 6. In step S20, the main control unit 3 instructs the document image data display unit 8 to display the document image data 7 on the memory 6, the content of the data is displayed on the display 9, and the process returns to step S15.

In step S21, when the main control unit 3 instructs the document image data fetching unit 4 to fetch the document image data, the document set on the scanner 5 becomes
The document image data 7 is stored in the memory 6. In step S22, the main control unit 3 instructs the registration processing unit 10 to update the page with the document image data 7 on the memory 6. In response to this, the registration processing unit 10 updates the corresponding data in the storage unit 12 with the document image data 7 in the memory 6 through the document image data / attribute storage unit 11.

In step S23, it is determined whether or not the next page is updated. If yes, the process proceeds to step S19. If not, the process proceeds to step S24. Step S2
4, the update history management table 13 on the memory 6 updated by the update history processing unit 14 is updated and stored in the storage unit 12 through the update history storage unit 15.

The update contents of the update history management table are shown in FIG.
5 will be described in detail through a specific example.

FIG. 3 shows the structure when the document image data of 5 pages is first registered. Pages 1 to 5 of the latest version management table correspond to document image data 1 to document image data 5 of the document image data table, respectively.

FIG. 4 shows the structure when the second page is updated to create the second version. The first version management table is shown in Figure 3.
1 to 5 correspond to the document image data 1 to the document image data 5 in the document image data table, respectively. The difference from FIG. 3 is that the first point is that the top of the page management table of the document management table is the latest version management table, that is, the top of the second version management table, and the second point is the latest version management table. The old page management head of is pointing to the head of the first version management table,
Further, the head of the second page data in the latest version management table does not indicate the document image data 2 in the document image data table, but the document image data 6 which is the updated two-page data.

FIG. 5 shows the structure when the third page is updated by updating the third page from the state of FIG. The first version management table corresponds to the first version management table in FIG. 4, and the second version management table corresponds to the latest version management table in FIG. The difference from FIG. 4 is that the first point is that the head of the page management table of the document management table is the latest version management table, that is, the head of the third version management table, and the second point is the latest version management table. The point that the old page management head of (1) points to the head of the second version management table, and the third point is that the old page management head of the second version management table points to the head of the first version management table.

Further, the head of the second page data of the latest version management table is not the document image data 2 of the document image data table, but the document image data 6 which is the updated page 2 data.
The top of the third page data indicates not the document image data 3 in the document image data table but the document image data 7 which is the updated three-page data.

Therefore, if one page is updated to 1-2 and the third page is updated to 3-2, and the third page is updated to 3-2, the update history management table First
The first edition is 1, 2, 3, 4, 5 and the second edition is 1, 2-2, 3,
It can be judged from 4, 5 that the third edition is 1, 2-2, 3-2, 4, 5. Further, according to the present invention, the document image data of all pages is not held for each version, but the same data is centrally held in the document image data table. There is no need to increase the file size.

In order to speed up access to the old version management table, the data indicating the beginning of the old version management table is shown in FIG.
It may be provided in the document management table as shown in.

[0028]

As described above, according to the present invention, an update history storage unit for storing update history information of document image data in a storage unit corresponding to a document, and an update history reading unit for reading the update history information. Since the update history information is updated in accordance with the update of the document image data, and the update history processing unit for storing and reading the document image data corresponding to the desired version based on the update history information is provided. It is possible to manage the update history for each document without increasing the file capacity by double management of the document image data.

[Brief description of drawings]

FIG. 1 is a configuration block diagram of an embodiment of the present invention.

FIG. 2 is a flowchart showing the operation of the embodiment.

FIG. 3 is an explanatory diagram of the structure of an update history management table.

FIG. 4 is an explanatory diagram of a structure of a second version update history management table in which a second page is updated.

FIG. 5 is an explanatory diagram of a structure of an update history management table of a third version in which the third page is updated.

FIG. 6 is an explanatory diagram of another structure of the update history management table.

[Explanation of symbols]

 1 Keyboard 2 Input Processing Section 3 Main Control Section 4 Document Image Data Importing Section 5 Scanner 6 Memory 7 Document Image Data 8 Document Image Data Display Section 9 Display 10 Registration Processing Section 11 Document Image Data / Attribute Storage Section 12 Storage Means 13 Update History Management table 14 Update history processing unit 15 Update history storage unit 16 Search processing unit 17 Update history reading unit 18 Document image data / attribute reading unit

Claims (1)

Claim: What is claimed is: 1. An image information storage / retrieval device for fetching document image data, storing the same in storage means, searching the stored document image data from the storage means, and displaying or printing the document image data. An update history storage unit that stores the update history information of data in a storage unit corresponding to a document, an update history reading unit that reads the update history information, and updates the update history information when the document image data is updated. An image information storage / retrieval device comprising: an update history processing unit that stores and reads document image data corresponding to a desired version based on the update history information.