Spoke: Add ability to load/import a script from Google doc, other external source

[joemcl]

It would be really handy to be able to load or import a Campaign 'script'/Interactions and Canned from an external source, particularly a Google Drive doc, which is what we use for templates and draft scripts. That way a collaborator can help edit/tweak a script and once finalized a user with Spoke Admin rights can import it right into a new campaign. It would also eliminate the tedium and time-waste of copying and pasting Interactions and Canned from a Google Doc into the Campaign creation UI.

[joemcl]

For example, Google Docs can connect to external APIs, and there might be an existing Zapier 'zap' to connect a Google Doc to a Postgres database.

[deasterdaywfp]

Yes! The amount of time that this would save is monumental and really want to endorse this idea wholeheartedly -- cc: @codygordon @bchrobot @shakalee14

[joemcl]

Thanks @deasterdaywfp . And see https://zapier.com/apps/google-docs/integrations/postgresql for example.

[bchrobot]

Do you have a proposed idea of what the format of the Google Doc would be and how that would map to a script? A link to a read-only example Google Doc would be very helpful.

[deasterdaywfp]

1405: 20190425 TX Meet and Greet with Dede -- Canvass Event Turnout
20190427
https://docs.google.com/document/d/1yWRJX5Jqze-AW2t4zJi83OjwvRt9EoyL7hm0BW7GLI4/edit?usp=drivesdk

On Wed, May 1, 2019, 9:25 AM Benjamin Chrobot [e-mail]
wrote:

Do you have a proposed idea of what the format of the Google Doc would be
and how that would map to a script? A link to a read-only example Google
Doc would be very helpful.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MoveOnOrg/Spoke/issues/1102#issuecomment-488281262,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIQWPSRU4G2VWXH5JAHYK5TPTGK5JANCNFSM4HJFMNBA
.

[schuyler1d]

@deasterdaywfp While I agree that it would be very cool to do something like this, my experience is that injesting a loose document format like a Google text doc would be fraught and error-prone -- honestly even doing so with a spreadsheet which is more structured would likely also be error prone.

I think existing work around this issue has gone with two directions

1. Copying past campaigns also copies a script which you can then edit. MoveOn, for instance has several 'template' campaigns we don't start at all, but just use to copy scripts to
2. Some old work that would need revival for syncing scripts with OSDI-supporting software is here: https://github.com/MoveOnOrg/Spoke/pull/690

That said, if someone builds this and sees it usefully operational locally, we'd be more than happy to merge. It would be a great feature.

For developers, I would recommend doing some careful work on the format before starting -- before even touching Spoke, making a separate library that can serialize a google doc is probably the first step, and then seeing how it performs after edits, and other pathological edge cases.

[joemcl]

@schuyler1d so maybe Google Doc/Sheet to json, with an automated check that the json is in correct format, then to Postgres?

[deasterdaywfp]

Joe it occurs to me that maybe the better way to do this is actually an
integration of survey questions from Votivate directly into spoke kind of
like how we have it set up with integration set up for syncing targeted
universes.

At least covering voter disposition basics.

On Thu, May 2, 2019, 3:21 PM Joe McLaughlin [e-mail]
wrote:

@schuyler1d https://github.com/schuyler1d so maybe Google Doc/Sheet to
json, with an automatrd check that the json is in correct format, then to
Postgres?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MoveOnOrg/Spoke/issues/1102#issuecomment-488798568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIQWPSQNFSCYTMINHQPBF5LPTM5MNANCNFSM4HJFMNBA
.

[joemcl]

@schuyler1d re this - "Copying past campaigns also copies a script which you can then edit. MoveOn, for instance has several 'template' campaigns we don't start at all, but just use to copy scripts to" - we do that too - clone/copy Campaigns and edit them. But, that requires collaborators to be an Admin on Spoke to edit those, and to not mess up loading of Interactions, which happens. With a Google Docs draft script, we can have a number of collaborators, using an interface with which they are familiar, who can make edits and not have to learn the correct way of editing or loading Interactions.

[joemcl]

Joe it occurs to me that maybe the better way to do this is actually an integration of survey questions from Votivate directly into spoke kind of like how we have it set up with integration set up for syncing targeted universes. At least covering voter disposition basics.
…
On Thu, May 2, 2019, 3:21 PM Joe McLaughlin @.*> wrote: @schuyler1d https://github.com/schuyler1d so maybe Google Doc/Sheet to json, with an automatrd check that the json is in correct format, then to Postgres? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1102 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AIQWPSQNFSCYTMINHQPBF5LPTM5MNANCNFSM4HJFMNBA .

@deasterdaywfp sure but that requires access to Votivate .

[joemcl]

@schuyler1d yes totally support moving this along as well - but it's different - and @codygordon @deasterdaywfp would be great for Votivate to implement OSDI - "Some old work that would need revival for syncing scripts with OSDI-supporting software is here: #690"

[joemcl]

I'm thinking as a first step that loading Canned should be simpler than Interactions - because there are no 'steps' in Canned, just one piece of text.

[shakalee14]

Fixed with https://github.com/MoveOnOrg/Spoke/pull/1134 and #1118

[joshco]

@joemcl is there a sample google document formatted for script import for reference?

[joemcl]

@joshco see this , and cc: @deasterdaywfp and @lperson -
https://docs.google.com/document/d/1zKRbDU9vwetJlfWYgSGd1taBEVj_QrI7bhu4snvHlmg/edit?usp=sharing