Transcription DB Update

[ddfridley]

Our current transcription functionality will generate new transcriptions when participants record.

To update what's in the database already, and to update things that get missed from time to time, we need a tool that runs through the database and finds all the participants without transcriptions and adds one.

Because there is a cost involved in doing all this transcription - we should prompt the user and say how many records we are about to translate.

And lets give the user the ability to put a query string on the command line. It would be a quoted string in JSON format, that would be converted to an object and then Object.assigned to the generic query string for participants. (meaning combined).

this should be a standalone node function in app/tools.

[poornaraob]

07/15: Use Url to determine which candidate conversation's to translate. Expect to complete by 07/21

https://github.com/EnCiv/smpreview

[ddfridley]

@djbowers wanted to let you know that I took a big step toward doing this. I'll push an update to the transcribe-frontend branch tomorrow. I wrote a tool that, given a database and a participantId will create a transcription Iota for the existing participant Iota.

[poornaraob]

07/22: @ddfridley completed the task. It is still in testing not in production yet. There is a tool (transcribe-participate) for creating the viewer id and transcribe it. It is inside transcribe front end branch.