Determine a method for matching people in a localized area

If beans were to support matching in a specific city and support neighborhood matching in that city, we would want an expandable way to match people based on their location. There are a few ways to do this.

1. Set up individual instances of the service for each sub region

• + simplifies logic
• - doesn't allow you to save history from meetings across regions (ie if someone met before and they switch regions, the datastore would be different and wouldn't know if they met anyone before in the new region)

2. Use the metadata field for the User entity to specify the User's "location". From there we could specify a matching filter to only look at people in the same area (we do the exact opposite for keeping people from matching in the same department) This would explicitly bucket you based on your area.

• - increases complexity
• + allows for management of an entire area in one app
• - this increases the number of matching bins, meaning low activity areas would be more prone to

Start by reading yelp_beans/match.py around the existing department-based matching exclusion, then inspect how the User metadata field is represented. Compare the two location approaches described in the issue, including their effects on history and matching groups. Done means selecting and documenting an expandable approach for city and neighborhood matching.