JP2021179857A - Data generation support device, data generation support method, and data generation support system - Google Patents

Abstract

To provide a data generation support device, a data generation support method, and a data generation support system which, even when information required for generating data is lacked, can generate the data.SOLUTION: A data generation support device 101 of a data generation support system 1 includes: a data generation request reception section for receiving request information for requesting generation of predetermined data; and a data generation management section for estimating features of contents of the predetermined data by a first model so as to identify processing capable of generating the predetermined data by other data having contents of the estimated features by a second model.SELECTED DRAWING: Figure 1

Description

The present invention relates to a data generation support device, a data generation support method, and a data generation support system.

In recent years, the amount of highly confidential data related to personal information, such as DNA data and user information of online services, has increased rapidly. These confidential data are highly useful because they can be used by organizations such as companies and research institutes for data analysis to gain significant insights into their businesses.

Examples of the method of using confidential data include mutual use of confidential data between organizations. An organization that holds a large amount of confidential data (data holding organization) processes various confidential data and analysis of those confidential data with the partner organization (alliance organization) that has an alliance for mutual use of confidential data. It provides a repository for managing the workflow to be executed and a workflow execution environment for using the workflow (utilization of on-site data). The data holding organization aims to make a profit by charging for the data usage by the customers (users of confidential data) of the alliance organization.

On the other hand, as a social trend related to the utilization of on-site data, there is a strengthening of laws and regulations on confidential data such as GDPR (General Data Protection Regulation) in Europe and revision of the Personal Information Protection Law in Japan. .. These laws and regulations impose strict restrictions on the management of sensitive data. Therefore, the data holding organization prohibits users from accessing particularly sensitive data (primary data), and instead restricts the particularly sensitive part of the primary data (for example, personally identifiable information). Access by users is permitted only for high-order data with relatively low confidentiality (secondary data, tertiary data obtained by further processing the secondary data, etc.) obtained by performing processing such as removal. We are taking measures such as.

Here, as a method of utilizing the secondary data, Patent Document 1 includes a data management system that enables the user to select a data processing workflow or a processing program for obtaining the target secondary data at his / her own discretion. It has been disclosed.

Japanese Patent Application Laid-Open No. 2019-1974983

However, the system of Patent Document 1 is premised on the case where the user of the data can access the primary data. In this case, if measures are taken to prevent the user from accessing the primary data, the user cannot use this system.

That is, the user needs to instruct the data holding organization or the alliance organization on the workflow (processing program) to be executed in order to obtain the secondary data that he / she wants to use. For that purpose, it is often necessary to know information about the primary data from which the data is based. For example, in order to specify the primary data to be input to the workflow, it is necessary to know the nature (content aspect) of the data as well as the data format such as the file extension as the information regarding the input data to the workflow.

However, if the user does not have access to the primary data in the first place, the user will not be able to know such information and will not be able to access the appropriate primary data and, as a result, select the workflow to be executed. Can not do it.

The present invention has been made in view of such a background, and an object thereof is data generation capable of generating data even if the information necessary for generating the data is lacking. The purpose is to provide a support device, a data generation support method, and a data generation support system.

One of the present inventions for solving the above-mentioned problems is a data generation request acceptance process for receiving request information requesting the generation of predetermined data, and an estimation of the characteristics of the contents of the predetermined data by a first model. A data generation support device including a calculation device for executing a data generation management process specified by a second model as a process in which the predetermined data can be generated by other data having the contents of the estimated features.

Further, another one of the present invention for solving the above-mentioned problems is a data generation request acceptance process in which the information processing apparatus receives request information requesting the generation of predetermined data, and the content of the predetermined data. Data generation support that estimates features by the first model and executes a process that can generate the predetermined data by other data having the contents of the estimated features, and a data generation management process that specifies by the second model. The method.

Another aspect of the present invention for solving the above problems is a user terminal for transmitting request information requesting the generation of predetermined data, a data generation request acceptance process for receiving the request information, and a data generation request acceptance process. A process in which the characteristic of the content of the predetermined data is estimated by the first model and the predetermined data can be generated by other data stored in the predetermined information processing apparatus having the content of the estimated characteristic is performed. The predetermined information processing apparatus is configured to include a data generation support device that executes data generation management processing specified by the two models, and the predetermined information processing apparatus stores the other data and the other by the user terminal. It is a data generation support system that prohibits access to data.

According to the present invention, even if the information necessary for generating the data is lacking, the data can be generated.

Issues, configurations and effects other than those described above will be clarified by the following description of the embodiments.

It is a figure which shows an example of the structure of the data generation support system which concerns on Example 1. FIG. It is a figure which shows an example of a data file. It is a figure explaining the detail of the data generation management part. It is a figure explaining an example of the function which the article search support system has. It is a figure which shows an example of a workflow metadata management table. It is a figure which shows an example of the file metadata extraction rule. It is a figure which shows an example of a workflow metadata extraction rule. It is a figure which shows an example of a workflow execution log. It is a figure which shows an example of the hardware composition which each information processing apparatus (user terminal, a data generation support apparatus, a workflow execution apparatus, a file management server, and a management console) in a data generation support system has. It is a flow diagram explaining an example of data generation support processing. It is a figure which shows an example of a data generation request. It is a figure which shows an example of a workflow specific screen. It is a flow diagram explaining an example of a file metadata management table generation process. It is a flow diagram explaining an example of a workflow metadata management table generation process. It is a figure which shows a part of the configuration example in the data generation support system which concerns on Example 2. FIG. It is a figure which shows an example of a workflow plan management table. It is a flow diagram explaining an example of a workflow plan management table generation process.

The data generation support system according to this embodiment will be described with reference to the drawings. It should be noted that the embodiments described below do not limit the invention according to the claims, and all of the elements and combinations thereof described in the embodiments are indispensable for the means for solving the invention. Is not always.

[Example 1]
-System configuration-
FIG. 1 is a diagram showing an example of the configuration of the data generation support system 1 according to the first embodiment.

The data generation support system 1 includes a user terminal 102, a file management server 105, a workflow execution device 120, a data generation support device 101, and a management console 107.

The user terminal 102 is an information processing device used by a user (organization or individual, for example, a doctor).

The file management server 105 is managed by a predetermined business operator and stores various confidential data (hereinafter, also referred to as primary data). The file management server 105 is, for example, a database device for genetic information of a large number of people managed by a predetermined data holding organization or an alliance organization thereof.

The file management server 105 permits access from the data generation support device 101 and the workflow execution device 120, but prohibits access from the user terminal 102.

The workflow execution device 120 is an information processing device managed by a predetermined business operator (for example, a data holding organization or an alliance organization thereof). The workflow execution device 120 processes the primary data by executing a predetermined processing program (hereinafter referred to as a workflow) based on the data generation request 108 received from the user terminal 102 and the primary data of the file management server 105. Data with low confidentiality (secondary data) obtained and data obtained by further processing this secondary data (hereinafter, these data are collectively referred to as result data) are generated.

The secondary data is, for example, mutation information generated based on genetic information. Outcome data is, for example, disease risk information generated based on mutation information.

The data generation support device 101 is an information processing device that mediates between the user terminal 102 and the workflow execution device 120. The data generation support device 101 identifies the primary data necessary for generating the result data based on the data generation request 108 received from the user terminal 102, and the result data is sent to the workflow execution device 120 based on the specified primary data. Requests the generation of (data generation plan).

The management console 107 is an information processing device used by the administrator 106 (organization or individual) of the data generation support device 101.

Wired LAN (Local Area Network), WAN (Wide Area Network), Internet, dedicated line, etc. between the user terminal 102, data generation support device 101, file management server 105, management console 107, and workflow execution device 120. Alternatively, it is communicably connected by a wireless network.

Here, the user of the user terminal 102 wants to obtain desired result data by designating the data held by himself / herself as the data generation request 108 and the workflow for generating the result data.

However, in order to execute the workflow, it is necessary to specify the primary data to be used, and the business operator cannot provide the information about this primary data to the user. Therefore, the business operator would normally have to perform complicated work to identify the necessary primary data from the provided data.

Therefore, the data generation support device 101 of the present embodiment automatically identifies an appropriate workflow for the user's data generation request 108, and causes the workflow execution device 120 to generate result data.

Hereinafter, the details of such a data generation support system 1 will be described.

--User terminal ---
First, the user terminal 102 transmits a data generation request 108 input by the user, which requests the generation of result data. The user terminal 102 includes a GUI (Graphic User Interface), a CUI (Command User Interface), and the like as an interface used by the user.

--Management console ---
The management console 107 generates the file metadata extraction rule 115 and the workflow metadata extraction rule 118 described later in the data generation support device 101 by input from the administrator 106. The management console 107 includes a GUI (Graphic User Interface), a CUI (Command User Interface), and the like as an interface used by the administrator 106.

--File management server ---
The file management server 105 holds a plurality of primary data files (hereinafter, also referred to as data files) used by the workflow. The file management server 105 may be incorporated in the data generation support device 101, or may be provided as an external function of the data generation support device 101. That is, the data file managed by the file management server 105 may be provided in any form such as NAS (Network Attached Storage), a local file server, and object storage on the cloud.

(data file)
Here, FIG. 2 is a diagram showing an example of a data file. The data file 150 has a data header unit R1001 and a data body unit R1021 which are portions in which bibliographic information and the like are set. The data header unit R1001 includes sub-information R1011 to R1016 such as a data model, a size of the data body unit R1021, or an ID of an external data file 150 associated with the data file 150. The data body unit R1021 is a data body and contains confidential information. Although the figure shows an example in which the data file 150 is in the binary file format, the data file 150 may be in the text format.

--Data generation support device ---
Next, as shown in FIG. 1, the data generation support device 101 is a functional unit (program) of a data generation request receiving unit 111, a data generation management unit 112, a file metadata extraction unit 113, and a workflow metadata extraction unit 116. ).

Further, the data generation support device 101 stores a file metadata management table 114, a file metadata extraction rule 115, a workflow metadata management table 117, and a workflow metadata extraction rule 118.

First, the data generation request receiving unit 111 receives the request information requesting the generation of predetermined data (result data). That is, the data generation request receiving unit 111 receives the data generation request 108 transmitted from the user terminal 102.

Further, the data generation request receiving unit 111 transmits the result data generated by the workflow execution device 120 or the information for accessing the result data to the user terminal 102.

The data generation management unit 112 estimates the characteristics of the content of the result data by the first model (file metadata management table 114), and can generate the result data by other data (primary data) having the contents of the estimated characteristics. The process (workflow) is specified by the second model (workflow metadata management table 117).

That is, the data generation management unit 112 is based on the data generation request 108, the file metadata management table 114, and the workflow metadata management table 117, and the workflow corresponding to the request content of the data generation request 108 and the data used for the workflow. Generate a data generation plan that is information in file 150. The data generation management unit 112 transmits the generated data generation plan to the workflow execution device 120.

Further, the data generation management unit 112 is generating the result data based on the information indicating that the process (workflow) in which the result data (secondary data or the like) can be generated is specified, or the process in which the result data can be generated. Display information indicating that.

Here, the details of the data generation management unit 112 will be described.

(Data generation management department)
FIG. 3 is a diagram illustrating details of the data generation management unit 112. The data generation management unit 112 includes a data generation planning unit 301, an input file specifying unit 302, an execution workflow specifying unit 303, and a planning management unit 304.

Based on the data generation request 108 received from the data generation request receiving unit 111, the data generation planning unit 301 specifies the workflow to be executed in cooperation with the execution workflow specifying unit 303 described below, and also specifies the input file described below. By linking with the unit 302, the file to be input to the specified workflow is specified. The data generation planning unit 301 inputs the information of these identified workflows and files to the planning management unit 304 as a data generation plan.

The input file specifying unit 302 acquires data (metadata) that characterizes the file from the file metadata management table 114 based on the information of the file input from the data generation planning unit 301.

The execution workflow specifying unit 303 acquires data (metadata) that characterizes the workflow from the workflow metadata management table 117 based on the workflow input from the data generation planning unit 301.

The plan management unit 304 acquires the data generation plan input from the data generation planning unit 301, and transmits the workflow execution request in the data generation plan to the workflow execution device 120. Further, the plan management unit 304 receives a data generation request notification from the plan management unit 304 to the effect that the execution of the workflow is completed, and the execution result of the workflow or the information necessary for accessing the execution result (execution result information). Input to unit 111.

Here, the file metadata management table 114 and the workflow metadata management table 117 will be described.

(File metadata management table)
FIG. 4 is a diagram showing an example of the file metadata management table 114.

File metadata The data management table 114 is a data format that characterizes the data file 150 in terms of format (hereinafter referred to as feature information) and a meta that is information that characterizes the data file 150 in terms of content. I remember the data.

That is, the file metadata management table 114 includes the data ID 501 which is the ID of the data file 150, the data format 502 which is the information of the format (for example, the extension of the file) of the data file 150 related to the data ID 501, and the data ID 501. It is composed of one or more records R521 to R526 having each item of metadata 503, which is information characterizing the contents of the data of the data file 150.

The metadata 503 has a data type 511, which is a type of the contents of the data file 150, and a classification 512 when the contents of the data file 150 are classified according to a predetermined rule. The content of the metadata 503 is characteristic information of the data file 150 that cannot be specified by the information related to the data format 502. For example, the metadata 503 is information obtained by analyzing the header portion R1001 or the body portion R1021 of the data file when the data file 150 is in a binary format.

(Workflow metadata management table)
FIG. 5 is a diagram showing an example of the workflow metadata management table 117. The workflow metadata management table 117 stores each workflow executed in the past or preset by the user and the feature information of each workflow.

The workflow metadata management table 117 is a workflow in which the workflow ID 601 in which the workflow ID is set and the feature information of the data file 150 (hereinafter referred to as input data) input when the workflow related to the workflow ID 601 are executed are set. One or more records R (R631 to R636) having each item including the input 602 and the workflow output 603 in which the characteristic information of the file (hereinafter referred to as output data) output by the execution of the workflow related to the workflow ID 601 is set. ).

The workflow input 602 has a data format 611 in which the format of the input data (for example, an extension) is set, and metadata 612 in which the metadata of the input data is set. The metadata 612 has a type 621 in which the type of metadata of the input data is set, and a classification 622 in which the classification of the metadata of the input data is set.

Further, the workflow output 603 has a data format 613 in which the format of the output data (for example, an extension) is set, and the metadata 614 in which the metadata of the output data is set. The metadata 614 has a type 623 in which the type of metadata of the output data is set, and a classification 624 in which the classification of the metadata of the output data is set.

In addition, 0 or more data are set in each of the workflow input 602 and the workflow output 603.

Next, as shown in FIG. 1, the file metadata extraction unit 113 accepts the input of a plurality of data (data file 150), and each feature of the content of the data file 150 input based on the content of the input data. Is estimated, and a file metadata management table 114 that stores the characteristics of each estimated content in association with each input data file 150 is generated as the first model. Specifically, the file metadata extraction unit 113 estimates the characteristics of the contents of the input data file 150 by extracting the characteristics from the contents of the input data file 150 according to a predetermined rule, that is, a file. The metadata extraction unit 113 extracts the metadata in each data file 150 from each data file 150 stored in the file management server 105 according to the file metadata extraction rule 115 described later, and the extracted metadata (hereinafter referred to as “)”. The file metadata) is stored in the file metadata management table 114.

The workflow metadata extraction unit 116 stores each feature of the content of the input data file 150 in association with the feature and the process of generating result data using the data having the feature of the content. The data management table 117 is generated as the second model. Specifically, the workflow metadata extraction unit 116 accepts input of processing information (workflow) and extracts the characteristics of the data (primary data) handled by the input processing according to a predetermined rule to obtain the result data. Specify the process to generate.

That is, the workflow metadata extraction unit 116 is based on the file metadata management table 114 and the workflow shown by the workflow execution log 104 described later, and according to the workflow metadata extraction rule 118 described later, the metadata in each workflow (hereinafter, workflow). (Metadata) is extracted, and the extracted workflow metadata is stored in the workflow metadata management table 117.

Here, the file metadata extraction rule 115 and the workflow metadata extraction rule 118 will be described.

(File metadata extraction rule)
FIG. 6 is a diagram showing an example of the file metadata extraction rule 115. The file metadata extraction rule 115 stores one or more rules for generating feature information (file metadata management table 114) of the data file 150 from each data file 150 recorded in the file management server 105. doing.

The file metadata extraction rule 115 applies the rule ID 801 which is the identifier of the rule, the data format 802 of the data file 150 to which the rule according to the rule ID 801 can be applied, and the rule according to the rule ID 801 to generate the file metadata. Extraction command 803 (hereinafter also referred to as file metadata extraction command), which is a command (script, program, etc.) for this purpose, and metadata definition, which is information that defines the attributes of the file metadata generated by the command related to the extraction command 803. It comprises one or more records R821-R824 having each item including 804.

The metadata definition 804 has one or more combinations including a key 811 which is information on attributes (types and classifications) of file metadata and a value 812 which is a variable for storing file metadata.

For example, in the record R821, a file metadata extraction command to be executed for a data file 150 having a data format (extension) of "CRAM" is set as an extraction command 803. Then, by executing this extraction command 803, the type information (for example, "Seq.") In the file metadata is set in the variable "v1", and the classification information in the file metadata (for example, "Whole" "mtDNA" is set. ") Is set to the variable" v2 ".

The file metadata extraction command may extract the file metadata from the data header unit R1001 of the data file 150, may be extracted from the data body unit R1021, or may be combined. Further, the file metadata extraction command may use the data obtained by processing the data body portion R1021 as the file metadata. For example, the file metadata performs a predetermined statistical analysis (for example, analysis of differences in the description method of the data model) or syntactic analysis (for example, analysis of statistical bias of words) on the data of the data body unit R1021. Data may be used.

(Workflow metadata extraction rule)
FIG. 7 is a diagram showing an example of the workflow metadata extraction rule 118. The workflow metadata extraction rule 118 stores one or a plurality of rules for generating workflow metadata (workflow metadata management table 117) from each workflow recorded in the workflow execution log 104. In addition, a plurality of rules related to the workflow metadata extraction rule 118 may be applied to one workflow in the workflow execution log 104.

The workflow metadata extraction rule 118 is a command for generating workflow metadata by applying the rule ID 901 which is an identifier of the rule, the step optional description 902 which is the information of the explanation for the rule related to the rule ID 801 and the rule related to the rule ID 801. Each information including the processing command 903 (hereinafter, also referred to as the workflow metadata extraction command) which is (script etc.) and the next step determination 904 which is the rule ID of the rule applied after the command related to the processing command 903 is executed. Have in each record.

For example, the record R911 (rule "WR01") is set with a rule for extracting the metadata of the input data from the input data of the workflow. That is, a workflow metadata extraction command that performs "DataID replacement of input data" in the workflow is set. Further, in the record R912 (rule "WR02"), a rule for extracting the metadata of the output data of the workflow is set. In the record R913 (rule "WR03"), a rule for extracting a workflow ID is set as one of the workflow feature information.

The workflow metadata extraction command executes a process of replacing the data ID included in the workflow input data 703 in the workflow execution log 104 with the data format and metadata of the file metadata management table 114.

The processing command 903 may be different for each workflow in the workflow execution log 104. Further, in the next step determination 904, a rule ID may be simply set, or a conditional expression for differentiating the rules to be applied thereafter may be set according to the execution result of the processing command 903.

--Workflow execution device ---
Next, as shown in FIG. 1, the workflow execution device 120 includes a workflow execution unit 103, a workflow management unit 109, and a workflow execution log 104.

The workflow execution unit 103 executes the data generation plan while using the workflow stored in the workflow management unit 109, which will be described later, and the data file 150 managed by the file management server 105. The workflow execution unit 103 may be incorporated in the workflow execution device 120, may be incorporated in the data generation support device 101, or may be provided in another external information processing device.

The workflow execution log 104 stores a history of processes executed by the workflow execution unit 103. The workflow execution log 104 may be incorporated in the workflow execution device 120, may be incorporated in the data generation support device 101, or may be provided in another external information processing device.

(Workflow execution log)
FIG. 8 is a diagram showing an example of the workflow execution log 104. The workflow execution log 104 is information on workflows executed in the past. The workflow execution log 104 is input when the time stamp 701 in which the date and time or time when the workflow is executed is set, the workflow ID 702 in which the ID of the executed workflow is set, and the workflow related to the workflow ID 702 are executed. One or more records R711 to R714 having each item including input data 703 in which data (data file 150) is set and output data 704 in which data output by executing a workflow related to workflow ID 702 are set. Be prepared.

Zero or more pieces of information are set in the input data 703 and the output data 704, respectively.

Next, FIG. 9 shows the hardware configuration of each information processing device (user terminal 102, data generation support device 101, workflow execution device 120, file management server 105, and management console 107) in the data generation support system 1. It is a figure which shows an example. Each information processing device includes a calculation device 201 such as a CPU, a main memory 202 such as a RAM (Random Access Memory) or a ROM (Read Only Memory) in which programs and data are developed, and an HDD (Hard Disk Drive). An auxiliary storage device 203 such as an SSD (Solid State Drive) or a flash memory, a communication interface 204 such as a network interface card that communicates with another information processing device, and a media interface 205 to which an external storage medium 207 is connected. It includes an input device such as a keyboard or a touch panel and an input / output device 206 including an output device such as a monitor or a display, and these are connected to each other by a bus or the like. The external storage medium 207 is, for example, a communication medium (that is, a network such as wired, wireless, optical, etc., or a carrier wave or digital signal propagating in the network), or a medium that can be attached to and detached from the media interface 205. The data generation support device 101 is connected to the management console 107 via the input / output device 206.

Each function of each information processing device described so far is realized by dedicated hardware or by reading and executing a program stored in the main memory 202 or the auxiliary storage device 203 by the arithmetic unit 201. .. Further, each program may be recorded in advance on the external storage medium 207, or may be introduced when necessary via a predetermined communication network.

-Processing-
Next, the processing performed in the data generation support system 1 will be described.

In the data generation support system 1, (1) a data generation support process that generates result data in response to a user's request, and (2) a file that generates a file metadata management table 114 necessary for executing the data generation support process. The metadata management table generation process and (3) the workflow metadata management table generation process for generating the workflow metadata management table 117 necessary for executing the data generation support process are executed.

It should be noted that, typically, (2) and (3) need to be executed before executing (1). Further, since the file metadata management table 114 is required to generate the workflow metadata management table 117, (2) is executed before the execution of (3).

Hereinafter, each of these processes will be described.

--Data generation support processing ---
FIG. 10 is a flow chart illustrating an example of data generation support processing. The data generation support process is executed, for example, when the data generation support device 101 is activated.

First, the data generation request receiving unit 111 of the data generation support device 101 waits for the reception of the data generation request 108 from the user terminal 102 (S1101). When the data generation request receiving unit 111 receives the data generation request 108, the data generation request receiving unit 111 inputs the received data generation request 108 to the data generation planning unit 301 of the data generation management unit 112 (S1101).

Here, the data generation request 108 will be described.

(Data generation request)
FIG. 11 is a diagram showing an example of the data generation request 108. The data generation request 108 includes request data designation information 401 which is information for specifying secondary data (result data) and usage workflow ID 402 which is an ID of a workflow for generating result data (hereinafter referred to as designated WF). Have.

The request data designation information 401 is information estimated from the attribute information of the primary data. The request data designation information 401 is, for example, an identifier registered in a catalog site that provides only information on the presence / absence of primary data (details of the primary data are unknown). If the primary data is genomic data, the attribute information of the primary data is, for example, the gender, disease status, or racial or ethnic background information of a person estimated from the genomic data. Such attribute information may be generated by external information such as an electronic medical record of a medical institution. When attribute information is used, a plurality of request data designation information 401 may be specified from the attribute information. In such a case, a plurality of pieces of information are set in the request data designation information 401.

Next, as shown in FIG. 10, the data generation planning unit 301 inputs the data designation information (hereinafter referred to as designated data) in the data generation request 108 received in S1101 to the input file identification unit 302 (S1111).

Specifically, the data generation planning unit 301 inputs the request data designation information 401 out of the input data generation request 108 to the input file identification unit 302.

Then, the input file specifying unit 302 acquires the feature information (data format and metadata (S1112) of the designated data.

Specifically, the input file specifying unit 302 identifies from the file metadata management table 114 a record in which the request data specification information 401 has the same contents as the request data specification information 401 set in the request data specification information 401. , Acquire the contents of the data format 502 and the metadata 503 of the specified record.

The data generation planning unit 301 inputs the designated WF together with the feature information of the designated data to the execution workflow specifying unit 303 (S1121).

Specifically, the data generation planning unit 301 inputs the data format 502 and the metadata 503 acquired in S1112 and the usage workflow ID 402 in the data generation request 108 received in S1101 to the execution workflow specifying unit 303.

The execution workflow specifying unit 303 acquires the workflow indicated by the designated WF from the workflow metadata management table 117 (S1122).

Specifically, the execution workflow specifying unit 303 identifies a record in which the ID having the same content as the usage workflow ID 402 input in S1121 is set in the workflow ID 601 from the workflow metadata management table 117, and identifies the specified record. get.

Further, the execution workflow specifying unit 303 acquires the feature information of the input data of the workflow indicated by the designated WF (S1123).

Specifically, the execution workflow specifying unit 303 acquires the workflow input 602 (data format 611 and metadata 612) of the record acquired in S1122.

The execution workflow specifying unit 303 uses data having the same characteristic information as the designated data as input data, and data having the same characteristic information as the input data of the workflow indicated by the designated data as output data (hereinafter referred to as execution WF). Specify (S1124).

Specifically, in the execution workflow specifying unit 303, the data format 502 and the metadata 503 acquired in S1112 are set in the workflow input 602 from the workflow metadata management table 117, and the workflow input 602 acquired in S1123 (data format 611). And the metadata 612) acquires the record set in the workflow output 603, and specifies the workflow ID 601 of the acquired record.

The data generation planning unit 301 inputs information for specifying the execution WF to the planning management unit 304 together with the designated data (S1131).

Specifically, the data generation planning unit 301 inputs the request data designation information 401 of the data generation request 108 received in S1101 and the workflow ID 601 specified in S1124 to the planning management unit 304.

The plan management unit 304 transmits the input designated data and information including information specifying the execution WF to the workflow execution device 120 as a data generation plan, and waits for the execution WF to be completed by the workflow execution device 120. Then, the plan management unit 304 waits until the completion notification to the effect that the execution of the execution WF is completed is received from the workflow execution device 120 (S1141).

The plan management unit 304 receives the result data output by the execution WF or information for accessing the result data (execution result information) together with the completion notification from the workflow execution device 120. The plan management unit 304 transmits the received execution result information to the data generation request reception unit 111.

After that, the data generation request receiving unit 111 transmits the received execution result information to the user terminal 102, and the user terminal 102 displays the content of the result data on the screen based on the received execution result information.

This completes the data generation support process.

(Workflow specific screen)
Here, FIG. 12 is a diagram showing an example of a screen (workflow specific screen) displayed by the data generation support device 101 when the execution WF is discovered in S1124. The workflow specification screen 160 displays information 161 indicating that the execution WF has been specified. Information on the name and ID of the execution WF, and information on the specific contents of the primary data used by the execution WF may be displayed.

Further, the workflow specifying screen 160 may display information 162 indicating that the workflow execution device 120 is generating secondary data or result data by the specified execution WF.

Next, the file metadata management table generation process will be described.

--File metadata management table generation process ---
FIG. 13 is a flow chart illustrating an example of a file metadata management table generation process. The file metadata management table generation process can be executed independently of the data generation support process. For example, when a predetermined input is received from the management console 107, a predetermined timing (for example, a predetermined date and time or a predetermined time interval) Is executed, or when a new data file 150 is registered in the file management server 105.

First, the file metadata extraction unit 113 of the data generation support device 101 refers to the file management server 105 and acquires a list of each data file 150 in the file metadata management table 114 (S1201).

The file metadata extraction unit 113 selects one data file 150 from the list of data files 150 acquired in S1201 (hereinafter referred to as a selection file) (S1211), and stores the selected data file 150 (path or URL). ) Is specified (S1212).

Then, the file metadata extraction unit 113 acquires the extension of the selected file in the specified storage location (S1212).

The file metadata extraction unit 113 specifies all the rules applicable to the extension of the selected file acquired in S1212 from the file metadata extraction rule 115 (S1213).

Specifically, the file metadata extraction unit 113 extracts all the records whose extension is set to the data format 802 acquired in S1212 from the file metadata extraction rule 115.

The file metadata extraction unit 113 selects one of the rules extracted in S1213 (hereinafter referred to as a selection rule) (S1221). Specifically, the file metadata extraction unit 113 acquires one of the records extracted in S1213.

The file metadata extraction unit 113 acquires the feature information of the output data of the selection file by executing the file metadata extraction command for applying the selection rule.

Specifically, the file metadata extraction unit 113 acquires the record extraction command 803 acquired in S1221 and executes the acquired command. Then, the file metadata extraction unit 113 acquires data having the configuration indicated by the metadata definition 804 of the same record (data having the configuration and contents indicated by the key 811 and the value 812) as the output data.

The file metadata extraction unit 113 determines whether or not the file metadata extraction command has acquired the feature information of the output data (S1223).

If the file metadata extraction command can acquire the feature information of the output data (S1223: YES), the file metadata extraction unit 113 executes the process of S1214 described below, and the file metadata extraction command is the output data. If the feature information could not be acquired (S1223: NO), the file metadata extraction unit 113 executes the process of S1224 described later.

In S1214, the file metadata extraction unit 113 registers the feature information acquired by the file metadata extraction command in the file metadata management table 114.

Specifically, the file metadata extraction unit 113 creates a new record in the file metadata management table 114, sets the extension acquired in S1212 to the data format 502 of the record, and the metadata of the record. The data (metadata) acquired in S1222 is set in 503.

The file metadata extraction unit 113 repeats the processing after S1211 until all the data files 150 in the list acquired in S1201 are selected in order to select a new selection file (S1215). When all the data files 150 are selected, the file metadata extraction unit 113 ends the file metadata management table generation process.

In S1224, the file metadata extraction unit 113 repeats the processing after S1221 until all the rules specified in S1213 are selected in order to select a new selection rule.

Next, the workflow metadata management table generation process will be described.

--Workflow metadata management table generation process ---
FIG. 14 is a flow chart illustrating an example of the workflow metadata management table generation process. The workflow metadata management table generation process can be executed independently of the data generation support process. For example, when a predetermined input is received from the management console 107, a predetermined timing (for example, a predetermined date and time or a predetermined time interval). Is executed, or when workflow data is newly registered in the workflow execution log 104.

Here, the workflow metadata management table generation process extracts the characteristic information of the workflow input / output file based on the three rules (WR01, WR02, WR03) of the workflow metadata extraction rule 118 shown in FIG. And.

First, the workflow metadata extraction unit 116 reads the workflow execution log 104 (S1301) and selects one of those workflows (hereinafter referred to as selection WF) (S1311). Specifically, the workflow metadata extraction unit 116 selects one record from the workflow execution log 104.

The workflow metadata extraction unit 116 executes a workflow metadata extraction command that is the first rule for the selection WF and applies a rule (WR01) for extracting the feature information of the input data. (S1312). Specifically, the workflow metadata extraction unit 116 acquires the processing command 903 of the record R911 at the beginning of the workflow metadata extraction rule 118, and executes the acquired processing command 903.

The workflow metadata extraction unit 116 estimates the feature information of the input data by executing the workflow metadata extraction command in S1312 (S1321).

Specifically, the workflow metadata extraction unit 116 acquires the input data 703 of the record related to the selection WF in the workflow execution log 104, and the same content as the content of the acquired input data 703 is set in the data ID 501. The record R911 of the file metadata management table 114 is specified, and the contents of the data format 502 and the metadata 503 of the specified record R911 are acquired.

The workflow metadata extraction unit 116 executes a workflow metadata extraction command to which the next rule for the selected WF and the rule (WR02) for extracting the feature information of the output data is applied (S1313).

Specifically, the workflow metadata extraction unit 116 identifies the record R912 in which the content of the next step determination 904 of the record R911 selected in S1311 is set in the rule ID 901, and acquires the processing command 903 of the specified record R912. Then, the acquired processing command 903 is executed.

The workflow metadata extraction unit 116 estimates the feature information of the output data by executing the workflow metadata extraction command in S1313 (S1331).

Specifically, the workflow metadata extraction unit 116 acquires the output data 704 of the record related to the selected WF in the workflow execution log 104, and the same content as the content of the acquired output data 704 is set in the data ID 501. The record R912 of the file metadata management table 114 is specified, and the data format 502 and the metadata 503 of the specified record R912 are acquired.

The workflow metadata extraction unit 116 executes a workflow metadata extraction command to which the next rule for the selected WF and the rule (WR03) for extracting the characteristic information of the workflow type is applied (S1314).

Specifically, the workflow metadata extraction unit 116 identifies the record R913 in which the content of the next step determination 904 of the record R912 related to the selection WF in the workflow execution log 104 is set in the rule ID 901, and the specified record R913. The processing command 903 is acquired, and the acquired processing command 903 is executed.

The workflow metadata extraction unit 116 estimates the characteristic information of the workflow type by executing the workflow metadata extraction command in S1314 (S1341).

Specifically, the workflow metadata extraction unit 116 acquires the workflow ID 702 of the record R913 of the workflow execution log 104 selected in S1312.

Here, the workflow metadata extraction unit 116 confirms that there is no further next processing command in the selection WF because the information is not set in the next step determination 904 in the record R913 of the workflow metadata extraction rule 118.

Then, the workflow metadata extraction unit 116 registers the selected WF and each feature information for the selected WF in the workflow metadata management table 117 (S1315).

Specifically, the workflow metadata extraction unit 116 sets the contents of the workflow ID 702 acquired in S1341 in the workflow ID 601 of the workflow metadata management table 117, and sets the contents of the data format 502 acquired in S1321 to the workflow metadata. The data format 611 in the workflow input 602 of the management table 117 is set, and the content of the metadata 503 acquired in S1321 is set in the metadata 612 (type 621 and classification 622) in the workflow input 602 of the workflow metadata management table 117. , The content of the data format 502 acquired in S1331 is set in the data format 613 in the workflow output 603 of the workflow metadata management table 117, and the content of the metadata 503 acquired in S1331 is set to the workflow output of the workflow metadata management table 117. It is set in the metadata 614 (type 623 and classification 624) in 603.

The workflow metadata extraction unit 116 selects a workflow that has not been selected as the selection WF in the workflow execution log 104 as the new selection WF, and repeats the processing after S1312 (S1316). The workflow metadata extraction unit 116 ends the workflow metadata management table generation process when all workflows are selected.

In this way, the workflow metadata management table generation process applies all the rules for the workflow to be processed (all rules specified by the workflow metadata extraction rule 118) to the workflow, so that the characteristic information (data format) of the workflow is applied. , Metadata, workflow ID), and the estimated feature information is registered in the workflow metadata management table 117.

As described above, the data generation support system 1 of the present embodiment receives the data generation request 108 for requesting the generation of the result data, and receives the characteristic information (metadata such as type and classification) of the secondary data. A workflow that is estimated by the file metadata management table 114 and can generate result data from data (primary data) having the estimated feature information is specified by the workflow metadata management table 117. As a result, even if the data required to generate the result data (primary data including sensitive information corresponding to the secondary data) cannot be specified, the data generation request 108 requests by using the metadata. The workflow for generating outcome data can be specified on demand.

In particular, by using metadata, it is possible to generate desired data on demand in response to a user's data request without comprehensively preparing necessary data in advance. That is, if the data must be comprehensively generated in advance, not only the resource consumption by the data itself but also the resource consumption for the association between the data will be consumed, so that the data can be enormous. The data generation support system 1 of the embodiment does not require such resources and can reduce the data management cost.

As described above, according to the data generation support system 1 of the present embodiment, even when the information necessary for generating the data is lacking, the data can be generated.

[Example 2]
The data generation support system of the second embodiment is a system applied when processing by a plurality of workflows is required in order to generate result data (secondary data, etc.) from the primary data.

-System configuration-
FIG. 15 is a diagram showing a part of a configuration example in the data generation support system 2 according to the second embodiment. The parts with the same reference numerals as those in the first embodiment have the same configurations and functions as those in the first embodiment. Further, the part not shown in the figure is assumed to have the same configuration and function as in the first embodiment.

That is, the data generation support system 2 of this embodiment includes a consolidated workflow calculation unit 1401 and a workflow plan management table 1402 in addition to the configuration of the data generation support system 1 of the first embodiment.

The concatenated workflow calculation unit 1401 outputs the characteristics (metadata) of the contents of the data input to each workflow in the second model (workflow metadata management table 117) generated by the workflow metadata extraction unit 116 and each workflow. By comparing with the characteristics (metadata) of the data contents, the execution order of the multiple outcome data that generates the outcome data (secondary data, etc.) from the primary data is specified, and the execution of the specified multiple outcome data. The order is generated as a third model (workflow plan management table 1402).

That is, the consolidated workflow calculation unit 1401 uses the workflow metadata management table 117 to provide information including a combination of primary data and secondary data that can be generated by concatenating a plurality of workflows and a configuration of the plurality of workflows. (Hereinafter referred to as workflow plan) is generated, and the generated plan is stored in the workflow plan management table 1402.

In this case, the data generation management unit 112 uses the workflow plan management table 1402 to specify the execution order of a plurality of workflows from which result data can be generated from the primary data, based on the third model (workflow plan management table 1402). It is a table which manages the workflow plan generated by the consolidated workflow calculation unit 1401. The workflow plan management table 1402 stores a workflow plan including execution of a plurality of workflows and a configuration for executing one workflow similar to the workflow metadata management table 117 in the first embodiment.

In the first embodiment, the workflow metadata management table 117 accepts the acquisition of the characteristic information (metadata) of the input / output data from the execution workflow specific unit 303 as a query, and returns the characteristic information for the query to the execution workflow specific unit 303. However, in the second embodiment, the workflow plan management table 1402 accepts a query from the execution workflow specifying unit 303.

(Workflow plan management table)
FIG. 16 is a diagram showing an example of the workflow plan management table 1402.

The workflow plan management table 1402 is characterized by a plan ID 1501 which is an ID of the workflow plan, a start workflow ID 1502 which is an ID of the workflow to be executed first in the workflow plan related to the plan ID 1501, and input data of the workflow related to the start workflow ID 1502. Each item includes a workflow input 1503 which is information, a consolidated workflow ID list 1504 which is a list of IDs of workflows executed after the second, and a workflow output 1505 which is characteristic information of output data of the workflow executed last. It is provided with one or more records R (R1531 to R1533) having a workflow.

The workflow input 1503 includes items of a data format 1511 (extension, etc.) which is a format of input data of the workflow, and a metadata 1512 which is a metadata of the input data of the workflow, and the metadata 1512 is further input. It has each item of data type 1521 and classification 1522.

The workflow output 1505 includes items of a data format 1513 (extension, etc.) which is a format of the output data of the workflow, and a metadata 1514 which is a metadata of the output data of the workflow, and the metadata 1514 is further output. It has each item of data type 1523 and classification 1524.

The start workflow ID 1502, the workflow input 1503, and the workflow output 1505 are items in which the same types of information as the workflow ID 601, the workflow input 602, and the workflow output 603 of the workflow metadata management table 117 are set, respectively.

--Workflow plan management table generation process ---
FIG. 17 is a flow chart illustrating an example of the workflow plan management table generation process. The workflow plan management table generation process can be executed independently of the data generation support process. For example, when a predetermined input is received from the management console 107, a predetermined timing (for example, a predetermined date and time or a predetermined time interval) is set. It is executed when it arrives or when the workflow data is newly registered in the workflow execution log 104.

First, the connection workflow calculation unit 1401 of the data generation support device 101 acquires all the contents of each workflow in the workflow metadata management table 117 (S1601). Specifically, the consolidated workflow calculation unit 1401 acquires all the records of the workflow metadata management table 117.

The consolidated workflow calculation unit 1401 selects the workflow (hereinafter referred to as a selection flow) registered first among the workflows that have not been selected so far among the workflows acquired in S1601 (S1611). Specifically, for example, the concatenation workflow calculation unit 1401 acquires the first record among the records that have not been selected so far from the records acquired in S1601. Then, the consolidated workflow calculation unit 1401 sets the workflow ID 601 of the acquired record in the start workflow ID 1502 of the new record generated in the workflow plan management table 1402.

The concatenated workflow calculation unit 1401 determines whether or not there is output data in the selection flow (S1621). Specifically, the consolidated workflow calculation unit 1401 determines whether or not data is registered in the workflow output 603 of the record acquired in S1611.

If there is output data in the selection flow (S1621: YES), the concatenation workflow calculation unit 1401 executes S1622 described below, and if there is no output data in the selection flow (S1621: NO), the concatenation workflow calculation unit 1401 Does not set the data about the selection flow in the workflow plan management table 1402. After that, the connection workflow calculation unit 1401 repeats the process of S1646 described later.

In S1622, when the characteristic information of the output data of a certain workflow and the characteristic information of the input data of another workflow match, the consolidated workflow calculation unit 1401 sets the former as a parent node (workflow) and the latter as its child node (workflow). By repeating the node search to be performed starting from the selection flow, the flow of each node (workflow) in a series is stored as a path.

Specifically, for example, the consolidated workflow calculation unit 1401 searches the workflow metadata management table 117 using the workflow output 603 of the record acquired in S1611 as a key, and the record whose key content is set in the workflow input 1503. To get. Hereinafter, the connection workflow calculation unit 1401 repeats the same processing.

In the consolidated workflow calculation unit 1401, the characteristic information of the input node of the first workflow and the output node of the last workflow is the same workflow (workflow in which processing loops. For example, the difference in input / output data is the difference between upper and lower case). A series of workflows that exist and there is virtually no difference in the data content between input and output.) Are excluded from the node search.

The concatenated workflow calculation unit 1401 selects one of the paths specified in S1622 (hereinafter referred to as a selection path) (S1631).

The concatenated workflow calculation unit 1401 orders each node in the selection path as a child node for the parent node, a child node for the child node, and so on, until the child node no longer exists (S1643: NO). The information of each ordered node is set in the workflow plan management table 1402 (S1641 to S1645).

Specifically, for example, the consolidated workflow calculation unit 1401 sets the workflow ID 601 of the record related to each ordered node (any record of the workflow metadata management table 117) to the consolidated workflow ID list 1504 of the workflow plan management table 1402. Store in each.

The concatenated workflow calculation unit 1401 executes the processing for each of the above nodes for all paths (S1646). Further, the consolidated workflow calculation unit 1401 executes the processing for each of the above paths for all the records (all workflows) in the workflow metadata management table (S1647).

As described above, according to the data generation support system 2 of this embodiment, when processing by a plurality of workflows is required to generate secondary data from the primary data, the workflow plan management table 1402 is used. A path for executing multiple workflows can be generated, and secondary data and result data can be generated by this path.

The content of the present invention described above is not limited to the above-described embodiment, and includes various modifications. The above-mentioned examples have been described in detail for a better understanding of the present invention, and are not necessarily limited to those having all the configurations of the description.

For example, in the present embodiment, the control line and the information line show what is considered necessary for explanation, and do not necessarily show all the control line and the information line in the product. In practice, it can be considered that almost all configurations are interconnected.

Further, a part or all of the functions provided in one information processing device may be provided in another information processing device.

Further, the data format used in this embodiment may be not only the file extension but also other formal information such as the file generation date or time, the file size, and the file creator.

In addition, although genetic information is taken up as confidential data in this embodiment, any other data may be used as long as it is data that should be kept secret by a predetermined individual or organization.

Further, in the present embodiment, the type and classification of data are taken up as an example of the metadata that characterizes the content of a certain data, but other types of data may be used. The metadata may be information of attributes that the primary data (confidential data) and the result data (secondary data, etc.) generated from the primary data have in common.

Further, in the present embodiment, the file metadata extraction rule 115 and the workflow metadata extraction rule 118 are used to generate the file metadata and the workflow metadata, respectively, but other information may be used. For example, machine learning (eg, decision tree or deep) using data files and features related to the workflow, respectively, regarding the relationship between the contents of the data file and the file metadata, and the relationship between the input / output data of the workflow and the workflow metadata, respectively. It may be determined by generating a trained model generated by (learning by learning).

The above description of the present specification clarifies at least the following. That is, in the data generation support device 101 of the present embodiment, the arithmetic device receives input of a plurality of data, estimates each feature of the content of the input data based on the input data, and estimates each. The first model generation process for generating the file metadata management table stored in association with the characteristics of the contents and the input data may be executed as the first model.

In this way, by estimating each feature of the contents of the plurality of data and generating the file metadata management table 114 that stores the features of each content in association with each of the above data, the contents of the target data are included. Features (metadata) can be identified accurately.

Further, in the data generation support device 101 of the present embodiment, the arithmetic unit is input by extracting the features of the contents from the input data according to a predetermined rule in the first model generation process. It may be possible to estimate the characteristics of the contents of the collected data.

In this way, by extracting the characteristics of the data contents from the input data according to a predetermined rule (file metadata extraction rule 115), the characteristics (metadata) of the data contents can be uniformly extracted.

Further, in the data generation support device 101 of the present embodiment, the arithmetic unit uses the characteristics of the contents and the data having the characteristics of the contents to determine the characteristics of each content of the input data. The second model generation process of generating the workflow metadata management table stored in association with the process of generating data as the second model may be executed.

In this way, by generating the workflow metadata management table 117 that associates the characteristics of each content of the data with the workflow that generates the result data using the primary data having the characteristics of the contents, the content of the workflow Features (metadata) can be accurately identified.

Further, in the data generation support device 101 of the present embodiment, the arithmetic unit accepts input of processing information in the second model generation process, and determines the characteristics of the content of the data handled by the input process as a predetermined rule. By extracting according to the above, a plurality of processes for generating the predetermined data may be specified.

In this way, by extracting the characteristics (file metadata) of the data contents handled by the input workflow according to a predetermined rule (workflow metadata extraction rule 118), the characteristics of the workflow contents (workflow metadata) are unified. Can be extracted as a workflow.

Further, in the data generation support device 101 of the present embodiment, the arithmetic device has the characteristics of the content of the data input to each of the processes in the generated second model and the characteristics of the content of the data output by each process. By comparing with and, the execution order of the plurality of processes that generate the second data from the first data is specified, and the execution order of the specified plurality of processes is generated as the third model. In the data generation management process, the execution order of a plurality of processes in which the predetermined data can be generated may be specified by the other data based on the third model.

In this way, the characteristics (metadata) of the content of the data input to each workflow in the second model (workflow metadata management table 117) are compared with the characteristics (metadata) of the content of the data output by the workflow. By specifying the execution order of the plurality of processes for generating the result data (for example, secondary data) from the primary data, and generating the execution order as the third model (workflow plan management table 1402), the result is obtained. You can identify multiple workflows that generate data. This makes it possible to reliably generate secondary data or result data even when the workflow for generating result data (secondary data or the like) from the primary data is complicated.

Further, in the data generation support device 101 of the present embodiment, the arithmetic unit generates information indicating that the process in which the predetermined data can be generated is specified in the data generation management process, or the predetermined data is generated. Information indicating that the predetermined data is being generated may be displayed based on possible processing.

In this way, by displaying the information indicating that the workflow in which the result data (secondary data) can be generated is specified and the information indicating that the result data (secondary data) is being generated based on the workflow. , The user can confirm that the result data (secondary data, etc.) can be generated from the primary data.

Further, in the present embodiment, the information processing apparatus estimates and estimates the data generation request acceptance process for receiving the request information requesting the generation of predetermined data and the characteristics of the content of the predetermined data by the first model. The process in which the predetermined data can be generated by other data having the content of the feature may be executed with the data generation management process specified by the second model.

Further, in the present embodiment, the information processing apparatus receives input of a plurality of data, estimates each feature of the content of the input data based on the input data, and the feature of each estimated content and the said. The first model generation process for generating the file metadata management table stored in association with each input data as the first model may be executed.

Further, in the present embodiment, the information processing apparatus extracts the features of the contents from the input data according to a predetermined rule in the first model generation process, so that the features of the contents of the input data are characterized. May be estimated.

Further, in the present embodiment, the information processing apparatus generates the predetermined data for the characteristics of each content of the input data by using the characteristics of the contents and the data having the characteristics of the contents. The second model generation process for generating the workflow metadata management table stored in association with the second model may be executed.

Further, in the present embodiment, the information processing apparatus receives input of processing information in the second model generation processing, and extracts the characteristics of the contents of the data handled by the input processing according to a predetermined rule. The process of generating the predetermined data may be specified.

Further, in the present embodiment, the information processing apparatus compares the characteristics of the content of the data input to each of the processes in the generated second model with the characteristics of the content of the data output by each process. , The execution order of the plurality of processes for generating the second data is specified from the first data, and the consolidated workflow calculation process for generating the execution order of the specified plurality of processes as the third model is executed, and the data generation is performed. In the management process, the execution order of a plurality of processes in which the predetermined data can be generated may be specified by the other data based on the third model.

Further, in the present embodiment, the information processing apparatus identifies the process in which the predetermined data can be generated in the data generation management process, or the process based on the process in which the predetermined data can be generated. Information indicating that predetermined data is being generated may be displayed.

Further, in the present embodiment, the characteristics of the user terminal for transmitting the request information requesting the generation of predetermined data, the data generation request acceptance process for receiving the request information, and the content of the predetermined data are first. A data generation management process is executed to specify the process in which the predetermined data can be generated by other data stored in the predetermined information processing apparatus, which is estimated by the model and has the contents of the estimated features, by the second model. The predetermined information processing device is configured to include the data generation support device, and the predetermined information processing device stores the other data and prohibits the user terminal from accessing the other data. It may be a generation support system.

In this way, the predetermined information processing device (file management server 105) stores the primary data and prohibits the user terminal 102 from accessing the primary data, so that the file management server 105 is an individual. Even if confidential information such as information is stored, the result data can be generated without being known to the user who wants to generate the result data.

1 data generation support system, 101 data generation support device, 102 user terminal, 12
0 Workflow executor, 105 file management server, 108 data generation request, 2
Data generation support system

Claims (15)

Data generation request acceptance processing to receive request information requesting the generation of predetermined data,
A data generation management process for estimating the characteristics of the contents of the predetermined data by the first model and specifying a process in which the predetermined data can be generated by other data having the contents of the estimated features by the second model.
Equipped with an arithmetic unit to execute
Data generation support device. The arithmetic unit is
A file that accepts input of multiple data, estimates each feature of the content of the input data based on the input data, and stores the feature of each estimated content in association with each input data. Execute the first model generation process for generating the metadata management table as the first model.
The data generation support device according to claim 1. The arithmetic unit is used in the first model generation process.
By extracting the characteristics of the contents from the input data according to a predetermined rule, the characteristics of the contents of the input data are estimated.
The data generation support device according to claim 2. The arithmetic unit is
The workflow metadata management table is stored in which the characteristics of each content of the input data are stored in association with the characteristics of the content and the process of generating the predetermined data using the data having the characteristics of the content. Execute the second model generation process to be generated as the second model,
The data generation support device according to claim 1. The arithmetic unit is used in the second model generation process.
By accepting the input of processing information and extracting the characteristics of the content of the data handled by the input processing according to a predetermined rule, a plurality of processes that generate the predetermined data are specified.
The data generation support device according to claim 4. The arithmetic unit is
The second data is generated from the first data by comparing the characteristics of the contents of the data input to each of the processes in the generated second model with the characteristics of the contents of the data output by each of the processes. Specify the execution order of multiple processes and execute the consolidated workflow calculation process to generate the execution order of the specified multiple processes as the third model.
In the data generation management process, based on the third model, the execution order of a plurality of processes in which the predetermined data can be generated by the other data is specified.
The data generation support device according to claim 4. The arithmetic unit is
In the data generation management process, information indicating that the process in which the predetermined data can be generated is specified, or information indicating that the predetermined data is being generated based on the process in which the predetermined data can be generated. indicate,
The data generation support device according to claim 2. Information processing equipment
Data generation request acceptance processing to receive request information requesting the generation of predetermined data,
A data generation management process for estimating the characteristics of the contents of the predetermined data by the first model and specifying a process in which the predetermined data can be generated by other data having the contents of the estimated features by the second model.
Data generation support method to execute. The information processing device
A file that accepts input of multiple data, estimates each feature of the content of the input data based on the input data, and stores the feature of each estimated content in association with each input data. Execute the first model generation process for generating the metadata management table as the first model.
The data generation support method according to claim 8. In the first model generation process, the information processing apparatus
By extracting the characteristics of the contents from the input data according to a predetermined rule, the characteristics of the contents of the input data are estimated.
The data generation support method according to claim 8. The information processing device
The workflow metadata management table is stored in which the characteristics of each content of the input data are stored in association with the characteristics of the content and the process of generating the predetermined data using the data having the characteristics of the content. Execute the second model generation process to be generated as the second model,
The data generation support method according to claim 10. In the second model generation process, the information processing apparatus
By accepting the input of processing information and extracting the characteristics of the content of the data handled by the input processing according to a predetermined rule, the processing for generating the predetermined data is specified.
The data generation support method according to claim 8. The information processing device
The second data is generated from the first data by comparing the characteristics of the contents of the data input to each of the processes in the generated second model with the characteristics of the contents of the data output by each of the processes. Specify the execution order of multiple processes and execute the consolidated workflow calculation process to generate the execution order of the specified multiple processes as the third model.
In the data generation management process, based on the third model, the execution order of a plurality of processes in which the predetermined data can be generated by the other data is specified.
The data generation support method according to claim 12. The information processing device
In the data generation management process, information indicating that the process in which the predetermined data can be generated is specified, or information indicating that the predetermined data is being generated based on the process in which the predetermined data can be generated. indicate,
The data generation support method according to claim 8. A user terminal that sends request information requesting the generation of predetermined data, and
Data generation request acceptance processing to receive the request information, and
A process in which the characteristics of the contents of the predetermined data are estimated by the first model and the predetermined data can be generated by other data stored in the predetermined information processing apparatus, which has the contents of the estimated characteristics, is the first. It is configured to include a data generation support device that executes data generation management processing specified by two models.
The predetermined information processing device stores the other data and prohibits the user terminal from accessing the other data.
Data generation support system.

Images