JP6291145B2 - Information processing apparatus, information processing method, program, and storage medium - Google Patents

Description

  The present invention relates to an information processing apparatus, an information processing method, a program, and a storage medium for managing recipes. Specifically, the present invention relates to various processes for presenting a recipe to a user.

JP2013-117775A

  In recent years, recipe search sites and software that can search recipes accumulated by postings by general users from a computer such as a PC have become widespread (for example, Patent Document 1). In these fields, for example, a recipe that the user may desire is estimated and presented to the user. In this case, a recipe may be searched and presented based on the user's preference information (information about taste ingredients and non-taste ingredients).

However, the recipe presentation based on the user's preference information often becomes an ordinary recipe that the user can come up with.
Therefore, an object of the present invention is to present an unusual recipe using a user's favorite ingredients.

An information processing apparatus according to the present invention includes:
Recipe management unit that classifies used ingredients set in a recipe into normal ingredients that are used frequently and non-usual ingredients that are used less frequently in the category to which the recipe belongs, and a preference that determines the ingredients that the user likes as favorite ingredients An ingredient determination part, a search part that searches for a recipe based on a search condition input by a user, and a user who increases the presentation priority of a recipe that includes the favorite ingredient in the non-normal ingredient among the searched recipes And a presenting unit for presenting.
This presents a recipe that is likely to be satisfied while changing the user's eating habits.

The preference food determination unit of the information processing apparatus described above determines a food not preferred by the user as a non-preference food.
Thereby, not only the ingredients that the user likes, but also the ingredients that are not preferred are managed.

The preference food determination unit of the information processing apparatus described above assigns a score to each user and food, determines a food having a score equal to or higher than a first threshold as the user's favorite food, and is less than a second threshold. The determined food material is determined as the non-preferred food material of the user.
Thereby, the digitized preference information is managed for each combination of the user and the food.

The preference food determination unit of the information processing apparatus described above determines the non-normal food of the usage estimation recipe estimated to be used by the user as the user's preference food, and among the normal foods in the category to which the usage estimation recipe belongs In this case, ingredients that are not used in the usage estimation recipe are determined as candidates for the non-preferred ingredients.
Thereby, a user's favorite foodstuff is determined based on the recipe estimated that the user actually used.

The preference food determination unit of the information processing apparatus described above determines the food input by the user as a search condition as the user's preference food.
Thereby, since the information of the favorite food is collected using the information when the user performs the search operation, the information can be efficiently collected without imposing an extra operation burden on the user.

The preference food determination unit of the information processing apparatus described above performs the determination for each time and season.
Thereby, preference information is updated regularly according to a season.

The presenting unit of the information processing apparatus described above lowers the presentation priority of a recipe that uses the non-preferred ingredients.
Thereby, the recipe search which considered both a user's favorite food and a non-taste food is made.

The preference food determination unit of the information processing apparatus described above determines an excluded food set as a search condition by the user as a non-preference food.
Thereby, information on non-preferred ingredients is collected using information input when the user performs a search operation.

An information processing method according to the present invention is an information processing method executed by an information processing apparatus , and uses used ingredients set in a recipe with normal ingredients that are used frequently and unusually used less frequently in the category to which the recipe belongs. Among the searched recipes, a classification step for classifying the ingredients into ingredients, a preference ingredient determination step for determining a favorite ingredient as a favorite ingredient, a search step for searching a recipe based on a search condition input by the user, And a presentation step of increasing the presentation priority of the recipe in which the favorite ingredient is included in the non-normal ingredient and presenting it to the user.
By this information processing method, an environment in which rare recipes using the user's favorite ingredients are easily presented is constructed.
The program according to the present invention is a program that causes an information processing apparatus to execute processing executed as the information processing method.
A storage medium according to the present invention is a storage medium storing the above program. The above information processing apparatus is realized by these programs and storage media.

  ADVANTAGE OF THE INVENTION According to this invention, the unusual recipe which uses a user's favorite foodstuff can be made easy to be shown.

It is explanatory drawing which shows the whole structure containing the information processing apparatus of embodiment of this invention. It is a block diagram which shows the structure containing a recipe management server and another apparatus. It is a block diagram of a computer apparatus. It is a figure explaining some information memorized by recipe DB. It is a figure explaining some information memorized by recipe DB. It is a figure which shows an example of the flow of a process. It is a flowchart which shows the flow of the process which a recipe management server performs. It is a flowchart which shows the 1st example of a presentation priority calculation process. It is a flowchart which shows the 2nd example of a presentation priority calculation process. It is a flowchart which shows the example of a batch process. It is a flowchart which shows the example of a classification process. It is a flowchart which shows the 1st example of a favorite food determination process. It is a flowchart which shows the 2nd example of a favorite food determination process. It is a flowchart which shows the 3rd example of a favorite food determination process. It is a flowchart which shows the 1st example of a non-preferred foodstuff determination process. It is a flowchart which shows the 2nd example of a non-preferred foodstuff determination process. It is a flowchart which shows the 3rd example of a non-preference foodstuff determination process. It is a flowchart which shows the example of a use estimation process.

Hereinafter, embodiments will be described in the following order.
<1. Overall configuration>
<2. Hardware configuration>
<3. DB>
[3-1. Recipe DB]
[3-2. User DB]
[3-3. Search DB]
<4. Process flow>
[4-1. Example of processing flow]
[4-2. Processing example of recipe management server]
[4-3. First example of presentation priority calculation process]
[4-4. Second example of presentation priority calculation processing]
[4-5. Batch processing]
[4-6. Classification process]
[4-7. First example of preference ingredient determination process]
[4-8. Second example of preference ingredient determination process]
[4-9. Third example of preference food determination process]
[4-10. First Example of Non-preferred Ingredient Determination Process]
[4-11. Second example of non-preferred food determination process]
[4-12. Third Example of Non-preference Food Ingredient Determination Process]
[4-13. Usage estimation process]
[4-14. Example of batch processing execution timing]
<5. Summary>
<6. Program and Storage Medium>

<1. Overall configuration>

First, the overall configuration in the embodiment of the present invention will be described.
In the following description, a cooking recipe (hereinafter simply referred to as a recipe) will be described as an evaluation target.
As shown in FIG. 1, the overall configuration including the information processing apparatus of the present invention is such that the recipe management server 1 can communicate with user terminals 3, 3, 3,... Connected with. The recipe management server 1 is connected to a recipe DB (Database) 50 in which information about recipes is stored, a user DB 51 in which information about users is stored, and a search DB 52 in which information on search keywords and search results is stored. . The recipe management server 1 corresponds to an embodiment of the information processing apparatus of the present invention.

  The recipe management server 1 is an information processing apparatus that manages a recipe posted by a user. A specific configuration will be described later.

The configuration of the communication network 2 is not particularly limited. For example, the Internet, an intranet, an extranet, a LAN (Local Area Network), a CATV (Community Antenna TeleVision) communication network, a virtual private network (Virtual Private Network), a telephone line A network, a mobile communication network, a satellite communication network, etc. are assumed.
Various examples of transmission media constituting all or part of the communication network 2 are also envisaged. For example, IEEE (Institute of Electrical and Electronics Engineers) 1394, USB (Universal Serial Bus), power line carrier, telephone line, etc., infrared, IrDA (Infrared Data Association), Bluetooth (registered trademark), 802.11 wireless It can also be used wirelessly, such as mobile phone networks, satellite lines, and digital terrestrial networks.

The user terminal 3 is a terminal used by a user who posts a recipe to the recipe management server 1, a user who browses recipe information managed by the recipe management server 1, and the like.
In the user terminal 3, various transmission / reception processes and display processes are executed as necessary. The user terminal 3 is, for example, a PC (Personal Computer), a feature phone, a PDA (Personal Digital Assistant) having a communication function, or a smart device such as a smartphone or a tablet terminal.

  As shown in FIG. 2, the recipe management server 1 includes a recipe management unit 1a, a favorite food determination unit 1b, a search unit 1c, and a presentation unit 1d.

The recipe management unit 1a manages the category information to which the recipe belongs and the ingredient information used for the recipe in association with the recipe posted by the user. For example, a recipe of “vegetable curry” posted by a user is a recipe belonging to the category “curry and rice”, and as used ingredient information, “potato”, “carrot”, “onion”, “broccoli”, “tomato” , "Spinach" is tied.
Moreover, the recipe management part 1a manages the normal foodstuff with high use frequency for every category. Specifically, for the category of “curry and rice”, “potato”, “carrot”, “onion”, “beef”, “pork”, and “chicken” that frequently appear in the ingredients used in recipes belonging to the same category. Usually set as an ingredient. In addition to foodstuffs, seasonings (such as “salt” and “pepper”) and the like (such as “carrero”) may be set as normal foodstuffs.
Further, the recipe management unit 1a manages the foods associated with the recipe by classifying them into normal foods and non-normal foods in the category to which the recipe belongs. In the following description, an example will be described in which all ingredients that do not correspond to ordinary ingredients are classified as non-ordinary ingredients, but they may be classified into three ingredients that do not fall into either ordinary ingredients or unusual ingredients.
These managements are performed using the recipe DB 50.

  The recipe management unit 1a manages a creation report posted for each recipe. The created report is a report describing the deliciousness and ease of cooking that the user feels when cooking using the recipe. The creation report is associated with each recipe in the recipe DB 50 and managed.

  The preference ingredient determination unit 1b executes a judgment process related to user preference information (information about preference ingredients and non-taste ingredients). Specifically, a favorite ingredient determination process for determining a user's favorite ingredient (favorite ingredient) and a non-preferred ingredient determination process for determining a non-preferred ingredient (a non-preferred ingredient) are executed. Some examples of each process will be described later.

The search unit 1c executes a search process for searching for a recipe desired by the user from the recipe stored in the recipe DB 50 in accordance with the search condition specified by the user. As a search condition, a search keyword that is a keyword related to a recipe that is to be extracted as a search result and an excluded keyword that is a keyword that is to be excluded from the search result can be specified. Also, the date and time information when the date and time when the recipe is posted, the evaluation information when searching for a highly evaluated recipe, and the like also correspond to the search conditions.
As a search result, a search result corresponding to the search keyword is extracted by a search process periodically executed in advance, and stored in the search DB 52. Therefore, when the user performs a recipe search operation, the search result stored in the search DB 52 is extracted according to the search condition.
When a keyword that is not stored in the search DB 52 is specified (for example, when a search keyword with a low search frequency or an excluded keyword with a low search frequency is specified), the search condition is set from each recipe stored in the recipe DB 50. A process for searching for the corresponding recipe is executed.

The presentation unit 1d performs processing for presenting the recipe extracted as a search result on the user terminal 3. Specifically, the presentation priority of each recipe is calculated for the search result extracted by the search unit 1c according to the search condition specified by the user. Furthermore, a process of generating a search result presentation page corresponding to the presentation priority and transmitting it to the user terminal 3 is executed.
In addition, the presentation unit 1d executes processing for transmitting various web page data corresponding to the user's operation. Examples of various web page data include web page data on a login screen, web page data on a recipe detail page, and web page data on a creation report posting page.
The data of these web pages is a structured document file such as HTML (Hyper Text Markup Language) or XHTML (Extensible HyperText Markup Language). The structured document file describes recipe names, ingredients used, image data such as text data and cooking images as cooking procedures, and their arrangement and display mode (character color, font, size, decoration, etc.). Yes.

In addition, the recipe management server 1 is provided with various units necessary for realizing a function of transmitting and receiving various types of information and an authentication process for a user login operation. The authentication process is a process for collating the user ID (Identification) and password as login information transmitted from the user terminal 3 with the authentication information stored in the user DB 51.

<2. Hardware configuration>

FIG. 3 is a diagram illustrating the hardware of the recipe management server 1 and the user terminal 3 and the hardware of the recipe DB 50, the user DB 51, and the search DB 52 shown in FIG. A CPU (Central Processing Unit) 101 of a computer device in each server, terminal, or DB is loaded into a RAM (Random Access Memory) 103 from a program stored in a ROM (Read Only Memory) 102 or a storage unit 108. Various processes are executed according to the program. The RAM 103 also appropriately stores data necessary for the CPU 101 to execute various processes.
The CPU 101, ROM 102, and RAM 103 are connected to each other via a bus 104. An input / output interface 105 is also connected to the bus 104.
The input / output interface 105 includes an input device 106 composed of a keyboard, mouse, touch panel, etc., a display composed of a liquid crystal display (LCD), a cathode ray tube (CRT), an organic EL (electroluminescence) panel, and an output composed of a speaker. A device 107, a storage unit 108 including an HDD (Hard Disk Drive), a flash memory device, and the like, and a communication unit 109 that performs communication processing and communication between devices via the communication network 2 are connected.
A media drive 110 is also connected to the input / output interface 105 as necessary, and a removable medium 111 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory is appropriately mounted, and information can be written to the removable medium 111. Reading is performed.

In such a computer apparatus, data and programs can be uploaded and downloaded through communication by the communication unit 109, and data and programs can be transferred via the removable medium 111.
As the CPU 101 performs processing operations based on various programs, information processing and communication described later are executed in each of the recipe management server 1, the user terminal 3, the recipe DB 50, the user DB 51, and the search DB 52.
In addition, each information processing apparatus which comprises the recipe management server 1, the user terminal 3, the recipe DB 50, the user DB 51, and the search DB 52 is not limited to a single computer apparatus as shown in FIG. A plurality of computer devices may be used. The plurality of computer devices may be systemized by a LAN or the like, or may be arranged in a remote place in a communicable state by a VPN (Virtual Private Network) using the Internet or the like.

<3. DB>

[3-1. Recipe DB]
The recipe DB 50 is a DB that stores recipe information posted by the user. Specifically, as shown in FIG. 4, for a recipe ID that can identify each recipe, a user ID that identifies the user who posted the recipe, posting date information, category information to which the recipe belongs, and a recipe Used ingredients information, recipe cooking procedures, image information such as cooking images (finished cooking images and cooking images), and other users who actually used the recipe (created dishes) A creation report ID that identifies the created creation report is associated with and stored.
Further, URL (Uniform Resource Locator) information of the recipe details page may be stored in association with the recipe ID.
Further, as shown in FIG. 5, the recipe DB 50 stores information on normal ingredients and non-normal ingredients in association with each cooking category.
In addition, it is good also as all non-normal foodstuffs other than a normal foodstuff, without memorize | storing an unusual foodstuff in recipe DB50.

Further, the recipe DB 50 stores information on creation reports posted for each recipe. As the information of the created report, text data indicating the report content, a user ID that can identify the poster, posting date information, and the like are stored.
In addition, although the recipe information shown in FIG. 4, the normal / unusual food information for each category shown in FIG. 5, and the creation report information are shown as examples stored in the recipe DB 50, they are independent DBs. May be stored.

[3-2. User DB]
The user DB 51 is a DB that stores user login information. Specifically, a user ID that can identify each user and a login password are stored in association with each other. Various history information such as login history may be stored.
The user DB 51 stores preference information for each user. The preference information is the user's favorite ingredients (favorable ingredients) or disliked ingredients (non-favorable ingredients) determined by the recipe management server 1 according to the user's behavior.

[3-3. Search DB]
The search DB 52 is a DB that stores search results corresponding to search keywords. Specifically, multiple recipes are linked and stored as search results according to search keywords such as dish names such as “curry and rice” and “hamburg” and ingredient names such as “mushroom” and “tomato”. The
In order to avoid performing a new search process when a user searches, a search process using a search keyword is periodically executed in advance, and the search result extracted as a result is linked to the search keyword. And stored in the search DB 52.

<4. Process flow>

[4-1. Example of processing flow]
An example of the flow of processing executed by the recipe management server 1 and the user terminal 3 will be described with reference to FIG.
Here, in order to receive various services provided by the recipe management server 1, an example will be described in which a user performs a login operation using the user terminal 3 to search for a recipe.

  In step S101, the user terminal 3 executes a login screen information request process corresponding to a login screen display operation by the user.

When a login screen information request is transmitted from the user terminal 3 to the recipe management server 1 by the login screen information request process, the recipe management server 1 executes a login screen information transmission process in step S201.
Thereby, for example, a web page corresponding to the login screen information (web page data) of the recipe site received from the recipe management server 1 is displayed on the user terminal 3.

  Next, in step S <b> 102, the user terminal 3 executes login information transmission processing for transmitting login information (user ID and login password) according to the user's input operation to the recipe management server 1.

When the login information is transmitted from the user terminal 3 to the recipe management server 1, the recipe management server 1 executes an authentication process in step S202, and executes an authentication result notification process in the subsequent step S203.
Specifically, the recipe management server 1 compares the user ID and password input on the user terminal 3 with information stored in the user DB 51 to determine whether the user can log in, and authenticates the login permission information. As a result, the user terminal 3 is notified. In addition, while returning an authentication result to the user terminal 3, you may transmit the web page data of the top page of a recipe site. Thereby, user authentication is performed and the top page of the recipe site is displayed on the user terminal 3.
Note that a series of flows shown in FIG. 6 shows a case where it is determined that login is possible in the authentication processing in step S202. If it is determined in step S202 that login is not possible, the user terminal 3 executes the process of step S102 again, and the recipe management server 1 executes the process of step S202 accordingly.

Subsequently, in step S <b> 103, the user terminal 3 executes a search condition transmission process for transmitting a recipe search condition for searching for a recipe input by the user to the recipe management server 1.
In this process, for example, a part of the recipe name designated by the user and the ingredients used are transmitted to the recipe management server 1 as information for extracting the search result.

Receiving the recipe search condition, the recipe management server 1 executes a search process for searching for a recipe based on the search condition and the information stored in the search DB 52 and extracting the result in step S204.
Furthermore, the recipe management server 1 performs the process which calculates a presentation priority with respect to each recipe extracted as a search result in step S205. The presentation priority is information for determining the presentation order of each recipe according to the user, and a recipe with a high presentation priority is presented to the user preferentially. “Preferentially presenting” means, for example, presenting each recipe on the user terminal 3 toward the top of the screen. Even if the recipe is the same, the presentation priority varies depending on the user, so that a recipe suited to the user can be presented.
In addition, in the presentation priority calculation process in the present embodiment, user preference information (preferred ingredients and non-preferred ingredients), and normal ingredients in the category to which the recipe belongs (“potato”, “carrot” in the “curry and rice” category, Priorities are calculated according to “onion” and other non-normal ingredients. Some examples of the presentation priority calculation processing will be described later.
Note that the calculated presentation priority for each recipe is stored in the DB in advance, and in step S205, the presentation priority for each recipe is acquired with reference to the DB, thereby replacing the presentation priority calculation process. Also good.

  Subsequently, in step S206, the recipe management server 1 executes a presentation process for displaying the search result extracted in step S204 on the user terminal 3 based on the presentation priority. In this process, the search result including the presentation priority information is transmitted to the user terminal 3.

When the presentation process is executed, the search result received from the recipe management server 1 is presented at the user terminal 3. When the user performs an operation of selecting one recipe from a plurality of recipes displayed as search results, the user terminal 3 executes a recipe selection process in step S104.
In the recipe selection process, the recipe management server 1 is notified of which recipe the recipe selected by the user is as selected recipe information. This process is a process for requesting the web page data of the detail page of the selected recipe.

In step S207, the recipe management server 1 that has received the selected recipe information executes detailed information transmission processing for transmitting data of the web page on which the detailed information of the selected recipe is described.
By this process, detailed information regarding the recipe selected by the user is presented on the user terminal 3. The detailed information is, for example, food information used for the recipe, cooking procedure, cooking utensil information, and the like.

[4-2. Processing example of recipe management server]
An example of processing executed by the recipe management server 1 to realize the above-described processing flow will be described with reference to FIG.
The recipe management server 1 performs various processes continuously by sequentially executing steps S301, S311, S321, and S331. Specifically, a process for determining whether or not login information has been received is executed in step S301, a process for determining whether or not a search condition has been received is executed in step S311, and a creation report is posted in step S321. Or a process for determining whether or not a recipe post has been received, and a process for determining whether or not a request for web page data has been received in step S331.

The login information is transmitted from the user terminal 3 to the recipe management server 1 when the user performs a login operation using the user terminal 3.
If it is determined in step S301 that the login information has been received, the recipe management server 1 executes an authentication process in step S302, and executes a process of notifying the user terminal 3 of the authentication result in step S303.
In the authentication process, the login information sent from the user terminal 3 and the user information (for example, user ID and login password) stored in the user DB 51 are collated to determine whether or not login is possible.

After the authentication result notification processing in step S303 or after determining that the login information has not been received in step S301, the recipe management server 1 executes processing for determining whether or not the search condition has been received in step S311. .
The search condition is a search keyword or an exclusion keyword specified when the user searches for a desired recipe using the user terminal 3, and is transmitted from the user terminal 3 to the recipe management server 1.

  If it is determined in step S311 that the search condition has been received, the recipe management server 1 executes a search process in step S312, executes a presentation priority calculation process in step S313, and executes a presentation process in step S314. These processes are the same as the processes in steps S204, S205, and S206 in FIG.

After the presentation process in step S314 or after determining that the search condition has not been received in step S311, the recipe management server 1 determines whether a creation report posting or a recipe posting has been received in step S321. Execute the process.
When the creation report posting or the recipe posting is received, the recipe management server 1 executes a storage process in the subsequent step S322. In the storage process, a process of storing each received post in the recipe DB 50 is executed.

After the storage process of step S322 or after determining that each posting has not been received in step S321, the recipe management server 1 executes a process of determining whether or not web page data has been received in step S331.
If it is determined that the web page data request has been received, the recipe management server 1 executes a process of acquiring the requested web page data from the DB in step S332. Specifically, web page data of a user page, web page data of a recipe detail page, web page data of a special feature page, and the like are acquired.
Then, the recipe management server 1 performs the process which transmits the said web page data to the user terminal 3 in step S333. As a result, the web page desired by the user is displayed on the user terminal 3.

After the web page data transmission process of step S333 or after determining that the web page data request is not received in step S331, the recipe management server 1 executes the process of step S301 again.

[4-3. First example of presentation priority calculation process]
A first example of the presentation priority calculation process will be described with reference to FIG.
In the first example of the presentation priority calculation process, the presentation priority is calculated based on the user's favorite ingredients (favorite ingredients) and the non-normal ingredients of the category to which the recipe belongs.
In addition, the favorite food determination process for determining the user's favorite food and the classification process for classifying the normal food and the non-normal food for each category will be described later.
That is, here, the user's favorite food is stored in the user DB 51 as the favorite food, and the normal food and the non-normal food for each category are stored in the recipe DB 50.

First, the recipe management server 1 performs the process which acquires favorite ingredient information from user DB51 in step S401.
For example, “anzu” which is a user's favorite ingredient is stored in the user DB 51 as a favorite ingredient, and “anzu” is acquired as the favorite ingredient information in the process of step S401.

Subsequently, in step S402, the recipe management server 1 acquires the non-normal ingredient information of the category to which the recipe belongs. In this process, for each recipe extracted as a search result, the non-normal ingredient information of the category to which each recipe belongs is acquired from the recipe DB 50.
Specifically, the user performs a recipe search using the search keyword “Western food”, and each recipe extracted as a search result by the search process (for example, step S412 in FIG. 7) is “curry rice”, “hamburg”, or the like. If you belong to each category, you will get “apricot”, “burdock”, “celery”, etc. as non-normal ingredients information of “curry and rice” category, “Chinese cabbage”, Get “Avocado”, “Squid”, etc.
That is, for each recipe, information on the non-normal ingredients in each category is acquired.
Note that what kind of food is determined as the non-normal food of the category will be described later.

Next, in step S403, the presentation priority is calculated. In the calculation of the presentation priority, for each recipe extracted as a search result, depending on the average value of evaluation values (values given to each recipe by each user), the posting date and time, the number of created reports, etc. The presentation priority is calculated. In particular, the calculation is performed so that the presentation priority of the recipe that uses the user's favorite food “anzu” as the non-normal food is high.
That is, the presentation priority of “anzu curry” using the non-normal food “anzu” tends to be high. However, “Chinese cabbage hamburger” for which “Chinese cabbage” is set as an unusual food has a high priority for presentation because “Chinese cabbage” is an unusual food because “Chinese cabbage” is not a user's favorite ingredient. Never become.

A specific calculation example of the presentation priority will be shown. First, the presentation priority is calculated in consideration of the degree of coincidence with the search keyword, the degree of popularity of the recipe, etc. (however, whether or not the favorite ingredient is set as an unusual ingredient is not yet considered). At this time, whether the user's favorite ingredients are included in the used ingredients may be taken into account.
Subsequently, it is determined whether or not the user's favorite ingredients for the search are set as the non-normal ingredients of the respective recipes. If applicable, the already calculated presentation priority is multiplied by 1.5.
Thereby, the presentation priority of the recipe in which the user's favorite ingredients are set as non-normal ingredients is relatively high.
In addition, the presentation priority of the recipe estimated to be used by the user is increased by 1.3 times instead of 1.5 times to increase the presentation priority of the recipe that has not been used by the user yet. Also good.

[4-4. Second example of presentation priority calculation processing]
A second example of the presentation priority calculation process will be described with reference to FIG.
In the second example of the presentation priority calculation process, the presentation priority is calculated using information on ingredients (non-favorable ingredients) that the user dislikes in addition to the favorite ingredients and non-normal ingredients.
In addition, the non-preference ingredient determination process which determines a user's non-preference ingredient is mentioned later.
That is, here, the user's disliked food is stored in the user DB 51 as a non-preferred food.

First, the recipe management server 1 performs the process which acquires favorite ingredient information from user DB51 in step S401.
Subsequently, in step S404, the recipe management server 1 executes processing for acquiring non-preferred ingredient information from the user DB 51.
Through the processing in steps S401 and S404, for example, the recipe management server 1 acquires information about the favorite ingredient “apricot” and the non-preferred ingredient “green pepper” as the user preference information.
Subsequently, in step S402, the recipe management server 1 acquires the non-normal food information of the category to which the recipe belongs. Since this process is the same as the process of FIG.

Next, the recipe management server 1 calculates the presentation priority in step S403.
In the calculation of the presentation priority, as in the first example above, the average value of evaluation values (values given to each recipe by each user) and the posting date and time for each recipe extracted as a search result In addition to the number of created reports, etc., the presentation priority is calculated according to the user's favorite ingredient information “anzu” and the non-normal ingredient information for each category. Also, in this example, the calculation is performed so that the priority of presenting recipes that use the user's non-preferred ingredient “green pepper” is low.
In other words, “anzu curry” (recipe including “anzu” in the used ingredients) and “anzu pepper curry” (anzu and “green pepper” in the used ingredients) that use the non-normal ingredients “anzu” in the “curry and rice” category. When the presentation priorities of two recipes (including recipes) are compared, “anzu curry” tends to have a relatively higher presentation priority than “anzu pepper curry”. In addition, as in the first example, the presentation priority of “Chinese cabbage hamburger” using the non-normal food ingredient “Chinese cabbage” is not likely to increase.

A specific calculation example of the presentation priority will be shown. First, the presentation priority is calculated in consideration of the degree of coincidence with the search keyword, the degree of popularity of the recipe, etc. (however, whether or not the favorite ingredient is set as an unusual ingredient is not yet considered). At this time, whether the user's favorite ingredients are included in the used ingredients may be taken into account.
Subsequently, it is determined whether or not the user's favorite ingredients for the search are set as the non-normal ingredients of the respective recipes. If applicable, the already calculated presentation priority is multiplied by 1.5.
Finally, it is determined whether or not the non-preferred ingredients of the user who performed the search are set as the ingredients used for each recipe. If applicable, the presentation priority is multiplied by 0.8.
Thereby, the presentation priority of the recipe in which the user's favorite ingredients are set as non-normal ingredients is relatively high, and the presentation priority of the recipe using the user's non-favorable ingredients is relatively low.
In addition, the presentation priority of the recipe estimated to be used by the user is increased by 1.3 times instead of 1.5 times to increase the presentation priority of the recipe that has not been used by the user yet. Also good.

[4-5. Batch processing]
In order for the recipe management server 1 to execute each process described above, there are several processes that the recipe management server 1 desirably performs in advance.
Here, an example in which such processing is periodically performed by batch processing will be described with reference to FIG.

  First, the recipe management server 1 executes a classification process in step S501. The classification process is a process in which a frequently used food for each category is set as a normal food, and a food that is not frequently used is set as a non-normal food. A specific processing procedure example will be described later.

  Subsequently, in step S502, the recipe management server 1 executes a favorite food determination process. As described above, the favorite food is a favorite food set for each user. A specific processing procedure example will be described later.

  And the recipe management server 1 performs a non-taste foodstuff determination process in step S503. Non-preference foods are disliked foods set for each user as described above. A specific processing procedure example will be described later.

Finally, in step S504, the recipe management server 1 executes usage estimation processing. The usage estimation process is a process for estimating a recipe that the user actually cooked. A specific processing procedure example will be described later.

[4-6. Classification process]
An example of the processing procedure of the classification process will be described with reference to FIG.
In the classification process, the recipe management server 1 first executes a process of determining whether or not there is an unprocessed category in step S601. Since the classification process is a process of setting normal ingredients and non-normal ingredients for each category, if the recipe belonging to the category does not change, the process result also does not change. That is, when the number of recipes belonging to a category increases after the previous classification process is performed (or when the number of recipes increases by a certain number or more), the category may be unprocessed.

If there is no unprocessed category, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if there is an unprocessed category, the recipe management server 1 executes a process of acquiring recipe information belonging to the category in step S602.
In this process, all recipe information (especially used ingredient information) belonging to the category is acquired.

Subsequently, in step S603, the recipe management server 1 executes a counting process. The tabulation process is a process of tabulating used ingredient information associated with the recipe information acquired in the previous step S602.
By this process, for example, the number of recipes using “potatoes” among the recipes belonging to the category, the ratio of the number of recipes using “potatoes” to the number of recipes belonging to the category, and the like are calculated.

Next, the recipe management server 1 performs a normal food determination process in step S604.
In the normal food determination process, it is determined whether or not the food is a normal food by comparing the number of recipes (or the ratio of the number of recipes) using the food with a threshold value. Specifically, when the threshold is 40%, in the recipe belonging to the “curry and rice” category, “potato” set as 90% of the ingredients used in the recipe and 80% of the ingredients used as the recipe are set. “Ginseng” and the like are set as normal ingredients in the “curry and rice” category.

Subsequently, in step S605, the recipe management server 1 executes a non-normal food ingredient determination process.
In the non-ordinary food determination process, the number of recipes using a certain food (or the ratio of the number of recipes) is compared with a threshold value to determine whether or not the food is an non-normal food. Specifically, when the threshold is set to 5%, in the recipes belonging to the “curry and rice” category, “anzu” set for the ingredients used in the recipe of 3% and “the ingredients used for the ingredients of 1%” are set. “Tangerine” is set as an unusual food in the “curry and rice” category.
After executing the process of step S605, the recipe management server 1 executes the process of step S601 again.

In this example, the threshold value for determining the normal food material and the threshold value for determining the non-normal food material are different numerical values, but both threshold values may be the same numerical value. In this case, all ingredients are classified as normal ingredients or non-ordinary ingredients.

[4-7. First example of preference ingredient determination process]
A first example of the preference food determination process will be described with reference to FIG.
In the first example of the favorite food determination process, the recipe management server 1 first executes a process of determining whether or not there is an unprocessed user in step S701.
In this example, it is determined based on the score information calculated for each ingredient whether or not it is a favorite ingredient. Ingredients whose score has not changed, the determination result does not change. Therefore, only users who have a possibility of fluctuation with respect to the score at the previous determination process may be unprocessed users.

If it is determined in step S701 that there is no unprocessed user, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if it is determined that there is an unprocessed user, the recipe management server 1 executes a process of calculating a score for each ingredient in the subsequent step S702.
The score for each ingredient is a numerical value representing the degree of likes and dislikes of the user for the ingredient. For example, the score becomes high (easily determined as a favorite food) by browsing the recipe set as the used food, using the recipe, or creating a creation report. In addition, when the search keyword is set as an excluded keyword, or when a recipe that does not use that ingredient is viewed (or used) even though it is a normal ingredient in a certain category, the score is low (determined as a favorite ingredient) Difficult).

Then, the recipe management server 1 performs the process which compares the score of each foodstuff with the threshold value for determination in step S703. A food with a score higher than the threshold is determined as the user's favorite food. This information is stored in the user DB 51.
After executing the process of step S703, the recipe management server 1 executes the process of step S701 again.

[4-8. Second example of preference ingredient determination process]
A second example of the preference food determination process will be described with reference to FIG.
In the second example of the preference food determination process, the recipe management server 1 first executes a process of determining whether or not there is an unprocessed user in step S701.
In this example, a favorite ingredient is determined from the user's usage recipe information. Therefore, if the used recipe information has not been updated since the previous determination process, there is a high possibility that the determination result will not change. Therefore, only users whose usage recipe information has been updated since the previous determination process may be unprocessed users. .
In addition, the process which estimates the utilization of the recipe by a user is mentioned later.

If it is determined in step S701 that there is no unprocessed user, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if it is determined that there is an unprocessed user, the recipe management server 1 executes a process of acquiring the used recipe information of the target user in step S704. For the used recipe, information on all recipes used by the target user may be acquired, information on the most recent predetermined number of recipes may be acquired, or information on recipes used in the most recent predetermined period may be acquired. Information may be acquired.

Next, in step S705, the recipe management server 1 executes processing for acquiring non-normal food information for each acquired usage recipe. Thereby, the non-normal foodstuff set to the recipe utilized by the user is extracted.
Then, the recipe management server 1 performs the process which extracts applicable foodstuff in step S706. In this process, in the recipe used by the user, the ingredients set as non-normal ingredients are extracted as favorite ingredients.
That is, if the user uses a recipe that uses ingredients that are not often used in the category to which the recipe belongs, it is presumed that there is a high possibility that the ingredients (unusual ingredients) are favorite ingredients.

After the process of step S706, the recipe management server 1 executes the process of step S701 again.

[4-9. Third example of preference food determination process]
A third example of the preference food determination process will be described with reference to FIG.
In the third example of the favorite food determination process, the recipe management server 1 first executes a process of determining whether or not there is an unprocessed user in step S701.
In this example, the user's favorite ingredients are determined using search conditions specified by the user when searching for a recipe. Therefore, if the user does not perform a new recipe search after the previous determination process, it is highly likely that the determination result of the favorite ingredients will not change, so only the user who uses the recipe search function from the previous determination process has not yet been processed. It may be a user.

If it is determined in step S701 that there is no unprocessed user, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if it is determined that there is an unprocessed user, the recipe management server 1 executes a process of acquiring the search condition history of the target user in step S707. In this process, in particular, information on the ingredients input as search keywords is acquired.
Next, the recipe management server 1 performs the process which extracts applicable foodstuff in step S708. This process is a process of extracting a food that satisfies a condition from among the foods input by the user as a search keyword. Specifically, for example, a food that has been input a predetermined number of times within a predetermined period may be extracted as a favorite food, or a food that has been input a predetermined number of times regardless of the period may be extracted as a favorite food.

After the process of step S708, the recipe management server 1 executes the process of step S701 again.
The search history may be stored in the user DB 51 or may be stored in a dedicated DB.

[4-10. First Example of Non-preferred Ingredient Determination Process]
A first example of the non-preferred ingredient determination process will be described with reference to FIG.
In the first example of the non-preferred food determination process, the recipe management server 1 first executes a process of determining whether or not there is an unprocessed user in step S801.
In this example, it is determined based on the score information calculated for each ingredient whether or not it is a favorite ingredient. Ingredients whose score has not changed, the determination result does not change. Therefore, only users who have a possibility of fluctuation with respect to the score at the previous determination process may be unprocessed users.

If it is determined in step S801 that there is no unprocessed user, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if it is determined that there is an unprocessed user, the recipe management server 1 executes a process of calculating a score for each food in step S802. This process is the same as the process in step S702 of FIG.
Then, the recipe management server 1 performs the process which compares the score of each foodstuff with the threshold value for determining with a non-preference foodstuff in step S803.
A food with a score lower than the threshold is determined as a non-preference food of the user. This information is stored in the user DB 51.
After executing the process of step S803, the recipe management server 1 executes the process of step S801 again.

In the first example of the preference food determination process described with reference to FIG. 12, the preference food may be determined and the non-preference food may be determined. Thereby, simplification of a process can be achieved.

[4-11. Second example of non-preferred food determination process]
A second example of the non-preferred ingredient determination process will be described with reference to FIG.
In the second example of the non-preference ingredient determination process, the recipe management server 1 first executes a process of determining whether or not there is an unprocessed user in step S801.
In this example, the user's non-preferred ingredients are determined using the search conditions specified by the user when searching for a recipe. Specifically, information on the ingredients specified by the user as exclusion keywords is used. Therefore, if the user has not searched for a new recipe since the previous determination process, it is highly likely that the determination result of the non-preferred ingredients will not change, so only the user who uses the recipe search function from the previous determination process has not yet been processed. It is good also as a user.

If it is determined in step S801 that there is no unprocessed user, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if it is determined that there is an unprocessed user, the recipe management server 1 executes a process of acquiring the search condition history of the target user in step S804. In this process, in particular, information on the ingredients input as exclusion keywords is acquired.

  Next, the recipe management server 1 performs the process which extracts applicable foodstuff in step S805. This process is a process of extracting a food that satisfies a condition among the foods input by the user as an excluded keyword. Specifically, for example, a food that has been input as an excluded keyword a predetermined number of times within a predetermined period may be extracted as a non-preferred food, or a food that has been input as a negative keyword a predetermined number of times regardless of the period May be extracted as Moreover, you may extract the foodstuff input as an exclusion keyword even as a non-preference foodstuff.

After the process of step S805, the recipe management server 1 executes the process of step S801 again.
The search history may be stored in the user DB 51 or may be stored in another dedicated DB.

[4-12. Third Example of Non-preference Food Ingredient Determination Process]
A third example of the non-preferred ingredient determination process will be described with reference to FIG.
In the third example of the non-preference food ingredient determination process, the recipe management server 1 first executes a process of determining whether or not there is an unprocessed user in step S801.
In this example, the user's non-preferred ingredients are determined from the user's usage recipe and the normal ingredients in the category to which the recipe belongs. Therefore, when there is no change in the user's used recipe, that is, when the user is not newly using the recipe from the previous determination process, the user may be processed.

If it is determined in step S801 that there is no unprocessed user, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if it is determined that there is an unprocessed user, the recipe management server 1 executes a process of acquiring used recipe information in step S806. This process is the same as step S704 in FIG. In addition, the process which estimates the utilization of the recipe by a user is mentioned later.

Subsequently, in step S807, the recipe management server 1 executes a process of acquiring normal food information for each acquired usage recipe. Thereby, the normal food set in the recipe used by the user is extracted.
Next, the recipe management server 1 performs the process which extracts applicable foodstuff in step S808. In this process, when there are many recipes in which the normal ingredients in the category are not used ingredients in the user's usage recipe, the normal ingredients are determined as non-preferred ingredients.
Specifically, for example, “potatoes” (for example, 90% of recipes belonging to the “curry and rice” category are set as used ingredients) are set as the normal ingredients in the “curry and rice” category. On the other hand, in 10 recipes of the “curry and rice” category used by the user, when there is no recipe in which “potato” is set as an ingredient to be used, it is estimated that the user is not good at “potato”.

After the process of step S807, the recipe management server 1 executes the process of step S801 again.
In addition, with respect to the ratio of recipes in which normal ingredients are set as used ingredients (the ratio of recipes using “potato” in the “curry and rice” category is 90%), the ingredients are used in the recipes used by the user. The recipe may be determined as a non-preferred ingredient when the ratio of the recipe set as is lower than a predetermined ratio (for example, 90 × 0.5 = 45% when 50% is set).

[4-13. Usage estimation process]
Here, the process of estimating the use of the recipe by the user will be described with reference to FIG.
First, in step S901, the recipe management server 1 executes a process for determining whether there is an unprocessed user.
If it is determined that there is no unprocessed user, the recipe management server 1 ends the series of processes shown in FIG.
On the other hand, if it is determined that there is an unprocessed user, the recipe management server 1 executes a process of acquiring information on a creation report posted by the user in step S902. There is a high possibility that the recipe for which the creation report has been posted is a recipe actually used (cooked) by the user.

Subsequently, the recipe management server 1 acquires recipe browsing information in step S903. The recipe viewed by the user may be a recipe actually used by the user.
In addition, if it is not only browsing but browsing time according to the cooking time set for every recipe, possibility that it is a used recipe will increase further.

  Next, the recipe management server 1 performs usage determination for each recipe in step S904. This determination is performed according to the creation report information acquired in step S902 and the recipe browsing information acquired in step S903.

  After executing the process of step S904, the recipe management server 1 executes the process of step S901 again.

In addition, in the recipe details page where the ingredients used and the cooking method of the recipe are described, when the portion where the ingredients used are listed and the portion where the cooking method is described are alternately viewed on the page, the recipe May be determined to have been used by the user. Moreover, you may determine with the said user having utilized the said recipe, when the part in which the cooking method is described is browsed for a long time.

[4-14. Example of batch processing execution timing]
An example of the timing for executing the previous batch processing described with reference to FIG. 10 will be described.
For example, it is conceivable to execute batch processing for each season. In this case, the favorite food determination process in step S502 of FIG. 10 and the non-preferred food determination process in step S503 are executed for each season. That is, a favorite food and a non-preference food are updated for every season. Thereby, a seasonal food becomes easy to be set as a favorite food or a non-taste food.

<5. Summary>

The above-described recipe management server 1 includes a recipe management unit 1a that classifies the used ingredients set in the recipe into normal ingredients that are frequently used and non-normal ingredients that are less frequently used in the category to which the recipe belongs, and a user preference A favorite ingredient determining unit 1b that determines an ingredient to be used as a favorite ingredient, a search unit 1c that searches for a recipe based on a search condition input by a user, and a recipe that includes non-normal ingredients in the searched recipe And a presentation unit 1d that presents the presentation priority to the user.
The provision of recipes using favorite foods by users has already been performed. However, the recipes so presented are often extracted based on popularity and evaluation values, and are likely to be ordinary recipes.
On the other hand, according to the present invention, a recipe that uses a user's favorite food as an unusual food is likely to be presented with high priority. That is, it becomes easy for a user to present an unusual recipe using favorite ingredients.
Thereby, while giving a change to a user's eating habits, a recipe with a high possibility of being satisfied can be presented. In particular, it is possible to improve the utility value of the recipe site by presenting a recipe that is not presented at other recipe sites.
Further, by presenting valuable information (recipe) in a limited presentation area (for example, a monitor) in the user terminal used by the user, the resources of the user terminal can be effectively utilized.

Moreover, as demonstrated in each example (1st example, 2nd example, 3rd example) of a non-taste foodstuff determination process, the taste foodstuff determination part 1b determines the foodstuff which a user does not like as a non-taste foodstuff.
Thereby, not only the ingredients that the user likes, but also the ingredients that are not preferred are managed.
Therefore, a more suitable recipe can be presented to the user.

Further, as described in the first example of the favorite ingredient determination process, the favorite ingredient determination unit 1b assigns a score to each user and the ingredient, and the ingredient whose score is equal to or higher than the first threshold is the favorite ingredient of the user. And the ingredients that are less than the second threshold are determined as non-preferred ingredients for the user.
The digitized preference information is managed for each combination of user and food.
For example, when updating the food score each time according to the user's behavior, etc., since the preference information is accumulated according to the user's behavior (for example, searching for a certain food) multiple times, It is possible to determine a favorite ingredient and a non-preference ingredient for each user after ensuring the reliability of the user.

Furthermore, as described in the second example of the favorite food determination process, the favorite food determination unit 1b determines the non-normal food of the usage estimation recipe estimated to be used by the user as the user's favorite food and uses it. Among the normal ingredients in the category to which the estimated recipe belongs, the ingredients that are not used in the usage estimation recipe are determined as candidates for non-preferred ingredients.
Thereby, since a user's favorite foodstuff is determined based on the recipe estimated to be actually used by the user, highly accurate information can be collected without causing the user to directly input the favorite foodstuff.

In addition, as described in the third example of the favorite food determination process, the favorite food determination unit 1b determines the food input by the user as the search condition as the user's favorite food.
Thereby, since the information of the favorite food is collected using the information when the user performs the search operation, the information can be efficiently collected without imposing an extra operation burden on the user.
In addition, it is highly probable that the ingredients used for the search are ingredients that the user wants to use even if they are not favorite ingredients, so propose a recipe that uses the searched ingredients determined as favorite ingredients. Is a recipe presentation according to the user's purpose.

And as demonstrated in the example of the execution timing of batch processing, the favorite food determination part 1b performs determination for every time and season.
Since the preference information is periodically updated, it is possible to suppress the presentation of recipes using ingredients that are not out of season. Moreover, the recipe according to the case where a favorite foodstuff changes can be shown.

In addition, as described in the second example of the presentation priority calculation process, the presentation unit 1d lowers the presentation priority of a recipe that uses a non-preferred ingredient.
Thereby, the recipe search which considered both a user's favorite food and a non-taste food is made.
Therefore, a more suitable recipe can be presented to the user.

Furthermore, as described in the second example of the non-preferred food determination process, the favorite food determination unit 1b determines the excluded food set as a search condition by the user as a non-preferred food.
As a result, the information input when the user performs a search operation is used to collect information on non-preferred ingredients, so that it is possible to efficiently collect information without imposing an extra operation burden on the user.

<6. Program and Storage Medium>

As mentioned above, although the recipe management server 1 as embodiment of the information processing apparatus of this invention was demonstrated, the program of embodiment is a program which makes an information processing apparatus (CPU etc.) perform each process in the recipe management server 1 It is.

The program according to the embodiment causes the information processing apparatus to execute a classification procedure for classifying the used food set in the recipe into a normal food having a high use frequency and a non-normal food having a low use frequency in the category to which the recipe belongs.
Further, the information processing apparatus is caused to execute a favorite food determination procedure for determining a food favorite by the user as a favorite food.
Further, the information processing apparatus is caused to execute a search procedure for searching for a recipe based on a search condition input by the user.
Furthermore, the information processing apparatus is caused to execute a presentation procedure for increasing the presentation priority of the recipe in which the non-normal ingredient includes the favorite ingredient among the retrieved recipes and presenting it to the user.
That is, this program is a program that causes the recipe management server 1 to execute the processes in steps S201 to S207 in FIG. 6 and the processes in FIGS.

With such a program, the information processing apparatus as the recipe management server 1 described above can be realized.
Such a program can be recorded in advance in an HDD as a recording medium built in a device such as a computer device, a ROM in a microcomputer having a CPU, or the like. Alternatively, it can be stored (recorded) temporarily or permanently in a removable recording medium such as a semiconductor memory, a memory card, an optical disk, a magneto-optical disk, or a magnetic disk. Moreover, such a removable recording medium can be provided as so-called package software.
Such a program can be downloaded from a removable recording medium to a personal computer or the like, or downloaded from a download site via a network such as a LAN or the Internet.

  DESCRIPTION OF SYMBOLS 1 Recipe management server, 1a Recipe management part, 1b Preference ingredient determination part, 1c Search part, 1d Presentation part, 2 Communication network, 3 User terminal, 50 Recipe DB, 51 User DB, 52 Search DB

Claims (11)

Recipe management unit that classifies the used ingredients set in the recipe into normal ingredients that are used frequently and non-usual ingredients that are used less frequently in the category to which the recipe belongs,
A preference food determination unit that determines a user preference as a preference food;
A search unit for searching a recipe based on a search condition input by a user;
An information processing apparatus comprising: a presentation unit that raises a presentation priority of a recipe in which the non-normal ingredient includes the favorite ingredient in the retrieved recipe and presents the recipe to the user. The information processing apparatus according to claim 1, wherein the preference food determination unit determines a food not preferred by the user as a non-preference food. The preference food determination unit assigns a score to each user and food, determines a food having a score equal to or higher than the first threshold as the user's favorite food, and selects the food that is less than a second threshold. The information processing apparatus according to claim 2, wherein the information processing apparatus is determined as the user's non-preferred food. The preference food determination unit determines a non-usual food of a usage estimation recipe estimated to be used by a user as the user's preference food, and selects the usage estimation recipe among the normal ingredients in the category to which the usage estimation recipe belongs. The information processing apparatus according to claim 2, wherein an unused ingredient is determined as a candidate for the non-preferred ingredient. The information processing apparatus according to claim 1, wherein the preference food determination unit determines a food input by a user as a search condition as the user's preference food. The information processing apparatus according to claim 1, wherein the preference food determination unit performs the determination for each period or season. The information processing apparatus according to claim 2, wherein the presentation unit lowers the presentation priority of a recipe that uses the non-preference food. The information processing apparatus according to claim 2, wherein the preference food determination unit determines an excluded food set as a search condition by the user as a non-preference food. A classification step for classifying the use ingredients set in the recipe into normal ingredients with high use frequency and non-normal use ingredients with low use frequency in the category to which the recipe belongs;
A preference ingredient determination step for judging a favorite ingredient as a favorite ingredient;
A search step for searching for recipes based on search criteria entered by the user;
Information processing method and a presentation step of presenting to the user to increase the presentation priority of the recipe that includes the preference ingredients in the non-normal food among the recipe the search information processing device executes. A classification procedure for classifying the use ingredients set in the recipe into normal ingredients with high use frequency and non-normal use ingredients with low use frequency in the category to which the recipe belongs;
A preference ingredient determination procedure for judging a favorite ingredient as a favorite ingredient;
A search procedure for searching for recipes based on search criteria entered by the user;
A program that causes an information processing apparatus to execute a presentation procedure for increasing the presentation priority of a recipe in which the non-normal ingredient includes the favorite ingredient in the retrieved recipe and presenting the recipe to the user. A classification procedure for classifying the use ingredients set in the recipe into normal ingredients with high use frequency and non-normal use ingredients with low use frequency in the category to which the recipe belongs;
A preference ingredient determination procedure for judging a favorite ingredient as a favorite ingredient;
A search procedure for searching for recipes based on search criteria entered by the user;
A storage medium storing a program for causing an information processing device to execute a presentation procedure for increasing a presentation priority of a recipe in which the non-normal ingredient includes the favorite ingredient among the retrieved recipes.

Images