On 6 Jul 2021, at 17:51, Ken Renard <kdrenard2@gmail.com> wrote:

3. User runs the tool and output is generated. Users are then asked
(and encouraged) to take an independent action to publish the data
(such as run a publish_data.sh script). The user may review the data
before executing the action to publish.

This one is tricky from a quality control standpoint.

First, because it requires that the tool store data locally somewhere, and then be able to retrieve it later. This can break for a number of reasons.

Second, it gives the user a chance to edit the file before it is sent. With this choice we’re going to end up with lots of user edited data entries, or failed data push events where the user tries to edit the data and then breaks the format of it. Thereby breaking the whole process.

--Andrew