Recipe management server, method, and program for aggregating multiple recipe sites

Abstract

To provide a system for collectively managing recipe information posted on multiple recipe sites. [Solution] The management server of the present disclosure includes a receiving means for receiving input operations, a registration means for registering recipe site information indicating the URL of a recipe site published on a website and original recipe information indicating the recipe information entered by input operations together with additional information in a recipe storage means and adding it to the user's My List as registered recipe information, and an output means for outputting the recipe site information and the additional information of the original recipe information as multiple recipe cards.

Description

[Technical Field]

[0001] The present invention relates to a recipe management server, method, and program that aggregates multiple recipe sites. [Background technology]

[0002] Japanese Patent Application Laid-Open No. 2019-144714 (Patent Document 1) is a background art in this technical field. This publication discloses a recipe management server that can detect inappropriate descriptions included in recipe information as a recipe. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-144714 Summary of the Invention [Problem to be solved by the invention]

[0004] The aforementioned Patent Document 1 discloses a system that supports posting of recipes to recipe sites. However, the conventional technology does not consider centralized management of recipe information posted to multiple recipe sites. Therefore, the present invention provides a mechanism for collectively managing recipe information posted on multiple recipe sites. [Means for solving the problem]

[0005] In order to solve the above problems, for example, the configurations described in the claims are adopted. [Effects of the Invention]

[0006] According to the present invention, it is possible to provide a system for collectively managing recipe information posted on a plurality of recipe sites. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is an example of an overall configuration diagram of a recipe management system. [Figure 2] FIG. 2 shows an example of a hardware configuration of the recipe management server shown in FIG. [Figure 3] FIG. 3 shows an example of a hardware configuration of the user terminal shown in FIG. [Figure 4] FIG. 4 is an example of the user information shown in FIGS. [Figure 5] FIG. 5 is an example of the recipe memo information shown in FIG. [Figure 6] FIG. 6 is an example of the original recipe information shown in FIG. [Figure 7] FIG. 7 is an example of the public recipe search information shown in FIG. [Figure 8] FIG. 8 is an example of the My List information shown in FIGS. [Figure 9] FIG. 9 is an example of the My List search information shown in FIGS. [Figure 10] FIG. 10 is an example of a flow of a process for registering recipe information. [Figure 11] FIG. 11 shows an example of a flow of a registration process for public recipe search information. [Figure 12] FIG. 12 shows an example of the flow of the registration process for My List search information. [Figure 13] FIG. 13 is an example of a flow of a recipe information search process. [Figure 14] FIG. 14 shows an example of a flow of a recipe card display process. [Figure 15] FIG. 15 is an example of a flow of a display process for a recipe details page. [Figure 16] FIG. 16 is an example of a flow of a recipe information update process. [Figure 17] FIG. 17 is an example of a home screen in the recipe management system. [Figure 18] FIG. 18 is an example of a My List screen in the recipe management system. [Figure 19] FIG. 19 shows an example of the My List search dialog screen. [Figure 20] FIG. 20 is an example of a screen shot of the recipe memo details page. [Figure 21] Figure 21 is an example of a screen shot of the details page of an original recipe. [Figure 22] FIG. 22 shows an example of a screen displaying everyone's list. [Figure 23] Figure 23 is an example of a search screen on an external recipe site. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, the embodiments will be described with reference to the drawings. <Outline of the Example> The recipe management system 1 (hereinafter simply referred to as system 1) according to the present disclosure is a system having a function of managing recipe information posted by users and making it available to other users. Furthermore, system 1 has a function of centrally managing recipe information posted on various other recipe sites, which are provided as web services available in an Internet environment, together with recipe information posted by the user.

[0009] Nowadays, various recipe providing services are widely provided through various media, and users who are interested in daily eating habits and cooking may use multiple recipe providing services. In such a situation, it would be convenient for users to consolidate and manage recipe information that is of interest to them from among the recipe information posted on various recipe sites.

[0010] For this reason, System 1 centrally manages recipe information published in various media by handling recipe information (original recipe information) in which the user directly inputs the cooking method, as well as recipe information (recipe notes) that quotes recipe information published on other recipe sites.

[0011] Various other recipe sites managed by System 1 include, for example: Recipe sites that are provided one-way for user viewing A recipe site for a recipe posting system provided for users to post and view recipes -Video sites distributed on recipe introduction channels on video distribution platforms The various other recipe sites that are managed by system 1 are not limited to those mentioned above. In other words, other recipe sites are media that can be used in an Internet environment, and there are no restrictions on their content as long as they provide recipe information to users.

[0012] The types of recipe information handled by the system 1 are defined as follows: "Recipe Notes": Recipe information including URL information of other recipe sites and additional information "Original recipe": Recipe information including cooking methods and additional information entered by the user "Public Recipes": Recipe notes and original recipes that the user who posted them wishes to make public "Favorite Recipes": Recipe information that users who viewed public recipes added to their favorites "Recipes I want to make": Recipe information that users who viewed public recipes have registered as ones they want to make (recipe preferences) (recipe preferences)

[0013] In other words, "recipe notes" in System 1 refer to recipe information registered in System 1 by quoting information about cooking methods posted on other recipe sites, without the user himself / herself inputting text data corresponding to the cooking method.

[0014] In contrast, an "original recipe" in System 1 refers to recipe information in which the user has input text data corresponding to the cooking method, regardless of whether the user came up with the idea for the cooking method. In other words, for example, a recipe in which the user has input text data corresponding to the cooking method, which is the content of a cooking video posted on a video distribution site, is also included in the "original recipe" in System 1.

[0015] In addition, the types of recipe information lists handled by the system 1 are defined as follows: ·Everyone's List: A list of public recipes published by all users Favorites list: A list of the user's favorite recipes My List: A list of recipe notes and original recipes registered by the user, as well as the user's "favorite recipes" · Want to make list: A list of recipes the user wants to make Based on these definitions, the overall configuration of the system 1 will be described below.

[0016] (1. Overall system configuration) FIG. 1 shows an example of the overall configuration of the system 1. The system 1 includes a recipe management server 200 (hereinafter simply referred to as the management server 200) and multiple user terminals 300, which are connected to each other via a network. The network may be wired or wireless, and each terminal can send and receive information via the network. The recipe management server 200 is a server device that manages recipe information and executes each process described below. The user terminal 300 is a terminal used by a user to view, post, edit, and the like recipe information.

[0017] The management server 200 and the user terminal 300 each include a processor that executes an operating system, applications, programs, etc., a main storage device such as RAM (Random Access Memory), an auxiliary storage device such as an IC card, hard disk drive, SSD (Solid State Drive), flash memory, etc., a communication control unit such as a network card, wireless communication module, or mobile communication module, input devices such as a touch panel, keyboard, mouse, voice input, and input based on motion detection captured by a camera unit, and an output device such as a monitor or display. Note that the output device may also be a device or terminal that transmits information to be output to an external monitor, display, printer, device, etc.

[0018] The main memory stores various programs, applications, etc. (modules), and the processor executes these programs and applications to realize the various functional elements of the overall system. These modules may be implemented in hardware, such as by integration. Each module may be an independent program or application, or may be implemented as a subprogram or function within a single integrated program or application.

[0019] In this specification, each module is described as the entity (subject) that performs the processing, but in reality, the processing is carried out by a processor that processes various programs, applications, etc. (modules). Various databases (DBs) are stored in the auxiliary storage device. A "database" is a functional element (storage unit) that stores a set of data so that it can accommodate any data manipulation (e.g., extraction, addition, deletion, overwriting, etc.) from a processor or an external computer. There are no limitations on how the database is implemented; for example, it can be a database management system, spreadsheet software, or a text file such as XML or JSON.

[0020] The management server 200 and the user terminal 300 may be, for example, a portable terminal (mobile terminal) such as a smartphone, tablet, mobile phone, or personal digital assistant (PDA), or may be a wearable terminal such as glasses, a wristwatch, or clothing. They may also be stationary or portable computers, or servers located on the cloud or a network. In terms of functionality, they may be VR (Virtual Reality) terminals, AR (Augmented Reality) terminals, or MR (Mixed Reality) terminals. Alternatively, they may be a combination of multiple of these terminals. For example, a combination of one smartphone and one wearable terminal may logically function as a single terminal. Other information processing terminals may also be used.

[0021] (2. Hardware Configuration of Management Server 200) FIG. 2 shows an example of the hardware configuration of the management server 200 shown in FIG. The management server 200 is configured, for example, by a server placed on a cloud. The main memory device 201 stores programs and applications such as an operation reception module 211, a registration module 212, a search module 213, a counting module 214, and an output module 215, and the processor 203 executes these programs and applications to realize each functional element of the management server 200.

[0022] The operation receiving module 211 receives an input operation by a user transmitted from the user terminal 300. The operation receiving module 211 is an example of a receiving unit. The registration module 212 registers and manages user information, recipe information, and the like in the auxiliary storage device 202. For example, the registration module 212 registers recipe site information, which is URL information cited in recipe notes, along with additional information in the auxiliary storage device 202. The recipe site information is URL information for recipe sites for other recipe providing systems published on a website. The additional information in a recipe note is various other recipe information that is entered along with the URL information.

[0023] The registration module 212 also registers original recipe information together with additional information in the auxiliary storage device 202. The original recipe information is recipe information including a cooking method input by the user as text data. The additional information in the original recipe is various other recipe information input together with the cooking method. In other words, the registration module 212 is an example of a registration means. The recipe information registration process will be described in detail later.

[0024] The search module 213 executes a search process for recipe information in response to a search operation from the user. The search module 213 performs the search process based on search conditions specified by the user. For example, the search module 213 searches for registered recipe information that includes, as additional information, information corresponding to any character string included in a search keyword entered by the user. In addition to a search keyword, search conditions include a user tag, a recipe tag, and a cooking time. In other words, the search module 213 is an example of a search means. Details of the search process for recipe information will be described later.

[0025] The counting module 214 counts additional information related to recipes. The additional information related to recipes refers to information related to cooking methods among the recipe information, or other information related to the recipe that is stored in association with URL information of a website that describes the cooking methods. The counting module 214 counts, for example, the number of times that recipe information published by a user has been designated as a "favorite recipe" by other users. In other words, the counting module 214 is an example of a counting means.

[0026] In response to user operations, the output module 215 outputs various types of information obtained by processing by the recipe management server 200 to the user terminal 300. For example, the output module 215 outputs multiple pieces of recipe information to the user terminal 300 as recipe cards. A recipe card refers to a recipe display field in which an outline of each piece of recipe information is displayed in card format, one for each piece of recipe information. The recipe card displays the title of the recipe and additional information. For example, the output module 215 outputs additional information about registered recipe information searched by the search module 213 as a recipe card.

[0027] In response to a display instruction from the user, the output module 215 outputs a list that combines recipe cards for recipe notes (recipe site information) and recipe cards for original recipes. The output module 215 is an example of an output means. Details of the output screen of the recipe cards by the output module 215 will be described in detail with reference to FIG. 18.

[0028] In this embodiment, a configuration in which each module of the management server 200 provides various functions of the system 1 will be described, but similar processing may be performed by each module provided in the user terminal 300, as shown in Fig. 3. Regarding the configuration common to the management server 200 and the user terminal 300, specific descriptions of the functions and processing will not be repeated.

[0029] The auxiliary storage device 202 stores user information 400, recipe memo information 500, original recipe information 600, public recipe search information 700, My List information 800, and My List search information 900. The auxiliary storage device 202 includes a database required to store these various pieces of information. The database may be implemented as a key-value store or as a relational DB. The contents of each piece of information will be described later.

[0030] (3. Hardware Configuration of User Terminal 300) FIG. 3 shows an example of the hardware configuration of the user terminal 300 shown in FIG. The user terminal 300 is configured as a terminal such as a smartphone, a tablet, a notebook PC, or a desktop PC. The main memory device 301 stores the same functional modules as the main memory device 201 of the management server 200. That is, the user terminal 300 can perform the same processing as the management server 200. The functions of these modules are the same as those described above, and therefore a description thereof will be omitted. Note that the main memory device 301 does not have to store all the same functional modules as the management server 200, and may store only some of the functional modules.

[0031] The auxiliary storage device 302 stores user information 400, My List information 800, and My List search information 900. Each piece of information is the same as part of the information stored in the auxiliary storage device 202 of the management server 200. Note that the auxiliary storage device 302 does not necessarily store the same information as part of the information stored in the auxiliary storage device 202 of the management server 200.

[0032] (4. Data types and database structure) Next, various types of information managed by the system 1 will be described. 4 to 9 show various types of information stored in the management server 200. In this embodiment, it is assumed that all or part of this information is stored in a key-value store format, which is a NoSQL format, but this is not limiting. The various types of information may also be configured to be stored in a relational database or other non-relational database such as a JSON format.

[0033] (4-1. User information 400) Fig. 4 shows an example of user information 400. Fig. 4A shows an example of a combination of key values ​​and value values ​​in user information 400. Fig. 4B shows information about user tags among subcollections set as a lower data layer than user information 400. Fig. 4C shows information about cooked data among subcollections set as a lower data layer than user information 400.

[0034] 4A, user information 400 includes various types of information related to the user. The various types of information related to the user include, for example, the following: Information about your account Information about user attributes Information about user activity history (cooking history, favorite registrations, etc.) Recipe information linked to the user

[0035] In the user information 400, a user ID 410, which is a unique value that can identify a user, is used as a key value, and multiple values ​​420 are set. The values ​​420 include a login pass 411, a user name 412, contact information 413, a user tag ID group 414, a data ID group 415 of cooked data, a recipe ID group 416 of my recipe notes, a recipe ID group 417 of my original recipes, a recipe ID group 418 of "recipes for search," and a recipe ID group 419 of "recipes I want to try." Although not shown in FIG. 4, similar data groups are linked to all user IDs.

[0036] The login pass 411, the user name 412, and the contact information 413 are all information related to the user's account. The login PASS 411 stores a password for authenticating a user account, which the user is required to input when logging in to the system 1. The user name 412 stores the user's name or a handle name used in the system 1. For example, an email address is stored as information for contacting the user in the contact information 413. Note that the contact information may be account information of various SNSs that can contact the user instead of an email address.

[0037] The user tag ID group 414 is information relating to user attributes, and stores identification information of user tags selected by the user, for example, by the user himself. A user tag is a tag that indicates a user attribute that can classify a group of users into multiple groups, such as user preferences, lifestyle, etc. User tags include, for example, the following: Tags related to gender or age, such as "male," "female," or "elderly" ·Tags related to taste preferences, such as "sweet tooth" or "spicy tooth" Tags related to lifestyle, such as "single," "housewife," and "large family" Tags related to cooking proficiency, such as "beginner" or "advanced"

[0038] As shown in Fig. 4B, for user tags, a user tag ID is used as a key value of the subcollection, and an attribute value indicating the content of the attribute of the user corresponding to the user tag ID is registered as a value. That is, although not shown in the figure, a user tag ID that serves as a unique value is assigned to each of the various user attributes mentioned above.

[0039] In the user information 400, one or more corresponding user tags are associated with each user ID. For example, when the user selects a corresponding attribute, a new record of the user tag is added to the user tag ID group 414. User tags are selected when the user starts using the system 1, and may also be added and selected by the user later.

[0040] The data ID group 415 of cooked data shown in FIG. 4A is information related to the cooking history of the user. Cooked data is information that records the cooking history of recipe information that the user actually cooked, which is declared by operating a recipe card, which will be described later. The operation of declaring the cooking history will be described in detail with reference to FIG. 18.

[0041] As shown in Figure 4C, for cooked data, the cooked data ID is used as a key value for the subcollection, and the recipe ID of the recipe cooked by the user and the time information when the cooking was performed are registered as the cooking history corresponding to the cooked data ID. In other words, the cooked data stores a cooking history that indicates when and which recipe the user cooked. Strictly speaking, the time information stored in the cooked data is the time information when the reporting operation was accepted after cooking.

[0042] Cooked data has a unique ID for each cooking history by a user. When a user cooks a recipe and reports that they have done so, a new record is linked to the user ID and added to the data ID group 415 of cooked data in the user information 400.

[0043] The recipe ID group 416 for "My Recipe Memo," the recipe ID group 417 for "My Original Recipes," the recipe ID group 418 for "Favorite Recipes," and the recipe ID group 419 for "Recipes I'd Like to Make" shown in Figure 4A are all recipe information linked to the user.

[0044] Among these, the recipe ID group 416 of "My Recipe Memo" stores the recipe IDs of the my recipes posted by the user corresponding to the user ID. Also, the recipe ID group 417 of "My Original Recipes" stores the recipe IDs of the original recipes posted by the user corresponding to the user ID.

[0045] Meanwhile, recipe IDs for public recipes posted and published by other users are stored in the "recipes to search" recipe ID group 418 and the "recipes to try" recipe ID group 419. Specifically, the "recipes to search" recipe ID group 418 stores recipe IDs for recipe information that the user has previously searched for, among public recipes published by other users. Furthermore, the "recipes to try" recipe ID group 419 stores recipe IDs for recipes that the user has registered as ones that they would like to try, among public recipes published by other users.

[0046] (4-2. Recipe memo information 500) FIG. 5 shows an example of recipe memo information 500. FIG. 5A shows an example of a combination of key values ​​and values ​​of recipe memo information. FIG. 5B is a database of cooking time information from a subcollection set as a lower data layer than the recipe memo information. FIG. 5C shows an example of recipe tag information from a subcollection set as a lower data layer than the recipe memo information.

[0047] 5A, in recipe memo information 500, a plurality of values ​​520 are set using a recipe ID 510 of the recipe memo, which is a unique value that can identify the recipe memo, as a key value. The values ​​520 include a quoted URL 521, a recipe name 522, a personal memo 523, a cooking time ID 524, a recipe tag ID group 525, a public flag 526, and a registration date and time 527. In the recipe memo, information other than the quoted URL 521 is additional information. Although not shown in FIG. 5, a similar data group is linked to every recipe ID.

[0048] Cited URL 521 stores the URL information of another recipe site that is cited as a recipe memo corresponding to the recipe ID. In other words, a recipe memo is recipe information that quotes recipe information from another recipe site. For this reason, recipe memo information 500 does not include information about cooking methods, including information about the types and amounts of ingredients and seasonings, as well as information about cooking procedures. This is because such information is posted on the other recipe site that is cited, and it is sufficient to check there.

[0049] The name of the recipe memo corresponding to the recipe ID is stored in the recipe name 522. The recipe name 522 may be automatically input from the recipe information of the recipe site of the citation. The personal memo 523 stores any memo that the user inputs at the time of registration for the recipe memo corresponding to the recipe ID.

[0050] Cooking time ID 524 stores a cooking time ID indicating the estimated cooking time for the recipe associated with the recipe memo corresponding to the recipe ID. As shown in FIG. 5B, the cooking time information stores the cooking time ID and estimated cooking time in association with each other. For example, the cooking time information specifies that when the cooking time ID is "3," the estimated cooking time is longer than 20 minutes and shorter than 30 minutes.

[0051] The recipe tag ID group 525 stores identification information of the recipe tag selected by the user for the recipe memo corresponding to the recipe ID. A recipe tag is an indicator (tag) of a recipe attribute that can classify a group of recipes into multiple groups. Recipe tags include, for example, the following: Tags related to recipe names and types, such as "curry" and "gratin" Tags related to ingredients such as "sanma" (Pacific saury) and "potatoes" Tags related to cooking methods such as "stewing" and "stir-frying" Tags related to the region where the recipe originates, such as "Italian" or "ethnic" Tags related to the seasons suitable for cooking, such as "winter" or "hot days" Tags related to recipe seasonings, such as "rich" or "light" Tags related to the purpose of cooking or suitable occasions, such as "entertaining" or "saving time"

[0052] 5C, recipe tag information is registered using a recipe tag ID as a subcollection key value and an attribute value indicating the content of the attribute of the recipe corresponding to the recipe tag ID as a value. That is, although not shown in the figure, a unique recipe tag ID is assigned to each of the various recipe attributes described above. In the recipe tag ID group 525 of recipe memo information 500, one or more corresponding recipe tags are linked to each recipe ID.

[0053] When a user registers recipe information, for example, the user selects a recipe tag, and a new record of the recipe tag information is added to the recipe tag ID group 525. A recipe tag is selected when registering recipe information for the first time, and can also be added and registered later.

[0054] The public flag 526 shown in FIG. 5A stores a variable that can identify a selection as to whether or not to make the recipe memo corresponding to the recipe ID public to other users in the system 1. In other words, the user can select whether or not to make the information of the recipe memo registered by the user public. A variable indicating the result of that selection is stored in the public flag 526. Then, among the recipe memos, recipe information for which the value of the public flag 526 is "True" is treated as public recipe information that is subject to disclosure.

[0055] That is, in the system 1, the output module 215 of the management server 200 outputs registered recipe information designated for disclosure by one user as public recipe information to the user terminals 300 used by other users. On the other hand, the output module 215 does not output registered recipe information not designated for disclosure by one user to the user terminals 300 used by other users. This allows the user to decide for themselves whether or not to make the posted recipe public, thereby improving user convenience.

[0056] The registration date and time 527 stores information about the date and time when the user registered the recipe memo corresponding to the recipe ID.

[0057] (4-3. Original recipe information 600) FIG. 6 is an example of original recipe information 600. In the original recipe information 600, a recipe ID 610 of the original recipe, which is a unique value that can identify the original recipe, is used as a key value, and multiple values ​​620 are set. The values ​​620 include a cooking method 621, a quoted URL 622, a recipe name 623, a personal note 624, a cooking time ID 625, a recipe tag ID group 626, a public flag 627, a registration date and time 628, a cooking image 629, a main recipe image 630, an ingredient list 631, and cooking tips and tricks 632. In the original recipe, information other than the cooking method 621 is additional information. Although not shown in FIG. 6, a similar data group is linked to every recipe ID.

[0058] The cooking method 621 includes information about the cooking method that corresponds to the original recipe that corresponds to the recipe ID. The information about the cooking method includes information about the types and amounts of ingredients and seasonings, and information about the cooking procedure using them. In other words, the original recipe is recipe information that handles the cooking method entered by the user. Therefore, the original recipe information 600 includes information about the specific cooking method.

[0059] If the original recipe corresponding to the recipe ID includes other recipe sites that are cited, the URL information of the corresponding recipe sites is stored in citation URL 622. For example, if a user enters the cooking steps of a cooking video distributed on a video distribution site as text as an original recipe, the site information of the source cooking video can be registered in the citation URL. In other words, for original recipes, entering a citation URL is entirely optional, and registration may be omitted if not required.

[0060] The recipe name 623 stores the name of the original recipe corresponding to the recipe ID. The personal memo 624 stores any memo that the user inputs at the time of registration for the original recipe corresponding to the recipe ID.

[0061] A cooking time ID that is a guideline for the cooking time of the original recipe corresponding to the recipe ID is stored in the cooking time ID 625. For the cooking time ID, the cooking time information shown in Fig. 5B is also applied to the original recipe information 600.

[0062] The recipe tag ID group 626 stores identification information of the recipe tag selected by the user for the original recipe corresponding to the recipe ID. The contents of the recipe tag and recipe tag ID are the same as those shown in FIG. 5C in the explanation of the recipe memo information 500. That is, in the original recipe, as in the recipe memo, a new record of the recipe tag is added to the recipe tag ID group 626 by, for example, selecting the recipe tag when the user registers the recipe information. The recipe tag is selected when the recipe information is initially registered, and can also be added and registered later.

[0063] The public flag 627 stores a variable that can identify the result of the user's selection as to whether or not to make the original recipe corresponding to the recipe ID public to other users. The user can select whether or not to make the recipe memo information registered by the user public. A variable indicating the result is stored as the public flag. Of the original recipes, recipe information for which the public flag 627 is "True" becomes public recipe information that is subject to public disclosure.

[0064] The registration date and time 628 stores information about the date and time when the user registered the original recipe corresponding to the recipe ID. Cooking images taken by the user during the cooking process for the original recipe corresponding to the recipe ID are stored in the cooking image 629. The cooking image 629 includes images that are posted together with the cooking method of the original recipe.

[0065] A representative image, which is used as a thumbnail for this recipe information, among the cooking images taken by the user is stored in the recipe main image 630. The recipe main image 630 is generally selected from images taken during cooking and specified by the user.

[0066] The ingredient list 631 stores information about the types and amounts of ingredients and seasonings used in the recipe. The cooking tips and points 632 stores information such as points to be careful of and key points to remember when cooking the recipe.

[0067] (4-4. Public recipe search information 700) FIG. 7 shows an example of public recipe search information 700. Public recipe search information 700 is information used for searching public recipe information (published recipe notes and original recipes). When registering recipe notes and original recipes, new records are generated and recorded in public recipe search information 700 for recipe information whose publication flag is on. The registration process for public recipe search information 700 will be described in detail in FIG. 11.

[0068] 7, in public recipe search information 700, multiple values ​​720 are set using a search recipe ID 710 as a key value. Here, either a recipe memo or the recipe ID of an original recipe is used as the search recipe ID 710. The values ​​720 include a search string 721, a registered user 722, a recipe tag ID group 723, a cooking time ID 724, a registration date and time 725, a user tag history 726, and a number of times saved 727. Although not shown in FIG. 7, a similar data group is associated with every recipe ID.

[0069] The search string 721 refers to a character string that is matched against the search keyword entered by the user as a search condition when searching for recipe information corresponding to the search recipe ID. In the system 1, multiple character strings obtained by dividing the recipe name included in the additional information into groups of any number of characters are stored as the search string 721.

[0070] For example, if the recipe name is "Lettuce Fried Rice," and the name is divided into two-character strings, seven search strings are obtained: "Lettuce," "Tasu," "Suchi," "Cha," "Yaa," "Ha," and "Han." The number of characters used to divide the recipe name when generating search strings can be set arbitrarily. Furthermore, search strings may be generated not from the recipe name but from other information included in the additional information. Then, the search module 213 can extract recipe information that matches the search keyword by performing a partial match search between the search keyword and the search string specified by the user as a search condition in the recipe search.

[0071] The registered user 722 stores the user ID of the user who registered the recipe information corresponding to the search recipe ID. In the user information 400 shown in Fig. 4A, the user ID is associated with a user tag. Therefore, based on the user tag specified by the user as a search condition in a recipe search, the search module 213 can extract recipe information registered by the user corresponding to the user tag.

[0072] Recipe tag IDs linked to recipe information corresponding to the search recipe ID are stored in recipe tag ID group 723. Specifically, in the case of a recipe memo, information corresponding to recipe tag ID group 525 shown in Fig. 5A is stored in recipe tag ID group 723. In addition, in the case of an original recipe, information corresponding to recipe tag ID group 626 shown in Fig. 6 is stored in recipe tag ID group 723. Then, based on a recipe tag specified by the user as a search condition in a recipe search, search module 213 can extract recipe information corresponding to that recipe tag.

[0073] The cooking time ID of the recipe linked to the recipe information corresponding to the search recipe ID is stored in cooking time ID 724. Specifically, in the case of a recipe memo, information corresponding to cooking time ID 524 shown in FIG. 5A is stored as cooking time ID 724. In addition, in the case of an original recipe, information corresponding to cooking time ID 625 shown in FIG. 6 is stored as cooking time ID 724. Then, based on the cooking time ID specified by the user as a search condition in the recipe search, search module 213 can extract recipe information corresponding to that cooking time ID.

[0074] The registration date and time 725 stores the date and time when search information for recipe information corresponding to the search recipe ID was registered in the public recipe search information.

[0075] The user tag history 726 stores the history of user tags associated with users who have previously registered the recipe information as favorites. By checking the user tag history, it is possible to determine the attributes of the user for whom the recipe information is suitable.

[0076] Information indicating the number of times the recipe information has been saved as a favorite recipe or a recipe that users would like to make is stored in the number of times saved 727. By checking the number of times saved 727, it is possible to quantitatively grasp the degree of interest that the recipe has attracted from other users.

[0077] (4-5. My List Information 800) FIG. 8 is an example of My List information 800. The My List information 800 includes the following information, and a database is constructed for each user. Recipe information for recipe notes registered by the user Recipe information for original recipes registered by the user Recipe information for public recipes that the user has added to their favorites Although not shown in FIG. 8, a similar data group is linked to every recipe ID.

[0078] That is, in system 1, in addition to registering recipe notes and original recipes as the above-mentioned recipe note information 500 and original recipe information 600, duplicate information about the same content is also stored as My List information 800. Therefore, when searching for recipe information included in My List, for example, search module 213 does not need to search recipe note information 500 and original recipe information 600, which record a huge number of items of all recipe information. In other words, search module 213 only needs to search My List information 800 created for each user. This makes it possible to limit the search space in the recipe search process, thereby reducing the load on the search process.

[0079] Furthermore, in the system 1, not only recipe information (recipe notes and original recipes) that a user has registered, but also recipe information that other users have registered and published and that the users have registered as favorites is recorded in the My List information 800. When registering a recipe as favorites, the user can edit part of the recipe information. Specifically, the user can enter a new note for themselves in the personal notes and further add a recipe tag to be linked to that recipe information. This allows the user to customize part of the recipe information that other users have published for their own use, ensuring user convenience.

[0080] In addition, recipe notes do not store actual recipe information, such as ingredient information and cooking procedures, but rather quote information from other recipe sites. Therefore, when searching for recipe information related to recipe notes, it can be difficult to set useful search information other than the recipe name. Therefore, by sequentially accumulating recipe tags selected later in addition to the recipe tag selected initially, searching becomes easier.

[0081] In the My List information 800, a plurality of values ​​820 are set using a recipe ID 810 of the My List as a key value. The values ​​820 include a cooking method 821, a quoted URL 822, a recipe name 823, a personal note 824, a cooking time ID 825, a recipe tag ID group 826, a public flag 827, a registration date and time 828, and a cooking image 829.

[0082] These pieces of information basically refer to the values ​​of each item in the recipe memo information 500 or original recipe information 600 that was selected for favorite registration. In the case of recipe memo, the cooking method 821 and cooking image 829 for which there is no corresponding item in the value 820 are left blank. The user can separately input personal notes 824. Furthermore, when registering a new recipe tag ID as a favorite, the user can add it to the recipe tag ID group 826. Details of the recipe information update process will be described in detail with reference to FIG.

[0083] (4-6. My List Search Information 900) FIG. 9 is an example of My List search information 900. My List search information 900 is information used for searching for recipe information included in My List. A new record is generated and recorded in My List search information 900 when a recipe memo or original recipe is registered, or when a public recipe is registered as a favorite. The registration process for My List search information 900 will be described in detail in FIG. 12.

[0084] In the My List search information 900, a search recipe ID 910 is used as a key value and multiple values ​​920 are set. The search recipe ID 910 is either the recipe ID of a recipe memo or original recipe registered by the user, or the recipe ID of recipe information registered as a favorite by the user.

[0085] The value 920 includes a search string 921, a registered user 922, a recipe tag ID group 923, a cooking time ID 924, a registration date and time 925, a number of times made 926, and a date when the recipe was last made 927. Of these items, the contents of the search string 921 to the registration date and time 925 are the same as the items of the value 720 in the public recipe search information 700 shown in Fig. 7, so a description thereof will be omitted. Also, although not shown in Fig. 9, a similar data group is linked to every recipe ID.

[0086] The number of times the user has made the recipe is stored in the number of times made 926. This information is created by referring to the data ID group 415 of cooked data in the user information 400 shown in FIG.

[0087] The date when the user last made the recipe is stored in the last made date 927. This information is created by referring to the data ID group 415 of cooked data in the user information 400 shown in FIG.

[0088] (5. System 1 Processing) Next, the processing of the system 1 will be explained for each processing stage.

[0089] (5-1. Recipe information registration process) 10 shows an example of the flow of recipe information registration processing 1000. This registration processing includes the following scenes. When the user enters new recipe information related to the recipe memo When the user enters new recipe information for an original recipe When you register a recipe memo or original recipe that has already been registered and published as a favorite.

[0090] That is, when registering new recipe information, the recipe information to be input may be a recipe memo or an original recipe. In this case, the user inputs the recipe information by operating the user terminal 300. On the other hand, when registering a favorite, the recipe information to be registered as a favorite is designated by a favorite registration operation described in detail in FIG. 22.

[0091] When registering a recipe memo as new recipe information, the user inputs the URL information of another recipe site as quoted URL 521 shown in FIG. 5A, and inputs information from recipe name 522 to disclosure flag 526 as other additional information.

[0092] When a user registers an original recipe as new recipe information, the user inputs information from a citation URL 622 to a disclosure flag 627 as additional information along with information about a cooking method 621 shown in Fig. 6. The user may also input a cooking image 629.

[0093] Furthermore, when a user registers a recipe as a favorite, the user specifies the recipe card to be registered as a favorite from among the recipe cards displayed on the user terminal 300, and the specified recipe information is treated as input information for the new registration process.

[0094] 10, in the system 1, the operation receiving module 211 of the management server 200 acquires the registration information (step 1010). Specifically, the operation receiving module 211 acquires the input information transmitted from the user terminal 300.

[0095] Next, the registration module 212 of the management server 200 performs a validation check (step 1011). The validation check is a process of verifying whether the input information contains information whose registration as recipe information is restricted. Specifically, it is confirmed whether the URL information that the user is attempting to register corresponds to the registrable site information (step 1012).

[0096] If the input URL information does not correspond to the registrable site information (No in step 1012), the registration module 212 determines that registration is not possible, outputs an error message (step 1013), and terminates the process. Here, the registrable site information refers to site information that is preset as a site that is permitted to be registered (a registrable site). Examples of types of registrable sites include recipe sites that do not correspond to any of the following: Recipe service websites that prohibit disclosure of information to anyone other than specific members Websites that are unrelated to cooking content and are not properly managed by System 1 Websites that do not comply with the terms of use of System 1, such as those whose content violates public order and morals

[0097] On the other hand, if the input URL information corresponds to registrable site information (Yes in step 1012), the registration module 212 determines that the URL information can be registered. In this case, the registration module 212 checks whether recipe information with the same URL information has already been registered in the database (step 1014).

[0098] If recipe information with the same URL information has already been registered (Yes in step 1015), the registration module 212 recognizes that the registration process for that recipe information is a favorite registration for an already registered and published recipe memo or original recipe. In this case, since the recipe information related to the input information exists in the recipe memo information or original recipe information, the process proceeds without registering a new record in the recipe memo information or original recipe information.

[0099] On the other hand, if there is no recipe information having the same URL information as the input URL information in step 1015 (No in step 1015), the registration module 212 recognizes the registration process of that recipe information as registration process of new recipe information. In this case, a new record is registered in recipe memo information or original recipe information depending on the type corresponding to the input recipe information (step 1016). Thereafter, the registration module 212 proceeds with the process.

[0100] Thereafter, the registration module 212 registers the input recipe information in the My List information 800 (step 1017). Thereafter, the registration module 212 registers the new record in the public recipe search information 700 (process 1100). This process will be described in detail with reference to FIG. Thereafter, the registration module 212 registers the new record in the My List search information 900 (process 1200). This process will be described in detail with reference to FIG.

[0101] (5-2. Registration process of public recipe search information 700) FIG. 11 shows an example of the flow of the registration process 1000 of the public recipe search information 700. 11, in the process of registering the public recipe search information 700, the registration module 212 first generates a search string (step 1110). Specifically, the registration module 212 acquires the character string of the recipe name from the additional information, and divides it into a predetermined number of characters to generate a search string.

[0102] Next, the registration module 212 checks the prefix of the recipe ID of the recipe information to be registered (step 1111). In the system 1, the type of recipe can be determined by the prefix of the recipe ID. Specifically, a recipe ID with the prefix "m_" is a recipe ID related to a recipe memo. Furthermore, a recipe ID with the prefix "o_" is a recipe ID related to an original recipe.

[0103] If the prefix of the recipe ID of the recipe information to be registered is "m_" ("m_" in step 1112), the registration module 212 obtains the recipe information registered in association with that recipe ID from the recipe memo information 500 (step 1113).

[0104] On the other hand, if the prefix of the recipe ID of the recipe information to be registered is "o_" ("o_" in step 1112), the registration module obtains the recipe information registered in association with that recipe ID from the original recipe information 600 (step 1114).

[0105] Next, the registration module 212 acquires user data that registered the recipe associated with the recipe ID from the additional information included in the acquired recipe information (step 1115). Specifically, the registration module 212 acquires user information included in the input information.

[0106] Next, the registration module 212 checks whether the acquired recipe information has already been registered in the public recipe search information 700 (step 1116).

[0107] Next, if the recipe search information to be registered has already been registered (Yes in step 1117), the registration module 212 updates the recipe search information in the public recipe search information 700 (step 1118).

[0108] On the other hand, if the recipe search information to be registered has not yet been registered (No in step 1117), the registration module 212 registers new recipe search information (step 1119).

[0109] Then, the registration module 212 registers the user tag history based on the acquired user information (step 1120), thereby completing the registration process of the public recipe search information 700.

[0110] (5-3. Registration process to My List search information 900) FIG. 12 shows an example of the flow of the registration process 1200 in the My List search information 900. 12, in the registration process to My List search information 900, first, registration module 212 generates a search string (step 1210). Specifically, registration module 212 acquires the character string of the recipe name included as additional information, and divides it into a predetermined number of characters to generate a search string.

[0111] Next, the registration module 212 checks the prefix of the recipe ID of the recipe information to be registered (step 1220). If the prefix of the recipe ID of the recipe information to be registered is "m_" ("m_" in step 1230), the registration module 212 acquires the recipe information registered in association with the recipe ID from the recipe memo information 500 (step 1240).

[0112] On the other hand, if the prefix of the recipe ID of the recipe information to be registered is "o_" ("o_" in step 1230), the registration module obtains the recipe information registered in association with that recipe ID from the original recipe information 600 (step 1250).

[0113] Next, the registration module 212 acquires user data that registered the recipe associated with the recipe ID from the additional information included in the acquired recipe information (step 1260). Specifically, the registration module 212 acquires user information included in the input information.

[0114] Next, registration module 212 registers the search string generated in the previous process and the acquired recipe information and user information in the corresponding items of My List search information 900 as values ​​920 (see FIG. 9) in My List search information 900. At this time, information that needs to be updated is updated as appropriate (step 1270). This completes the registration process for My List search information 900. This also completes the recipe information registration process 1000 shown in FIG. 10.

[0115] (5-4. Recipe information search process) FIG. 13 shows an example of the flow of a recipe information search process 1300. In the system 1, recipe information can be searched for using search conditions specified by the user. The search conditions include the following four: Search keyword specification: Search criteria consisting of any string entered by the user User tag specification: Search criteria consisting of one or more user tags specified by the user. Recipe tag specification: Search criteria consisting of one or more recipe tags specified by the user. Cooking time specification: The desired cooking time specified by the user. In the system 1, the user specifies at least one of these search conditions on the user terminal 300 to search for recipe information.

[0116] 13, in the recipe information search process, first, the management server 200 acquires a search request (step 1310). Specifically, a search request including search conditions input to the user terminal 300 is transmitted from the user terminal 300 to the server. The operation reception module 211 of the management server 200 acquires the search request including the search conditions.

[0117] Next, the search module 213 of the management server 200 acquires the user ID of the user who performed the search from the search request. The user ID is used to search for recipe information from My List.

[0118] Next, the search module 213 checks the search conditions included in the search request (step 1312). Specifically, if the search conditions include a search keyword (Yes in step 1313), the search module 213 adds the search keyword to the search query (step 1314) and sets the sort order (step 1321). On the other hand, if the search conditions do not include a search keyword (No in step 1313), the search module 213 checks whether a user tag is specified in the search conditions (step 1315).

[0119] Next, if a user tag is specified in the search conditions (Yes in step 1315), the search module 213 adds the search user tag to the search query (step 1316) and sets the sort order (step 1321). On the other hand, if the search condition does not specify a user tag (No in step 1315), the search module 213 checks whether the search condition specifies a recipe tag (step 1317).

[0120] Next, if a recipe tag is specified in the search conditions (Yes in step 1317), the search module 213 adds the search recipe tag to the search query (step 1318) and sets the sort order (step 1321). On the other hand, if the search conditions do not specify a recipe tag (No in step 1317), the search module 213 checks whether the search conditions specify a cooking time (step 1319).

[0121] If the search conditions include a cooking time (Yes in step 1319), the search module 213 adds the search cooking time to the search query (step 1320) and sets the sort order (step 132). On the other hand, if the cooking time is not specified in the search conditions (No in step 1319), the search module 213 sets the sort order without adding a search query (step 1321).

[0122] In setting the sort order (step 1321), the registration module 212 sets the order in which to arrange the recipe information acquired by the search. The sort order may be set according to a default value, or may be specified by the user.

[0123] Thereafter, the search module 213 executes a search (step 1322). If a search query has been generated, the search module 213 uses the search query to search for recipe information in any of the databases of recipe memo information 500, original recipe information 600, or My List information 800, and acquires the corresponding recipe information.

[0124] On the other hand, if a search query has not been generated through steps 1313 to 1320, the search module 213 acquires all information stored in each database without using a search query. Recipe information is acquired from each database in preset quantities (for example, 20 items).

[0125] Thereafter, if there are other search conditions not included in the search query, the search module 213 narrows down the recipe information by the other search conditions for every predetermined number of acquired recipe information (for example, every 20 recipe information) (step 1324). Here, if there are no other search conditions, no narrowing down is performed.

[0126] Thereafter, the search module 213 returns the recipe IDs of the recipe information hit by the narrowing down to the output module 215 (step 1325), thereby completing the search process for recipe information.

[0127] (5-5. Recipe card display process) FIG. 14 shows an example of the flow of a recipe card display process 1400. 14, in the recipe card display process, the output module 215 acquires the recipe information to be displayed (step 1410). Specifically, the output module 215 acquires the recipe ID of the hit recipe information output as a result of the search process shown in FIG.

[0128] Next, the output module 215 generates a recipe card (step 1420). Specifically, for each piece of recipe information to be displayed, the output module 215 references the corresponding database, acquires the necessary information, and generates card information to be displayed as a recipe card.

[0129] Next, the output module 215 determines the recipe type (step 1430). Specifically, the output module 215 determines whether each piece of recipe information to be displayed corresponds to a recipe memo or an original recipe. This is because the information displayed on the recipe card differs depending on the recipe type.

[0130] If the recipe information related to the display process is a recipe memo ("recipe memo" in step S1440), the output module 215 accesses the website indicated by the URL related to the recipe site information and acquires image information of the site page. The output module 215 embeds the acquired image information and generates a recipe card for the recipe memo (step S1450).

[0131] On the other hand, if the recipe information related to the display process is an original recipe ("original recipe" in step S1440), the output module 215 generates a recipe card in which a recipe main image is embedded.

[0132] In this way, in the system 1, for registered recipe information related to original recipes, the output module 215 includes the registered recipe main image as additional information in the recipe card. On the other hand, for registered recipe information related to recipe site information, i.e., recipe notes, the output module 215 retrieves the cooking image from the website at the URL and includes it in the recipe card.

[0133] The reason why the processing procedure for displaying an image on a recipe card differs depending on the recipe type is that recipe notes are information that quotes recipe information from other recipe sites, and cooking images are not stored in the recipe note information 500. In this way, by obtaining cooking images using URL information for recipe notes, it is possible to display images that serve as thumbnails on recipe cards even for recipe notes that do not have cooking images.

[0134] Alternatively, in system 1, recipe cards for recipe notes may be generated without embedding cooking images. In this case, a dummy image is displayed instead of the cooking image. In this way, by providing different display modes for recipe cards (whether a cooking image or a dummy image), the user can easily distinguish, when viewing a list of recipe cards, whether each recipe card contains recipe information related to a recipe note or an original recipe.

[0135] Next, the output module 215 outputs the list of the generated recipe cards (step 1470). An example of the screen of the recipe cards output to the user terminal 300 will be described in detail with reference to FIG.

[0136] Next, the management server 200 registers the item as a favorite or as something the user would like to create, as necessary (step 1480). The registration of the item as a favorite or as something the user would like to create is performed based on an operation by the user. The specific operation content on the display screen will be described in detail with reference to FIG. 22.

[0137] Next, the output module 215 of the management server 200 displays details of the recipe information (process 1500). The process of displaying details of the recipe information will be described in detail with reference to FIG.

[0138] (5-6. Detailed display process of recipe information) FIG. 15 shows an example of the flow of a detailed display process 1500 of recipe information. 15, in the process of displaying details of recipe information, the output module 215 receives a detailed display instruction (step 1510). Specifically, when a pressing operation on a recipe card displayed on the user terminal 300 is received, detailed display of the recipe information is executed.

[0139] Next, the output module 215 determines the recipe type (step 1520). Specifically, the output module 215 determines whether the recipe information to be displayed in detail corresponds to a recipe memo or an original recipe. This is because the format of the recipe information detail page differs between recipe memo and original recipe, and the output module 215 selects which format to display the detailed information in.

[0140] If the recipe information related to the detailed display process is a recipe memo ("Recipe memo" in step 1530), the output module 215 embeds the URL information of the recipe memo in a detailed page format for recipe memo and generates a detailed page (step 1540). On the other hand, if the recipe information related to the display process is an original recipe ("Original Recipe" in step 1530), the output module 215 embeds the cooking method of the original recipe in a detail page format for original recipes and generates a detail page (step 1550).

[0141] In this way, in system 1, when the output module 215 receives an instruction to display details of a recipe card for an original recipe, it outputs the cooking method related to that original recipe. On the other hand, when the output module 215 receives an instruction to display details of a recipe card for a recipe note, it outputs URL information of the recipe website related to that recipe note. Therefore, for an original recipe in which a cooking method is registered, the cooking method can be displayed in detail, and for a recipe note in which no cooking method is registered, URL information of the recipe website in which the cooking method is described can be output. Therefore, regardless of which recipe information is the target of detailed display, it is possible to display all information related to the cooking method requested by the user.

[0142] The output module 215 then outputs the generated recipe details page to the display unit of the user terminal 300 (step 1560). This completes the recipe information details display process. The recipe note details page will be described in detail in FIG. 20. The original recipe details page will be described in detail in FIG. 21.

[0143] (5-7. Recipe information update process) FIG. 16 shows an example of the flow of a recipe information update process 1600. Here, the recipe information is updated in the following cases. · Update recipe information for recipe notes or original recipes you have registered yourself -Add recipe tags to your favorite recipes

[0144] 16, in the recipe information update process, the registration module 212 of the management server 200 registers the update information (step 1610). Specifically, the update information input by the user is used to overwrite the corresponding item values ​​in the database.

[0145] Next, the registration module 212 checks the user who originally registered the updated recipe information (step 1620). If the registration module 212 determines that the user who performed the update is not the same user who originally registered (Yes in step 1630), it updates the number of times saved (step 1640).

[0146] Next, the registration module 212 updates the user tag history (step 1650). Next, the registration module 212 updates the recipe tag (step 1660), and then ends the process.

[0147] On the other hand, if it is determined in step 1630 that the user who performed the update is the same user who originally registered (No in step 1630), the registration module 212 checks whether a recipe tag has been added (step 1670).

[0148] If the addition of the recipe tag is confirmed (Yes in step 1680), the registration module 212 updates the tag usage history (step 1690), and then ends the process. On the other hand, if the addition of the recipe tag is not confirmed (No in step 1680), the registration module 212 ends the process. This completes the recipe information update process.

[0149] (6. Screen example) Next, an example of an output screen that is output to the user terminal 300 in the system 1 will be described.

[0150] (6-1. Example of the first screen: Home screen) FIG. 17 is an example of a home screen 1700 in the system 1. 17 is a portal page that is first displayed when logging in to the system 1. The home screen 1700 mainly displays a search bar 1701, a pick-up 1702, a genre selection 1703, a toolbar 1704, a recommended recipe 1705, and a creation history 1706.

[0151] A search bar 1701 is an input field for search keywords in recipe search processing.

[0152] Pickup 1702 displays public recipe information that has been registered as a favorite a predetermined number of times or more. Specifically, recipes that have been registered as a favorite two or more times in the past are displayed randomly. By swiping this screen left or right, other recipe information included in pickup 1702 can be displayed. On this screen, the output module 215 of the management server 200 obtains the number of times each piece of recipe information has been registered as a favorite, calculated by the calculation module 214, and randomly extracts and outputs recipe information based on the number of times it has been registered.

[0153] The genre selection 1703 is an operation button for specifying a narrowing down of the genre of dishes to be displayed for published recipe notes and published original recipes. By selecting the appropriate genre, the pick-up 1702 is made up of recipes that fall under the selected genre.

[0154] The toolbar 1704 contains display icons for each screen for executing the main functions of the system 1. Of these, the "My List" screen is described in detail in Fig. 18, the "Everyone's List" screen in Fig. 22, and the "Search on the Web" screen in Fig. 23.

[0155] The recommended recipes 1705 is a screen that automatically recommends recipes that other similar users have registered as favorites based on the user's attributes. In this case, the output module 215 of the management server 200 references the user tag associated with the user and searches each database for recipes that other users associated with the same user tag have registered as favorites in the past, thereby extracting the recommended recipe information.

[0156] That is, in the system 1, the output module 215 refers to the My List information 800 of other users who have the same attributes as the user based on the user tag, and recommends to one user public recipe information included in the My List of the other users. This recommendation process allows users with the same attributes to share favorite recipes, and can suggest effective recipes to users. That is, the output module 215 is an example of a recommendation means.

[0157] Furthermore, in the system 1, a similar group code may be assigned to each user attribute. In this case, for example, the character strings of the user tags are vectorized, and the cosine similarity between the vectors is evaluated to assign a similar group code to each user tag. When recommending public recipe information, the output module 215 may refer to the similar group code of the user tag to identify user attributes similar to those of the user to be recommended, and recommend public recipe information included in the My List of a user with similar user attributes. This recommendation process allows users with similar attributes to share favorite recipes, and can suggest effective recipes to users.

[0158] The recipe history 1706 displays the recipes that the user has recently made. The recently made recipes can be identified by referencing the value of the cooked data linked to the user information 400. By swiping this screen left or right, other recently made recipes can be displayed.

[0159] (6-2. Example of the second screen: My List screen) FIG. 18 is an example of a My List screen 1800 in the system 1. This screen is displayed by pressing the "My List" button on toolbar 1704 in Fig. 17. Recipe information included in the user's My List is displayed on My List screen 1800. Specifically, recipe notes and original recipes registered by the user, as well as recipe information published by other users, and recipes that the user has registered as favorites are displayed as recipe cards on My List screen 1800.

[0160] In the illustrated example, the My List Display button 1801 has been selected, so a list of recipe cards for recipe information included in the My List is displayed. On the other hand, when the Cookbook List Display button 1802 is pressed on this screen, a list of recipe cards for recipe information included in the Cookbook List is displayed. In addition, the My List screen 1800 has a toolbar 1704 displayed at the bottom.

[0161] The recipe cards included in the My List are displayed on the My List screen 1800. In the illustrated example, three recipe cards 1803 to 1805 are displayed. On this screen, the recipe cards can be advanced in sort order by scrolling toward the top of the screen. In the illustrated example, three recipe cards are displayed simultaneously, but the number of recipe cards displayed simultaneously can be set as desired.

[0162] Of these, the first recipe card 1803 and the second recipe card 1804 are recipe information related to original recipes. On the other hand, the third recipe card 1805 corresponds to recipe information related to recipe notes. This screen example shows an example in which a dummy image is displayed without displaying a cooking image for the recipe card related to the recipe note. Therefore, the display manner of the two differs in whether or not a cooking image is included. As mentioned above, if an image of the site page at the URL destination for the recipe note is acquired and displayed, the acquired image may be displayed as an image (thumbnail image) on the recipe card. Each recipe card displays the cooking time A, the most recent cooking date B, and the recipe tag C stored as additional information.

[0163] Each recipe card 1803-1805 also displays a cooking count column D that indicates the number of times the dish has been cooked. In this way, the output module 215 of the management server 200 outputs the cooking history entered by the user and linked to the user information by the registration module 212, attached to the recipe card.

[0164] Additionally, each recipe card 1803-1805 displays a "Made button (cooked declaration button)" E, which allows the user to declare that they have cooked the dish. When the user cooks the recipe, the cooking history is recorded as cooked data by pressing the "Made button." In the example shown, the Made button E on the second recipe card 1804 has been selected.

[0165] (6-3. Third screen example: Search dialog screen) FIG. 19 is an example of a My List search dialog 1900 screen. In the search dialog 1900, the user can specify search conditions and perform a search process for recipe information. The user can include a search keyword in the search conditions by entering the search keyword in the search bar 1901 .

[0166] In the selected tag column 1902, when a recipe tag is selected as a search condition, the recipe tag that has already been selected is highlighted. The frequently used tag column 1903 lists recipe tags that the user frequently uses in recipe searches.

[0167] The recently used tags field 1904 lists recipe tags that the user has recently used in recipe searches. In the cooking time column 1905, when cooking time is specified as a search condition, tags for accepting the specification of cooking time are displayed.

[0168] In the recipe tag selection field 1906, recipe tags are categorized and arranged by their content. In the example shown, the original tag field selected contains recipe tags added by the user. The recipe tags are categorized by type, such as purpose, cooking utensil, fish, meat, etc., and arranged in each selection field.

[0169] (6-4. Example of the 4th screen: Recipe memo details page) FIG. 20 is an example of a screen of a recipe memo details page 2000. The recipe memo details page 2000 is a screen that is displayed by the processing of step 1560 shown in FIG. 15 when, for example, the recipe card 1805 of the recipe memo shown in FIG. 18 is selected.

[0170] A dummy image 2001 is displayed on the recipe note detail page 2000. That is, this screen example shows an example in which a dummy image is displayed without displaying a cooking image for the recipe card related to the recipe note. Because recipe notes quote recipe information from other recipe sites, they do not have cooking images related to the recipe. Therefore, no cooking images are displayed on the recipe note detail page, and a dummy image is uniformly displayed. Note that, as mentioned above, if an image of the site page at the URL destination for the recipe note is obtained, the obtained image may be displayed as the image on the detail page.

[0171] Recipe memo detail page 2000 displays quoted URL 2002. By clicking link 2003 labeled "View Recipe," the user can transition the screen of user terminal 300 to another recipe site indicated by the quoted URL and access the recipe information of the other recipe site cited in the recipe memo.

[0172] In this way, System 1 registers recipe information published on other recipe sites by quoting the URL information of those recipe sites. This allows information from various recipe sites to be centrally managed and made easily visible, improving convenience for users who use multiple recipe providing services.

[0173] Recipe memo detail page 2000 further displays estimated cooking time 2004, an add to my list button 2005, a made button 2006, and a recipe tag 2007.

[0174] Estimated cooking time 2004 displays the estimated cooking time for the recipe corresponding to the recipe memo. The Add to My List button 2005 is a button that is pressed by a user who has viewed a recipe memo published by another user to register the recipe memo as a favorite and add it to his or her own My List.

[0175] The Created button 2006 is pressed when reporting the cooking history after cooking a recipe corresponding to the recipe memo. By pressing the Created button 2006, a new record of cooked data is added.

[0176] Recipe tags linked to this recipe note are listed in Recipe Tags 2007. When a user registers a recipe note published by another user as a favorite, the user can add a recipe tag. The added recipe tag is newly linked to the recipe note related to the user's My List, and is added to and stored in the original recipe note.

[0177] (6-5. 5th screen example: Original recipe details page) FIG. 21 is an example of a screen of a details page 2100 of an original recipe. The original recipe details page 2100 is a screen that is displayed by the processing of step 1560 shown in FIG. 15 when, for example, recipe cards 1803 and 1804 of the original recipe shown in FIG. 18 are selected.

[0178] A cooking image 2101 is displayed on the details page 2100 of the original recipe. Unlike the recipe memo described above in FIG. 20, the original recipe has a cooking image that is registered when the cooking method is entered, as the user himself / herself inputs the cooking method. Therefore, the details page of the recipe memo displays the cooking image 2101. Note that if the user who registered the original recipe did not register a cooking image, a dummy image may be displayed.

[0179] The recipe memo details page 2100 further includes a "I want to make this" button 2102, an "Add to my list" button 2103, a recipe bar 2104, and a recipe display field 2105.

[0180] The "I want to make this" button 2102 is a button that a user who has viewed an original recipe published by another user presses when adding the original recipe to a list of recipes that the user wants to make.

[0181] The Add to My List button 2103 is a button that is pressed by a user who has viewed a recipe memo published by another user to register the original recipe as a favorite and add it to their own My List.

[0182] The recipe bar 2104 is a bar for selecting the category of recipe information to be displayed in the recipe display field 2105. The categories of recipe information include, for example, the following: Basic information: Basic information about the recipe, such as its origin and recommended occasions Ingredients: Information on the types and amounts of ingredients and seasonings required for the recipe. Cooking Instructions: Information about the cooking steps that make up the recipe

[0183] Recipe display field 2105 displays recipe information corresponding to the category selected in recipe bar 2104. In the example shown, "ingredients" has been selected, so information indicating ingredients is displayed from the recipe information related to the original recipe.

[0184] (6-6. Example of the 6th screen: Everyone's list display screen) FIG. 22 is an example of a display screen 2200 for everyone's list. The display screen 2200 of everyone's list is a screen that is displayed by pressing the "Everyone's Recipes" display on the toolbar 1704 shown in Fig. 17. The display screen 2200 of everyone's list displays all public recipe information that the registered users wish to make public, out of the recipe notes and original recipes registered by all users.

[0185] 13, the public recipe information narrowed down by the series of search processes is displayed as a list of recipe cards in the set sort order. In the example shown, recipe cards 2201 and 2203 for two original recipes and recipe card 2202 for one recipe memo are displayed. In addition, toolbar 1704 is displayed at the bottom of everyone's list display screen 2200.

[0186] Here, we will explain the processes of favorite registration (adding recipe information to My List) and want-to-make registration (adding recipe information to Want-to-Make List) executed on the everyone's list display screen 2200. First, we will explain the favorite registration operation.

[0187] By performing a swipe operation SW2 to the left on the second recipe card 2202 in Fig. 22, an indication C2 of adding to My List is displayed. That is, on the display screen 2200 of everyone's list, the user can register the recipe information related to the displayed recipe card in the favorites list by performing a swipe operation SW2 to the left on the recipe card. Note that the operation of registering to favorites may be performed by pressing a predetermined button instead of a swipe operation. Furthermore, the direction of the swipe operation as the operation of registering to favorites is not limited to the direction described in Fig. 22.

[0188] Next, the operation for registering recipes that the user would like to make will be described. By performing a swipe operation SW1 to the right on the first recipe card 2201 and the third recipe card 2203 in FIG. 22, a display C1 for registering recipes that the user would like to make is displayed. That is, on the display screen 2200 for everyone's list, the user can add the recipe information related to a displayed recipe card to the list of recipes that the user would like to make by performing a swipe operation SW1 to the right on the displayed recipe card. Note that the operation for registering recipes that the user would like to make may be performed by pressing a predetermined button instead of a swipe operation. Also, the direction of the swipe operation for registering recipes that the user would like to make is not limited to the direction described in FIG. 22.

[0189] In this way, in the system 1, when the registration module 212 of the management server 200 receives a swipe operation in a first direction (leftward in FIG. 22) on the display of a recipe card output to the user terminal, it registers the registered recipe information related to that recipe card as a favorite recipe. Furthermore, when the registration module 212 receives a swipe operation in a second direction (rightward in FIG. 22) that is different from the first direction, it registers the registered recipe information related to that recipe card as a recipe that the user would like to make (desired cooking recipe). This allows recipe information to be registered as a favorite or as something that the user would like to make with a simple operation, improving user convenience.

[0190] (6-7. 7th screen example: Search screen 2300 of external recipe site) FIG. 23 is an example of a search screen 2300 for an external recipe site. An external recipe site search screen 2300 is displayed by pressing the "Search on the Web" button on toolbar 1704 in Figure 17. A search bar 2301 and toolbar 1704 are displayed on external recipe site search screen 2300. The user can search for other recipe sites using search bar 2301. While accessing the other recipe site that the user has searched for, the user can obtain the URL information of the site page and register a new recipe memo.

[0191] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0192] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0193] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. The above-described embodiments disclose at least the configurations described in the claims. [Explanation of symbols]

[0194] 100... recipe management system, 200... recipe management server 200, 300... user terminal, 211... operation reception module, 212... registration module, 213... search module, 214... aggregation module, 215... output module, 400... user information, 500... recipe memo information, 600... original recipe information, 700... public recipe search information, 800... my list information, 900... my list search information

Claims

1. A receiving means for receiving an input operation; a registration means for registering recipe site information indicating the URL of the recipe site published on the website and original recipe information including the cooking method input by the input operation together with additional information in a recipe storage means, and adding the registered recipe information to the user's My List; and an output unit that outputs the recipe site information and the additional information of the original recipe information as a plurality of recipe cards.

2. The output means The recipe card for the recipe site information; The recipe management server according to claim 1 , wherein the recipe management server outputs a list in which the original recipe information and the recipe card are mixed.

3. When outputting the recipe card, the output means For the registered recipe information related to the original recipe information, the image information registered as the additional information is included in the recipe card; The recipe management server according to claim 2 , wherein image information is not included in the recipe card for the registered recipe information related to the recipe site information.

4. When outputting the recipe card, the output means For the registered recipe information related to the original recipe information, the image information registered as the additional information is included in the recipe card; The recipe management server of claim 2, wherein the registered recipe information related to the recipe site information is accessed by accessing a website indicated by a URL related to the recipe site information, and image information of the site page is obtained and included in the recipe card.

5. The output means When an instruction to display details of the recipe card for the original recipe information is received, the cooking method related to the original recipe information is output; The recipe management server according to claim 2 , wherein when an instruction to display details of the recipe card for the recipe site information is received, the recipe management server outputs a URL of the recipe site related to the recipe site information.

6. The output means outputting the registered recipe information designated by one user as public recipe information to a user terminal used by another user; The recipe management server according to claim 1 , wherein the registered recipe information that is not designated for disclosure by the one user is not output to the user terminal used by the other user.

7. The registration means A recipe management server according to any one of claims 1 to 5, wherein if the recipe site information that a user wishes to register corresponds to registrable site information indicating site information that is permitted for registration in advance, the recipe site information is registered as the registered recipe information.

8. The method further includes a search unit that receives an input of a search keyword including at least an arbitrary character string and searches for the registered recipe information including, as the additional information, information corresponding to the arbitrary character string included in the search keyword, The recipe management server according to claim 1 , wherein the output unit outputs the additional information about the registered recipe information retrieved by the retrieval unit as the recipe card.

9. The registration means, in response to the display of the recipe card output to the user terminal, When a swipe operation in a first direction is received, the registered recipe information related to the recipe card is registered in the recipe storage means as a favorite recipe indicating a recipe that is a favorite of the user; A recipe management server as described in any one of claims 1 to 5, wherein when another swipe operation in a second direction different from the first direction is received, the registered recipe information related to the recipe card is registered in the recipe storage means as a desired cooking recipe indicating a recipe that the user wishes to cook.

10. The registration means registers the cooking history input by the user in association with user information, The recipe management server according to claim 1 , wherein the output unit outputs the recipe card together with the cooking history.

11. The recipe management server according to any one of claims 1 to 5, further comprising a recommendation means that, based on an attribute tag indicating an attribute of a user selected by the user, refers to the My Lists of other users having the same or similar attributes as the user, and recommends to the user the registered recipe information included in the My Lists of the other users.

12. A method executed by a recipe management server, the method comprising: a reception step for receiving an input operation; a registration step of registering recipe site information indicating the URL of the recipe site published on the website and original recipe information including the cooking method input by the input operation together with additional information in a recipe storage means and adding the registered recipe information to the user's My List; an output step of outputting the recipe site information and the additional information of the original recipe information as a plurality of recipe cards.

13. A program that causes a recipe management server to execute each step of the recipe management method according to claim 12.

Images