vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Migrating to the new experience 

If you are using an older product instance, you might still be using the classic Watson Assistant experience. To take advantage of the latest features, consider switching to the new experience.

You can freely switch which experience you see without losing any of your work or affecting other users of the instance.

For more information about how to switch between the classic experience and the new experience, see [Switching the experience](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-welcome-new-assistantwelcome-new-assistant-switch-experience).

Consider the following questions to decide which experience you want to use:

Do you want to build a new actions-based assistant?
:   The new experience provides a simplified user interface that was designed around actions, as well as an improved [deployment process](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish-overview). If you plan to build an actions-based assistant, use the new experience for access to the latest features and improvements.

Are you working on an existing assistant built in the classic Watson Assistant?
:   If you have a dialog-based assistant that was built using the classic Watson Assistant, and you are not currently planning to migrate to an actions-based assistant, you might still want to consider migrating it to the new experience so you can take advantage of the new process for publishing and deploying your assistant. Migrating to the new experience also makes it easy for you to begin using actions when you are ready.

For more information about how to migrate a dialog-based assistant to the new experience, see [Activating dialog and migrating skills](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-activate-dialog).

Do you want to convert an existing dialog-based assistant to use actions?
:   If you have a dialog-based assistant, but you want to reimplement it to use actions instead, start by migrating it to the new experience. You can then start using actions alongside your dialog, and you can replace your dialog nodes with actions at your own pace.

For more information about using a dialog with actions, see [Calling actions from a dialog](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-dialog-call-action).
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/icon_hamburger.svg). Then, select Observability to access the Observability dashboard.
3. Select Activity Tracker, then click Create instance.
4. Enter a name for the service instance.
5. Select the [location](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-regions) where you plan to provision the instance.
6. Select a resource group.

By default, the Default resource group is set.

Note: If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.
7. Select the Lite service plan.

By default, the lite plan is set.
8. Click Create.



After you provision an instance, the Activity Tracker dashboard opens.

Next, go to the web UI to view the events in your account. [Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-view_events).





 Provisioning an instance through the catalog 

To provision an instance of IBM Cloud Activity Tracker through the IBM Cloud catalog, complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud UI opens.
2. Click Catalog. The list of the services that are available in IBM Cloud opens.
3. To filter the list of services that is displayed, select the Logging and Monitoring category.
4. Click the IBM Cloud Activity Tracker tile.
5. Enter a name for the service instance.
6. Select the location where you plan to provision the 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).
* 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/docs/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 more information, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs&interface=ui).







You cannot directly downgrade from one plan to another. If you want to move from an Enterprise plan to a Plus plan, for example, you must provision a new Plus plan and then move data to it from your existing Enterprise plan. After the data is moved, you can delete the Enterprise plan. For more information about how to back up data that you want to move between service instances, see [High availability and disaster recovery](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-recovery).

For more information about plans, see [Discovery pricing plans](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-pricing-plans).
If you have a billable account, you can access your invoice by clicking Manage > Billing and usage, and selecting Invoices. If you have a Lite account, you don't have an invoice because you're never charged for Lite plan usage.

You might be redirected to [IBM Invoices website](https://www.ibm.com/invoices). See [How do I view invoices for Pay-As-You-Go or Subscription accounts?](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-ts_cant-view-invoice) and [Viewing your invoices](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-managing-invoices) for more information.
* Why does my usage not match my invoice?

Your usage might not match your invoice because the months that are used to compare usage aren't the same, or the total amount of the orgs wasn't selected. For more information, see [Viewing your usage](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-viewingusage). If it still doesn't match, get in touch with us by calling 1-866-325-0045 and choosing the third option, or by opening a [support case](https://cloud.ibm.com/unifiedsupport/supportcenter).
* Why can't I manage my invoices?

You might not have the correct permissions. Ask your account owner to add you to the View account summary access group. For more information, see [Managing migrated SoftLayer account permissions](https://cloud.ibm.com/docs/account?topic=account-migrated_permissions).
* How can I download my invoice?

To download your invoice, go to Manage > Billing and usage, and select Invoices. Then, click the Download icon ![Download icon](https://cloud.ibm.com/icons/download.svg) and choose an invoice format.
The most common such situation is transferring a conversation to the web chat integration, to take advantage of web chat features such as service desk integration. For more information, see [Adding a Channel transfer response type](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-overviewdialog-overview-add-channel-transfer).

Intercom and WhatsApp integrations now available in Lite plan
: The integrations for Intercom and WhatsApp are now available in the Lite plan for Watson Assistant. For more information, see [Integrating with Intercom](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-intercom) and [Integrating with WhatsApp](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-whatsapp).





 16 March 2021 

Session history now generally available
: Session history allows your web chats to maintain conversation history and context when users refresh a page or change to a different page on the same website. It is enabled by default. For more information about this feature, see [Session history](https://web-chat.global.assistant.watson.cloud.ibm.com/docs.html?to=tutorials-session-history).

Session history persists within only one browser tab, not across multiple tabs. The dialog provides an option for links to open in a new tab or the same tab. See [this example](https://web-chat.global.assistant.watson.cloud.ibm.com/docs.html?to=tutorials-session-historyTutorial1) for more information on how to format links to open in the same tab.

Session history saves changes that are made to messages with the [pre:receive event](https://web-chat.global.assistant.watson.cloud.ibm.com/docs.html?to=api-eventsprereceive) so that messages still look the same on rerender. This data is only saved for the length of the session.
You can trigger a search of the existing material in real time to get the latest and most up-to-date answer for your customers.

To use the search skill response type, you must create a search skill and add it to the same assistant that uses this dialog skill. For more information, see [Creating a search skill](https://cloud.ibm.com/docs/assistant?topic=assistant-skill-search-add).

To add a Search skill response type, complete the following steps:



1. From the dialog node where you want to add the response type, click the dropdown menu in the Assistant responds field, and then choose Search skill.

Indicates that you want to search an external data source for a relevant response.
2. To edit the search query to pass to the Discovery service, click Customize, and then fill in the following fields:



* Query: Optional. You can specify a specific query in natural language to pass to Discovery. If you do not add a query, then the customer's exact input text is passed as the query.

For example, you can specify What cities do you fly to?. This query value is passed to Discovery as a search query. Discovery uses natural language understanding to understand the query and to find an answer or relevant information about the subject in the data collection that is configured for the search skill.

You can include specific information provided by the user by referencing entities that were detected in the user's input as part of the query. For example, Tell me about @product. Or you can reference a context variable, such as Do you have flights to $destination?. Just be sure to design your dialog such that the search is not triggered unless any entities or context variables that you reference in the query have been set to valid values.

This field is equivalent to the Discovery natural_language_query parameter. For more information, see [Query parameters](https://cloud.ibm.com/docs/discovery?topic=discovery-query-parametersnlq).



* Filter: Optional. Specify a text string that defines information that must be present in any of the search results that are returned.
* The Discovery News is part of the system environment and cannot be included in multiple collection queries.
* Individual collection relevancy training does not affect ranking of results when querying multiple collections. To rerank results returned when querying multiple collections implement [Continuous Relevancy Training](https://cloud.ibm.com/docs/discovery?topic=discovery-crt).
* Reranking is not performed on any part of a multiple collection query, even if all collections in the query are trained.



See the [multiple collection query API reference](https://cloud.ibm.com/apidocs/discoveryquery-documents-in-multiple-collections) for more information.

You can view notices across multiple collections in the same environment by using the environments/{environment_id}/notices API method.



* The collection_ids parameter must be specified when using this method. collection_ids is a comma-separated list of collections in the environment to query.
* passages are supported when querying multiple collections.



See the [multiple collection notices API reference](https://cloud.ibm.com/apidocs/discoveryget-collection-details) for more information.

You can view the fields available across collections in the same environment by using the environments/{environment_id}/fields API method. See the [multiple collection field query API reference](https://cloud.ibm.com/apidocs/discoverylist-fields-across-collections) for more information.





 Query expansion 

You can expand the scope of a query beyond exact matches - for example, you can expand a query for "ibm" to include "international business machines" and "big blue" - by uploading a list of query expansion terms. Query expansion terms are usually synonyms, antonyms, or typical misspellings for common terms.

You can define two types of expansions:



* bidirectional - each expanded_term expands to include all expanded terms. For example, a query for ibm expands to ibm OR international business machines OR big blue).
* unidirectional - the input_terms in the query are replaced by the expanded_terms. For example, a query for banana could expand to plantain and fruit.
If you reach the plan limit of versions you can have, you need to delete a version before you can publish another one.



Service plan published versions

 Service plan Published versions 

 Enterprise 50 
 Premium (legacy) 50 
 Plus 10 
 Trial 10 
 Lite 2 







 The live environment 

Use the Live environment tab to manage the live environment. This tab indicates which content is live in the assistant and which channels that content is connected to. The left side of the tab displays the channels where content is deployed, or where customers can interact with the assistant. The right side of the tab displays the resolution methods, or how the assistant responds to customer questions or requests.

Zoom

![Live environment](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/live-environment-page.png)

Live environment

Resolution Methods shows the content version that is published to the live environment.

There are two ways to publish a version to the live environment:



* When you publish a version from the draft environment
* Use the Live environment tab and click Publish version.



After a version is published to the live environment, there are two ways you can switch to a different version:



* When you publish a version from the draft environment, you have the option of assigning it to the live environment, replacing the one that's already there
* Use the Live environment tab and click Switch version.



For more information about publishing, see [Publishing your content](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish).





 Environment settings 

The draft and live environments each have settings. On either tab, click the Settings gear icon to open the settings.

API details provide these values for each environment:



* Environment name
* Environment ID
* Session URL



Webhooks

Settings for pre-message, post-message, and log webhooks.
When you have both production and DR on the same provider, your risk condition is increased and must be carefully considered.





 Having only a plan A 

Risks can't be eliminated; they can be only mitigated. The more risk that you mitigate with a single solution, the more the solution would cost. Thus, any solutions have a residual risk, as budget for disaster recovery is normally a finite or limited number.

Having a plan B with a different

recovery time objective(RTO) might help to mitigate additional risks, like increased resiliency and not add too much cost to the budget.

Your plan B RTO might not be the one expected in plan A, meaning you will need more time to restart your operations, and thus you will have more economic impact by the emergency. But, restarting later might be far better than not restarting at all.

A possible plan B, in a two sites topology, might include a periodic backup that is secured off-site from the two sites and at a distance to be considered reasonably safe.





 Preparing a poor DR testing methodology 

An untested DR solution is like running blindfolded in the woods. There are high chances that you will encounter an obstacle that stops your running. Moreover, you discover that only during the most important run of your life.

If testing is essential to guarantee that you have a valid solution, then the conditions you are going to test are also important.

If you plan to perform a DR test by doing a planned close of operation on one site and a well-organized restart on the other, you are sure your DR tests works, but is this what will happen during an emergency?

You should design your tests to mimic the potential emergency conditions as closely as possible by simulating a so-called “rolling disaster condition”, where your IT service is impacted progressively by the emergency. This is the best way to test your solution and have a reasonable understanding if it is resilient and has the ability to resist stress conditions.

Testing is one of the most important activities in the disaster recovery process but often hard to complete in the proper manner on public cloud. Because of the standardized nature of the cloud, you can't take for granted the ability to run testing as you need when using on-demand resources, for example:
If there is no guideline, consider starting one. The first entry can address the question you are debating now, and can describe the resolution that you come to. This entry will save time for the next human annotator who stumbles upon the same issue.
* Discuss the question with other human annotators involved in the workspace, and try to decide together on the optimal solution. This type of discussion is expected and beneficial to the workspace overall. It will encourage you to all follow the same methodology as you annotate the documents.







 Related information 

[Annotating documents](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-user-guide)

[Dictionaries](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-dictionaries)

[Type systems](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-typesystem)
Using the Discovery v1 API 

IBM Watson™ Discovery v1 is deprecated. As of 1 October 2021, you cannot create new v1 instances. Lite or Advanced plan service instances are Discovery v1 instances, as are service instances that you created with a Premium plan before 16 July 2020. Existing v1 service instances are supported until 11 July 2023. Any v1 instances that still exist on that date will be deleted. Migrate your solutions to use Discovery v2 before 11 July 2023. For more information, see the [Discovery v2 documentation](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-version-choose).

In this short tutorial, we introduce the Discovery v1 API and go through the process of creating a private data collection and searching it.

If you prefer to work in the Discovery tooling, see [Getting started with Discovery v1](https://cloud.ibm.com/docs/discovery?topic=discovery-getting-started).



 Before you begin 



1. Create an instance of the service:



1. Go to the [Discovery](https://cloud.ibm.com/catalog/services/discovery) page in the catalog.

The service instance is created in the default resource group if you do not choose a different one, and it cannot be changed later. This group is sufficient for the purposes of trying out the service. If you're creating an instance for more robust use, then learn more about [resource groups](https://cloud.ibm.com/docs/resources/bestpractice_rgs.htmlbp_resourcegroups)
2. Sign up for a free IBM Cloud account or log in.
3. Click Create.

A Discovery service instance is created and a summary page is displayed.



2. Copy the credentials to authenticate to your service instance:



1. Click Show credentials.
2. Copy the API key and URL values.



3. Make sure that you have the curl command.



* Test whether curl is installed. Run the following command on the command line.
Select a pricing plan - Based on your business requirements, select a pricing plan: Lite, and Standard.
4. Configure your resource by providing a Service name for your instance, or use the preset name.
5. Select a resource group - The resource group selection helps how you want resources to be organized in your account. The resource group that you select cannot be changed after the service instance is created.
6. Optionally, define Tags to help you to identify and organize the instance in your account. If your tags are billing related, consider writing tags as key:value pairs to help group-related tags, such as costctr:124.
7. Optionally, define Access management tags that are required to apply flexible access policies on specific resources. For example, access:dev, proj:version-1.
8. For the Service endpoints, from the list of endpoint options, select Both public & private network.

By default, Event Notifications instances accept API requests from both public and private endpoints.
9. Accept the licensing agreements and terms by clicking the checkbox.
10. Click Create. A new service instance is created and the Event Notifications console displayed.







 Viewing your endpoint URLs 

The service endpoint URLs are different for private and public network connections. For more information about your service endpoint URLs, see [Regions and endpoints](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-regions-endpoints).
Next steps 

From the logging Web UI, you can view your logs as they pass through the system. You view logs by using log tailing.For more information, see [Viewing logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs).

With the Free service plan, you can only tail your latest logs.

Try out the following additional features:



* [Filtering logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step5)
* [Searching logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step6)
* [Defining views](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step7)
* [Configuring alerts](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-alerts).



To use any of these features, you must upgrade the IBM Log Analysis plan to a paid plan.