vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The following JSON passage shows the relevant section of the configuration to which you add CSS selector information.

{
"name": "Default Configuration",
"description": "The configuration used by default when creating a new collection without specifying a configuration_id.",
"conversions": {
...
"html": {
"exclude_tags_completely": [
"script",
"sup"
],
"exclude_tags_keep_content": [
"font",
"em",
"span"
],
"exclude_content": {
"xpaths": []
},
"keep_content": {
"xpaths": []
},
"exclude_tag_attributes": [
"EVENT_ACTIONS"
]
}
...
}
}
Show more

The following passage shows the configuration with a new name and description, as well as the location where you can specify CSS selectors.

{
"name": "Extract JSON config",
"description": "New configuration enabling extraction of JSON fields from HTML",
"conversions": {
...
"html": {
"exclude_tags_completely": [
"script",
"sup"
],
"exclude_tags_keep_content": [
"font",
"em",
"span"
],
"exclude_content": {
"xpaths": []
},
"keep_content": {
"xpaths": []
},
"exclude_tag_attributes": [
"EVENT_ACTIONS"
],
"extracted_fields": {
"{field_name_1}": {
"css_selector": "{CSS_selector_expression_1}",
"type": "{field_type}"
},
...
GET https://{bucket-name}.{endpoint}/{object-name}?tagging virtual host style

Example request

This is an example of reading a set of object tags.

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

GET /apiarymyObject?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: 0

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: 128

<Tagging>
<TagSet>
<Tag>
<Key>string</Key>
<Value>string</Value>
</Tag>
</TagSet>
</Tagging>

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





 Delete an object's tags 

A DELETE issued to a bucket with the proper parameters removes an object's tags.

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
extract.F.first as first, M.initial as middle, L.last as last
pattern ('Mr.'|'Ms.'|'Miss')? (<F.first> <M.initial>? <L.last>)
return group 0 as reference
and group 1 as salutation
and group 2 as name
from FirstName F, MiddleInitial M, LastName L;



* Regular expressions Use a regular expression extraction specification to identify matching patterns that are contained by the regular expression across the input text.
* Dictionaries Use the dictionary extraction specification to extract strings from input text that are contained in a dictionary of strings.
* Splits Use the split extraction specification to split a large span into several smaller spans.
* Blocks Use the blocks extraction specification to identify blocks of contiguous spans across input text.
* Part of speech Use the part-of-speech extraction specification to identify locations of different parts of speech across the input text.
* Sequence patterns Use the pattern extraction specification to perform pattern matching across an input document and other spans that are extracted from the input document.









 Regular expressions 

Use a regular expression extraction specification to identify matching patterns that are contained by the regular expression across the input text.



 Syntax 

regex[es] /<regex1>/
[and /<regex2>/ and ... and /<regex n>/]
[with flags '<flags string>']
on <token spec>] <name>.<column>
<grouping spec>





 Description 



* regex[es] /<regex1>/

Specifies the regular expressions to be used in the extraction. By default, AQL uses Perl syntax for regular expressions, which means that regular expression literals are enclosed in two forward slash (//) characters. Regular expression escape sequences take precedence over other escape characters. AQL allows regular expressions in SQL string syntax, so a regular expression for United States phone numbers can be expressed as either of the examples:

/d{3}-d{5}/

'\d{3}-\d{5}'
* [and /<regex2>/ and ...
* 24 - Common Suffix
* 140 - Proper Noun (Last Name)
* 141 - Proper Noun (First Name)
* 146 - Proper Noun (Person Name)
* 142 - Proper Noun (Organization)
* 144 - Proper Noun (Place Name)
* 143 - Proper Noun (Region)
* 145 - Proper Noun (Other)



* poscode (Korean)

Specifies a code that identifies the part of speech. The part of speech value is important for text tokenization and pre-annotation in languages like Korean that do not use white space to denote word boundaries.



* 10010 - Noun
* 10300 - Proper Noun (Last Name)
* 10310 - Proper Noun (First Name)
* 110360 - Proper Noun (Person Name)
* 10320 - Proper Noun (Organization)
* 10340 - Proper Noun (Place Name)
* 10330 - Proper Noun (Region)
* 10350 - Proper Noun (Other)



* surface

Specifies equivalent terms, also called surface forms. Repeat the lemma as a surface form and use a comma to separate multiple surface forms. If a surface form includes a comma, enclose the surface form in quotation marks.



For example:

lemma,poscode,surface
IBM,3,IBM Corp.,IBM,"International Business Machines, Inc."
Department of Energy,3,DOE,Department of Energy
premium,4,premium,premium-grade

Related concepts:

[Uploading resources from another workspace](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-exportimport)

Related tasks:

[Pre-annotating documents with a dictionary](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-preannotationwks_preannot)







 Adding dictionaries to a workspace 

Adding dictionaries is an optional step in creating a model. Dictionaries are helpful because they enable you to jump start the annotation process.



 About this task
},
{
"default": ""tag:test1", "tag:test2"]",
"description": "",
"name": "vpc_tags",
"type": "list(string)"
}
],
"variablestore":
{
"name": "sample_var",
"secure": true,
"value": "$SCHEMATICSSECRET$04$.KMS04&crn:v1:bluemix:public:kms:us-south:a/c19ef85117044059a3be5e45d6dc1cf6:0de40d7c-085d-4373-9083-bbe598d7c3a9:key:4e6e436a-e53f-423d-848d-a7af60335c1f&crn:v1:bluemix:public:kms:us-east:a/c19ef85117044059a3be5e45d6dc1cf6:4d336da6-914a-4d17-8dc6-dfd9da51a422:key:1987a798-d933-446f-af49-3df7de755269&eyJjaXBoZXJ0ZXh0IjoiMitWZXYveFdRc3VKTi9obnAvYWtBT0dDL0NDK0pTOGJYWk5VWGg3RHRVU2JXbFc0Rkx6SjlGRzVWN1U9IiwiaXYiOiJMMjFzRXNSSXFSYXl1VWh0IiwidmVyc2lvbiI6IjQuMC4wIiwiaGFuZGxlIjoiMWQ0ZWE1ODItY2ZmOS00ZDQ3LWE3OGQtYWJjZmQ5NDM0MjA1In0=.15c9468cde760d8bfbacaeed.e0f233aa99d32be8a146dfe0d07db4721c021df5d8cda989d4064996abae4fe6d3d5f3692c754d53ba438548bbecef6c42810b4a",
"type": "",
"description": "Description of sample_var"
},
{
"name": "sleepy_time",
"secure": false,
"value": "15",
"type": "",
"description": ""
}
],
"has_githubtoken": false
}
],
"runtime_data":
{
"id": "b44c147b-81fb-4e",
"engine_name": "terraform",
* [Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_registry)
* [Registry namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_namespace)
* [Repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_repository)
* [Tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag)
* [Untagged image](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_untagged)



* [Regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions)



* [Global registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_global)



* [Targeting the global registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_global_target)



* [Local regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_local)



* [Targeting a local region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_local_target)





* [Supported clients](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewsupport_clients)



* [Support for Docker](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewdocker)
* [Support for other clients](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewclients)









 Container Registry architecture and workload
* column_header_texts_normalized: If you provide customization input, the normalized version of the column header texts according to the customization; otherwise, the same value as column_header_texts.
* 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.



* 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.





* document_structure: An object that describes the structure of the input document.



* section_titles: An array that contains one object per section or subsection that is detected in the input document. Sections and subsections are not nested.
At run time, your assistant recognizes terms in the user input that exactly match the values or synonyms that you defined for the entity as mentions of that entity.
* Pattern entity: You define a category of terms as an entity (contact_info), and then one or more values in that category (email). For each value, you specify a regular expression that defines the textual pattern of mentions of that value type. For an email entity value, you might want to specify a regular expression that defines a text@text.com pattern.

At run time, your assistant looks for patterns matching your regular expression in the user input, and identifies any matches as mentions of that entity.
* System entity: Synonym entities that are prebuilt for you by IBM. They cover commonly used categories, such as numbers, dates, and times. You simply enable a system entity to start using it.







 Annotation-based method 

When you define an annotation-based entity, which is also referred to as a contextual entity, a model is trained on both the annotated term and the context in which the term is used in the sentence you annotate. This new contextual entity model enables your assistant to calculate a confidence score that identifies how likely a word or phrase is to be an instance of an entity, based on how it is used in the user input.



* Contextual entity: First, you define a category of terms as an entity (product). Next, you go to the Intents page and mine your existing intent user examples to find any mentions of the entity, and label them as such. For example, you might go to the buy_something intent, and find a user example that says, I want to buy a Coach bag. You can label Coach bag as a mention of the @product entity.

For training purposes, the term you annotated, Coach bag, is added as a value of the @product entity.

At run time, your assistant evaluates terms based on the context in which they are used in the sentence only. If the structure of a user request that mentions the term matches the structure of an intent user example in which a mention is labeled, then your assistant interprets the term to be a mention of that entity type.
Segments 

Use segments to define a group of users or resources based on rules. Feature flags can target segments to deliver variants of a feature based on the needs like beta launches and experiments.

By default, the Segments pane displays the list of segments that are created in the current App Configuration service instance along with Name of the segment, tags, and date of creation.

Zoom

![List of segments](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-segments-default.png)

Figure 1. List of segments



 Create a segment 

To create a segment, complete these steps:



1. In the App Configuration console, click Segments.
2. Click Create. The side-panel opens with fields for creating a new segment.

Zoom

![Create a segment](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-segments-create.png)

Figure 2. Creating a new segment
3. Provide the segment details:



* Name - name of the segment.
* Description - add a description of the segment, which is optional.
* Optionally, define Tags that are required to identify with the segment.
* Specify a rule for including users to a segment in the Include user attributes in segment. For further details about adding users to a segment, refer [here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-segmentsadding-users-to-segment).



4. Click Create.







 Adding user in a segment 

Attributes specify the context of a request that you want to be evaluated as part of a decision.
* [Example tagging scheme](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-tagging-resourcesshared-tagging-resources-example-scheme)
* [Related controls in IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-tagging-resourcesshared-tagging-resources-related-controls)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-tagging-resourcesshared-tagging-resources-next-steps)







 Networking 



 Networking for VPC reference architecture 

[VPC networking overview](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-overviewvpc-architecture-connectivity-overview)



* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-overviewnext-steps)



[Creating and connecting the management and workload VPCs](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-create-vpcsvpc-architecture-connectivity-create-vpcs)



* [Related controls in IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-create-vpcsrelated-controls)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-create-vpcsnext-steps)



[Connecting application provider to the management VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-managementvpc-architecture-connectivity-management)
* location: The location of the title in the input document as defined by its begin and end indexes.
* text: The text of the identified table title or caption.



* table_headers: An array of table-level cells applicable as headers to all the other cells of the current table. Each table header is defined as a collection of the following elements:



* cell_id: The unique ID of the cell in the current table.
* location: The location of the cell in the input document as defined by its begin and end indexes.
* text: The textual contents of the cell from the input document without associated markup content.
* row_index_begin: The begin index of the cell's row location in the current table.
* row_index_end: The end index of the cell's row location in the current table.
* column_index_begin: The begin index of the cell's column location in the current table.
* column_index_end: The end index of the cell's column location in the current table.



* row_headers: An array of row-level cells, each applicable as a header to other cells in the same row as itself, of the current table. Each row header is defined as a collection of the following items:



* cell_id: The unique ID of the cell in the current table.
* location: The location of the cell in the input document as defined by its begin and end indexes.
* text: The textual contents of the cell from the input document without associated markup content.
* text_normalized: If you provide customization input, the normalized version of the cell text according to the customization; otherwise, the same value as text.
* row_index_begin: The begin index of the cell's row location in the current table.
* row_index_end: The end index of the cell's row location in the current table.
* column_index_begin: The begin index of the cell's column location in the current table.
* column_index_end: The end index of the cell's column location in the current table.
* 24 - Common Suffix
* 140 - Proper Noun (Last Name)
* 141 - Proper Noun (First Name)
* 146 - Proper Noun (Person Name)
* 142 - Proper Noun (Organization)
* 144 - Proper Noun (Place Name)
* 143 - Proper Noun (Region)
* 145 - Proper Noun (Other)



* poscode (Korean)

Specifies a code that identifies the part of speech. The part of speech value is important for text tokenization and pre-annotation in languages like Korean that do not use white space to denote word boundaries.



* 10010 - Noun
* 10300 - Proper Noun (Last Name)
* 10310 - Proper Noun (First Name)
* 110360 - Proper Noun (Person Name)
* 10320 - Proper Noun (Organization)
* 10340 - Proper Noun (Place Name)
* 10330 - Proper Noun (Region)
* 10350 - Proper Noun (Other)



* surface

Specifies equivalent terms, also called surface forms. Repeat the lemma as a surface form and use a comma to separate multiple surface forms. If a surface form includes a comma, enclose the surface form in quotation marks.



For example:

lemma,poscode,surface
IBM,3,IBM Corp.,IBM,"International Business Machines, Inc."
Department of Energy,3,DOE,Department of Energy
premium,4,premium,premium-grade

Related concepts:

[Uploading resources from another workspace](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-exportimport)

Related tasks:

[Pre-annotating documents with a dictionary](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-preannotationwks_preannot)







 Adding dictionaries to a workspace 

Adding dictionaries is an optional step in creating a model. Dictionaries are helpful because they enable you to jump start the annotation process.



 About this task
Why do all the tags get deleted when I delete an image? 

You tried to delete an image from IBM Cloud® Container Registry by using the ibmcloud cr image-rm command and all the [tags](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag) that referenced that image got deleted too.

  What’s happening 

You deleted an image by using the ibmcloud cr image-rm command and all the tags within the same repository that referenced the image also got deleted.

  Why it’s happening 

Where multiple tags exist for the same image [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest) within a repository, the [ibmcloud cr image-rm](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_rm) command removes the underlying image and all its tags. If the same image exists in a different repository or namespace, that copy of the image is not removed.

  How to fix it 

If you want to remove a tag from an image, but leave the underlying image and any other tags, use the [ibmcloud cr image-untag](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_untag) command. For more information, see [Removing tags from images in your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_untag) and [Deleting images from your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove).
When a resource is tagged, it is visible to all users who have read access to the resource. However, to attach or detach a tag on a resource, certain access roles or permissions are required depending on the resource type and the tag type. For example, to attach user tags to any of the resources that are managed by using IAM, you must be assigned the Editor or Administrator role on the resource.

You can attach access management tags to IAM-enabled resources only.

For more information about the required access for other resources types, see [Tagging permissions](https://cloud.ibm.com/docs/account?topic=account-accesstagging-permissions).
* Where can I find my resources in the IBM Cloud console?

To view all of your resources, select from the following options:



* Click the Navigation menu icon ![Navigation Menu icon](https://cloud.ibm.com/icons/icon_hamburger.svg) > Resource List.
* Click the Navigation menu icon ![Navigation Menu icon](https://cloud.ibm.com/icons/icon_hamburger.svg) > Dashboard, and click any of the links that are listed in the Resource summary widget.



To view just your classic infrastructure resources, select from the following options:



* Click the Navigation menu icon ![Navigation Menu icon](https://cloud.ibm.com/icons/icon_hamburger.svg) > Classic Infrastructure.
* Click the Navigation menu icon ![Navigation Menu icon](https://cloud.ibm.com/icons/icon_hamburger.svg) > Dashboard, and click any of the links that are listed in the Classic infrastructure widget.



* What causes resource restorations to fail?

A resource restoration can fail if you try to restore a resource in a deleted resource group or the resource restoration request isn't submitted in time. Most requests must be submitted within 7 days.
* How do I retrieve details on a resource that is scheduled for reclamation?

After the instance is deleted from the console, you can view it in your account by using the CLI in the SCHEDULED state. The SCHEDULED state indicates that this instance is scheduled for reclamation.