Define a data structure for Auditor 2 "voucher" data, metadata, and media files to be ingested

[rudokemper]

Feature Request

We need a define a data structure that will feed into an ETL pipeline for storing Auditor 2 "voucher" data, associated metadata, and media files in a data lake.

For this issue, let's focus on the structure of the source data only; the actual pipeline scripting will be handled at a later stage.

We can close the issue when we have schematized a mapping of incoming source columns (from multiple CSVs) to database columns, and file storage paths.

Implementation

• @abfleishman to create table with “human readable" labels
• @abfleishman to finalize CSV tables (with human readable labels added)
• @rudokemper to create schema mapping incoming source columns to database columns, and file paths