Auto Transcribe
QName: f:auto-transcribe
With this feature in place, a content instance will automatically have an audio attachment converted to text
using speech-to-text conversion. The generated text will be stored back to an attachment named transcription
(as
a text/plain
file).
To use this service, you will first need to set up a Transcription Service. The service can either be configured
as the default Transcription Service for your Project or it can be referenced from the f:auto-transcribe
feature.
This allows different feature configurations to use different services if that is your preference.
The feature is defined as shown here:
{
"_qname": "f:auto-transcribe",
"_type": "d:feature",
"type": "object",
"title": "Auto Transcribe",
"description": "Indicates that a node with an attachment should have a transcription produced automatically",
"systemBootstrapped": true
}
Configuration
<thead>
<tr>
<th>Property</th>
<th>Type</th>
<th>Default</th>
<th nowrap>Read-Only</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>serviceId</td>
<td>text</td>
<td></td>
<td></td>
<td>
The `_doc` identifier of the Transcription Service configuration to use.
</td>
</tr>
<tr>
<td>sourceAttachmentId</td>
<td>text</td>
<td></td>
<td></td>
<td>
The name of the source attachment containing the source audio. Default is `default`.
</td>
</tr>
</tbody>
Transcription
The resulting transcription text file is stored onto the content node as the transcription
attachment.
For more information, please see our formal documentation on how Cloud CMS works with Transcription.
Example
If you have a default Transcription Service configured for your project, all you need to do is this:
{
"title": "My Document",
"_features": {
"f:auto-transcribe": {
}
}
}
Otherwise, you will need to point to a configuration:
{
"title": "My Document",
"_features": {
"f:auto-transcribe": {
"serviceId": "ec0a7bfb2d2f971b262e"
}
}
}