Handling multiple locations on a single organization when ranking

[madeleineb]

Bearden already knows all the locations we have records of for a particular organization, providing those locations all share a single web address. However, for the purposes of the MVP, we decided to take only the one most authoritative source's location for an organization when sending ranked data to Redshift.

In the longer run, we will need a way to better rank and represent multiple locations for organizations—

1. Represent the existence of distinct locations for a single org record in the ranked output

2. Separately rank distinct addresses from multiple sources
   Example: "A Org" has locations in London and Berlin, we should recognize that Source A (rank 1) and Source B (rank 2) each have an address for London and Berlin, and choose London & Berlin from Source A rather than Source B.

3. Associate general contact information with the appropriate location.
   Example: the London and Berlin locations should have different phone numbers, and have different emails, i.e. london@a-org.com, berlin@a-org.com.