vania-janet/multiturn-rag-retrieval-data huggingface dataset:
A tag consists of multiple parts:

X.Y.Z-<date>.[hash]

Where



* X represents the major version of an image.
* Y represents the minor version of an image.
* Z represents an incremental ID that determines the latest patched minor version.
* <date> represents the date that the image is built and available. The format is YYYYMMDD.
* [hash] represents the digest (manifest) of the container image. It is a unique SHA-256 hash.



The following table outlines the tagging convention adopted and the agent update behavior:



Table 1. logging agent tags explained

 Tag Logging agent auto-update enabled More info 

 X YES The logging agent auto-updates when a new minor version releases. <br>The logging agent does not update to a new major version, as these updates may require configuration changes. 
 X.Y YES The logging agent auto-updates when a new patch version is released. 
 X.Y.Z YES The logging agent auto-updates when a new vulnerability fix is released. The agent code does not change, but the included libraries have vulnerability fixes. 
 X.Y.Z-<date>.[hash] NO The logging agent never updates. If you use this tag, make sure you are watching for new agent releases that have vulnerability fixes. 



Depending on the tag that you use, you must consider upgrading the logging agent image in your DevOps maintenance plan, to resolve vulnerabilities and apply agent enhancements and agent bug fixes. For example:



* In a development environment, you can use a tag X and let auto-updates happen as new minor versions are released.
* In a staging environment, you might consider using a tag X.Y so auto-updates happen when a new patch is released.
* In a production environment, you can use the tag X.Y.Z so that auto-updates happen when a new vulnerability fix is released.
* For highly regulated environments, you should use the tag X.Y.Z-<date>.[hash]. Notice that you will have to check periodically for vulnerability fixes, patches, and minor version releases to keep the agent free of issues.
Although, it might be difficult to know which field to search later for information that you need if the field names don't match the content. The default set are representative field types that are meant to help you get started. Only the text and table fields have special significance. Do not use them to identify anything other than text and tables.



Default field labels

 Field Definition 

 answer In a question-and-answer pair (often in an FAQ), the answer to the question. 
 author Name of author or authors. 
 footer Use this tag to denote meta-information about the document (such as the page number or references), that appear at the end of the page. 
 header Use this tag to denote meta-information about the document that appears at the start of the page. 
 question In a question-and-answer pair (often in an FAQ), the question. 
 subtitle The secondary title of the document. 
 table_of_contents Use this tag on lists in the document table of contents. 
 text By default, every block of text in the document is labeled as text. Apply different labels only to blocks of text with special meaning. 
 title The main title of the document. 
 table Use this tag to annotate tables in your document. 
 image Images are not shown in the document preview. If you enable OCR, text from an image or diagram is displayed in the preview instead. If you want to prevent text from some images from being included in search results, tag the image text as an image. You can exclude the image field from the index later. 







 Reusing SDU models 

After you define a model with the SDU tool, you can save it and reuse it in other collections by exporting it from one collection and importing it to another.

To reuse a model, complete the following steps:



1. Export the model that you want to reuse. From the SDU toolbar menu, select Export model.

Zoom

!
Required field - input either as a flag or from file.

--rules RULES
: List of rules that determine whether the entity is part of the segment. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the segment. Required field - input either as a flag or from file.

--file FILE
: Input through a file. File format Supported - JSON





 Example 

To create a collection with name sample using flags ([click here](https://cloud.ibm.com/docs/app-configuration-cli-plugin?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac segment create --name "IBM Employees" --segment_id "ibm_employees" --description "IBM Employees Segment" --tags "ibm" --rules '[{"attribute_name": "email", "operator": "endsWith", "values": "@ibm.com"]}]'



 Output 

The command returns the following output:

name IBM Employees
segment_id ibm_employees
description IBM Employees Segment
created_time 2021-02-02T19:04:22Z
updated_time 2021-02-02T19:04:22Z









 ibmcloud ac segment get 

You can get a segment, by using the command:

ibmcloud ac segment get --segment_id SEGMENT_ID [--include INCLUDE]



 Command options 

--segment_id SEGMENT_ID
: Segment ID.

--include INCLUDE (optional)
: Instructs to include the feature and property details based on the segments association.





 Example 

To get a segment with ID ibm_employees, run the following command:

ibmcloud ac segment get --segment_id ibm_employees



 Output 

The command returns the following output:

segment_id description features created_time updated_time name attribute_name operator values
: Domain portion of the FQDN.

-g, --tag
: Tags to set or empty string to remove all.

-F, --userfile
: Read user data from a file.

-u, --userdata
: User defined metadata string.

-p, --public-speed
: Public port speed, options are: 0,10,100,1000,10000.

-v, --private-speed
: Private port speed, options are: 0,10,100,1000,10000.





 ibmcloud sl hardware list 

List hardware servers:

ibmcloud sl hardware list [OPTIONS]

Command options:

-c, --cpu
: Filter by number of CPU cores.

-D, --domain
: Filter by domain.

-H, --hostname
: Filter by host name.

-d, --datacenter
: Filter by datacenter.

-m, --memory
: Filter by memory in GB.

-n, --network
: Filter by network port speed in Mbps.

-g, --tag
: Filter by tags. You can specify more than one.

-p, --public-ip
: Filter by public IP address.

-v, --private-ip
: Filter by private IP address.

-o, --order
: Filter by the ID of the order that purchased the hardware server.

--owner
: Filter by ID of the owner.

--sortby
: Column to sort by, default:hostname, option:id,guid,hostname,domain,public_ip,private_ip,cpu,memory,os,datacenter,status,ipmi_ip,created,created_by.

--column
: Column to display, options are: id,hostname,domain,public_ip,private_ip,datacenter,status,guid,cpu,memory,os,ipmi_ip,created,created_by,tags. This option can be specified multiple times.





 ibmcloud sl hardware power-cycle
Key Container <br><br> * <br><br><br> Tag Required 
 Value String <br><br> * <br><br><br> Tag Required 



Tags must comply with the following restrictions:



* An object can have a maximum of 10 tags
* For each object, each tag key must be unique, and each tag key can have only one value.
* Minimum key length - 1 Unicode characters in UTF-8
* Maximum key length - 128 Unicode characters in UTF-8
* Maximum key byte size - 256 bytes
* Minimum value length - 0 Unicode characters in UTF-8 (Tag Value can be empty)
* Maximum value length - 256 Unicode characters in UTF-8
* Maximum value byte size - 512 bytes
* A Tag key and value may consist of US Alpha Numeric Characters (a-zA-Z0-9), and spaces representable in UTF-8, and the following symbols: !, _, ., , , (, ), -, :
* Tag keys and values are case-sensitive
* ibm: cannot be used as a key prefix for tags



Example request

This is an example of adding a set of tags to an object.

PUT /apiary/myObject?tagging HTTP/1.1
Authorization: Bearer {token}
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud
Content-Length: 119

PUT /apiary/myObject?tagging HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud
Content-Length: 128

<Tagging>
<TagSet>
<Tag>
<Key>string</Key>
<Value>string</Value>
* importance: The importance of the party. Possible values are Primary for a primary party and Unknown for a non-primary party.
* addresses: An array that identifies addresses.



* text: An address.
* location: The location of the address as defined by its begin and end indexes.



* contacts: An array that defines the names and roles of contacts that are identified in the input document.



* name: The name of a contact.
* role: The role of the contact.



* mentions: An array that lists all mentions of the party in the input document.



* text: The name of the party.
* location: The location of the mention as defined by its begin and end indexes.





The values of role that can be returned for contracts include, but are not limited to:



 role Description 

 Buyer The party responsible for paying for the goods or services that are listed in the contract. 
 End User The party who interacts with the provided goods or services, explicitly distinguished from the Buyer. 
 None No party was identified for the element. 
 Supplier The party responsible for providing the goods or services that are listed in the contract. 







 Categories 

The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.

The categories array defines the subject matter of the sentence. Currently supported categories include:



 categories Description 

 Amendments Elements that specify changes to the contract after it is signed, or alterations to a standard contract. Includes discussions of the conditions for changing the terms of a contract. 
 Asset Use Elements that refer to how one party might or might not use the assets of another party. This specifically applies to one party having access to or using assets such as licenses, equipment, tools, or personnel of the other party while in the process of conducting their duties under the agreement, including permissions and restrictions thereon. This does not extend to specifications of a party's obligations or rights regarding any purchased goods, services, licenses, etc., as those are the party's own assets, rather than assets of another party. 
 Assignments Elements that describe the transfer of rights, obligations, or both to a third party.
The index numbers indicate the beginning and ending positions, respectively, of the element as character numbers in the HTML document that the service created from your input document.
* text: The text of the element.
* types: An array that describes what the element is and whom it affects.



* label: An object that defines the type by using a pair of the following elements:



* nature: The type of action the sentence requires. Current values are Definition, Disclaimer, Exclusion, Obligation, and Right.
* party: A string that identifies the party to whom the sentence applies.



* provenance_ids: An array of one or more hashed values that you can send to IBM to provide feedback or receive support.



* categories: An array that lists the functional categories into which the element falls; in other words, the subject matter of the element.



* label: A string that lists the identified category. You can find a list of [categories](https://cloud.ibm.com/docs/discovery?topic=discovery-contract_parsingcontract_categories) in [Understanding element classification](https://cloud.ibm.com/docs/discovery?topic=discovery-contract_parsing).
* provenance_ids: An array of one or more hashed values that you can send to IBM to provide feedback or receive support.



* attributes: An array that identifies document attributes. Each object in the array consists of three elements:



* type: The type of attribute. Possible values are Currency, DateTime, DefinedTerm, Duration, Location, Number, Organization, Percentage, and Person as described at [Attributes](https://cloud.ibm.com/docs/discovery?topic=discovery-contract_parsingattributes).
* text: The text that is associated with the attribute.
* location: The location of the attribute as defined by its begin and end indexes.





* effective_dates: An array that identifies the date or dates on which the document becomes effective.



* confidence_level: The confidence level of the identification of the effective date. Possible values include High, Medium, and Low.
* text: An effective date, which is listed as a string.
[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 

Log in to [IBM Cloud® CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) and select your account to run the appropriate CLI command.

To attach a tag to a resource, use the [ibmcloud resource tag-attach](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_tag_attach) command. The allowed values for tag-type are user for user tags and access for access management tags. The default value is user. The following example shows how to attach a user tag that is called MyTag to a resource named MyResource:

ibmcloud resource tag-attach --tag-names MyTag --resource-name 'MyResource'

An example for attaching an access management tag called project:myproject to a resource named MyResource:

ibmcloud resource tag-attach --tag-names project:myproject --resource-name 'MyResource' --tag-type access 





 Detaching tags from a resource by using the CLI 

To detach a tag from a resource, use the [ibmcloud resource tag-detach](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_tag_detach) command. An example to detach a user tag called MyTag from a resource named MyResource:

ibmcloud resource tag-detach --tag-names MyTag —resource-name 'MyResource'
Since our example document text is only one sentence, there are no related concepts, so Concept tagging returns the following concepts:

"text": "Acme Corporation"
"text": "factory"

Since the Keyword extraction enrichment identifies content typically used when indexing data, generating tag clouds, or searching, Keyword extraction returns the following keywords:

"text": "Acme Corporation"
"text": "new factory"
"text": "stockholders"
"text": "Atlanta"
"text": "Georgia"

These enrichments work together to help you build better queries.







 Customizing field extraction 



 Using CSS selectors to extract fields from HTML documents 

You can extract fields from HTML documents using the Discovery API.

If you are ingesting well-formed HTML, you can use CSS selectors to extract JSON fields and then apply enrichments to the extracted fields. Edit your configuration file to enable this feature. Specifically, add an extracted_fields element to the conversions/html hierarchy, then specify field names, CSS selectors, and field types, as follows:

{
"name": "Extract JSON config",
"description": "New configuration enabling extraction of JSON fields from HTML",
"conversions": {
...
"html": {
...
"extracted_fields": {
"{field_name_1}": {
"css_selector": "{CSS_selector_expression_1}",
"type": "{field_type}"
},
...
"{field_name_N}": {
"css_selector": "{CSS_selector_expression_N}",
"type": "{field_type}"
}
}
...
}
}
}
Show more

Specify values for the new fields as follows:



* field_name — The name of the field that you want to add to the JSON output.
<RetainUntilDate>2023-04-12T23:01:00.000Z</RetainUntilDate>
</Retention>

Example response

HTTP/1.1 200 OK
Date: Wed, 5 Oct 2020 15:39:38 GMT
X-Clv-Request-Id: 7afca6d8-e209-4519-8f2c-1af3f1540b42
Accept-Ranges: bytes
Content-Length: 0

--------------------

--------------------





 Add tags to an object 

A PUT issued to an object with the proper parameters creates or replaces a set of key-value tags associated with the object.

Not all operations are supported in Satellite environments. For details, see [supported Satellite APIs](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-apis-cos-satellite)

Syntax

PUT https://{endpoint}/{bucket-name}/{object-name}?tagging path style
PUT https://{bucket-name}.{endpoint}/{object-name}?tagging virtual host style

Payload Elements

The body of the request must contain an XML block with the following schema:



 Element Type Children Ancestor Notes 

 Tagging Container TagSet <br><br> * <br><br><br> Required 
 TagSet Container Tag Tagging Required 
 Tag String Key, Value TagSet Required 
 Key Container <br><br> * <br><br><br> Tag Required 
 Value String <br><br> * <br><br><br> Tag Required 



Tags must comply with the following restrictions:



* An object can have a maximum of 10 tags
* For each object, each tag key must be unique, and each tag key can have only one value.
* Minimum key length - 1 Unicode characters in UTF-8
* Maximum key length - 128 Unicode characters in UTF-8
"type" : string,
"text" : string,
"location" : {
"begin" : int,
"end" : int
}
},
...
]
},
...
],
"key_value_pairs":
{
"key": {
"cell_id": string,
"location": {
"begin": int,
"end": int
},
"text": string
},
"value": {
"cell_id": string,
"location": {
"begin": int,
"end": int
},
"text": string
},
...
]
},
...
],
"contexts":
{
"text": string,
"location": {
"begin": int,
"end": int
}
},
...
]
}
]
}
Show more





 Schema arrangement 

The schema is arranged as follows.



* tables: An array that defines the tables that are identified in the input document.



* location: The location of the current table as defined by its begin and end indexes in the input document.
* text: The textual contents of the current table from the input document without associated markup content.
* section_title: If identified, the location of a section title contained in the current table. Empty if no section title is identified.



* text: The text of the identified section title.
* location: The location of the section title in the input document as defined by its begin and end indexes.



* title: If identified, the title or caption of the current table of the form Table x.: .... Empty when no title is identified. When present, the title is excluded from the contexts array of the same table.



* location: The location of the title in the input document as defined by its begin and end indexes.
* An [IAM API key](https://cloud.ibm.com/docs/cloud-object-storage/iam?topic=cloud-object-storage-iam-overview) with Writer access to your Object Storage bucket or instance
* Either existing or new objects that will have tags applied to them.







 Reading tags 

Tags are accessible throughout an instance with the proper permissions. While the true organizational power of using tags as an organizational principle scales with you, you can access tags on an individual basis as well.

Log in to the [console](https://cloud.ibm.com/), selecting your instance of IBM Cloud Object Storage and your bucket where your data is represented. After you've uploaded files to your bucket, you can view and manage your tags right in place. Place the cursor over the ellipses at the end of any row representing your data (stored as an object), and select "Manage your tags" from the options in the menu.

![Manage your tags](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/object-manage-tags.jpg)

A properly formed and authenticated "GET" request with the ?tagging query paramter is all that is required for accessing the tags for your objects using curl. The examples here use bearer tokens generated using [this example](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-curlcurl-token). In addition to the bucket identifier and object key, you will also need the correct [endpoint](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints). The resulting XML object is also shown, where the "Tag" element will be repeated for each tag assigned to the object. If there are no tags, the response will return XML with an empty element, <TagSet />.
There is only one 'TagSet' element for each object, and the 'PUT' command will replace any existing metadata with the values you specified.

curl -X "PUT" "https://s3.test.cloud-object-storage.sample.appdomain.cloud/taggingtest/example-file.csv?tagging" -H "Authorization: bearer ...iOiIyMDIwMTIwNzE0NDkiLCJh..." -H "ibm-service-instance-id: 7nnnnn52-2nn0-nna9-bann-7nnnnn4cc4e7" --data "<Tagging><TagSet><Tag><Key>source</Key><Value>text</Value></Tag></TagSet></Tagging>"





 Editing tags 

Once your objects have been tagged, over time it may become necessary to modify them.

In order to edit the tags using the graphic interface, you will have to log into the console and access your objects as described previously. Once you've clicked on the "Manage Tags" option, simply change the contents of the form fields. Remember to press "Save" when complete.

![Save tags when complete](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/object-save-tags.jpg)

Your requests must be authenticated in order to tag your data. Also, you will have to programmatically keep any old tags while updating your objects with new information. The example shown repeats the tags from the previous examples while adding a new tag.

Remember that performing "PUT" operations involving tags will overwrite any current tags.
<br><br> * Number<br> * Currency<br> * Percent<br><br><br> <br><br> * is defined<br> * is not defined<br> * is equal to (==)<br> * is not equal to (≠)<br> * is less than (<)<br> * is less than or equal to (<=)<br> * is greater than (>)<br> * is greater than or equal to (>=)<br><br><br> 
 <br><br> * Date<br><br><br> <br><br> * is defined<br> * is not defined<br> * is on (also allows specific day of the week)<br> * is not on<br> * is before<br> * is after<br> * is on or before<br> * is on or after<br><br><br> 
 <br><br> * Time<br><br><br> <br><br> * is defined<br> * is not defined<br> * is at<br> * is not at<br> * is before<br> * is after<br> * is at or before<br> * is at or after<br><br><br> 
 <br><br> * Free text<br><br><br> <br><br> * is<br> * is not<br> * contains<br> * does not contain<br> * matches<br> * does not match<br><br><br>