Abstract:
A non-transitory computer-readable recording medium stores a data conversion program that converts pre-conversion type-format data for a first model of an image forming apparatus into post-conversion type-format data for a second model of the image forming apparatus. The data conversion program causes a computer to function as: i) a common-format conversion unit configured to convert the pre-conversion type-format data into common-format data of format independent of the model based on pre-conversion-data conversion rule information that indicates a rule for converting between the pre-conversion type-format data and the common-format data; and ii) a type-format conversion unit configured to convert the common-format data generated by the common-format conversion unit into the post-conversion type-format data based on post-conversion-data conversion rule information that indicates a rule for converting between the post-conversion type-format data and the common format data.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
       [0001]    This application is based upon, and claims the benefit of priority from, corresponding Japanese Patent Application No. 2013-016689 filed in the Japan Patent Office on Jan. 31, 2013, the entire contents of which are incorporated herein by reference. 
       BACKGROUND 
       [0002]    Unless otherwise indicated herein, the description in this section is not prior art to the claims in this application and is not admitted to be prior art by inclusion in this section. 
         [0003]    In an image forming apparatus, there is a typical program that converts data in accordance with a change in application version. The typical program converts the data in the image forming apparatus of the same. 
         [0004]    To date, various image forming apparatus models have been developed and released. Each model uses type-format data of format depending on the model itself. The type-format data includes individual values as type-format values that each belong to a type-format item. Recently, adding new functions to new models or the like increases the number of type-format items. Accordingly, in the case where a user purchases a new image forming apparatus model and changes the currently-used image forming apparatus to the new one, the user places importance that the type-format data for the currently-used image forming apparatus can be easily converted into type-format data for the new image forming apparatus. 
       SUMMARY 
       [0005]    The present disclosure provides a non-transitory computer-readable recording medium storing a data conversion program that converts pre-conversion type-format data for a first model of an image forming apparatus into post-conversion type-format data for a second model of the image forming apparatus. The data conversion program causes a computer to function as: i) a common-format conversion unit configured to convert the pre-conversion type-format data into common-format data of format independent of the model based on pre-conversion-data conversion rule information that indicates a rule for converting between the pre-conversion type-format data and the common-format data; and ii) a type-format conversion unit configured to convert the common-format data generated by the common-format conversion unit into the post-conversion type-format data based on post-conversion-data conversion rule information that indicates a rule for converting between the post-conversion type-format data and the common format data. 
         [0006]    These as well as other aspects, advantages, and alternatives will become apparent to those of ordinary skill in the art by reading the following detailed description with reference where appropriate to the accompanying drawings. Further, it should be understood that the description provided in this summary section and elsewhere in this document is intended to illustrate the claimed subject matter by way of example and not by way of limitation. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0007]    In the accompanying drawings: 
           [0008]      FIG. 1  is a schematic diagram illustrating a relationship between a data conversion apparatus and multifunction peripherals (MFPs) according to one embodiment of the present disclosure. 
           [0009]      FIG. 2  is a schematic diagram illustrating exemplary type-format data for currently-used MFP among the two MFPs. 
           [0010]      FIG. 3  is a schematic diagram illustrating the type-format data in  FIG. 2  that is represented in table format. 
           [0011]      FIG. 4  is a schematic diagram illustrating the exemplary type-format data that is represented in the table format for new MFP among the two MFPs. 
           [0012]      FIG. 5  is a block diagram illustrating a configuration of the data conversion apparatus. 
           [0013]      FIG. 6  is a schematic diagram illustrating one conversion rule information among the two conversion rule information in  FIG. 5 . 
           [0014]      FIG. 7  is a schematic diagram illustrating the other conversion rule information among the two conversion rule information in  FIG. 5 . 
           [0015]      FIG. 8  is a schematic diagram of the exemplary common-format data generated by the data conversion apparatus. 
           [0016]      FIG. 9  is a flowchart illustrating operations of the data conversion apparatus. 
           [0017]      FIG. 10  is a flowchart illustrating operations of a common-format conversion unit in  FIG. 5  for writing a common-format value. 
           [0018]      FIG. 11  is a schematic diagram illustrating exemplary common-format null data used by the data conversion apparatus. 
           [0019]      FIG. 12  is a flowchart illustrating operations of a type-format conversion unit illustrated in  FIG. 5  for writing a type-format value. 
       
    
    
     DETAILED DESCRIPTION 
       [0020]    Example apparatuses are described herein. Other example embodiments or features may further be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented herein. In the following detailed description, reference is made to the accompanying drawings, which form a part thereof. 
         [0021]    The example embodiments described herein are not meant to be limiting. It will be readily understood that the aspects of the disclosure, as generally described herein, and illustrated in the drawings, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are explicitly contemplated herein. 
         [0022]    The following describes one embodiment of this disclosure using the drawings. 
         [0023]    First, a configuration of a data conversion apparatus  10  according to the embodiment will be described. 
         [0024]      FIG. 1  is a schematic diagram illustrating the relationship between the data conversion apparatus  10 , and an MFP 91 and an MFP 92. 
         [0025]    As illustrated in  FIG. 1 , the data conversion apparatus  10  is an apparatus that converts currently used type-format data for a multifunction peripheral (MFP)  91  into type-format data for new MFP 92 when a user of the MFP 91 as an image forming apparatus purchases a new image forming apparatus, the MFP 92, and changes the model from the MFP 91 to the MFP 92. The data conversion apparatus  10  is used by a serviceman, for example. 
         [0026]    MFP 91 and MFP 92 each store an address book, a user list, a department list, and apparatus setting information. The address book includes various addresses, such as a FAX address and an e-mail address, for each of user or department. The user list includes various information on a user, such as a user name and a user password. The department list includes various information on a department, such as a department name and a department password. The apparatus setting information includes various setting information on the MFP itself, such as a sleep mode setting. The MFP 91 and the MFP 92 each have an export function and an import function. The export function exports various information registered with the MFP itself, such as the address book, the user list, the department list, and the apparatus setting information, as type-format data. The import function imports the type-format data as various information, such as the address book, the user list, the department list, and the apparatus setting information, registered with the MFP itself. The MFP 91 and the MFP 92 send the type-format data exported to the outside and reads the type-format data imported from the outside via, for example, a Universal Serial Bus (USB) memory. 
         [0027]      FIG. 2  is a schematic diagram of exemplary type-format data for the MFP 91. 
         [0028]    The type-format data is binary data uniquely processed by, for example, compressing Comma-Separated Values (CSV) format data and adding various information to the compressed CSV format data. The various information includes information on the MFP model compatible with the type-format data (hereinafter referred to as “model information”) and information on a type of contents in the type-format data, such as the address book, the user list, the department list, and the apparatus setting information (hereinafter referred to as “data type information”). The type-format data can be referred to and edited only by use of a data conversion program  14   a  (see  FIG. 5 ), which will be described later. The type-format data for the MFP 91 can be converted into CSV format data as illustrated in  FIG. 2 . The type-format data illustrated in  FIG. 2  corresponds to the user list. As illustrated in  FIG. 2 , the first line of the type-format data arrays type-format items to which type-format values, individual values in the type-format data, belong. Each line of the second line or later of the type-format data is a line corresponding to individual data in the type-format data. Each line of the second line or later of the type-format data is a line where type-format values are arrayed. That is, the type-format data is data where the type-format items are expressed in accordance with the order in a series of the type-format values. 
         [0029]      FIG. 3  is a schematic diagram illustrating the type-format data illustrated in  FIG. 2  that is represented in table format. 
         [0030]    When the type-format data illustrated in  FIG. 2  is expressed in table format for ease of understanding, the type-format data is as illustrated in  FIG. 3 . In the type-format data illustrated in  FIG. 3 , the access level (access_level) “2” denotes a general user and the access level “1” denotes an administrator. 
         [0031]      FIG. 4  is a schematic diagram illustrating exemplary type-format data for the MFP 92 that is represented in table format. 
         [0032]    In the type-format data illustrated in  FIG. 4 , the access level (access_level) “1” denotes a general user and the access level “0” denotes an administrator. Different from the type-format data illustrated in  FIG. 3 , the type-format data illustrated in  FIG. 4  does not include a type-format item referred to as an e-mail address (e-mail_address). Different from the type-format data illustrated in  FIG. 3 , the type-format data illustrated in  FIG. 4  includes a type-format item referred to as a password mode (password_mode). 
         [0033]      FIG. 5  is a block diagram illustrating the configuration of the data conversion apparatus  10 . 
         [0034]    As illustrated in  FIG. 5 , the data conversion apparatus  10  includes a operation unit  11 , a display unit  12 , a communication unit  13 , a storage unit  14 , and a control unit  15 . The operation unit  11  is an input device, such as a computer mouse and a keyboard, to which various operations are input by the user. The display unit  12  is a display device, such as a Liquid Crystal Display (LCD), that displays various information. The communication unit  13  is a communication device for communications with an external device. The storage unit  14  is a non-volatile storage device, such as a Hard Disk Drive (HDD), that stores various data. The control unit  15  controls the entire data conversion apparatus  10 . The data conversion apparatus  10  is configured by, for example, a computer such as a Personal Computer (PC). 
         [0035]    The storage unit  14  stores the data conversion program  14   a  executed by the data conversion apparatus  10 . The data conversion program  14   a  is type-format data of format dependent on the MFP model. The data conversion program  14   a  converts pre-conversion type-format data, which is for a given model, into post-conversion type-format data, which is type-format data for a model different from the model. The data conversion program  14   a  may be installed on the data conversion apparatus  10  at a production stage of the data conversion apparatus  10 , may be additionally installed on the data conversion apparatus  10  from a storage medium such as a Compact Disk (CD), a Digital Versatile Disk (DVD), and a USB flash drive, or may be additionally installed on the data conversion apparatus  10  via a network. 
         [0036]    The storage unit  14  stores conversion rule information  14   b  and conversion rule information  14   c . The conversion rule information  14   b  is the conversion rule information showing a rule for converting the type-format data and the common-format data of format independent of MFP model. The conversion rule information  14   b  is stored as pre-conversion-data conversion rule information, which is conversion rule information for the pre-conversion type-format data. The conversion rule information  14   c  is stored as post-conversion-data conversion rule information, which is conversion rule information for the post-conversion type-format data. 
         [0037]      FIG. 6  is a schematic diagram illustrating the conversion rule information  14   b .  FIG. 7  is a schematic diagram illustrating the conversion rule information  14   c.    
         [0038]    As illustrated in  FIG. 6  and  FIG. 7 , the conversion rule information  14   b  and the conversion rule information  14   c  are Extensible Markup Language (XML) definition files. 
         [0039]      FIG. 8  is a schematic diagram illustrating exemplary common-format data generated by the data conversion apparatus  10 . 
         [0040]    The common-format data illustrated in  FIG. 8  is an XML file. The common-format data illustrated in  FIG. 8  includes common-format values (for example, “user001” and “9317”) and common-format items (for example, “UserLogin” and “UserPassword”) related with one another in the common-format data. The common-format value is an individual value in the common-format data. The common-format item is an item to which the common-format value belongs. Here, the common-format items are expressed as an element of each tag, for example, “UserLogin,” “UserPassword,” “EMailAddress,” “UserAuthority,” and “PasswordMode.” The common-format value is expressed as a content sandwiched between a start tag and an end tag. 
         [0041]    The control unit  15  illustrated in  FIG. 5  includes, for example, a Central Processing Unit (CPU), a Read Only Memory (ROM), which preliminary stores a program and various data, and a Random Access Memory (RAM), which is employed as a work area for the CPU. The CPU runs a program stored in the ROM or the storage unit  14 . 
         [0042]    The control unit  15  functions as a common-format conversion unit  15   a , a type-format conversion unit  15   b , and a data editing unit  15   c . The common-format conversion unit  15   a  converts pre-conversion type-format data into common-format data based on the conversion rule information  14   b  on the storage unit  14  by running the data conversion program  14   a  stored in the storage unit  14 . The type-format conversion unit  15   b  converts the common-format data generated by the common-format conversion unit  15   a  into the post-conversion type-format data based on the conversion rule information  14   c  on the storage unit  14 . The data editing unit  15   c  edits the common-format data generated by the common-format conversion unit  15   a.    
         [0043]    Next, operations of the data conversion apparatus  10  will be described. 
         [0044]      FIG. 9  is a flowchart illustrating the operations of the data conversion apparatus  10 . 
         [0045]    As illustrated in  FIG. 9 , when the common-format conversion unit  15   a  of the control unit  15  of the data conversion apparatus  10  is instructed to convert the pre-conversion type-format data, which is the type-format data to which information such as the address book, the user list, the department list, and the apparatus setting information of the MFP 91, is exported by the MFP 91, into the common-format data via the operation unit  11 , the common-format conversion unit  15   a  converts the pre-conversion type-format data input to the data conversion apparatus  10  via, for example, the USB flash drive into the common-format data based on the conversion rule information  14   b  (S 101 ). 
         [0046]    The common-format conversion unit  15   a  performs a process shown in  FIG. 10  when writing a common-format value. 
         [0047]      FIG. 10  is a flowchart illustrating the operations of the common-format conversion unit  15   a  for writing a common-format value. 
         [0048]    As illustrated in  FIG. 10 , the common-format conversion unit  15   a  determines whether “Value” is included in the applied rule or not (S 131 ). Here, “Value” is a rule for correlation of the type-format value with the common-format value. 
         [0049]    If the common-format conversion unit  15   a  determines that “Value” is not included in the applied rule at S 131 , the common-format conversion unit  15   a  writes the type-format value as the common-format value (S 132 ) as it is and ends the operation shown in  FIG. 10 . 
         [0050]    On the other hand, if the common-format conversion unit  15   a  determines that “Value” is included in the applied rule at S 131 , the common-format conversion unit  15   a  writes the common-format value related with the type-format value in “Value” (S 133 ) and ends the operation shown in  FIG. 10 . 
         [0051]    The following describes a case where the type-format data illustrated in  FIG. 3 , namely, the pre-conversion type-format data is converted into the common-format data using an example of user list. 
         [0052]    The common-format conversion unit  15   a  reads the conversion rule information  14   b  corresponding to the model information in the pre-conversion type-format data, “MFP — 01,” from the storage unit  14 . Then, the common-format conversion unit  15   a  generates the common-format data illustrated in  FIG. 8  based on the rule corresponding to the data type information in the pre-conversion type-format data, “user_list,” among the conversion rule information  14   b  illustrated in  FIG. 6 . Specifically, the common-format conversion unit  15   a  applies the rule corresponding to the column number of the type-format value among the rules corresponding to “user_list” in the conversion rule information  14   b  to the type-format value in the pre-conversion type-format data so as to generate the common-format data. 
         [0053]    First, the common-format conversion unit  15   a  generates a start tag and an end tag with element name of “Data001” corresponding to “data 1” of the pre-conversion type-format data. The common-format conversion unit  15   a  writes the common-format null data, which is common-format data with null value illustrated in  FIG. 11 , to the area sandwiched between the start tag and the end tag. 
         [0054]    Next, the common-format conversion unit  15   a  writes “user001” to “UserLogin” in the common-format null data between the start tag and the end tag with the element name of “Data001” as a common-format value related in the common-format null data (S 132 ). “user001” is a type-format value of the column number “1” in “data 1” in the pre-conversion type-format data. “UserLogin” is the common-format item (NodeName) for “No. 1” related with the column number “1” in the conversion rule information  14   b.    
         [0055]    Next, the common-format conversion unit  15   a  writes “9317” to “UserPassword” in the common-format null data between the start tag and the end tag with the element name of “Data001” as a common-format value related in the common-format null data (S 132 ). “9317” is a type-format value of the column number “2” in “data 1” in the pre-conversion type-format data. “UserPassword” is the common-format item (NodeName) for “No. 2” related with the column number “2” in the conversion rule information  14   b.    
         [0056]    Next, the common-format conversion unit  15   a  writes “001 @xxxxx” to “EMailAddress” in the common-format null data between the start tag and the end tag with the element name of “Data001” as a common-format value related in the common-format null data (S 132 ). “001@xxxxx” is a type-format value of the column number “3” in “data 1” in the pre-conversion type-format data. “EMailAddress” is the common-format item (NodeName) for “No. 3” related with the column number “3” in the conversion rule information  14   b.    
         [0057]    Next, since “Value” is included in the rule of “No. 4” related with the column number “4” in the conversion rule information  14   b  (YES at S 131 ), the common-format conversion unit  15   a  writes “0” to “UserAuthority” in the common-format null data between the start tag and the end tag with the element name of “Data001” as a common-format value related in the common-format null data (S 133 ). “0” is a common-format value where “2,” the type-format value of the column number “4” in “data 1” in the pre-conversion type-format data, is related as “No. 2” in “Value.” “UserAuthority” is the common-format item (NodeName) for “No. 4” related with the column number “4” in the conversion rule information  14   b.    
         [0058]    Next, the common-format conversion unit  15   a  also reflects the type-format values of the column number “5” or later in “data 1” in the pre-conversion type-format data to the common-format data, similarly to the type-format values of the column number up to “4 in “data 1” in the pre-conversion type-format data. 
         [0059]    Next, the common-format conversion unit  15   a  also reflects each type-format value in “data 2” in the pre-conversion type-format data to the common-format data, similarly to the information in “data 1.” Here, since “Value,” which is the rule for correlating the type-format value and the common-format value, is included in the rule of “No. 4” related with the column number “4” in the conversion rule information  14   b  (YES at S 131 ), the common-format conversion unit  15   a  writes “1” to “UserAuthority” in the common-format null data between the start tag and the end tag with the element name of “Data002” as a common-format value related in the common-format null data (S 133 ). “1” is a common-format value where the type-format value of the column number “4” in “data 2” in the pre-conversion type-format data is related as “No. 1” in “Value.” “UserAuthority” is the common-format item (NodeName) for “No. 4” related with the column number “4” in the conversion rule information  14   b.    
         [0060]    Next, the common-format conversion unit  15   a  also reflects each type-format value in “data 3” or later in the pre-conversion type-format data to the common-format data, similarly to the information in “data 1” or “data 2” in the pre-conversion type-format data. 
         [0061]    As illustrated in  FIG. 9 , the data editing unit  15   c  of the control unit  15  of the data conversion apparatus  10  displays the common-format data generated at S 101  on the display unit  12  and edits the common-format data in accordance with an instruction via the operation unit  11  (S 102 ). The process in S 102  can be omitted. 
         [0062]    Next, assume that the type-format conversion unit  15   b  of the control unit  15  of the data conversion apparatus  10  is instructed to convert the common-format data into the post-conversion type-format data via the operation unit  11 . Then, in the case where the common-format data is not edited by the data editing unit  15   c  at S 102 , the common-format data generated by the common-format conversion unit  15   a  is converted into the post-conversion type-format data based on the conversion rule information  14   c  on the storage unit  14  (S 103 ) and ends the process illustrated in  FIG. 9 . In the case where the common-format data is edited by the data editing unit  15   c  at S 102 , the common-format data edited by the data editing unit  15   c  is converted into the post-conversion type-format data based on the conversion rule information  14   c  on the storage unit  14  (S 103 ) and ends the process shown in  FIG. 9 . 
         [0063]    When writing the type-format value, the type-format conversion unit  15   b  performs the processes shown in  FIG. 12 . 
         [0064]      FIG. 12  is a flowchart illustrating the operations of the type-format conversion unit  15   b  for writing a type-format value. 
         [0065]    As shown in  FIG. 12 , the type-format conversion unit  15   b  determines whether the common-format value is a null value or not (S 161 ). 
         [0066]    When the type-format conversion unit  15   b  determines that the common-format value is not a null value at S 161 , the type-format conversion unit  15   b  determines whether “Value” is included in the applied rule or not (S 162 ). 
         [0067]    If the type-format conversion unit  15   b  determines that “Value” is not included in the applied rule at S 162 , the type-format conversion unit  15   b  writes the common-format value as the type-format value (S 163 ) as it is and ends the operation shown in  FIG. 12 . 
         [0068]    On the other hand, if the type-format conversion unit  15   b  determines that the applied rule does not include “Value” at S 162 , the type-format conversion unit  15   b  writes the type-format value related with the common-format value in “Value” (S 164 ) and ends the operation shown in  FIG. 12   
         [0069]    If the type-format conversion unit  15   b  determines that the common-format value is a null value at S 161 , the type-format conversion unit  15   b  determines whether “InitialValue” is included in the applied rule or not (S 165 ). 
         [0070]    When the type-format conversion unit  15   b  determines that the applied rule includes “InitialValue” at S 165 , the type-format conversion unit  15   b  writes a null value type-format value, which is set related with “InitialValue” as a type-format value in the case where the common-format value is a null value, as the type-format value (S 166 ) and ends the operation shown in  FIG. 12 . 
         [0071]    If the type-format conversion unit  15   b  determines that “InitialValue” is not included in the applied rule at S 165 , the type-format conversion unit  15   b  does not write anything and ends the operation shown in  FIG. 12 . 
         [0072]    The following describes a case where the common-format data illustrated in  FIG. 8  is converted into the post-conversion type-format data using an example of user list. 
         [0073]    The type-format conversion unit  15   b  reads the conversion rule information  14   c  corresponding to “MFP — 02,” which is the model information of the MFP 92 specified by the user via the operation unit  11 , from the storage unit  14 . Then, the type-format conversion unit  15   b  generates the post-conversion type-format data, namely, the type-format data illustrated in  FIG. 4  based on the rule corresponding to “user_list,” which is the data type information in the common-format data, among the conversion rule information  14   c  illustrated in  FIG. 7 . Specifically, the type-format conversion unit  15   b  applies the rule corresponding to the element name surrounding the common-format value among the rules corresponding to “user_list” in the conversion rule information  14   c  to the common-format value in the common-format data so as to generate the post-conversion type-format data. 
         [0074]    First, the type-format conversion unit  15   b  creates a CSV format file (hereinafter referred to as a “CSV file”) for post-conversion type-format data. The type-format conversion unit  15   b  writes “user,” which is the type-format item (CSVHeader) related with “No. 1” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file. 
         [0075]    Next, the type-format conversion unit  15   b  additionally writes commas to the CSV file. Then, the type-format conversion unit  15   b  additionally writes “password,” which is the type-format item (CSVHeader) related with “No. 2” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file. 
         [0076]    Next, the type-format conversion unit  15   b  additionally writes commas to the CSV file. Then, the type-format conversion unit  15   b  additionally writes “access_level,” which is the type-format item (CSVHeader) related with “No. 3” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file. 
         [0077]    Next, the type-format conversion unit  15   b  additionally writes commas to the CSV file. Then, the type-format conversion unit  15   b  additionally writes “password_mode,” which is the type-format item (CSVHeader) related with “No. 4” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file. 
         [0078]    Next, the type-format conversion unit  15   b  also additionally writes type-format items (CSVHeader) related with “No. 5” or later in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file, similarly to the type-format items (CSVHeader) related with up to “No. 4” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file. 
         [0079]    Next, the type-format conversion unit  15   b  additionally writes a line break to the CSV file. Then, the type-format conversion unit  15   b  additionally writes “user001,” which is the common-format value related between the start tag and the end tag with the element name of “Data001” in the common-format data, to “UserLogin,” which is the common-format item (NodeName) of “No. 1” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file (S 163 ). 
         [0080]    Next, the type-format conversion unit  15   b  additionally writes commas to the CSV file. Then, the type-format conversion unit  15   b  additionally writes “9317,” which is the common-format value related between the start tag and the end tag with the element name of “Data001” in the common-format data, to “UserPassword,” which is the common-format item (NodeName) of “No. 2” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file (S 163 ). 
         [0081]    Next, since “Value,” which is the rule for correlating the type-format value with the common-format value, is included in the rule of “No. 3” related with “user_list” in the conversion rule information  14   c  (YES at S 162 ), the type-format conversion unit  15   b  additionally writes commas to the CSV file. Then, the type-format conversion unit  15   b  additionally writes “1,” which is the type-format value related as “No. 1” in “Value,” to “0, which is the common-format value related between the start tag and the end tag with the element name of “Data001” in the common-format data to “UserAuthority,” which is the common-format item (NodeName) of “No. 3” in the rule corresponding to “user_list” in the conversion rule information  14   c , to the CSV file (S 164 ). 
         [0082]    In the rule corresponding to “user_list” in the conversion rule information  14   c , the common-format value related with “PasswordMode,” which is the common-format item (NodeName) of “No. 4,” between the start tag and the end tag with the element name of “Data001” in the common-format data is a null value (YES at S 161 ). Accordingly, the type-format conversion unit  15   b  additionally writes commas to the CSV file, and then the type-format conversion unit  15   b  additionally writes not the null value but “1,” which is related with “PasswordMode” as “InitialValue” in the conversion rule information  14   c , to the CSV file (S 166 ). Here, “1” related with “InitialValue” is a null value type-format value of this disclosure set as a type-format value when the common-format value in the common-format data is a null value. 
         [0083]    Next, the type-format conversion unit  15   b  also additionally writes each common-format value, which is related between the start tag and the end tag with the element name of “Data001 in the common-format data, to the common-format item (NodeName) of “No. 5” or later in the rules corresponding to “user_list” in the conversion rule information  14   c  to the CSV file. This writing is performed similarly to the common-format value, which is related between the start tag and the end tag with the element name of “Data001” in the common-format data, to the common-format items (NodeName) of up to “No. 4” in the rules corresponding to “user_list” in the conversion rule information  14   c.    
         [0084]    Next, the type-format conversion unit  15   b  also additionally writes each common-format value, which is related between the start tag and the end tag with the element name of “Data002” in the common-format data, to the CSV file, similarly to the common-format value, which is related between the start tag and the end tag with the element name of “Data001” in the common-format data. 
         [0085]    Finally, the type-format conversion unit  15   b  compresses the CSV file. The type-format conversion unit  15   b  generates the post-conversion type-format data by, for example, adding various information including “MFP 02,” which is device information in the conversion rule information  14   c , and “user_list,” which is data type information, to the compressed CSV file. 
         [0086]    The post-conversion type-format data generated by the type-format conversion unit  15   b  at S 103  is input from the data conversion apparatus  10  to the MFP 92 via a USB flash drive, and imported by the MFP 92 as information such as the address book, the user list, the department list, and the apparatus setting information of the MFP 92. 
         [0087]    As described above, the data conversion program  14   a  once converts the pre-conversion type-format data into the common-format data (S 101 ) and then converts the common-format data into the post-conversion type-format data (S 103 ). Accordingly, the type-format data can be converted in accordance with a change in the MFP model. 
         [0088]    The conversion rule information  14   b  and the conversion rule information  14   c  include the rule for correlating the order in the series of the type-format values in the type-format data and the common-format items. This allows the data conversion program  14   a  to convert the type-format data, where the type-format items are expressed in accordance with the order in the series of the type-format values, in accordance with the change in the MFP model. 
         [0089]    The conversion rule information  14   b  and the conversion rule information  14   c  include the rules for correlating the type-format values with the common-format values. Accordingly, this allows the data conversion program  14   a  to convert the type-format data in accordance with the change in the MFP model even if the same type-format value has different meanings depending on the type-format data (YES at S 131 , YES at S 162 ). 
         [0090]    The conversion rule information  14   c  includes the rules for correlating the common-format values with the null value type-format values. Accordingly, this allows the data conversion program  14   a  to generate the post-conversion type-format data where the type-format items are related with the null value type-format values even if the type-format item not present in the pre-conversion type-format data is present in the post-conversion type-format data (YES at S 165 ). 
         [0091]    The conversion rule information  14   c  includes the rule for correlating the order in the series of the type-format values in the type-format data and the type-format items. This allows the data conversion program  14   a  to generate the post-conversion type-format data including information where the type-format items themselves are arrayed in the order in the series of the type-format values in the type-format data. 
         [0092]    The data conversion program  14   a  edits the common-format data of format independent of the MFP model (S 102 ). Accordingly, compared with the case of editing the type-format data of format dependent on the MFP model, data can be edited with simple configuration independent of the model. 
         [0093]    This embodiment describes an example where the type-format data illustrated in  FIG. 3  is converted into the type-format data illustrated in  FIG. 4 . However, the type-format data illustrated in  FIG. 4  can be converted into the type-format data illustrated in  FIG. 3  in a similar manner. Type-format data for a model other than the above-described model can support such conversion simply by preparing the corresponding conversion rule information. 
         [0094]    While the image forming apparatus of this disclosure is an MFP in this embodiment, the image forming apparatus may be an image forming apparatus other than the MFP such as a print-only machine, a copy-only machine, or a FAX only machine. 
         [0095]    While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.