vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"From this day you must be a stranger to one of your parents. Your mother will never see you again if you do not marry Mr. Collins, and I will never see you again if you do."
],
"metadata": {
"name": "favorites2.json"
},
"Speaker": "Mr. Bennett"
},
"notices": []
}
Show more

You cannot submit an array of objects as input. For example, you might want to analyze multiple quotations, so your source might look as follows:

{
"quotations":[
{
"Author": "Jane Austen",
"Book": "Sense and Sensibility",
"Quote": "Is there a felicity in the world superior to this?",
"Year": "1811/01/01",
"Subject": "Nature",
"Speaker": "Marianne Dashwood",
"url": "https://www.gutenberg.org/files/1342/1342-h/1342-h.htmlink2HCH0059"
},
{
"Author": "Jane Austen",
"Book": "Persuasion",
"Quote": "A man does not recover from such a devotion of the heart to such a woman. He ought not; he does not.",
"Subject": "Romantic love",
"Year": "1818/01/01",
"Speaker": "Captain Wentworth",
"url": "https://www.gutenberg.org/files/105/105-h/105-h.htmchap20"
}
]
}
Show more

If so, break each object into a separate file and analyze each file individually.





 Analyzing a text snippet 

You can submit text for analysis when you specify the text in JSON format by using syntax like this:

{
"text":"The text that you want to analyze."
}
To comply with the regulatory standards, you may need to get a consent (opt-in) from the SMS recipients to receive SMSs from each of the Event Notifications subscriptions.



 Create a subscription with IBM SMS service as destination 



1. From the Event Notifications dashboard, click Subscriptions in the navigation menu.
2. Click Create + to display Create a Subscription side panel.
3. Complete the following subscription details:



* Name: name of the subscription.
* Description: add an optional description for this subscription



4. Select a Topic from the list.
5. Select IBM Cloud SMS service as Destination from the list.
6. The Recipients section displays three tabs:



* Invited - displays the list of phone numbers added to the subscription. Enter the phone numbers that need to receive SMS notifications and need to be part of the subscription.
* Active - displays the list of phone numbers added to the subscription and confirmed by the user to receive SMS notifications.
* Unsubscribed - displays the list of phone numbers added to the subscription and refused by the user not to receive SMS notifications.



Add the user's phone numbers with a + and country code, who needs to receive SMS messages as part of this subscription, with comma (,) as separator between the numbers.
7. Click Create. The recipient automatically receives initial message that they have been invited to subscribe to the topic. This is the opt-in message.



The Opt-in message contains:



* invitee name or account
* name of the subscription
* name of the topic
* a link that will take you to a web page. The web page contains information that the recipient is subscribed to receive SMS notifications to a topic and a Confirm button. When the recipient click the Confirm button, then the recipient's number is moved from Invited tab to Active tab. A confirmation message also displaying that the recipient has accepted to receive SMS notifications. The confirmation message also contains a link to Unsubscribe, which on clicking moves to recipient's number to the Unsubscribed tab.
* an expiration time for the opt-in message.
mask:="userType;eventName,eventCreateDate"
eventLogs :=getAllEvents(filter,mask,pagination,maxNumberOfEvents)
printLogs(eventLogs)
}

/
Shows the SYSTEM Logs.
Request URL:
GET https://api.softlayer.com/rest/v3.1/SoftLayer_Event_Log/getAllObjects.json?
objectFilter={"userType":{"operation":"SYSTEM"}}&
objectMask=mask[userType,eventName,eventCreateDate]&
resultLimit=0,50
/
func getSystemLogs(){
getLogsByUserType("SYSTEM")
}

/
Shows the Login Logs
RequestURL:
GET https://api.softlayer.com/rest/v3.1/SoftLayer_Event_Log/getAllObjects.json?
objectFilter={"eventName":{"operation":"^=+Login"}}&
objectMask=mask[userType;eventName,eventCreateDate]&
resultLimit=0,50
/
func getLoginLogs(){
getLogsByName("Login")
}

/
Shows the recent Logs, based on a number of days ago.
Request URL:
GET https://api.softlayer.com/rest/v3.1/SoftLayer_Event_Log/getAllObjects.json?
objectFilter={"eventCreateDate":{"operation":"greaterThanDate",
"options":[{"name":"date","value":"2021-04-24T00:00:00.0000-06:00"]}]}}&
objectMask=mask[userType;eventName,eventCreateDate]&
resultLimit=0,50
/
func getRecentLogs(daysAgo int){
The email includes information such as a copy of the comment, the user who posted it, and when the comment was posted. To turn off all email notifications for your project, complete the following steps:



1. From the project sidebar, click Settings > General.
2. On the **General Settings **page, click Visibility > project features > permissions.
3. Select the Disable email notifications checkbox.
4. Click Save changes.







 Project integrations and webhooks 

Git Repos and Issue Tracking projects might also be configured with integrations or webhooks to other systems, or equipped with access tokens, deploy tokens, and deploy keys. To review or change the integrations, webhooks, tokens, and keys that might be configured with your project, from the project sidebar, complete the following steps:



1. From the project sidebar, click Settings.
2. Click Integrations to work with your project's integrations with other applications.
3. Click Webhooks to work with your project's webhooks to other systems.
4. Click Access Tokens to work with access tokens that might grant access to your project.
5. Expand Deploy Tokens to work with the deploy tokens that might grant access to your project.
6. Expand Deploy Keys to work with deploy keys that might grant access to your project.



To learn more about working with Git Repos and Issue Tracking, see [Git Repos and Issue Tracking](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-git_working).







 Protecting your data when you use Delivery Pipelines 

Continuous Delivery pipelines run the jobs and steps that you provide. The Continuous Delivery service securely manages the log output and build artifacts that are produced by your pipeline runs. However, Continuous Delivery does not limit or manage the function of your pipeline job or step scripts.

When you develop and configure your pipeline job and step scripts, ensure that your scripts do not run actions that might compromise the confidentiality, integrity, or availability of your resources, or otherwise violate regulatory controls.
As a part of this guide, you have set up Application AMS for end to end security of messages. We have demonstrated that this ensures message integrity and message privacy are protected and that messages are readable only by authorized users.





 Appendix 



 Appendix 1: connection_info.txt 

To retrieve the connection_info.txt file containing queue manager connection details:



1. Login to the IBM Cloud service instance by clicking on the relevant service shown in the table
![Image showing service instance](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_ams_si.png)
2. This will open the queue manager view. Select the queue manager you wish to retrieve the connection info from
![Image showing list of queue managers](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_ams_qmview.png)
3. Click Connection information
![Image of queue manager connection information](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_ams_connection_info.png)
4. Download this file in 'JSON text format'







 Appendix 2: platformApiKey.json 

To create or reset your administrator api key:



1. Login to the IBM Cloud service instance by clicking on the relevant service shown in the table
!
You probably want either the Found response for all of them or none of them to be returned.

To prevent Found responses from being displayed, you can do one of the following things to each Found response:

- Add a condition to the response that prevents it from being displayed if particular slots are filled. For example, you can add a condition, like !($size && $time), that prevents the response from being displayed if the $size and $time context variables are both provided.
- Add the !all_slots_filled condition to the response. This setting prevents the response from being displayed if all of the slots are filled. Do not use this approach if you are including a confirmation slot. The confirmation slot is also a slot, and you typically want to prevent the Found responses from being displayed before the confirmation slot itself is filled.

 Handling requests to exit a process {: dialog-slots-node-level-handler}

Add at least one slot handler that can recognize it when a user wants to exit the node.

For example, in a node that collects information to schedule a pet grooming appointment, you can add a handler that conditions on the cancel intent, which recognizes utterances such as, <q>Forget it. I changed my mind.</q>

1. In the JSON editor for the handler, fill all of the slot context variables with dummy values to prevent the node from continuing to ask for any that are missing. And in the handler response, add a message such as, Ok, we'll stop there. No appointment will be scheduled.
1. Choose what action you want your assistant to take next from the following options:

- Prompt again (Default): Displays the prompt for the slot that the user was working with just before asking the off-topic question.
- Skip current slot: Displays the prompt associated with the slot that comes after the slot that the user was working with just before asking the off-topic question. And your assistant makes no further attempts to fill the skipped slot.
- Skip to response: Skips the prompts for all remaining empty slots including the slot the user was working with just before asking the off-topic question.

1.
objectFilter={"eventCreateDate":{"operation":"greaterThanDate",
"options":[{"name":"date","value":"2021-04-24T00:00:00.0000-06:00"]}]}}&
objectMask=mask[userType;eventName,eventCreateDate]&
resultLimit=0,50
/
func getRecentLogs(daysAgo int){
offsetDate :=getDateString(-daysAgo)
filterObject:=filter.Build(filter.Path("eventCreateDate").DateAfter(offsetDate))
mask:="userType;eventName,eventCreateDate"
recentEvents:=getAllEvents(filterObject,mask,pagination,maxNumberOfEvents)
printLogs(recentEvents)
}

/
Pages through all results from the Event_Log. This might take long time.
/
func getAllEvents(
filter string,
mask string,
pagination int,
maxNumberOfEvents int,
) (resp []datatypes.Event_Log) {
limit:=pagination
offset:=0
eventsSize:=limit
var allEvents []datatypes.Event_Log
for eventsSize<=maxNumberOfEvents {
events := getAllObjects(limit,offset,filter,mask)
// return if the events are a list of empty structure like [{}]
if events[0]==(datatypes.Event_Log{}){
return allEvents
}
allEvents=append(allEvents, events...)
eventsSize=eventsSize+pagination
}
return allEvents
}

/
Request URL:
GET https://api.softlayer.com/rest/v3.1/SoftLayer_Event_Log/getAllObjects.json?
Confirm you can see your test message and then click Close.







 Get a message using the amqsgetc sample program 

This step is unique to runmqsc and cannot be achieved on MQ Explorer.

In the same shell used in the previous steps:



1. Run <PATH_TO_SAMPLE_BIN_DIR>/amqsgetc DEV.TEST.1 <your QMGR name>
2. Enter your platform API key when prompted for a password.



Your test message is displayed.

After a short period, the amqsputc sample program should end after finding no more messages.





 Delete the test queue 



 Using MQ Explorer 



1. Right click on queue 'DEV.TEST.1'.
2. Click 'Delete'.
3. Click 'Delete'.
4. Check the 'Clear all messages from the queue' box.
5. Click Delete.
6. Click OK.



You can see that queue 'DEV.TEST.1' has been removed from the list of queues.





 Using runmqsc 

In the same shell used in the previous steps:



1. Run <PATH_TO_BIN_DIR>/runmqsc -c -u <your MQ username> -w60 <QUEUE_MANAGER_NAME>
2. Enter your platform API key when prompted for a password.
3. Run DELETE QLOCAL(DEV.TEST.1)



* You receive a message stating that the queue has been deleted.



4. Run DISPLAY QLOCAL(DEV.TEST.1) to prove the queue has been deleted.



* You receive a message stating that the queue was not found.



5. Run end



* The runmqsc session is closed.











 Conclusion 

You've successfully:



* Connected to a queue manager using either MQ Explorer or runmqsc and have created a new test queue
* Put a test message onto the test queue
* Either browsed the the test queue to view the test message or used amqsgetc to view the test message
* UI
* API







 Filtering and searching keys 

You can filter and search for your managed keys in Unified Key Orchestrator with the IBM Cloud® console, or programmatically with the Unified Key Orchestrator API.



 Filtering keys with the IBM Cloud console 

To filter keys by using the console, complete the following steps:



1. [Log in to the Hyper Protect Crypto Services instance](https://cloud.ibm.com/login).
2. Click Managed keys from the navigation to view all the available keys.
3. Click the Filter icon ![Filter icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/filter.svg) in the table.
4. Specify the filter criteria as you need, and click Apply.

You can set the following filter criteria.



Table 1. Filter managed keys

 Property Description 

 Vault The vault that controls access to the managed key. 
 Activation Set a date range of when you activate the key. 
 Expiration Set a date range of when you deactivate the key. 
 Creation Set a date range of when the key was created. 
 Keystore types The type of keystore where the key is stored. 
 Keystores The keystores that the key is activated in. 
 Algorithm The encryption algorithm to encrypt data for the key. 
 Minimum key length The minimum number of bits that represents the encryption strength of the key. 
 Maximum key length The maximum number of bits that represents the encryption strength of the key. 
 State Key states include Pre-active, Active, Deactivated, and Destroyed. For more information, see [Monitoring the lifecycle of encryption keys in Unified Key Orchestrator](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-key-states). 
 Last rotated The time range when the key was last rotated. 









 Searching for keys with the IBM Cloud console 

To search for a key by using the console, complete the following steps:



1.
[RabbitMQ Management plug-in](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-plug-insrabbitmq-management-plug-in) rabbitmq_management 
 [JMS plug-in](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-plug-insjms-plug-in) rabbitmq_jms_topic_exchange 
 [MQTT plug-in](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-plug-insmqtt-plug-in) rabbitmq_mqtt 







 Shovel plug-in 

Messages for RabbitMQ comes with the [Shovel plug-in](https://www.rabbitmq.com/shovel.html), rabbitmq_shovel, and the [Shovel Management plug-in](https://github.com/rabbitmq/rabbitmq-shovel-management), rabbitmq_shovel_management, enabled. You can configure the plug-in through both the [RabbitMQ Management plug-in UI](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-plug-insrabbitmq-management-plug-in) and its accompanying API.

The Shovel Status and Shovel Management links appear under the Admin tab.

Zoom

![Admin tab with the Shovel plug-in](https://cloud.ibm.com/docs-content/v1/content/4dfeb7bbbdd817dfbdb17402735fb55d9cfbc7fb/messages-for-rabbitmq/images/plugins-shovel-ui.png)

Figure 1. Admin tab with the Shovel plug-in
The sole exception is keyword spotting, for which the service returns all words as specified by the user, regardless of whether profanity_filter is true.



 Profanity filtering example 

The following example shows the results for a brief audio file that is transcribed with the default true value for the profanity_filter parameter. The request also sets the word_alternatives_threshold parameter to a relatively high value of 0.99 and the word_confidence and timestamps parameters to true.

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/flac" --data-binary @{path}audio-file.flac "{url}/v1/recognize?word_alternatives_threshold=0.99&word_confidence=true&timestamps=true"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/flac" --data-binary @{path}audio-file.flac "{url}/v1/recognize?word_alternatives_threshold=0.99&word_confidence=true&timestamps=true"

The service masks profanity from the response by replacing it with a series of asterisks:

{
"result_index": 0,
"results": [
{
"word_alternatives":
{
"start_time": 0.03,
"alternatives":
{
"confidence": 1.0,
"word": ""
}
],
"end_time": 0.25
},
{
"start_time": 0.25,
"alternatives":
{
"confidence": 0.99,
"word": "you"
}
],
"end_time": 0.56
}
],
"alternatives":
{
"transcript": " you",
"confidence": 0.99,
"word_confidence":
"", 1.0],
If the message is in base64 format, you can choose to have the message decoded when the event is sent. You can also specify the content type for your custom event data. Click Next to proceed.
5. For Event consumer, specify the application or job to receive events. Notice that you can choose from a list of defined applications and jobs. For this example, use the myapp application that references the icr.io/codeengine/cron image. If you have not yet created your app or job, you can specify the name of your application or job and [create your application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) or [create your job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan) after you create the Periodic timer (cron) subscription. For applications only, you can optionally specify a path. By default, events are routed to the root URL of the destination application. You can send events to a different destination within the app by specifying a path. For example, if your subscription path specifies /events, the events are sent to https://<base application URL>/events. Click Next to proceed.
6. For Summary, review the settings for your Periodic timer event subscription and make changes if needed. When ready, click Create to create the Periodic timer (cron) subscription.



5. Now that your Periodic timer (cron) subscription is created, go to the Event subscriptions page to [view a listing of defined subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronview-eventing-cron-app-ui).
6. To update a subscription, navigate to your Periodic timer (cron) subscription page. From the Event subscriptions page, click the name of the subscription that you want to update.
7. From your Periodic timer (cron) subscription page, let's change the data in the event message.
def getAllObjects(self, _filter, limit=50, offset=0):
"""Pages through all results from the Event_Log. This might take long time."""
notDone = True
while notDone:
events = self.client.call('SoftLayer_Event_Log', 'getAllObjects', filter=_filter, limit=limit, offset=offset)
print("%s from getAllObjects, offset = %s" % (len(events), offset))

for event in events:
yield event
if len(events) < limit:
notDone = False
offset = offset + limit
notDone = False

def debug(self):
for call in self.client.transport.get_last_calls():
print(self.client.transport.print_reproduceable(call))

def getDateString(self, delta=30):
date_object = datetime.date.today() - datetime.timedelta(days=delta)
return date_object.strftime("%Y-%m-%dT00:00:00.0000-06:00")

def printLogs(log):
print("%s - %s - %s" % (log['eventName'],log['eventCreateDate'], log['userType']))

if __name__ == "__main__":
main = example()
main.allLogs()
main.debug()

package main

import (
"encoding/json"
"fmt"
"github.com/softlayer/softlayer-go/datatypes"
"github.com/softlayer/softlayer-go/filter"
"github.com/softlayer/softlayer-go/services"
"github.com/softlayer/softlayer-go/session"
"time"
)
event-notifications.devices.read GET /event-notifications/v1/instances/{instanceID}/destinations/{id}/devices/{device_id} Manager, Administrator, Device-Manager Get a single device under a push notifications FCM destination 
 event-notifications.devices.list GET /event-notifications/v1/instances/{instanceID}/destinations/{id}/devices Manager, Administrator, Device-Manager Create all devices under a push notifications FCM Destination 
 event-notifications.devices.update PUT /event-notifications/v1/instances/{instanceID}/destinations/{id}/devices/{device_id} Manager, Administrator, Device-Manager Update an existing device under a push notifications FCM destination 
 event-notifications.devices.delete POST /event-notifications/v1/instances/{instanceID}/destinations/{id}/devices/{device_id} Manager, Administrator, Device-Manager Delete an existing device under a push notifications FCM destination 
 event-notifications.tag-subscriptions.list GET /event-notifications/v1/instances/{instanceID}/destinations/{id}/tag_subscriptions Manager, Administrator list all subscriptions under a push DCM destination 
 event-notifications.tag-subscriptions.devices.list GET /event-notifications/v1/instances/{instanceID}/destinations/{id}/tag_subscriptions/devices/{device_id} Manager, Administrator, Device-Manager Get a single device from tag subscriptions under a push notifications FCM destination 
 event-notifications.tag-subscriptions.create POST /event-notifications/v1/instances/{instanceID}/destinations/{id}/tag_subscriptions Manager, Administrator, Device-Manager Create a tag subscription under a push notifications FCM Destination 
 event-notifications.tag-subscriptions.delete DELETE /event-notifications/v1/instances/{instanceID}/destinations/{id}/tag_subscriptions Manager, Administrator, Device-Manager Delete tag subscriptions under a push notifications FCM destination
One of permit, deny.

--prefix PREFIX
: Specify an IPv4 subnet CIDR indicating both the address and mask length.

--before BEFORE
: To prioritize this filter in the export route filter list, specify the ID of the route filter that comes before this filter. Optional.

--ge GE
: Specify a minimum matching length (GE, greater than or equal to). Optional. For more information, see [Route filtering rules](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes&interface=uiroute-filtering-rules).

--le LE
: Specify a maximum matching length (LE, less than or equal to). Optional. For more information, see [Route filtering rules](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes&interface=uiroute-filtering-rules).

--help|-h
: Get help on this command. Optional.

--output value
: Specify whether you want the output displayed in JSON format. Currently, json is the only supported format. Optional.





 Examples 



* ibmcloud dl erfc dc206f57-5693-442f-8888-6d43b6c82d73 --action permit --prefix 10.10.0.0/24
* ibmcloud dl erfc dc206f57-5693-442f-8888-6d43b6c82d73 --action deny --prefix 10.10.0.0/24 -le 29









 ibmcloud dl export-route-filter-delete 

Delete an export route filter.

ibmcloud dl export-route-filter-delete|erfd GATEWAY_ID FILTER_ID [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

FILTER_ID
: Specify the ID of the export route filter that you want to delete.

--help|-h
"ibmenpushto": "{"user_ids": ["ajay@accts.acmebank.com","ankit@accts.acmebank.com"]}"

Targeting notifications to push tags.

"ibmenpushto": "{"tags": ["salesTeam","TechTeam"]}"

Targeting notifications to platforms.

"ibmenpushto": "{"platforms":["push_android","push_ios"]]}"

Targeting notifications to specific platform.

"ibmenpushto": "{"platforms":["push_android"]}"
"ibmenpushto": "{"platforms":["push_ios"]}"
"ibmenpushto": "{"platforms":["push_chrome"]}"
"ibmenpushto": "{"platforms":["push_firefox"]}"
"ibmenpushto": "{"platforms":["push_safari"]}"