Data management system and data management method

Abstract

To provide a technique relating to a data monitoring system which allows data in various formats to be stored and easily searched.SOLUTION: One of representative data management systems of the present invention is a data management system (200) which allows pieces of input data (201 and 202) different in data definition to be stored, and the data management system comprises: a data conversion interface (204) which converts the input data to a dataset (205) consisting of structured data (208) provided with a designated data structure and non-structured data information (209); and a NoSQL database (207) which stores therein the dataset and can operate the dataset.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a data management system and a data management method.

Background Art

[0002] In a data management system, various data are organized in a certain format and stored in a database. Therefore, the data stored in the database can be searched, and the necessary data can be retrieved when needed. In addition, in order to improve the searchability of data, for example, in addition to data in a file format that combines audio and video, metadata describing the contents of the file is also attached. By attaching such metadata, it is also possible to efficiently classify, search, and organize files.

[0003] In order to efficiently handle such metadata and files, for example, in Patent Document 1, it is disclosed that "a transmission system includes transmission equipment that transmits an audio / video file and a metadata file via a microwave line, and reception equipment that receives the microwave line. The transmission equipment has a first file transmission device that generates a transmission file from the audio / video file and the metadata file. The reception equipment has an FPU reception device that receives the microwave line and outputs a received file, and a second file transmission device that separates the audio / video file and the metadata file from the received file."

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in Patent Document 1, it is premised that the formats of the data handled by the transmission equipment and the receiving device are based on a certain format. Therefore, the cases of handling data in various formats are not fully assumed. The definition of the metadata to be assigned, that is, the data structure, is determined in advance, and for data different from the determined data structure of the metadata, it was necessary to newly develop software for converting the input data into the determined data structure. In addition, since the data stored in the database is the data obtained by converting the input data, rather than the input data itself, there is a problem that it is difficult to confirm the content of the input data when the accuracy of the conversion, that is, quantization, is inappropriate.

[0006] Therefore, an object of the present invention is to provide a technology related to a data monitoring system that can store data in various formats and can be easily searched.

Means for Solving the Problems

[0007] In order to solve the above problems, one of the typical data management systems of the present invention is a data management system capable of storing input data with different data definitions, and converts the input data into a data set composed of structured data having a specified data structure and unstructured data information. It includes a data conversion interface and a NoSQL database that stores the data set and can operate on the data set.

Effects of the Invention

[0008] According to the present invention, it is possible to provide a technology related to a data monitoring system that can store data in various formats and can be easily searched. Problems, configurations, and effects other than those described above will be clarified by the description in the following embodiments for carrying out the invention.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

MODE FOR CARRYING OUT THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the present invention is not limited by this embodiment. Also, in the description of the drawings, the same parts are denoted by the same reference numerals. When there are a plurality of components having the same or similar functions, they may be described with the same reference numeral and different subscripts. Also, when it is not necessary to distinguish these plurality of components, the subscripts may be omitted in the description. Also, terms such as "first", "second", "third", etc. may be used in the present disclosure to describe various elements or components, but it will be understood that these elements or components should not be limited by these terms. These terms are used only to distinguish one element or component from another. Therefore, the first element or component discussed below can also be referred to as the second element or component without departing from the teachings of the inventive concept. The positions, sizes, shapes, ranges, etc. of the respective components shown in the drawings may not represent the actual positions, sizes, shapes, ranges, etc. in order to facilitate understanding of the invention. For this reason, the present invention is not necessarily limited to the positions, sizes, shapes, ranges, etc. disclosed in the drawings.

[0011] In the present disclosure, the "data definition" is a concept referring to the structure of input data, and means the structure of the form for storing data and the attributes included in the data content. In addition, "structured data" means data that has been formatted to have a certain defined structure, and "unstructured data" means data that is often not in a unified format and is stored in its original form, and in many cases, means data handled in a file format. In addition, "unstructured data information" means the unstructured data itself, or information indicating the storage location where the unstructured data is stored, or information indicating that it is empty data. In addition, "dataset" means data in which a plurality of data are combined and can be handled as a set of data. In the present disclosure, a pair of "structured data" and "unstructured data information" is referred to as a dataset. In addition, "relational database" means a database designed and developed based on the relational model, which manages data in a plurality of tables composed of rows (records) and columns (attributes), and can handle the relevance of data by defining the relationship between tables. It means a data management system capable of storing input data with different data definitions. In addition, "NoSQL database" means a database other than a relational database, and includes key-value type, column-oriented type (column-oriented type), graph type, document type databases, etc. In addition, "document database" means a database with a free data structure to be stored. One piece of data is called a document and is stored as data written in a description format such as JSON format. In addition, "JSON" is an abbreviation for "JavaScript Object Notation" and means a description method structured as a format that allows humans to easily handle data while reading and writing. In addition, "external command" means a command for operating data included in a database, which is sent from a system other than the data management system, and indicates, for example, SQL in a relational database. In addition, "file path" means information indicating the location where the specified file is stored.

[0012] <Prior Art Data Management System> First, with reference to FIG. 1, an example of a data management system for storing input data with different data definitions will be described. FIG. 1 is a diagram showing a configuration example of a data management system 100 that manages two types of input data with different data definitions. The data management system 100 is composed of a first data conversion interface 104 corresponding to the first input data, a second data conversion interface 105 corresponding to the second input, and a relational database 106 for storing them.

[0013] The relational database 106 is a database that manages data in a plurality of tables and can handle the relevance of data by defining the relationship between tables. For this reason, in order to store the first input data and the second input data with different data definitions, the first input data 101 input to the first data conversion interface 104 is converted into the first conversion data 1011 and stored in the first table 107 and the second table 108, and then accumulated in the relational database 106. Similarly, the second input data 102 input to the second data conversion interface 105 is converted into the second conversion data 1021 and stored in the first table 107 and the second table 108, and then accumulated in the relational database 106.

[0014] <Input Data> Here, generally, since input data is a collection of qualitative or quantitative values related to things and events, for example, in the case of a disaster prevention database, it includes various data such as open data provided by an external system, meteorological data provided by local governments across the country, and disaster prevention information. Also, as a method of expressing input data, various data definitions are adopted, for example, the data is displayed as a character string or expressed as a file in which the character string is displayed.

[0015] Furthermore, when the input data is audio data or video data, the audio data and video data may be provided in a file format, and are often raw data such as audio data and video data as analog data. Therefore, every time the definition and format of the input data are different, in order to store each in the relational database, it is necessary to prepare a dedicated data conversion interface tailored to each input data.

[0016] That is, in order to store various input data in the respective tables of the relational database 106, an interface is required to convert the data into regularly organized data for each data type and content.

[0017] However, in a large-scale database, the definitions of the input data are diverse, and it is not easy to develop a dedicated interface for each input data. Furthermore, in a database that continuously requires data input, the occurrence of new-defined data and changes in data definitions are also considered, and in order to handle these, it becomes necessary to re-develop the data conversion interface.

[0018] If a conventionally widely used relational database is used, it is possible to manage data as multiple tables and define the relationships between the tables, thereby handling the complexity of data relationships. If the data is regularly accumulated by type, strict data consistency can be ensured through transactions. And thereby, advanced search and aggregation processing can be performed with external commands, for example, operations using a database language.

[0019] However, since the data stored in the relational database 106 often stores the input data after conversion, there is also a problem that it is difficult to refer to the raw input data (RAW data) on the database. In particular, in the process of converting the input data, when part of the data is missing or the quantization of the data cannot be properly performed, it may be difficult to refer to the original data. Thus, when using a relational database, there are problems such as the need for a large number of data conversion interfaces according to the type of input data, and the difficulty in referring to RAW data and the like included in the input data.

[0020] [First Embodiment] Next, with reference to FIG. 2, a data management system 200 according to the first embodiment will be described. FIG. 2 is a diagram showing a configuration example of a data management system 200 according to the first embodiment. The data management system 200 includes a data conversion interface 204 and a database 207, and manages the input data. In the following, the case where the input data has two types of data definitions will be described as an example, but the data management system of the present disclosure is not limited thereto.

[0021] The data management system 200 converts input data (input data 201, input data 202) with different data definitions into a data set including structured data having a specified data structure and unstructured data information. That is, input data with different data definitions is converted into unified structured data by a data conversion interface 204 that can be commonly used, and stored in the database 207. In the following, as an example of specific input data, it is assumed that the input data 201 is composed of data in a file format describing an arithmetic progression that increases by 1 from 1 to 100, and the input data 202 is composed only of the arithmetic progression itself that increases by 1 from 101 to 200. However, the types and formats of input data that can be handled by the data management system of the present disclosure may be other types and formats.

[0022] <Data Set> Next, a data set including structured data having a specified data structure and unstructured data information will be described. The dataset 205 is data obtained by converting the input data 201 through the data conversion interface 204, and includes structured data 208 and unstructured data information 209. That is, the dataset 205 has a structure in which the structured data 208 and the unstructured data information 209 are integrated in pairs.

[0023] <Structured data> Next, the structured data 208 will be described. The structured data 208 of the dataset is data in which the input data is converted into a specified data structure by the data conversion interface 204, and the data structure such as the data type, the array of data, and the delimiter character is converted into a unified structure. For example, when the input data is composed of structured metadata and unstructured data in file format, it is data obtained by converting the metadata part into a specified structure.

[0024] Specifically, the structured data 208 is document data in which the content of the input data is described in JSON format, and is data described according to the specified data structure of the JSON format. For example, when the input data 201 is in file format with a sequence of numbers from 1 to 100 described, since the data content of the file is an arithmetic sequence that increases by 1 from 1 to 100, the structured data 208 obtained by converting the input data 201 is data in which the sequence of numbers from 1 to 100, which is the data content of the file, is described in JSON format. Similarly, the input data 202 has a sequence of numbers from 101 to 200 described, and since the data content is the arithmetic sequence itself that increases by 1 from 101 to 200, the structured data 208 obtained by converting the input data 202 is data in which the sequence of numbers from 101 to 200, which is the data itself, is described in JSON format.

[0025] Also, as the structured data 208, information not included in the input data may be added as the structured data 208. For example, since the input data 201 and the input data 202 are in an arithmetic progression where the data content increases by 1 each time, they can also be regarded as related data. In such a case, an ID for associating the input data 201 and the input data 202, which are different input data, may be assigned to the structured data 208 obtained by converting the input data 201 and the structured data 208 obtained by converting the input data 202.

[0026] Thereby, when performing data operations, particularly search operations, in the database 207 as described later, the two input data can be associated and searched.

[0027] Also, as the structured data 208, information indicating the storage location of the unstructured data included in the input data may be assigned as the structured data 208. For example, since the input data 201 is in a file format in which a sequence of numbers from 1 to 100 is described, the file can be saved to an external storage, and the storage location of the file can be indicated in the unstructured data information. In such a case, the storage location of the file saved to the external storage may be assigned to the structured data 208 obtained by converting the input data 201.

[0028] Thereby, even when the input data cannot be directly stored in the database 207, RAW data and the like included in the input data can be referenced.

[0029] Also, if the data content of the structured data 208 is described in a data structure with unified data, the structured data 208 may be a document described in a format other than the JSON format.

[0030] <Unstructured data information> Next, the unstructured data information 209 will be described. The unstructured data information 209 is information obtained by converting data such as data types, data arrays, delimiter characters, etc. whose data structures are not clearly defined in the input data, for example, audio data, video data files, etc. through a data conversion interface.

[0031] In an embodiment of the present disclosure, when the input data contains unstructured data in a file format, the unstructured data information 209 may be a file path to the storage where the file is stored, or the unstructured data itself in that file format. Further, as will be described later, when the input data does not contain unstructured data, it may be empty data or an empty dummy file. For example, when the input data 201 is a file describing an arithmetic sequence that increases by 1 up to 100, the unstructured data information 209 can be the description of the file or the file path of the file. Also, when the input data 202 is only an arithmetic sequence that increases by 1 from 101 to 200 and no file exists, empty data may be generated and used as the unstructured data information 209, or a file may be generated as empty data and used as the unstructured data information 209.

[0032] Also, when the input data is analog data, the location of the recording medium on which the analog data is recorded may be used as the unstructured data information.

[0033] <Data conversion interface> The data conversion interface 204 is a functional unit that converts input data into a data set consisting of structured data 208 having a specified data structure and unstructured data information 209.

[0034] Specifically, as described above, the data conversion interface 204 reads the data content of the input data and converts the read data content into a document described in JSON format as structured data 208. Then, as unstructured data information 209, the file in which the input data is stored, or the file path where the file is stored, or empty data is converted.

[0035] Also, when the input data is analog data, the analog data may be recorded on a recording medium and the location of the recording medium may be stored.

[0036] <Database> The database 207 stores and accumulates the data set generated by the data conversion interface 204.

[0037] Also, the database 207 can perform operations (search, extraction, etc.) on the accumulated data based on operations from a database language which is an external command.

[0038] When the database 207 is a document database which is one of NoSQL databases, it is possible to search for data content specified by a database language from structured data and easily output the search result. In particular, when the database 207 is a document database, as long as the specified data structure is provided for the structured data part, it is possible to search even without strict data types and regularity as described in the table in the case of a relational database. Therefore, it is suitable for storing input data with different various data definitions in a searchable format.

[0039] For example, when a data set is accumulated in the database 207 and searching for "data containing the number 10" by a database language, the database 207 searches for "data containing the number 10" from the structured data 208 included in the accumulated data set. The database 207 can display, as search results, a data set in which the structured data 208 contains "data including the number 10". That is, as search results, in addition to the structured data 208, the unstructured data information 209 can also be displayed.

[0040] <Data conversion processing flow of the data management system> Next, with reference to FIG. 3, the data conversion processing flow of the data management system 300 will be described. FIG. 3 is a flowchart showing the data conversion processing of the data management system 300.

[0041] (Step S101) In step S101, the data conversion interface 204 determines the presence or absence of structured data and unstructured data included in the input data. Specifically, the data conversion interface 204 determines whether the input data is "composed of structured data and unstructured data", "does not have structured data", that is, "does not have structured data and is composed only of unstructured data", or "does not have unstructured data", that is, "does not have unstructured data and is composed only of structured data". Note that since there is no input data that "does not have both structured data and unstructured data", it is not necessary to be the subject of this determination. If the input data is "composed of structured data and unstructured data", it proceeds to step S102 as Case 1. If it "does not have structured data and is composed of unstructured data", it proceeds to step S104 as Case 2. If it "does not have unstructured data and is composed of structured data", it proceeds to step S106 as Case 3.

[0042] (Step S102) In step S102, in Case 1, since both structured data and unstructured data exist in the input data, the data conversion interface 204 converts the structured data included in the input data into structured data 208 in the JSON format, which is the specified data structure.

[0043] (Step S103) In step S103, the data conversion interface 204, together with the structured data 208, converts the unstructured data included in the input data into unstructured data information 209, converts it into the dataset 205, stores it in the database 207, and ends the process. Note that, as described above, the content of the unstructured data information 209 in this case may be the unstructured data itself or the information indicating its storage location.

[0044] (Step S104) In step S104, in Case 2, since there is no structured data in the input data, the data conversion interface 204 reads the data content of the unstructured data included in the input data and converts the data content into structured data 208 in the JSON format, which is a specified data structure.

[0045] (Step S105) In step S105, the data conversion interface 204, together with the structured data 208, converts the unstructured data included in the input data into unstructured data information 209, converts it into the dataset 205, stores it in the database 207, and ends the process.

[0046] (Step S106) In step S106, in Case 3, since there is no unstructured data in the input data, the data conversion interface 204 converts the structured data included in the input data into structured data 208 in the JSON format, which is a specified data structure.

[0047] (Step S107) In step S109, the data conversion interface 204 generates empty data as the unstructured data information 209, converts it into the dataset 205 together with the structured data 208, stores it in the database 207, and ends the process.

[0048] <Function and Effect> The data management system 200 of the present disclosure has been described above. The data management system 200 of the present disclosure mainly includes a data conversion interface 204 and a database 207. The data conversion interface 204, which is common to various input data, can convert input data into a data set and store it in the database 207. Thereby, when performing data operations on the data stored in the database 207, the operability of the data is improved by performing data operations on the data set using the structured data 208 included in the data set, and the raw input data stored in the unstructured data information 209 can be referred to and confirmed.

[0049] In addition, the data conversion interface 204 can convert input data into a data set regardless of the type of input data and data definition. Thereby, data can be stored in the database 207 without developing a data conversion interface corresponding to the input data for each of various types of input data.

[0050] [Example] Next, with reference to FIG. 4, an example of a disaster prevention-related data management system that handles a wide variety of input data will be described. FIG. 4 is a diagram showing a configuration example of a data management system 300 according to an example. The data management system 300 includes a data management system API, a data conversion interface 204, a data management interface 211, a data output interface 213, a document database 2071, and an external storage 214, manages the input data, and outputs the managed data to the customer system 410 as needed. In addition, the input data of the data management system 300 is a mixture of various forms of data such as open data provided by the open data disclosure institution 400 and data provided by the business application 411 of the customer system 410. In addition, the open data disclosure institution 400 includes the Japan Meteorological Agency 401, the Meteorological Business Support Center 402, the River Information Center 403, etc., but is not necessarily limited to these, and other institutions other than the above may also be acceptable. In the following description, components that are the same as or equivalent to those in the above-described first embodiment and the like are denoted by the same reference numerals, and the description thereof is simplified or omitted.

[0051] <Open data disclosure institution> The open data disclosure institution 400 is a public institution that discloses publicly available public data (open data). As described above, the open data disclosure institution 400 includes the Japan Meteorological Agency 401, the Meteorological Business Support Center 402, the River Information Center 403, etc., and meteorological information, river / watershed information, etc. are provided as open data, respectively. The data management system 300 inputs the open data as input data and accumulates it in the database 207. In addition, the open data may be data other than public data as long as it is publicly available data, and the open data disclosure institution 400 may be an institution other than a public institution as long as it is an institution that discloses open data. That is, the open data disclosure institution 400 is not limited to the Japan Meteorological Agency 401, the Meteorological Business Support Center 402, and the River Information Center 403. These open data may include RAW data in various formats, and it is important for the data management system to be able to directly access the RAW data.

[0052] <Customer system> The customer system 410 is a system owned by the customer and is a system in which the business application 411 is operating. In addition, the customer system 410 inputs the data calculated by the business application 411 as input data to the data management system 300 and receives necessary data from the data management system 300. In this embodiment, the data management system 300 is connected to only one customer system 410, but may be connected to a plurality of customer systems 410.

[0053] <Data Management System API> The data management system API 210 is a functional unit that manages data input and output. Specifically, in the data management system 300, when input data is input, it is transmitted to the data conversion interface 204 via the data management system API 210. Also, as described above, when data stored in the data management system 300 is requested from the business application 411, the data is output.

[0054] <Data Management Interface> The data management interface 211 is a functional unit that manages the data set 205 stored in the document database 2071. Specifically, the data management interface 211 accesses the data set 205 stored in the document database 2071 and performs operations such as adding, deleting, and changing the data content displayed on the data set maintenance screen 212. Also, the data management interface 211 may access the data management system API 210 and restrict the open data disclosure institution 400 that transmits input data.

[0055] <Document Database> The document database 2071 is one of the NoSQL databases, and stores and accumulates the data set generated by the data conversion interface 204 as a document written in a description format such as JSON format.

[0056] <External Storage> The external storage 214 is a storage unit connected to the document database 2071 that stores files containing input data as unstructured data. When the input data is a file, the file is saved in the external storage 214, and the storage location of the file can be indicated in the unstructured data information. By accessing the storage location of the file in the unstructured data information, direct access to the RAW data can be achieved.

[0057] <Function and Effect> As described above, the data management system 300 of this embodiment has been explained. The data management system 300 of this embodiment mainly has a common data conversion interface 204 corresponding to various inputs, a data output interface 213, a data set 205 composed of structured data 208 and unstructured data information 209, and a document database 2071. By doing so, the input data transmitted from an open data disclosure institution 400 or the like is accumulated in the document database 2071, and the data output interface 213 transmits the accumulated data to the customer system 410. Thereby, with respect to the data accumulated in the document database 2071, the business application 411 can utilize various types of data.

[0058] As described above, the embodiments of the present invention have been explained. However, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the gist of the present invention. Note that the following aspects are included in the present disclosure.

[0059] (Aspect 1) A data management system capable of storing input data with different data definitions, a data conversion interface that converts the input data into a data set composed of structured data having a specified data structure and unstructured data information, and a NoSQL database that stores the data set and is capable of operating on the data set. Data management system.

[0060] (Aspect 2) In the data management system according to Aspect 1, the unstructured data information is the unstructured data itself included in the input data, information indicating its storage location, or information indicating empty data, and the database is a document database. A data management system characterized by the following.

[0061] (Aspect 3) In the data management system according to Aspect 1 or 2, The data conversion interface, When the input data is composed of structured data and unstructured data, Convert the structured data into structured data with a specified data structure, And store it in the database as the data set together with the unstructured data information. A data management system characterized by the following.

[0062] (Aspect 4) In the data management system according to any one of Aspects 1 to 3, The data conversion interface, When the input data does not include structured data, Generate structured data in a specified format based on the content of the unstructured data, And store it in the database as the data set together with the unstructured data information. A data management system characterized by the following.

[0063] (Aspect 5) In the data management system according to any one of Aspects 1 to 4, The data conversion interface, When the input data does not include unstructured data, Convert the structured data into structured data with a specified data structure, Generate the unstructured data information as empty data or an empty data file, And store it in the database as the data set together with the structured data. A data management system characterized by the following.

[0064] (Aspect 6) In the data management system according to any one of Aspects 1 to 5, The structured data generated by the data conversion interface includes information indicating the storage location of the unstructured data included in the input data. A data management system characterized by the above.

[0065] (Aspect 7) In the data management system according to any one of Aspects 1 to 6, The structured data generated by the data conversion interface includes information for associating the input data with each other. A data management system characterized by the above.

[0066] (Aspect 8) In the data management system according to any one of Aspects 1 to 7, The database is capable of data search by searching for structured data having the specified data structure based on an external command. A data management system characterized by the above.

[0067] (Aspect 9) In a data management system including a data conversion interface that converts input data to generate a data set and a database that stores the data set, the data conversion interface converts the input data into a data set including structured data having a specified data structure and unstructured data information, and stores the data set in a database. A data management method.

[0068] (Aspect 10) In the data management method according to Aspect 9, the unstructured data information is information indicating that the unstructured data itself included in the input data, its storage location, or empty data, the database is a document database, the data conversion interface When the input data is composed of structured data and unstructured data, convert the structured data into structured data with a specified data structure, store it in a database as the data set together with the unstructured data information, when the input data does not include structured data, generate structured data in a specified format based on the content of the unstructured data, store it in a database as the data set together with the unstructured data information, when the input data does not include unstructured data, convert the structured data into structured data with a specified data structure, generate the unstructured data information as empty data or an empty data file, store it in a database as the data set together with the structured data A data management method characterized by the above.

Explanation of Signs

[0069] 100, 200, 300 Data management system 101 First input data 102 Second input data 201, 202 Input data 1011 First converted data 1021 Second converted data 104 First data conversion interface 105 Second data conversion interface 106 Relational database 107 First table 108 Second table 204 Data conversion interface 205 Data set 207 Database 2071 Document database 208 Structured data 209 Unstructured data information 210 Data Management System API 211 Data Management Interface 212 Dataset Maintenance Screen 213 Data Output Interface 214 External Storage 400 Open Data Publishing Institution 401 Japan Meteorological Agency 402 Meteorological Business Support Center 403 River Information Center 410 Customer System 411 Business Application

Claims

1. A data management system capable of storing input data with different data definitions, A data conversion interface for converting the input data into a data set consisting of structured data with a specified data structure and unstructured data information, An NoSQL database that stores the data set and can operate on the data set, comprising A data management system.

2. In the data management system according to Claim 1, The unstructured data information is the unstructured data itself included in the input data, information indicating its storage location, or information indicating empty data, The database is a document database A data management system characterized by this.

3. In the data management system according to Claim 1, The data conversion interface is When the input data is composed of structured data and unstructured data, Convert the structured data into structured data with a specified data structure, Store it in the database as the data set together with the unstructured data information A data management system characterized by this.

4. In the data management system according to Claim 1, The data conversion interface is When the input data does not have structured data, Generate structured data in a specified format based on the content of the unstructured data, Store it in the database as the data set together with the unstructured data information A data management system characterized by this.

5. In the data management system according to Claim 1, The data conversion interface, when the input data does not include unstructured data, converts the structured data into structured data with a specified data structure, generates the unstructured data information as empty data or an empty data file, and stores the structured data and the unstructured data information in a database as the dataset. A data management system characterized by the above.

6. In the data management system according to claim 1, the structured data generated by the data conversion interface includes information indicating the storage location of the unstructured data included in the input data. A data management system characterized by the above.

7. In the data management system according to claim 1, the structured data generated by the data conversion interface includes information for associating the input data with each other. A data management system characterized by the above.

8. In the data management system according to claim 1, the database, can perform data search by searching for structured data having the specified data structure based on an external command. A data management system characterized by the above.

9. In a data management system including a data conversion interface for converting input data to generate a dataset and a NoSQL database for storing the dataset, the data conversion interface, converts the data content of the input data into a dataset including structured data having a specified data structure and unstructured data information, and stores the dataset in a database. Data management method.

10. In the data management method according to claim 9, the unstructured data information is information indicating that the unstructured data itself, its storage location, or empty data is included in the input data, the database is a document database, the data conversion interface, when the input data is composed of structured data and unstructured data, convert the structured data into structured data with a specified data structure, store it in the database as the data set together with the unstructured data information, when the input data does not include structured data, generate structured data in a specified format based on the content of the unstructured data, store it in the database as the data set together with the unstructured data information, when the input data does not include unstructured data, convert the structured data into structured data with a specified data structure, generate the unstructured data information as empty data or an empty data file, and store it in the database as the data set together with the structured data A data management method characterized by the above.

Images