vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The limit is being reduced by location according to the schedule in Table 1.



Table 1. Schedule of 50-hour limit per location

 Location Planned date of new limit Actual date of new limit 

 eu-gb (London) 11 August 2022 11 August 2022 
 au-syd (Sydney) 19 October 2022 19 October 2022 
 us-east (Washington, DC) First-quarter 2023 TBD 
 us-south (Dallas) First-quarter 2023 TBD 
 eu-de (Frankfurt) First-quarter 2023 TBD 
 jp-tok (Tokyo) First-quarter 2023 TBD 



If you currently have a custom acoustic model with more than 50 hours of audio data, you can do one of the following:



* Leave the model alone. The model will continue to work with speech recognition requests. However, you cannot add more audio to the model or retrain the model.
* Reduce the amount of audio that the model contains. Maintain the audio that makes the most difference, meaning the audio that is most representative of the characteristics that you wish to address with the model. Remove audio that is less characteristics of the audio you plan to recognize. By using only better quality audio, you can reduce the amount audio the you need for the model.
* If possible, separate the audio into multiple models. Create new, smaller models that address specific characteristics that the original model addressed. For example, you might be using the same model to represent multiple audio characteristics. Instead of relying on a single large model, create multiple smaller models that represent more refined characteristics. This might not be possible for all models. But because you can specify only a single custom acoustic model with a speech recognition request, it can help if your data accommodates such refinement.
Creating and managing custom models 

The first step in working with any custom model is to create it. Once it exists, you can manage the model by querying or updating its metadata and entries, and by deleting it if it is no longer needed. Before getting started, review the following general usage information about custom models.

A custom model can also include custom prompts that you define for the Tune by Example feature. For more information about Tune by Example, custom prompts, and speaker models, see [Understanding Tune by Example](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-tbe-intro).



 Usage notes for customization 

Consider the following guidelines when working with the customization interface.



 Ownership of custom models 

A custom model is owned by the instance of the Text to Speech service whose credentials are used to create it. You must use credentials for that service instance with methods of the customization interface to work with the custom model in any way.

All credentials obtained for the same instance of the Text to Speech service share access to all custom models created for that service instance. To restrict access to a custom model, create a separate instance of the service and use only the credentials for that service instance to create and work with the model. Credentials for other service instances cannot affect the custom model.

An advantage of sharing ownership across credentials is that you can cancel a set of credentials, for example, if they become compromised. You can then create new credentials for the same service instance and still maintain ownership of and access to custom models created with the original credentials.





 Information security 

The service allows you to associate a customer ID with data that is added or updated for custom models. You can associate a customer ID with custom words by passing the X-Watson-Metadata header with the following methods. If necessary, you can then delete the data associated with the customer ID by using the DELETE /v1/user_data method.



* POST /v1/customizations/{customization_id}
* POST /v1/customizations/{customization_id}/words
* PUT /v1/customizations/{customization_id}/words/{word}
To learn how to create a search skill in Watson Assistant, see [Creating a search skill](https://cloud.ibm.com/docs/services/assistant?topic=assistant-skill-search-add). (This feature is available only to Watson Assistant Plus or Premium plan users.)

See the following to learn more about working with Discovery:



* To learn how to create a service instance, see [Getting started with the Discovery tooling](https://cloud.ibm.com/docs/discovery?topic=discovery-getting-started). Select Washington, DC or Dallas as the region for your instance. The COVID-19 kit is available in all pricing plans, including Lite plans. See [Discovery pricing plans](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans) for details on each plan.
* After you create your instance, click Launch Watson Discovery. On the Manage data screen, choose Create COVID-19 kit to create a collection that uses the pre-configured web sources. After the collection is created, click the Sync settings tab to view the names of the web sites in the collection. To learn more about working with collections, see [Managing collections](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcesmanage-collections).
* You can create additional collections by uploading documents, crawling other websites, or connecting to other data sources (including Box, Salesforce, Microsoft SharePoint Online, Microsoft SharePoint 2016 On-Premise, and IBM Cloud Object Storage). See [Creating a collection using the tooling](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcessource_tooling) and [Available data sources](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcesavailable) for details.
* To learn how to extract custom fields from your documents, see [Smart Document Understanding](https://cloud.ibm.com/docs/discovery?topic=discovery-sdu).
* You can automatically filter stopwords (words that add little value) out of queries.
[Create Root Keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-root-keys) You can create up to 5 aliases while creating a root key. 
 [Create Standard Keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-standard-keys) You can create up to 5 aliases while creating a standard key. 
 [Retrieve a key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-key) You can retrieve a key by ID or alias. 
 [View key metadata](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-key-metadata) You can retrieve the metadata of a key by ID or alias.
Manager Read, edit, delete, or create assistants and skills in the service instance; view all conversation logs; access the v1 API for all skills in the instance. 







 Resource-level service roles 

To fine tune a person's level of access to individual skills and assistants within the instance, assign one or more resource-level service roles to the user.

You do not need to assign resource-level roles to people who already have access to all the resources based on their global service role. But, if you want to tailor a bit more who can read, edit, or add to specific assistants or skills within the instance, then apply resource-level roles.

You cannot assign someone to a resource-level role that has fewer privileges than the instance-level role to which the person is assigned. If the person has an instance-level Manager access role, for example, you cannot give them read-only access to a specific assistant. The higher-level role assignment wins.



Table 3. Resource service role details

 Role Privileges of the users in this role 

 Reader Open and read the assistant or skill, but not edit it. 
 Writer Read, edit, delete, or create an assistant or skill. 
 Manager Read, edit, delete, or create an assistant or skill, and view conversation logs. 



Anyone who creates an assistant or skill is automatically granted the Manager service role to that resource.





 Service access examples 



* Reader

The following screen capture shows you what someone with Reader service access to a resource sees on the Dialog page.

![Shows the dialog page with disabled buttons.](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/access-control-read-only.png)

Most buttons, such as Add node, Add folder, and Save new version are disabled. There is no Analytics option in the navigation. The "Try it out" pane is available.
* Writer

This screen capture shows you what someone with Writer service access to a resource sees on the same page.

!
To understand which roles can do an action, go to the row that describes the action, and find the columns for the role you are interested in.

 Action Reader Writer Manager 

 Open and view an assistant or skill ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 View API details for an assistant or skill ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Create an assistant or skill ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Rename, edit, delete an assistant or skill ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Open, view, create, edit, or delete an integration ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Add, swap, or remove skills !
Creating a job 

You create a recognition job by calling the POST /v1/recognitions method. How you learn the status and results of the job depends on the approach you use and the parameters you pass:



* To use callback notifications, include the callback_url query parameter to specify a URL to which the service is to send callback notifications when the status of the job changes. You can also specify the following optional query parameters:



* events to subscribe to a list of notification events. By default, the service sends callback notifications when the job is started (the recognitions.started event), when the job is complete (the recognitions.completed event), and if an error occurs (the recognitions.failed event). You can specify a subset of the events or use the recognitions.completed_with_results event instead of the recognitions.completed event to include the results with the job-completed notification.
* user_token to specify a string that is to be included with each notification for the job. Because you can use the same callback URL with an indefinite number of jobs, you can leverage user tokens to differentiate notifications for different jobs.



* To use polling, omit the callback_url, events, and user_token query parameters. You must then use the GET /v1/recognitions or GET /v1/recognitions/{id} methods to check the status of the job, using the latter to retrieve the results when the job is complete.



In both cases, you can include the results_ttl query parameter to specify the number of minutes for which the results are to remain available after the job completes. The new job is owned by the instance of the service whose credentials are used to create it.

In addition to the previous parameters, which are specific to the asynchronous interface, the POST /v1/recognitions method supports most of the same parameters as the WebSocket and synchronous HTTP interfaces. For more information, see the [Parameter summary](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-summary).



 Callback notifications
Plan information 

The assistant that you build is hosted by IBM Cloud Pak for Data.



 Artifact limits 

Information about the artifact limits is available from the topics that describe how to create the artifacts, so you can refer to the limits when you need to know them. Here are links to the topics:



* [Assistants](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-assistant-addassistant-add-limits)
* [Counterexamples](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-irrelevance-detectionirrelevance-detection-limits)
* [Dialog nodes](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-tasksdialog-tasks-node-limits)
* [Entities](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-entitiesentities-limits)
* [Inactivity timeout](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-assistant-settingsassistant-settings-session-limits)
* [Intents](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-intentsintents-limits)
* [Integrations](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-deploy-integration-adddeploy-integration-add-limits)
* [Logs](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-logslogs-limits)
* [Skills](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-skill-addskill-add-limits)
* [Versions](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-versionsversions-limits)







 User information 

A unique user is recognized by the user ID that is associated with the person that interacts with your assistant.
The Stripe credit card processing service allows a maximum of 25 subscriptions per account.

 How to fix it 

Ensure that you have an Enterprise level account for your API Connect service, and that there are fewer than 25 instances. If you already have the maximum number of instances, remove an instance.





 Getting help and support for API Connect 

If you have problems or questions when using API Connect, you can get help by searching for information or by asking questions through a forum. You can also open a support ticket.

When using the forums to ask a question, tag your question so that it is seen by the IBM Cloud development teams.



* If you have technical questions about developing or deploying an app with API Connect, post your question on Stack Overflow and tag your question with "ibm-cloud" and "api connect."
* For questions about the service and getting stated instructions, use the IBM DeveloperWorks dW Answers forum. Include the "ibm cloud" and "api connect" tags. See Getting help for more details about using the forums.



For information about opening an IBM support ticket, or about support levels and ticket severities, see [Contacting support](https://cloud.ibm.com/docs/get-support?topic=get-support-getting-customer-support).
You can select any step that precedes the step you are editing.

Note that only the selected steps will repeat, regardless of their And then settings. Therefore, if you want to repeat the entire action up to this point, you must select all of the previous steps.

The current step you are editing is automatically included in the list of steps to be repeated. To avoid an infinite loop, use step conditions to ensure that this step only executes when it is appropriate for previous steps to be repeated. For example, you might have a step that repeats previous steps only if the user answered No to a confirmation question; this way, if the user answers Yes, nothing is repeated and the action continues.
3. Click Apply.



Any session variable values that were defined based on choices that the customer made in the repeated steps are cleared and replaced with the new responses.

There is no option to jump to a later step. Instead of jumping directly to a later step, control the flow through the intervening steps with step conditions or skipping steps.





 Go to a subaction 

An action that is called from another action is referred to as a subaction. This option switches the conversation flow to another action. If you have an action flow that can be applied across multiple actions, you can use a subaction to build it once and then call it from each action that needs it. For example, as part of an action to place an order, you might call a subaction that enables a new customer to create an account.

To call a subaction:



1. In the And then field, select Go to a subaction.
2. In the Settings window, click the Go to field and select the action that you want to call.
3. If you do not want to continue with the current action, click End this action after the other action is completed. You might use this option in cases where the customer decides to do something different; in this case, you want the conversation flow to switch to the subaction and not return.

By default, the assistant returns to the current action after the subaction completes. Any action variables or session variables that are defined in the subaction are accessible from subsequent steps in the calling action.
4.
Assembling a team 

The creation of a model requires input from subject matter experts, project managers, and users who can understand and interpret statistical models. You must add a user in Knowledge Studio for each person who needs to log in.



 Before you begin 



* Make sure you're using a supported browser. For information, see [Browser requirements](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-system-requirements).
* Make sure that you are assigned an Admin role for your Knowledge Studio instance. The first user to launch Knowledge Studio is automatically assigned an Admin role.
* Understand the [Knowledge Studio roles](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-rolesdescriptions) that you can assign.







 Adding users in Knowledge Studio 

To add users to a Knowledge Studio service instance:



1. [Launch the Knowledge Studio application.](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-wks_tutintrolaunching-the-knowledge-studio-application)
2. Click the Settings icon ![the Settings icon](https://cloud.ibm.com/docs-content/v1/content/148d3bd95f946aa1bb53ea1540475f522e6b61c9/watson-knowledge-studio-data/images/settings.png)
3. In the Manage users section, enter the IBMid for the user you want to add.
4. Select the role you want to give the user. For descriptions of the roles that are available, see [User roles in Knowledge Studio](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-roles).

Note: You can't downgrade user roles after assigning them, so be sure that you understand the tasks each role can perform when assigning the admin role and project manager role.
Optional: You can adjust the maximum number of facet values that are displayed.

The maximum number is the sum of the number of facet values that are displayed for each facet type. By default, a total of 10 facet values are displayed.
5. As you test the facet, you can adjust the options.







 Creating a facet by creating a dictionary 

Add a facet to group a set of terms that have special meaning to your use case by creating a dictionary.

For example, an owner of a retail clothing store collects customer reviews and wants to be able to find any recurring complaints to identify retail items to discontinue. The owner can create a dictionary to help recognize and tag mentions of specific articles of clothing in the review text. To support the goal of filtering customer feedback by clothing article type, the owner might add entries similar to the entries listed in the following table.



Example dictionary entries

 Dictionary entry Synonyms Dictionary name 

 shirt top,button-down,tunic,blouse,t-shirt,long-sleeve,short-sleeve,tank clothing 
 pants slacks,jeans,leggings,sweats,capris,culottes,trousers,chinos clothing 



A review that says, This long-sleeve is so badly proportioned. Who has arms that long! is returned when you filter the documents by the clothing facet.

To create a facet by creating a dictionary, complete the following steps:



1. On the Improve and customize page, click Customize display, and then click Facets.
2. Click New facet > By creating a dictionary.
3. Enter a name for the facet, and then create a dictionary of the terms that you want to categorize.

After you save the dictionary, the name that you used for the facet label is shown in the list of facets.
4. As you test the facet, you can add more terms to the dictionary you created by selecting Teach domain concepts > Dictionaries.

The dictionary that you created is shown in the list on the Dictionaries page.
Through the Developer Portal, the customer is then able to subscribe to one of the Plans that is available to them, as determined in the API Manager. If it is a Plan with billing, the customer must provide credit card information when subscribing. The user can subscribe to one Plan from a specific Product. Multiple Plans within a single Product are useful in that they can fulfill similar purposes but with differing levels of performance and cost. For example, you might have a "Demo Plan", which makes a single API available, and a "Full Plan", which makes several available.

As well as controlling which APIs a customer can use, different Plans can be used to implement rate limits. A rate limit can be implemented as a default rate across an entire Plan, or for specific operations of an API within that Plan, exempting them from the Plan rate limit. Different Plans can have differing rate limits, both between operations and for the overall limit. Applying rate limits to Plans makes it easy to offer different levels of service to customers. For example, a "Demo Plan" might enforce a rate limit of 10 calls per minute while a "Full Plan" might permit up to 1000 calls per minute.

Finally, different Plans can be used to assign a billing cost. A Plan can be set as a free Plan, or as a Plan with billing. Plans with billing can be used with rate limits to set different levels of service to customers. For example, a "Demo Plan" might enforce a rate limit of 10 calls per minute for a cost of $5 per month, while a "Full Plan" might permit up to 1000 calls per minute for a cost of $20 per month.

Note: Applying a rate limit at the Plan level, creates a default rate limit that applies to each operation within the Plan. If you need to set specific rate limits for specific operations, you must set them within the operations themselves and this setting overrides the setting at the Plan level.

IBM API Connect also supports the implementation of multiple versions of Products. You can choose version numbers and use them to aid the development of your Products and Plans.

Note: The version for a Product is distinct from the version of any APIs that are contained in the associated Plans. Plans cannot themselves have their own version, they use the version of their parent Product.