Primadonna

If we ever want to give Drake his google maps mash-up, we're going to have to store addresses with restaurants (also zip codes). Which raises two issues:

1. How do we get addresses? Obviously we don't ask the user for them, 'cause if someone asked me to find and key in addresses for 12 restaurants before I could start using their system, I would fall out of my chair laughing. And if I hit my head on the corner of a desk on the way down, I'd sue. The only approach I can see is to do a yahoo search everytime a restaurant is created (using the restaurant name and group zip) and then prompt with "Do you mean X (at 12345 Y Street)?" And that has risks, too.
   
2. A lotta people like these here chain restaurants. So we run into an issue when "The Lunchtastics" in MI and "The Lunchmatics" in OH both want to include Chili's in their list of restaurants. Obviously there are about 12 million ways to solve this one, but all of them add more data. Plus if we're really moving to the tag model, it would be nice to know that the Chili's in MI and the Chili's in OH are both "crappy" "chains."

Whatever solution we come up with, I think Drake better start looking into the best practice way to parse the response data from Yahoo's Local Search Web Service in Ruby -- there's gotta be some way to dynamically create objects once you figure out Yahoo's XML-style.