Struct aws_sdk_transcribe::input::CreateVocabularyInput
source · [−]#[non_exhaustive]pub struct CreateVocabularyInput { /* private fields */ }Implementations
sourceimpl CreateVocabularyInput
impl CreateVocabularyInput
sourcepub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateVocabulary, AwsResponseRetryClassifier>, BuildError>
pub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateVocabulary, AwsResponseRetryClassifier>, BuildError>
Consumes the builder and constructs an Operation<CreateVocabulary>
sourcepub fn builder() -> Builder
pub fn builder() -> Builder
Creates a new builder-style object to manufacture CreateVocabularyInput.
sourceimpl CreateVocabularyInput
impl CreateVocabularyInput
sourcepub fn vocabulary_name(&self) -> Option<&str>
pub fn vocabulary_name(&self) -> Option<&str>
A unique name, chosen by you, for your new custom vocabulary.
This name is case sensitive, cannot contain spaces, and must be unique within an Amazon Web Services account. If you try to create a new vocabulary with the same name as an existing vocabulary, you get a ConflictException error.
sourcepub fn language_code(&self) -> Option<&LanguageCode>
pub fn language_code(&self) -> Option<&LanguageCode>
The language code that represents the language of the entries in your custom vocabulary. Each vocabulary must contain terms in only one language.
A custom vocabulary can only be used to transcribe files in the same language as the vocabulary. For example, if you create a vocabulary using US English (en-US), you can only apply this vocabulary to files that contain English audio.
For a list of supported languages and their associated language codes, refer to the Supported languages table.
sourcepub fn phrases(&self) -> Option<&[String]>
pub fn phrases(&self) -> Option<&[String]>
Use this parameter if you want to create your vocabulary by including all desired terms, as comma-separated values, within your request. The other option for creating your vocabulary is to save your entries in a text file and upload them to an Amazon S3 bucket, then specify the location of your file using the VocabularyFileUri parameter.
Note that if you include Phrases in your request, you cannot use VocabularyFileUri; you must choose one or the other.
Each language has a character set that contains all allowed characters for that specific language. If you use unsupported characters, your vocabulary filter request fails. Refer to Character Sets for Custom Vocabularies to get the character set for your language.
sourcepub fn vocabulary_file_uri(&self) -> Option<&str>
pub fn vocabulary_file_uri(&self) -> Option<&str>
The Amazon S3 location of the text file that contains your custom vocabulary. The URI must be located in the same Amazon Web Services Region as the resource you're calling.
Here's an example URI path: s3://DOC-EXAMPLE-BUCKET/my-vocab-file.txt
Note that if you include VocabularyFileUri in your request, you cannot use the Phrases flag; you must choose one or the other.
Adds one or more custom tags, each in the form of a key:value pair, to a new custom vocabulary at the time you create this new vocabulary.
To learn more about using tags with Amazon Transcribe, refer to Tagging resources.
Trait Implementations
sourceimpl Clone for CreateVocabularyInput
impl Clone for CreateVocabularyInput
sourcefn clone(&self) -> CreateVocabularyInput
fn clone(&self) -> CreateVocabularyInput
1.0.0 · sourcefn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more