Feature Request: Set OutputKey for transcription job #67
Description
Given the input files for call recordings are nicely stored in the S3 bucket in a key such as connect/instance-name/CallRecordings/year/month/day/ it seems a shame that the transcription json files are stored directly in the bucket, making it much harder to browse in the UI
Setting the OutputKey on the start_transcription_job call to something like lambda-name/CallTranscriptions/year/month/day/ would seem to be a better idea