vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* UI
* CLI
* API
* Terraform







 Deleting unused tags from the account 

Before you can delete a tag, you must remove it from all resources and service IDs. If you still can't delete it, the tag might be attached to a resource that you don't have permission to view or was reclaimed. The same tag can be attached to several resources and service IDs by different users in the same billing account.

If a reclaimed resource is blocking tag deletion, you can either completely delete that reclaimed resource or restore it within 7 days after you delete it. Not all resources can be restored. You can use the IBM Cloud® CLI to manage the reclamation process of specific resources. For more information, see [Using resource reclamations](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).

When you delete an access management tag from the account, any associated IAM policies are also deleted with it.



 Deleting unused tags in the console 



1. To see the full list of tags in your account, go to Manage > Account in the IBM Cloud® console, and select Tags.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Delete next to the unused tag.







 Deleting unused tags by using the CLI 

Log in to [IBM Cloud® CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) and select your account to run the ibmcloud resource tag-delete command for deleting only one or all of the unused tags.

The following example deletes the MyTag user tag:

ibmcloud resource tag-delete --tag-name MyTag





 Deleting unused tags by using the API
For example, lots of entries that include the key "herbivore". This situation makes pagination by using only startkey/endkey tricky, so you can use other parameters to help: startkey_docid/endkey_docid.See the following example of a first request:<-- <ul> --> * Curl * Java * Node * Python * Go<-- </ul> --> get first page of animals by diet
curl -H "Authorization: Bearer $API_BEARER_TOKEN" "$SERVICE_URL/animaldb/_design/views101/_view/diet?limit=3&startkey="herbivore"&endkey="herbivore""
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.PostViewOptions;
import com.ibm.cloud.cloudant.v1.model.ViewResult;
import com.ibm.cloud.cloudant.v1.model.ViewResultRow;

int pageSize = 3;
String diet = "herbivore";
PostViewOptions.Builder viewOptionsBuilder =
new PostViewOptions.Builder()
.db("animaldb")
.ddoc("views101")
.view("diet")
.limit(pageSize) // Fetch pageSize documents
.startKey(diet)
.endKey(diet);
ViewResult response =
service.postView(viewOptionsBuilder.build())
.execute()
.getResult();

while (response.getRows().size() > 0) {
List<ViewResultRow> responseDocuments = response.getRows();
System.out.println(responseDocuments);
// The startKeyDocId of the next request becomes the last document id appended with u0000
viewOptionsBuilder.startKeyDocId(
responseDocuments
.get(responseDocuments.size() - 1)
* UI
* CLI
* API
* Terraform







 Attaching and detaching tags 

You can attach and detach tags on a resource or service ID through the console, CLI, or API. To attach or detach a tag on a resource or service ID, users must be assigned the appropriate permission. For more information, see [Granting users access to tag resources](https://cloud.ibm.com/docs/account?topic=account-access).

A resource can have a maximum of 1000 user tags, 1000 service tags, and 250 access tags.



 Attaching and detaching tags on a resource in the console 



1. From the IBM Cloud® console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/icon_hamburger.svg) > Resource list to view your list of resources.
2. Locate the specific resource in the list.
3. To attach a tag to the resource, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Add tags.
4. Enter the name of the tag, and click Save.
5. To detach the tag from the resource, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg) next to the tag in your resource list.

When you detach an access management tag from a resource, any associated access policies are also detached from that resource.







 Attaching tags to a resource by using the CLI
* For UI, CLI, API, and Terraform information on using tags, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag).





 Limitations 



1. Some gaps exist between current implementation and the API Spec, which are documented [here](https://cloud.ibm.com/docs/vpc?topic=vpc-known-issues).
2. Instance templates and dedicated host groups don't support access management tags. As a result, you can't completely manage [Auto scale](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group&interface=cli) and [Dedicated hosts](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances&interface=cli) access by using these tags.
3. Internet Key Exchange (IKE) and IPsec policy resources that are used in [site-to-site VPNs](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-overview) don't support access management tags.





 UI Limitations for Assigning Service Defined roles 

Assigning Service Defined roles to an access policy with an access management tag by using the UI isn't supported. This feature is supported only through the API and CLI.







 Using API for Assigning Service Defined roles 

Assigning Service Defined roles to an access policy with an access management tag by using the UI isn't supported. This feature is supported only through the API and CLI. Use the following example for API.

curl --location --request POST 'https://iam.cloud.ibm.com/v1/policies' --header 'Content-Type: application/json' --header 'Authorization: <your token>' --data-raw '{
"description": "useful description here",
"type": "access",
"subjects": [
{
"attributes":
{
"name": "iam_id",
highlight_size Slice up field content into number of characters, so-called fragments, and highlights matches only inside the specified fragments. Yes, defaults to 100 characters Numeric Yes 
 include_docs Include the full content of the documents in the response. Yes Boolean Yes 
 include_fields A JSON array of field names to include in search results. Any fields that are included must be indexed with the store:true option. Yes, the default is all fields. Array of strings Yes 
 limit Limit the number of the returned documents to the specified number. For a grouped search, this parameter limits the number of documents per group. Yes Numeric The limit value can be any positive integer number up to and including 200. Yes 
 q Abbreviation for query. Runs a Lucene query. No String or Number Yes 
 query Runs a Lucene query. No String or Number Yes 
 ranges This field defines ranges for faceted, numeric search fields. The value is a JSON object where the fields names are faceted numeric search fields, and the values of the fields are JSON objects. The field names of the JSON objects are names for ranges. The values are strings that describe the range, for example "[0 TO 10]". Yes JSON The value must be an object with fields that have objects as their values. These objects must have strings with ranges as their field values. No 
 sort Specifies the sort order of the results. In a grouped search (when group_field is used), this parameter specifies the sort order within a group. The default sort order is relevance. Yes JSON A JSON string of the form "fieldname<type>" or -fieldname<type> for descending order. The fieldname is the name of a String or Number field, and type is either a number, a string, or a JSON array of strings. The type part is optional, and defaults to number. Some examples are "foo", "-foo", "bar<string>", "-foo<number>", and ["-foo<number>","bar<string>"]. String fields that are used for sorting must not be analyzed fields.
<xsd:documentation>Column taxonomy: category of the data.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="usageType">
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="automatic">
<xsd:annotation>
<xsd:documentation>Specifies that the usage is not known.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="identifier">
<xsd:annotation>
<xsd:documentation>Specifies that the object is to be treated as an identifier.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="fact">
<xsd:annotation>
<xsd:documentation>Specifies that the object is to be treated as a fact.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="attribute">
<xsd:annotation>
<xsd:documentation>Specifies that the object is to be treated as an attribute.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="regularAggregateType">
<xsd:annotation>
<xsd:documentation>The aggregation rule. same as V5 aggregate name. </xsd:documentation>
</xsd:annotation>
ibmcloud resource tag-detach --tag-names MyTag --resource-id rn:v1:bluemix:public:containers-kubernetes:us-south:a/a27a4741a57dcf5c965939adb66fe1c7:a46242e638ca47b09f10e9a3cbe5687a::
* To detach the user tag MyTag to a resource named MyResource:

ibmcloud resource tag-detach --tag-name MyTag --resource-name 'MyResource'
* To detach the user tag MyTag to a classic infrastructure virtual guest named MyVM, first look for the ID of the virtual guest you would like to detach the tag from:

ibmcloud resource search 'fullyQualifiedDomainName:MyVM _objectType:SoftLayer_Virtual_Guest' -p classic-infrastructure

Take a note of the ID, which is a string similar to 48373549.
* To detach the tag, run the following command:

ibmcloud resource tag-detach --tag-names MyTag --resource-id 48373549 --resource-type SoftLayer_Virtual_Guest
* To detach the access management tag project:myproject from an instance of IBM Cloud Object Storage called Project data, run the following command:

ibmcloud resource tag-detach --tag-names "project:myproject" --resource-name Project data -—tag-type access









 ibmcloud resource tag-delete 

Delete a tag:

ibmcloud resource tag-delete (--tag-name TAG_NAME | -a, --all [-f, --force]) [-p, --provider PROVIDER] [--tag-type TAG_TYPE] [--account-id ACCOUNT_ID]



 Command options 

--tag-name value
: Tag name to be deleted.

--provider value, -p value
: Delete the tag in the specified provider (only supported value is classic-infrastructure).
To set a namespace, repository, digest, or tag as the scope, enter the value in one of the following formats:



* namespace
* namespace/repository
* namespace/repository:tag
* namespace/repository@digest







 Examples 

List all your exemptions for security issues that apply to images in the birds/bluebird repository. The output includes exemptions that are account-wide, exemptions that are scoped to the birds namespace, and exemptions that are scoped to the birds/bluebird repository. The output doesn't include any exemptions that are scoped to specific tags within the birds/bluebird repository.

ibmcloud cr exemption-list --scope birds/bluebird

List all your exemptions for security issues that apply to images in the birds/bluebird@sha256:101010101010 digest. The output includes exemptions that are account-wide, exemptions that are scoped to the birds namespace, and exemptions that are scoped to the birds/bluebird repository and to the birds/bluebird@sha256:101010101010 digest. The output doesn't include any exemptions that are scoped to specific tags within the birds/bluebird repository.

ibmcloud cr exemption-list --scope birds/bluebird@sha256:101010101010







 ibmcloud cr exemption-rm 

Delete an exemption for a security issue. To view your existing exemptions, run ibmcloud cr exemption-list.

You can identify the images in the scope by using either the [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag) or the [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest). You can reference the image by digest <dns>/<namespace>/<repo>@<digest>, which affects the digest and all its tags in the same repository, or by tag <dns>/<namespace>/<repo>:<tag>.
The output is returned in a discrete group.<-- </section "id="section-min-example" "> --><-- </section "id="section-min" "> --><-- <section "id="section-nested" "> --> nested Applying nested before an aggregation query restricts the aggregation to the area of the results that are specified.For example, nested(enriched_text.entities) means that only the enriched_text.entities components of any result are used to aggregate against.The following example checks how many mentions are returned per model type. nested(enriched_text.entities).term(enriched_text.entities.model_name)
The result shows that there are a total of 50 recognized entities and all of them are of type NLU. "aggregations":
{
"type": "nested",
"path": "enriched_text.entities",
"matching_results": 50,
"aggregations":
{
"type": "term",
"field": "enriched_text.entities.model_name",
"results":
{
"key": "natural_language_understanding",
"matching_results": 50
}
]
}
]
}
]
Show more
For another example, see Starting with nested objects]] ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !!! ! ! .<-- </section "id="section-nested" "> --><-- <section "id="section-pair" "> --> pair Analyzes relationships between two fields.<-- <section "id="section-pair-syntax" "> --> Syntax pair(first:{aggregation},second:{aggregation})
where {url} is the appropriate URL for your instance. For more details, see [Service endpoint](https://cloud.ibm.com/apidocs/assistant/assistant-v1service-endpoint).

In the response, the total attribute in the pagination object contains the number of dialog nodes.



If the total seems larger than you expected, it might be because the dialog that you build from the application is translated into a JSON object. Some fields that appear to be part of a single node are actually structured as separate dialog nodes in the underlying JSON object.

- Each node and folder is represented as its own node.
- Each conditional response that is associated with a single dialog node is represented as an individual node.
- For a node with slots, each slot, slot found response, slot not found response, slot handler, and if set, the "prompt for everything" response is an individual node. In effect, one node with three slots might be equivalent to eleven dialog nodes.
* Partial match - With partial matching, the feature automatically suggests substring-based synonyms present in the user-defined entities, and assigns a lower confidence score as compared to the exact entity match.

The partial match component is supported only in English-language dialog skills.



For English, fuzzy matching prevents the capturing of some common, valid English words as fuzzy matches for a given entity. This feature uses standard English dictionary words. You can also define an English entity value/synonym, and fuzzy matching will match only your defined entity value/synonym. For example, fuzzy matching may match the term unsure with insurance; but if you have unsure defined as a value/synonym for an entity like @option, then unsure will always be matched to @option, and not to insurance.

Interactions between the stemming and misspelling fuzzy matching features are not allowed. Specifically, if either an entity or the input is stemmed, misspelling fuzzy matching does not work. For example, assume that the entity is @lending and the input word is pending. During entity stemming, @lending produces lend. During input stemming, pending produces pend. In this case, lend does not match to pend because the entity and input were stemmed. This change applies to only the English language.

Your fuzzy matching setting has no impact on synonym recommendations. Even if fuzzy matching is enabled, synonyms are suggested for the exact value you specify only, not the value and slight variations of the value. To understand how fuzzy matching and autocorrection are related to one another, see the [autocorrection documentation](https://cloud.ibm.com/docs/assistant?topic=assistant-autocorrectionautocorrection-vs-fuzzy-matching).







 Adding contextual entities 

Annotation-based entites are those for which you annotate occurrences of the entity in sample sentences to teach your assistant about the context in which the entity is typically used.

In order to train a contextual entity model, you can take advantage of your intent examples, which provide readily-available sentences to annotate.

This feature is generally available in English-language dialog skills and is available as a beta feature in French-langage dialog skills.
Log in to [IBM Cloud® CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) and select your account to run the ibmcloud resource tag-delete command for deleting only one or all of the unused tags.

The following example deletes the MyTag user tag:

ibmcloud resource tag-delete --tag-name MyTag





 Deleting unused tags by using the API 

You can delete tags by calling the [Global Search and Tagging - Tagging API](https://cloud.ibm.com/apidocs/taggingdelete-tag-all) as shown in the following sample requests. The allowed values for the tag_type query parameter are: user for user tags and access for access management tags.



 Deleting a tag 

Deleting an access management tag called project:myproject from the account:



* Curl
* Java
* Python
* Go
* Node



curl -X DELETE -H "Authorization: {iam_token}" -H "Accept: application/json" "https://tags.global-search-tagging.cloud.ibm.com/v3/tags/project:myproject?tag_type=access"

DeleteTagOptions deleteTagOptions = new DeleteTagOptions.Builder()
.tagName("env:example-access-tag")
.tagType("access")
.build();

Response<DeleteTagResults> response = service.deleteTag(deleteTagOptions).execute();
DeleteTagResults deleteTagResults = response.getResult();
System.out.println(deleteTagResults.toString());

delete_tag_results = global_tagging_service.delete_tag(
tag_name='env:example-access-tag',
tag_type='access').get_result()

print(json.dumps(delete_tag_results, indent=2))
* [Remove tags from images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes13jun2019_tags)



* [13 May 2019](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-13may2019)



* [End of support for Container Scanner](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes13may2019_cs)



* [2 April 2019](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-2apr2019)



* [General Availability of Container Image Security Enforcement](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes2apr2019_cise)



* [14 March 2019](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-14mar2019)



* [IBM Cloud Activity Tracker available for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes14mar2019_at)



* [25 February 2019](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notesregistry-25feb2019)



* [New domain names](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes25feb2019_dns)
* [Adding IAM API key policies to control access to resources](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes25feb2019_secrets)
* [New region in ap-north](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes25feb2019_ap-north)
8.530665755719783,
18
],
"fields": {
"city": "New York, N.Y.",
"lat": 40.78333333333333,
"lon": -73.96666666666667
}
},
{
"id": "city177",
"order":
13.756343205985946,
17
],
"fields": {
"city": "Newark, N.J.",
"lat": 40.733333333333334,
"lon": -74.16666666666667
}
},
{
"id": "city178",
"order":
113.53603438866077,
26
],
"fields": {
"city": "New Haven, Conn.",
"lat": 41.31666666666667,
"lon": -72.91666666666667
}
}
]
}
Show more





 Highlighting search terms 

Sometimes it is useful to get the context in which a search term was mentioned so that you can show more emphasized results to a user.

To get more emphasized results, add the highlight_fields parameter to the search query. Specify the field names for which you would like excerpts, with the highlighted search term returned.

By default, the search term is placed in <em> tags to highlight it, but the highlight can be overridden by using the highlights_pre_tag and highlights_post_tag parameters.

The length of the fragments is 100 characters by default. A different length can be requested with the highlights_size parameter.

The highlights_number parameter controls the number of fragments that are returned, and defaults to 1.

In the response, a highlights field is added, with one subfield per field name.

For each field, you receive an array of fragments with the search term highlighted.
* column_header_texts_normalized: An array of values, where each value is the normalized text from a column header for this body cell.
* attributes: An array that identifies document attributes. Each object in the array consists of three elements:



* type: The type of attribute. Possible values are Address, Currency, DateTime, Duration, Location, Number, Organization, Percentage, and Person.
* text: The text that is associated with the attribute.
* location: The location of the attribute as defined by its begin and end indexes.





* key_value_pairs: An array that specifies any key-value pairs in tables in the input document. For more information, see [Understanding key-value pairs](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-understanding_tableskey-value-pairs).



* key: An object that specifies a key for a key-value pair.



* cell_id: The unique ID of the key in the table.
* location: The location of the key cell in the input document as defined by its begin and end indexes.
* text: The text content of the table cell without HTML markup.



* value: An array that specifies the value or values for a key-value pair.



* cell_id: The unique ID of the value in the table.
* location: The location of the value cell in the input document as defined by its begin and end indexes.
* text: The text content of the table cell without HTML markup.





* contexts: A list of related material that precedes and follows åthe table, excluding its section title, which is provided in the section_title field. Related material includes related sentences; footnotes; and sentences from other parts of the document that refer to the table. The list is represented as an array. Each object in the array consists of the following elements:



* text: The text contents of a related material from the input document, without HTML markup.
* location: The location of the related material in the input document as defined by its begin and end indexes.









 Notes on the table output schema