Information processing apparatus, control method for information processing apparatus, and storage medium, for displaying a candidate for selection

An information processing apparatus disclosed herein includes a transmitting unit configured to transmit image data, an obtaining unit configured to obtain identification information of a user, and a display unit configured to display a candidate for a domain name to be used in a destination address of the image data to be transmitted by the transmitting unit. In this case, the display unit displays a domain name based on the identification information obtained by the obtaining unit as a candidate for the domain name to be used in the destination address.

BACKGROUND

Field

The present disclosure relates to an information processing apparatus for displaying a candidate for a character string to be input, a control method therefor and a storage medium therefor.

Description of the Related Art

An information processing apparatus has been known which, while a user is attempting to input an e-mail address, can display candidate domain names which are registered in advance, for the domain name to be input. In such an information processing apparatus, a user may select one of the candidate domain names to input the intended domain name. Japanese Patent Laid-Open No. 2008-204483 discloses extracting a character string located after an at sign in an e-mail address input by a user and storing the character string as a candidate for a domain name. The stored domain name may then be displayed as a domain name candidate the next time that a user attempts to input an e-mail address.

In such an information processing apparatus, however, domain name candidates to be displayed on a screen are not determined for each user. To any user who is inputting a domain name to the information processing apparatus, prestored domain name candidates are displayed. The displayed domain name candidates are not specifically determined for the user. As a result, a domain name which is rarely input by a user may sometimes be displayed as a candidate for the domain name that the user is inputting, which may lower the usability of this feature.

SUMMARY

Various embodiments of the information processing apparatus disclosed herein determine a domain name candidate to be displayed specifically for each user who is using the information processing apparatus.

In various embodiments, an information processing apparatus disclosed herein includes a transmitting unit configured to transmit image data, an obtaining unit configured to obtain identification information of a user, and a display unit configured to display a candidate for a domain name to be used in a destination address of the image data to be transmitted by the transmitting unit. In some embodiments, the display unit displays a domain name based on the identification information obtained by the obtaining unit, as a candidate for the domain name to be used in the destination address.

DESCRIPTION OF THE EMBODIMENTS

First Embodiment

Best modes for embodying various embodiments of the present disclosure will be described below. It should be understood that the following embodiments are not intended to limit the present disclosure and that all of the combinations of features according to the described embodiments are not necessary in all embodiments of the present disclosure.

FIG. 1illustrates an example of a configuration diagram of a hardware block in an information processing apparatus according to an embodiment of the present disclosure. An information processing apparatus1implements various embodiments of the present disclosure. An information processing apparatus according to a first embodiment is an apparatus such as a multifunction peripheral which can exchange image data, for example, by using an e-mail address.

A control unit20includes a CPU11, a RAM12, a network interface (I/F)16, a hard disk13, an operating unit interface (I/F)14, and a scanner19. These components can exchange information via a main bus18. The information processing apparatus1is connected to a network2connecting to another communicate apparatus such as a mail server through a network interface (I/F)16. According to the first embodiment, the CPU11is configured to control the RAM12, the hard disk13, the operating unit I/F14, the network I/F16, and a scanner interface (I/F)17via the main bus18unless otherwise specified.

The CPU11may read out a control program stored in a storage device such as the hard disk13to control the information processing apparatus1. The RAM12may provide a work area and a temporary storage area for the CPU11. The hard disk13may be a storage device configured to store a program to be executed by the CPU11and to store various settings and files. The hard disk13may be a storage device of other kinds such as a floppy disk and an NVRAM (Non-Volatile RAM). The hard disk13may further store an address book which manages destinations to be used by the information processing apparatus1for transmitting a document to another information processing apparatus over the network2. Such an address book may be managed as a personal address book for each user. A log-in user is allowed to view his or her personal address book only and is not allowed to read out and use a destination registered in an address book for a different user, from the address book for the different user. The hard disk13is configured to manage an e-mail address for each user.

The operating unit I/F14is configured to connect an operating unit21and the control unit20. The operating unit21may be a liquid crystal display unit having a touch panel function. The operating unit21may operate as a display device and an input device configured to receive inputs from a user. The operating unit I/F14is configured to obtain an input to the operating unit21and passes the obtained operation content to the CPU11. The CPU11is configured to generate a display screen to be displayed on the operating unit21based on information received from the operating unit I/F14.

The scanner I/F17is configured to connect the scanner19and the control unit20. The scanner19may be a document scanning apparatus configured to scan a document and generate image data therefrom. The scanner19is configured to input the generated image data to the control unit20through the scanner I/F17. The information processing apparatus1may use the scanner19, attach an e-mail to the image data generated by scanning a document, and may transmit the image data and email to another information processing apparatus.

FIG. 2illustrates an example of a system configuration including the information processing apparatus1according to this embodiment. The information processing apparatus1and a mail server3are connected over the network2. A domain name “email-domain.jp” is set for the mail server3. According to this embodiment, a character string located after a delimiter, such as an at sign, in a character string included in an e-mail address is called a domain name.

First, a flow of operations for inputting an e-mail address according to this embodiment will be described with reference toFIGS. 3 to 6.

FIG. 3illustrates an example of a log-in screen401to be displayed on the operating unit21when a user logs into the information processing apparatus1. The log-in screen401displays a user ID input field402, a password input field403, and a “LOG IN” button404.

The user ID input field402may display a user ID input by a user. In response to a pressing of the user ID input field402performed by a user, the operating unit21displays a software keyboard, not illustrated. The operating unit21then displays a character string input by the user in the user ID input field402. While this embodiment assumes that a user ID is an e-mail address of a user, the user ID is not limited to an e-mail address of a user.

When a user presses the password input field403, a software keyboard may also be displayed on the operating unit21, like the user ID input field402, and the user may press keys to input a password on the software keyboard so that the input password is displayed in the password input field403.

In response to a press on the “LOG-IN” button404performed by a user, the information processing apparatus1performs log-in processing. While this embodiment uses a user ID and a password to perform log-in processing, log-in processing may be performed by another method using an IC card, for example.

FIG. 4illustrates an example of a basic screen201for defining settings regarding a destination to be displayed on the operating unit21after a user logs into the information processing apparatus1. This screen is displayed on the operating unit21in response to a predetermined operation performed by a user after he or she logs in. The predetermined operation may be an operation for displaying a screen relating to destination settings to be performed on a screen for using a facsimile function or an e-mail function, for example, by a user.

A button202is usable by a user for displaying a screen for newly inputting a destination. A button203is usable for opening an address book. A button204is usable by a user for defining a setting relating to a domain name button to be displayed on the e-mail address input screen. A “LOG OUT” button205is usable by a user for performing processing for logging out from the information processing apparatus1.

FIG. 5illustrates an example of a screen to be displayed on the operating unit21as a screen for inputting an e-mail address. An e-mail address input screen701is to be displayed on the operating unit21when a user presses the button202on the basic screen201or when an operation for adding a new destination to an address book is performed after the button203is pressed. A user may press text input keys706so that text corresponding to pressed keys is displayed in an address display area702. Domain name buttons703and704are usable for inputting a domain name. Referring toFIG. 5, two domain name buttons are displayed. However, the number of domain name buttons to be displayed is not limited thereto. In response to a press on one of the domain name buttons703and704performed by a user, a domain name displayed on the domain name button is displayed at the end of the character string displayed in the address display area702.

A button705is usable for displaying a domain name that is not displayed on the domain name buttons703and704. In response to a press of the button705performed by a user, a pop-up screen801illustrated inFIG. 6is displayed.

An area804displays a total number of pages of a screen801and the page number of the currently displayed pages. Referring toFIG. 6, the screen801displays the first page of one page in total, the area804displays “1/1”. A button803is usable for moving to another page. Referring toFIG. 6, because there is no page other than the currently displayed page, the button803is displayed in a gray-out state. If moving to another page is possible, the button803is not displayed in a gray-out state. The page to be displayed is changed in response to a press of the button803performed by a user.

In response to a press on a domain name button805performed by a user, the applicable domain name is displayed on the address display area702. When a user presses a number button806, the domain name on the domain name button805displayed on the right-hand side of the number button is displayed on the address display area702. A user may also use one of the domain name button805and the number button806to input a domain name. The information processing apparatus1may have a numeric keypad, not illustrated, and the numeric keypad may be used to input a number so that the domain name displayed on the right-hand side of the number button806corresponding to the input number may be input. A “CLOSE” button802is usable for closing the screen801. After a user presses the domain name button805or the number button806and inputs a domain name, the user may press the “CLOSE” button802to close the screen and return to the e-mail address input screen701.

Each of the domain name buttons703,704, and805can display a domain name stored in a shared domain name database prestored in the hard disk13, for example.

Alternatively, each of the domain name buttons703,704, and805may display a domain name of an e-mail address registered with a personal address book which is allowed to be used by a log-in user or a domain name of an e-mail address of the user. A domain name to be used may be registered with a personal domain name database for each user, and the domain name registered with the domain name database of a log-in user may be displayed on one of the domain name buttons.

By using an e-mail address registered with a personal address book of a log-in user, an e-mail address of the user, or a personal domain name database for each user, a domain name to be displayed on a domain name button may be determined for each log-in user. According to this embodiment, it may be set in advance such that a domain name obtained by a user based on a certain method can be displayed on a domain name button on the e-mail address input screen701. In accordance with the setting, the domain name to be displayed on the domain name button is obtained, and a domain name button having the domain name thereon is displayed on the e-mail address input screen701.

With reference toFIGS. 18A to 18D, information stored in the hard disk13for obtaining a domain name to be displayed on a domain name button will be described. The information to be used for obtaining a domain name may be a database of user shared and user personal domain names, a user personal address book, a user ID, or a user e-mail address.

FIG. 18Ais a schematic diagram of a shared domain name database which is stored in the hard disk13and which is usable when a user logs in. A registration number and a domain name are stored in the hard disk13in association. The e-mail address input screen701displays domain names in increasing order of the associated registration numbers. A domain name not displayed because of the limited space of the area for displaying domain name buttons on the e-mail address input screen701is displayed on the pop-up screen801.

FIG. 18Bis a schematic diagram illustrating a personal domain name database, which is stored in the hard disk13, of a log-in user. A user ID field stores a user ID of a user associated with the personal domain name database.FIG. 18Billustrates a personal domain name database of a user with a user ID “11111”.

FIG. 18Cis a schematic diagram illustrating a personal address book which is stored in the hard disk13and which is managed for each user. The personal address book stores a user ID of a user who uses the address book and a registration number, a registered name, and an e-mail address of an address in association.FIG. 18Cillustrates a personal address book of a user having a user ID “abcde”.

FIG. 18Dis a schematic diagram illustrating data which is stored in the hard disk13and which stores a user ID and an e-mail address of a log-in user. When a user logs in, the data are to be used for obtaining an e-mail address of a log-in user. For example, referring toFIG. 18D, when a user with a user ID “11111” logs in, an e-mail address “AAA@aaa.ne.jp” of the log-in user is obtained.

According to this embodiment, a domain name is obtained from one of shared and personal domain name databases, a personal address book, and e-mail addresses stored in forms illustrated inFIGS. 18A to 18Dand is displayed on a domain name button.

FIG. 7is a flowchart illustrating a flow of processing to be performed during a period from a time when a user logs into the information processing apparatus1to a time when the user logs out. A program for executing the processing illustrated inFIG. 7may be stored in the hard disk13, be developed in the RAM12, and be executed by the CPU11.

The processing illustrated in the flowchart inFIG. 7is started with supply of power to the information processing apparatus1.

The CPU11executes authentication processing on a user (S101). Processing to be executed as the authentication processing will be described below with reference toFIG. 8.

The CPU11displays the basic screen201illustrated inFIG. 4on the operating unit21in response to a predetermined operation performed by a user after a user logs in (S102).

The CPU11determines whether the user has pressed the button202for inputting a new destination on the basic screen201displayed on the operating unit21(S103). If it is determined that the button202has been pressed, the CPU11performs domain-name obtaining processing based on setting information stored in the hard disk13(S104). Processing details of the domain-name obtaining processing to be performed by the CPU11will be described below with reference toFIG. 9.

After the CPU11performs the domain-name obtaining processing, the CPU11performs address input processing (S105). Processing details to be performed by the CPU11in S105will be described below with reference toFIG. 10.

After the CPU11performs the address input processing, an e-mail is transmitted to an input e-mail address (S106). The transmission processing to be performed by the CPU11in S106will be described below with reference toFIG. 11. After the transmission processing is performed, the CPU11executes processing in S111.

Next, in S103, if it is determined that the button202has not been pressed, the CPU11determines whether the button203for defining a setting regarding an address book has been pressed (S107). If it is determined that the button203has been pressed, the CPU11performs address book processing for selecting a destination from an address book stored in the hard disk13or adding an address to the address book stored in the hard disk13(S108). The address book processing will be described below with reference toFIGS. 13 and 14. After the address book processing is executed, the CPU11executes the processing in S111.

In S107, if it is determined that the button203has not been pressed, the CPU11determines whether the button204has been pressed (S109). If it is determined in S109that the button204has been pressed, the CPU11performs domain-name-obtaining setting processing (S110). The domain-name-obtaining setting processing is performed for setting a domain name to be displayed on the domain name button703or704to be displayed on the e-mail address input screen701. The domain-name-obtaining setting processing will be described with reference toFIGS. 15 to 17. After the domain-name-obtaining setting processing is executed, the CPU11executes the processing in S112.

If it is determined in S109that the button204has not been pressed, the CPU11determines whether the “LOG OUT” button205has been pressed (S111). If it is determined that the “LOG OUT” button205has been pressed, the CPU11executes processing for causing the log-in user to log out the information processing apparatus1. After the CPU11completes the logout processing, the CPU11returns the processing to S101.

If it is determined that the “LOG OUT” button205has not been pressed, the CPU11returns the processing to S103.

FIG. 8is a flowchart illustrating a flow of processing to be executed by the CPU11in the authentication processing in S101inFIG. 7. The processing in the flowchart is implemented by a program stored in the hard disk13, developed in the RAM12and executed by the CPU11.

The CPU11displays the log-in screen401illustrated inFIG. 3on the operating unit21(S301). After the log-in screen401is displayed, the CPU11receives a user ID and a password input from a user.

The CPU11determines whether the “LOG-IN” button404has been pressed (S302). If it is determined that the “LOG-IN” button404has been pressed, the CPU11authenticates the user by using the input user ID and password (S303). If it is determined that the “LOG-IN” button404has not been pressed, the processing in S302is continuously performed. According to this embodiment, the hard disk13stores a user ID and a password in association, and the CPU11checks whether user information having the input user ID and password is stored in the hard disk13. The information containing a user ID and a password in association may be stored in a storage device such as an external server connected over the network2. In this case, in S303, the CPU11checks whether user information having the user ID and password input onto the log-in screen401is stored in the external server.

The CPU11determines the authentication has succeeded (S304). If user information having the user ID password input onto the log-in screen401is in the hard disk13, the CPU11determines that the authentication has succeeded. Then, the processing on the flowchart ends. If the authentication has not succeeded, the CPU11returns the processing to S302. In this case, a screen for notifying a user of that the authentication has failed is displayed on the operating unit21.

Having described the processing illustrated inFIG. 8as the authentication processing according to this embodiment, any other publicly known method may be applied if a user of the information processing apparatus can be identified.

FIG. 9is a flowchart illustrating a flow of processing to be executed by the CPU11in the domain-name obtaining processing in S104inFIG. 7. The processing according to the flowchart is implemented by a program which is stored in the hard disk13, is developed in the RAM12, and is executed by the CPU11. The processing illustrated inFIG. 9is started in response to a press of the button202performed by a user on the basic screen201displayed in the operating unit21.

The CPU11obtains a setting for obtaining a domain name stored in the hard disk13(S901). A setting for obtaining a domain name can be defined by executing the processing in S109inFIG. 7.

The CPU11determines whether the setting obtained in S901is defined to obtain a domain name from an address book (S902). If the setting obtained in S901is defined to obtain a domain name from an address book, the CPU11obtains an e-mail address stored in a personal address book, which is stored in the hard disk13, of a log-in user (S903). For example, if the log-in user has a user ID “abcde”, all e-mail addresses with registration numbers1to6are obtained from the personal address book as illustrated inFIG. 18C, which is stored in the hard disk13.

The CPU11obtains a domain name from the e-mail addresses obtained in S903(S904). The CPU11extracts, as a domain name, a character string located after a predetermined delimiter such as an at sign from the obtained e-mail address. For example, in a case where an e-mail address “aaa@email-domain.jp” is obtained in S901, a part “email-domain.jp” is extracted as a domain name. This is performed on all of the e-mail addresses registered with the personal address book.

The CPU11sorts the extracted domain names in decreasing order of the number of e-mail addresses registered with the address book (S905). For example, the personal address book illustrated inFIG. 18Chas three e-mail addresses including “xxx.ne.jp”, two e-mail addresses including “email-domain.jp”, and one e-mail address including “yyy.co.jp”. In this case, in S905, the CPU11sorts the obtained domain names in order of “xxx.ne.jp”, “email-domain.jp”, and “yyy.co.jp”. After the processing in S905completes, the CPU11exits the processing in the flowchart.

In S902, if the setting obtained in S901is not defined to obtain a domain name from the address book, the CPU11determines whether the obtained setting is a common setting (S906). A common setting is a setting for displaying on a domain name button on the e-mail address input screen, a domain name registered with a shared domain name database stored in the hard disk13even when any user logs into the information processing apparatus1.

If the setting obtained in S901is a common setting, the CPU11obtains a domain name stored in a shared domain name database stored in the hard disk13(S907). For example, if the shared domain name database is the one illustrated inFIG. 18A, the CPU11obtains all of five domain names having registration numbers1to5in S907. After the processing in S907, the processing illustrated inFIG. 9ends.

If the setting obtained in S901is not a common setting, the CPU11determines whether the obtained setting is a personal setting (S908). A personal setting is a setting for displaying a domain name button by using a personal domain name database stored in association with user information in the hard disk13.

If the setting obtained in S901is a personal setting, the CPU11obtains a domain name registered with a personal domain name database of a log-in user (S909). For example, when a log-in user has a user ID “11111” and his or her personal domain name database is the one inFIG. 18B, the CPU11in S909obtains all of three domain names having registration numbers1to3. After the processing in S909ends, the processing illustrated inFIG. 9ends.

If the setting obtained in S901is not a personal setting, the CPU11determines whether the obtained setting is a setting defined to obtain a domain name from a personal e-mail address (S910). If the setting obtained in S901is a setting defined to obtain a domain name from a personal e-mail address, the CPU11obtains an e-mail address of the log-in user from the hard disk13. After that, a character string located after a delimiter such as an at sign is extracted from the obtained e-mail address (S911). For example, when the log-in user has a user ID “11111”, an e-mail address “AAA@aaa.ne.jp” of the log-in user is obtained from the one inFIG. 18Dstored in the hard disk13. The part after @ in the obtained e-mail address, that is, “aaa.ne.jp” is then obtained as a domain name. After the processing in S911, the processing inFIG. 9ends.

FIG. 10is a flowchart illustrating a flow of processing to be executed by the CPU11in the address input processing in S105illustrated inFIG. 7. The processing according to the flowchart is implemented by a program which is stored in the hard disk13, is developed in the RAM12, and is executed by the CPU11. The flowchart is started in response to completion of the domain-name obtaining processing illustrated inFIG. 9.

The CPU11displays the e-mail address input screen701illustrated inFIG. 5on the operating unit21(S601).

The CPU11uses the domain names obtained in the domain-name obtaining processing to display the domain name buttons703and704(S602). After the processing in S602completes, the CPU11receives a press on the text input key706, the domain name button703or704, or the button705performed by a user through the operating unit21. A user may use the key or button to input an e-mail address. Having described that a plurality of domain name buttons are displayed according to this embodiment, one domain name button may be displayed.

The CPU11determines whether an “OK” button707has been pressed (S603). If it is determined that the “OK” button707has been pressed, the CPU11determines that completion of the operation for inputting an e-mail address is instructed and exits the processing illustrated in the flowchart inFIG. 10. In this case, a transmission screen1101inFIG. 12, which will be described below, is displayed which includes the character string displayed on the address display area702as the input e-mail address.

If it is determined that the “OK” button707has not been pressed, the CPU11determines whether the domain name button703or704has been pressed (S604). It is assumed here that it is determined that the domain name button703or704has been pressed in the flowchart. In a case where many domain names are obtained in S601, a screen illustrated inFIG. 6may be displayed in response to a press on the button705so that a domain name other than the domain names displayed on the domain name buttons703and704can be input.

If it is determined that one of the domain name buttons703and704has been pressed, the CPU11adds and displays the domain name corresponding to the pressed domain name button to the end of the character string displayed in the address display area702(S605). After the domain name is added in the address display area702, the CPU11returns the processing to S603.

If it is determined in S604that none of the domain name buttons703and704has not been pressed, the CPU11determines whether the text input key706has been pressed (S606). If the text input key706has been pressed, the CPU11displays text corresponding to the pressed text input key in the address display area702(S607). After the text corresponding to the pressed key is displayed in the address display area702, the CPU11returns the processing to S603.

If the text input key706has not been pressed, the CPU11returns the processing to S603.

FIG. 11is a flowchart illustrating a flow of processing to be executed by the CPU11in the transmission processing in S105illustrated inFIG. 7. The processing according to the flowchart is implemented by a program which is stored in the hard disk13, is developed in the RAM12, and is executed by the CPU11. The processing illustrated inFIG. 11is started in response to completion of the address input processing illustrated inFIG. 10.

The CPU11displays the transmission screen1101illustrated inFIG. 12on the operating unit21. A destination display area1102displays an e-mail address of a destination. A “START” button1104is usable for scanning a document by using the scanner19and transmitting an e-mail to a destination displayed in the destination display area1102. A “CANCEL” button1103is usable for exiting the transmission processing.

The CPU11displays the e-mail address input in S104in the destination display area1102(S1002). The CPU11determines whether the “START” button1104has been pressed (S1003). If it is determined that the “START” button1104has been pressed, the CPU11requests the scanner I/F17to start scanning of a document by using the scanner19. Then, the scanner19scans the document (S1004). After the scanning of the document by the scanner19completes, the CPU11receives image data generated by the scanner19through the scanner I/F17.

The CPU11transmits image data generated by scanning the document in S1004to the e-mail address input in S104(S1005). After the transmission completes, the CPU11exits the processing on the flowchart illustrated inFIG. 11ends.

If it is determined in S1003that the “START” button1104has not been pressed, the CPU11determines whether the “CANCEL” button1103has been pressed (S1006). If the “CANCEL” button1103has been pressed, the processing illustrated inFIG. 10ends. If the “CANCEL” button1103has not been pressed, the CPU11returns the processing to S1003.

Next, with reference toFIGS. 13 and 14, the address book processing in S107illustrated inFIG. 7will be described. The address book processing is processing for newly registering a destination to an address book and invoking a registered destination.

FIG. 13illustrates an example of an address book screen1301to be displayed when a user presses the button203on the basic screen201. A destination designation button1302is usable for selecting a destination of an email from destinations registered with an address book stored in the hard disk13. A destination addition button1303is usable for adding a new destination to an address book stored in the hard disk13.

FIG. 14is a flowchart illustrating a flow of processing to be executed by the CPU11in the address book processing in S107illustrated inFIG. 7. The processing according to the flowchart is implemented by a program which is stored in the hard disk13, is developed in the RAM12, and is executed by the CPU11.

The CPU11displays the address book screen1301illustrated inFIG. 13on the operating unit21(S1201). The CPU11determines whether the destination designation button1302has been pressed (S1202). If the destination designation button1302has been pressed, the CPU11obtains from the hard disk13a personal address book stored in association with the user authenticated by the authentication processing illustrated inFIG. 8(S1203).

The CPU11displays a list of destinations stored in the personal address book obtained in S1203on the operating unit21(S1204).

The CPU11determines whether a destination has been designated from the list of destinations displayed in S1204(S1205). For example, it is determined that a destination has been designate based on a press of an arbitrary destination performed by a user among the displayed listed destinations. An “OK” button may be displayed on a screen displaying a list of destinations, not illustrated. When a user presses and selects an arbitrary destination among listed destinations and then presses the “OK” button, it may be determined that the selected destination has been designated.

If no destination has been designated in S1205, the CPU11continuously executes the processing in S1204.

After a destination is designated in S1205, the CPU11executes the transmission processing illustrated inFIG. 11(S105).

If it is determined in S1202that the destination designation button1302has not been pressed, the CPU11determines whether the destination addition button1303has been pressed (S1206). If the destination addition button1303has been pressed, the CPU11executes the domain-name obtaining processing (S104) and the address input processing (S105). After the address input processing ends, the CPU11registers the input destination with the personal address book of the log-in user stored in the hard disk13. The processing in the flowchart ends (S1207).

Next, the domain-name-obtaining setting processing in S109illustrated inFIG. 7will be described with reference toFIGS. 15 to 17.FIGS. 15 and 16illustrates examples of screens to be displayed on the operating unit21in order to define a setting for obtaining a domain name.

FIG. 15illustrates a domain-name-obtaining setting screen1501to be displayed on the operating unit21when a user presses the button204on the basic screen201illustrated inFIG. 4. A button1502is usable for defining a setting for obtaining a domain name to be displayed on a domain name button from an e-mail address registered with an address book. According to this embodiment, in response to a selection of the button1502, a domain name of an e-mail address registered with a personal address book of a log-in user is displayed on a domain name button on the e-mail address input screen.

A button1503is usable for defining a setting for displaying on a domain name button a domain name registered with a shared domain name database stored in the hard disk13in the information processing apparatus1. When a user presses the button1503, a domain name input screen1601illustrated inFIG. 16is displayed on the operating unit21. A domain name to be displayed here or a domain name to be input here corresponds to a domain name which can be used in common for displaying a domain name button by any user logging into the information processing apparatus1. A domain name is registered with a number1602. Domain name buttons are displayed in increasing order of the number1602on the e-mail address input screen701.

FIG. 16illustrates a domain name display area1603. The domain name display area1603displays a domain name registered with a domain name database. A user may press the domain name display area to change the domain name displayed on the display area. For example, when a user press a domain display area having “email-domain.jp” thereon, a software keyboard may be displayed on the operating unit21so that the user can input a character string on the domain name display area. In response to a press of a “SET” button1604performed by a user, the display of the domain name input screen1601is closed.

The button1504is set to be usable for displaying on the e-mail address input screen701a domain name registered with a personal domain name database stored in the hard disk13for each user. In response to a press on the button1504performed by the user, the domain name input screen1601illustrated inFIG. 16is displayed. However, a domain name registered on the screen is displayed on the e-mail address input screen701only when a user logs in who is identical to the user logging into the information processing apparatus1. Therefore, when a different user logs in, a domain name registered with the personal domain name database by the different user is displayed on the domain name button.

A button1505on the domain-name-obtaining setting screen1501is set to display a domain name of an e-mail address of a log-in user on a domain name button. A user who is allowed to log in the information processing apparatus1is given a personal e-mail address. According to this embodiment, the association between a user and a personal e-mail address is stored in the hard disk13in the information processing apparatus1. However, the association between a user and a personal e-mail address may be stored in an external storage device connected to the information processing apparatus1.

FIG. 17is a flowchart illustrating a flow of processing to be executed by the CPU11in the domain-name-obtaining setting processing in S110illustrated inFIG. 7. The processing according to the flowchart is implemented by a program which is stored in the hard disk13, is developed in the RAM12, and is executed by the CPU11.

The processing illustrated inFIG. 17starts in response to a press on the button204on the basic screen201displayed on the operating unit21.

The CPU11displays a domain-name-obtaining setting screen illustrated inFIG. 15on the operating unit21(S1401). After that, the CPU11determines whether the button1502has been pressed to select an address book (S1402). If it is determined that the button1502has been pressed, the CPU11displays the e-mail address input screen701on the operating unit21by storing in the hard disk13a setting for displaying a domain name of an e-mail address registered with a personal address book (S1403). After that, the processing illustrated in the flowchart ends.

If it is determined that the button1502has not been pressed, the CPU11determines whether the button1503has been pressed to select a common setting (S1404). If the button1503has been pressed, the CPU11obtains a shared domain name database stored in the hard disk13and displays the domain name input screen1601on the operating unit21(S1405). In S1405, the CPU11displays the domain name input screen illustrated inFIG. 16by using a registration number and domain name stored in a shared domain name database illustrated inFIG. 18A. After that, a domain name is registered on the domain name input screen1601based on a user's operation.

In response to a press on a “SET” button1604performed by a user, the CPU11stores in the hard disk13a setting for displaying a domain name registered with a common setting on a domain name button on the e-mail address input screen (S1403). Here, domain names stored are used as a shared domain name database. After that, the processing illustrated in the flowchart ends.

If the button1503has not been pressed, the CPU11determines whether the button1504has been pressed to select a personal setting (S1407). If the button1504has been pressed, the CPU11displays the domain name input screen illustrated inFIG. 16on the operating unit21(S1408). In S1408, the CPU11displays the domain name input screen illustrated inFIG. 16based on the personal domain name database illustrated inFIG. 18B, which is stored in the hard disk13, on the operating unit21. After that, a domain name is registered on the domain name input screen1601based on a user's operation.

In response to a press on the “SET” button1604performed by a user, the CPU11stores in the hard disk13the currently logging in user and the domain name input on the domain name input screen1601in association as a personal setting. Thus, a user can add or delete a domain name registered with his or her personal domain name database. The CPU11stores in the hard disk13a setting for displaying a domain name stored as a personal setting on a domain name button on the e-mail address input screen in response to a press performed on the “SET” button1604(S1409). Here, domain names stored in the hard disk13are used as a personal domain name database.

If the button1504has not been pressed, the CPU11determines whether the button1505has been pressed to select a personal e-mail address (1410). If the button1410has been pressed, the CPU11stores in the hard disk13a setting for displaying a domain name of an e-mail address of a log-in user on a domain name button on the e-mail address input screen while the user is logging in (S1411). After that, the processing illustrated in the flowchart ends.

If the button1505has not been pressed, the CPU11returns the processing to S1401.

According to the first embodiment, a personal address book is stored in the hard disk13. A shared address book which is available to all users of the information processing apparatus1may be stored in the hard disk13in addition to a personal address. In this case, when an address book is selected as a domain-name-obtaining setting, a domain name of an e-mail address registered with the personal address book and the shared address book is displayed on a domain name button.

According to the first embodiment, it is set for obtaining a domain name from a personal address book or a user's personal e-mail address. With the setting, a character string located after a delimiter such as an at sign is extracted from an e-mail address registered with the personal address book or an e-mail address of a log-in user, and is displayed on a domain name button. Thus, the domain name button to be displayed can be determined for each user logging into the information processing apparatus.

According to the first embodiment, the domain-name-obtaining setting is a personal setting so that a domain name registered with a personal domain name database can be displayed on a domain name button. Thus, a domain name to be displayed on a domain name display button can be determined for each user. This can prevent a domain name which is not used by a log-in user from being displayed on a domain name button.

Furthermore, a domain to be input, which is selected from displayed domain name candidates, is received so that a user can input a domain name without being required to input the domain name letter by letter by using a keyboard.

OTHER EMBODIMENTS

According to the first embodiment, a domain name to be displayed may be obtained from one of a personal address book, a shared domain name database, a personal domain name database, and an e-mail address of a log-in user. However, a domain name to be displayed may be obtained from a plurality of the sources described above as well.

For example, it may be configured such that a user can set whether to use a personal address book, a shared domain name database, a personal domain name database, and an e-mail address of a log-in user as a source of a domain name or not, individually. Thus, in some embodiments, more domain names can be displayed on domain name buttons than those of the first embodiment.

According to the first embodiment, a domain name may be obtained from an e-mail address registered with a personal address book of a log-in user. Users may be divided into groups in advance, and a domain name of an e-mail address registered with an address book of another user in a group to which a log-in user belongs or a shared address book of the group, may be displayed on a domain name button.

According to the first embodiment, on the e-mail address input screen701, the domain name buttons703and704can be displayed as keys that can be pressed. However, without limiting to the above method, candidates for a domain name may be displayed by other methods as well. For example, on the e-mail address input screen701, a user may input an e-mail address, and a list of candidates for a domain name may be displayed in the address display area702in response to input of a delimiter such as an at sign performed by a user. In response to a selection of a domain name from a domain name list performed by a user, the selected domain name may be displayed as a character string to be input in an address display area.

According to the first embodiment, a character string located after an at sign defined as a delimiter is displayed as a domain name on the e-mail address input screen701. A character string including an at sign may be displayed as a domain name on the e-mail address input screen701.

The present disclosure may be implemented by execution of the following processing. That is, software (for example, a program or programs) implementing functions of the aforementioned embodiments may be supplied to a system or an apparatus over a network or through a storage medium, and a computer (or a processor, CPU or an MPU, for example) in the system or the apparatus may read out and execute the program. In this case, the computer program and a storage medium storing the computer program are components of embodiments of the present disclosure.

Various embodiments of the present disclosure can determine a candidate for a domain name to be displayed for each user of an information processing apparatus.

This application claims the benefit of Japanese Patent Application No. 2016-230826 filed Nov. 29, 2016, which is hereby incorporated by reference herein in its entirety.