Scaffolding for Google Drive Action

[gabestein]

Motivation

So users can insert content into PubPub from Google Drive

Requirements

• Users can add the gdrive action to their workflows from the action tab of a stage
• Allows users to specify a pub field which contains a Google Drive URL
• Allows users to specify a field which will serve as the html content field for the pub, where generated HTML will be stored
• When run, given google drive URL in field, runs code that @isTravis will iterate on over time that will eventually accomplish the below.

Eventual Gdrive Functionality

• Generate HTML from Google Document in folder and update specified HTML content Pub field
• Create related pub field for citations if needed, create or update (if already extant) related pubs for citations and adds related fields with string values for any text that should be added to the citation (e.g. page numbers)
• Create related pub field for tags if needed, create or update tag pubs and adds related fields with null value
• Create or updates child pubs for images, including uploading images to platform assets bucket in folder named same as pub id
• In action settings, users can specify shortcodes for creating related pubs and transforming some text into HTML

Acceptance Criteria

• Uses a globally stored Google account key (see: Sensitive Key Storage Tables #779) to query drive API (could use a local env var for testing purposes/so as not to be blocked)

Extra work

[tefkah]

is it worth making the "write output to a specific field" a more generic functionality of actions, as that's also being done in the http action? if not for now, i will just reuse that code in an ugly way

[gabestein]

Definitely eventually...but I feel like we should design that more intentionally, and for now it could be copied.