<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>User's Food Preference Extraction for Personalized Cooking Recipe Recommendation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mayumi Ueda</string-name>
          <email>mayumi@mm.media.kyoto-u.ac.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mari Takahata</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Shinsuke Nakajima</string-name>
          <email>nakajima@cse.kyoto-su.ac.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Kyoto University</institution>
        </aff>
      </contrib-group>
      <fpage>98</fpage>
      <lpage>105</lpage>
      <abstract>
        <p>There are many websites and researches that involve cooking recipe recommendation. However, these websites present cooking recipes on the basis of entry date, access frequency, or the recipe's user ratings. They do not re ect the user's personal preferences. We have proposed a personalized recipe recommendation method that is based on the user's food preferences. For extracting the user's food preferences, we use his/her recipe browsing and cooking history. In this paper, we present a method for extracting the user's preferences. In the experimental results, extracting the user's favorite ingredients were detected with a 60 to 83% of precision. And extracting the unfavorite ingredients were detected with 14.7% of precision, and 58% of recall. Furthermore, the F-measure value for extraction of favorite ingredients was 60.8% when we focused on the top 20 ingredients.</p>
      </abstract>
      <kwd-group>
        <kwd>user's food preferences</kwd>
        <kwd>preference extraction</kwd>
        <kwd>recipe recommendation</kwd>
        <kwd>cooking and browsing history</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>As a result of the lifestyle-related disease epidemic, dietary life is now attracting
attention. Good eating habits are important for maintaining a healthy life.
However, menu planning requires one to take various factors into consideration, such
as the nutritional value, food in stock, food preferences, and cost. Thus, people
need to expand a lot of effort toward planning their daily menu. Against this
background, a number of cooking websites comprising various food recipes have
recently been launched, such as Cookpad[1] and Yahoo! Recipe[2]. Many people
refer to these websites when planning their menu. Cookpad contains 900,000
recipes and has 10,000,000 monthly users[3]. This data reflects the high demand
for recipe-providing services. However, these websites do not reflect user’s
preferences and conditions, although these two factors need to be considered if the
goal is to provide high-satisfactory recipes.</p>
      <p>Furthermore, several researches on cooking recipe recommendation for menu
planning support have been conducted in the past. Mino et al. propose a method
that takes the user’s schedule into consideration[4]. This paper defines the
evaluation value of either the intake or consumption calories that are assigned to
each event in the user’s schedules. Karikome et al. propose a system that helps
users plan nutritionally balanced menus and visualize their dietary habits[5].
Their system calculates the nutritional value of each dish, and records this
information in the form of a dietary log. Next, the system recommends recipes
foster sound nutrition. Freyne et al. show the results of their investigation in
which they compare three recommendation strategies: content-based,
collaborative, and hybrid[6].</p>
      <p>In these circumstances, we have proposed a recipe recommendation method
based on the user’s food preferences[7]. Our method breaks recipes down into
their ingredients, and scores them on the basis of the frequency of use and
specificity of the ingredients. Furthermore, our proposed system does not recommend
dishes that are similar to the food the users have eaten over the past few days on
the grounds that people do not want to eat similar dishes iteratively. Moreover,
our system does not require any particular action on the user’s past to reflect
his/her food preferences: it estimates the user’s food preferences automatically
through his/hers recipe browsing and cooking history. In this paper, we present
a method for extracting the user’s preferences.</p>
      <p>This paper is structured as follows. Section 2 describes the method of scoring
recipes and extracting user’s preferences. Section 3 shows experimental results,
using precision and recall. Section 4 shows concludes the paper.
2</p>
      <p>
        Scoring Recipes and Extracting User's Preferences
In the recent years, concern over various health issues, such as lifestyle-related
diseases and diets, has been growing. It has also been noted that picky eating
is one of the main reasons causing these health issues. However, people do not
want to eat food that they dislike even if it perfectly addresses their nutritional
needs. They hope to derive essential nutrition solely from their favorite foods.
We conducted questionnaire to the 20 men and women in their 20s to 40s to
survey the key considerations for menu planning. According to the results of the
questionnaire, people consider the following elements (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) food preferences, (
        <xref ref-type="bibr" rid="ref2">2</xref>
        )
nutritional balance and calories, (
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) ingredients they have in stock or they can
procure easily, (
        <xref ref-type="bibr" rid="ref4">4</xref>
        ) easily to cook, and (
        <xref ref-type="bibr" rid="ref5">5</xref>
        ) mood. Therefore, in this paper, we
focus on (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) food preferences and try to extract user’s food preferences.
2.1
      </p>
      <p>
        Preferences for Ingredients
We express the user’s food preferences Ik by using in the form of the following
Eq.(
        <xref ref-type="bibr" rid="ref1">1</xref>
        ).
      </p>
      <p>
        Ik = Ik+ + Ik
(
        <xref ref-type="bibr" rid="ref1">1</xref>
        )
      </p>
      <p>
        User's favorite ingredients Fig.1 shows the key idea behind estimating user’s
favorite ingredients by his/her cooking history. Our method considers the
ingredient that the user eats repeatedly as his/her favorite ingredients. It breaks
recipes down into their ingredient as the outset and calculates the score of
ingredients Ik+ by incorporating the frequency of use of the ingredients in the
dishes that the target user has eaten(F Fk: Foodstuff Frequency) as well as the
specificity of ingredients(IRFk: Inverted Recipe Frequency) into Eq.(
        <xref ref-type="bibr" rid="ref2">2</xref>
        ). This
equation is based on the idea of TF-IDF.
      </p>
      <p>Ik+ = F Fk</p>
      <p>
        IRFk
For estimating the user’s favorite ingredients by using the frequency of use of
ingredient k (F Fk), we utilize the simple frequency of use of ingredient k (Fk)
during a definite period D, as shown in Eq.(
        <xref ref-type="bibr" rid="ref3">3</xref>
        ).
      </p>
      <p>F Fk =</p>
      <p>Fk</p>
      <p>D
IRFk = log</p>
      <p>
        M
Mk
Then, we calculate —it the specificity of ingredient k (IRFk) using the total
number of recipe (M ) and the number of recipes that contain ingredient k (Mk),
as shown in Eq.(
        <xref ref-type="bibr" rid="ref4">4</xref>
        ).
(
        <xref ref-type="bibr" rid="ref2">2</xref>
        )
(
        <xref ref-type="bibr" rid="ref3">3</xref>
        )
(
        <xref ref-type="bibr" rid="ref4">4</xref>
        )
User's disliked ingredients We consider that user’s food preferences are also
influenced by his/her disliked ingredients. We estimate the user’s disliked
ingredients, by considering the ingredients in the recipes that he/she has never
cooked, even if he/she has browsed the recipe details. Fig.2 shows the
estimating method for user’s disliked ingredients through the user’s recipe browsing and
cooking history. N corresponds to the set of ingredients in the recipes that the
user has not browse. C corresponds to the set of ingredients in the recipes that
the user has cooked over the past few days. U corresponds to the set of
ingredients in the recipes that the user has not cooked, even if he/she has browse them
completely. For example, “shrimp” in Fig.2 corresponds to the user’s disliked
ingredient. We calculate the score of disliked ingredient k (Ik ) in Eq.(
        <xref ref-type="bibr" rid="ref5">5</xref>
        ).
      </p>
      <p>Ik (x) =
{ 0
( 2jjAUkkjj
1)x
(0 &lt; 2jjAUkkjj 5 0:5)
(0:5 &lt; 2jjAUkkjj 5 1)
jUkj denotes the presence of ingredient k in U and jAkj denotes the presence of
ingredient k in the recipe database. We should investigate the ratio or frequency
of the user’s avoidance of the ingredient that he/she dislikes, because he/she will
use the ingredients that he/she does not like. x denotes the ratio or frequency
of avoiding the ingredients, and we plan to verify x through some preliminary
experiments.
2.2</p>
      <p>
        Recipe Scoring
Our method scores cooking recipes in accordance with the estimation results
regarding favorite/disliked ingredients, and then provides recipes in decreasing
order of the scores. In general, people do not like eating dishes similar to those
they have eaten in the past few days. Therefore, our method weights recipes to
avoid the repetition of similar dishes. The score of cooking recipes are defined as
shown in Eq.(
        <xref ref-type="bibr" rid="ref6">6</xref>
        ).
      </p>
      <p>
        Score(R) =
∑ Ik
k2R
∑ (wd sim (R; Rd))
d=1
(
        <xref ref-type="bibr" rid="ref5">5</xref>
        )
(
        <xref ref-type="bibr" rid="ref6">6</xref>
        )
d denotes the weight for avoiding repeating similar dishes iteratively. sim (R; Rd)
denotes the similarities between the considered recipe R and the recipe of the
dish eaten d days ago Rd. The weight wd for avoiding similar dishes eaten d days
ago is defined as shown in Eq.(
        <xref ref-type="bibr" rid="ref7">7</xref>
        ).
      </p>
      <p>wd = 1
d</p>
      <p>
        1
7
(1 5 d 5 7)
(
        <xref ref-type="bibr" rid="ref7">7</xref>
        )
3
      </p>
      <p>Evaluation of the Accuracy of Extracting User's Food
Preference
3.1</p>
      <p>Experimental Condition
In order to verify the extracting accuracy of the user’s food preferences, we
conducted simple experiments. We used 100 recipes extracted from Cookpad[1]
that is a most popular recipe search website in Japan. We used randomly selected
recipes categorized as main dish.</p>
      <p>We conducted experiment as follows.
1. We present a list of 10 recipe titles to subjects.
2. He/She chooses recipes which he/she would like to browse completely, such
as ingredients, procedures, and so on.
3. He/She chooses one recipe that he/she would like to cook.
4. Repeat this sequence(Step 1 to 3) 10 times.</p>
      <p>We gathered each user’s browsed recipes and recipes he/she would like to cook
through the above procedure. 6 men and women in their 20s to 40s participated
in this experiment as subjects.</p>
      <p>
        We calculated the specificity of ingredient k (IRFk) in the target 100 recipes,
using Eq.(
        <xref ref-type="bibr" rid="ref4">4</xref>
        ). Table 1 shows the examples of IRFk. Furthermore, we collected
the labeled data as the user’s preferences via questionnaire. Responses are coded
on a 6-point scale, ranging from “love” to “hate”.
3.2
      </p>
      <p>
        Evaluation of Extracting the Favorite Ingredients
We evaluated the extraction accuracy of the user’s favorite ingredients. We
extracted individual user’s favorite ingredients by calculating Ik+, using Eq.(
        <xref ref-type="bibr" rid="ref2">2</xref>
        ). For
evaluating the accuracy, we calculated precision, recall, and F-measure for top
N ingredients which sorted by Ik+. The results are shown in Table 2 and Fig.3.
The precision, recall, and F-measure were calculated by the number of extracted
user’s favorite ingredients in the top N (E) and the number of user’s favorite
ingredients via questionnaire (Q), as follows.
      </p>
      <p>P recision =</p>
      <p>Recall =</p>
      <p>E
N
E
Q
pumpkin 1.70 oyster 1.52 white wine 1.10
cucumber 1.70 eggplant 1.40 mayonnaise 1.01
burdock root 1.70 parsley 1.40 tomato 1.00
konjac 1.70 honey 1.40 sesame oil 0.96
snow crab 1.70 beef 1.40 carrot 0.92
green pepper 1.70 shrimp 1.30 butter 0.92
yellowtail 1.70 bacon 1.30 milk 0.92
lettuce 1.70 Japanese radish 1.22 mushroom 0.89
yam 1.70 minced meat 1.22 egg 0.77
soy milk 1.70 potato 1.15 pork 0.74
pickled plum 1.70 miso 1.15 ginger 0.68
chinese chive 1.52 lemon 1.15 garlic 0.57
bean sprout 1.52 tofu 1.15 cibol 0.57
salmon 1.52 cabbage 1.10 chicken 0.54
Colocasia esculenta 1.52 cheese 1.10 onion 0.44</p>
      <p>
        As shown in Table 2, when we focused on the only top one ingredient (N = 1),
our method extracted with precision of 83.3%. However, at the same time, the
recall was only 4.5%. When we focused on the top 20 ingredients (N = 20),
the recall was increased to 61%. Since the average number of individual user’s
favorite ingredients was 19.2, the recall was not enough value when we focused on
a few ingredients such as N = 1; 3; 5. It was found from the result that even if our
system focused on the top 20 ingredients (N = 20), the precision did not reduce
very much. Furthermore, the highest value of F-measure, at this experiment,
was 60.8% when we focused on the top 20 ingredients (Table 2). Therefore, the
results show that our system should focus on the top 20 ingredients sorted by
Ik+ for recipe recommendation.
We evaluated the accuracy of extracting user’s disliked ingredients. We extracted
individual user’s disliked ingredients by calculating Ik , using Eq.(
        <xref ref-type="bibr" rid="ref5">5</xref>
        ). The
precision of the extracting disliked ingredients was 14.7%, and the recall was 58.3%.
In this experiment, we considered that the ingredients which were contained only
in U , were the user’s disliked ingredients. In other words, in this experiment, our
method estimated the user’s disliked ingredients which were in the recipes that
he/she has never cooked, even if he/she has browsed the complete recipe.
disliked ingredients = fU \ Cg
(9)
In this experiment, we could not extract satisfactory accuracy for disliked
ingredients, because of the lack of the number of experiments. Since the number of
experiments was not enough, our method determined that the ingredient which
happened to include in U was his/her disliked ingredient. We consider that our
method can improve the accuracy of extracting favorite ingredients, by
increasing the number of experiments.
4
      </p>
    </sec>
    <sec id="sec-2">
      <title>Conclusion</title>
      <p>In this paper, we presented a method for extracting the user’s food preferences for
recipe recommendation. Our method estimates a user’s preferences from his/her
past actions, such as through their recipe browsing and menu planning history.
For extracting the preferences, our method breaks recipes down into their
ingredients and scores the recipes using the frequency and specificity of ingredients.
Since our method can estimate the preferences through their browsing and
cooking history, the user convey his/her preferences to the system without having
to carry out any particular operation. Furthermore, the user can convey the
changes in his/her preferences to the system on a daily basis.</p>
      <p>In order to verify the extracting accuracy of the user’s food preferences,
we conducted simple experiments. In the experimental results, extracting the
user’s favorite ingredients were detected with a 60 to 83% of precision. And
the F-measure was 60.8% when we focused on the top 20 ingredients. Since the
average number of user’s favorite ingredients was 19.2, our system should focus
on the top 20 ingredients sorted by Ik+ to score recipes for recommendation. And
extracting the disliked ingredient were detected with 14.7% of precision, and 58%
of recall. In this time, we could not extract satisfactory accuracy. However, we
consider that our method can improve the accuracy of extraction, by increasing
the number of experiments.</p>
      <p>
        As future work, we plan to consider the ingredient ontology for estimating
favorite/disliked ingredients. Furthermore, we plan to investigate the various
weights. For example, we plan to verify x in Eq.(
        <xref ref-type="bibr" rid="ref5">5</xref>
        ), the ratio or frequency of
avoiding the ingredients, through experiments. Moreover, we want to investigate
the length of time for which the system should avoid recommending similar
dishes for d in Eq.(
        <xref ref-type="bibr" rid="ref6">6</xref>
        ),(
        <xref ref-type="bibr" rid="ref7">7</xref>
        ), and the degree of similarity that the system should
consider while refraining from recommending similar dishes for in Eq.(
        <xref ref-type="bibr" rid="ref6">6</xref>
        ).
      </p>
    </sec>
    <sec id="sec-3">
      <title>Acknowledgments</title>
      <p>This work is supported in part by Kyoto University Global COE Program:
Informatics Education and Research Center for Knowledge-Circulating Society
(MEXT Global COE Program) , and the MEXT Grant-in-Aid for Scientific
Research(C) (#23500140).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Cookpad. http://cookpad.com/,
          <source>(Accessed 12 August</source>
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. Yahoo! Recipe. http://recipe.gourmet.yahoo.co.jp/,
          <source>(Accessed 12 August</source>
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <article-title>Choose dishes using websites of cooking. (in Japanese)</article-title>
          , http://otona.- yomiuri.co.jp/news/news110118 03.htm,
          <source>(Accessed 12 August</source>
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Yoko</given-names>
            <surname>Mino</surname>
          </string-name>
          and
          <string-name>
            <given-names>Ichiro</given-names>
            <surname>Kobayashi</surname>
          </string-name>
          .
          <article-title>Recipe Recommendation for a Diet Considering a User's Schedule and the Balance of Nourishment</article-title>
          .
          <source>Proceedings of IEEE International Conference on Intelligent Computing and Intelligent Systems</source>
          <year>2009</year>
          , pp.
          <fpage>383</fpage>
          -
          <lpage>387</lpage>
          .
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Shihono</given-names>
            <surname>Karikome</surname>
          </string-name>
          and
          <string-name>
            <given-names>Atsushi</given-names>
            <surname>Fujii</surname>
          </string-name>
          .
          <article-title>A System for Supporting Dietary Habits: Planning Menus and Visualizing Nutritional Intake Balance</article-title>
          .
          <source>Proceedings of the 4th International Conference on Ubiquitous Information Management and Communication</source>
          , pp.
          <fpage>386</fpage>
          -
          <lpage>391</lpage>
          .
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>Jill</given-names>
            <surname>Freye</surname>
          </string-name>
          and
          <string-name>
            <given-names>Shlomo</given-names>
            <surname>Berkovsky</surname>
          </string-name>
          .
          <article-title>Intelligent Food Planning: Personalized Recipe Recommendation</article-title>
          . In IUI(
          <year>2010</year>
          )
          <fpage>321</fpage>
          -
          <lpage>324</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>Mayumi</given-names>
            <surname>Ueda</surname>
          </string-name>
          , Mari Takahata and
          <string-name>
            <given-names>Shinsuke</given-names>
            <surname>Nakajima</surname>
          </string-name>
          .
          <article-title>Recipe Recommendation Method Based on User's Food Preferences</article-title>
          .
          <source>Proceedings of the IADIS International Conference on e-Society</source>
          <year>2011</year>
          , pp.
          <fpage>591</fpage>
          -
          <lpage>594</lpage>
          .
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>