Confirm delivery to CSCL manager

[mattyschell]

This repo currently plans to output 2 datasets:

1. subaddress_delete: A list of sub_address_ids to be deleted
2. subaddress_add: Subaddress records with business values populated

The repo should remain agnostic about how and when the CSCL manager processes these outputs. New synthetic and business keys (objectid, ap_id) should not be managed by this repo, that is a real-time CSCL processing concern.

Confirm the above with the CSCL team. If we need some more processing to make these outputs ready for CSCL loading we should separate those concerns into another repo or SQL in a word document or whatever the team prefers.

[mattyschell]

CSCL management says:

• subaddress_add should have all of the same columns and types as target subaddress except for globalid
• this includes columns that will be unpopulated like objectid, created_by, etc

Final output should be a file geodatabase.