Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

transcribe Update models to latest #3214

Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
/*
* Copyright 2010-2022 Amazon.com, Inc. or its affiliates. All Rights Reserved.
* Copyright 2010-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License").
* You may not use this file except in compliance with the License.
Expand Down Expand Up @@ -120,12 +120,12 @@ public interface AmazonTranscribe {
* </p>
* <p>
* When creating a new category, you can use the <code>InputType</code>
* parameter to label the category as a batch category (
* <code>POST_CALL</code>) or a streaming category (<code>REAL_TIME</code>).
* Batch categories can only be applied to batch transcriptions and
* streaming categories can only be applied to streaming transcriptions. If
* you do not include <code>InputType</code>, your category is created as a
* batch category by default.
* parameter to label the category as a <code>POST_CALL</code> or a
* <code>REAL_TIME</code> category. <code>POST_CALL</code> categories can
* only be applied to post-call transcriptions and <code>REAL_TIME</code>
* categories can only be applied to real-time transcriptions. If you do not
* include <code>InputType</code>, your category is created as a
* <code>POST_CALL</code> category by default.
* </p>
* <p>
* Call Analytics categories are composed of rules. For each category, you
Expand All @@ -138,9 +138,9 @@ public interface AmazonTranscribe {
* <p>
* To learn more about Call Analytics categories, see <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-batch.html"
* >Creating categories for batch transcriptions</a> and <a href=
* >Creating categories for post-call transcriptions</a> and <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-stream.html"
* >Creating categories for streaming transcriptions</a>.
* >Creating categories for real-time transcriptions</a>.
* </p>
*
* @param createCallAnalyticsCategoryRequest
Expand Down Expand Up @@ -221,11 +221,11 @@ CreateLanguageModelResult createLanguageModel(
* </p>
* <p>
* Before creating a new custom medical vocabulary, you must first upload a
* text file that contains your new entries, phrases, and terms into an
* Amazon S3 bucket. Note that this differs from , where you can include a
* list of terms within your request using the <code>Phrases</code> flag;
* text file that contains your vocabulary table into an Amazon S3 bucket.
* Note that this differs from , where you can include a list of terms
* within your request using the <code>Phrases</code> flag;
* <code>CreateMedicalVocabulary</code> does not support the
* <code>Phrases</code> flag.
* <code>Phrases</code> flag and only accepts vocabularies in table format.
* </p>
* <p>
* Each language has a character set that contains all allowed characters
Expand Down Expand Up @@ -1101,16 +1101,19 @@ ListVocabularyFiltersResult listVocabularyFilters(
* retroactively applied to a job. To create a new category, use the
* operation. To learn more about Call Analytics categories, see <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-batch.html"
* >Creating categories for batch transcriptions</a> and <a href=
* >Creating categories for post-call transcriptions</a> and <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-stream.html"
* >Creating categories for streaming transcriptions</a>.
* >Creating categories for real-time transcriptions</a>.
* </p>
* <p>
* To make a <code>StartCallAnalyticsJob</code> request, you must first
* upload your media file into an Amazon S3 bucket; you can then specify the
* Amazon S3 location of the file using the <code>Media</code> parameter.
* </p>
* <p>
* Note that job queuing is enabled by default for Call Analytics jobs.
* </p>
* <p>
* You must include the following parameters in your
* <code>StartCallAnalyticsJob</code> request:
* </p>
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
/*
* Copyright 2010-2022 Amazon.com, Inc. or its affiliates. All Rights Reserved.
* Copyright 2010-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License").
* You may not use this file except in compliance with the License.
Expand Down Expand Up @@ -64,12 +64,12 @@ public interface AmazonTranscribeAsync extends AmazonTranscribe {
* </p>
* <p>
* When creating a new category, you can use the <code>InputType</code>
* parameter to label the category as a batch category (
* <code>POST_CALL</code>) or a streaming category (<code>REAL_TIME</code>).
* Batch categories can only be applied to batch transcriptions and
* streaming categories can only be applied to streaming transcriptions. If
* you do not include <code>InputType</code>, your category is created as a
* batch category by default.
* parameter to label the category as a <code>POST_CALL</code> or a
* <code>REAL_TIME</code> category. <code>POST_CALL</code> categories can
* only be applied to post-call transcriptions and <code>REAL_TIME</code>
* categories can only be applied to real-time transcriptions. If you do not
* include <code>InputType</code>, your category is created as a
* <code>POST_CALL</code> category by default.
* </p>
* <p>
* Call Analytics categories are composed of rules. For each category, you
Expand All @@ -82,9 +82,9 @@ public interface AmazonTranscribeAsync extends AmazonTranscribe {
* <p>
* To learn more about Call Analytics categories, see <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-batch.html"
* >Creating categories for batch transcriptions</a> and <a href=
* >Creating categories for post-call transcriptions</a> and <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-stream.html"
* >Creating categories for streaming transcriptions</a>.
* >Creating categories for real-time transcriptions</a>.
* </p>
*
* @param createCallAnalyticsCategoryRequest
Expand Down Expand Up @@ -119,12 +119,12 @@ Future<CreateCallAnalyticsCategoryResult> createCallAnalyticsCategoryAsync(
* </p>
* <p>
* When creating a new category, you can use the <code>InputType</code>
* parameter to label the category as a batch category (
* <code>POST_CALL</code>) or a streaming category (<code>REAL_TIME</code>).
* Batch categories can only be applied to batch transcriptions and
* streaming categories can only be applied to streaming transcriptions. If
* you do not include <code>InputType</code>, your category is created as a
* batch category by default.
* parameter to label the category as a <code>POST_CALL</code> or a
* <code>REAL_TIME</code> category. <code>POST_CALL</code> categories can
* only be applied to post-call transcriptions and <code>REAL_TIME</code>
* categories can only be applied to real-time transcriptions. If you do not
* include <code>InputType</code>, your category is created as a
* <code>POST_CALL</code> category by default.
* </p>
* <p>
* Call Analytics categories are composed of rules. For each category, you
Expand All @@ -137,9 +137,9 @@ Future<CreateCallAnalyticsCategoryResult> createCallAnalyticsCategoryAsync(
* <p>
* To learn more about Call Analytics categories, see <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-batch.html"
* >Creating categories for batch transcriptions</a> and <a href=
* >Creating categories for post-call transcriptions</a> and <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-stream.html"
* >Creating categories for streaming transcriptions</a>.
* >Creating categories for real-time transcriptions</a>.
* </p>
*
* @param createCallAnalyticsCategoryRequest
Expand Down Expand Up @@ -282,11 +282,11 @@ Future<CreateLanguageModelResult> createLanguageModelAsync(
* </p>
* <p>
* Before creating a new custom medical vocabulary, you must first upload a
* text file that contains your new entries, phrases, and terms into an
* Amazon S3 bucket. Note that this differs from , where you can include a
* list of terms within your request using the <code>Phrases</code> flag;
* text file that contains your vocabulary table into an Amazon S3 bucket.
* Note that this differs from , where you can include a list of terms
* within your request using the <code>Phrases</code> flag;
* <code>CreateMedicalVocabulary</code> does not support the
* <code>Phrases</code> flag.
* <code>Phrases</code> flag and only accepts vocabularies in table format.
* </p>
* <p>
* Each language has a character set that contains all allowed characters
Expand Down Expand Up @@ -328,11 +328,11 @@ Future<CreateMedicalVocabularyResult> createMedicalVocabularyAsync(
* </p>
* <p>
* Before creating a new custom medical vocabulary, you must first upload a
* text file that contains your new entries, phrases, and terms into an
* Amazon S3 bucket. Note that this differs from , where you can include a
* list of terms within your request using the <code>Phrases</code> flag;
* text file that contains your vocabulary table into an Amazon S3 bucket.
* Note that this differs from , where you can include a list of terms
* within your request using the <code>Phrases</code> flag;
* <code>CreateMedicalVocabulary</code> does not support the
* <code>Phrases</code> flag.
* <code>Phrases</code> flag and only accepts vocabularies in table format.
* </p>
* <p>
* Each language has a character set that contains all allowed characters
Expand Down Expand Up @@ -2222,16 +2222,19 @@ Future<ListVocabularyFiltersResult> listVocabularyFiltersAsync(
* retroactively applied to a job. To create a new category, use the
* operation. To learn more about Call Analytics categories, see <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-batch.html"
* >Creating categories for batch transcriptions</a> and <a href=
* >Creating categories for post-call transcriptions</a> and <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-stream.html"
* >Creating categories for streaming transcriptions</a>.
* >Creating categories for real-time transcriptions</a>.
* </p>
* <p>
* To make a <code>StartCallAnalyticsJob</code> request, you must first
* upload your media file into an Amazon S3 bucket; you can then specify the
* Amazon S3 location of the file using the <code>Media</code> parameter.
* </p>
* <p>
* Note that job queuing is enabled by default for Call Analytics jobs.
* </p>
* <p>
* You must include the following parameters in your
* <code>StartCallAnalyticsJob</code> request:
* </p>
Expand Down Expand Up @@ -2317,16 +2320,19 @@ Future<StartCallAnalyticsJobResult> startCallAnalyticsJobAsync(
* retroactively applied to a job. To create a new category, use the
* operation. To learn more about Call Analytics categories, see <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-batch.html"
* >Creating categories for batch transcriptions</a> and <a href=
* >Creating categories for post-call transcriptions</a> and <a href=
* "https://docs.aws.amazon.com/transcribe/latest/dg/tca-categories-stream.html"
* >Creating categories for streaming transcriptions</a>.
* >Creating categories for real-time transcriptions</a>.
* </p>
* <p>
* To make a <code>StartCallAnalyticsJob</code> request, you must first
* upload your media file into an Amazon S3 bucket; you can then specify the
* Amazon S3 location of the file using the <code>Media</code> parameter.
* </p>
* <p>
* Note that job queuing is enabled by default for Call Analytics jobs.
* </p>
* <p>
* You must include the following parameters in your
* <code>StartCallAnalyticsJob</code> request:
* </p>
Expand Down
Loading