Page Comparison

...

1. For each schema, if the corresponding Synapse table hasn't been created, the Bridge Exporter
   1. creates that table
   2. sets that table with ACLs, which give the Bridge Exporter account ACCESS_TYPE_ALL and the data access team (configured and managed by the research team) ACCESS_TYPE_READ. The idea is the Bridge Exporter needs to create and write to these tables, but once exporter, the data should be immutable.
   3. adds the mapping to DDB table prod-exporter-SynapseTables (which is how we know whether the table has been created or not) IMPORTANT: If you're deleting a table from Synapse, be sure to update this mapping, or the Bridge Exporter will get confused.
2. For each study, the Bridge Exporter creates an appVersion table, if such a table doesn't already exist.
   1. This table is used to get a broad overview of all upload records in a study. It can also be used to get a table of uploads per day, uploads per version, unique healthCodes, or a combination of the above (depending on your SQL skills).
   2. The study to appVersion table mapping is found in DDB table prod-exporter-SynapseMetaTables.
3. For each schema and each appVersion table, the Bridge Exporter also creates a TSV file on disk with the headers corresponding to the schema's field names.

...