Setting Up

Last updated 04/14/2021

Hotpepper requires paths to four resources:

  • Directory that stores the Hotpepper database
  • Directory that stores input datasets (collections of audio files to transcribe)
  • Directory to which packaged datasets should be output
  • Configuration file, which is written in TOML to promote easy human editing

To learn more about configuring Hotpepper and see a sample configuration file, visit Get and Configure Deepgram Products.

Allowing Automatic Transcription

Hotpepper can be configured to allow users labeling at level L1 to submit assigned files to an on-premise Deepgram Speech Engine for automatic speech recognition (ASR) and transcription. When ASR is used, the Hotpepper server sends the assigned audio file to the configured Speech API endpoint, parses a transcript from the results, and automatically populates the Transcript textarea of the labeling view with the returned transcript. In our experience, users value this feature highly when labeling.

To learn more about setting up automatic transcription for data labeling, visit Get and Configure Deepgram Products.

Adding an Administrator

To add the first administrator, configure the following environment variables in the Docker Compose deployment files:

  • DASHSCRIPT_ADMIN_USER
  • DASHSCRIPT_ADMIN_PASSWORD

To see a sample Docker Compose file for Hotpepper, visit Deploy Deepgram Products.

Backing up Data

To avoid losing all transcripts produced by Hotpepper, back up both your dataset directories and the Hotpepper database. Hotpepper uses a SQLite database, so you only need to copy the configured database file to a secure location.