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

Description

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

It has been known to cleanse a large amount of data before analyzing it. An example of this cleansing is a process for eliminating spelling variations.

Patent Document 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 unified and used in the format, and that the content data used in the format is supplemented to this content data file. (Claim 1, abstract, etc.). There is also software that replaces character strings by specifying regular expressions.

Japanese Patent Application Publication No. 2004-341605

The above-mentioned conventional technology performs cleansing based on a predetermined conversion rule or an input conversion rule. By the way, if the user comes up with their own conversion rules, there is a possibility that the information will not be converted into the information desired by the user.

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

SUMMARY OF THE INVENTION Therefore, an object of the present invention is to provide a data conversion device and a data conversion method that provide information for determining whether or not the data has been converted into desired information according to the conversion rules before performing a cleansing process on actual data. There is a particular thing.

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

A brief overview of typical inventions disclosed in this application is as follows.

A data conversion device according to a typical embodiment of the present invention includes a data list acquisition section that acquires a data list, a conversion rule acquisition section that acquires a conversion rule, and a data conversion device that performs conversion from the data list acquired by the data list acquisition section. An extraction unit that extracts a temporary application target data list, which is a data list to which rules are temporarily applied, and a temporary application target data list that applies the conversion rules acquired by the conversion rule acquisition unit to the temporary application target data list extracted by the extraction unit. A conversion table generation unit that applies the application and generates a conversion table that associates the temporary application target data list extracted by the extraction unit with the results of the 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 this application, the effects obtained by typical inventions are briefly explained below.

That is, according to a typical embodiment of the present invention, before performing cleansing processing on actual data, it is possible to provide information for determining whether or not the data has been converted into desired information according to the conversion rule. .

1 is a diagram schematically showing a configuration example of an information processing system including a data conversion device according to an embodiment of the present invention. FIG. 2 is a diagram schematically showing a data list input screen in an embodiment of the present invention. FIG. 2 is a diagram schematically showing a data conversion procedure input screen in an embodiment of the present invention. FIG. 3 is a diagram showing an outline of an example of data stored in a data list storage unit according to an embodiment of the present invention. It is a figure showing the outline of the example of data stored in the conversion rule storage part in one embodiment of the present invention. FIG. 3 is a diagram illustrating an overview of an example of data stored in a unique list storage unit according to an embodiment of the present invention. It is a figure showing an outline of a conversion confirmation screen in one embodiment of the present invention. FIG. 3 is a diagram illustrating an overview of an example of data stored in a conversion table storage unit according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an overview of an example of data conversion history information stored in a conversion history storage unit in an embodiment of the present invention. It is a figure showing an outline of an example of conversion history detail information stored in a conversion history storage part in one embodiment of the present invention. An example of the overall processing flow in which a unique list extracted from a data list in an embodiment of the present invention is temporarily converted and main application is performed to the data list based on the result of the temporary conversion will be summarized. FIG. FIG. 2 is a diagram illustrating an overview of an example of the flow of processing for generating a unique list in an embodiment of the present invention. FIG. 2 is a diagram showing an overview of an example of the flow of processing for generating a conversion table in an embodiment of the present invention. FIG. 3 is a diagram illustrating an overview of an example of the flow of processing for modifying a conversion table according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an overview of an example of the flow of processing for data conversion using a conversion table according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail based on the drawings. In addition, in all the figures for explaining the embodiment, the same parts are given the same reference numerals in principle, and repeated explanations thereof will be omitted. On the other hand, parts described with reference numerals in a certain figure may be referred to with the same reference numerals when describing other figures, although they are not shown again.

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

The data conversion device 100 and the terminal device 200 can send and receive information to each other via the network 300. Network 300 is a wired or wireless network.

The terminal device 200 connected to the data conversion device 100 via the network 300 is an information processing device such as a smartphone 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 in response to an input operation by a user of the terminal device 200. Further, the terminal device 200 displays and outputs the information acquired from the data conversion device 100. Further, the terminal device 200 stores a data list to be converted, in 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 using predetermined hardware and software. For example, the data conversion device 100 and the terminal device 200 include a processor, a memory, and the like. The program on the memory executed by the processor causes the computers of the data conversion device 100 and the terminal device 200 to function. Furthermore, the data conversion device 100 and the terminal device 200 have input means (keyboard, mouse, etc.) and output means (display means such as a display).

The data conversion device 100 of this embodiment includes 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 106.

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

Each of the above-mentioned parts of the data conversion device 100 is implemented as a software program running 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 and obtains contents input to the various input screens in response to requests from the terminal device 200.

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

Here, an example of the data list input screen will be explained using FIG. 2. FIG. 2 is a diagram schematically showing a data list input screen. The data list input screen is a screen for inputting 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. It is a 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 designation box 13, an add column button 14, and a next button 15.

When the file selection button 10 is selected through an input operation by the user of the terminal device 200, the terminal device 200 calls up a screen (not shown) for specifying a file in the data list. Then, when a file in the data list is selected on the screen, the terminal device 200 displays the file name (including the storage path) of the file in the selected file area 11.

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

In the example of FIG. 2, a data list regarding company names is displayed, and there are 11 items. Note that it is not necessary to display all the data in the data list, and only a 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, is all full-width. Furthermore, for "ABC Systems Co., Ltd." whose record ID is 2, the "systems" part is a half-width character. Furthermore, the part in parentheses for "EF Software Co., Ltd." whose record ID is 11 is a half-width character. Also, since the notation is not unified, with some records being written as "Co., Ltd." and others being written as "Corporation Corporation," 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, which will be described later, is applied. For example, read the part of the data list where column names are defined and display it in a drop-down list. The column specified in the change target column specification box 13 becomes the column to which the conversion rule is applied.

The column addition button 14 is a button for adding a column specification box 13 to be changed. This allows multiple columns to be specified. When the next button 15 is pressed, the terminal device 200 determines the data list file and the column to be changed (retains the contents of the data list file and the column to be changed in memory, etc.), and saves the data. A request is made to the conversion device 100 to send a data conversion procedure input screen.

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

Here, an example of the data conversion procedure input screen will be explained using FIG. 3. FIG. 3 is a diagram schematically showing a data conversion procedure input screen. The data conversion procedure input screen is a screen for inputting rules for converting a data list (conversion rules). Specifically, it has a conversion rule input area 20, a procedure addition button 21, a procedure deletion button 22, and a next button 23.

The conversion rule input area 20 is an area for inputting a pre-conversion target (for example, character string, character input mode) and a post-conversion target in the conversion rule, and an area for inputting the conversion rule procedure (application of multiple conversion rules). This is an area that defines the 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 is to be converted to full-width kana. Second, a conversion rule is defined that indicates that the character string ``Corporation'' (the parentheses for ``stock'' are full-width characters) is to be converted to ``stock''. Third, a conversion rule is defined that indicates that a corporation is to be converted to a blank.

The plurality of conversion rules shown in FIG. 3 are rules for converting all katakana names to full-width characters and removing the notation indicating a corporation (including "Corporation Co., Ltd.") all at once.

Further, when the procedure addition button 21 is pressed, the terminal device 200 additionally displays a conversion rule input area 20. In the example of FIG. 3, when the add procedure 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 finalizes the plurality of conversion rules and the procedure of the conversion rule, and saves the data list, the plurality of conversion rules, and the procedure of the conversion rule. The information is sent to the conversion device 100 to request provisional application of conversion rules.

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 temporary application request, and also acquires the data list, a plurality of conversion rules, and the procedure of the conversion rules. In this way, the input screen interface section 101 functions as a data list acquisition section. The input screen interface section 101 also functions as a conversion rule acquisition section. As described above, upon acquiring the data list, the input screen interface unit 101 generates an ID (data ID) that identifies the data list, associates the ID with the data list, and stores the data list in the data list storage unit 102. Register to.

Here, an example of data stored in the data list storage unit 102 will be explained using FIG. 4. FIG. 4 is a diagram showing an overview of an example of data stored in the data list storage unit 102. As shown in FIG. 4, the data list storage unit 102 stores a data ID, a record ID, and a pre-conversion list indicating list data before conversion in association with each other.

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) that identifies the current conversion. The input screen interface unit 101 associates the conversion rule ID, the procedure (procedure of the conversion rule), and the conversion rule (before conversion and after conversion) and registers them in the conversion rule storage unit 103.

Note that the input screen interface unit 101 may store the character string itself of the conversion rule, may store a regular expression, or may store a function of a programming language. Note that the input screen interface unit 101 may store information associating conversion rule IDs with conversion target columns.

Here, an example of data stored in the conversion rule storage unit 103 will be explained using FIG. 5. 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. 5, the conversion rule storage unit 103 stores conversion rule IDs, procedures, before conversion, and after conversion in association with each other.

In this way, the conversion rule storage unit 103 stores the 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 section 103 functions as a conversion rule history information storage section.

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

The extraction unit 104 is a part that extracts a temporary application target data list, which is a data list to which a conversion rule is temporarily applied, from the data list acquired by the input screen interface unit 101. Upon 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.

Further, the extraction unit 104 refers to the conversion rule storage unit 103 and obtains 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 a unique list, refers to the conversion target columns of the acquired records one by one, and if the conversion target column does not exist in the unique list, stores the value of the conversion target column of the record in the unique list. Furthermore, 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 a unique list obtained by referring to all the values of the conversion target column of the acquired record, the extraction unit 104 registers the unique list in the unique list storage unit 105 in association with the data ID. Furthermore, when there are multiple conversion target columns, the extraction unit 104 may further associate the conversion target column IDs 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 explained using FIG. 6. 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. 6, the unique list storage unit 105 stores data IDs and company names, which are conversion target columns, in association with each other.

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

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

Although the case has been described in which the extraction unit 104 generates the unique list as the temporary application target data list, it may also extract all the conversion target columns of the acquired record as the temporary application target data list.

The conversion table generation unit 106 is a unit 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 in accordance with the order of application. Further, the conversion table generation unit 106 is a part that generates a conversion table that associates the temporary application target data list extracted by the extraction unit 104 with the results of the temporary application.

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

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

The conversion table generation unit 106 sends the conversion confirmation screen, data ID, and conversion rule ID to the 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 acquiring the conversion confirmation screen, data ID, and conversion rule ID, the conversion table output unit 107 sends the conversion confirmation screen to the terminal device 200 . In this way, the conversion table output unit 107 outputs the conversion table. Upon acquiring the conversion confirmation screen, the terminal device 200 displays the conversion confirmation screen.

Here, an example of the conversion confirmation screen will be explained using FIG. 7. FIG. 7 is a diagram schematically showing a conversion confirmation screen. The conversion confirmation screen is a screen for confirming the conversion result when the data list is converted (that is, when it is temporarily applied).

As shown in FIG. 7, records other than those with half-width parentheses are converted to character strings with "Corporation" or "Corporation" removed, and half-width katakana are converted to full-width katakana.

The conversion confirmation screen includes 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 that displays a conversion table that associates a unique list before conversion with a result of converting the unique list. Note that if there are multiple conversion target columns, there is a conversion table for each conversion target column.

The modification button 32 is a button that indicates a request to modify the content after conversion. When the user of the terminal device 200 presses the correction button 32 through an input operation, the terminal device 200 makes the converted portion of the conversion table editable.

In the example of FIG. 7, it is conceivable to modify the part of EF Software Co., Ltd. that has half-width parentheses to remove it.

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

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

Returning to FIG. 1, the conversion request accepting unit 108 is a part that accepts a request for converting a data list after the conversion table output unit 107 outputs the conversion table.

The conversion request receiving unit 108 obtains the latest conversion table and also receives a request for converting a data list. Note that the conversion request reception unit 108 may acquire all conversion tables for each conversion target column. In this way, the conversion request reception unit 108 functions as a modification acquisition unit. Note that the conversion request reception unit 108 may acquire all conversion tables for each conversion target column. The conversion request reception unit 108 generates an ID (conversion table ID) for the latest conversion table. Note that when the conversion request reception unit 108 obtains conversion tables 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 reception unit 108 may generate information that can specify the conversion target column corresponding to the conversion table ID. For example, the conversion request reception unit 108 may associate the conversion table ID with the conversion target column name.

Further, the conversion request reception unit 108 assigns an ID (conversion statement detail ID) to each record of the latest conversion table. The conversion request reception unit 108 stores information in which the conversion table ID, the conversion request 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 explained using FIG. 8. 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. 8, the conversion table storage unit 109 stores the conversion table ID, conversion table detail ID, before conversion (the part before conversion of the latest conversion table), and after conversion (the part after conversion of the latest conversion table). ) are stored in association with each other.

Returning to FIG. 1, since the conversion request reception unit 108 obtains the latest conversion table, the modified conversion table is reflected. That is, the conversion request reception unit 108 functions as a modification reception unit.

The conversion request reception unit 108 acquires the data ID and conversion rule ID from the conversion table output unit 107 and sends the data ID, conversion rule ID, and conversion table ID to the main application unit 110.

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

The application unit 110 obtains the data ID, conversion rule ID, and conversion table ID. The application unit 110 refers to the data list storage unit 102 and obtains the data list corresponding to the data ID. Further, the application unit 110 generates an ID (change history ID) determined for each application, and associates the change history ID, conversion date, data ID, conversion rule ID, and conversion table ID. The converted information (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 explained using FIG. 9. FIG. 9 is a diagram illustrating an overview of an example of data conversion history information stored in the conversion history storage unit 111. 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 if 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, Convert the value of the change target column of the record in the data list to the converted content of the record in the change table.

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

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

The application unit 110 stores information (conversion history detailed information) in which the change history ID, the record ID of the data in the converted data list, and the conversion statement detail ID of the record in the conversion table are associated with each other in the conversion history storage unit 111. Store it in

Here, an example of the conversion history detailed information stored in the conversion history storage unit 111 will be explained using FIG. 10. FIG. 10 is a diagram showing an overview of an example of conversion history detailed information stored in the conversion history storage unit 111. As shown in FIG. 10, the conversion history storage unit 111 stores information in which conversion history IDs, record IDs, and conversion statement details IDs are associated with each other.

In this way, the conversion history storage unit 111 converts the data (record ID) of the data list converted by the main application unit 110 and the data (conversion table) temporarily applied by the conversion table generation unit 106. It stores information that is associated with the information used to perform the conversion (conversion statement detail ID). Since the information corresponds to the conversion execution history, the conversion history storage section 111 functions as a conversion execution history storage section.

In this case, since the data conversion device 100 stores a history of conversion, it can store information that allows confirmation of which data has been converted, and by referring to this information, the user can determine whether the conversion has been performed appropriately. be able to.

When the application unit 110 refers to the data lists corresponding to the data ID one by one and determines whether there is any data that matches the data in all the data lists before converting the records in the conversion table, This application processing ends. 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, obtains 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 overall processing flow in this embodiment, in which a unique list extracted from a data list is temporarily converted, and the data list is actually applied based on the result of the temporary conversion. FIG.

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, a 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 procedure 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 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 in accordance with the application order. The conversion table generation unit 106 also generates a conversion table that associates the temporary application target data list extracted by the extraction unit 104 with the results of the temporary application, and displays a conversion confirmation screen including the conversion table on the terminal device 200. Send (S3).

When the terminal device 200 receives the input of a conversion table modification request, it performs a process of modifying the conversion table (conversion table modification process) and issues a data list conversion request (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).

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

The extraction unit 104 initializes the unique list (S11). Subsequently, the extraction unit 104 reads the data list (S12). If there is an unobtained row (record) (S13: Yes), the extraction unit 104 obtains one unobtained 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 the process advances to step S13. Note that in step S16, if the value is included in the unique list (S16: No), the process advances to step S13. Further, in step S13, if there is no unobtained row (S13: No), the process ends.

<Processing flow (conversion table generation process)>
FIG. 13 is a diagram illustrating an overview of an example of the flow of processing for generating a conversion table in this embodiment. 12 is a diagram showing details of the process of step S3 in the flowchart of FIG. 11. FIG. First, the conversion table generation unit 106 initializes the conversion table (S21). Subsequently, the conversion table generation unit 106 obtains the unique list and reads the unique list (S22). If there is an unobtained unique list (S23: Yes), the conversion table generation unit 106 obtains one row (record) of the unobtained unique list (S24). The conversion table generation unit 106 applies conversion rules to the obtained values in the order of conversion (S25), and adds information associating the values (values before conversion) with the application results (after conversion) to the conversion table. (S26), and the process advances to step S23. Further, in step S23, if there is no unobtained row (S23: No), the process ends.

<Processing flow (correction processing)>
FIG. 14 is a diagram illustrating an overview of an example of the flow of processing for modifying a conversion table in this embodiment. 12 is a diagram showing details of the process in step S4 of the flowchart in FIG. 11. FIG. First, upon acquiring the conversion confirmation screen from the data conversion device 100, the terminal device 200 displays the conversion confirmation screen (S31). When the correction button 32 on the conversion confirmation screen is pressed to request correction of the conversion table 31 (S32: Yes), the terminal device 200 makes the conversion table 31 editable, and the correction information of 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 with the updated conversion table 31 (S35). Furthermore, if a request to modify the conversion table 31 is not made (S32: No), the process ends.

<Processing flow (data conversion process)>
FIG. 15 is a diagram illustrating an overview of an example of the flow of data conversion processing using a conversion table in this embodiment. 12 is a diagram showing details of the process in step S5 of the flowchart in FIG. 11. FIG. First, when the conversion request reception unit 108 receives a data list conversion request, the main application unit 110 reads the data list by acquiring the data list corresponding to the data ID to be converted from the data list storage unit 102. (S41).

Next, 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 receiving unit 108, and stores the data conversion history information in the conversion history storage unit 111. (S42). If there is an unconverted row (S43: Yes), the application unit 110 acquires one unconverted row (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 an unconverted value that matches the acquired value (S46), and converts the acquired value to the converted value of the record in the searched conversion table (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 statement detail ID of the record in the conversion table (S48), and in step S43 Proceed to. Note that in step S46, if the value before conversion that matches the acquired value cannot be retrieved from the conversion table, the process skips steps S47 and S48 and proceeds to step S43. Further, in step S43, if there are no unconverted rows (S43: No), the process ends.

In the above embodiment, on the data conversion procedure input screen, there is an area for inputting a target before conversion (for example, character string, character input mode), a target after conversion, and a case where new input of the conversion order is accepted. I talked about it. Instead, on the data conversion procedure input screen, the input screen interface unit 101 receives a selection of a plurality of conversion rules stored in the conversion rule storage unit 103 and the application order of the plurality of conversion rules, and The plurality of selected conversion rules and the application order of the plurality of conversion rules may be acquired.

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

In the above embodiment, an information processing system including 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, a case has been described in which the input screen interface unit 101 acquires a plurality of conversion rules and the application order of the plurality of conversion rules, but even if it acquires a single conversion rule. good.

As described above, in the data conversion device 100 that is an embodiment of the present invention, the input screen interface unit 101 acquires a data list and acquires conversion rules. Further, the extraction 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 generation unit 106 temporarily applies the conversion rules to the temporary application target data list according to the order of application, generates a conversion table that associates the temporary application target list with the result of the temporary application, and generates a conversion table. The output unit 107 outputs the conversion table.

In this way, the data conversion device 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. and output a conversion table containing the applied results. As a result, the data conversion device 100 can provide information for determining whether or not the actual data has been converted into desired information according to the conversion rule, before performing the cleansing process on the actual data.

Further, the extraction unit 104 extracts a unique list as a temporary application target list. Thereby, the data conversion device 100 can generate a non-redundant conversion table, use the conversion table to appropriately convert the data list, and easily check whether the data list has been converted into desired information using conversion rules. It is possible to provide information for making decisions.

Further, when the conversion request reception unit 108 accepts a data list conversion request, the main application unit 110 converts the data list using information based on conversion rules. In this way, the data conversion device 100 converts the data list after outputting the conversion table, so it is possible to convert the data list 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. Thereby, the data conversion device 100 converts the data list using the conversion table, so that processing can be executed more easily than when applying conversion rules to the data list.

Further, since the application unit 110 applies the modified 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 explained based on the embodiments above, the present invention is not limited to the above embodiments, and can be modified in various ways without departing from the gist thereof. Needless to say. For example, the embodiments described above are described in detail to explain the present invention in an easy-to-understand manner, and the present invention is not necessarily limited to having all the configurations described. Furthermore, it is possible to add, delete, or replace some of the configurations of the above embodiments with other configurations.

INDUSTRIAL APPLICATION This invention can be utilized for the apparatus which converts data.

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

Claims (6)

A data conversion device that converts data based on conversion rules,
a data list acquisition unit that acquires a data list;
a conversion rule acquisition unit that acquires a plurality of conversion rules as the conversion rules and an application order of the plurality of conversion rules;
an extraction unit 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 data list acquisition unit;
A temporary application target data list extracted by the extraction unit by temporarily applying the conversion rule acquired by the conversion rule acquisition unit to the temporary application target data list extracted by the extraction unit; a conversion table generation unit that generates a conversion table that associates the tentatively applied results;
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 output unit outputs the conversion table;
In response to a conversion request received by the conversion request reception unit, the data list is created using the plurality of conversion rules and the order of application of the plurality of conversion rules as conversion rules acquired by the conversion rule acquisition unit. a main application unit that performs the main application processing for conversion and outputs the result of the main application processing;
Equipped with
The extraction unit is a data conversion device that 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 extraction unit is a data conversion device that extracts, as the temporary application target data list, all data in conversion target columns of the acquired record from among the data list acquired by the data list acquisition unit. The data conversion device according to claim 1,
The conversion rule acquisition unit displays a data conversion procedure input screen, and allows 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 allows inputting the order of application of the plurality of conversion rules, and allows inputting 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 allows selection and 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 that allows inputting the order of application of the plurality of conversion rules. The data conversion device according to claim 1,
further comprising a modification acquisition unit that acquires a modification result of a temporary application result in the conversion table generated by the conversion table generation unit,
The correction acquisition unit acquires the correction result of the post-conversion part when a correction button is pressed in the result of provisional application in the conversion table displayed on the conversion table confirmation screen output by the conversion table output unit. and displaying the correction results when a correction completion button is pressed, and requesting conversion of the data list together with an updated conversion table that reflects the correction results when a conversion execution button is pressed. Data conversion device. A data conversion method executed by a data conversion device that converts data based on conversion rules, the method comprising:
a data list acquisition step of acquiring a data list;
a conversion rule acquisition step of acquiring a plurality of conversion rules as the conversion rules and an application order of the plurality of conversion rules;
an extraction step of 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 in the data list acquisition step;
A temporary application target data list extracted by the extraction step by temporarily applying the conversion rule acquired by the conversion rule acquisition step to the temporary application target data list extracted by the extraction step; a conversion table generation step of generating a conversion table that associates the tentatively applied results;
a conversion table output step of outputting the conversion table generated by the conversion table generation step;
a conversion request receiving step of receiving a conversion request for the data list after the conversion table is output in the conversion table output step;
In response to the conversion request accepted by the conversion request receiving step, the data list is created using the plurality of conversion rules and the order of application of the plurality of conversion rules as the conversion rules obtained by the conversion rule obtaining step. a main application step of performing main application processing to convert and outputting a result of the main application processing;
has
In the data conversion method, the extraction step extracts a unique list, which is a unique data list, from among the data lists acquired in the data list acquisition step, as the temporary application target data list.

Images