You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
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
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: