Strategy discussion on resiliency of validation API about test-at-home HOT 4 CLOSED

Dirty (less than pristine) Event Stream

Even taking bad orders, we, and USPS should be able to generate a filter that de-dupes a relatively dirty event stream, to normalize per residential address. This is a question for the USPS meeting agenda.

Which address services?

Is the order of services:

1. Smarty
2. USPS
3. none / fallback
4. turn of service

Do we need another?

from test-at-home.

11:30 mtg where this will be discussed (amongst other things re:address validation).

from test-at-home.

Decision from 11:30 meeting.

Approach:
Must have by 1/18 launch

• Create a parallel app that will intake orders
  • Email is mandatory for this app
• Orders will be saved without validating address
• Upon API recovery, a background process will validate address for those orders
• Email can be used to contact users of any post processing issues encountered by that process

Nice to have by 1/18 launch

• Parallel app would implement, on top of above, an address validation against USPS API

from test-at-home.

#67 and #68 created. Closing this issue as path forward was agreed upon.

from test-at-home.