Data retrieval system and method

Abstract

To provide a technology that enables desired data to be appropriately found by using a tag even though content or a storage location of the data is changed.SOLUTION: A data search system includes: an agent server that includes a storage and stores data in the storage; and a host server that manages tag management information in which a tag as a term for searching the data and a storage as a storage location of the data are associated with the data, receives a query including a search designation tag, and acquires data associated with the search designation tag from the storage location of the data by referring to the tag management information and responds to the query. The host server continuously updates the tag management information according to content and the storage location of the data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a technique for accessing data stored in a computer system. [Background technology]

[0002] File systems and database systems are widely used as computer systems for storing data. Both file systems and database systems are accessed from a terminal to read and write data. In file systems and database systems, it is important to be able to accurately find the desired data. Reading data stored in a file or database and checking its contents can reliably tell whether it is the desired data, but this is not very efficient.

[0003] One technique for efficiently finding desired data is called ontology-based data access (see Non-Patent Document 1). Ontology-based data access is a technique in which an ontology containing a list of terms (hereinafter referred to as "tags") and a mapping between tags and data are set in advance, and data is accessed using the tags.

[0004] For example, if you define a tag called "disease name" in the ontology and set up a mapping that associates the tag "disease name" with data related to the term "disease name," you can find data related to "disease name" without having to read the data and check its contents. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] Xiao, Guohui, et al. “Virtual knowledge graphs: An overview of systems and use cases.” Data Intelligence 1.3(2019):201-223. Summary of the Invention [Problem to be solved by the invention]

[0006] However, with the ontology-based data access described in Non-Patent Document 1, if the storage location of the data changes, it becomes impossible to correctly find the desired data from the tag. Also, if the content of the data is updated, an inconsistency occurs between the mapping tag and the actual data, making it impossible to correctly find the desired data using the tag.

[0007] One object of the present disclosure is to provide a technology that enables desired data to be appropriately found using tags even if the content or storage location of the data changes. [Means for solving the problem]

[0008] A data search system according to one aspect of the present disclosure comprises an agent server equipped with a storage and storing data in the storage, and a host server that manages tag management information that associates, for the data, tags that are search terms for the data with the storage location of the data, and that receives queries including search-specified tags and responds by referencing the tag management information to retrieve data associated with the search-specified tags from the storage location of the data, and the host server continuously updates the tag management information according to the content and storage location of the data. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, tags associated with data are updated according to the content and storage location of the data, so that desired data can be properly found using tags even if the content or storage location of the data changes. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram of a data retrieval system. [Figure 2] FIG. 10 is a diagram showing an example of a file tag management table 109. [Figure 3] FIG. 2 is a diagram showing an example of a column tag management table 110. [Figure 4] FIG. 2 is a diagram illustrating an example of a storage management table 111. [Figure 5] FIG. 2 is a diagram illustrating an example of a cache management table 112. [Figure 6] FIG. 10 is a diagram showing an example of a tag sample management table 113. [Figure 7] FIG. 10 is a diagram showing an example of a data storage location management table 106. [Figure 8] FIG. 2 is a diagram illustrating an example of data stored in a storage 120. [Figure 9] 10 is a diagram illustrating an example of data stored in a tag data cache 121. FIG. [Figure 10] 10 is a flowchart of a data tag management process executed by a data tag management function unit 107. [Figure 11] 10 is a flowchart of a data tagging process executed by a data tagging function unit 117. [Figure 12] 10 is a flowchart of a tag generation process executed by a data tagging function unit 117. [Figure 13] FIG. 10 is a diagram showing an example of a query received by the tag-based data search function unit 104. [Figure 14] 10 is a flowchart of a tag-based search process executed by a tag-based data search function unit 104. [Figure 15] 10 is a flowchart of a movement determination process executed by a data tagging function unit 117. [Figure 16] 10 is a flowchart of a tag sample registration process executed by a tag sample management function unit 108. DETAILED DESCRIPTION OF THE INVENTION

[0011] DETAILED DESCRIPTION OF THE INVENTION The following describes the embodiments of the invention.

[0012] FIG. 1 is a block diagram of a data retrieval system.

[0013] The data search system includes a host server 101 , an agent server 114 , a storage 120 , and a tag data cache 121 .

[0014] The data search system is a system that performs tag-based data searches. Tags are associated with data to be searched. The data to be searched is, for example, a file. Storage 120 is a storage device that stores data to be searched. Agent server 114 is a server device that retrieves data stored in storage 120 in response to instructions from host server 101. Host server 101 is a server device that accepts queries containing tags from users, instructs agent server 114 to obtain data related to the tags, and returns the data to the user. Tag data cache 121 is a memory that stores search results so that they can be used for subsequent searches.

[0015] The host server 101 has a CPU 102 and memory 103. The memory stores software programs that realize various functions and tables used for the various functions. The tag-based data search function unit 104, data storage location management function unit 105, data tag management function unit 107, and tag sample management function unit 108 are function units realized by the software programs. Tables used for the various functions include a data storage location management table 106, a file tag management table 109, a column tag management table 110, a storage management table 111, a cache management table 1123, and a tag sample management table 113. The CPU 102 is a processor that executes the processing of the software program using these tables. The processing of each unit and each table will be described in detail below.

[0016] Agent server 114 has CPU 115 and memory 116. Memory 116 stores software programs that realize various functions. Data tagging function unit 117, data extraction function unit 118, and storage location check function unit 119 are function units realized by software programs. CPU 115 is a processor that executes the processing of these software programs. The processing of each unit will be described in detail below.

[0017] In this embodiment, a file has columns, and it is possible to associate tags with the entire file and with each column. A tag associated with a file is a file tag. A tag associated with a column is a column tag.

[0018] 2 is a diagram showing an example of the file tag management table 109. The file tag management table 109 records the file name of each file to be searched, the file tag associated with the file, and information identifying the storage in which the file is stored, in association with each other.

[0019] 3 is a diagram showing an example of the column tag management table 110. The column tag management table 110 records the file name of each file, the column number of the column included in the file, the column tag associated with the column, and information identifying the storage in which the file is stored, in association with each other.

[0020] 4 is a diagram showing an example of the storage management table 111. The storage management table 111 records information for identifying each storage, the agent name of the agent in which the storage entity is located, the IP address for accessing the storage, the ID and password for accessing the storage, and the port number for accessing the storage, in association with each other.

[0021] 5 is a diagram showing an example of the cache management table 112. The cache management table 112 records information for managing the contents stored in the tag data cache 121 in which search results are stored. The cache management table 112 records the file name of the target file, the column number of the column included in the file, the column tag associated with the column, and storage information indicating that the file is stored in the cache, in correspondence with each other.

[0022] 6 is a diagram showing an example of the tag sample management table 113. The tag sample management table 113 is a table that associates tags with the data (sample data) to which the tags are assigned. The tag sample management table 113 includes a tag sample management table 113A related to column tags and a tag sample management table 113B related to file tags.

[0023] The tag sample management table 113A records the correspondence between a column tag name 501, which is the name of a column tag, and sample data 502, which indicates data to which the column tag is assigned.

[0024] The tag sample management table 113B stores a correspondence between a file tag name 601, which is the name of a file tag, and sample data 602, which indicates the data to which the file tag is assigned. The sample data 602 contains a column name. If a column included in a file has a column name included in the sample data 602, the file is assigned a file tag with the file tag name 601.

[0025] 7 is a diagram showing an example of the data storage location management table 106. The data storage location management table 106 is a table that manages the storage location of data. The storage location (storage) of data (files) is not necessarily fixed, and files may move from one storage to another.

[0026] The storage in which the file was originally stored when the file tag was assigned is recorded in the file tag management table 109, but if the file storage location is subsequently moved to another storage, information on the new location is recorded in the data storage location management table 106.

[0027] The data storage location management table 106 records the file name of the moved file, information identifying the storage to which the file is moved, the last update date and time indicating the date and time when the file was last moved and the storage location was moved, and the hash value of the file.

[0028] When a file is moved, the contents of the file may or may not be rewritten. If the contents of the file are rewritten, it may be necessary to update the tag associated with the file. Therefore, it is necessary to check whether the contents of the file have been rewritten. Hash values ​​are used to check whether the contents have been rewritten when the file is moved.

[0029] FIG. 8 is a diagram showing an example of data stored in storage 120. Data 801 is in CSV (Comma Separated Value) format. The first line of data 801 is the column name, and the second line and onwards are the data values. The Patient_ID column is identification information that identifies each patient. The Disease column is the name of the disease. The Symptom column is the symptom. The Emergency column is the degree of urgency. YES indicates high urgency, and NO indicates low urgency.

[0030] 9 is a diagram showing an example of data stored in the tag data cache 121. The data stored in the tag data cache 121 is a search result corresponding to a search query. The data 901 is in CSV format. The first line of the data 901 contains column names, and the second and subsequent lines contain data values. In the example of FIG. 9, the data 901 includes a Patient_ID column indicating the patient's identification information and a Disease column indicating the disease name.

[0031] 10 is a flowchart of the data tag management process executed by the data tag management function unit 107. The data tag management process is a process for updating tags attached to data. The data tag management process is executed periodically, for example, once a day.

[0032] In step S901, the data tag management function unit 107 extracts tagging information for each agent server 114 from the data storage location management table 106.

[0033] In step S902, the data tag management function unit 107 transmits to each agent server 114 information on the file name, storage, last update date and time, and hash value extracted from the data storage location management table 106.

[0034] In step S903, the data tag management function unit 107 transmits the information stored in the tag sample management table 113 to each agent server 114.

[0035] In step S904, the data tag management function unit 107 instructs the data tagging function unit 117 of each agent server 114 to tag the data (data tagging). The process executed by the data tagging function unit 117 that has received the data tagging instruction will be described later.

[0036] In step S905, the data tag management function unit 107 receives the tagging result from the data tagging function unit 117.

[0037] In step S906, the data tag management function unit 107 updates the file tag management table 109, the column tag management table 110, the storage management table 111, and the data storage location management table 106 based on the tagging results received from the data tagging function unit 117.

[0038] 11 is a flowchart of the data tagging process executed by the data tagging function unit 117. The data tagging process is a process of attaching tags to data.

[0039] In step S1001, the data tagging function unit 117 receives a data tagging instruction from the data tag management function unit 107.

[0040] In step S 1002 , the data tagging function unit 117 extracts one piece of data stored in the storage 120 .

[0041] In step S1003, the data tagging function unit 117 determines whether the extracted data has already been tagged by the agent server 114. If the data has already been tagged by the agent server 114, the data tagging function unit 117 proceeds to step S1011.

[0042] If the data has not been tagged by this agent server 114, in step S1004, the data tagging function unit 117 determines whether the data has been moved from another agent. Movement here refers to the data itself being unchanged, with only a change in storage location. Whether the data has been moved from another agent can be determined by whether the hash value of the data matches the hash value extracted from the data storage location management table 106. The process of determining whether the data has been moved from another agent (movement determination process) will be described later.

[0043] If the data in question has been moved from another agent, then in step S1005, data tagging function unit 117 notifies data storage location management function unit 105 that the data has been moved. Upon receiving the notification that the data has been moved, data storage location management function unit 105 updates data storage location management table 106 in accordance with the notification. After step S1005, data tagging function unit 117 proceeds to step S1011.

[0044] If the corresponding data is not data that has been moved from another agent, then in step S1006, data tagging function unit 117 determines whether the corresponding data is new data. If the corresponding data is new data, then in step S1007, data tagging function unit 117 notifies data storage location management function unit 105 that the corresponding data is new data. Upon receiving the notification that the corresponding data is new data, data storage location management function unit 105 adds information to data storage location management table 106 in accordance with the notification.

[0045] If the data is not new data, or after step S1007, the data tagging function unit 117 generates a file tag and a column tag for the data in step S1008. The process of generating the file tag and column tag (tag generation process) will be described later.

[0046] Furthermore, in step S1009, the data tagging function unit 117 acquires the last update date and time and the hash value for the relevant data.

[0047] In step S1010, the data tagging function unit 117 notifies the data tag management function unit 107 of the file tag and column tag generated in step S1008, and notifies the data storage location management function unit 105 of the last update date and time and hash value acquired in step S1009.

[0048] Upon receiving the notification of the file tag and column tag, the data tag management function unit 107 updates the file tag management table 109 and the column tag management table 110 in accordance with the notification. Upon receiving the notification of the last update date and time and the hash value, the data storage location management function unit 105 updates the data storage location management table 106 in accordance with the notification.

[0049] In step S1011, the data tagging function unit 117 determines whether or not all data stored in the storage 120 has been extracted. If unextracted data remains, the data tagging function unit 117 returns to step S1002. If all data has been extracted, the data tagging function unit 117 completes the series of processes.

[0050] Fig. 12 is a flowchart of the tag generation process executed by the data tagging function unit 117. The tag generation process corresponds to step S1008 described above, and Fig. 12 shows the details of this process.

[0051] In step S1101, the data tagging function unit 117 reads out the relevant data 801. In step S1102, the first line of the data 801 is regarded as the column name, and the second line and onwards are regarded as the data body. In step S1103, the data tagging function unit 117 calculates the similarity between each column of the data body and the sample data 502 in each row of the tag sample management table 113A. For example, the number of times the same word is included can be used as the similarity.

[0052] In step S1104, the data tagging function unit 117 determines whether the similarity calculated in the processing of step S1103 is equal to or greater than a predetermined threshold. If the similarity is equal to or greater than the threshold, in step S1105, the data tagging function unit 117 sets the column tag name 501 corresponding to the sample data 502 whose similarity in the tag sample management table 113A is equal to or greater than the threshold as the column tag name of the corresponding column of the data 801. If the similarity is smaller than the threshold, in step S1106, the data tagging function unit 117 sets the column name of each column in the first row of the data 801 as the column tag name of each column.

[0053] In step S1107, the data tagging function unit 117 calculates the similarity between the tag name of each column in the data body of the data 801 and the sample data 602 of each row in the tag sample management table 113B. For example, the number of times the same word is included can be used as the similarity.

[0054] In step S1108, the data tagging function unit 117 determines whether the similarity calculated in the processing of step S1107 is equal to or greater than a predetermined threshold. If the similarity is equal to or greater than the threshold, in step S1109, the data tagging function unit 117 sets the file tag name 601 corresponding to the sample data 602 in the tag sample management table 113B whose similarity is equal to or greater than the threshold as the file tag name of the data 801. If the similarity is smaller than the threshold, in step S1110, the data tagging function unit 117 sets the file name of the data 801 as the file tag name of the data 801.

[0055] 13 is a diagram showing an example of a query received by the tag-based data search function unit 104. Query 1201 is a query for retrieving data related to the "diagnosis" of a patient whose "disease name" is "pneumonia." USE_CACHE specifies whether or not to use cache data for the search. STORE_CACHE specifies whether or not to store the search results in the cache. Query 1201 specifies that the data stored in tag data cache 121 is not used for the search using this query, but that the results of the search using this query are to be stored in tag data cache 121.

[0056] FIG. 14 is a flowchart of the tag-based search process executed by the tag-based data search function unit 104.

[0057] When the tag-based data search function unit 104 receives a query in step S1301, it determines in step S1302 whether or not USE_CACHE=YES is specified in the query. If USE_CACHE=YES is specified, in step S1309, the tag-based data search function unit 104 inquires of the data tag management function unit 107 whether or not data matching the query is stored in the tag data cache 121. Then, in step S1310, the tag-based data search function unit 104 determines whether or not data matching the query is stored in the tag data cache 121.

[0058] If data matching the query is found in the tag data cache 121, then in step S1311 the tag-based data search function unit 104 responds to the query with data from the tag data cache 121. If data matching the query is not found in the tag data cache 121, then in step S1303 the tag-based data search function unit 104 queries the data tag management function unit 107 and obtains a list of data having the file tag and column tag specified in the query.

[0059] Then, in step S1304, the tag-based data search function unit 104 requests the data extraction function unit 118 of the agent server 114 that includes the storage 120 in which the data included in the obtained list is stored to extract that data.

[0060] In the agent server 114 , the data extraction function unit 118 extracts the requested data from the storage 120 and transmits it to the tag-based data search function unit 104 of the host server 101 .

[0061] The tag-based data search function unit 104 receives the data included in the list from the agent server 114, and in step S1305 integrates the data received from the agent server 114. Integration means, for example, connecting the data included in the list to form one piece of data. This integrated data becomes the search result.

[0062] In step S1306, the tag-based data search function unit 104 determines whether or not STORE_CACHE=YES is specified in the query. If STORE_CACHE=YES is specified in the query, in step S1307, the tag-based data search function unit 104 registers the data integrated in the processing of step S1305 in the tag data cache 121.

[0063] If the query does not specify STORE_CACHE=YES, or if the integrated data is registered in the tag data cache 121, the tag-based data search function unit 104 responds to the query in step S1308 using the data integrated in the processing of step S1305.

[0064] 15 is a flowchart of the movement determination process executed by the data tagging function unit 117. The movement determination process corresponds to step S1004 described above, and FIG.

[0065] In step S1401, the data tagging function unit 117 inquires of the data storage location management function unit 105 whether or not the relevant data is stored in the data storage location management table 106. In step S1402, the data tagging function unit 117 determines whether or not the relevant data is stored in the data storage location management table 106.

[0066] If the data is stored in the data storage location management table 106, in step S1403 the data tagging function unit 117 inquires of the data storage location management function unit 105 whether the storage in which the data is stored has changed. In step S1404, the data tagging function unit 117 determines whether the storage in which the data is stored has changed.

[0067] If the storage in which the data is stored has been changed, then in step S1405 the data tagging function unit 117 determines whether the data has the same hash value as before the change.

[0068] If it is determined in step S1402 that the data in question is not stored in the data storage location management table 106, if it is determined in step S1404 that the storage in which the data in question is stored has not been changed, or if it is determined in step S1405 that the data in question does not have the same hash value as before the change, then in step S1407 the data tagging function unit 117 determines that the data in question is not data that has simply been moved from another agent server 114.

[0069] If it is determined in step S1405 that the data in question has the same hash value as before the change, in step S1406, the data tagging function unit 117 identifies the data in question as data that has simply been moved from another agent server 114.

[0070] 16 is a flowchart of the tag sample registration process executed by the tag sample management function unit 108. The tag sample registration process is a process for registering a tag sample in the tag sample management table 113. The tag sample registration process is a process common to both column tags and file tags.

[0071] In step S1501, the tag sample management function unit 108 receives the tag name and sample data of the tag sample from the user. In step S1502, the tag sample management function unit 108 registers the received tag name and sample data in the tag sample management table 113.

[0072] The above-described embodiments are merely examples for explaining the present invention, and are not intended to limit the scope of the present invention to these embodiments. Those skilled in the art can implement the present invention in various other forms without departing from the scope of the present invention.

[0073] This embodiment also includes the following features: However, the features included in this embodiment are not limited to those listed below.

[0074] (Item 1) an agent server having a storage and storing data in the storage; a host server that manages tag management information for the data, which associates tags, which are search terms for the data, with storage, which is a storage location of the data, and receives a query including a search specified tag, and responds by retrieving data associated with the search specified tag from the storage location of the data by referring to the tag management information; The host server continuously updates the tag management information according to the content and storage location of the data. Data retrieval system. This allows the tag associated with the data to be updated according to the content and storage location of the data, so that desired data can be appropriately found using the tag even if the content or storage location of the data changes.

[0075] (Item 2) The host server sends a request to the agent server to tag data stored in the storage; the agent server receives the request, determines a tag to be associated with the data stored in the storage, and sends a notification to the host server; The host server receives the notification and updates the tag management information. Item 1. A data retrieval system according to item 1. According to this, each agent server tags its own data, so that the processing load of tagging can be distributed.

[0076] (Item 3) The agent server If the data stored in the storage has been moved from another agent server with its contents intact, the host server is notified that the data has been moved; If the data stored in the storage is not data that has been moved from another agent server with its contents intact, a tag associated with the data is generated and notified to the host server. Item 2. A data retrieval system according to item 2. This allows for a configuration in which tagging processing is distributed to each agent server, and tagging processing is not performed on data that has simply been moved between agent servers, thereby reducing the load of tagging processing.

[0077] (Item 4) The host server further manages a hash value of the data and transmits the hash value to the agent server when requesting the tagging; The agent server calculates a hash value for data that has not been tagged by itself, and if the calculated hash value matches the hash value received from the host server, determines that the data has been moved from another agent server with its contents intact. Item 3. A data retrieval system according to item 3. According to this method, since the data match is confirmed using the hash value, it is possible to easily and reliably confirm that the data content has not been altered.

[0078] (Item 5) If the agent server determines that the data has been moved from another agent server with its contents intact, it transmits the hash value to the host server; The host server manages the hash value received from the agent server. Item 4. A data retrieval system according to item 4. With this, the host server does not calculate hash values ​​by itself, but acquires and manages hash values ​​generated by the agent server, so the host saga does not need to bear the load of hash value calculation processing.

[0079] (Item 6) The tag is associated in advance with sample data including one or more words related to the tag, the agent server associates the data with a tag corresponding to the sample data if the similarity between the data and the sample data is equal to or greater than a predetermined threshold; Item 2. A data retrieval system according to item 2. This allows tags to be assigned to data without manual intervention, making it easy to continually update tags.

[0080] (Item 7) the data is a file, the file containing one or more columns and the column names; First tag sample management information that associates a file tag, which is a tag assigned to a file, with sample data that includes one or more words related to the file tag, and second tag sample management information that associates a column tag, which is a tag assigned to a column, with sample data that includes one or more words related to the column tag, are set in advance; The agent server calculating a similarity between each column included in the file and the sample data of the second tag sample management information, and if there is a column and sample data for which the similarity is equal to or greater than a threshold, assigning a column tag associated with the sample data to the column; calculating a similarity between a column name included in the file and sample data in the first tag sample management information, and if there is sample data whose similarity with the file is equal to or greater than a threshold, assigning a file tag associated with the sample data to the file; Item 6. A data retrieval system according to item 6. This allows file tags and column tags to be assigned to data without manual intervention, making it easy to continuously update file tags and column tags.

[0081] (Item 8) The host server updates the tag management information at regular intervals. Item 1. A data retrieval system according to item 1. This allows the desired data to be properly found using the tag. [Explanation of symbols]

[0082] 101...host server, 102...CPU, 103...memory, 104...tag-based data search function unit, 105...data storage location management function unit, 106...data storage location management table, 107...data tag management function unit, 108...tag sample management function unit, 109...file tag management table, 110...column tag management table, 111...storage management table, 112...cache management table, 113...tag sample management table, 113A...tag sample management table, 113B...tag sample management table, 114...agent server, 115...CPU, 116...memory, 117...data tagging function unit, 118...data extraction function unit, 119...storage location check function unit, 120...storage, 121...tag data cache, 501...column tag name, 502...sample data, 601...file tag name, 602...sample data, 801...data, 901...data, 1201...query

Claims

1. a plurality of agent servers each having a storage and storing data in said storage; a host server that manages tag management information for the data, which associates tags, which are search terms for the data, with storage, which is a storage location of the data, and receives a query including a search specified tag, and responds by referencing the tag management information to retrieve data associated with the search specified tag from the storage, which is a storage location of the data; The host server periodically sending a request for tagging data stored in the storage to each of the plurality of agent servers; Upon receiving the request, the agent server: The agent server determines whether the data has been tagged, If the data has already been tagged by the agent server, the tag associated with the data is not generated. If the data has not been tagged by the agent server, it is determined whether the data has been moved from another agent server with its contents intact; If the data has been moved from another agent server with its contents intact, a tag associated with the data is not generated, and the host server is notified that the data has been moved from the other agent server; If the data has not been tagged by the agent server and has not been moved from another agent server with its contents intact, a tag is generated to be associated with the data, and the generated tag is notified to the host server; The host server updates the tag management information based on the notification. Data retrieval system.

2. the host server further manages hash values ​​of data stored in the storage of each of the plurality of agent servers, and when requesting tagging, transmits all of the managed hash values ​​to the plurality of agent servers; The agent server calculates a hash value for data that has not been tagged by the agent server among the data stored in the storage of the agent server, and if the hash value matches the hash value received from the host server, determines that the data has been moved from another agent server with its contents intact.

2. The data retrieval system according to claim 1.

3. If the agent server determines that the data has been moved from another agent server with its contents intact, it transmits the hash value to the host server; the host server updates information for managing hash values ​​of data stored in the storage of each of the plurality of agent servers so that the information includes the hash value received from the agent server; 3. The data search system according to claim 2.

4. The tag is associated in advance with sample data including one or more words related to the tag, the agent server associates the data with a tag corresponding to the sample data if the similarity between the data and the sample data is equal to or greater than a predetermined threshold; 2. The data retrieval system according to claim 1.

5. the data is a file, the file including one or more columns and column names for each of the one or more columns; First tag sample management information that associates a file tag, which is a tag assigned to a file, with sample data that includes one or more words related to the file tag, and second tag sample management information that associates a column tag, which is a tag assigned to a column, with sample data that includes one or more words related to the column tag, are preset; The agent server calculating a similarity between each column included in the file and the sample data of the second tag sample management information, and if there is a column and sample data for which the similarity is equal to or greater than a threshold, assigning a column tag associated with the sample data to the column; a similarity between a column tag name of each column included in the file and sample data in the first tag sample management information is calculated, and if there is sample data whose similarity with the column tag name of the column included in the file is equal to or greater than a threshold, a file tag associated with the sample data is assigned to the file; 5. The data search system according to claim 4.

6. A data search method in a computer system having a plurality of agent servers and a host server, comprising: The agent servers each have a storage device and store data in the storage device; the host server manages tag management information for the data, which associates tags, which are search terms for the data, with storage, which is a storage location of the data; receives a query including a search specification tag, and responds by referencing the tag management information to retrieve data associated with the search specification tag from the storage, which is a storage location of the data; The host server periodically sending a request for tagging data stored in the storage to each of the plurality of agent servers; Upon receiving the request, the agent server: The agent server determines whether the data has been tagged, If the data has already been tagged by the agent server, the tag associated with the data is not generated. If the data has not been tagged by the agent server, it is determined whether the data has been moved from another agent server with its contents intact; If the data has been moved from another agent server with its contents intact, a tag associated with the data is not generated, and the host server is notified that the data has been moved from the other agent server; If the data has not been tagged by the agent server and has not been moved from another agent server with its contents intact, a tag is generated to be associated with the data, and the generated tag is notified to the host server; The host server updates the tag management information based on the notification. Data retrieval methods.

Images