JP2007334412A - Retrieval program and retrieving device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a retrieval program and a retrieving device capable of accurately retrieving files by a simple operation by specifying the information between operation histories as requirement for file retrieval. <P>SOLUTION: The history information on the operation of files performed by a data operation processing part 103 as operation histories is administrated by a database 108 through an operation history administration part 104. Based on the requirements for retrieval as the time intervals from the operation histories recorded according to the order of operations and the other operations among the requirements for retrieval input by a retrieval requirement input part 101, the operation history administration part 104 compares the date and time of operation with the present date and time. Then, the operation history administration part retrieves the operation history recorded in the database 108, and acquires the file of the operation history from a HDD 109. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a search program and a search device for searching for a file based on an operation history with respect to a file operation, and more particularly to a search program and a search device that can easily perform a search using information between the operation histories.

  When referring to a file such as an electronic document or image data managed by a conventional file management system, a predetermined search condition is input, and a file corresponding to the search condition is displayed in a list to search for a desired file. There is a way to do it. Normally, attribute information given to a managed file can be specified as a search condition.

  Furthermore, as another method for searching for a managed file, there is a method using operation history information indicating the operation content of a past file. This operation history information is information indicating what kind of processing has been performed, such as new registration of a file or update processing of a managed file, and the following search is performed using this operation history information. Can do.

1. 1. Search for a file based on the presence / absence of an operation content indicated by an operation history performed in the past (whether or not it has been executed) A certain operation history information is managed collectively, and a file is searched by judging whether it is similar to the group. When a file search is performed using the operation history information using these methods, the search conditions are detailed. Conditions cannot be specified, for example, only at the level of a file that has been “updated” as an operation content or a file that has been operated by a system.

  Patent Document 1 is a conventional technique that manages this operation history information, determines the state of data to be displayed as a list from the managed operation history information, and displays the list using icons indicating the determined state. Is disclosed.

  In this patent document 1, the state of data can be identified at a glance without giving the user a different feeling of use by expressing the state of data with the shape of an icon.

  Further, Patent Document 2 discloses a conventional technique that enables history information to be traced and managed efficiently by storing history information at a timing according to a user instruction and storing operation history and data history as synchronized data. Is disclosed.

  In this patent document 2, operation history information and data history information as document information are independently stored and managed, and history information is traced by enabling each history data to be mutually searched by a history search unit. It is possible to execute accurately and easily.

In addition, files managed as a file management system can be searched by analyzing the operation log by a system administrator, etc., but if all the operation history is extracted and collected for each target file, is it applicable to the file to be searched? Is required for each file, which not only consumes a large amount of work but also a large amount of man-hours.
JP 2000-76109 A JP 2001-265760 A

  The prior art disclosed in Patent Document 1 is configured to determine the state of data to be displayed from managed operation history information, and the operation history information includes general operation history such as update and new registration. In addition to the current status such as open status and locked status, it has been printed in the past, has been accessed within a specified period, and has not been accessed after updating However, since all search conditions are operation history information specified by the presence or absence of update, files cannot be searched using more detailed operation history as search conditions. There is.

  In addition, in the prior art disclosed in Patent Document 2, in addition to history information such as new creation and update of a file, a history such as a new document, an updated document, a revised version, etc., awaiting approval In addition to storing a data history that records document information such as document status (or process) during creation, rejection, etc., and maintaining and managing operation history and data history as correlated information, Although status grasping and operation trace processing when a problem occurs can be efficiently executed, a method of searching based on a managed data history or operation history is not shown.

  Therefore, an object of the present invention is to provide a search program and a search apparatus that can perform an accurate file search with a simple operation by designating information related to operation history as a file search condition.

  In order to achieve the above object, the first aspect of the present invention provides a first step of managing electronic data as an operation target in association with the operation content, operation target type and operation target of the operation on the electronic data, And a second step of searching for the electronic data using at least the search conditions that are the operation contents of the electronic data managed in the first step, the presence / absence of the operation, and the operation order thereof.

  The invention of claim 2 is characterized in that, in the invention of claim 1, the search condition further includes the operation object type and the operation object.

  The invention according to claim 3 is the invention according to claim 1 or 2, wherein the search condition further includes an interval from a previous corresponding operation.

  According to a fourth aspect of the present invention, there is provided a management means for managing electronic data as an operation target in association with the operation content, operation target type and operation target of the operation on the electronic data, and the management means managing the electronic data Search means for searching the electronic data using the operation content of the operation on the electronic data, the presence or absence of the operation, and the operation order as at least a search condition.

  According to the present invention, an operation history for a file is designated as a search condition for searching for a desired file from managed files. In particular, in the operation history, information between individual operation histories, for example, continuous operation contents Since it is configured such that information formed within the specified period can be specified as a search condition, there is an effect that an accurate file can be searched more easily.

  Hereinafter, an embodiment of a search program and a search apparatus according to the present invention will be described in detail with reference to the accompanying drawings.

  FIG. 1 is a system configuration diagram of a file management system configured by applying a search program and a search apparatus according to the present invention.

  In FIG. 1, this file management system is a system for managing an electronic document file (hereinafter referred to as “file”) created using a predetermined application, and an operation of a user operation performed on the managed file. Information is managed as a history ("operation history"), and a file search is performed on the condition of the managed operation history. In particular, the file search is performed by specifying the order in which the operation history is recorded (also referred to as “operation order”) and the time interval between the recorded operation histories as search conditions.

  User operations for files include registration processing for newly registering files, update processing for updating registered file contents (hereinafter referred to as “content”) and attribute information, change processing for changing the file management destination, There are a migration process, a list creation process for creating a list of managed files, and the like, and these user operations are managed as an operation history together with operation information such as a user (operator) and operation date and time.

  For example, when update processing of attribute information given to a file is performed after file registration processing, file registration and attribute information update are recorded in this order as an operation history. That is, the operation order is “1” for the registration process and “2” for the update process.

  When the operation order is designated as the file search condition, the file operated in the operation order is searched.

  In the present invention, a “recording process” for recording an operation history when a user operation is performed, and a “file search process” for searching for a file by specifying the operation history recorded by the recording process as a search condition. Is called.

  As an operation source for performing user operations and a specification source for specifying search conditions, for example, there is a client computer (not shown). In this case, the client computer is connected to the file management system via a communication line, Mutual communication is possible.

  The file management system shown in FIG. 1 includes a search condition input unit 101, a search processing unit 102, a data operation processing unit 103, an operation history management unit 104, a data management unit 105, a content management unit 106, an attribute management unit 107, and a database 108. The HDD 109 and the display unit 110 are configured to perform an operation history “recording process” by operating a file and a “file search process” using the operation history as a search condition.

  First, the “recording process” of the operation history will be described.

  When an operator issues an operation instruction such as a new file registration operation or an update operation using a client computer or the like, the data operation processing unit 103 performs file operation processing based on the operation instruction, and based on the operation instruction. The operation history management unit 104 and the data management unit 105 perform processing.

  The processing performed by the data operation processing unit 103 is processing for generating an object ID for identifying a file for which an operation instruction has been performed (processing for numbering an object ID), and is generated (numbered). An operation instruction is given to the operation history management unit 104 and the data management unit 105 together with the object ID.

  In response to the instruction from the data operation processing unit 103, the operation history management unit 104 analyzes the operation information included in the operation instruction from the data operation processing unit 103, the operator who operated the file, the operation content, the operation date and time, the operation type Each piece of information to be operated is extracted and recorded as operation history (108-A) on the database 108 with operation identification information ("operation ID") and the generated (numbered) object ID. An example of this operation history (108-A) is shown in FIGS.

  The operation type recorded as the operation history is information indicating which part of the operated file has been operated. When a content such as a document or image of the file is operated, “content” is displayed as the operation type. In addition, when the attribute information given to the file is operated, “attribute” is indicated as the operation type.

  Similarly, the operation target recorded as the operation history indicates a more specific operation location of the operation part indicated by the operation type. When the file name of “attribute” is operated, “name” is set as the operation target. In addition, when the main part of “content” is operated, “main” is indicated as the operation target.

  When such information is recorded in the database 108 as the operation history (108-A), in parallel or in advance, the data management unit 105 that has received an instruction from the data operation processing unit 103 performs an operation from the data operation processing unit 103. A processing instruction is given to the attribute management unit 106 and the content management unit 107 together with the object ID included in the instruction.

「「 」「 「
The attribute management unit 107 extracts the attribute information given to the file for the content at the time of new registration of the content, associates the extracted attribute information with the object ID of the file to which the attribute information was given, As attribute data (108-B).

  When updating the attribute information, the corresponding attribute information is acquired from the attribute data (108-B) on the database 108 based on the designated object ID, and the update process is performed.

  In addition, the content management unit 107 registers the file as content in the HDD 109 serving as a management area by an operation instruction for newly registering a file, acquires the content registered in the HDD 109 by an operation instruction for file update, and operates the instruction Update process based on. The content registered in the HDD 109 is entity data indicating the file itself.

  The database 108 manages content information (not shown) in addition to the operation history (108-A) and attribute data (108-B), and this content information is managed as attribute data (108-B). This is information in which the object ID assigned to the attribute information is associated with the address information on the HDD 109 where the content of the attribute information is stored.

  That is, the attribute information managed as attribute data (108-B) on the database 108 and the content managed by the HDD 109 are in a state of being associated with each other by the content information.

  By such processing, the operation history can be recorded on the database by operations such as new registration and update of the file, and the attribute information and content of the file that is the operation target of the operation history are managed by the database 108 and the HDD 109. be able to.

""""""
FIG. 2 is a flowchart showing a flow of recording processing for recording an operation history performed by the operation history management unit 104 at this time.

  Next, a “file search process” for specifying an operation history recorded by the above-described recording process as a search condition and searching for a file that satisfies the condition will be described.

  Information managed as an operation history on the database 108 as a search condition for searching for a file, for example, an operator who has operated a file, operation details, operation date / time, operation order, and other operations are recorded. A search condition such as a time interval with the operation history is input from the search condition input unit 101, and the search condition is transmitted to the search processing unit 102.

  In the search condition input unit 101, a search condition can be input by a client computer (not shown). An example of the search condition input by the search condition input unit 101 is shown in FIG. The search condition input unit 101 can also input attribute information given to the file as a search condition.

  The search processing unit 102 that has received the search condition input by the search condition input unit 101 checks the consistency of the search condition, checks whether there is a contradiction in the search condition, and performs a search due to a contradiction in the search condition. If this is not possible, the search process is not performed and the process is interrupted. As a result, the search process can be prevented from being performed permanently on the system, and a more stable search can be performed.

  Of course, when the search process is interrupted, the searcher (user) may be notified by displaying the fact.

  When the consistency check is performed by the search processing unit 102, a search instruction based on the search condition is issued to the operation history management unit 104, and the operation history management unit 104 associates the operation history that matches the search condition. The file identification information (“object ID”) is acquired from the operation history (108 -A) of the database 108. Further, the operation history management unit 104 transfers the acquired object ID to the search processing unit 102.

  On the other hand, if it cannot be acquired because there is no object ID that matches the search condition, that fact is displayed on the display unit 110 and the process is terminated.

  When the search order at this time specifies the operation order and the time interval with the operation history recorded by other operations, the operation date and time information managed in the operation history (108-A) of the database 108 is included. Based on this, the object ID of the file that meets the search condition is searched.

  The search condition for the operation order is a search condition for judging whether it is newer or older than the other search conditions from the operation date and time, and with the operation history recorded by performing other operations. The time interval search condition is a condition for calculating an elapsed time by comparing the operation date and time of another operation with the current date and searching whether the elapsed time is within a specified time interval.

  Other operations usually indicate the previous operation performed immediately before, but of course, it is also possible to indicate the operation by specifying the content of the operation performed. In this case, the specified operation Compares the time elapsed since the operation was performed with the specified time interval.

  Further, when the object ID can be acquired because there is a file that satisfies the search condition, the object is transferred to the data management unit 105 based on the object ID transferred from the operation history management unit 104 by the search processing unit 102. Request acquisition of attribute information for the ID. Upon receiving the attribute information acquisition request, the data management unit 105 transfers the attribute information acquisition request for the object ID to the attribute management unit 107, and the attribute management unit 107 manages it as attribute data (108-B) of the database 108. Attribute information for the object ID is acquired from the attribute information.

  When the attribute information given to the file by the search condition input unit 101 is used as a search condition, the search condition is set by performing a logical product operation with the attribute information indicated by the object ID acquired by the search processing unit 102. The attribute information of the applicable object ID is acquired.

  When the search processing unit 102 displays the acquired attribute information on the display unit 110 and designates a file to be operated by the user from the attribute information of the displayed file, the search processing unit sends an acquisition request for the file indicated by the object ID for the specified attribute information. This is performed from 102 to the data management unit 105. The data management unit 105 makes a request to acquire the file indicated by the object ID to the content management unit 107.

"""
The content management unit 107 refers to content information (not shown) managed by the database 108 and acquires content from the HDD 109 based on the content address information for the object ID specified by the data management unit 105 to obtain data. Transfer to the management unit 105. As a result, an operation is received from the data operation processing unit 103.

""""
The data operation processing unit 103 can issue an instruction to delete the recorded operation history. In this case, the operation history management unit 104 deletes the designated operation history. As a deletion unit at this time, it can be deleted for each object ID and each stored area, and can also be deleted by designating the date and time.

  If the file for the object ID does not exist, that effect is displayed on the display unit 110 and the process ends.

  As a result, the file search can be performed using the information on the operation order and the time interval with the operation history recorded by performing another operation as a search condition.

  FIG. 6 is a flowchart showing the flow of search processing performed by the search processing unit 102 and the operation history management unit 104 at this time.

  With such a configuration, it is possible to perform a file search in which the time interval with the operation history recorded by other operations and the operation order are designated as search conditions, and a desired file can be easily searched.

  FIG. 2 is an operation history recording flowchart showing a flow of recording an operation history in the data operation of the present invention.

  In FIG. 2, when a data operation request (operation history recording instruction) for recording an operation performed by the user as an operation history is received, the process is started, and recording information to be recorded as an operation history is extracted from the operation information of the data operation request. (201). For example, as the record information, an operator who is the source of the data operation request that performed the data operation, the operation content of the data that is the type of the data operation request, the operation date and time when the data operation was performed, and the like are extracted.

  After extracting the record information to be recorded as the operation history from the data operation request, it is searched whether the operated file is recorded (managed) on the database (202). As a result of the search, it is determined whether or not the file is recorded (203), and if the file is not recorded (NO in 203), for example, if the file is being recorded, it waits until the recording process is completed. A process is performed to determine whether the recording is performed again. Further, when a file is not recorded due to a failure or the like during recording, the operation history recording process by the data operation request may be interrupted.

  When the file from which the record information is extracted is recorded (YES in 203), the operation type indicating which part of the operated file has been operated and the operation part indicated by the operation type are more specific. An operation target indicating a specific operation location is extracted and set as operation target information (204).

  Through the above processing, the extracted record information and operation target information are recorded in the database as operation history information (205).

  As a result, file operation information can be recorded as an operation history, and a file can be searched using information between operation histories.

  FIG. 3 is a configuration diagram showing a main table that manages the operation history of the present invention.

  The operation history table of FIG. 3 is a main table for managing the operation information extracted by the process of extracting the record information shown in FIG. 2, and the operator, operation content, and operation date and time extracted by the extraction process are respectively The operation history table is managed corresponding to the [operator] column 303, the [operation content] column 305, and the [operation date / time] column 304.

  When recording these pieces of recording information, an operation ID, which is information for identifying an operation history, and an object ID for identifying a file corresponding to the operation history are given, and an [operation ID] column 301, [object ID] Each is managed in a column 302.

  For example, in the operation information in which the [operator] column 303 is “userA”, the [operation date / time] column 304 is “2005/01/01 01:01:01”, and the [operation content] column 305 is “registration”. Is given an operation ID “331”, and the object ID of the data to be operated is “0011”.

  This operation information is operation information indicating an operation history in which “userA” newly “registers” a file with the object ID “0011” at “01:01:01 on 01/01/2005”.

  Furthermore, the record indicated by the [operation ID] column 301 indicates the object ID “0011”, the operator “userA”, the operation date and time “2005/01/02 01:03:01”, and the operation content “update”. This operation information is information indicating an operation history that “userA” “updated” the file with the object ID “0011” to “01:03:01 on January 02, 2005”.

  That is, the records with operation IDs “331” and “332” indicate that the same user “userA” is history information operated on the same file with the object ID “0011”.

  The table in FIG. 4 shows what information (operation type, operation target) in the file indicated by the object ID corresponding to the operation ID is operated.

  FIG. 4 is a table for managing information extracted as the operation target information shown in FIG. 2, and includes an [operation ID] column 401, an [operation type] column 402, and an [operation target] 403. [Operation ID] column 401 is associated with [Operation ID] column 301 shown in FIG.

  The operation type indicated in the [operation type] column 402 is a type indicating which part of the file has been operated. For example, when an operation is performed on the file itself (entity data), “ “Content” is indicated, and “attribute” is indicated as the operation type when the attribute information given to the file is operated.

  The operation target indicated by the [operation target] column 403 indicates a more specific (detailed) operation location of the operation type indicated by the [operation type] column 402.

  In the [operation type] column 402 in which the [operation ID] column 401 shown in FIG. 4 is “331”, two types of attribute types “attribute” and “content” are specified. The attribute information indicated by “attribute” in the “operation type” column 402 includes operation objects such as an attribute ID, a user attribute A, and a user attribute B, and these are indicated in the “operation object” column 403.

  The attribute information indicated by “content” in the [operation type] column 402 is configured by operation targets such as main content (indicated as main) and sub-content (indicated as sub 1 and sub 2) as content types. Is displayed in the [operation object] column 403.

  The operation history shown in FIGS. 3 and 4 is an example of information recorded by executing the operation history recording flowchart of FIG.

  Next, a process for searching for a file that satisfies a condition from the recorded operation history will be described with reference to FIGS. 5 and 6.

  FIG. 5 is a diagram illustrating an example of specifying search conditions.

  FIG. 5 shows an example in which four conditions (condition 1) to (condition 4) are used as search conditions.

  Each condition ((condition 1) to (condition 4)) includes [operation order] 501, [operation presence / absence] 502, [operation content] 503, [operator] 504, [operation type] 505, [operation target] 506 and [Time interval with operation of other conditions] 507 can be designated as search condition items.

  (Condition 1) is [Operation order] 501 is “1”, [Operation execution status] 502 is “Yes”, [Operation content] 503 is “Register”, [Operator] 504 to [Operation of other conditions] [Time interval from] 507 is designated as “(blank)” in the search condition. This is the operation of “registration” in the “1” -th operation (hereinafter, “(first operation)”). The condition is to search for a file. At this time, [operator] 504 to [time interval with operation under other conditions] 507 (blank) indicates that these items are not included in the search condition.

  (Condition 2): [Operation order] 501 is “2”, [Operation execution status] 502 is “Yes”, [Operation content] 503 is “Update”, [Operator] 504 is “(blank)”, The “operation type” 505 is “attribute”, the “operation target” 506 is “name” and “user attribute A” are specified as search conditions. This is the “second” operation (hereinafter referred to as “(second The operation is to search for a file in which the operation “update” is performed on the operation target “name” and “user attribute A” of the operation type “attribute” in “operation”)).

  (Condition 3): [Operation order] 501 is “3”, [Operation execution status] 502 is “Yes”, [Operation content] 503 is “Update”, [Operator] 504 is “(blank)”, [Operation type] 505 is “attribute”, [operation object] 506 is “state”, and [time interval with operation of other conditions] 507 is “within 30 days”. , The operation “update” is performed on the operation target “attribute ID” of the operation type “attribute” in the “3” th operation (hereinafter, “(3-1 operation)”) (second operation) This is a condition for searching for a file that has been performed “within 30 days”.

  (Condition 4): [Operation order] 501 is “3”, “Operation execution status” 502 is “None”, [Operator] 504 is “(Blank)”, [Operation type] 505 is “Content”, [Operation target] 506 is “main”, and [time interval with other conditions operation] 507 is “within 30 days”, which is designated as a search condition. “(3-2 operation)”) is a condition for searching for a file that has not been operated within “within 30 days” for the operation object “main” of the operation type “content”.

  [Time interval with other condition operation] 507 of the search conditions shown in the above (Condition 3) and (Condition 4) is the time interval that has elapsed since the previous operation (second operation) was performed. By comparing the operation date and time in the operation history table shown in FIG. 3 with the current date and time, it is determined whether or not the time interval satisfies the condition.

  FIG. 6 shows the flow of search processing performed when such a condition is designated.

  FIG. 6 is a flowchart showing the flow of processing for performing a file search in the present invention.

  First, a matching operation ID is extracted based on the (3-1 operation) search condition shown in (Condition 3) of FIG. 5 (601). If the operation ID cannot be extracted (NO in 602), the process ends.

  In this (Condition 3), the operation “update” is performed on the operation target “attribute ID” of the operation type “attribute” in (3-1 operation), and “30” after performing the (second operation). Search for files made within "days". [Operation order] 501 and [Time interval with operation of other conditions] 507 at this time are related to the operation indicated by the next condition, and are applied when a search is performed under the next condition.

  Subsequently, a matching operation ID is extracted based on the (second operation) search condition indicated by (Condition 2) (603). Also in this case, if the operation ID cannot be extracted (NO in 604), the process is terminated.

  In (Condition 2), a search is performed for a file in which the operation “update” is performed on the operation target “name” of the operation type “attribute” and “user attribute A” in (second operation). Further, (Condition 3) (3-1 operation) is performed in consideration of [Operation order] 501 and [Time interval with operation of other conditions] 507 specified as search conditions in (Condition 3). This is performed in consideration of the condition that the operation has been performed before and the time interval between the (3-1 operation) is within 30 days.

  Subsequently, a matching operation ID is extracted based on the (first operation) search condition indicated by (Condition 1) (605). Also in this case, if the operation ID cannot be extracted (NO in 606), the process is terminated.

  In this (Condition 1), the file for which the operation of “registration” was performed in (first operation) is searched.

  Subsequently, a matching operation ID is extracted based on the (3-2 operation) search condition indicated by (Condition 4) (607). Also in this case, if the operation ID cannot be extracted (NO in 608), the process is terminated.

  In this (condition 4), “within 30 days” after performing the (second operation) of (condition 2) on the operation object “main” of the operation type “content” in (3-2 operation) The operation ID that has not been operated is extracted.

  If an operation ID that satisfies these (condition 1) to (condition 4) can be extracted (YES in 608), a list of object ID files corresponding to the operation ID is displayed. For example, file attribute information is displayed, content is displayed, and attribute information is displayed together with the content.

  As a result, a desired file is searched and file operation becomes possible.

  With the configuration and flowchart as described above, in the file search process in the file management system of the present invention, it is possible to perform a file search in which information between operation histories is designated as a search condition.

  This makes it possible to search for a desired file more easily and accurately.

  The present invention is not limited to the embodiments described above and shown in the drawings, and can be implemented with appropriate modifications within a range not changing the gist thereof.

  The present invention can be applied to a search program and a search device that search a predetermined file from managed files based on an operation history, and in particular, performs a file search more easily and accurately based on information between operation histories. Useful for.

1 is a system configuration diagram of a file management system configured by applying a search program and a search apparatus according to the present invention. The operation history recording flowchart which shows the flow which records the operation history in the data operation of this invention. The block diagram which shows the main table which managed the operation history of this invention. The table which manages the information extracted as operation target information shown in FIG. The figure which shows the example of designation | designated of search conditions. The flowchart which shows the flow of the process which searches the data in this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 Search condition input part 102 Search processing part 103 Data operation process part 104 Operation history management part 105 Data management part 106 Attribute management part 107 Content management part 108 Database 108-A Operation history information 108-B Attribute data 109 HDD
110 Display section

Claims (4)

A first step of managing electronic data as an operation target in association with the operation content of the operation on the electronic data, the operation target type, and the operation target in association with the operation date and time;
The computer executes a search process including: a second step of searching the electronic data using at least the search conditions that are the operation content of the electronic data managed in the first step, the presence / absence of the operation, and the operation order thereof. Search program to let you. The search condition is:
The search program according to claim 1, further comprising: the operation object type and the operation object. The search condition is:
The search program according to claim 1 or 2, further comprising: an interval from a previous corresponding operation. A management means for managing electronic data as an operation target in association with the operation content, operation target type and operation target of the operation on the electronic data;
A search device comprising: search means for searching for the electronic data using at least search conditions as operation details of the operation, presence / absence of the operation, and operation order of the electronic data managed by the management means.

Images