JP2019101533A - Support device for active use of data, support system for active use of data, and support method for active use of data - Google Patents

Abstract

To enable relevance between data in a data base to be easily and properly recognized.SOLUTION: A server 112 supporting active use of data comprises: a first metadata generation part 113 generating first metadata 114 regarding data in a data base 130 based on an access history; a second metadata generation part 118 generating second metadata 119 regarding data in a data base 111 based on an access history; a data-related information generation part 123 generating related information causing data in the relevant data base 130 to correspond to data in the data base 111 based on the first metadata 114 and the second metadata 119; an inquiry result generation part 122 and an inquiry result output part 121 that identify another data related to prescribed data in the data base 130 based on the related information, and output information regarding relevancy between the prescribed data and the relevant another data.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a data utilization support apparatus and the like that support utilization of data managed in a plurality of databases.

  In recent years, an effort has been made to open a database of survey results, research results, etc. for the purpose of accelerating technological development, and a technology related to such an approach is known (for example, see Patent Document 1). For example, in the field of material development, a database on the characteristics of materials obtained by experiments and simulations is published. In the medical field, efforts are being made to open up databases such as receipt information and medical examinations.

  These published databases are called open data. By utilizing open data, it is possible to obtain data that could not be obtained conventionally, and it is expected to be effective in accelerating technology development.

  A data lake is used as a technology for managing data stored in a database (see, for example, Patent Document 2). In data lakes, it is widely used to add metadata to data. Examples of metadata added to data include the creator of the data, the date and time of creation, and the file name of the data. In data lakes, metadata is provided in advance to data to facilitate data search and use. For example, metadata "chair" can be added to image data including a chair image. By providing metadata in this manner, it is possible to easily search for data including a chair image from a large number of image data.

JP, 2014-14068, A JP 2017-54487 A

  For example, although a certain company may have a database (in-house database) in the company, it is considered that the use of open data, not only in-company database, promotes technology development. However, whether technology development can be promoted depends on how to connect and use an in-house database and open data. Therefore, it is required to be able to easily grasp the relationship between data in an in-house database and open data, and the relationship between data in an in-house database linked via open data.

  In addition, when open data is used, there may be a problem that the access history of the open data leaks to the outside. For example, when the access history leaks to the outside, there is a possibility that the corporate activity can be estimated from the outside of the corporate.

  The present invention has been made in view of the above-mentioned circumstances, and an object thereof is to provide a technology which enables the relevance of data of a database to be grasped easily and appropriately.

  In order to achieve the above object, a data utilization support device according to one aspect is a data utilization support device for supporting utilization of data of a plurality of databases, which is a first database based on the access history by the user to the first database. The first metadata generation unit that generates the first metadata related to the second data, and the second metadata generation that generates the second metadata related to the data of the second database based on the access history by the user for the second database A related information generation unit that generates related information for correlating the data of the related first database with the data of the second database based on the first metadata and the second metadata, and based on the related information , Identifying other data associated with the predetermined data of the first database, and Comprising a related information output processing unit for outputting information about the association with other data.

  According to the present invention, it is possible to easily and appropriately grasp the relevancy of database data.

FIG. 1 is an overall configuration diagram of a data utilization support system according to an embodiment. FIG. 2 is a block diagram of first metadata according to an embodiment. FIG. 3 is a configuration diagram of a user attribute table according to an embodiment. FIG. 4 is a block diagram of second metadata according to an embodiment. FIG. 5 is a configuration diagram of a data association table according to an embodiment. FIG. 6 is a configuration diagram of a data history table according to an embodiment. FIG. 7 is a configuration diagram of a download data management table according to an embodiment. FIG. 8 is a block diagram of an access log according to an embodiment. FIG. 9 is a hardware configuration diagram of a server according to an embodiment. FIG. 10 is a hardware configuration diagram of a proxy server according to an embodiment. FIG. 11 is a flowchart of data management processing according to an embodiment. FIG. 12 is a flowchart of related object display processing according to an embodiment. FIG. 13 is a diagram illustrating an inquiry request according to an embodiment. FIG. 14 is a diagram showing an inquiry result screen according to an embodiment. FIG. 15 is a flowchart of data acquisition management processing according to an embodiment. FIG. 16 is a flowchart of download data generation processing according to an embodiment.

  Embodiments will be described with reference to the drawings. The embodiments described below do not limit the invention according to the claims, and all of the elements described in the embodiments and their combinations are essential to the solution means of the invention. There is no limit.

  In the following description, information may be described by the expression “AAA table”, but the information may be expressed by any data structure. That is, the "AAA table" can be called "AAA information" to indicate that the information does not depend on the data structure.

  FIG. 1 is an overall configuration diagram of a data utilization support system according to an embodiment.

  The data utilization support system 10 includes one or more terminals 102, a proxy server 104, one or more external sites 110 (110a and 110b), a server 112 as an example of a data utilization support device, and an example of a storage device. And a storage device 129. The terminal 102, the proxy server 104, and the server 112 are connected via the network 103. The proxy server 104 and the external site 110 are connected via the network 109. The server 112 and the storage device 129 are connected, for example, via a cable.

  In the present embodiment, the terminal 102, the proxy server 104, the server 112, and the storage device 129 are arranged in a certain company (in-house), and the external site 110 is arranged outside the certain company. ing. In the present embodiment, the network 103 is, for example, a LAN (Local Area Network), and the network 109 is, for example, a Wide Area Network (WAN) such as the Internet. The configurations of the network 103 and the network 109 are not limited to this, and may be any network using wire or wireless.

  The external site 110 (110a, 110b) has a database 111 (111a, 111b) for storing various data, and provides functions such as searching and browsing the database 111. Here, the database 111 corresponds to a second database (external database). In the present embodiment, the database 111 of the external site 110 is an open database (open data) in which available users are not limited.

  The terminal 102 is a device used by a user (user) 101 who is an employee of a certain company when using the database 111 of the external site 110 and the database 130 of the storage device 129. The terminal 102 is constituted by, for example, a PC (Personal Computer) including a CPU, a memory, etc., receives an input request for access to a database (for example, a search keyword etc.), transmits it to another device, and transmits it to other devices. It receives the information etc. of the access result and displays it on a display etc. not shown. In the present embodiment, the terminal 102 receives an inquiry request for requesting display of data relevance from the user 101, transmits it to the server 112, and receives a result (inquiry result screen) corresponding to the inquiry request from the server 112 And display the query result screen.

  The storage device 129 includes, for example, a non-temporary storage device (nonvolatile storage device) such as a hard disk drive (HDD) or a solid state drive (SSD), and stores various information. In the present embodiment, the storage device 129 stores a database 130 (first database: in-house database) that can be used by the user 101 who is an employee, and a download database 131 that manages data downloaded from the external site 110.

  The server 112 comprises a data management mechanism 116. The data management mechanism 116 includes a first metadata generation unit 113, a first metadata 114, a user attribute table 115, an access log acquisition unit 117, a second metadata generation unit 118, and a second metadata 119. , An inquiry reception unit 120, an inquiry result output unit 121, an inquiry result generation unit 122, a data related information generation unit 123 as an example of a related information generation unit, a data relation table 124, and an example of related information A data history table 125, a download data search unit 126 as an example of a download data transmission unit, a download data generation unit 127 as an example of a download processing unit, and a download data management table 128 are provided. Here, the related information output control unit is configured by the inquiry result output unit 121 and the inquiry result generation unit 122.

  The first metadata generation unit 113 receives an access request for the database 130 from the terminal 102, and adds an entry corresponding to the access request to the first metadata 114 based on the information included in the access request.

  The access log acquisition unit 117 acquires the access log 108 from the proxy server 104. The second metadata generation unit 118 adds an entry corresponding to each log (entry) of the access log 108 to the second metadata 119 based on the content of the access log 108 acquired by the access log acquisition unit 117.

  The proxy server 104 has a proxy processing mechanism 150. The proxy processing mechanism 105 includes an access log acquisition unit 106, a data acquisition unit 107, and an access log 108. The access log acquisition unit 106 acquires the content of the access request from the terminal 102 to the external site 110, and adds an entry corresponding to the access request to the access log 108. The data acquisition unit 107 receives the access request from the terminal 102, and executes processing for transmitting the corresponding data to the terminal 102. The access log 108 will be described later.

  Next, tables, data, and the like stored in the server 112 will be described.

  FIG. 2 is a block diagram of first metadata according to an embodiment.

  The first metadata 114 manages information on access to the database 130 by the user 101 of the terminal 102 as an entry corresponding to each access. The entry of the first metadata 114 has fields of access date and time 401, access source IP address 402, access type 403, object name 404, and change source object 405.

  The access date and time 401 stores the date and time when data (data object: simply referred to as an object) of the database 130 is accessed. The access source IP address 402 stores the IP (Internet Protocol) address of the terminal 102 that has accessed the database 130. The access type 403 stores the type of access to the object of the database 130. Here, as the type of access, there are “Create” indicating that an object has been newly created, “View” indicating that an object has been viewed, “Change” indicating that an object has been changed, and the like. The object name 404 stores the name (object name) of an object of the accessed database 130. In the example of FIG. 2, the object name is the same as the storage destination information indicating the storage destination of the object. The change source object 405 stores the object name of the object that is the change source when the object is changed.

  FIG. 3 is a configuration diagram of a user attribute table according to an embodiment.

  The user attribute table 115 is a table for managing the attributes of the user 101 of the terminal 102, and stores an entry for each user 101. The entry of the user attribute table 115 has fields of an IP address 501, a belonging project 502, and a role 503. The IP address 501 stores the IP address assigned to the terminal 102 used by the user 101. In the belonging project 502, the name of the project to which the user 101 belongs is stored. The role 503 stores the role of the user 101.

  FIG. 4 is a block diagram of second metadata according to an embodiment.

  The second metadata 119 manages information on access to the database 111 of the external site 110 by the user of the terminal 102 as an entry corresponding to each access. The entry of the second metadata 119 has fields of access date / time 701, access source IP address 702, access type 703, search condition 704, access URL 705, and data storage destination 706.

  The access date and time 701 stores the date and time when data (data object: simply referred to as an object) of the database 111 is accessed. The access source IP address 702 stores the IP address of the terminal 102 that has accessed the database 111. The access type 703 stores the type of access to the object of the database 111. Here, as the type of access, there are a “search” indicating that the database 111 has been searched, “browse” indicating that the object has been browsed, and “download” indicating that the object has been downloaded. The search condition 704 stores the condition (search condition) used in the search corresponding to the access to the database 111. In the present embodiment, the second metadata generation unit 118 sets a plurality of search keywords in an expression format (for example, in the description of the URL to be accessed) by the second metadata generation unit 118 in the search condition 704. The search conditions converted into the expression form unified between the databases 111 are stored. Thereby, the difference in the expression form due to the difference in the database 111 is absorbed. The access URL 705 stores a URL (Uniform Resource Locator) of the accessed data. The data storage destination 706 stores information (storage destination information) indicating the storage destination of the data when the data is downloaded. Here, the storage destination information is, for example, acquired from the access request from the terminal 102.

  FIG. 5 is a configuration diagram of a data association table according to an embodiment.

  The data association table 124 is a table that manages the object to which the database 111 has been accessed and the object of the database 130 to which the access has occurred after accessing the object in association with each other. The entries of the data association table 124 include fields of a first database object 901, a second database object 902, a temporal relevance 903, an access method relevance 904, and a search keyword 905.

  In the first database object 901, storage destination information of objects of the database 130 is stored. In the second database object 902, storage destination information of objects of the database 111 is stored. The temporal degree of association 903 stores the degree of association regarding the access time between the object of the database 130 corresponding to the entry and the object of the database 111. The degree of association may be an interval of occurrence time of those accesses. In the access method association degree 904, the association degree regarding the access method of the object of the database 130 corresponding to the entry and the object of the database 111 is stored. The degree of association regarding the access method stores the type of access to the objects of the database 111. The search keyword 905 stores the search keyword used in the search corresponding to the access to the database 111.

  FIG. 6 is a configuration diagram of a data history table according to an embodiment.

  The data history table 125 is a table for managing how the objects of the database 111 and the database 130 are accessed, that is, the data history, and for example, the object of the database 111 and the access to this object are affected. It is a table which manages the correspondence between the objects of the database 130 and the objects of the database 130 affected by the objects of the database 111. The entries of the data history table 125 include a first database object 1 1001, a first database object 2 1002, a second database object 1003, a temporal relevance 1004, an access method relevance 1005, and a search keyword 1006. Including fields.

  In the second database object 1003, storage destination information (also referred to as an object name) of an object of the database 111 is stored. In the first database object 1 1001, storage destination information (also referred to as object name) of an object of the database 130 that was accessed before access to an object of the database 111 where storage destination information is stored in the second database object 1003 of the entry Is stored. The first database object 2 1002 includes storage location information (also referred to as an object name) of an object of the database 130 accessed after accessing an object of the database 111 in which storage location information is stored in the second database object 1003 of the entry. Stored.

  In the temporal relevance 1004, the degree of association regarding the access time between an object of the database 111 corresponding to the entry (an object whose storage destination information is stored in the second database object 1003) and an object of the first database object 2 1002. Is stored. The degree of association may be an interval of occurrence time of those accesses. In the access method association degree 1005, the association degree regarding the access method of the object of the database 130 corresponding to the entry and the object of the first database object 2 1002 is stored. The degree of association regarding the access method stores the type of access to the objects of the database 111. The types of access include, for example, “search” indicating that an object has been searched, “browse” indicating that an object has been browsed, and “download” indicating that an object has been downloaded. Here, it means that the object of the database 130 corresponding to the entry and the object of the first database object 2 1002 are highly correlated in the order of downloading, browsing, and searching. The search keyword 1006 stores the search keyword used in the search corresponding to the access to the database 111.

  FIG. 7 is a configuration diagram of a download data management table according to an embodiment.

  The download data management table 128 is a table for managing data downloaded from the database 111 to the storage device 129, and stores an entry for each object downloaded from the database 111.

  The entry of the download data management table 128 includes fields of a second database object 1401 and a download database object 1402.

  The second database object 1401 stores storage destination information (object name) of the object downloaded from the database 111 corresponding to the entry. The download database object 1402 stores storage destination information (object name) of an object of the download database 131 in which data of the object of the database 111 corresponding to the entry is stored.

  FIG. 8 is a block diagram of an access log according to an embodiment.

  The access log 108 is a log for managing information on access from the terminal 102 to the external site 110 (object of the database 111). The entry of the access log 108 has fields of access date / time 601, access source IP address 602, access destination IP address 603, access URL 604, and data storage destination 605.

  The access date 601 stores the date when the object of the database 111 corresponding to the entry is accessed. The access source IP address 602 stores the IP address of the terminal 102 that has accessed the database 111. The access destination IP address 603 stores the IP address of the server that manages the database 111 of the external site 110 that is the access destination. The access destination URL 604 stores the URL of the data of the access destination. Data storage destination 605 stores data storage destination information when data is downloaded. Here, the storage destination information can be acquired from, for example, an access request from the terminal 102.

  FIG. 9 is a hardware configuration diagram of a server according to an embodiment.

  The server 112 includes a central processing unit (CPU) 201 as an example of a processor, and a memory 203. The CPU 201 and the memory 203 are connected via the bus 202. The server 112 is provided with a communication interface (not shown) and the like.

  The CPU 201 executes various processes in accordance with a program stored in the memory 203. The memory 203 is, for example, a RAM (RANDOM ACCESS MEMORY), and stores a program executed by the CPU 201 and necessary information. In the present embodiment, the memory 203 stores information such as programs and tables required to configure the data management mechanism 116. In the present embodiment, each processing unit shown in FIG. 1 constituting the data management mechanism 116 is configured by the CPU 201 executing a program stored in the memory 203.

  FIG. 10 is a hardware configuration diagram of a proxy server according to an embodiment.

  The proxy server 104 includes a CPU 301 as an example of a processor, and a memory 303. The CPU 301 and the memory 303 are connected via the bus 302. The proxy server 104 is provided with a communication interface (not shown) and the like.

  The CPU 301 executes various processes in accordance with a program stored in the memory 303. The memory 303 is, for example, a RAM, and stores programs executed by the CPU 301 and necessary information. In the present embodiment, the memory 303 stores information such as programs and tables required to configure the proxy processing mechanism 105. In the present embodiment, each processing unit shown in FIG. 1 constituting the proxy processing mechanism 105 is configured by the CPU 301 executing a program stored in the memory 303.

  Next, the processing operation of the data utilization support system according to the embodiment will be described.

  First, data management processing by the data-related information generation unit 123 of the server 112 will be described.

  FIG. 11 is a flowchart of data management processing according to an embodiment.

  First, the data-related information generation unit 123 extracts one data (entry) in the past predetermined period (for example, one day) from the second metadata 119 in time order (step 801). Here, in the description of the present process, the extracted data is referred to as target metadata.

  Next, the data-related information generation unit 123 determines that the target metadata and the access source IP address are the same IP address, and the data (entry) of the first metadata 114 whose access date and time is later than the access date and time of the target metadata. It is determined whether or not there is (step 802).

  As a result, when the target metadata and the access source IP address are the same IP address, and there is no entry of the first metadata 114 whose access date and time is later than the access date and time of the target metadata (step 802: No). The data related information generation unit 123 proceeds with the process to step 808.

  On the other hand, if the target metadata and the access source IP address are the same IP address, and there is an entry of the first metadata 114 whose access date and time is later than the access date and time of the target metadata (step 802: Yes) Since it is considered that the object corresponding to the target metadata and the object corresponding to this entry are accessed by the same terminal 102 (user 101) and the object corresponding to this entry is highly relevant, the data-related information generation unit 123 Fetch one entry (step 803). Here, in the description of the present process, the extracted entry is referred to as post-relevant metadata.

  Next, the data-related information generation unit 123 adds an entry corresponding to the content of the post-related metadata to the data related data 124 (step 804).

  Next, the data-related information generation unit 123 determines that the target metadata and the access source IP address are the same IP address, and the data (entry) of the first metadata 114 whose access date and time is earlier than the access date and time of the target data. It is determined whether there is any (step 805).

  As a result, when the target metadata and the access source IP address are the same IP address, and there is no entry of the first metadata 114 whose access date and time is earlier than the access date and time of the target metadata (step 805: No). The data-related information generation unit 123 advances the process to step 807.

  On the other hand, when the target metadata and the access source IP address are the same IP address, and there is an entry of the first metadata 114 whose access date and time is earlier than the access date and time of the target metadata (step 805: Yes) Since the object corresponding to the target metadata and the object corresponding to this entry (previous related metadata) are considered to be highly relevant, the data related information generation unit 123 converts the data history table 125 to the target metadata. The corresponding entry is added (step 806), and the process proceeds to step 807. In step 806, specifically, the data-related information generation unit 123 adds an entry to the data history table 125, and stores the content of the access URL 705 in the target metadata in the second database object 1003 with respect to the entry. The content of the access type 703 in the target metadata is stored in the access method relevance 1005, the value of the search condition 704 in the target metadata is stored in the search keyword 1006, and the object name 404 of the post related metadata is the first database object 2 stored in 1002, the object name 404 of the previous related metadata is stored in the first database object 1001, and the time difference between the access date and time 401 of the previous related metadata and the access date and time 701 of the target metadata is Relationship Store in degrees 1004.

  In step 807, the data-related information generation unit 123 sets the target metadata and the access source IP address to the same IP address, and for all the first metadata 114 whose access date and time is later than the access date and time of the target metadata. It is determined whether the process for the entry has been completed (step 807). If the process is not completed (step 807: No), the process proceeds to step 803 while the process is completed (step). 807: Yes), the process proceeds to step 808.

  In step 808, the data-related information generation unit 123 determines whether or not processing for all data (entries) within a predetermined period in the past has been completed (step 808), and if the processing is not completed (step 808) If NO, the process proceeds to step 801, and if the process is completed (step 808: YES), the data management process is ended.

  Next, related object display processing by the server 112 will be described.

  FIG. 12 is a flowchart of related object display processing according to an embodiment. FIG. 13 is a diagram illustrating an inquiry request according to an embodiment. FIG. 14 is a diagram showing an inquiry result screen according to an embodiment.

  The inquiry receiving unit 120 of the server 112 determines whether an inquiry request has been received from the terminal 102 (step 1601).

  As a result, if the inquiry request has not been received (step 1601: No), the inquiry receiving unit 120 proceeds the process to step 1601 while if the inquiry request has been received (step 1601: Yes) And notify the inquiry result generation unit 122 that the inquiry request has been received. Here, as shown in FIG. 13, the inquiry request includes storage destination information (object name) of an object to be displayed on the information of the related object.

  The query result generation unit 122 that has received the notification that the query request has been received, based on the storage location information of the object included in the query request, detects the database 130 that was accessed before accessing the object of the storage location information. Information of the object (previous related object) is acquired (step 1602). Specifically, the query result generation unit 122 refers to the data history table 125, specifies an entry whose storage destination information of the object included in the query request is stored in the first database object 2 1002, and information of this entry To get

  Then, based on the storage destination information of the object included in the query request, the query result generation unit 122 acquires information of an object (post-related object) of the database 130 accessed after accessing the object of the storage destination information Step 1603). Specifically, the inquiry result generation unit 122 refers to the data history table 125, specifies an entry in which the storage destination information of the object included in the inquiry request is stored in the first database object 1001, and the information of this entry To get

  Next, the inquiry result generation unit 122 generates the inquiry result screen 1200 (see FIG. 14) based on the information of the entry acquired in step 1602 and step 1603, and the inquiry result output unit 121 causes the terminal of the request source of the inquiry request. The inquiry result screen 1200 is displayed on the screen 102 (step 1604).

  Here, in the query result screen 1200, as shown in FIG. 14, a target object display area 1201 in which storage destination information of an object (target object) targeted by the query request is displayed, and access before accessing the target object The previous related object display area 1202 in which the storage destination information of the previous related object is displayed, and the rear related object display area 1203 in which the storage destination information of the previous related object accessed after accessing the target object is displayed Used to access the previous external object display area 1204 for displaying the storage destination information of the object (previous external object) of the database 111 that was being accessed during the access between the object and the previous related object, and the previous external object Search key A keyword display area 1205 for displaying a document, and a post external object display area 1206 for displaying storage destination information of an object (post external object) of the database 111 which has been accessed during access to the target object and the post related object; And a keyword display area 1207 for displaying a search keyword used to access the back external object.

  According to the inquiry result screen 1200, it is possible to easily and appropriately confirm the object of the database 130 viewed before the target object, the object of the database 111 accessed during that time, and the search keyword used. Therefore, it is possible to easily and appropriately grasp the progress of the target object. Further, according to the inquiry result screen 1200, it is possible to easily and appropriately confirm the object of the database 130 seen after the target object, the object of the database 111 accessed during that time, and the search keyword used. Therefore, it is possible to easily and appropriately grasp what kind of progress has been taken from the target object.

  Next, data acquisition management processing by the data acquisition unit 107 of the proxy server 104 will be described.

  FIG. 15 is a flowchart of data acquisition management processing according to an embodiment.

  The data acquisition unit 107 of the proxy server 104 determines whether a request for access to data (request) has been received from the terminal 102 (step 1301). As a result, when the request for access is not received (Step 1301: No), the data acquisition unit 107 proceeds with the process to Step 1301.

  On the other hand, when the request for access is received (step 1301: Yes), the data acquisition unit 107 instructs the download data search unit 126 whether or not the data to be requested (target data) is stored in the download database 131. An inquiry is made (step 1302). As a result, the download data search unit 126 having received the inquiry refers to the download data management table 128 to determine whether or not the target data is stored in the download database 131, and returns the determination result to the data acquisition unit 107. It will be done.

  Next, the data acquisition unit 107 determines whether the target data is stored in the download database 131 based on the determination result from the download data search unit 126 (step 1303).

  As a result, when the target data is stored in the download database 131 (step 1303: Yes), the data acquisition unit 107 acquires the target data from the town load database 131 via the download data search unit 126 of the server 112. Then, the target data is transmitted to the request source terminal 102 (step 1304), and the process is ended.

  On the other hand, when the target data is not stored in the download database 131 (step 1303: No), the data acquisition unit 107 transmits the access request for the target data to the external site 110, so that the target is acquired from the database 111. The data is acquired, the target data is transmitted to the request source terminal 102 (step 1305), and the process is ended.

  According to the data acquisition management process described above, since the request for access to the data downloaded to the download database 131 is not transmitted to the external site 110, the information on the data to be accessed to the external site 110 is Can be properly prevented from becoming known.

  Next, download data generation processing by the download data generation unit 127 of the server 112 will be described.

  FIG. 16 is a flowchart of download data generation processing according to an embodiment.

  Based on the data history table 125, the download data generation unit 127 estimates open data that is likely to be used in the future (step 1501).

  Here, as data that is likely to be used in the future, for example, data having a high frequency of appearance as a search keyword may be used. Further, data likely to be used in the future may be data of the database 111 of another external site 110 searched by a keyword corresponding to a search keyword for the database 111 of one external site 110. Also, data that is likely to be used in the future may be other data included in the search results when data actually downloaded by the user is searched. In addition, in determining whether the possibility of use in the future is high, for example, it may be determined that the higher the degree of association of the access method is, the higher the degree of temporal relevancy ( It may be determined that the possibility is higher as the time difference is smaller. In addition, whether or not the possibility of being used in the future is high may be determined based on the browsing frequency, the frequency of downloading, and the like.

  Next, the download data generation unit 127 uses the result estimated in step 1501 to download data from the second database (database 111) to the download database 131 (step 1502).

  Next, the download data generation unit 127 adds an entry corresponding to the downloaded data to the download data management table 128 (step 1503), and ends the process.

  According to the download data generation process, data which is likely to be used in the future is downloaded in advance to the download database 131. Therefore, when there is a request for access to the corresponding data from the terminal 102 thereafter. Desired data can be transmitted to the terminal 102 without accessing the database 111 of the external site 110. For this reason, it is possible to appropriately prevent the external site 110 from being informed about the data to be accessed.

  The present invention is not limited to the embodiments described above, and can be appropriately modified and implemented without departing from the spirit of the present invention.

  For example, although the access log of the terminal 102 is acquired from the proxy server 105 in the above embodiment, the present invention is not limited to this, for example, the terminal 102 may store the access log for the external site 110 The access log may be acquired from the terminal 102.

  Further, although the server 112 and the storage device 129 are separated in the above embodiment, the present invention is not limited to this, and the configuration and function of the storage device 129 may be provided in the server 112.

  In the above embodiment, a part or all of the processing performed by the CPU (CPUs 201 and 301) may be performed by a dedicated hardware circuit. Also, the program in the above embodiment may be installed from a program source. The program source may be a program distribution server or storage medium (eg, portable non-volatile storage medium).

  10: data utilization support system, 102: terminal, 104: proxy server, 110: external site, 111: database, 112: server, 113: first metadata generation unit, 114: first metadata, 118: second metadata Data generation unit 119 Second metadata 121 Inquiry result output unit 122 Inquiry result generation unit 123 Data related information generation unit 125 Data history table 127 Download data generation unit 129 Storage device , 130 ... database, 131 ... download database, 1200 ... inquiry result screen.

Claims (12)

A data utilization support device for supporting utilization of data of a plurality of databases,
A first metadata generation unit that generates first metadata related to data of the first database based on a user's access history to the first database;
A second metadata generation unit that generates second metadata related to data of the second database based on an access history by a user with respect to the second database;
A related information generation unit that generates related information that associates data of the first database with data of the second database based on the first metadata and the second metadata;
A related information output processing unit that specifies other data related to predetermined data in the first database based on the related information, and outputs information related to the predetermined data and the related other data When,
Data utilization support device provided with The first database is a database limited in available users,
The data utilization support device according to claim 1, wherein the second database is a database in which available users are not limited. The related information is accessed after accessing the data of the first database, the data of the second database accessed before accessing the data of the first database, and the data of the first database The data utilization support device according to claim 1 or 2, further comprising information correlating with the data of the second database. The data utilization support device according to claim 3, wherein the related information output processing unit specifies that a plurality of data in the first database, which are accessed across access to data in the same second database, are related. There are a plurality of second databases,
The second metadata includes a search condition corresponding to a search keyword at the time of access to a plurality of the second databases,
5. The method according to claim 1, wherein the second metadata generation unit converts the search keyword in each of the second databases into a search condition in an expression format unified among the plurality of second databases. The data utilization support device according to one item. The information processing apparatus further includes an access history acquisition unit that acquires an access history to the second database from a proxy server that relays access to the second database by a user terminal.
The data utilization support device according to any one of claims 1 to 5, wherein the second metadata generation unit generates the second metadata based on the access history acquired by the access history acquisition unit. . The related information output processing unit includes: information indicating a plurality of related data of the first database; information indicating data of the second database accessed during access to the plurality of data; and the second database The data utilization support device according to any one of claims 1 to 6, displaying a screen including information of a search condition used when searching for the data of. A download processing unit that downloads highly likely data from the second database based on the related information and stores the data in a predetermined storage device;
The download data transmission part which takes out the said data from the said storage device, and there is an access request | requirement to the said downloaded said data, It transmits to an access request origin. The data utilization support device according to any one of the items. Comprising a plurality of said second databases,
The download processing unit downloads data corresponding to a search result obtained by performing a search on another second database based on a search condition used for accessing the one second database. The data utilization support device according to claim 8, stored in the storage device. A data utilization system comprising a first database, a second database, and a data utilization support device for supporting utilization of data of the first database and the second database,
The data utilization support device is
A first metadata generation unit that generates first metadata related to data of the first database based on a user's access history to the first database;
A second metadata generation unit that generates second metadata related to data of the second database based on a user's access history to the second database;
A related information generation unit that generates related information that associates data of the first database with data of the second database based on the first metadata and the second metadata;
A related information output processing unit that specifies other data related to predetermined data in the first database based on the related information, and outputs information related to the predetermined data and the related other data When,
Data utilization support system equipped with The data utilization support system is
And a proxy server that handles access to the second database from the user's terminal;
A storage device storing data of a part of the second database;
The proxy server determines whether data targeted for an access request from the terminal is stored in the storage device, and in the case where the data is stored in the storage device, from the storage device 11. The data utilization support system according to claim 10, wherein control is performed to send the data back to the terminal. A data utilization support method by a data utilization support device for supporting utilization of data of a plurality of databases,
Generating first metadata relating to data of the first database based on a user's access history to the first database;
Generating second metadata relating to data of the second database based on access history by a user on the second database,
Based on the first metadata and the second metadata, association information is generated that associates data of the associated first database with data of the second database,
A data utilization support method for specifying other data related to predetermined data of the first database based on the related information, and outputting information related to the relation between the predetermined data and the other related data.