vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Migration to Standard Next plans 

To migrate from your current Standard plan to a Standard Next plan, take the following steps.



1. Enter your existing CIS instance
2. Navigate to the Plan page in left side panel
3. Select Standard Next plan
4. Check the box to acknowledge the terms and conditions
5. Click Create and follow any prompts that might block this plan change









 Transitioning to Enterprise Tier plans 

Starting 31 August 2023, the current CIS Enterprise Package, Enterprise GLB, and Enterprise Security plans will no longer be available for new instances. Any instance that is created on or after this date will use the new Enterprise Tier plans.

By moving to a more metered model, the base cost of the Enterprise Tier plans are smaller than the original Enterprise plans. The following table shows what features are available in the Enterprise Tier plans.



Table 2. Comparison of CIS Enterprise Tier plans

 Features Enterprise Essential Enterprise Advanced Enterprise Premier 

 Included domains 1 2 2 
 Included DNS records 3500 3500 3500 
 Protected traffic included (DDoS, CDN, DNS, WAF, GLB) 5 TB 5 TB 5 TB 
 Requests included (CDN, WAF, GLB) in millions 150 150 150 
 Custom uploaded certificates 25 25 25 
 GLB: Origins, pools, GLB included 20 20 20 
 Range (Layer 3/4) No Yes Yes 
 Advanced rate limiting No Yes Yes 
 Advanced WAF No Yes Yes 
 Bot management No No Yes 





 Migration to Enterprise Tiers plans 

To migrate from your current Enterprise Package, Enterprise GLB, and Enterprise Security plans, take the following steps.



1. Enter your existing CIS instance
2. Navigate to the Plan page in left side panel
3. Select desired Enterprise Tier plan
4. Check the box to acknowledge the terms and conditions
5. Click Create and follow any prompts that might block this plan change
To update your app, you can choose from various strategies such as the following. You might start with a rolling deployment or instantaneous switch before you progress to a more complicated canary deployment.

Rolling deployment
: You can use Kubernetes-native functionality to create a v2 deployment and to gradually replace your previous v1 deployment. This approach requires that apps are compatible with earlier version so that users who are served the v2 app version don't experience any breaking changes. For more information, see [Managing rolling deployments to update your apps](https://cloud.ibm.com/docs/containers?topic=containers-update_appapp_rolling).

Instantaneous switch
: Also referred to as a blue-green deployment, an instantaneous switch requires double the compute resources to have two versions of an app running at once. With this approach, you can switch your users to the newer version in near real time. Make sure that you use service label selectors (such as version: green and version: blue) to make sure that requests are sent to the correct app version. You can create the new version: green deployment, wait until it is ready, and then delete the version: blue deployment. Or you can perform a [rolling update](https://cloud.ibm.com/docs/containers?topic=containers-update_appapp_rolling), but set the maxUnavailable parameter to 0% and the maxSurge parameter to 100%.

Canary or A/B deployment
: A more complex update strategy, a canary deployment is when you pick a percentage of users such as 5% and send them to the new app version. You collect metrics in your logging and monitoring tools on how the new app version performs, do A/B testing, and then roll out the update to more users. As with all deployments, labeling the app (such as version: stable and version: canary) is critical.
For more information about the different types of queries and how to decide which one to use, see [Choosing the right query type](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-conceptsquery-choose).



Knowledge Studio



* How do I set data collection options?

For Lite and Standard plans, by default, Knowledge Studio uses client data to improve the service. This data is used only in aggregate. Client data is not shared or made public.

To prevent Knowledge Studio from using client data, you must opt out by using at least one of two ways:



* Clear the Data collection checkbox on the Service Details page in the Knowledge Studio application.
* As the owner of the Knowledge Studio service instance, opt out of all data collection for Watson services at /watson/settings.



For Premium plans and Dedicated accounts, Knowledge Studio does not use client data to improve the service.

For more information, see the latest [Knowledge Studio service description](https://www.ibm.com/software/sla/sladb.nsf/searchsaas/?searchview&searchorder=4&searchmax=0&query=Knowledge+Studio).
* Can I deploy custom models across regions?

Deployment of models across regions is not supported. A custom model can only be deployed to the same region as your Knowledge Studio instance.
* Can I access Knowledge Studio with an API?

At this time, there is no API to interact with Knowledge Studio. To launch the Knowledge Studio application, you click Launch tool from within the Manage page for the Knowledge Studio service instance in the IBM Cloud console. Or you can copy the tool URL and use it to launch the application directly. For details, see [Launching the Knowledge Studio application](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks_tutintrolaunching-the-knowledge-studio-application).
* Can I change from a Standard to Lite plan?

Downgrading your plan for Knowledge Studio is not supported. You can, however, manage users, storage, billing, and usage with options such as setting limits or notifications.
* The following file types can be ingested by Discovery, all other document types are ignored:





 Lite plans Advanced plans 

 PDF, Word, PowerPoint, Excel, JSON*, HTML* PDF, Word, PowerPoint, Excel, PNG**, TIFF**, JPG**, JSON*, HTML* 



* JSON and HTML documents are supported by IBM Watson™ Discovery, but can not be edited using the SDU editor. To change the configuration of HTML and JSON docs, you need to use the API. For more information, see the [API reference](https://cloud.ibm.com/apidocs/discovery/).

** Individual image files (PNG, TIFF, JPG) are scanned and the text (if any) is extracted. PNG, TIFF, and JPEG images embedded in PDF, Word, PowerPoint, and Excel files are also scanned and the text (if any) extracted.



* You cannot specify the data type (For example: text or date) of fields. During document ingestion, if a field is detected that does not yet exist in the index, Discovery automatically detects the data type of that field based on the value of the field for the first document indexed.
* A document can fail to be ingested because of a type mismatch between data in the current document and similar data in a previously ingested document. For example, a field might be typed as a date in one document and a string in a subsequent document, preventing the subsequent document from being indexed correctly.
* If you plan to use custom tokenization (currently only available for Japanese collections when using the Discovery API), the tokenization dictionary for your collection must be added before uploading documents.







 Uploading documents with the Discovery tooling 



1. Create a collection. See [Preparing the service for your documents](https://cloud.ibm.com/docs/discovery?topic=discovery-configservicepreparing-the-service-for-your-documents).
2. Click on the collection to open it.
3. Click the Upload documents button and start uploading your documents via drag and drop or browse.
The Watson Assistant chart requires Etcd version 3 with enabled authorization.



 LiteLinks service discovery 

The Dialog, NLU, Master, TAS, and ED-MM microservices act as LiteLinks servers. Each LiteLinks server is registered in Etcd with its own key under the /bluegoat/litelinks/ path. Each pod stores its metadata, such as its IP address and port, into Etcd. For example, the Dialog microservice pod with IP address 10.131.2.25 might register itself under a key named /bluegoat/litelinks/voyager-dialog-slot-${release-name}/10.128.0.231_8089_16ea2cde43f.

The ${release-name} is watson-assistant.

The Store, NLU, Master, TAS, and ED-MM microservices are LiteLinks clients. (Some microservices function as both a server and client.) Each LiteLinks client reads these Etcd keys and communicates directly with the registered pod IP address and port of the server. In effect, LiteLinks clients do not use the Kubernetes DNS. As a result, Kubernetes service objects are not used for LiteLinks servers. Without the Kubernetes service objects, the readiness probes are ignored even though they are good indicators of pod health.

The following table lists the key names for each LiteLinks server.



LiteLinks server Etcd paths

 Microservice LiteLinks server key name 

 Dialog voyager-dialog-slot-${release-name} 
 NLU voyager-nlu-slot-${release-name} 
 Master voyager-master-slot-${release-name} 
 TAS tas-runtime-slot-${release-name} 
 ED-MM ${release-name}-ed-mm 



Microservice pods that are either LiteLinks clients or servers contain an initContainer that, on pod creation, checks, and waits until Etcd is operational and contains configuration entries.





 Configuration storage
For more information about the different types of queries and how to decide which one to use, see [Choosing the right query type](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-conceptsquery-choose).



Knowledge Studio



* How do I set data collection options?

For Lite and Standard plans, by default, Knowledge Studio uses client data to improve the service. This data is used only in aggregate. Client data is not shared or made public.

To prevent Knowledge Studio from using client data, you must opt out by using at least one of two ways:



* Clear the Data collection checkbox on the Service Details page in the Knowledge Studio application.
* As the owner of the Knowledge Studio service instance, opt out of all data collection for Watson services at /watson/settings.



For Premium plans and Dedicated accounts, Knowledge Studio does not use client data to improve the service.

For more information, see the latest [Knowledge Studio service description](https://www.ibm.com/software/sla/sladb.nsf/searchsaas/?searchview&searchorder=4&searchmax=0&query=Knowledge+Studio).
* Can I deploy custom models across regions?

Deployment of models across regions is not supported. A custom model can only be deployed to the same region as your Knowledge Studio instance.
* Can I access Knowledge Studio with an API?

At this time, there is no API to interact with Knowledge Studio. To launch the Knowledge Studio application, you click Launch tool from within the Manage page for the Knowledge Studio service instance in the IBM Cloud console. Or you can copy the tool URL and use it to launch the application directly. For details, see [Launching the Knowledge Studio application](https://cloud.ibm.com/docs/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks_tutintrolaunching-the-knowledge-studio-application).
* Can I change from a Standard to Lite plan?

Downgrading your plan for Knowledge Studio is not supported. You can, however, manage users, storage, billing, and usage with options such as setting limits or notifications.
5. Under Time Frame, select the month you need.
6. Select your Plus plans or Plus Trial plans to see monthly active users and the API calls.



* Error: New Off Topic not supported

You see the error New Off Topic not supported after editing the JSON file for a dialog skill and changing the skill language from English to another language.

To resolve this issue, modify the JSON file by setting off_topic to false. For more information about this feature, see [Defining what's irrelevant](https://cloud.ibm.com/docs/assistant?topic=assistant-irrelevance-detection).
* Is it possible to increase the number of intents per skill

No, it is not possible to increase the number of intents per skill.



Discovery v1



* Where can I get technical support for Discovery?

If you cannot find a solution to the issue you are having, search this documentation. You can also try the resources available from the Developer community section of the table of contents.

If your service plan covers it, you can get help by creating a case from [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).
* How do you interpret the confidence score that appears in query results?

Discovery returns a confidence score for both natural language queries and those written in the Discovery Query Language. For more information, see [Confidence scores](https://cloud.ibm.com/docs/services/discovery?topic=discovery-improving-result-relevance-with-the-toolingconfidence).
* How do you integrate Watson Discovery with Watson Assistant?

If you create a chatbot in IBM Watson™ Assistant, you can route complex customer inquiries to Discovery using a search skill. When a customer asks a question that the dialog is not designed to answer, your assistant can search for relevant information from Discovery, extract the information, and return it as the response. See [Creating a search skill](https://cloud.ibm.com/docs/services/assistant?topic=assistant-skill-search-add) for details. (This feature is available only to Watson Assistant Plus or Premium plan users.)
For more information, see [Switching the experience](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-welcome-new-assistantwelcome-new-assistant-switch-experience).
* What happens when I switch between the classic and new Watson Assistant experiences?

 What happens when I switch between the classic and new Watson Assistant experiences? 

The assistants that you create in one experience don't transfer to the other. However, you can switch experiences, return to your work, and create or use assistants. You don't lose anything by switching. Changing experiences doesn't affect other users in the same instance. For more information, see [Switching the experience](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-welcome-new-assistantwelcome-new-assistant-switch-experience).
* Is the classic Watson Assistant experience going away?

 Is the classic Watson Assistant experience going away? 

IBM has no plans to discontinue the classic Watson Assistant experience. However, we encourage you to explore the benefits and capabilities in the new Watson Assistant. For more information, see the [Getting Started guide](https://www.ibm.com/blogs/watson/2021/12/getting-started-with-the-new-watson-assistant-part-i-the-build-guide/) or the [documentation](https://cloud.ibm.com/docs/watson-assistant) for the new experience.
* Where are the search skill and channel integrations in the new Watson Assistant experience?

 Where are the search skill and channel integrations in the new Watson Assistant experience? 

In the left navigation, click Integrations![Integrations](https://cloud.ibm.com/images/integrations-icon.png). On the Integrations page, you can add search, channel, and extension integrations to your assistant. For more information, see [Adding integrations](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-integration-add).
* Where is the Assistant ID found in the new product experience?
For example, you might want to show facets based on keywords or dictionary categories. For more information, see [Facets](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-facets).





 Explore other search features 

When you test your project from the Discovery user interface, you submit a natural language query. Search features are available that you can enable to influence how the natural language query search is done. And Discovery Query Language search is another type of search that you can leverage by using the API. If the initial results don't meet your needs, experiment with another search method.



* Discovery Query Language (DQL) search: A search mechanism that accepts more complex queries. You must use the query API to submit DQL queries.

For example, you can search for specific values in fields that are generated by enrichments that are applied to a collection.
* Natural language query is the type of search that is triggered from the Improve and customize page.



For more information about the Query API, see [Query API overview](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-concepts).
Managing the app lifecycle 

Use Kubernetes-native and third-party tools to perform rolling updates and rollbacks of apps without downtime for your users.



 Update strategies 

To update your app, you can choose from various strategies such as the following. You might start with a rolling deployment or instantaneous switch before you progress to a more complicated canary deployment.

Rolling deployment
: You can use Kubernetes-native functionality to create a v2 deployment and to gradually replace your previous v1 deployment. This approach requires that apps are backwards-compatible so that users who are served the v2 app version don't experience any breaking changes. For more information, see [Managing rolling deployments to update your apps](https://cloud.ibm.com/docs/containers?topic=containers-update_appapp_rolling).

Instantaneous switch
: Also referred to as a blue-green deployment, an instantaneous switch requires double the compute resources to have two versions of an app running at once. With this approach, you can switch your users to the newer version in near real time. Make sure that you use service label selectors (such as version: green and version: blue) to make sure that requests are sent to the correct app version. You can create the new version: green deployment, wait until it is ready, and then delete the version: blue deployment. Or you can perform a [rolling update](https://cloud.ibm.com/docs/containers?topic=containers-update_appapp_rolling), but set the maxUnavailable parameter to 0% and the maxSurge parameter to 100%.

Canary or A/B deployment
: A more complex update strategy, a canary deployment is when you pick a percentage of users such as 5% and send them to the new app version. You collect metrics in your logging and monitoring tools on how the new app version performs, do A/B testing, and then roll out the update to more users. As with all deployments, labeling the app (such as version: stable and version: canary) is critical.
When the answer-finding feature is enabled, Discovery also provides a "short answer" within the passage, and a confidence score to show whether the "short answer" answers the question that is explicit or implicit in the user query. Applications that use the answer-finding feature can display the short answer alone or can display the short answer emphasized in the context of the full passage. For most applications, displaying the short answer emphasized within the full passage is preferable, because answers generally make more sense in context.

The answer finding feature behaves in the following ways:

In the passage examples that follow, the short answers are shown in bold font.



* Finds answers. It doesn’t create answers. The answer must be part of the text; it can't be inferred.

“What was IBM’s revenue in 2022?” can get a correct answer if you have a document that states what IBM’s revenue was in 2022. However, if you have a document that lists what IBM’s revenue was in each quarter of 2022, it doesn't add them up and give you a total.
* Handles synonyms and lexical variations if the answer is available.



* Example question: “When did IBM purchase Red Hat?”
* Passage: “IBM closed its $34 billion acquisition of Red Hat in July of 2019."



* Combines information across multiple sentences if they are close together (within approximately 2,000 characters).



* Example question: “When did IBM purchase Red Hat?”
* Passage: “IBM acquired Red Hat for $34 billion. The deal closed in July of 2019."



* Handles implicit questions similar to the way it would handle the equivalent explicit question.

Example questions:



* company that developed the AS/400
* What company developed the AS/400?



* Works well with questions with longer phrase or clause answers.



* Example question: How do I flip a pancake?
* Passage: The key to getting a world-class pancake is flipping it properly. The best way to flip a pancake is to stick a spatula under it, lift it at least 4 inches in the air, and quickly rotate the spatula 180 degrees.



* Many how or why questions are only fully answered by much longer spans of text.
Getting help 

Frequently asked questions about Discovery.



 Where can I get technical support for Discovery? 

If you cannot find a solution to the issue you are having, search this documentation. You can also try the resources available from the Developer community section of the table of contents.

If your service plan covers it, you can get help by creating a case from [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 How do you interpret the confidence score that appears in query results? 

Discovery returns a confidence score for both natural language queries and those written in the Discovery Query Language. For more information, see [Confidence scores](https://cloud.ibm.com/docs/services/discovery?topic=discovery-improving-result-relevance-with-the-toolingconfidence).





 How do you integrate Watson Discovery with Watson Assistant? 

If you create a chatbot in IBM Watson™ Assistant, you can route complex customer inquiries to Discovery using a search skill. When a customer asks a question that the dialog is not designed to answer, your assistant can search for relevant information from Discovery, extract the information, and return it as the response. See [Creating a search skill](https://cloud.ibm.com/docs/services/assistant?topic=assistant-skill-search-add) for details. (This feature is available only to Watson Assistant Plus or Premium plan users.)





 What does the "Only one free environment is allowed per resource group" error message mean? 

If you have recently deleted a Lite instance and then receive a 400 - Only one free environment is allowed per resource group error message when creating a new environment in a new Lite instance, you need to finish deleting the original Lite instance. See [ibmcloud resource reclamations](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_reclamations) and follow the reclamation-delete instructions.





 Is there size limitation on the length of Natural Language Queries (NLQ)? 

The maximum query string length for a natural language query is 2048.