Difference between revisions of "Restaurant Guide"

From ConRunner
Jump to: navigation, search
(categorize)
Line 12: Line 12:
 
*website (for menus, online booking etc.)
 
*website (for menus, online booking etc.)
 
*price guide (either a typical meal price range, or sometimes encoded, e.g. "$"=cheap to "$$$$$"=very expensive)
 
*price guide (either a typical meal price range, or sometimes encoded, e.g. "$"=cheap to "$$$$$"=very expensive)
*any other factual notes (dress code, closed on Labor Day, booking required on Saturday evenings, Kareoke Elvis during all-you-can-eat Sunday Cheeseburger Buffet)
+
*any other factual notes (e.g. dress code, closed on Labor Day, booking required on Saturday evenings, Karaoke Elvis during all-you-can-eat Sunday Cheeseburger Buffet, etc.)
 
*if possible, a quick review ("great pizza, avoid the garlic bread, service very slow on Saturdays")
 
*if possible, a quick review ("great pizza, avoid the garlic bread, service very slow on Saturdays")
  
Line 25: Line 25:
  
 
Cross reference with local area map (e.g. put in reference numbers on the map and match them up on the restaurant list).
 
Cross reference with local area map (e.g. put in reference numbers on the map and match them up on the restaurant list).
 +
 +
[[category:Publications]]
 +
[[category:Member Relations]]
 +
[[category:Hospitality]]

Revision as of 17:02, 27 March 2007

Restaurant Guide

A list of places to eat (pretty obvious really!).

There have been many good restaurant guides produced over the years, and here is some of the information that they have included:

  • Name of restaurant
  • Cuisine type (pizza, Indian, French etc.)
  • Address
  • Zip/postal code, especially useful if people will be using SatNav or MapQuest/Multimap etc.
  • phone number for booking or to order delivery
  • website (for menus, online booking etc.)
  • price guide (either a typical meal price range, or sometimes encoded, e.g. "$"=cheap to "$$$$$"=very expensive)
  • any other factual notes (e.g. dress code, closed on Labor Day, booking required on Saturday evenings, Karaoke Elvis during all-you-can-eat Sunday Cheeseburger Buffet, etc.)
  • if possible, a quick review ("great pizza, avoid the garlic bread, service very slow on Saturdays")


Unless it is a really short list, it is suggested that restaurants should be listed grouped by cuisine/culture (e.g. Japanese, Italian etc.)

It is also possible to group restaurants into "delivery/takeaway" and "eat in".

And it is possible to divide restaurants by distance/time (e.g. short walking distance, long walk, taxi/car/bus distance).

To reduce duplication of data, each sub-divided group can just list the restaurants that come under that heading (e.g. a list of Japanese restaurants) and then there can be an alphabetical restaurant list with the contact details, pricing etc.

Cross reference with local area map (e.g. put in reference numbers on the map and match them up on the restaurant list).