JP2022121747A - Data conversion device and data conversion method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide information to determine whether or not conversion to desired information has been performed by a conversion rule before performing cleansing processing on actual data.

SOLUTION: In a data conversion device 100, an input screen interface unit 101 acquires a data list and further acquires a conversion rule. An extraction unit 104 extracts a provisional application object data list being a data list to which the conversion rule is to be provisionally applied, from the data list. A conversion table generation unit 106 provisionally applies the conversion rule to the provisional application object data list to generate a conversion table associating the provisional application object list and a result of provisional application with each other, and a conversion table output unit 107 outputs the conversion table.

SELECTED DRAWING: Figure 1

COPYRIGHT: (C)2022,JPO&INPIT

Description

The present invention relates to a data conversion device and a data conversion method.

It is conventionally known to cleanse large amounts of data before analyzing it. As an example of this cleansing, there is a process of eliminating spelling variations and the like.

Patent Literature 1 describes a technique for cleansing data. Specifically, it is described that the item name data in the content data file is converted into item name data that is used by standardizing the format, and that the content data used in the format is complemented to this content data file. (Claim 1, abstract, etc.). There is also software that replaces character strings by specifying regular expressions.

Japanese Patent Application Laid-Open No. 2004-341605

The conventional techniques described above perform cleansing based on predetermined conversion rules or input conversion rules. By the way, when the user independently considers the conversion rule, there is a possibility that the information is not converted into the information desired by the user.

Therefore, it is desirable to be able to determine whether or not the desired conversion result is obtained by the above conversion rules before performing the cleansing process on the actual data.

Accordingly, an object of the present invention is to provide a data conversion apparatus and a data conversion method that provide information for determining whether or not actual data has been converted into desired information according to the conversion rule before performing cleansing processing on the actual data. That's what it is.

The above and other objects and novel features of the present invention will become apparent from the description of the specification and the accompanying drawings.

A brief outline of typical inventions disclosed in the present application is as follows.

A data conversion device according to a representative embodiment of the present invention includes a data list acquisition unit that acquires a data list, a conversion rule acquisition unit that acquires a conversion rule, and a conversion from the data list acquired by the data list acquisition unit. An extraction unit for extracting a temporary application target data list, which is a data list to which a rule is provisionally applied, and a temporary application for applying the conversion rule acquired by the conversion rule acquisition unit to the provisional application target data list extracted by the extraction unit. A conversion table generation unit that applies and generates a conversion table that associates the temporary application target data list extracted by the extraction unit with the result of temporary application, and outputs the conversion table generated by the conversion table generation unit. and a conversion table output unit.

Among the inventions disclosed in the present application, the effects obtained by representative ones are briefly described below.

That is, according to the representative embodiment of the present invention, it is possible to provide information for determining whether or not the data has been converted into desired information according to the conversion rule before the actual data is subjected to the cleansing process. .

1 is a diagram showing an overview of a configuration example of an information processing system including a data conversion device that is an embodiment of the present invention; FIG. It is the figure which showed the outline of the data list input screen in one embodiment of this invention. It is the figure which showed the outline of the data conversion procedure input screen in one embodiment of this invention. 4 is a diagram showing an overview of data examples stored in a data list storage unit according to one embodiment of the present invention; FIG. 4 is a diagram showing an overview of data examples stored in a conversion rule storage unit according to one embodiment of the present invention; FIG. It is a figure which shows the outline|summary of the data example memorize|stored in the unique list storage part in one embodiment of this invention. It is the figure which showed the outline of the conversion confirmation screen in one embodiment of this invention. It is a figure which shows the outline|summary of the data example memorize|stored in the conversion table storage part in one embodiment of this invention. 4 is a diagram showing an overview of an example of data conversion history information stored in a conversion history storage unit according to one embodiment of the present invention; FIG. 4 is a diagram showing an overview of an example of conversion history detail information stored in a conversion history storage unit according to one embodiment of the present invention; FIG. Briefly describe an example of the flow of overall processing that is temporarily converted to a unique list extracted from a data list in one embodiment of the present invention and applied to the data list based on the result of the temporary conversion. It is a diagram showing. FIG. 4 is a diagram showing an overview of an example of the flow of processing for generating a unique list according to one embodiment of the present invention; FIG. 4 is a diagram showing an overview of an example of the flow of processing for generating a conversion table according to one embodiment of the present invention; FIG. 4 is a diagram showing an overview of an example of the flow of processing for correcting a conversion table according to one embodiment of the present invention; FIG. 4 is a diagram showing an overview of an example of the flow of processing for data conversion using a conversion table according to one embodiment of the present invention;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In principle, the same parts are denoted by the same reference numerals throughout the drawings for describing the embodiments, and repeated descriptions thereof will be omitted. On the other hand, parts that have been described with reference numerals in one drawing may be referred to with the same reference numerals, although they are not shown again in the description of other drawings.

<System configuration>
FIG. 1 is a diagram showing an overview of a configuration example of an information processing system including a data conversion device that is an embodiment of the present invention. The data conversion device 100 of this embodiment is a device that converts data based on a conversion rule. The data conversion device 100 is an information processing device such as a server device.

Data conversion device 100 and terminal device 200 can transmit and receive information to and from each other via network 300 . Network 300 is a wired or wireless network.

A terminal device 200 connected to the data conversion device 100 via the network 300 is an information processing device such as a smart phone or a personal computer. The terminal device 200 transmits information to the data conversion device 100 via the network 300 or acquires information from the data conversion device 100 according to input operations by the user of the terminal device 200 . Also, the terminal device 200 displays and outputs information acquired from the data conversion device 100 . The terminal device 200 also stores a data list to be converted into a file format or the like. Here, the data list is a list of data records in one or more columns, and is included in, for example, a CSV (comma-separated values) format file.

Data conversion device 100 and terminal device 200 are implemented by predetermined hardware and software. For example, the data conversion device 100 and the terminal device 200 have processors, memories, and the like. A program on the memory executed by the processor causes the computers of data conversion device 100 and terminal device 200 to function. The data conversion device 100 and the terminal device 200 also have input means (keyboard, mouse, etc.) and output means (display means such as a display).

The data conversion apparatus 100 of this embodiment has an input screen interface section 101, a data list storage section 102, a conversion rule storage section 103, an extraction section 104, a unique list storage section 105, and a conversion table generation section .

The data conversion apparatus 100 also includes a conversion table output unit 107 , a conversion request reception unit 108 , a conversion table storage unit 109 , a main application unit 110 and a conversion history storage unit 111 .

Each part of the data conversion apparatus 100 is implemented as a software program that runs on middleware such as an OS (Operating System), a DBMS (DataBase Management System), and a Web server program (not shown).

The input screen interface unit 101 is a part that outputs various input screens to the terminal device 200 in response to a request from the terminal device 200 and acquires the contents input to the various input screens.

Upon receiving a data list input request from terminal device 200 , input screen interface section 101 generates a data list input screen and transmits the data list input screen to terminal device 200 .

An example of the data list input screen will now be described with reference to FIG. FIG. 2 is a diagram showing an outline of the data list input screen. The data list input screen is a screen for entering the data list to be converted. Specifically, it is possible to specify the file that will be the data list to be converted and the columns to be converted. screen.

The data list input screen has a file selection button 10 , a selected file area 11 , an actual data display area 12 , a change target column specification box 13 , an add column button 14 and a next button 15 .

When the user of the terminal device 200 selects the file selection button 10, the terminal device 200 calls up a screen (not shown) for designating a data list file. Then, when a file of the data list is selected on the screen, the terminal device 200 displays the file name (including the save path) of the file in the selected file area 11 .

In addition, the terminal device 200 refers to the contents of the data list file, and assigns the data list and an ID (record ID of the data list) to the data list. Then, the terminal device 200 associates the ID with the data list and displays them in the actual data display area 12 .

In the example of FIG. 2, a data list of company names is displayed and has 11 items. Note that it is not necessary to display all the data in the data list, and only part of the data may be displayed.

The data displayed in the actual data display area 12, "ABC Systems Co., Ltd." whose record ID is 1, are all full-width characters. Also, "ABC Systems Co., Ltd." with a record ID of 2 has half-width characters for "systems." In addition, the part in parenthesis of “EF Software Co., Ltd.” whose record ID is 11 is half-width. Also, depending on the record, the notation is not unified, such as "stock company" and "stock company", so it is necessary to perform data conversion (cleansing processing).

The change target column specification box 13 is a part for specifying a column to which a conversion rule to be described later is applied. For example, read the part where the column names of the data list are defined and display them in a dropdown list. The column specified in the change target column specification box 13 becomes the column to which the conversion rule is applied.

The add column button 14 is a button for adding a change target column specification box 13 . This allows you to specify multiple columns. When the next button 15 is pressed, the terminal device 200 confirms the file of the data list and the column to be changed (holds the contents of the file of the data list and the column to be changed in a memory or the like), and prepares the data. A transmission request for a data conversion procedure input screen is sent to the conversion device 100 .

When the input screen interface unit 101 receives a transmission request for the data conversion procedure input screen from the terminal device 200, it transmits the data conversion procedure input screen to the terminal device 200 in response. When acquiring the data conversion procedure input screen, the terminal device 200 displays the data conversion procedure input screen.

An example of the data conversion procedure input screen will now be described with reference to FIG. FIG. 3 is a diagram showing an outline of the data conversion procedure input screen. The data conversion procedure input screen is a screen for inputting a rule (conversion rule) for converting the data list. Specifically, it has a conversion rule input area 20 , a procedure add button 21 , a procedure delete button 22 , and a next button 23 .

The conversion rule input area 20 is an area for inputting an object before conversion (for example, a character string, character input mode) and an object after conversion in the conversion rule, and a conversion rule procedure (applying a plurality of conversion rules). order).

In the example of FIG. 3, first, a conversion rule is defined that indicates that a character string whose character input mode is half-width kana should be converted to full-width kana character input mode. Secondly, a conversion rule is defined that indicates that a character string of (stock) (the parentheses of stock are full-width characters) to be converted into a stock company. Thirdly, a conversion rule is defined to convert a corporation to a blank.

The plurality of conversion rules shown in FIG. 3 are rules for collectively performing the process of converting all katakana names to full-width characters and removing notations indicating corporations (including corporations).

Further, when the procedure addition button 21 is pressed, the terminal device 200 additionally displays the conversion rule input area 20 . In the case of the example of FIG. 3, when the procedure addition button 21 is pressed, an area for inputting the fourth conversion rule is displayed.

Further, when the procedure deletion button 22 is pressed, the conversion rule input area 20 corresponding to the procedure deletion button 22 is deleted. In the example of FIG. 3, when the first procedure deletion button 22 is pressed, the first conversion rule is deleted.

When the next button 23 is pressed, the terminal device 200 confirms the plurality of conversion rules and the procedures of the conversion rules, and stores the data list, the plurality of conversion rules, and the procedures of the conversion rules as data. It is transmitted to the conversion device 100 to request provisional application of the conversion rule.

Note that the data conversion procedure input screen shown in FIG. 3 may include a known interface for changing the conversion order.

Returning to FIG. 1, the input screen interface unit 101 receives the provisional application request, and acquires a data list, a plurality of conversion rules, and the procedures of the conversion rules. Thus, the input screen interface unit 101 functions as a data list acquisition unit. The input screen interface unit 101 also functions as a conversion rule acquisition unit. As described above, when the data list is acquired, the input screen interface unit 101 generates an ID (data ID) for identifying the data list, associates the ID with the data list, and stores the data list storage unit 102 in the data list storage unit 102. Register to

Here, an example of data stored in the data list storage unit 102 will be described with reference to FIG. FIG. 4 is a diagram showing an overview of data examples stored in the data list storage unit 102. As shown in FIG. As shown in FIG. 4, the data list storage unit 102 associates and stores data IDs, record IDs, and pre-conversion indicating list data before conversion.

Returning to FIG. 1, when the input screen interface unit 101 acquires a plurality of conversion rules and the procedures of the conversion rules as described above, it generates an ID (conversion rule ID) for identifying the current conversion. The input screen interface unit 101 associates the conversion rule ID, the procedure (conversion rule procedure), and the conversion rule (before conversion and after conversion) with each other and registers them in the conversion rule storage unit 103 .

The input screen interface unit 101 may store the character string itself of the conversion rule, may store the regular expression, or may store the function of the programming language. Note that the input screen interface unit 101 may store information in which the conversion rule ID and the conversion target string are associated with each other.

Here, an example of data stored in the conversion rule storage unit 103 will be described with reference to FIG. FIG. 5 is a diagram showing an overview of an example of data stored in the conversion rule storage unit 103. As shown in FIG. As shown in FIG. 5, the conversion rule storage unit 103 associates and stores conversion rule IDs, procedures, pre-conversion, and post-conversion.

Thus, the conversion rule storage unit 103 stores a plurality of conversion rules acquired by the input screen interface unit 101 and the application order of the plurality of conversion rules as conversion rule history information. That is, the conversion rule storage unit 103 functions as a conversion rule history information storage unit.

Returning to FIG. 1 , input screen interface section 101 registers data in data list storage section 102 and conversion rule storage section 103 , and then sends data ID and conversion rule ID to extraction section 104 .

The extraction unit 104 is a part that extracts a temporary application target data list, which is a data list to which the conversion rule is temporarily applied, from the data list acquired by the input screen interface unit 101 . After acquiring the data ID and conversion rule ID from the input screen interface unit 101 , the extraction unit 104 acquires a record corresponding to the data ID from the data stored in the data list storage unit 102 .

Also, the extraction unit 104 refers to the conversion rule storage unit 103 and acquires a conversion target column corresponding to the conversion rule ID.

The extraction unit 104 generates a unique list (temporary application target data list) from which duplicate data is removed for each conversion target column in the acquired record. For example, the extraction unit 104 initializes the unique list, refers to the conversion target columns of the acquired records one by one, and stores the values of the conversion target columns of the record in the unique list if they do not exist in the unique list. Also, if the value of the conversion target column of the acquired record is included in the unique list, the extraction unit 104 does not store it in the unique list.

When the extraction unit 104 generates the unique list obtained as a result of referring to all the values of the conversion target column of the acquired record, it associates the unique list with the data ID and registers it in the unique list storage unit 105 . Further, when there are a plurality of columns to be converted, the extracting unit 104 may further associate the IDs of the columns to be converted and register them in the unique list storage unit 105 .

Here, an example of data stored in the unique list storage unit 105 will be described with reference to FIG. FIG. 6 is a diagram showing an overview of an example of data stored in the unique list storage unit 105. As shown in FIG. As shown in FIG. 6, the unique list storage unit 105 associates and stores data IDs and company names, which are columns to be converted.

As shown in FIG. 6, "EF Software Co., Ltd." with full-width brackets and "EF Software Co., Ltd." with half-width brackets are stored.

Returning to FIG. 1 , extraction unit 104 generates a unique list, stores the unique list in unique list storage unit 105 , and then sends the data ID and conversion rule ID to conversion table generation unit 106 .

Note that the extraction unit 104 has described a case where the unique list is generated as the provisional application target data list, but may extract all conversion target columns of the acquired records as the provisional application target data list.

The conversion table generation unit 106 is a part that temporarily applies the conversion rules acquired by the input screen interface unit 101 to the temporary application target data list extracted by the extraction unit 104 according to the order of application. The conversion table generation unit 106 is a part that generates a conversion table that associates the provisional application target data list extracted by the extraction unit 104 with the results of provisional application.

After obtaining the data ID and the conversion rule ID from the extraction unit 104, the conversion table generation unit 106 refers to the unique list storage unit 105 and obtains the unique list corresponding to the data ID. The conversion table generation unit 106 also refers to the conversion rule storage unit 103 to acquire the procedure, conversion rule (before and after conversion), and conversion target column corresponding to the conversion rule ID.

The conversion table generation unit 106 also applies the conversion rules to the unique list in the order of conversion for each conversion target column, and generates an application result. The conversion table generation unit 106 generates a conversion table including information that associates the unique list with the application result, and generates a conversion confirmation screen (details will be described later) including the conversion table.

Conversion table generation unit 106 sends the conversion confirmation screen, data ID, and conversion rule ID to conversion table output unit 107 .

The conversion table output section 107 is a section that outputs the conversion table generated by the conversion table generation section 106 . Upon obtaining the conversion confirmation screen, data ID, and conversion rule ID, conversion table output unit 107 outputs the conversion confirmation screen to terminal device 200 . Thus, the conversion table output unit 107 outputs the conversion table. When acquiring the conversion confirmation screen, the terminal device 200 displays the conversion confirmation screen.

An example of the conversion confirmation screen will now be described with reference to FIG. FIG. 7 is a diagram showing an outline of the conversion confirmation screen. The conversion confirmation screen is a screen for confirming the conversion result when the data list is temporarily converted (that is, when it is temporarily applied).

As shown in FIG. 7, records other than records with half-width parentheses are converted into character strings from which KK or KK is removed, and half-width katakana characters are converted to full-width katakana characters.

The conversion confirmation screen has a conversion table display area 31 , a correction button 32 and a conversion execution button 33 . The conversion table display area 31 is an area for displaying a conversion table in which the unique list before conversion is associated with the conversion result of the unique list. Note that when there are a plurality of conversion target columns, there is a conversion table for each conversion target column.

The correction button 32 is a button indicating a request for correction of the content after conversion. When the correction button 32 is pressed by the user of the terminal device 200, the terminal device 200 enables editing of the post-conversion part of the conversion table.

In the case of the example of FIG. 7, it is conceivable to make a modification to remove the part of EF Software Co., Ltd. that has half-width brackets.

The terminal device 200 edits the post-conversion part of the conversion table by an input operation by the user, and when an instruction indicating completion of editing (for example, pressing a button indicating completion of correction, not shown) is given, the post-conversion after correction is edited. Redisplay the part of

Further, when the conversion execution button 33 is pressed, the terminal device 200 transmits the latest conversion table (updated conversion table, that is, correction result) to the data conversion device 100 and requests conversion of the data list. When there are a plurality of columns to be converted, the terminal device 200 transmits all conversion tables for each column to be converted to the data conversion device 100 .

Returning to FIG. 1, the conversion request reception unit 108 is a portion that receives a data list conversion request after the conversion table is output by the conversion table output unit 107 .

A conversion request receiving unit 108 acquires the latest conversion table and receives a data list conversion request. Note that the conversion request receiving unit 108 may acquire the entire conversion table for each conversion target column. In this way, the conversion request receiving unit 108 functions as a correction acquisition unit. Note that the conversion request receiving unit 108 may acquire the entire conversion table for each conversion target column. The conversion request receiving unit 108 generates an ID (conversion table ID) for the latest conversion table. Note that when the conversion request receiving unit 108 acquires a conversion table for each of a plurality of conversion target columns, it generates a different conversion table ID for each conversion table. Note that the conversion request receiving unit 108 may generate information that can specify the conversion target column corresponding to the conversion table ID. For example, the conversion request receiving unit 108 may associate the conversion table ID with the conversion target column name.

Also, the conversion request receiving unit 108 assigns an ID (conversion table detail ID) to each record of the latest conversion table. The conversion request receiving unit 108 stores information in which the conversion table ID, the conversion table detail ID, and the latest conversion table are associated with each other in the conversion table storage unit 109 .

Here, an example of data stored in the conversion rule storage unit 103 will be described with reference to FIG. FIG. 8 is a diagram showing an overview of an example of data stored in the conversion table storage unit 109. As shown in FIG. As shown in FIG. 8, the conversion table storage unit 109 stores a conversion table ID, a conversion table detail ID, pre-conversion (part of the latest conversion table before conversion), and post-conversion (part of the latest conversion table after conversion). part) are associated with each other and stored.

Returning to FIG. 1, since the conversion request receiving unit 108 acquires the latest conversion table, the corrected conversion table is reflected. That is, the conversion request receiving unit 108 functions as a correction receiving unit.

Conversion request accepting section 108 acquires the data ID and the conversion rule ID from conversion table output section 107 , and sends the data ID, conversion rule ID, and conversion table ID to application section 110 .

The application unit 110 uses information based on the plurality of rules acquired by the input screen interface unit 101 and the order of application of the plurality of conversion rules in response to the conversion request received by the conversion request receiving unit 108. , the part that performs the process of converting the data list (this application process). That is, the application unit 110 is a part that performs cleansing processing on the data list.

The application unit 110 acquires the data ID, conversion rule ID, and conversion table ID. The application unit 110 refers to the data list storage unit 102 and acquires the data list corresponding to the data ID. Further, the main application unit 110 generates an ID (change history ID) determined for each main application, and associates the change history ID, the conversion date, the data ID, the conversion rule ID, and the conversion table ID. The information obtained (data conversion history information) is stored in the conversion history storage unit 111 .

Here, an example of data conversion history information stored in the conversion history storage unit 111 will be described using FIG. FIG. 9 is a diagram showing an overview of an example of data conversion history information stored in the conversion history storage unit 111. As shown in FIG. As shown in FIG. 9, the conversion history storage unit 111 stores information in which conversion history IDs, conversion dates, data IDs, conversion rule IDs, and conversion table IDs are associated with each other.

The application unit 110 acquires the conversion table corresponding to the conversion table ID. The application unit 110 refers to the data list corresponding to the data ID one by one (one record), and when the value of the change target column of the record in the data list matches the value before conversion of the record in the conversion table, The value of the change target column of the record of the data list is converted to the post-conversion content of the record of the change table.

In this way, the application unit 110 converts data in the data list using a conversion table as information based on a plurality of rules and the order of application of the plurality of conversion rules.

Note that the main application unit 110 may perform the above-described main application process for each of a plurality of columns to be changed.

The application unit 110 stores information (conversion history detail information) in which the change history ID, the record ID of the data in the converted data list, and the conversion table detail ID of the record in the conversion table are associated with each other (conversion history detail information). store to

Here, an example of conversion history detail information stored in the conversion history storage unit 111 will be described with reference to FIG. FIG. 10 is a diagram showing an overview of an example of conversion history detail information stored in the conversion history storage unit 111. As shown in FIG. As shown in FIG. 10, the conversion history storage unit 111 stores information in which conversion history IDs, record IDs, and conversion table detail IDs are associated with each other.

As described above, the conversion history storage unit 111 converts the data (record ID) of the data list converted by the main application unit 110 and the result (conversion table) provisionally applied by the conversion table generation unit 106. Information associated with information (conversion table detail ID) used for conversion is stored. Since the information corresponds to the conversion execution history, the conversion history storage unit 111 functions as a conversion execution history storage unit.

In this case, since the data conversion device 100 stores the history of conversion, it is possible to store information for confirming which data has been converted. be able to.

The application unit 110 refers to the data list corresponding to the data ID one by one, and determines whether or not there is matching data in all the data lists before the conversion of the records in the conversion table. End this application process. The application unit 110 sends the converted data list to the terminal device 200, and the terminal device 200 displays and outputs the converted data list.

Note that the application unit 110 refers to the conversion rule storage unit 103 to acquire the order and conversion rule corresponding to the conversion ID, and converts the target data list based on this information. good too.

<Processing Flow (Overall Processing from Temporary Conversion to Final Application)>
FIG. 11 is an overview of an example of the flow of overall processing in this embodiment, in which a unique list extracted from a data list is provisionally converted, and based on the result of the provisional conversion, is applied to the data list. It is a figure showing.

First, the input screen interface unit 101 receives a data list input request from the terminal device 200 and transmits a data list input screen and a data conversion procedure screen to the terminal device 200 . Then, the terminal device 200 transmits the data list, the plurality of conversion rules, and the procedure of the conversion rule to the data conversion device 100 based on the information (input information) input by the input operation on the screen. . The input screen interface unit 101 acquires the data list, a plurality of conversion rules, and the procedures of the conversion rules (S1).

The extraction unit 104 generates a unique list from the acquired data list (S2). The conversion table generation unit 106 provisionally applies the conversion rule acquired by the input screen interface unit 101 to the provisional application target data list extracted by the extraction unit 104 according to the order of application. Further, the conversion table generation unit 106 generates a conversion table that associates the provisional application target data list extracted by the extraction unit 104 with the result of the provisional application, and displays a conversion confirmation screen including the conversion table to the terminal device 200. Send (S3).

When receiving the input of the conversion table correction request, the terminal device 200 performs processing for correcting the conversion table (conversion table correction processing) and requests conversion of the data list (S4). The application unit 110 converts the data in the data list using the conversion table in response to the conversion request (S5). Further, the application unit 110 transmits the data conversion result to the terminal device 200, and the terminal device 200 displays the data conversion result (S6).

<Process flow (unique list generation process)>
FIG. 12 is a diagram showing an overview of an example of the flow of processing for generating a unique list in this embodiment. FIG. 12 is a diagram showing details of the process of step S2 in the flowchart of FIG. 11;

The extraction unit 104 initializes the unique list (S11). Subsequently, the extraction unit 104 reads the data list (S12). If there is an unacquired row (record) (S13: Yes), the extraction unit 104 acquires one unacquired row (S14). The extraction unit 104 acquires the value of the target column (conversion target column) from the acquired row (S15), and if the value is not included in the unique list (S16: Yes), adds the value to the unique list. (S17) and proceeds to step S13. In step S16, if the value is included in the unique list (S16: No), the process proceeds to step S13. Further, in step S13, if there is no unacquired line (S13: No), the process ends.

<Process flow (conversion table generation process)>
FIG. 13 is a diagram showing an overview of an example of the flow of processing for generating a conversion table in this embodiment. FIG. 12 is a diagram showing details of the process of step S3 in the flowchart of FIG. 11; First, the conversion table generator 106 initializes the conversion table (S21). Subsequently, the conversion table generator 106 acquires the unique list and reads the unique list (S22). If there is an unacquired unique list (S23: Yes), the conversion table generation unit 106 acquires one row (one record) of the unacquired unique list (S24). The conversion table generation unit 106 applies conversion rules to the acquired values in the order of conversion (S25), and adds information that associates the values (values before conversion) with the results of application (after conversion) to the conversion table. Then (S26), the process proceeds to step S23. Further, in step S23, if there is no unacquired line (S23: No), the process is terminated.

<Process flow (correction process)>
FIG. 14 is a diagram showing an overview of an example of the flow of processing for correcting the conversion table in this embodiment. FIG. 12 is a diagram showing details of the process of step S4 in the flowchart of FIG. 11; First, when the terminal device 200 acquires the conversion confirmation screen from the data conversion device 100, the terminal device 200 displays the conversion confirmation screen (S31). When a correction request for the conversion table 31 is made by pressing the correction button 32 on the conversion confirmation screen (S32: Yes), the terminal device 200 makes the conversion table 31 editable, and corrects the conversion table 31 ( correction result) is obtained (S33). Then, the terminal device 200 updates the conversion table 31 (S34), and displays a conversion confirmation screen on which the conversion table 31 is updated (S35). If no request for correction of the conversion table 31 is made (S32: No), the process is terminated.

<Process flow (data conversion process)>
FIG. 15 is a diagram showing an overview of an example of the flow of data conversion using a conversion table in this embodiment. FIG. 12 is a diagram showing details of the process of step S5 in the flowchart of FIG. 11; First, when the conversion request receiving unit 108 receives a data list conversion request, the application unit 110 acquires the data list corresponding to the data ID to be converted from the data list storage unit 102, thereby reading the data list. (S41).

Subsequently, the application unit 110 generates data conversion history information based on the data ID, conversion rule ID, and conversion table ID acquired from the conversion request reception unit 108, and stores the data conversion history information in the conversion history storage unit 111. (S42). If there is an unconverted line (S43: Yes), the application unit 110 acquires one unconverted line (record) (S44). The application unit 110 acquires the value of the conversion target column from the acquired row (S45). The application unit 110 searches the conversion table for a pre-conversion value that matches the acquired value (S46), and converts the acquired value to the post-conversion value of the searched conversion table record (S47).

The application unit 110 stores the conversion history detail information in the conversion history storage unit 111 based on the record ID of the data in the converted data list and the conversion table detail ID of the record in the conversion table (S48), and step S43. proceed to In step S46, if the pre-conversion value that matches the acquired value cannot be retrieved from the conversion table, the processing in steps S47 and S48 is skipped and the process proceeds to step S43. Also, in step S43, if there is no unconverted line (S43: No), the process ends.

In the above-described embodiment, in the data conversion procedure input screen, when accepting a new input of the target before conversion (for example, character string, character input mode) and the target after conversion, and the conversion order said about Alternatively, on the data conversion procedure input screen, the input screen interface unit 101 accepts selection of a plurality of conversion rules stored in the conversion rule storage unit 103 and the order of application of the plurality of conversion rules, and The plurality of selected conversion rules and the order of application of the plurality of conversion rules may be obtained.

In this case, the data conversion device 100 can avoid having the user input the same conversion rule again.

In the above embodiment, the information processing system having the data conversion device 100 and the terminal device 200 has been described, but these devices may be integrated.

Further, in the above-described embodiment, the case where the input screen interface unit 101 acquires a plurality of conversion rules and the order of application of the plurality of conversion rules has been described. good.

As described above, in the data conversion device 100 according to one embodiment of the present invention, the input screen interface section 101 acquires the data list and the conversion rule. Further, the extracting unit 104 extracts a temporary application target data list, which is a data list to which the conversion rule is temporarily applied, from the data list. The conversion table generating unit 106 provisionally applies the conversion rules to the provisional application target data list according to the order of application, generates a conversion table in which the provisional application target list and the results of the provisional application are associated, The output unit 107 outputs the conversion table.

As described above, the data conversion apparatus 100 extracts the temporary application target list extracted by the extraction unit 104 and applies the conversion rule to the temporary application target list before applying the conversion rule to the data list. to output a conversion table containing the results of the application. As a result, the data conversion device 100 can provide information for determining whether or not the data has been converted into desired information according to the conversion rule before performing the cleansing process on the actual data.

Also, the extraction unit 104 extracts a unique list as a temporary application target list. As a result, the data conversion device 100 can generate a non-redundant conversion table, appropriately convert the data list using the conversion table, and easily determine whether or not the data list has been converted into desired information according to the conversion rules. It is possible to provide information for judging

When the conversion request reception unit 108 receives a data list conversion request, the application unit 110 converts the data list using information based on the conversion rule. In this way, the data conversion device 100 converts the data list after outputting the conversion table, so that the data list can be converted more appropriately.

Further, the application unit 110 uses the conversion table generated by the conversion table generation unit 106 as information based on the conversion rule. As a result, the data conversion device 100 converts the data list using the conversion table, so that the process can be executed more easily than when the conversion rule is applied to the data list.

Moreover, since the application unit 110 applies the corrected conversion table to the data list, it is possible to more appropriately provide the conversion result desired by the user.

Although the invention made by the present inventor has been specifically described above based on the embodiments, the present invention is not limited to the above embodiments, and can be variously modified without departing from the scope of the invention. Needless to say. For example, the above embodiments have been described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the described configurations. Moreover, it is possible to add, delete, or replace some of the configurations of the above-described embodiments with other configurations.

INDUSTRIAL APPLICABILITY The present invention is applicable to devices that convert data.

100... Data conversion device,
101... Input screen interface unit 102... Data list storage unit 103... Conversion rule storage unit 104... Extraction unit 105... Unique list storage unit 106... Conversion table generation unit 107... Conversion table output unit 108... Conversion Request accepting unit 109 Conversion table storage unit 110 Application unit 111 Conversion history storage unit 200 Terminal device 300 Network.

Claims (7)

A data conversion device that converts data based on a conversion rule,
a data list acquisition unit for acquiring a data list;
a conversion rule acquisition unit that acquires a plurality of conversion rules as the conversion rules and an order of application of the plurality of conversion rules;
an extraction unit for extracting a temporary application target data list, which is a data list to which the conversion rule is temporarily applied, from the data list acquired by the data list acquisition unit;
provisional application of the conversion rule acquired by the conversion rule acquisition unit to the provisional application target data list extracted by the extraction unit, and a provisional application target data list extracted by the extraction unit; a conversion table generation unit that generates a conversion table in which the results of the provisional application are associated with each other;
a conversion table output unit that outputs the conversion table generated by the conversion table generation unit;
a conversion request reception unit that receives a conversion request for the data list after the conversion table is output by the conversion table output unit;
In response to the conversion request received by the conversion request receiving unit, the data list is obtained using the plurality of conversion rules as the conversion rules obtained by the conversion rule obtaining unit and the order of application of the plurality of conversion rules. a main application unit that performs the main application process for conversion and outputs the result of the main application process;
A data conversion device comprising: The data conversion device according to claim 1,
The data conversion device, wherein the extraction unit extracts a unique list, which is a unique data list, from among the data lists acquired by the data list acquisition unit, as the temporary application target data list. The data conversion device according to claim 1,
The data conversion device, wherein the extraction unit extracts all data in a conversion target column of an acquired record from the data list acquired by the data list acquisition unit as the provisional application target data list. The data conversion device according to claim 1,
The conversion rule acquisition unit displays a data conversion procedure input screen, and enables input of a target before conversion and a target after conversion for each conversion rule in a plurality of conversion rules on the data conversion procedure input screen, A data conversion device that enables input of the order of application of the plurality of conversion rules, and input of addition and deletion of the conversion rules. The data conversion device according to claim 1,
further comprising a conversion rule history information storage unit that stores the conversion rule acquired by the conversion rule acquisition unit as conversion rule history information;
The conversion rule acquisition unit displays a data conversion procedure input screen, and enables selection input of a plurality of conversion rules from the conversion rules stored in the conversion rule history information storage unit on the data conversion procedure input screen. , a data conversion device capable of inputting the order of application of the plurality of conversion rules. The data conversion device according to claim 1,
further comprising a correction acquisition unit that acquires a correction result of the temporary application result in the conversion table generated by the conversion table generation unit;
The correction acquisition unit acquires the correction result of the converted part when a correction button is pressed in the temporarily applied result of the conversion table displayed on the conversion table confirmation screen output by the conversion table output unit. Then, when the correction completion button is pressed, the correction result is displayed, and when the conversion execution button is pressed, the conversion request is made for the data list together with the updated conversion table reflecting the correction result, Data converter. A data conversion method executed by a data conversion device that converts data based on a conversion rule,
a data list obtaining step for obtaining a data list;
a conversion rule acquisition step of acquiring a plurality of conversion rules as the conversion rules and an order of application of the plurality of conversion rules;
an extracting step of extracting a provisional application target data list, which is a data list to which the conversion rule is provisionally applied, from the data list obtained by the data list obtaining step;
provisionally applying the conversion rule acquired by the conversion rule acquisition step to the provisional application target data list extracted by the extraction step, and a provisional application target data list extracted by the extraction step; a conversion table generating step of generating a conversion table in which the results of the provisional application are associated with each other;
a conversion table output step of outputting the conversion table generated by the conversion table generation step;
a conversion request reception step for receiving a conversion request for the data list after the conversion table is output by the conversion table output step;
in accordance with the conversion request accepted by the conversion request acceptance step, using the plurality of conversion rules as the conversion rules acquired by the conversion rule acquisition step and the order of application of the plurality of conversion rules to obtain the data list; a main application step of performing the main application process for conversion and outputting the result of the main application process;
A data conversion method comprising:

Images