vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud cr region-set global

ibmcloud cr images --include-ibm
* What tools can I use to build and push images?

 What tools can I use to build and push images? 

You can use Docker and non-Docker tools to build and push images to the registry. You can use non-Docker tools that support OCI container image A container image that is compliant with the OCI Image Format Specification format and protocol. To log in by using other clients, see [Accessing your namespaces interactively](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_interactive).
* How many namespaces can you have?

 How many namespaces can you have? 

You can have 100 registry namespaces A collection of repositories that store images in a registry. A namespace is associated with an IBM Cloud account, which can include multiple namespaces. in each region.
* Can I rename a namespace?

 Can I rename a namespace? 

You can't rename a namespace A collection of repositories that store images in a registry. A namespace is associated with an IBM Cloud account, which can include multiple namespaces.. If you want to change the name of the namespace, you must create a namespace with the new name and transfer its data. To transfer its data, you can copy the contents of the existing namespace into the namespace that you created.

If you don't want to transfer data manually, you can create a script for this action by using the [ibmcloud cr image-tag](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_tag) command. For example, you can use the following script, where <old_namespace> is the existing namespace and <new_namespace> is the namespace that you created:

IMAGES=$(icr images --restrict <old_namespace> --format "{{ .Repository }}:{{ .Tag }}")

for i in $IMAGES ; do
To find out whether a collection is being shared, open the My Projects page, and then complete the appropriate step for your deployment:



IBM Cloud Pak for Data

Click Collection usage and sharing.
IBM Cloud

Click Data usage and GDPR, and then review the Collection usage page.



Collections can be associated with a single project, shared by two or more projects, or not associated with any project.





 Reusing data from a collection 

When you share collections across multiple projects, the following resources are shared:



* The processed data
* Configured connector



If you make any of the following changes to a shared collection, the changes are applied to the collection in every project where it is shared:



* Changing the Optical Character Recognition (OCR) setting
* Annotating fields or adding fields by using Smart Document Understanding
* Enabling or disabling fields
* Changing the setting for document splitting
* Changing any of the connector settings



Enrichments and improvement tool settings are not included when a collection is shared because they are set at the project level.

For more information about the other tabs, see the following topics:



* GDPR data label

IBM Cloud

: For more information about GDPR and labeling data, see [European Union General Data Protection Regulation (GDPR)](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-information-securitygdpr).
* API usage

IBM Cloud Pak for Data

For more information about monitoring Analyze API usage, see [Monitoring usage](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-analyzeapiapi-usage).







 Deleting collections 

Find out whether a collection is being used anywhere before you delete it from the Collection usage page. Unshared collections can be deleted directly from this page.



* To delete a single collection from a project, open the Manage collections page from the navigation panel, find the collection tile, and then click the delete icon.

Decide whether to keep the underlying data and configuration settings. If you choose to keep the data, you can find the collection in the unshared list on the Collection usage page.
In this release, you can:



* Create a file share.
* Mount a file share to one or multiple virtual server instances across multiple VPCs within the same zone or across zones.
* Restrict access to a specific virtual server instance when mounting a file share by using security groups.
* Enable end-to-end encryption in transit for file share data.
* Delete a file share.
* Delete all mount targets or delete a single mount target. When you delete one or several mount targets, the instances that are mounting the file share for the VPCs where the mount target is deleted can't access the file share.
* List file shares and mount targets.
* Update file share and mount target name.
* Create replication between the source file share and a replica file share.
* Fail over to a replica file share when the source share is compromised. Fall back to the original share when the issue is resolved.
* Add, manage, and delete file share user tags. Create and manage access management tags.



* Who do I contact to help with any issues? What information do I need to provide?

 Who do I contact to help with any issues? What information do I need to provide? 

For more information about who to contact, see [Getting help and support](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-help). Provide as much information as you can, including error messages, screen captures, and API error codes and responses. Include any messages from the VPC and the file storage service.
* Can I mount the same file share in different zones in my region?

 Can I mount the same file share in different zones in my region? 

Yes, you can mount file shares across different zones in your region.
* Can I mount file shares for my Kube containers?

 Can I mount file shares for my Kube containers? 

Yes. You can mount file shares by using the NFSv4.1 protocol.
* Can I mount same file shares between two virtual server instances?

 Can I mount same file shares between two virtual server instances? 

Yes, when the virtual server instances are in the same region.
Previewing and sharing your assistant 

Internal review is a necessary step in any virtual assistant workflow. You need an environment without customer interactions so your team can test your assistant. The draft environment closely resembles the final experience that your users encounter so you can ensure that you are publishing the optimal end product.



 Saving and editing your work in the draft environment 

The draft environment contains all your in-progress work in the Actions, Preview, and Publish pages. Use the Draft environment tab to manage the draft environment, including adding draft environment integrations (channels and extensions) that you can use for internal testing before deployment. These integrations are unique to the draft environment, and changes to draft integrations don't affect the live environment.





 The Preview page 

Use the Preview page to test your assistant. You can experience your assistant from your customers' perspective. The Preview page includes an interactive web chat widget where you can test out your assistant as if you were a customer. The content that is contained in the assistant is the content that you built into your actions or set up with the search integration.

On the Preview page, you also find the following elements:



* Copy link to share: Share an unauthenticated version of your assistant with your colleagues by sending them a link. For more information, see [Copying a link to share](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-preview-sharepreview-share-link).
* Change background: Change the background of the page so you can see what your assistant looks like on different web pages. For more information, see [Changing background website](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-preview-sharepreview-change-background).
* Customize web chat: Customize your draft web chat channel to match your brand or website. For more information, see [Web chat setup overview](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-web-chat-config).



!
This documentation is for the classic Watson Assistant experience. To see the documentation for the new Watson Assistant, please go [here](https://cloud.ibm.com/docs/watson-assistant).



 Integrating with Zendesk 

Integrate your web chat with a Zendesk service desk solution so your customers always get the help they need.

Integrate with a Zendesk service desk by deploying your assistant with the web chat integration. The web chat serves as the client interface for your assistant. If, in the course of a conversation with your assistant, a customer asks to speak to a person, you can transfer the conversation directly to a Zendesk agent.

Zendesk Chat lets you help customers in real time, which increases customer satisfaction. And satisfied customers are happier customers. To learn more about this service desk solution, see the [Zendesk website](https://www.zendesk.com/chat/).

Zendesk Chat is an add-on to Zendesk Support. Zendesk Support puts all your customer support interactions in one place, so communication is seamless, personal, and efficient, which means more productive agents and satisfied customers.



 Before you begin 



1. You must have a Zendesk account. If not, create one.

A Zendesk Chat Enterprise plan is required.
2. Decide whether you want to enable security.

If you choose to enable security in Zendesk, you must collect the name and email address of each user. This information must be passed to the web chat so it can be provided to Zendesk when the conversation is transferred.







 Setting up the Zendesk service desk connection 

To set up a Zendesk service desk integration, complete the following steps:



1. Create a web chat integration. For more information, see [Integrating the web chat with your website](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-web-chat).
2. From the web chat integration page in Watson Assistant, set the Allow transfers to live agents switch to On, and then choose Zendesk as the service desk type, and then click Next.
3.
Guiding customers with journeys ![BETA](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/beta.png) 

A journey is an interactive response that you can use to guide your customers through a complex task, or to give them a tour of new features, taking advantage of capabilities your website already supports. A journey is a multipart response that can combine text, video, and images presented in sequence.

This beta feature is available for evaluation and testing purposes but should not be used in production environments. Journeys require web chat version 6.9.0 or later.

When the customer starts a journey, the chat window temporarily closes. The web chat integration then presents the journey elements one step at a time in a small window superimposed over your website, enabling your customers to navigate and use the website as they step through the journey. At any time during the journey, the customer can freely return to the assistant chat window and then resume the journey.

![Image showing examples of journey](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/journeys_example.png)

You might use a journey in situations like the following examples:



* Onboarding new customers to your product or website and showing them where everything is
* Providing customers with step-by-step guidance for a complex task, like filing a claim or creating an account
* Promoting sales opportunities in your product to target users during specific marketing opportunities, such as offering a new rewards program to customers who are concerned about expenses



For more information about deciding when and how to use journeys, see our [best practices guide](https://medium.com/ibm-watson/best-practices-for-watson-assistant-journeys-993d16fb0ad0).



 Creating a journey 

A journey is defined using the user_defined response type, which is available only in the JSON editor.
: This release does not include the following features, which are available for cloud instances at the time of this release:



* Service desk support is not included.
* The phone integration is not supported.
* The actions skill is not available.
* The intent recommendations feature and the enhanced intent detection model are not supported.







 19 March 2021 

IBM Watson® Assistant 1.5.0 patch 1 is available
: For installations on IBM Cloud Pak® for Data 3.5, patch 1 includes configuration changes for FIPS compatibility and other fixes. See [Available patches for IBM Watson® Assistant for IBM Cloud Pak® for Data](https://www.ibm.com/support/pages/node/6240164)





 9 December 2020 

IBM Watson® Assistant for IBM Cloud Pak® for Data 1.5.0 is available
: Watson Assistant for IBM Cloud Pak® for Data 1.5.0 is compatible with IBM Cloud Pak® for Data 3.5 and IBM Cloud Pak® for Data 3.0.1 deployments on Red Hat OpenShift 4.6, 4.5, or 3.11. See the [support matrix](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-installinstall-support-matrix) for more details.

IBM Watson® Assistant for IBM Cloud Pak® for Data 1.5.0 is available
: Watson Assistant for IBM Cloud Pak® for Data 1.5.0 is compatible with IBM Cloud Pak® for Data 3.5 and IBM Cloud Pak® for Data 3.0.1 deployments on Red Hat OpenShift 4.5 or 3.11.

Access conversation logs and metrics
: An Analytics page is now available. From this page, you can see conversation logs and metrics that give you insights, such as what topics your customers are asking about and how often the assistant succeeds in addressing customer requests. For more information, see [Metrics overview](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-logs-overview).

Introducing the Web chat integration
: Deploy your assistant in minutes. Create a web chat integration to embed your assistant into a page on your website as a chat widget.
[GIF of how to delete a channel](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/delete-channel.gif)

If you deployed your assistant to a channel, then deleting the channel does not remove the assistant from the channel. For example, if you deploy web chat, you paste the JavaScript snippet into the HTML header of your website. Deleting your channel disconnects your content from the customer experience that is shown on your website. Be sure to remove the JavaScript snippet before you delete the channel.

Deleting a channel is final and deletes the channel from all environments. Think twice before you delete an integration because each new integration that you might add starts with default settings. If you delete your channel and then decide you want it back in a previous state, you must rebuild the channel after you add it back.
Deploying the deployable architecture can take more than an hour. You are notified when the deployment is successful.

The Output tab populates a website URL in addition to other values. Copy the website URL and paste it into your browser to view the website that is created from your configuration.



During the validation and deployment process, monitor the [needs attention items](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-needs-attention-projects). The widget reflects any issue that occurs in your configurations.
To publish new changes from the draft environment to an environment:



1. If changes are available to publish, click Publish.
2. Enter a description of the version.
3. Choose an environment.
4. Click Publish.



To publish an existing version to an environment:



1. On the Environments page, click the environment tab.
2. In Resolution Methods, click Switch version.
3. Choose a version to publish, then click Switch version.





 Moving a version through multiple environments 

This example explains moving a content version through multiple environments to build, test, iterate, and deploy.



Example

 Environment Activity 

 Draft Publish version V3 to Review environment 
 Review Conduct initial testing of V3 
 Test Switch to version V3 for further testing with a configured channel 
 Staging Switch to version V3 for testing with an internal staging website 
 Live Switch to version V3 for customer use 
 Live Switch to version V2 after a bug is found in version V3 
 Draft Revert to version V3 to fix the bug. For more information, see [Reverting to a previous version](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publishpublish-revert) 
 Draft Publish version V4 to Review environment for retesting 
 Test Switch to version V4 for further retesting 
 Staging Switch to version V4 for testing with an internal staging website 
 Live Switch to version V4 for customer use 









 Previewing an environment 

On each environment tab, you can click Preview this environment to open another browser tab and preview your assistant as an interactive web chat widget.

Zoom

![Preview](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/multiple-env-preview.png)

Preview

You can share this unauthenticated version of your assistant with your team by sending them the link to the environment preview.
Variable A variable is data that a customer shares with the assistant, which is collected and saved so it can be referenced later. In actions, you can collect action and session variables. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-manage-infoaction-variables-and-session-variables). 
 Web chat A channel that you can use to embed your assistant in your company website. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-web-chat). 
 Webhook A mechanism for calling out to an external program during a conversation. For example, your assistant can call an external service to translate a string from English to French and back again in the course of the conversation. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-webhook-overview).
A TLS certificate is necessary to create a TLS connection with a website and comprises the domain name, the name of the company, and additional data, such as company address, city, state, and country. The certificate also shows the expiration date and details of the issuing Certificate Authority (CA).
* How Does TLS Work?

When a browser initiates a connection with a TLS secured website, it first retrieves the site's TLS Certificate to check whether the certificate is still valid. It verifies that the CA is one that the browser trusts, and that the certificate is being used by the website for which it has been issued. If any of these checks fail, you'll get a warning indicating that the website is not secured by a valid certificate.

When a TLS certificate is installed on a web server, it enables a secure connection between the web server and the browser that connects to it. The website's URL is prefixed with "HTTPS" instead of "HTTP" and a padlock is shown on the address bar. If the website uses an extended validation (EV) certificate, the browser might also show a green address bar.
* Why do I see a privacy warning?

The TLS certificates issued by IBM Cloud CIS cover the root domain (example.com) and one level of subdomain (.example.com). If you’re trying to reach a second-level subdomain (..example.com) a privacy warning appears in your browser, because these host names are not added to the SAN.

Allow up to 15 minutes for one of our partner Certificates Authorities (CAs) to issue a new certificate. A privacy warning appears in your browser if your new certificate has not yet been issued.
* Why do I see invalid SSL certificate error?

If you see "Error 526, Invalid SSL Certificate" when visiting your site, it might mean your origin certificate is invalid. When the CIS proxy is enabled, a valid CA-signed certificate is required at the origin in the default SSL mode, which is "End-to-end CA Signed". Note that the default setting for the SSL mode was previously "End-to-end Flexible", which ignores the validity of certificates presented by the origin.
Their web content is served from an Edge server, which is located in the geographic area closest to the customer who requests the content. This technique lets the users receive the content with less delay than we might achieve by delivering the content from one centralized location. It delivers a better overall experience for your customers.
* How does a Content Delivery Network (CDN) work?

A CDN achieves its purpose by caching web content on Edge servers around the world. When a user requests web content, the content request is routed to the Edge server that is geographically closest to that user. By reducing the distance that the content must travel, the CDN offers optimized throughput, minimized latency, and increased performance.
* Where do I find cost estimates for CDN?

You can estimate the cost of a service using the cost estimator on the provisioning pages for CDN offerings. For example, log in to the [IBM Cloud Content Delivery Network](https://cloud.ibm.com/catalog/infrastructure/cdn-powered-by-akamai) console and click Create. As you complete the ordering form, cost estimates appear in the Summary side panel.
* How is my IBM Cloud® Content Delivery Network service account created?

Your account is created during the CDN ordering process. If you are creating a CDN from the legacy portal, when you click the Order CDN button, under the Network > CDN page, your account is created. If you are creating a CDN from the IBM Cloud portal, when you click the Create button, under the Catalog > Network > Content Delivery Network page, your account is created.
* What do I do when my CDN is in CNAME configuration status?

For HTTP and SAN certificate-based HTTPS CDN, update your DNS record so that your website points to the CNAME associated with your new CDN mapping.

For wildcard, certificate-based HTTPS CDN, this DNS update is not needed because you access the website through https://<CNAME>. You can refresh your CDN status by clicking Get status from the menu of your CDN instance.

It can take up to 15 - 30 minutes for the update to take effect. Check with your DNS provider to obtain an accurate time estimate.
Web crawl 

Add a web crawl collection to crawl a website, analyze its page content, and store meaningful information. Specify one or more base web page URLs and configure how many linked pages for the web crawl to follow. You can configure how often to synchronize with the website, so you control how up to date the data in your collection is.

IBM Cloud

IBM Cloud only

This information applies only to managed deployments. For more information about connecting to a website from an installed deployment, see [Web crawl](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-web-cp4d).



 What documents are crawled 

You can connect to the following types of web content:



* Public websites
* Private company websites or other sites that require authentication
* Websites that are behind a corporate firewall



During the initial crawl of the content, all website pages that match your search settings are crawled and added to the document index of your collection. The crawl starts on the web page that you specify in the Starting URLs field. If your collection is configured to follow links, the crawl follows links on the starting page that share the same subtree as the starting page. For example, if you specify https://www.example.com/banking/faqs.html, links with URLs that begin with https://www.example.com/banking/ are crawled. If you specify https://www.example.com/banking, links with URLs that begin with https://www.example.com/ are crawled.

The crawl cannot access secure subdirectories. For example, if a subdirectory that you expect the crawl to access, such as https://www.example.com/banking/pdfs, isn't being crawled, check whether you can access the subdirectory URL from a web browser directly. If you can't access it, the crawl can't access it.

During subsequent scheduled recrawls, a full recrawl is performed and any changes are reflected in your collection.