In elgg_restaurant_info table, there is currently a "Category" field instead of
nationality we previously proposed. For example, for a korean restaurant, its
category field may have this kind of string "Restaurants, Korean Restaurants,
Pan Asian Restaurants, Family Restaurants". At one hand it made us a little
difficult to categorize restaurants by nationality, but at the other hand it
makes easier for searching to work if we have a search box at top.
So in the API to categorize restaurants, it needs to do some parsing first, we
can have an all-nation list first like {korean, thai, chinese, american,
russian,...}, during the parsing "Category" value for each restaurant, if we
found a sub-string belong to this list, then take it out and put in another new
list. Frontend will only need to display this new list.
We also put a search box at top. If user prefer searching a restaurant, then
another API searches restaurants by comparing their "Category" value with
searching words.
Original issue reported on code.google.com by jt.xion...@gmail.com on 9 Aug 2010 at 6:06
Original issue reported on code.google.com by
jt.xion...@gmail.com
on 9 Aug 2010 at 6:06