amplify
amplify copied to clipboard
Data in Transit: Lob letter cardinality
Description
Advocacy groups singly pointed out that customized letters help gather pivotal data points for impactful storytelling thats specific to localized solutions.
Exit Criteria & References:
- [ ] #360
- [ ] #593
- [ ] #707
- [ ] Define letter template object #183
- [ ] #708
- [ ] Explore salting or hashing of content. Encrypt JSON string input by constituent via either UUID or salt entire string
User Story: How to encrypt data so we can aggregate and tell compelling stories based on communities: recommendations, experience, org affiliations, etc
- User enters message to customize letter
- Customized message is added to letter to be printed as a merge variable
- Once letter is sent, a copy of the template is saved in our database
- Personal User information related to the letter_sent is encrypted (name, email, number, address except for zipcode) so aggregates of data can be presented in a visual dashboard adhering to PII compliance
Context & Considerations
- slides 42-44
- We use Objection.js to store current data structures
- Currently our letter templates are stored in Lob. Lob sends paper mail. Lob.js file for Amplify
- We have templates within Lob
- We currently use retrieve to display the letter
- We currently use post to create_letter and send
- We need to hold this information in our ORM since Lob does not break down location further than state level We need to cache the customization of the letter if user wants to save their past work
Code This line in lobjs documentation can either be string or template_id, it can be changed to customized data, either by sending back customized part via submit api and concating in the backend or send it as a file param which is concated in the frontend, adding a input field though as part of this issue