Handling confidential addresses in HSDS 3.0

Just providing an update on this. We are actually liking one of @robredpath 's earlier suggestions the most, and I wish I had been astute enough to forecast that at the time.

Adding a location.type of redacted most neatly communicates the most and most useful information:

  1. We can interpret how to handle addresses, but I still know what type the addresses themselves are.
  2. It’s important to know whether a location is redacted at the location level, because if the address should be redacted, then the lat/long usually should be too.
  3. The heuristics for our most common types of locations are already located here at the location level: A) Call Centers (et al) are “virtual” indicating a non-physical intake point, B) Domestic Violence Shelters are “redacted” indicating confidential information, and everything else is “physical”. We have few or no cases so far for labeling a location as “mailing”, but I’m sure those edge cases exist.

I would recommend that we add a new location.location_type of “redacted” in a future, minor update. Thoughts @devin @robredpath @bloom ?