Get clear about intake to know whether Federalist will be sustainable for GSA privacy

[nikzei]

We've been focused on getting the front end right; this is re: getting the backend right: let's get clearer about how data will come in, whether we can keep a simple and sustainable process for our partners while relying on Federalist.

[AC]
Test whether Federalist + google script works for partners.

• have script/questions ready
  • Is GSA privacy ok with a google spreadsheet?
  • If they find a typo, they'll be ok updating it in the spreadsheet
  • Ok with adding new data into spreadsheet
  • ok with a five minute delay?
  • anything else
• outcomes from test help us answer this question
• engineering folks to make final call with next steps for backend build

(for scale w/ agencies that don't use google, we'd have to build it out, prob)

[ondrae]

I've got a rough plan:

• We have a spreadsheet of data that is shared with our partners.
• They can make changes to it as they want.
• They can even create a google form that enters data into the spreadsheet as a new row.
• We have a google script that runs whenever a change is made.
• This google script saves the data of the sheet as a csv.
• This google script commits the csv to our privacy-dashboard repo.
• In a few minutes that new data from the spreadsheet shows up on the production website.

[ondrae]

I talked about the source of the idea above with reference links at https://gsa-tts.slack.com/archives/CNT2MQF7V/p1582062720148000

[nikzei]

Maybe save for week two, sprint 3.

[peterrowland]

Working on question script here: https://docs.google.com/document/d/1SN1owLoygSQjsANKHqBCuBgeQirH8m7mFvK50CV0M0o/edit