JP7375586B2 - Document search device, image processing device, document search method, and document search program - Google Patents

Description

The present invention relates to a document retrieval device, an image processing device, a document retrieval method, and a document retrieval program, and in particular, a document retrieval device for retrieving document data that can be shared by multiple people, and an image processing device equipped with the document retrieval device. The present invention relates to a document retrieval device, a document retrieval method executed by the document retrieval device, and a document retrieval program that causes a computer to execute the document retrieval method.

In recent years, document structure analysis techniques for analyzing the structure of documents have become known. According to this document structure analysis technology, metadata indicating the content of constituent elements included in a document is generated, and its tag is associated with the document. Since meaning can be attached to data based on the contents of the constituent elements of a document, it is now possible to search for documents from various angles in addition to the conventional search using character strings. For example, from the memory of the structure of documents that the user has viewed in the past, it is possible to identify documents that the user has viewed in the past by searching using that structure.

For example, Japanese Patent Laid-Open No. 2008-299432 discloses a function for storing digitized document data as accumulated document data in a mass storage device installed in the main body of the device, and a function for managing the accumulated document data. a function for retaining and managing metadata for each stored document data in association with the stored document data, including information on the document, a document name for searching, a user name, or words characterizing the content of the document; A function of outputting accumulated document data stored in the device as document data to a portable mass storage device attached to the device body or an information terminal device connected via a network, and storing it in the mass storage device. a function for importing and outputting metadata accompanying document data to be output from a mass storage device, an editing function for arbitrarily registering, deleting, or changing the contents of the metadata; A function for converting the data format of stored document data or stored document data output to the portable mass storage device or the information terminal device, and for searching desired stored document data from among the stored document data. A function to search for desired stored document data using the metadata based on the search conditions specified by means for specifying the search conditions, and a function that matches the search conditions or a preset search condition. Accordingly, a data management device for an image forming device is described which is characterized by having a function of allowing a user to recognize corresponding stored document data.

However, in an environment where a document can be accessed by multiple people, the document may be changed by another user after the user previously viewed the document and before the user searches for the document again. In this case, since the structure of the document is changed from the time when the user viewed it in the past, there is a problem that it is difficult to specify desired document data by searching.

JP2008-299432A

One of the objects of the present invention is to provide a document search device that is capable of searching document data accessed by a plurality of people.

Another object of the present invention is to provide an image processing device that is capable of searching document data accessed by multiple people.

Still another object of the present invention is to provide a document search method that makes it possible to search document data accessed by multiple people.

Still another object of the present invention is to provide a document search program that is capable of searching document data accessed by multiple people.

According to an aspect of the present invention, a document retrieval device includes an analysis unit that analyzes the structure of document data and generates metadata indicating characteristics of constituent elements included in the document data; Accordingly, an associating means for associating the metadata generated by the analysis means for the document data at the time when the access is terminated with the user accessing the document data; A search means for searching using metadata associated with an instructing user who has instructed a search among the plurality of metadata.

According to this aspect, in response to document data being accessed by a user, metadata generated for the document data at the time the access ends is associated with the user, and multiple metadata associated with multiple users, respectively. The search is performed using metadata associated with the instructing user who instructed the search. Therefore, even if the document data that the user viewed in the past is changed by another user, the document data can be specified based on the memory of the user who viewed the document data. As a result, it is possible to provide a document search device that can search document data accessed by multiple people.

Preferably, the analysis means generates metadata for the changed version in response to changes to the document data.

According to this aspect, since the search is performed using metadata corresponding to the document data after the change, the document data can be searched based on the user's last viewed memory.

Preferably, the information processing apparatus further includes document management means for executing a display process for displaying the document data or a change process for changing the document data by accessing the document data.

According to this aspect, as the process of accessing document data, it is possible to execute a process of changing document data or a process of not changing document data.

Preferably, the document data extracted by the search by the search means using version control information indicating a history of changes made by the user accessing the document data has been changed since the last time the document data was accessed by the specified user. The apparatus further includes a change detecting means for detecting that the document data has been changed, and a change notifying means for notifying change information regarding the changed part when the change detecting means detects that the document data has been changed.

According to this aspect, it is possible to notify the user that the document data specified by the search is not the latest version and the changed portion.

Preferably, when executing the display process, the document management means does not change the document data while the document data is being displayed.

According to this aspect, when display processing is executed, document data can be prevented from being changed.

Preferably, if there is metadata for the same version of the document data at the time when the user accessing the document data ends, the association means can perform the association without having the analysis means analyze the document data. The apparatus further includes determining means for associating metadata for the same version as the document data with the designated user.

According to this aspect, if document data of the same version as the document data exists, metadata is not generated. For example, when display processing is executed, metadata generated in the past for displayed document data is associated with the user. Therefore, there is no need to execute the process of generating metadata, so the load can be reduced.

Preferably, when the document data is changed by accessing the document data by a user accessing the document data, metadata and document data that were previously generated by an analysis means for the document data before being changed are accessed. The information processing apparatus further includes a resolution means for dissolving the association with the user.

According to this aspect, when document data is changed, the association between the metadata corresponding to the document data before the change and the user is dissolved. Therefore, it is possible to associate the metadata of the document data that the user last accessed with the user.

Preferably, when the document data is changed, the document version management means stores the document data of each version before and after the change, and the metadata whose association with the user is canceled by the resolution means is not associated with any other user. If the metadata has not been deleted, the apparatus further includes document erasing means for erasing the document data of the version corresponding to the metadata.

According to this aspect, document data corresponding to metadata that is not associated with a user is deleted, so storage resources can be used effectively.

Preferably, the analysis means updates metadata for the document data at a predetermined timing regardless of changes in the document data.

According to this aspect, the metadata is updated at a predetermined timing regardless of changes in document data, so that the characteristics of the constituent elements can be updated to the latest state. For example, when performing analysis using deep learning, metadata can be generated depending on the degree of learning.

According to another aspect of the invention, an image processing device includes the above-described document search device and a document reading unit that reads a document and outputs image data representing an image of the document.

According to this aspect, it is possible to provide an image processing device that is capable of searching document data accessed by a plurality of people.

According to still another aspect of the present invention, a document retrieval method includes an analysis step of analyzing the structure of document data and generating metadata indicating characteristics of constituent elements included in the document data; an association step that associates the metadata generated in the analysis step for the document data at the time the access ends with the user accessing the document data, and associates each of the metadata with multiple users in the association step The document retrieval device is caused to perform a retrieval step of retrieving using metadata associated with the instructing user who has instructed the retrieval among the plurality of metadata retrieved.

According to this aspect, it is possible to provide a document search method that makes it possible to search document data accessed by multiple people.

According to still another aspect of the invention, the document search program includes an analysis step of analyzing the structure of document data and generating metadata indicating characteristics of constituent elements included in the document data; an association step that associates the metadata generated in the analysis step for the document data at the time the access ends with the user accessing the document data, and associates each of the metadata with multiple users in the association step The computer is caused to perform a search step of searching using metadata associated with an instructing user who has instructed the search among the plurality of metadata provided.

According to this aspect, it is possible to provide a document search program that makes it possible to search document data accessed by multiple people.

1 is a diagram showing an example of a document management system according to an embodiment of the present invention. 1 is a perspective view showing the appearance of an MFP in this embodiment. FIG. 2 is a block diagram showing an overview of the hardware configuration of the MFP. FIG. 2 is a block diagram illustrating an example of functions of a CPU included in the MFP. FIG. 3 is a diagram showing an example of first document data. FIG. 3 is a diagram for explaining first metadata. It is a figure which shows an example of metadata. FIG. 7 is a diagram showing an example of second document data. FIG. 3 is a diagram for explaining second metadata. FIG. 7 is a diagram showing an example of third document data. FIG. 7 is a diagram for explaining third metadata. FIG. 3 is a diagram showing an example of an access history table. FIG. 2 is a first diagram showing an example of an association table. FIG. 2 is a second diagram showing an example of an association table. FIG. 7 is a third diagram showing an example of an association table. 3 is a flowchart illustrating an example of the flow of access control processing. 3 is a flowchart illustrating an example of the flow of association control processing. 3 is a flowchart illustrating an example of the flow of search processing.

Embodiments of the present invention will be described below with reference to the drawings. In the following description, the same parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed explanations thereof will not be repeated.

FIG. 1 is a diagram showing an example of a document management system according to an embodiment of the present invention. Referring to FIG. 1, a document management system 1 includes an MFP (Multi Function Peripheral) 100 that functions as a document search device, and a personal computer (hereinafter referred to as "PC") 5. PC5 is a general computer. Its hardware configuration and functions are well known and will not be repeated here.

MFP 100 and PC 5 are connected via network 3 and can communicate with each other. The network 3 is a local area network (LAN), and the connection type may be wired or wireless. Further, the network 3 is not limited to a LAN, but may be a wide area network (WAN), a public switched telephone network (PSTN), the Internet, or the like.

FIG. 2 is a perspective view showing the appearance of the MFP in this embodiment. FIG. 3 is a block diagram showing an overview of the hardware configuration of the MFP. Referring to FIGS. 2 and 3, an MFP (Multi Function Peripheral) 100 includes a main circuit 110, a document reading section 130 that reads a document, an automatic document feeder 120 that conveys the document to the document reading section 130, and an image It includes an image forming section 140 that forms an image on paper based on data, a paper feed section 150 that supplies paper to the image forming section 140, and an operation panel 160 as a user interface.

The automatic document feeder 120 automatically transports a plurality of originals set on a document tray one by one to the original reading position of the original reading unit 130, and the image formed on the original is read by the original reading unit 130. eject the original onto the original ejection tray.

The image forming section 140 forms an image on a sheet of paper conveyed by the paper feeding section 150 using a well-known electrophotographic method. In the present embodiment, the image forming section 140 forms an image on the paper conveyed by the paper feeding section 150 using image data and image forming conditions corresponding to the medium type of the paper. The paper on which the image has been formed is ejected to a paper ejection tray.

The main circuit 110 includes a CPU (Central Processing Unit) 111 that controls the entire MFP 100, a communication interface (I/F) section 112, a ROM (Read Only Memory) 113, and a RAM (Random Access Memory) 114. It includes a hard disk drive (HDD) 115 as a mass storage device, a facsimile section 116, and an external storage device 118. CPU 111 is an example of a computer that executes a program. By executing a program, CPU 111 is connected to automatic document feeder 120, document reading section 130, image forming section 140, paper feeding section 150, and operation panel 160, and controls the entire MFP 100.

The ROM 113 stores programs executed by the CPU 111 or data necessary for executing the programs. The RAM 114 is used as a work area when the CPU 111 executes a program. Further, the RAM 114 temporarily stores image data continuously sent from the document reading section 130.

Operation panel 160 is provided at the top of MFP 100. Operation panel 160 includes a display section 161 and an operation section 163. The display unit 161 is, for example, a liquid crystal display (LCD), and displays an instruction menu for the user, information regarding the acquired image data, and the like. Note that instead of the LCD, an organic EL (electroluminescence) display, for example, can be used as a device that displays images.

The operation section 163 includes a touch panel 165 and a hard key section 167. The touch panel 165 is of a capacitive type. Note that the touch panel 165 is not limited to the capacitance type, and other types such as a resistive film type, a surface acoustic wave type, an infrared type, an electromagnetic induction type, etc. can be used. Hard key section 167 includes a plurality of hard keys. The hard key is, for example, a contact switch.

Communication I/F section 112 is an interface for connecting MFP 100 to network 3. The communication I/F unit 112 communicates with the PC 5 or other computers connected to the network 3 using a communication protocol such as TCP (Transmission Control Protocol) or FTP (File Transfer Protocol).

The facsimile unit 116 is connected to the public switched telephone network (PSTN) and transmits facsimile data to or receives facsimile data from the PSTN. The facsimile unit 116 stores the received facsimile data in the HDD 115, converts it into print data that can be printed by the image forming unit 140, and outputs the print data to the image forming unit 140. Thereby, the image forming section 140 forms an image of the facsimile data received by the facsimile section 116 on a sheet of paper. Furthermore, the facsimile unit 116 converts the data stored in the HDD 115 into facsimile data and transmits it to a facsimile device connected to the PSTN.

The external storage device 118 is controlled by the CPU 111, and is equipped with a CD-ROM (Compact Disk Read Only Memory) 118A or a semiconductor memory. In this embodiment, an example will be described in which the CPU 111 executes a program stored in the ROM 113, but the CPU 111 controls the external storage device 118 to read a program for the CPU 111 to execute from the CD-ROM 118A. , the read program may be stored in the RAM 114 and executed.

The CPU 111 controls the image forming unit 140 to form an image of image data on a recording medium such as paper. The image data that the CPU 111 outputs to the image forming section 140 includes image data input from the document reading section 130 as well as image data such as print data received from the outside.

Note that the recording medium that stores the program to be executed by the CPU 111 is not limited to the CD-ROM 118A, but may also include a flexible disk, a cassette tape, an optical disk (MO (Magnetic Optical Disc)/MD (Mini Disc))/DVD (Digital Versatile Disc). )), an IC card, an optical card, a mask ROM, an EPROM (Erasable Programmable ROM), and other semiconductor memories. Furthermore, the CPU 111 downloads a program from a computer connected to the network and stores it in the HDD 115, or the computer connected to the network writes the program to the HDD 115, and the program stored in the HDD 115 is loaded into the RAM 114. Alternatively, the CPU 111 may perform the processing. The programs referred to here include not only programs that can be directly executed by the CPU 111, but also source programs, compressed programs, encrypted programs, and the like.

FIG. 4 is a block diagram illustrating an example of the functions of a CPU included in the MFP. The functions shown in FIG. 4 are realized by CPU 111 included in MFP 100 by executing a document search program stored in ROM 113, HDD 115, or CD-ROM 118A.

Referring to FIG. 4, the CPU 111 includes an operating user identification section 51, a document management section 53, a metadata management section 55, an access history storage section 57, a determination section 59, an analysis section 61, and a search section 63. and a search result notification section 65.

The operating user specifying unit 51 specifies the user who operates the MFP 100. When a user operates MFP 100 using operation panel 160, operating user identification unit 51 identifies the user operating operation panel 160. For example, an authentication screen is displayed on the display unit 161, authentication information that the user inputs into the operation unit 163 according to the authentication screen is acquired, and a user identified by the authentication information is specified. The authentication information includes, for example, an ID for identifying the user. Furthermore, if the MFP 100 has an infrared communication function or a short-distance communication function using radio waves, it may receive information for identifying the user from a portable information device or an IC card carried by the user.

Furthermore, MFP 100 may be remotely controlled by an external computer. For example, a user operating the PC 5 may remotely control the MFP 100. The operating user identification unit 51 communicates with the PC 5 via the communication I/F unit 112 and transmits an authentication screen to the PC 5. Since the PC 5 displays an authentication screen, when the user follows the authentication screen and inputs authentication information into the PC 5, the PC 5 transmits the received authentication information to the MFP 100. The operating user identifying unit 51 identifies the user identified by the authentication information that the communication I/F unit 112 receives from the PC 5.

Hereinafter, the user who operates the operating unit 163 and the user who operates the PC 5 to remotely control the MFP 100 are collectively referred to as operating users. Further, an operation input into the operation unit 163 by a user operating the operation unit 163 or a remote operation input into the PC 5 by a user who operates the PC 5 to remotely control the MFP 100 is collectively referred to as a user operation. In response to specifying the operating user, the operating user identification unit 51 outputs a user ID (identification) for identifying the operating user to the document management unit 53 and the search unit 63.

The document management unit 53 manages document data stored in the HDD 115. The document data is data representing a document, and includes data in which character information is encoded, image data in which characters are represented as images, and data in which figures or photographs are represented in images. The document data stored in the HDD 115 includes image data read and output by the document reading section 130, print data received from a computer connected to the network 3 via the communication I/F section 112, such as PC5, and facsimile section 116. This includes facsimile data received by the external storage device 118 and data read from the CD-ROM 118A or semiconductor memory attached to the external storage device 118. Further, the document data managed by the document management unit 53 may include data stored in the HDD 115 by a user operating the PC 5 by remotely operating the MFP 100. The document management section 53 includes a document access section 71, a document version management section 73, and a document deletion section 75.

The document access unit 71 executes a process of accessing document data according to a user operation by an operating user. The process in which the document access unit 71 accesses document data includes a display process in which the document access unit 71 displays data, and a change process in which the document access unit 71 changes the document data. The change process executed by the document access unit 71 includes a storage process in which the document access unit 71 stores new data in the HDD 115 and an update process in which the document access unit 71 changes existing data stored in the HDD 115. When storing document data in the HDD 115, the document access unit 71 gives the document data identification information for identifying the document data. The identification information includes a file name and a version. The document access unit 71 adds a version indicating that it is the first version to the document data when executing the storage process, and adds a version that is counted up from the version attached to the document data before the update when executing the update process. Added to the updated document data. Since the document data before the update and the document data after the update have different identification information, they are treated as different data. Specifically, when executing the update process and storing the updated document data in the HDD 115, the document access unit 71 does not overwrite the document data before the update, but stores it in the HDD 115 as separate document data. do. The document access unit 71 outputs the new version identification information to the document version management unit 73 when adding the new version identification information to document data.

When the document access unit 71 executes the process of accessing document data, it notifies the access history storage unit 57 and the determination unit 59 of the accessed document data and the operating user. Here, the document access unit 71 outputs a set of identification information for identifying document data and the user ID of the operating user to the access history storage unit 57 and the determination unit 59. Specifically, when executing the display process, the document access unit 71 outputs a pair of the identification information of the displayed document data and the operating user to the access history storage unit 57 and the determination unit 59, and executes the change process. If so, the set of the changed identification information of the document data and the operating user is output to the access history storage section 57 and the judgment section 59.

A specific example of the storage process executed by the document access unit 71 will be described. When the operating user operates the operation panel 160 to cause the document reading section 130 to read a document, the document access section 71 identifies the image data that the document reading section 130 reads and outputs the document as document data. Information is added and stored in the HDD 115. It is shown that the version included in the identification information is the first edition. Further, the document access unit 71 outputs a set of the identification information of the document data and the user ID of the operating user to the access history storage unit 57 and the determination unit 59, and outputs the identification information of the document data to the document version management unit 73. do.

Further, when print data is received from the PC 5 by the communication I/F unit 112, the document access unit 71 stores the print data as document data in the HDD 115 by adding identification information to the document data. It is shown that the version included in the identification information is the first edition. Further, the document access unit 71 outputs a set of the identification information of the document data and the user ID received by the communication I/F unit 112 together with the print data to the access history storage unit 57 and the determination unit 59, and The identification information is output to the document version management section 73.

Further, when facsimile data is received by the facsimile unit 116, the document access unit 71 stores the facsimile data as document data in the HDD 115 by adding identification information to the document data. It is shown that the version included in the identification information is the first edition. Further, the document access unit 71 outputs a set of the identification information of the document data and the user ID of the sender of the facsimile data to the access history storage unit 57 and the determination unit 59, and also outputs the identification information of the document data to the document version management unit. 73. A user table is prepared in advance in which facsimile numbers of facsimile data senders are associated with user IDs, and user IDs are identified from the facsimile numbers of facsimile data senders.

Further, when data is read from the semiconductor memory by the external storage device 118, the document access unit 71 stores the data read from the semiconductor memory as document data in the HDD 115 by adding identification information to the document data. It is shown that the version included in the identification information is the first edition. Further, the document access unit 71 outputs a set of the identification information of the document data and the user ID of the operating user who inputted the operation instructing reading into the operation unit 163 to the access history storage unit 57 and the determination unit 59, and Data identification information is output to the document version management section 73.

A specific example of the update process executed by the document access unit 71 will be described. When the user operating the operation panel 160 edits and changes the document data stored in the HDD 115, the document access unit 71 adds identification information to the changed document data and stores it in the HDD 115. When the document data is changed, the changed document data is changed from the document data before the change. Therefore, the document data before the change and the document data after the change are different. The identification information given to the document data after the change includes the same file name as the file name of the identification information given to the document data before the change, and a version in which the version is counted up. Further, the document access unit 71 outputs a set of the identification information of the changed document data and the user ID of the operating user to the access history storage unit 57 and the determination unit 59, and also outputs the identification information of the changed document data to the access history storage unit 57 and the determination unit 59. It is output to the version management section 73.

A specific example of display processing executed by the document access unit 71 will be described. When the user operating the operation panel 160 specifies identification information of document data stored in the HDD 115, the document access section 71 displays the document data identified by the identification information on the display section 161. The document data is not changed before and after being displayed on the display section 161. In this case, the document access unit 71 does not store the displayed document data in the HDD 115. Further, the document access unit 71 outputs a set of the identification information of the document data and the user ID of the operating user to the access history storage unit 57 and the determination unit 59.

The access history storage unit 57 stores access history information in response to input of a combination of identification information and user ID from the document access unit 71. The access history information includes identification information, a user ID, and the date and time when these are input from the document access unit 71. Specifically, the access history storage unit 57 generates an access record including identification information, a user ID, and date and time, and adds the access record to the access history table stored in the HDD 115.

The document version management unit 73 manages versions of document data. Specifically, in response to input of identification information from the document access unit 71, the document version management unit 73 stores the identification information in association with the date and time when the identification information is input. More specifically, document version management section 73 generates a version record including identification information and date and time, and adds the version record to the version management table stored in HDD 115. When identification information is input from the document access unit 71, it is a case where a change process is executed by the document access unit 71. In other words, when the document data of the first version is stored in the HDD 115, or when the document data of the first version is stored in the HDD 115. This is a case where the document data that has been updated is updated.

In response to input of a pair of identification information and user ID from the document access unit 71, the determination unit 59 determines whether document data of the same version as the document data specified by the identification information is accessed by the document access unit 71. It is determined whether or not the data was stored in the HDD 115 before being downloaded. Specifically, the determination unit 59 refers to the version management table, extracts a version record including identification information input from the document access unit 71, and determines the date and time included in the extracted version record from the document access unit 71. From this, it is determined whether or not the date and time at which the pair of identification information and user ID is input is earlier than the date and time.

The determining unit 59 analyzes if the date and time included in the version record including identification information input from the document access unit 71 is the same as the date and time at the time when the pair of identification information and user ID is input from the document access unit 71. It outputs an analysis instruction to the unit 61 to start analysis, and outputs an association instruction to the metadata management unit 55. The analysis instruction includes identification information input from the document access unit 71. The association instruction includes a pair of identification information input from the document access unit 71 and a user ID.

The determination unit 59 analyzes if the date and time included in the version record including identification information input from the document access unit 71 is before the date and time at which the pair of identification information and user ID is input from the document access unit 71. An association instruction is output to the metadata management section 55 without outputting an analysis instruction to the section 61.

In response to input of the analysis instruction from the determination unit 59, the analysis unit 61 analyzes the structure of the document data specified by the identification information included in the analysis instruction, and indicates the characteristics of the constituent elements included in the document data. Generate metadata. The analysis unit 61 uses deep learning to analyze document data. For example, the analysis unit 61 performs image processing on document data to extract constituent elements, and determines the characteristics of each constituent element. The components can be, for example, a text area where characters are displayed, a graphic area where graphics are displayed, and a photo area where a photo is displayed. As the characteristics of a component, the image type represented by the component, the position of the component in the document data, the color of the component, and the shape of the component can be used. The image type is a character type indicating that the constituent elements of the text area are composed of characters, a figure type indicating that the constituent elements of the graphic area are composed of figures, and a constituent element of the photo area is composed of photographs. It can be a photo type that indicates that In this case, the metadata includes the image type for each component and position information indicating the position in the document data. Note that the analysis of document data by the analysis unit 61 is not limited to this.

Note that the timing at which the analysis unit 61 analyzes document data is not limited to when an analysis instruction is input, but may be performed each time document data is accessed. If the document data is accessed but no analysis instruction is input, the metadata before analysis is updated with the metadata that is the analysis result without changing the metadata identification information.

When generating metadata, the analysis unit 61 stores the generated metadata in the HDD 115 in association with the document data. Specifically, the analysis unit 61 adds metadata identification information for identifying the metadata as a file name to the metadata, and stores the metadata in the HDD 115. The metadata identification information includes identification information of document data. Metadata corresponds to the document data from which it was generated. Therefore, when document data is specified, one piece of metadata corresponding to the document data is specified. Furthermore, when generating metadata, the analysis unit 61 outputs metadata identification information to the metadata management unit 55.

The metadata management section 55 includes an association section 81, a resolution section 83, and a metadata update section 85. The association unit 81 associates an operating user with metadata corresponding to document data that is a target of processing performed in accordance with an operation input by the operating user. The association unit 81 receives an association instruction from the determination unit 59 . When the metadata identification information is input from the analysis unit 61, the association unit 81 generates information generated from document data processed by the operating user in response to an association instruction input from the determination unit 59. Associate metadata with operating users. Specifically, the association unit 81 generates an association record including metadata identification information including identification information included in the association instruction and a user ID included in the association instruction, and The record is added to and stored in the association table stored in the HDD 115.

If metadata identification information is not input from the analysis unit 61 to the association unit 81, the document data targeted for processing by the operating user has not been changed. For this reason, metadata has been generated in the past from document data that has been processed by an operating user. The association unit 81 associates the operating user with metadata generated in the past from document data processed by the operating user. Specifically, in response to the association instruction being input from the determination unit 59, the association unit 81 extracts an association record containing the same identification information as the identification information included in the association instruction from the association table. Then, it generates an association record including the metadata identification information included in the extracted association record and the user ID included in the association instruction, and uses the generated association record as an association record stored in the HDD 115. Add to table and remember.

When the document data is changed by access to the document data by the operating user, the dissolving unit 83 disassociates the metadata corresponding to the document data before the change from the operating user. Specifically, in response to the addition of a new association record to the association table by the association unit 81, the resolution unit 83 generates a user ID that is the same as the user ID included in the new association record that has been added. , and which includes identification information with the same file name as the file name of the identification information included in the added new association record, is deleted from the association table. The extracted associated record differs from the newly added associated record only in the version of the identification information, and the metadata corresponding to the document data before the document data was changed by the operation user's access to the document data. Associate with the operating user.

When deleting an associated record, if there is no other associated record in the associated table that includes the same identification information as the identified information included in the deleted associated record, the elimination unit 83 sends a deletion instruction to the document deletion unit. Output to 75. The deletion instruction includes identification information included in the associated record to be deleted.

The document erasing unit 75 erases the document data specified by the identification information included in the erasing instruction from the HDD 115 in response to the erasing instruction input from the erasing unit 83 . As a result, document data corresponding to metadata that is not associated with any user is not stored in the HDD 115, so that the storage area of the HDD 115 can be used effectively. The document deletion unit 75 outputs the deletion result to the document version management unit 73 in response to deleting document data. The deletion result includes identification information of the deleted document data.

In response to input of the deletion result from the document deletion unit 75, the document version management unit 73 refers to the version management table and deletes the version record including the identification information included in the deletion result from the version management table. As a result, version records that are not scheduled to be used are deleted, so that the processing load for extracting version records from the version management table can be reduced, and the storage area of the HDD 115 can be used effectively.

The metadata update unit 85 updates metadata. The analysis unit 61 uses deep learning to analyze document data. Therefore, even if the document data is the same, the metadata may differ depending on the degree of learning performed by the analysis unit 61. Therefore, the metadata update unit 85 controls the analysis unit 61 at a predetermined timing to analyze the document data stored in the HDD 115 and generate metadata. When causing the analysis unit 61 to analyze document data, the metadata update unit 85 updates the metadata stored in the HDD 115 corresponding to the document data with metadata newly generated by analysis by the analysis unit 61. Therefore, since the analysis unit 61 updates the metadata at a predetermined timing, it is possible to generate metadata according to the degree of learning.

The search unit 63 searches document data stored in the HDD 115 according to search conditions input by an instructing user. The instruction user is one of the operating users who operate MFP 100 who instructs to search document data. The search condition includes at least one of the type, position, color, and shape of the component included in the document data. The position indicates the position in the document data, the color indicates the color of the image of the component, the type indicates the image type, and the shape indicates the shape of the component.

The search unit 63 searches for document data using metadata associated with the instruction user from among the metadata stored in the HDD 115 according to an instruction from the instruction user. Specifically, the search unit 63 extracts an association record including the user ID of the instructed user from the association table, and searches for metadata specified by metadata identification information included in the extracted association record. set to target. Instructions The instructions input by the user include at least one designation of the type, position, color, and shape of the component. For example, a case will be explained in which an instruction is given in which the type of component is specified as the character type and the position is specified in the upper right. The search unit 63 refers to the association table stored in the HDD 115 and extracts all association records including the user ID of the instructed user. Then, the search unit 63 sets the metadata specified by the metadata identification information included in the extracted association record as a search target. Then, the search unit 63 extracts, from the extracted metadata, metadata that includes a component whose type is character type and whose position is set to the upper right. The search unit 63 outputs the user ID of the instructing user and the metadata identification information of the extracted metadata to the search result notification unit 65.

The search result notification unit 65 notifies the instructing user of the search results obtained by the search unit 63. The search result notification unit 65 displays document data corresponding to the metadata specified by the metadata identification information input from the search unit 63 on the display unit 161.

The search result notification unit 65 includes a change detection unit 91 and a change notification unit 93. The change detection unit 91 detects that the document data extracted by the search by the search unit 63 has been changed since the last access by the designated user. Specifically, the change detection unit 91 determines the identification information of the document data corresponding to the metadata in response to the metadata identification information input from the search unit 63. The document data specified by the identification information determined here is the document data that was last accessed by the operating user. The change detection unit 91 extracts a version record having the same file name as the document data last accessed by the operating user from the version control table, and determines whether there is a version record with a newer version than the version of the document data last accessed by the operating user. Decide whether or not to do so. If the change detection unit 91 determines that there is a newer version of the document data than the version of the document data last accessed by the operating user, the change detection unit 91 identifies the latest version of the document data, and identifies the latest version of the document data. is output to the change notification section 93.

When the identification information of the latest version of document data is input from the change detection unit 91, the change notification unit 93 detects the difference between the document data last accessed by the operating user and the latest version of the document data, The detected difference is displayed on the display section 161. Specifically, the change notification unit 93 displays the latest version of the document data side by side with the document data last accessed by the operating user. The change notification section 93 displays the correspondence of the constituent elements. For example, the change notification unit 93 associates each of the plurality of constituent elements included in the document data last accessed by the operating user with the corresponding constituent element among the plurality of constituent elements included in the latest version of the document data. indicate. For example, the change notification unit 93 displays two corresponding components in the same display mode and in a different display mode from other components. The display mode includes, for example, brightness and color. Further, the change notification section 93 displays an image of a figure connecting two corresponding components.

FIG. 5 is a diagram showing an example of first document data. Referring to FIG. 5, first document data 200 includes components 211, 212, and 213. The component 211 is located at the upper left of the first document data 200 and is a rectangular character type representing a monochrome character. The component 212 is a rectangular photo type that is placed in the upper right corner of the first document data 200 and represents a color photo. The component 213 is a rectangular graphic type that is arranged below in the document data and represents a colored graph.

FIG. 6 is a diagram for explaining the first metadata. Referring to FIG. 6, element metadata 221 corresponding to component 211, element metadata 222 corresponding to component 212, and element metadata 223 corresponding to component 213 included in first document data 200. is shown. The element metadata includes the position, color, type, and shape of each component as characteristics of that component. The position indicates the position in the document data, the color indicates the color of the image of the component, the type indicates the image type, and the shape indicates the shape of the component. In the element metadata 221 corresponding to the component 211, the position is upper left, the color is monochrome, the type is a character indicating the character type, and the shape is square. In addition, the element metadata 222 corresponding to the component 212 has a position set to the upper right, a color set to color, a type set to a photo indicating the type of photo, and a shape set to a square. In the element metadata 223 corresponding to the component 213, the position is set to bottom, the color is set to color, the type is set to a figure indicating the type of figure, and the shape is set to square.

FIG. 7 is a diagram showing an example of metadata. In FIG. 7, first metadata 210 corresponding to first document data 200 is shown. The first metadata 210 associates a component with element metadata corresponding to the component. First metadata 210 includes multiple metadata records. The metadata record includes a tag ID item and a component ID item. In the tag ID field, a tag ID for identifying a component is set, and in the component ID field, a component ID for identifying a component is set. Specifically, the first metadata 210 includes a metadata record including a tag ID 211A of the component 211 and a component ID 221A of the element metadata 221, a tag ID 212A of the component 212, and a component ID 222A of the element metadata 222. and a metadata record including the tag ID 213A of the component 213 and the component ID 223A of the element metadata 223.

FIG. 8 is a diagram showing an example of second document data. Referring to FIG. 8, second document data 200A is the first document data 200 that has been changed. Specifically, the component 211 is enlarged to a larger size and moved to the upper position in the second document data 200A, and the component 212 is reduced to a smaller size and moved to the lower left position in the second document data 200A. The component 213 is reduced in size and changed to the lower right position in the second document data 200A.

FIG. 9 is a diagram for explaining the second metadata. Referring to FIG. 9, element metadata 231 corresponding to component 211, element metadata 232 corresponding to component 212, and element metadata 233 corresponding to component 213 included in second document data 200A. is shown. In the element metadata 231 corresponding to the component 211, the position is set as top, the color as monochrome, the type as text, and the shape as square. Further, the element metadata 232 corresponding to the component 212 has a position of lower left, a color of color, a type of photograph, and a shape of square. In the element metadata 233 corresponding to the component 213, the position is set to the lower right, the color is set to color, the type is set to figure, and the shape is set to square.

FIG. 10 is a diagram showing an example of third document data. Referring to FIG. 10, third document data 200B is obtained by changing second document data 200A. Specifically, the component 211 is changed to the lower position in the second document data 200A, the component 212 is changed to the upper left position in the second document data 200A, and the component 213 is changed to the lower position in the second document data 200A. Changed to the top right position in the middle.

FIG. 11 is a diagram for explaining the third metadata. Referring to FIG. 11, element metadata 241 corresponding to component 211, element metadata 242 corresponding to component 212, and element metadata 243 corresponding to component 213 included in third document data 200B. is shown. In the element metadata 241 corresponding to the component 211, the position is defined as bottom, the color is monochrome, the type is text, and the shape is square. Further, the element metadata 242 corresponding to the component 212 has a position of upper left, a color of color, a type of photograph, and a shape of square. In the element metadata 243 corresponding to the component 213, the position is upper right, the color is color, the type is figure, and the shape is square.

FIG. 12 is a diagram showing an example of an access history table. Referring to FIG. 12, the access history table includes four access history records. The access history record is No. , an identification information item, a user item, a date and time item, and an access content item. No. In the field, a number is set to identify the access history record. An arbitrary number is set as the number. Here, No. In the field, numbers are set that are sequentially numbered in the order in which access history records are added to the access history table. In the identification information item, identification information of the document data to be accessed is set. The identification information items include a file name item and a version item. A file name given to the document data is set in the file name field, and a version given to the document data is set in the version field. User identification information for identifying the operating user who accessed the document data is set in the user item. In the date and time field, the date and time when the document data was accessed by the operating user is set. In the access content item, process identification information for identifying the process executed when the document data is accessed by the operating user is set. The process identification information includes storage as process identification information for identifying a storage process, update as process identification information for identifying an update process, and display for identifying a display process.

No. The access history record 1 indicates that the first document data 200 was stored in the HDD 115 by user A at 12:00 on 2020/01/01. Here, as the identification information of the first document data 200, a case is shown in which D1 is added to the file name and the first version is added to the version.

No. The access history record No. 2 indicates that the first document data 200 stored in the HDD 115 was displayed by user B at 12:00 on 2020/01/02.

No. The access history record No. 3 indicates that the first document data 200 stored in the HDD 115 was changed to the second document data 200A by user A at 12:00 on 2020/01/03. Here, an example is shown where D1 is added to the file name and the second version is added to the version as the identification information of the second document data 200A.

No. The access history record No. 4 indicates that the second document data 200A stored in the HDD 115 was changed to the third document data 200B by user B at 12:00 on 2020/01/04. Here, an example is shown where D1 is added to the file name and the third version is added to the version as the identification information of the third document data 200B.

FIG. 13 is a first diagram showing an example of an association table. The association table shown in FIG. 13 shows the association table as of 2020/01/02 12:00. Referring to FIG. 13, the association table includes two association records. The associated record is No. , an identification information item, a metadata item, and a user item. No. In the field, a number is set to identify the associated record. An arbitrary number is set as the number. Here, No. A number is set in the field that is assigned sequentially in the order in which associated records are added to the associated table. In the identification information item, identification information of the document data to be accessed is set. The identification information items include a file name item and a version item. A file name given to the document data is set in the file name field, and a version given to the document data is set in the version field. Metadata identification information of metadata corresponding to the document data specified by the identification information is set in the metadata item. User identification information for identifying the operating user who accessed the document data is set in the user item.

At the stage of 2020/01/01 12:00, the first document data 200 is stored in the HDD 115 by user A, so the number is set to No. 1 association record is added to the association table. The number is No. The first association record associates with user A the first metadata corresponding to the first document data 200 with the file name D1 and the first version. At this stage, the first document data 200 is analyzed and first metadata is generated.

Thereafter, at 12:00 on 2020/01/02, the first document data 200 stored in the HDD 115 by user B is displayed, and the number is displayed. 2 association records are added to the association table. The number is No. The association record No. 2 associates with user B the first metadata corresponding to the first document data having the file name D1 and the first version. The number is No. Since the first metadata has been generated at the stage when the second association record is added to the association table, the first document data is not analyzed.

FIG. 14 is a second diagram showing an example of the association table. The association table shown in FIG. 14 shows the association table as of 2020/01/03 12:00. Referring to FIG. 14, at the stage of 2020/01/03 12:00, the first document data 200 stored in the HDD 115 is changed by the user A to the second document data 200A, so that the number is changed to No. 3 association records are added to the association table. The number is No. The association record No. 3 associates with user A the second metadata corresponding to the second document data 200A having the file name D1 and the second version.

At this stage, the second document data 200A is analyzed and second metadata is generated. Further, since the first document data 200 is changed to the second document data 200A by accessing the first document data 200 by the user A, the first metadata corresponding to the first document data 200 before the change and the user The number associated with A is No. 1 association record is deleted from the association table.

FIG. 15 is a third diagram showing an example of the association table. The association table shown in FIG. 15 shows the association table as of 2020/01/04 12:00. Referring to FIG. 15, at the stage of 2020/01/04 12:00, the second document data 200A stored in the HDD 115 is changed to the third document data 200B by user B, so that the number is changed to No. 4 association records are added to the association table. The number is No. The association record No. 4 associates with user B the third metadata corresponding to the third document data 200B having the file name D1 and the third version.

At this stage, the third document data 200B is analyzed and third metadata is generated. Further, since the third document data 200B is accessed by user B, the number that associates user B with the first metadata corresponding to the version of the first document data 200 before being changed to the third document data 200B is No. 2 association record is deleted from the association table. Further, at this stage, the first metadata corresponding to the first version of the first document data 200 is not associated with either user A or user B, so the first metadata and the first document data 200 are It is erased from the HDD 115.

FIG. 16 is a flowchart showing an example of the flow of access control processing. The access control process is a process executed by CPU 111 included in MFP 100 when CPU 111 executes a document search program stored in ROM 113, HDD 115, or CD-ROM 118A.

Referring to FIG. 16, CPU 111 identifies operation target data (step S01), and advances the process to step S02. Specifically, CPU 111 identifies data instructed by a user operating MFP 100 as operation target data. CPU 111 specifies document data instructed by an operating user operating MFP 100 from among the document data stored in HDD 115 as operation target data. For example, when the operating user causes the document reading section 130 to read a document, the CPU 111 specifies the image data output by the document reading section 130 as the operation target data. Further, when the operating user operating the PC 5 remotely operates the MFP 100 and instructs the MFP 100 to transmit data such as print data from the PC 5, the CPU 111 specifies the data received from the PC 5 as the operation target data. Furthermore, when the facsimile unit 116 receives facsimile data from an external facsimile device, the CPU 111 specifies the received facsimile data as operation target data. Furthermore, when the operating user instructs to read data from the semiconductor memory attached to the external storage device 118, the CPU 111 specifies the read data as the data to be operated. Further, when the operating user specifies any of the document data stored in the HDD 115, the CPU 111 specifies the specified document data as the data to be operated.

In step S02, the operating user is specified. When a user operates MFP 100 using operation panel 160, the user operating operation panel 160 is specified. Further, when the MFP 100 is remotely controlled by an external computer such as the PC 5, the user operating the PC 5 is specified as the operating user. Furthermore, when facsimile data is received, the user associated with the number assigned to the facsimile device that is the source of the facsimile data is specified as the operating user.

In step S03, it is determined whether the operation by the operating user has ended. For example, it is determined that the operation by the operating user has ended when the operating user inputs an instruction to end the operation, when a predetermined period of time has elapsed without accepting any operation by the operating user, or when the reception of facsimile data is completed. . If the operation by the operating user is completed, the process proceeds to step S04, but if not, the process returns to step S01.

In step S04, it is determined whether document data having the same file name as the operation target data is stored in the HDD 115. If document data having the same file name as the operation target data is stored in the HDD 115, the process proceeds to step S05, but otherwise the process proceeds to step S06. In step S06, the operation target data is stored in the HDD 115 as the initial version of the document data, and the process proceeds to step S08.

In step S05, it is determined whether the latest version of the document data having the same file name as the operation target data is the same as the operation target data. If the operation target data and document data are the same, the process proceeds to step S10, but otherwise the process proceeds to step S07. If the latest version of the document data having the same file name as the operation target data is the same as the operation target data, the process executed on the operation target data according to the operation of the operating user is a display process. If the latest version of document data having the same file name as the operation target data is not the same as the operation target data, the process executed on the operation target data according to the operation of the operating user is a change process.

In step S07, the version of the document data that is the latest version of the document data that has the same file name as the operation target data is determined, and the version that has the operation target data counted up is stored in the HDD 115. is stored as document data, and the process proceeds to step S08.

In step S08, the access history information is stored in the HDD 115, and the process proceeds to step S09. In step S06 or step S07, an access history record containing the identification information of the document data stored in the HDD 115, the user ID of the operating user, and the date and time at that time is generated and added to the access history table stored in the HDD 115. be done. In step S09, the document data is analyzed, and the process proceeds to step S13. Metadata is generated by analyzing document data.

In step S10, access history information is stored in the HDD 115, and the process proceeds to step S11. An access history record including identification information of the same document data as the operation target data, the user ID of the operating user, and the current date and time is generated and added to the access history table stored in the HDD 115. In step S11, metadata is specified, and the process proceeds to step S12. Metadata corresponding to the same document data as the operation target data is identified. Specifically, an association record including identification information of the same document data as the operation target data is extracted from an association table stored in the HDD 115, and metadata identification information set in the association record is determined. be done.

In step S12, it is determined whether the identified metadata and the operating user have been associated. If an association record containing the metadata identification information of the identified metadata and the user ID of the operating user exists in the association table, it is determined that the association has been completed, but if such an association record does not exist, It is determined that there is no association. If the metadata and the operating user have been associated, the process returns to step S01; otherwise, the process proceeds to step S13. In step S13, an association control process is executed, and the process returns to step S01.

FIG. 17 is a flowchart illustrating an example of the flow of association control processing. The association control process is a process executed in step S13 of the access control process. Before the association control process is executed, the operating user and the metadata to be processed are identified. Referring to FIG. 17, CPU 111 associates the metadata to be processed with the operating user, and advances the process to step S22 (step S21). An association record is generated that includes identification information of document data corresponding to the metadata, metadata identification information for identifying the metadata, and the user ID of the operating user.

In step S22, the association record is added to the association table, and the process proceeds to step S23. In step S23, it is determined whether the operating user is associated with the old version of metadata. If there is an association record that associates the operating user's user ID with metadata whose version is older than the metadata to be processed, it is determined that the operating user is associated with the older version of the metadata. Specifically, an association record that includes the user ID of the operating user and has the same file name as the document data corresponding to the metadata to be processed is extracted from the association table. If there is an associated record that includes identification information of an older version of document data than the version of document data corresponding to the metadata to be processed among the extracted associated records, the operating user Determine that it is associated with the data. If the operating user is associated with the old version of metadata, the process proceeds to step S24, but if not, the process returns to the access control process.

In step S24, the association with the old version of metadata with which the operating user is associated is canceled, and the process proceeds to step S25. Specifically, an association record including identification information of a version of document data older than the version of document data corresponding to the metadata to be processed is deleted from the association table.

In step S25, it is determined whether there is a user associated with the old version of metadata. It is determined that a user associated with an older version of metadata exists and such an association is If the record does not exist in the association table, it is determined that the user associated with the previous version of metadata does not exist. If there is no user associated with the old version of the metadata, the process proceeds to step S26, but if there is a user associated with the old version of the metadata, the process returns to the access control process.

In step S26, the document data corresponding to the old version of the metadata is deleted, and the process returns to the access control process.

FIG. 18 is a flowchart showing an example of the flow of search processing. The search process is a process executed by CPU 111 included in MFP 100 when CPU 111 executes a document search program stored in ROM 113, HDD 115, or CD-ROM 118A. Referring to FIG. 18, CPU 111 identifies the designated user and advances the process to step S32 (step S31). When a user operates MFP 100 using operation panel 160, the user operating operation panel 160 is specified as an instruction user. Furthermore, when the MFP 100 is remotely controlled by an external computer such as the PC 5, the user who operates the PC 5 is specified as the designated user.

In step S32, the search conditions are accepted, and the process proceeds to step S33. The search condition includes at least one of the position, color, type, and shape of the component included in the document data. The position indicates the position in the document data, the color indicates the color of the image of the component, the type indicates the image type, and the shape indicates the shape of the component.

In step S33, metadata associated with the designated user is searched according to the search conditions accepted in step S32. Metadata matching the search condition is extracted from the metadata associated with the designated user. An association record including the user ID of the instruction user is extracted from the association table, and the metadata specified by the metadata identification information included in the extracted association record is the metadata associated with the instruction user. be identified. Since the metadata associated with the designated user is searched, it is possible to search for document data from memories that the designated user has viewed in the past. In particular, even if the document data is changed by another person after the designated user viewed it in the past, the document data can be retrieved from the memory of the designated user's past viewings.

In step S34, document data matching the search conditions is identified, and the process proceeds to step S35. In step S33, document data corresponding to the metadata extracted by the search is specified. In step S35, the document data specified in step S34 is displayed, and the process proceeds to step S36. When the instructed user operates the operation panel 160, document data is displayed on the display unit 161, and when the instructed user remotely operates the MFP 100 using the PC 5, the document data is displayed on the PC 5.

In step S36, it is determined whether there is document data whose version is newer than the document data specified in step S34. If there is document data with a newer version than the document data specified in step S34, the process proceeds to step S37, but if not, the process ends.

In step S37, the changed portion from the document data specified in step S34 is specified, and the process proceeds to step S38. The difference between the document data specified in step S34 and the new version of the document data is extracted, and the difference is specified as a changed portion.

In step S38, the changed location is displayed. For example, the document data identified in step S34 and the new version of the document data are displayed side by side, and the changed portion is displayed in a different display manner from other portions. The display mode includes brightness, color, and hue. Furthermore, an arrow pointing to the changed location may be displayed. Thereby, it is possible to notify the instruction user of the fact that the displayed document data has been changed by another person and the details of the change.

Note that in this embodiment, the MFP 100 functioning as an image processing device has been described as an example of a document search device, but the document search device may be realized by the PC 5. The document search device may be any device that includes a central processing unit, a storage device that stores data, and an operation section that can be operated by a user.

As described above, the MFP 100 in this embodiment functions as a document search device, and the CPU 111 analyzes the structure of document data, generates metadata indicating the characteristics of the constituent elements included in the document data, and When the document data is accessed by a user, the metadata generated for the document data at the time the access ends is associated with the user accessing the document data, and multiple metadata associated with multiple users are The search is performed using metadata associated with the instructing user who instructed the search. Therefore, even if the document data that the user viewed in the past is changed by another user, the document data can be specified based on the memory of the user who viewed the document data. Therefore, document data accessed by multiple users can be searched by multiple users.

Furthermore, in response to changes to the document data, the CPU 111 generates metadata for the changed version. Therefore, since the search is performed using metadata corresponding to the document data after the change, the document data can be searched based on the user's last viewed memory.

Further, the CPU 111 executes a display process for displaying document data or a change process for changing document data by accessing the document data. Therefore, the CPU 111 can execute a process of changing document data or a process of not changing document data, as a process of accessing document data.

The CPU 111 also searches a version control table that shows the history of changes made to the document data by the user accessing the document data, thereby determining whether the document data extracted by the search has been changed since the last time it was accessed by the designated user. If it is detected that the document data has been changed, the user is notified of the change information regarding the changed part. Therefore, it is possible to notify the user that the document data extracted by the search is not the latest version and that the portion has been changed.

Further, when executing the display process, the CPU 111 does not change the document data while the document data is being displayed. Therefore, although the document data is accessed, it is possible to prevent the document data from being changed.

In addition, if there is metadata for the same version of the document data at the time when the user accessing the document data has finished accessing the document data, the CPU 111 executes the metadata that is the same as the document data without analyzing the document data. Associating metadata for the version with the indicated user. Therefore, if document data of the same version as the document data accessed by the user exists, metadata is not generated. For example, when display processing is executed, metadata generated in the past for displayed document data is associated with the user. Therefore, there is no need to execute the process of generating metadata, so the load can be reduced.

In addition, when the document data is changed due to access by a user accessing the document data, the CPU 111 also controls metadata generated in the past for the document data before the change and the user accessing the document data. Disassociate from. Therefore, it is possible to associate the metadata corresponding to the document data that the user last accessed with the user.

In addition, when document data is changed, the CPU 111 stores the document data for each version before and after the change, and when metadata that has been disassociated from a user is not associated with any other user, the CPU 111 Delete the document data of the version corresponding to the data. Therefore, the storage area of the HDD 115 can be used effectively.

Further, the CPU 111 updates metadata for the document data at a predetermined timing regardless of changes to the document data. The predetermined timing may be determined in advance. Therefore, regardless of changes in document data, the metadata is updated at a predetermined timing, so that the characteristics of the constituent elements can be kept up to date. When performing analysis using deep learning, metadata can be generated according to the degree of learning.

The embodiments disclosed this time should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims rather than the above description, and it is intended that all changes within the meaning and range equivalent to the claims are included.

5 PC, 100 MFP, 111 CPU, 112 communication I/F section, 113 ROM, 114 RAM, 115 HDD, 116 facsimile section, 118 external storage device, 120 automatic document feeder, 130 document reading section, 140 image forming section, 150 paper feed section, 160 operation panel, 161 display section, 163 operation section, 165 touch panel, 167 hard key section, 51 operation user identification section, 53 document management section, 55 metadata management section, 57 access history storage section, 59 judgment section, 61 analysis section, 63 search section, 65 search result notification section, 71 document access section, 73 document version management section, 75 document deletion section, 81 association section, 83 cancellation section, 85 metadata update section, 91 change detection section Division, 93 Change Notification Division.

Claims (12)

an analysis means for analyzing the structure of document data and generating metadata indicating characteristics of constituent elements included in the document data;
Associating means for associating the metadata generated by the analysis means with respect to the document data at the time when the access ends, with the user accessing the document data, in response to the document data being accessed by the user; and,
A document retrieval device comprising: a retrieval unit that performs a retrieval using the metadata associated with an instructing user who has instructed a search among the plurality of metadata respectively associated with a plurality of users by the association unit. 2. The document search device according to claim 1, wherein said analysis means generates said metadata for a changed version in response to said document data being changed. 3. The document search device according to claim 1, further comprising document management means for executing display processing for displaying the document data or change processing for changing the document data by accessing the document data. The document data extracted by the search by the search means using version control information indicating a history of changes made by the user accessing the document data has been changed since the last time the document data was accessed by the designated user. change detection means for detecting that the
4. The document retrieval device according to claim 3, further comprising change notification means for notifying change information regarding the changed portion when the change detection means detects that the document data has been changed. 5. The document search device according to claim 3, wherein the document management means does not change the document data while the document data is being displayed when executing the display process. If the metadata exists for the same version of the document data at the time when the user accessing the document data ends, the analysis means does not analyze the document data. 6. The document retrieval device according to claim 1, further comprising determining means for causing the associating means to associate the metadata for the same version as the document data with the designated user. When the document data is changed due to access to the document data by the user accessing the document data, the metadata previously generated by the analysis means and the The document search device according to any one of claims 1 to 6, further comprising a dissolution means for dissolving the association with the user who has accessed the document data. When the document data is changed, a document version management means for storing the document data in respective versions before and after the change;
The method further comprises document erasing means for erasing a version of the document data corresponding to the metadata when the metadata whose association with the user has been canceled by the erasing means is not associated with any other user. Further, the document search device according to claim 7. 9. The document search device according to claim 1, wherein the analysis means updates the metadata for the document data at a predetermined timing regardless of changes in the document data. A document retrieval device according to any one of claims 1 to 9,
An image processing apparatus comprising: a document reading unit that reads a document and outputs image data representing an image of the document. an analysis step of analyzing the structure of document data and generating metadata indicating characteristics of constituent elements included in the document data;
In response to the document data being accessed by a user, an association step of associating the metadata generated in the analysis step with the user accessing the document data at the time when the access ends; and,
A document that causes a document search device to perform a search step of searching using the metadata associated with an instructing user who has instructed a search among the plurality of metadata respectively associated with a plurality of users in the association step. retrieval method. an analysis step of analyzing the structure of document data and generating metadata indicating characteristics of constituent elements included in the document data;
In response to the document data being accessed by a user, an association step of associating the metadata generated in the analysis step with respect to the document data at the time when the access ends with the user accessing the document data. and,
A document search program that causes a computer to perform a search step of searching using the metadata associated with the instruction user who instructed the search among the plurality of metadata respectively associated with a plurality of users in the association step. .

Images