Audio Data Process

Overview:

This page provides information about DAILP’s current and past audio data processes.

Past Audio Data Processes

DAILP’s audio data processes have evolved over the years as project needs have changed. At the start of Spring 2023, DAILP transitioned our long term storage and archiving of audio from the Northeastern University Digital Scholarship Group's (DSG) Digital Repository Service (DRS) to DAILP-managed AWS S3 buckets. This transition to the AWS S3 buckets was in preparation for user submitted audio.

Then prior to Spring 2024, DAILP’s audio data processes were collected and recorded primarily over Zoom. From the Zoom recording, the audio data was encoded and segmented using Praat and then archived in the DSG Digital Repository Service (DRS). Archived audio segments in the DRS were attached to entries in the DAILP database and displayed publicly on the DAILP website.

By Spring 2024, the project began shifting toward a new user contribution workflow that moved the new audio recordings and uploading process to be accomplished directly on the DAILP website. This has established DAILP’s current audio recording process.

Current Audio Process

The front-end aspects of DAILP’s audio data process include the ability to record, save, and publish document and individual word audio on the DAILP Translation Interface (TI). Editors and Contributors have the ability to contribute audio.

Our User Contributed Audio page and User Workflows page have additional information about how Editors and Contributors can use DAILP’s audio features.

Once audio is recorded on DAILP Translation Interface (TI), the audio file directly uploads to the DAILP AWS media server. The audio metadata, which includes who made the audio and when the audio was created, is saved to the database.

The audio relies on a database governance structure that links corresponding entries. Meaning, the word audio is owned by the word translation and the document audio is owned by the document translation.