Patent Publication Number: US-2017364533-A1

Title: Image processing apparatus, control method of image processing  apparatus, and program

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 14/789,376, filed Jul. 1, 2015, which is herein incorporated by reference. 
    
    
     BACKGROUND OF THE INVENTION 
     Field of the Invention 
     The present invention relates to an image processing apparatus, a control method of the image processing apparatus, and a program and, more particularly, is suitable when it is used to import destination data into an image processing apparatus. 
     Description of the Related Art 
     In the related arts, an image processing apparatus such as a digital multifunction apparatus or the like has a function for converting a scanned document into electronic data and transmitting the electronic document to an arbitrary transmission destination by E-mail and a function for performing a file transmission (SMB transmission or the like). 
     There is a case where the destination data at the time of transmitting the electronic document by E-mail or file-transmitting it is stored in an address book managed in the image processing apparatus. When the destination data is stored in the address book, the destination data can be also classified and stored (refer to Japanese Patent Application Laid-Open No. 2001-358864). 
     The destination data in the address book of the image processing apparatus can be extracted from an external computer terminal via a Web Browser and stored into another image processing apparatus. In the following description, such an operation that the destination data in the address book is extracted is called “export” in accordance with necessity. Such an operation that the extracted destination data is stored into another image processing apparatus is called “import” in accordance with necessity. 
     It is also possible that communication is directly made between image processing apparatuses without passing through a computer terminal and destination data in an address book of the image processing apparatus is exported and is directly imported into another image processing apparatus (refer to Japanese Patent Application Laid-Open No. 2006-33459). 
     However, there is a case where functions of the address books in two image processing apparatuses A and B differ. For example, it is now assumed that as a function about the address book, the image processing apparatus A has only a function about the address book which can be referred to by everyone. On the other hand, it is assumed that in addition to the function about the address book which can be referred to by everyone, the image processing apparatus B has a function about the address book in which an access can be restricted every user or group in an interlocking relational manner with a user authentication. 
     In the related arts, when the destination data in the address book stored in the image processing apparatus A is exported and is imported into the image processing apparatus B, the destination data can be imported only into the same address book as that of the image processing apparatus A on an export source side. 
     For example, the destination data in the address book which has been stored in the image processing apparatus A and can be referred to by everyone is exported and is imported into the image processing apparatus B, the destination data can be imported only into the address book which can be referred to by everyone. 
     Therefore, in the case where the image processing apparatus A is replaced by the image processing apparatus B, the following process has to be performed. That is, after the destination data was manually imported into the address book existing hitherto, the destination data has to be moved to an address book which is newly added (address book in which an access can be restricted on a group unit basis or the like in an interlocking relational manner with a user authentication). Thus, a troublesomeness which is required for export and import of the address book increases. 
     The invention is made in consideration of the foregoing problem and it is an aspect of the invention to reduce a troublesomeness which is required when exporting/importing an address book (destination data) between image processing apparatuses. 
     SUMMARY OF THE INVENTION 
     According to an aspect of the invention, there is provided an image processing apparatus comprising: a first obtaining unit configured to obtain, from an external apparatus, at least either destination data in a first destination table or destination data in a second destination table in which a managing method of the destination data differs from that of the first destination table; a second obtaining unit configured to obtain, from the external apparatus, an instruction to import the destination data in the first destination table into the second destination table; and an importing unit configured to import the destination data in the first destination table obtained by the first obtaining unit into the second destination table in the case where the destination data in the second destination table is not obtained by the first obtaining unit and the instruction is obtained by the second obtaining unit. 
     According to the invention, the troublesomeness which is required when exporting/importing the address book (destination data) between the image processing apparatuses can be reduced. 
     Further features of the present invention will become apparent from the following description of exemplary embodiments with reference to the attached drawings. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a diagram illustrating a construction of an image processing system. 
         FIG. 2  is a diagram illustrating a construction of hardware of an image processing apparatus. 
         FIG. 3  is a diagram illustrating a construction of modules of the image processing apparatus. 
         FIGS. 4A and 4B  are diagrams illustrating display examples of a destination list and a group destination list. 
         FIGS. 5A, 5B, and 5C  are diagrams illustrating administration tables for managing destination data and the destination data. 
         FIG. 6  is a diagram illustrating an administration table for managing the users. 
         FIG. 7  is a diagram illustrating relations among user groups, group destination tables, and destination data. 
         FIG. 8  is a diagram illustrating a data structure of destination data for import and import destinations. 
         FIG. 9  is a flowchart for describing a first example of the operation of the image processing apparatus. 
         FIG. 10  is a diagram illustrating a first example of a display screen to instruct the import. 
         FIGS. 11A, 11B, and 11C  are diagrams illustrating error display screens. 
         FIG. 12  is a flowchart for describing a second example of the operation of the image processing apparatus. 
         FIG. 13  is a diagram illustrating a second example of a display screen to instruct the import. 
         FIGS. 14A and 14B  are diagrams illustrating examples of description of destination data for import. 
         FIG. 15  is a diagram illustrating a third example of a display screen to instruct the import. 
         FIG. 16  is a flowchart for describing a third example of the operation of the image processing apparatus. 
     
    
    
     DESCRIPTION OF THE EMBODIMENTS 
     Preferred embodiments of the present invention will now be described in detail in accordance with the accompanying drawings. 
     First Embodiment 
     First, the first embodiment will be described. 
       FIG. 1  is a diagram illustrating an example of a construction of an image processing system. 
     Image processing apparatuses  103  and  105  can convert a scanned paper original into electronic data and transmit to a shared folder or the like of a computer  101  through a network  104 . 
     The image processing apparatuses  103  and  105  have a user authenticating function. When the image processing apparatuses  103  and  105  are operated, whether or not the user authentication is necessary can be set to the image processing apparatuses  103  and  105  by the device administrator. 
     Although a user name, a password, and the like of each user which are necessary for the user authentication can be also managed in the image processing apparatuses  103  and  105 , they can be also managed in an authenticating server  102  on the network  104 . 
     A destination table list  401  and destination data  402  (refer to  FIGS. 4A and 5A , which will be described hereinlater) included in a destination table shown in the destination table list  401  have been stored in the image processing apparatus  103 . The destination table list  401  and the destination data  402  stored in the image processing apparatus  103  can be exported from the Web Browser of the computer  101  through the network  104 . 
     The destination table list  401  and the destination data  402  exported from the image processing apparatus  103  can be imported into another image processing apparatus  105  through the network  104 . In the following description, the destination data including the destination table list exported from the image processing apparatus  103  is called “destination data for import” in accordance with necessity. 
     By connecting from the image processing apparatus  103  to the image processing apparatus  105  through the network  104 , the destination data for import can be directly transmitted to the image processing apparatus  105  without passing through the computer  101 . 
     As mentioned above, in the embodiment, the case where the destination table list  401  and the destination data  402  exported from the image processing apparatus  103  are imported into another image processing apparatus  105  through the network  104  will be described as an example. However, the image processing apparatus for exporting the destination table list  401  and the destination data  402  and the image processing apparatus for importing the destination table list  401  and the destination data  402  may be replaced. 
       FIG. 2  is a block diagram illustrating an example of a construction of hardware of the image processing apparatus  105 . A construction of hardware of the image processing apparatus  103  can be also realized by the construction illustrated in  FIG. 2 . Therefore, the detailed construction of the image processing apparatus  103  is omitted here. 
     By loading a program stored in a ROM  209  into a RAM  208 , a CPU  201  controls the whole operation of the image processing apparatus  105 . The CPU  201  communicates with each construction in the image processing apparatus  105  through a bus  202 . 
     A printer  204  prints an image based on image data which was input onto recording paper (sheet). 
     A scanner  205  reads an image on an original which was set onto a sheet table by the user and stores image data thus obtained into an HDD  203 , the RAM  208 , or the like. The scanner  205  includes an automatic document feeder (also referred to as an ADF hereinbelow). After a plurality of originals set onto the ADF were sequentially fed onto the sheet table, the scanner  205  can read them. 
     The HDD  203  is a hard disk drive containing a hard disk. The HDD  203  can store the image data input by the scanner  205  and various kinds of user data (address book, and the like). 
     An operation unit  206  includes: a plurality of keys which are used by the user to instruct; and a display unit for displaying various kinds of information to be notified to the user. 
     A network I/F  207  connects the image processing apparatus  105  to the network  104  and controls transmission and reception of data to/from an external apparatus. For example, the network I/F  207  controls the transmission of the image data scanned by the scanner  205  to the external apparatus such as a computer  101  or the like connected to the network  104 . 
     A FAX  210  transmits and receives the image data through a telephone line. 
       FIG. 3  is a diagram illustrating an example of a construction of modules of the image processing apparatus  105 . 
     An address book administration module  301  performs a management of the destination table list and the destination data. 
     The destination table list  401  and the destination data  402  which are managed by the address book administration module  301  are stored into a destination table DB  304  in the HDD  203 . Details of the destination table list  401  and the destination data  402  will be described hereinlater with reference to  FIGS. 4A and 5A . 
     A user group module  302  performs a management about with which user group each user is associated. Details of the user group module  302  will be described hereinlater with reference to  FIG. 6 . 
     A group destination table administration module  303  performs a management of user groups which can access each group destination table list  403  and a management of destination data associated with each group destination table included in the group destination table list  403 . Details of the group destination table list  403  will be described hereinlater with reference to  FIGS. 4B and 5B . 
     The group destination table list  403  and the destination data which are managed by the group destination table administration module  303  are stored in a group destination table DB  305  in the HDD  203 . 
       FIG. 4A  is a diagram illustrating an example of a display form of the destination table list  401 . 
     When a display request of the destination table list  401  is received from the operation unit  206 , the address book administration module  301  obtains the destination table list  401  and the destination data  402  stored in the HDD  203  and displays to the operation unit  206 . 
     In the example illustrated in  FIG. 4A , the destination table list  401  includes ten destination tables of (1 to 10). The destination data  402  can be stored in each destination table. 
     When the destination table list  401  is displayed, all of the destination tables of (1 to 10) included in the destination table list  401  can be always referred to. 
       FIG. 4B  is a diagram illustrating an example of a display form of the group destination table list  403 . 
     When a display request of the group destination table list  403  is received from the operation unit  206 , the address book administration module  301  obtains information of the user group which is operating at present from a user group module  302 . It is assumed that information of the user who is operating is included in the display request of the group destination table list  403 . 
     The address book administration module  301  notifies the group destination table administration module  303  of the obtained user group. 
     The group destination table administration module  303  retrieves the group destination table list corresponding to the user group notified from the address book administration module  301  from the HDD  203  (group destination table DB  305 ). The group destination table administration module  303  returns the retrieved group destination table list  403  and destination data  404  associated therewith to the address book administration module  301 . 
     The address book administration module  301  displays the group destination table list  403  and the destination data  404  associated therewith which were obtained from the group destination table administration module  303  to the operation unit  206 . 
     As mentioned above, when the group destination table list  403  is displayed, only the group destination table associated with the user group to which the user who is operating the operation unit  206  belongs is displayed. 
     As mentioned above, in the embodiment, the destination table included in the destination table list  401  is an example of the destination table of the first type and there is no access restriction in this destination table. The group destination table included in the group destination table list  403  is an example of the destination table of the second type and, to this group destination table, the access can be restricted every user group. 
       FIG. 5A  is a diagram illustrating an example of an administration table in which the destination table and the destination data are registered so as to be associated with each other. 
     Any one of destination table IDs  501  of (1 to 10) is uniquely allocated to each destination table  502  as identification information (ID information) to identify the destination table included in the destination table list  401 . Each destination data  503  is associated with each destination table and stored into the HDD  203  (destination table DB  304 ). The administration table illustrated in  FIG. 5A  is also stored in the image processing apparatus  103 . 
       FIG. 5B  is a diagram illustrating an example of an administration table in which the group destination table, the user group, and the destination data are registered so as to be associated with each other. 
     Any one of group destination table IDs  504  of (1 to N) is uniquely allocated to each group destination table  505  as identification information (ID information) to identify the group destination table included in the group destination table list  403 . In this instance, N is a positive integer which changes dynamically in accordance with the settings. 
     A user group  506  which can access the relevant group destination table and each destination data  507  are associated with each other in each group destination table  505  and stored into the HDD  203  (group destination table DB  305 ). 
       FIG. 5C  is a diagram illustrating an example of data which is stored into each of the destination data  503  and  507 . 
     In the example illustrated in  FIG. 5C , a destination name, a name of the host to which data is transmitted, a folder path name, a user name, and a password are stored into the destination data. The user name and the password illustrated in  FIG. 5C  are necessary when the user logs-in the host name illustrated in  FIG. 5C . 
       FIG. 6  is a diagram illustrating an example of an administration table in which each user and the user group are registered so as to be associated with each other. 
     As identification information (ID information) to identify the user group, a unique group ID is allocated to each user group. The user who can access has been allocated to each user group every user group (refer to a column of the included users). 
     The user group module  302  retrieves the user received from the address book administration module  301  from the column of the included users in the administration table illustrated in  FIG. 6  and returns the information of all of the user groups to which the user belongs to the address book administration module  301 . 
       FIG. 7  is a diagram illustrating relations among the user groups, the group destination tables, and the destination data described with reference to  FIGS. 5A to 5C and 6  from a viewpoint of a data structure. 
     The user groups, the group destination tables, and the destination data are managed by a tree structure. Specifically describing, each group destination table is associated under a node of each user group (GroupA or the like) and each destination data is further associated under each group destination table. 
       FIG. 8  is a diagram conceptually illustrating an example of a data structure of destination data  801  for import and import destinations when the destination data is imported into the image processing apparatus  105 . 
     When the address book administration module  301  receives an import request, the destination data  801  for import is imported into either the destination table DB  304  or the group destination table DB  305  in accordance with the destination data  801  for import. When the destination data  801  for import is imported into the group destination table DB  305 , it is imported through the group destination table administration module  303 . 
     An example of the operation of the image processing apparatus  105  at the time of importing the destination data for import (destination data) will be described hereinbelow with reference to a flowchart of  FIG. 9 . 
     A process shown in the flowchart is executed by, for example, the CPU  201  after a program stored in the ROM  209  was loaded into the RAM  208 . When a result of the execution by the CPU  201  is displayed, the execution result is displayed to the operation unit  206 . 
     When the import request is received, in S 901 , the address book administration module  301  executes a first obtaining process for obtaining the destination data  801  for import. The address book administration module  301  retrieves the data of the group destination table from the destination data  801  for import. 
     Subsequently, in S 902 , the address book administration module  301  discriminates whether or not the data of the group destination table is included in the destination data  801  for import. 
     As a result of the discrimination, if the data of the group destination table is not included in the destination data  801  for import, the processing routine advances to S 903 . In S 903 , the address book administration module  301  discriminates whether or not an import instruction to the group destination table  505  has been made at the time of requesting the import. 
     An example of the import instruction to the group destination table  505  will now be described with reference to  FIG. 10 . 
       FIG. 10  is a diagram illustrating an example of a display screen for instructing the image processing apparatus  105  to import the destination data  801  for import from the Web Browser of the computer  101 . A location where the destination data  801  for import has been stored is designated to a file path  1001 . 
     By checking a check box  1002  of “IMPORT DESTINATION TABLE TO GROUP DESTINATION TABLE” at the time of import, the import instruction to import each destination data included in the destination data  801  for import into the group destination table  505  is performed. The address book administration module  301  executes a second obtaining process for obtaining the import instruction and executes a process of S 903 . 
     As a result of the discrimination of S 903 , if it is determined that there is not the import instruction to the group destination table  505 , S 921  follows. In S 921 , the address book administration module  301  obtains each destination data and a destination table ID (identification information to identify the destination table) from the destination data  801  for import. 
     The address book administration module  301  retrieves the destination table ID  501  which coincides with the destination table ID obtained from the destination data  801  for import and specifies the destination table of an import destination side from the destination table  502 . 
     The address book administration module  301  imports the destination data obtained from the destination data  801  for import into the destination table DB  304  in the HDD  203  as destination data  503  associated with the specified destination table  502 . 
     The address book administration module  301  executes the foregoing importing process to all of the destination data included in the destination data  801  for import. The process according to the flowchart of  FIG. 9  is ended. 
     On the other hand, as a result of the discrimination of S 903 , if it is determined that there is the import instruction to the group destination table  505 , S 904  follows. In S 904 , the address book administration module  301  discriminates whether or not the setting of a use permission of the group destination table is validated. 
     Whether or not the setting of the use permission of the group destination table is validated is preset, for example, based on the operation to the display screen displayed to the operation unit  206  of the image processing apparatus  105  and is stored into the HDD  203 . The setting about whether or not the setting of the use permission of the group destination table is validated may be performed to the image processing apparatus  105  from the Web Browser of the computer  101 . 
     As a result of this discrimination, if the setting of the use permission of the group destination table is validated, S 905  follows. In S 905 , the address book administration module  301  obtains the number of destination table IDs (that is, the number of destination tables) included in the destination data  801  for import. Subsequently, in S 906 , the address book administration module  301  obtains the number of group destination tables from the group destination table administration module  303 . 
     Subsequently, in S 907 , the address book administration module  301  discriminates whether or not the number obtained in S 906  is equal to or larger than the number obtained in S 905 . 
     As a result of this discrimination, if the number obtained in S 906  is equal to or larger than the number obtained in S 905 , S 908  follows. In S 908 , the address book administration module  301  obtains the destination data of each destination table from the destination data  801  for import and obtains the maximum number of destination data in one destination table. 
     Subsequently, in S 909 , the address book administration module  301  obtains the maximum number of destination data manageable by one group destination table from the HDD  203 . 
     The maximum number of destination data manageable by one group destination table is preset, for example, based on the operation to the display screen displayed to the operation unit  206  of the image processing apparatus  105  and is stored into the HDD  203 . The setting of the maximum number of destination data manageable by one group destination table may be performed to the image processing apparatus  105  from the Web Browser of the computer  101 . 
     Subsequently, in S 910 , the address book administration module  301  discriminates whether or not the maximum number obtained in S 909  is equal to or larger than the maximum number obtained in S 908 . 
     As a result of this discrimination, if the maximum number obtained in S 909  is equal to or larger than the maximum number obtained in S 908 , it is determined that the apparatus is in a state where the destination data  801  for import can be imported to the group destination table, and S 911  follows. In S 911 , the address book administration module  301  obtains each destination data and the destination table ID associated with each destination data from the destination data  801  for import. 
     The address book administration module  301  retrieves the group destination table ID  504  which coincides with the destination table ID obtained from the destination data  801  for import. The address book administration module  301  specifies the group destination table  505  associated with the group destination table ID  504  as a group destination table of the import destination side. 
     The address book administration module  301  imports the destination data, as destination data  507 , obtained from the destination data  801  for import for the specified group destination table into the group destination table DB  305 . 
     The address book administration module  301  executes the foregoing importing process to all of the destination data included in the destination data  801  for import. The process according to the flowchart of  FIG. 9  is ended. 
     As a result of the discrimination in S 904 , if the setting of the use permission of the group destination table is not validated (is invalid), the group destination table cannot be used. Therefore, in S 922 , the address book administration module  301  determines that there is such an import error that the destination data  801  for import cannot be imported to the group destination table has. 
     Subsequently, in S 923 , the computer  101  displays an error display screen to its own Web Browser.  FIG. 11A  is a diagram illustrating an example of the error display screen which is displayed in the case where the processing routine advances from S 904  to S 922  and S 923 . 
     As a result of the discrimination in S 907 , if the number obtained in S 906  is smaller than the number obtained in S 905 , the address book administration module  301  cannot import all of the destination tables of the destination data  801  for import into the group destination table. Therefore, in S 922 , the address book administration module  301  determines that there is such an import error that the destination data  801  for import cannot be imported to the group destination table. 
     Subsequently, in S 923 , the computer  101  displays an error display screen to its own Web Browser.  FIG. 11B  is a diagram illustrating an example of the error display screen which is displayed in the case where the processing routine advances from S 907  to S 922  and S 923 . 
     As a result of the discrimination in S 910 , if the maximum number obtained in S 909  is smaller than the maximum number obtained in S 908 , all of the destination data associated with the destination table of the destination data  801  for import cannot be imported to the group destination table. Therefore, in S 922 , the address book administration module  301  determines that there is such an import error that the destination data  801  for import cannot be imported to the group destination table. 
     Subsequently, in S 923 , the computer  101  displays an error display screen to its own Web Browser.  FIG. 11C  is a diagram illustrating an example of the error display screen which is displayed in the case where the processing routine advances from S 910  to S 922  and S 923 . 
     As a result of the discrimination in S 902 , if the data of the group destination table is included in the destination data  801  for import, S 912  follows. In S 912 , the address book administration module  301  obtains the destination table data and the group destination table data from the destination data  801  for import. If the data of the destination table is not included in the destination data  801  for import, the address book administration module  301  obtains only the group destination table data. 
     Processes of S 913  to S 918  are substantially the same as those of S 905  to S 910 , respectively. Therefore, a detailed description of the processes of S 913  to S 918  is omitted. However, in S 913  and S 916 , the number of group destination tables and the maximum number of destination data in one group destination table are obtained from the destination data  801  for import. 
     In S 918 , if the maximum number obtained in S 917  is equal to or larger than the number obtained in S 916 , S 919  follows. In S 919 , the address book administration module  301  imports the destination data included in the data of the group destination table obtained in S 912  into the group destination table DB  305  through the group destination table administration module  303 . For example, the address book administration module  301  obtains each destination data and a group destination table ID associated with each destination data from the destination data  801  for import. The address book administration module  301  retrieves the group destination table ID  504  which coincides with the obtained group destination table ID and specifies the group destination table  505  associated with the group destination table ID  504  as a group destination table of the import destination side. The address book administration module  301  imports the destination data, as destination data  507 , obtained from the destination data  801  for import into the specified group destination table (group destination table DB  305 ). 
     Subsequently, in S 920 , the address book administration module  301  imports the destination data included in the data of the destination table obtained in S 912  into the destination table DB  304 . For example, the address book administration module  301  retrieves the destination table ID  501  which coincides with the destination table ID obtained from the destination data  801  for import and specifies the destination table of the import destination side from the destination table  502 . The address book administration module  301  imports the destination data obtained from the destination data  801  for import into the destination table DB  304  in the HDD  203  as destination data  503  associated with the specified destination table  502 . 
     The address book administration module  301  executes the foregoing importing process of S 919  and S 920  to all of the destination data included in the destination data  801  for import. The process according to the flowchart of  FIG. 9  is ended. 
     If the destination table ID and the group destination table ID cannot be retrieved in S 911 , S 919 , S 920 , and S 921 , the processing routine advances to S 922  and S 923  and an error display screen showing that the data cannot be imported into the destination table and the group destination table may be displayed. 
     As mentioned above, in the embodiment, at the time of the import request of the destination data  801  for import, an import instruction to the group destination table  505  is performed. The group destination table ID  504  which coincides with the destination table ID obtained from the destination data  801  for import is retrieved. The group destination table  505  associated with the group destination table ID  504  is specified as a group destination table of the import destination side. The destination data obtained from the destination data  801  for import is imported as destination data  507  into the specified group destination table (group destination table DB  305 ). Therefore, at the time of importing the destination data  801  for import, merely by designating by the user, the destination data can be imported to the group destination table while taking over a classification by the destination table, and the group destination table can be soon used. Therefore, a usability in the case where the destination data  801  for import exported from the image processing apparatus  103  which does not have the function of the group destination table is imported into the image processing apparatus  105  having the function of the group destination table is improved. Thus, a troublesomeness which is required when the address book (destination table) is exported/imported between the image processing apparatuses  103  and  105  can be reduced. 
     In the embodiment, at the time of the importing process of the destination data  801  for import, the contents of the destination data  801  for import is confirmed. Specifically speaking, whether or not the number of destination tables included in the destination data  801  for import is larger than the number of group destination tables is confirmed and whether or not the maximum value of the destination data included in one destination table is larger than the maximum value manageable by one group destination table is confirmed. Therefore, the destination data  801  for import can be certainly imported. When the import error occurs in the confirmation at the time of import, the error message is output every cause of the error. Therefore, the usability of the user is further improved. 
     Second Embodiment 
     Subsequently, the second embodiment will be described. In the first embodiment, the case where when the import error occurs, the error message is unconditionally displayed has been described as an example. In the second embodiment, when the import error occurs, either a mode of importing the destination data of the number as many as the importable data or a mode of displaying the error message is selected. As mentioned above, the second embodiment and the first embodiment differ mainly with respect to a part of the process in the case where the import error has occurred. Therefore, in the description of the embodiment, substantially the same portions as those in the first embodiment are designated by the same reference numerals as those in  FIGS. 1 to 11C  and their detailed description is omitted. 
     An example of the operation of the image processing apparatus  105  in the case of importing the destination data for import (destination data) will now be described with reference to  FIG. 12 . 
     Processes of S 1201  to S 1222  are substantially the same as those of S 901  to S 922  in  FIG. 9 . 
     If it is determined in S 1222  that the import error has occurred, in S 1223 , the address book administration module  301  discriminates whether or not there is an instruction to import the destination data of the number as many as the importable data at the time of the import request. 
     An example of the instruction to import the destination data of the number as many as the importable data will now be described with reference to  FIG. 13 . 
       FIG. 13  is a diagram illustrating an example of a display screen to instruct the image processing apparatus  105  to import the destination data  801  for import from the Web Browser of the computer  101  in a manner similar to  FIG. 10 . 
       FIG. 13  differs from  FIG. 10  with respect to a point that such a setting as “IMPORT BY IMPORTABLE NUMBER” can be performed as an operation at the time of the import error. 
     A location where the destination data  801  for import has been stored is designated in a file path  1301 . 
     Upon importing, by checking a check box  1302  of “IMPORT DESTINATION TABLE TO GROUP DESTINATION TABLE”, such an import instruction that each destination data included in the destination data  801  for import is imported into the group destination table  505  is performed. By checking a check box  1303  of “OPERATION IN IMPORT ERROR IMPORT BY IMPORTABLE NUMBER”, even in the case of the import error, the destination data of the number as many as the importable data can be imported. Specifically speaking, even if the number of group destination tables of the image processing apparatus  105  of the import destination side is small or even if the maximum number of destination data manageable by each group destination table is small, the destination data of the number as many as the importable data can be imported. 
     The address book administration module  301  executes the second and third obtaining processes for obtaining such an import instruction and executes the process of S 1222 . 
     The check of the check box  1303  is validated only in the case the check box  1302  has been checked. For example, if the check box  1302  is not checked, it is disabled to check the check box  1303 . 
     Returning to the description of  FIG. 12 , as a result of the discrimination of S 1223 , if there is the instruction to import the destination data of the number as many as the importable data at the time of the import request, S 1225  follows. In S 1225 , the address book administration module  301  imports the destination data of the number as many as the importable data. A method of importing the destination data can be realized by substantially the same method as that described in S 911  and S 919  in  FIG. 9 . Priorities of the destination data to be imported are preset, for example, based on the operation to the screen which is displayed to the operation unit  206  of the image processing apparatus  105  and are stored into the HDD  203 . For example, the destination data can be imported in order from the head destination data of the destination data  801  for import. 
     On the other hand, as a result of the discrimination of S 1223 , if there is not the instruction to import the destination data of the number as many as the importable data at the time of the import request, S 1224  follows. In S 1224 , the computer  101  displays an error display screen to its own Web Browser. The error display screen of the contents according to the contents of the error is displayed in a manner similar to that described in S 923  in  FIG. 9  (refer to  FIGS. 11A to 11C ). 
     As mentioned above, in the embodiment, upon import requesting, the instruction to import the destination data of the number as many as the importable data can be performed. If there is the instruction to import the destination data of the number as many as the importable data, the destination data of the number as many as the importable data is imported. Therefore, in addition to the effect described in the first embodiment, by importing all of the destination data of the number as many as the importable data, such a troublesomeness that the destination data is registered by the manual input from the beginning can be omitted. Thus, the usability in the case where the destination data  801  for import exported from the image processing apparatus  103  which does not have the function of the group destination table is imported to the image processing apparatus  105  having the function of the group destination table is further improved. 
     Third Embodiment 
     Subsequently, the third embodiment will be described. 
     General data formats exist as a data format of the address book. For example, vCard, CSV (comma-separated values), and the like exist. Details of vCard have been described in RFC2425 and RFC2426. Details of CSV have been described in RFC4180. Those general data formats of the address book have been standardized. However, in CSV, the user can freely define the tag itself. In vCard, although the tag itself has been defined, the user can freely describe which value into which tag. 
     As mentioned above, even if the data format of the address book has been standardized, in which meaning the data in the data format is handled is determined every user. Therefore, when the general data formats of the address book are processed in the image processing apparatus, if it is impossible to recognize that the tags of those data formats are the data of which meaning, the data cannot be correctly handled as data of the address book. Thus, a troublesomeness which is required when exporting and importing the address book increases. 
     In the embodiment, therefore, in addition to the construction of the first embodiment, at the time of the import request, a file format of the destination data for import, a tag to be used as a group destination table, and a value which is obtained when a plurality of values have been set in the tag are designated. As mentioned above, the third embodiment and the first embodiment mainly differ with respect to a part of the process at the time of the import request of the destination data for import and a part of the process at the time of the import of the destination data for import. Therefore, in the description of the embodiment, substantially the same portions as those in the first embodiment are designated by the same reference numerals as those in  FIGS. 1 to 11C  and their detailed description is omitted. 
       FIGS. 14A and 14B  are diagrams illustrating examples of description of the destination data for import of the general data formats of the address book. 
       FIG. 14A  illustrates the example of the description of the destination data for import when the data format is vCard. 
     The leftmost column (BEGIN, VERSION, UID, or the like) of each row is tag information defined in vCard. 
     A value after a colon (:) after each tag is a value corresponding to the tag. 
     A plurality of values can be described in the tag. For instance, in the example illustrated in  FIG. 14A , two values of “Company1” and “GENERAL AFFAIRS 1ST SECTION” are set in the tag showing an organization of ORG. 
       FIG. 14B  illustrates an example of a description of the destination data for import when the data format is CSV. 
     When the data format is CSV, a definition itself of the tag can be freely described. A delimiter between each tag and each value is made by a comma (,). 
     In the example illustrated in  FIG. 14B , the head row is a description showing the tag. For example, a tag which means a group is “GROUP”. 
     The second and third rows are a description of the actual destination data for import. They are described in such a manner that values corresponding to the tags of UID are 001 and 002 and values corresponding to the tag of GROUP are group1 and group2, respectively. 
       FIG. 15  is a diagram illustrating an example of a display screen for instructing the image processing apparatus  105  to import the destination data for import illustrated in  FIG. 8  from the Web Browser of the computer  101 . 
     A location where the destination data for import illustrated in  FIG. 8  has been stored is designated to a file path  1501 . 
     At the time of import, by checking a check box  1502  of “IMPORT DESTINATION TABLE TO GROUP DESTINATION TABLE”, the import instruction to import each destination data included in the destination data for import into the group destination table  505  is performed. 
     When importing, as a file format of the destination data for import illustrated in  FIG. 8 , either vCard or CSV is set by a pull-down menu  1503 . 
     As a tag to be used as a group destination table, any one of ORG, TITLE, and an arbitrary character string is set by a pull-down menu  1504 . 
     If the arbitrary character string is selected here, the arbitrary character string can be registered. Various kinds of character strings can be set as a tag. 
     The file formats and tags described in the pull-down menus  1503  and  1504  are merely shown as an example and any other formats and tags which are not shown here can be also applied. 
     In a pull-down menu  1505 , when values corresponding to the tag set by the pull-down menu  1504  are obtained, which value should be obtained is set. 
     For example, in the case of the vCard format illustrated in  FIG. 14A , ORG is set as a tag by the pull-down menu  1504 . When “1” is set by the pull-down menu  1505 , the first value “Company1” is obtained as a value. When ORG is set as a tag by the pull-down menu  1504  and “2” is set by the pull-down menu  1505 , the second value “GENERAL AFFAIRS 1ST SECTION” is obtained as a value. 
     If the number having no value is designated, for example, it is sufficient that the first value is always obtained. 
     An example of the process of the image processing apparatus  105  at the time when the destination data obtained from the destination data  801  for import is imported into the group destination table will be described hereinbelow with reference to a flowchart of  FIG. 16 . The flowchart of  FIG. 16  is executed, for example, in S 911  and S 919  in  FIG. 9 . 
     In S 1601 , the address book administration module  301  executes a fourth obtaining process for obtaining a file format of the destination data for import set by the pull-down menu  1503  in response to the import request. 
     Subsequently, in S 1602 , the address book administration module  301  executes a fourth obtaining process for obtaining a tag to be used as a group destination table set by the pull-down menu  1504  in response to the import request. 
     Subsequently, in S 1603 , the address book administration module  301  obtains the head destination data in accordance with the file format obtained in S 1601 . 
     Subsequently, in S 1604 , the address book administration module  301  obtains tag information according to the file format from the destination data obtained in S 1603 . 
     Subsequently, in S 1605 , the address book administration module  301  discriminates whether or not the tag information obtained in S 1602  is included in the tag information obtained in S 1604 . 
     As a result of the discrimination, if no tag information is included, the destination data obtained in S 1603  cannot be used as a group destination table. Therefore, in S 1613 , the address book administration module  301  imports the destination data obtained in S 1603  into the destination table DB  304 . The processing routine advances to S 1612 , which will be described hereinlater. The process of S 1613  is realized, for example, in a manner similar to the process of S 921  in  FIG. 9 . 
     If it is determined in S 1605  that the tag information is included, S 1606  follows. In S 1606 , the address book administration module  301  obtains the value corresponding to the tag information obtained in S 1604  and discriminates whether or not the data is described in such a value. 
     As a result of the discrimination, if the data is not described in the value, since the data is empty, the destination data obtained in S 1603  cannot be used as a group destination table. Therefore, in S 1613 , the address book administration module  301  imports the destination data obtained in S 1603  into the destination table DB  304 . The processing routine advances to S 1612 , which will be described hereinlater. 
     If it is determined in S 1606  that the data is described in the value, S 1607  follows. In S 1607 , the address book administration module  301  discriminates whether or not the setting for obtaining which value has been made by the pull-down menu  1505  in response to the import request. 
     As a result of the discrimination, if the setting for obtaining which value has been made, S 1608  follows. In S 1608 , the address book administration module  301  obtains the value corresponding to the setting. The processing routine advances to S 1609 , which will be described hereinlater. If the setting for obtaining which value is not made, S 1614  follows. In S 1614 , the address book administration module  301  obtains the first value. The processing routine advances to S 1609 . 
     In S 1609 , through the user group module  302 , the address book administration module  301  confirms whether or not the same values as those obtained in S 1608  and S 1614  exist as a user group. 
     As a result of the confirmation, if the same values as those obtained in S 1608  and S 1614  do not exist as a user group, the destination data obtained in S 1603  cannot be used as a group destination table. Therefore, in S 1613 , the address book administration module  301  imports the destination data obtained in S 1603  into the destination table DB  304 . The processing routine advances to S 1612 , which will be described hereinlater. 
     On the other hand, if the same values as those obtained in S 1608  and S 1614  exist as a user group, S 1610  follows. In S 1610 , through the group destination table administration module  303 , the address book administration module  301  confirms whether or not the group destination table associated with the user group exists. 
     As a result of the confirmation, if the group destination table associated with the user group does not exist, the destination data obtained in S 1603  cannot be used as a group destination table. Therefore, in S 1613 , the address book administration module  301  imports the destination data obtained in S 1603  into the destination table DB  304 . The processing routine advances to S 1612 , which will be described hereinlater. 
     On the other hand, if the group destination table associated with the user group exists, the destination data obtained in S 1603  can be used as a group destination table. Therefore, in S 1611 , the address book administration module  301  imports the destination data obtained in S 1603  into the group destination table DB  305 . 
     In S 1612 , the address book administration module  301  discriminates whether or not the destination data to be imported exists. As a result of the discrimination, if the destination data to be imported exists, the processing routine is returned to S 1603  and the processes of S 1603  to S 1611  are repeated with respect to such destination data. If there are no more destinations to be imported, the process according to the flowchart of  FIG. 16  is ended. 
     As mentioned above, in the embodiment, at the time of import request, the file format of the destination data for import, the tag to be used as a group destination table, and the values to be obtained in the case where a plurality of values have been set to the tag are designated. In the destination data (relevant designation), if there is the tag to be used as a group destination table and the same user group as the values of the tag and there is the group destination table associated with the user group, such destination data is installed into the group destination table. Therefore, even in the case of importing the destination data of the vCard or CSV format as a general data format of the address book, at the time of import, the file format and the tag to be used as a group destination table can be designated. Consequently, even in the general data format of the address book, immediately after the destination data was imported, it can be used as a group destination table. Therefore, a time which is required to move the destination data is eliminated and the usability of the user is improved. Thus, the troublesomeness which is required when exporting and importing the address book (destination table) between the image processing apparatuses  103  and  105  can be reduced. 
     Further, even if a plurality of values were set to the tag, which value should be obtained can be set at the time of import. Therefore, it is possible to more flexibly cope with various kinds of data formats. 
     In the embodiment, the case of executing the flowchart of  FIG. 16  in S 911  and S 919  in  FIG. 9  has been described as an example. However, it is not always necessary to use such a method. For instance, the flowchart of  FIG. 16  may be executed in S 1211  and S 1219  in  FIG. 12 . The flowchart of  FIG. 16  may be executed at timing different from that in the flowchart of  FIG. 9  or  FIG. 12 . In this case, when only the group destination table is imported without presuming a case of importing the destination table, the check box  1502  is unnecessary in the display screen illustrated in  FIG. 15 . 
     The foregoing embodiments have merely been shown as an example of embodying the invention and the technical scope of the invention should not be limitedly interpreted by them. That is, the invention can be embodied in various forms without departing from a technical idea or a principal feature of the invention. 
     Other Embodiments 
     Embodiment(s) of the present invention can also be realized by a computer of a system or apparatus that reads out and executes computer-executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be referred to more fully as a ‘non-transitory computer-readable storage medium’) to perform the functions of one or more of the above-described embodiment(s) and/or that includes one or more circuits (e.g., application specific integrated circuit (ASIC)) for performing the functions of one or more of the above-described embodiment(s), and by a method performed by the computer of the system or apparatus by, for example, reading out and executing the computer-executable instructions from the storage medium to perform the functions of one or more of the above-described embodiment(s) and/or controlling the one or more circuits to perform the functions of one or more of the above-described embodiment(s). The computer may comprise one or more processors (e.g., central processing unit (CPU), micro processing unit (MPU)) and may include a network of separate computers or separate processors to read out and execute the computer executable instructions. The computer-executable instructions may be provided to the computer, for example, from a network or the storage medium. The storage medium may include, for example, one or more of a hard disk, a random-access memory (RAM), a read only memory (ROM), a storage of distributed computing systems, an optical disk (such as a compact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™), a flash memory device, a memory card, and the like. 
     While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions. 
     This application claims the benefit of Japanese Patent Application No. 2014-140682, filed Jul. 8, 2014, which is hereby incorporated by reference herein in its entirety.