Configuring and running Scribe transcription

This article contains a description of the Speech Transcription Data Management Policy configuration.

A Data Management policy configured with the Speech Transcription action is used for specifying the recorded conversations to be transcribed. Servers running the Verba Speech Analytics Service read the media file from an SMB storage, then store the recorded conversations on their local disk temporarily while transcribing. The audio files are then sent to the Scribe servers for transcription over HTTPS. After the transcript is created, the media files will be discarded, and the transcript and analytics files are moved to the media's storage location. Each policy you define can be set up for a set of filters to determine which conversations should be transcribed. These filters are based on the metadata stored in the database for each conversation.

This is a good way to account for differences used for conversations of different locations, groups etc.

Creating a transcription policy

Step 1 - Follow the generic policy creation steps described on the following page: Data management policies

Step 2 - Select Speech Transcription as the action.

Step 3 - Select the Scribe data processor.

Step 5 - Select your filters to specify which conversations should be processed by this policy.

Step 6 - Click on Save. The policy will run periodically.

Running and monitoring the transcription process

The transcription actions are executed by the Verba Speech Analytics Service on the servers where this service is enabled in combination with the Scribe transcription containers. 

The transcription process can be monitored on the Dashboard with a Background Tasks Widget or in the list of background tasks in the Verba Web Interface at System > Background Tasks.

The Log files for the service can be found at (your application path might be different):