Skip to content
This repository was archived by the owner on Feb 23, 2022. It is now read-only.

Data Structures

mahrsbar edited this page Nov 17, 2021 · 11 revisions

Campaigns table

Describes the campaigns and the amount of letters sent for each campaign. CampaignTable


letter_versions table

This data is sent to Lob, primarily template_id which is specific to each campaign by office division. This data structure triages the letter object that's being displayed and sent, specific to the template_id of the region that's being picked by the office.

​​LetterVersions

  • keyID: use to create join or belong relationships for Users, Campaigns, and Letters sent
  • template_id: lob html template
  • office_division: each campaign has a different letter dependent on filter. Federal is the default.
  • state: Custom versions per state
  • county: Custom versions per county
  • CampaignID: maps to campaigns table

letter_sent table

Way to understand volumes of letters being sent. This table will be used to measure conversion for letter_upload, user_volunteer and user_campaign. letter_sent


Constituent Table

constituent

*This information is collected from review letter screen

  • Letters sent holds id of letter that was successfully posted with Lob (payment and address verification went through)
  • User agreement is a boolean that they abide by the platforms best practices
  • Updates is sending campaign_id so that we can send to advocacy groups so they can follow up and by our user education team
  • Street address, City, and State are strings
  • Zipcode is a string
Clone this wiki locally