Proposal: "exports" process

[bertday]

Right now AIS can ingest address data but doesn't have a way of exporting the standardized and geocoded version back to a common database, which means that some datasets need to be processed a second time in order to be mapped, analyzed, etc. (use case: RTT transactions). The only product is Address Summary, which is one-to-one with addresses and can be difficult to join back to source datasets that don't map cleanly to addresses. This feature would add a process to copy those source tables, append standardized address and XY fields, and place them back in the enterprise database.

The config could take a list of address sources that require an export:

'exports': [
    {
        'source_name': 'rtt_documents',
        # potentially more config here...
    }
]

[Alexander-M-Waldman]

@rbrtmrtn is this as simple as joining address_summary to source_address table based on street_address?