vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can also use the unrecognized request groups to identify existing actions that you might want to modify. You can:



* Add unrecognized requests as example phrases to existing actions
* Move example phrases from existing actions and add them to any new actions you create based on unrecognized requests



If a group lists related actions, you might focus on modifying them to address the unrecognized request.

Zoom

![Related actions](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-unrecognized-related-actions.png)

Related actions starts





 Downloading groups 

You can download all group data or individual group data in a CSV file.

To download all group data, click the Download groups icon on the Recognition page.

Zoom

![Download groups](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-unrecognized-download-groups.png)

Download groups

To download data for an individual group, open the group, then click the Download group icon.

Zoom

![Download group](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-unrecognized-download-group.png)

Download group

The CSV file includes this information:



Download group CSV file

 Column Description 

 Group The name of the unrecognized requests group 
 Example Each verbatim request in the group 
 Count The number of times the unrecognized request is included in this group 
 Group Id ID number for the group
Release notes for subnets and IPs 

Use these release notes to learn about the latest updates to subnets and IPs that are grouped by date.



  27 May 2021 

Link remediation
:   Removed obsolete links from the getting started and ordering topics.
Analyzing CSV files 

You can add the data that you want to analyze as a comma-separated value (CSV) formatted file.

The content mining project works well with CSV files. When your CSV file is ingested, each row in the spreadsheet is stored as a separate document in the collection index. Each column becomes a root-level field in the document.

Follow these guidelines when you create a CSV file for use in the project:



* Add each record that you want to analyze as a row in the spreadsheet.
* Include a column for each significant data point.
* Specify column headers.

The root-level field that is added to the document is given the column header name. If no header exists, hardcoded names, such as column_0 and column_1, are applied to the columns. Specify column names to ensure that the resulting document fields have meaningful names.
* If you want to find trends over time, be sure that each record has some date information that can be used to plot the information on a timeline.

Discovery recognizes the following date formats automatically:

yyyy-MM-dd'T'HH:mm:ssZ
yyyy-MM-dd'T'HH:mm:ssXXX
yyyy-MM-dd'T'HH:mm:ss.SSSZ
yyyy-MM-dd'T'HH:mm:ss.SSSX
yyyy-MM-dd
M/d/yy
yyyyMMdd
yyyy/MM/dd

If you store dates in other formats, you can add the format to the list of supported formats.

From the Discovery user interface, open the Manage collection page. Click your collection tile. From the Manage fields page for the collection, add a format to the Date formats field. Specify a date format that is supported by the Java [SimpleDateFormat](https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html) class.
These transactions are added to the transaction log within the blockchain and include a [read-write set](https://hyperledger-fabric.readthedocs.io/en/release-2.2/readwrite.html) that is used to update the key-value pairs in the world state.

If in-country data residency is a requirement, you need to consider the location of your peers and the ordering service, as well as your client applications. You also need to know the location of the peers that belong to other organizations on your channels. If you are using IBM Blockchain Platform for IBM Cloud, you can find the list of [IBM Blockchain Platform regions and locations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-regions-locationsibp-regions-locations) where you and the members of your consortium can deploy your components.





 A use case for data residency 

We can use an example consortium to illustrate how data is distributed on the IBM Blockchain Platform, and to explore how members can achieve data residency. The following figure contains a consortium with one ordering service and four organizations. Each organization has one peer node. Two organizations, Org A and Org B, and the ordering service are located in the United States. The other two organizations, Org C and Org D, are located in Germany. All four organizations are members of and have joined their peers to channel X.

Zoom

![An example consortium](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/data_res_use_case.svg)

Figure 1. An example blockchain consortium with one ordering service and four organizations. The four organizations are all members of one channel, Channel X.

Each peer joined to channel X stores a copy of the channel ledger, which is displayed in Figure 1 as Ledger X. Because peers from the United States and Germany are joined to the channel, the data on the channel ledger resides in both geographies.
In addition to the [data source requirements](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesrequirements) for all installed deployments, your FileNet P8 data source must meet the following requirements:



* The data source can crawl FileNet P8 5.5.0 and the Content Engine Web Services (CEWS) of a FileNet server that is installed on IBM Cloud Pak for Automation.
* FileNet P8 5.5.0 and FileNet on Cloud Pak for Automation support the HTTP and HTTPS protocols.







 Prerequisite steps 

If you want to enable document-level security, you must take some steps to set it up. For more information, see [About document-level security](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesconfiguredls).





 Connecting to a FileNet P8 data source 

From your Discovery project, complete the following steps:



1. From the navigation pane, choose Manage collections.
2. Click New collection.
3. Click FileNet P8, and then click Next.
4. Name the collection.
5. If the language of the documents in FileNet is not English, select the appropriate language.

For a list of supported languages, see [Language support](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-language-support).
6. Optional: Change the synchronization schedule.

For more information, see [Crawl schedule options](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionscrawlschedule).
7. Complete the following fields in the Enter your credentials section:

Content Engine Web Service URL
: The Content Engine web service URL of the IBM FileNet P8 server.

When you enter the URL, use the format: <protocol>://<server>:<port>/wsi/FNCEWS40MTOM. You can use the HTTP or HTTPS protocol.
Prerequisite step 

When you set up the collection, you must provide details such as the LDAP host name and port, for your directory server type. For more information about how to discover these values, see the documentation from the vendor:



* [IBM Security Directory Server](https://www.ibm.com/docs/en/sdse/6.4.0?topic=do-security-directory-server-overview)
* [Microsoft Active Directory](https://docs.microsoft.com/en-us/machine-learning-server/operationalize/configure-authenticationactive-directory-and-ldapldap-s)
* [Oracle Directory Server](https://docs.oracle.com/cd/E20295_01/html/821-1220/bcalm.htmlscrolltoc)







 Connecting to an LDAP directory data source 

From your Discovery project, complete the following steps:



1. From the navigation pane, choose Manage collections.
2. Click New collection.
3. Click LDAP directory, and then click Next.
4. Name the collection.
5. If the language of the documents in Salesforce is not English, select the appropriate language.

For a list of supported languages, see [Language support](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-language-support).
6. Optional: Change the synchronization schedule.

The crawler schedule options work as follows for LDAP directories:

Full crawling
: Crawls all entries.

Crawling updates
: Crawls all entries, then filters out any entries that were inserted, updated, or deleted since the last crawl.

Crawling new and modified content
: Runs an LDAP query against the data source server to pick up any entries that were inserted or updated only.

For more information, see [Crawl schedule options](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionscrawlschedule).
7. Configure a secure connection to the directory.

Server type
In addition to the [data source requirements](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesrequirements) for all installed deployments, your SharePoint On Prem data source must meet the following requirements:



* The data source connection supports SharePoint 2013, 2016, or 2019.
* You must obtain any required service licenses for the data source that you want to connect to. For more information about licenses, contact the system administrator of the data source.



For more information about SharePoint On Prem, see [Microsoft SharePoint developer documentation](https://docs.microsoft.com/en-us/sharepoint/dev/).





 Prerequisite steps 

Before you create a SharePoint On Prem collection, you must do the following things:



1. Work with the Sharepoint administrator to coordinate the set up of full read access for the web application.

For more information, see [Manage permissions for a web application in Sharepoint Server](https://docs.microsoft.com/en-us/sharepoint/administration/manage-permissions-for-a-web-application).
2. If you want to enable document-level security, you must take some steps to set it up. For more information, see [Supporting document-level security](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesconfiguredls).

You must collect the following information from the LDAP administrator:

LDAP server URL
: The LDAP server URL to connect to, for example ldap://<ldap_server>:<port>.

LDAP binding username
: The username used to bind to the directory service. In most cases, this username is a distinguished name (DN). The logon name might sometimes work with Active Directory. But unlike the general Windows logon, it is case sensitive. The distinguished name always works.

LDAP binding user password
: The password used to bind to the directory service.

LDAP base DN
* [Architecture pattern for using IPsec over Direct Link with a vCenter Server with NSX-T instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-arch-pattern-nsx-t-direct-link-ipsec)
* [Architecture pattern for using Direct Link with NSX-T edge cluster in colocation](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-arch-pattern-direct-link-edge)
* [Architecture pattern for using Direct Link with NSX-T and EVPN](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-arch-pattern-direct-link-evpn)
* [Virtual Private Network (VPN)](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-A8B113EC-3D53-41A5-919E-78F1A3705F58.html)
* [Adding a cross-account connection](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-adding-cross-account-connections&interface=ui)







 Related links 



* [Commvault - Enterprise data solutions](https://www.commvault.com)
* [Dell PowerProtect DD Virtual edition data sheet](https://www.delltechnologies.com/asset/en-my/products/data-protection/technical-support/h17925-dellemc-powerprotect-ddve-ds.pdf)
* [IBM Spectrum Protect](https://www.ibm.com/products/data-protection-and-recovery)
* [IBM Spectrum Protect Plus](https://www.ibm.com/products/ibm-spectrum-protect-plus)
* [Rubrik - Remote and Branch Office backup software](https://www.rubrik.com/solutions/remote-branch-office)
$pool2 = Get-NsxEdge OpenShift-ESG | Get-NsxLoadBalancer | New-NsxLoadBalancerPool -name api-pool-22623 -Description "OpenShift API TCP 22623" -Transparent:$false -Algorithm Round-Robin -Monitor $monitor -Memberspec $poolMember5,$poolMember6,$poolMember7,$poolMember8
$pool3 = Get-NsxEdge OpenShift-ESG | Get-NsxLoadBalancer | New-NsxLoadBalancerPool -name app-pool-80 -Description "OpenShift Application HTTP" -Transparent:$false -Algorithm Round-Robin -Monitor $monitor -Memberspec $poolMember9,$poolMember10,$poolMember11
$pool4 = Get-NsxEdge OpenShift-ESG | Get-NsxLoadBalancer | New-NsxLoadBalancerPool -name app-pool-443 -Description "OpenShift Application HTTPS" -Transparent:$false -Algorithm Round-Robin -Monitor $monitor -Memberspec $poolMember12,$poolMember13,$poolMember14

 Configure Load-balancer application profile
$appProfile = Get-NsxEdge OpenShift-ESG | Get-NsxLoadBalancer | New-NsxLoadBalancerApplicationProfile -Name TCP-Source-Profile -Type TCP -PersistenceMethod sourceip

 Configure Load-balancer VIPs
Get-NsxEdge OpenShift-ESG | Get-NsxLoadBalancer | Add-NsxLoadBalancerVip -name api-6443-lb -Description "API / API-INT" -ipaddress 10.208.242.132 -Protocol tcp -Port 6443 -ApplicationProfile $appProfile -DefaultPool $pool1 -AccelerationEnabled
HubSpot [hubspot.advanced.openapi.json](https://github.com/watson-developer-cloud/assistant-toolkit/blob/master/integrations/extensions/starter-kits/hubspot/advanced/hubspot.advanced.openapi.json) [HubSpot setup](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-actions-templatesactions-templates-extension-setup-hubspot) 
 NeuralSeek Requires a file specific to your instance of NeuralSeek. Refer to the setup instructions. [NeuralSeek extension setup](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-actions-templatesactions-templates-extension-setup-neuralseek) 
 ServiceNow [sn.openapi.json](https://github.com/watson-developer-cloud/assistant-toolkit/blob/master/integrations/extensions/starter-kits/servicenow/sn.openapi.json) [ServiceNow extension setup](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-actions-templatesactions-templates-extension-setup-servicenow) 
 Zendesk [zendesk-openapi.json](https://github.com/watson-developer-cloud/assistant-toolkit/blob/master/integrations/extensions/starter-kits/zendesk-support/zendesk.openapi.json) [Zendesk extension setup](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-actions-templatesactions-templates-extension-setup-zendesk) 





 Coveo search extension setup 

To set up the extension for Coveo search, see [Coveo search extension setup](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-search-extension-coveo).





 Google custom search extension setup
[Create a public NodePort service](https://cloud.ibm.com/docs/openshift?topic=openshift-nodeportnodeport_config). 
 NLB v1.0 (+ subdomain) Basic load balancing that exposes the app with an IP address or a subdomain. Quickly expose one app to the public with an IP address or a subdomain that supports SSL termination. [Create a public network load balancer](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancerlb_config) (NLB) 1.0 in a [single](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancerlb_config) or [multizone](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancermulti_zone_config) cluster. Optionally [register](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer_hostname) a subdomain and health checks. 
 NLB v2.0 (+ subdomain) DSR load balancing that exposes the app with an IP address or a subdomain. Expose an app that might receive high levels of traffic to the public with an IP address or a subdomain that supports SSL termination.<br><br><br><br>1. Complete the [prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-v2ipvs_provision).<br>2.
canonical = 'POST' + headers['Content-Type'] + payload['id'] + payload['serviceName'] + payload['event'] 
+ payload['timestamp'] + headers['X-IBM-Nonce']
signature = base64.b64encode(hmac.new(secret, canonical, hashlib.sha256).hexdigest())
match_flag = hmac.compare_digest(headers['Authorization'], signature)

PHP:

// This assumes that the request headers are stored in an associative array called $headers and that
// the JSON content of the request is decoded into an associative array called $payload.

$secret = 'Your secret key';
$canonical = 'POST' . $headers['Content-Type'] . $payload['id'] . $payload['serviceName'] . $payload['event']
. payload['time stamp'] . $headers['X-IBM-Nonce'];
$signature = base64_encode(hash_hmac('sha256', $canonical, $secret));
$matchFlag = hash_equals($headers['Authorization'], $signature);

Node.js:

// This assumes that the request headers are stored in variables that are named content_type, nonce, and auth_string.
// This also assumes that the content of the request is a JSON object called payload.

const crypto = require('crypto');

var canonical = 'POST' + content_type + payload.id + payload.serviceName + payload.event + payload.timestamp + nonce;
hmac = crypto.createHmac('sha256', secret).update(canonical);
signature = Buffer.from(hmac.digest('hex')).toString('base64');
matchFlag = crypto.timingSafeEqual(auth_string, signature);
* [29 April 2022](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-apr2922)



* Node.js version 16 is now the default.





* [June 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-jun21)



* [21 June 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-jun2121)



* Overview topic for troubleshooting





* [May 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-may21)



* [7 May 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-may721)



* Deprecated of packages and runtimes.



* [1 May 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-may0121)



* Added information about error handling.
* Added information about getting support.





* [April 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-apr21)



* [27 April 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-apr0721)



* Added information about deprecating Watson services.
Aligned with the requirements of the Financial Services industry, Continuous Delivery provides a reference implementation of [NIST Configuration Management](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls/release-search!/controls?version=5.1&family=CM) controls as a service.

Out of the box, DevSecOps with Continuous Delivery also uses scanning tools such as SonarQube, Gosec, OWASP Zap (dynamic scan), any unit test framework, and GPG signing. It can also be used with more tools such as external Git providers and artifact stores. DevSecOps supports hybrid deployments, in particular by using [pipeline private workers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-private-workers), and can be interfaced with other deployment tools such as Satellite Config and ArgoCD. For more information, see [DevSecOps with Continuous Delivery](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops_intro).

You can configure this deployable architecture from the catalog by adding it to a

project, configuring the input variables, validating your updates, and deploying it in just a short time. Learn about how you can [Deploy DevSecOps Application Lifecycle Management with projects](https://cloud.ibm.com/docs/devsecops-alm?topic=devsecops-alm-devsecops-alm-proj).
Research references 

For more information about the research behind the IBM Watson® Text to Speech service, see the following documents. IBM® researchers wrote or contributed to all of these papers.



1. Eide, Ellen M., and Raul Fernandez. [Database Mining for Flexible Concatenative Text-to-Speech.](http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=4218196) Proceedings of International Conference on Acoustics, Speech and Signal Processing (ICASSP), Vol. 4 (2007): pp. 697-700.
2. Eide, Ellen, Raul Fernandez, Ron Hoory, Wael Hamza, Zvi Kons, Michael Picheny, Ariel Sagi, Slava Shechtman, and Zhi Wei Shuang. [The IBM Submitted to the 2006 Blizzard Text-to-Speech Challenge.](http://www.festvox.org/blizzard/bc2006/ibm_blizzard2006.pdf) Blizzard Challenge Workshop 2006.
3. Fernandez, Raul, David Daws, Guy Lorberdam, Slava Shechtman, and Alexander Sorin. [Transplantation of Conversational Speaking Style with Interjections in Sequence-to-Sequence Speech Synthesis.](https://arxiv.org/abs/2207.12262) Proceedings Interspeech (2022): publication pending.
4. Fernandez, Raul, Asaf Rendel, Bhuvana Ramabhadran, and Ron Hoory. [Using Deep Bidirectional Recurrent Neural Networks for Prosodic-Target Prediction in a Unit-Selection Text-to-Speech System.](https://www.researchgate.net/publication/295080074_Using_Deep_Bidirectional_Recurrent_Neural_Networks_for_Prosodic-Target_Prediction_in_a_Unit-Selection_Text-to-Speech_System) Proceedings Interspeech (2015), pp. 1606-1610.
5. Fernandez, Raul, Asaf Rendel, Bhuvana Ramabhadran, and Ron Hoory.
SPDX [npm] (Copyright not found)([https://github.com/nodejs/node/tree/v12.13.0/deps/npm](https://github.com/nodejs/node/tree/v12.13.0/deps/npm))





 Creative Commons Attribution 4.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by/4.0/legalcode](https://creativecommons.org/licenses/by/4.0/legalcode).

CANIUSE-LITE (Copyright (c) Alexis Deveria)([http://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30000974.tgz](http://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30000974.tgz))





 Creative Commons Attribution Share Alike 3.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by-sa/3.0/legalcode](https://creativecommons.org/licenses/by-sa/3.0/legalcode).

T/MAXMIND-DB/* [libmaxminddb-dev] (Copyright: 2013-2014 MaxMind, Inc.)([https://packages.debian.org/stretch/libmaxminddb-dev](https://packages.debian.org/stretch/libmaxminddb-dev))
* ZONE_NAME: us-south-2
* PROFILE_NAME: bx2-2x8
* SUBNET: 0726-198db988-3b9b-4cfa-9dec-0206420d37d0
* IMAGE: Debian 11 image r134-f83ce520-00b5-40c5-9938-a5c82a273f91
* KEYS: r134-89ec781c-9630-4f76-b9c4-a7d204828d61



The response varies depending on the option values that you use.

ID 0726_67b1179a-8b25-4ac9-8bc0-7f3027466ed0
Name my-instance
CRN crn:v1:public:is:us-south-2:a/2d1bace7b46e4815a81e52c6ffeba5cf::instance:0726_67b1179a-8b25-4ac9-8bc0-7f3027466ed0
Status pending
Availability policy on host failure restart
Startable true
Profile bx2-2x8
Architecture amd64
vCPU Manufacturer intel
vCPUs 2
Memory(GiB) 8
Bandwidth(Mbps) 4000
Volume bandwidth(Mbps) 1000
Network bandwidth(Mbps) 3000
Lifecycle Reasons Code Message
- -

Lifecycle State pending

Metadata service Enabled Protocol Response hop limit
false http 1

Image ID Name
r134-f83ce520-00b5-40c5-9938-a5c82a273f91 ibm-debian-11-3-minimal-amd64-4

VPC ID Name
r134-35b9cf35-616e-462e-a145-cf8db4062fcf my-vpc

Zone us-south-2
Resource group ID Name
"refresh_token": "J1D6UZp3fEhxRdPCzhY4kvt7ojXIdUHjmO8x9pxGMgSZt0XpGd15F098WFKKUwp_v0pktQxdOZtcBGx3sL5THYUxU-PlkxELZ3gKX78dWf4P7lYDLDXR2x_n48fPIvRQoDD0ZJAKewO3o1IcegmNdf_InSgvu2M3Ra3FwlJPDN9mRH6-2e8pHnvq4e1rdY6pV0ufxweKc9dGqU-U7VU765BCg84kr8tkb9kpZnnPseDJ89gf5lhkZteKoNVkn-uiLUF0L-yv33tgtoDrdU5-FqaV00TUbLBoJEeTTnUD1fgIGB6SfphIImCQ0368gTU2emGBe3lzlQBnvkOXaMoBds3Nc2YL6px2LhqBWFd_ho68P4ahz1cbTn1rhqIjZMokeN88sreAKsRWhH7nVgBpfN3FS7OJBrVTx55j44vrZdH3vFJ-glLNb3FBwI6_6N_i2lVz7W-_