<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Label Text API on</title><link>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/</link><description>Recent content in Label Text API on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/index.xml" rel="self" type="application/rss+xml"/><item><title>Handling Overlapping Conflicts</title><link>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/overlap/</link><pubDate>Tue, 20 Feb 2024 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/overlap/</guid><description>&lt;p>While classifying data, the providers may label an identical text under two different entities. This distinction arises from the detection strategies the classifiers adopt. Data Discovery handles these conflicts by applying certain rules on these conflicting entities.&lt;/p>
&lt;p>The rules for handling the conflicting entities are as follows:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>No overlap&lt;/strong>: If the two entities do not conflict, retain the results in the original form.&lt;/p>
&lt;p>For example, &lt;code>Jake Filbert lives in Connecticut&lt;/code>. If only &lt;em>Jake Filbert&lt;/em> is identified, the result will be labeled as &lt;code>[NAME] lives in Connecticut&lt;/code>.&lt;/p></description></item><item><title>Sample Response Default</title><link>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/output/sample_response_default/</link><pubDate>Tue, 20 Feb 2024 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/output/sample_response_default/</guid><description>{
&amp;ldquo;transform&amp;rdquo;: {
&amp;ldquo;text&amp;rdquo;: &amp;ldquo;[PERSON] lives at [LOCATION] [LOCATION], [LOCATION] [LOCATION], [LOCATION].&amp;rdquo;
}
}


&lt;p>The fields are described as follows:&lt;/p>


 




	






 






 &lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Name&lt;/th>
 &lt;th>Example Response&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>transform.text&lt;/td>
 &lt;td>[PERSON] lives at [LOCATION]..&lt;/td>
 &lt;td>The labed input text with classified entities listed by name in place of the original sensitive data&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table></description></item><item><title/><link>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/output/reseponse_fields_description_transform_label/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/output/reseponse_fields_description_transform_label/</guid><description>&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Name&lt;/th>
 &lt;th>Example Response&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>transform.text&lt;/td>
 &lt;td>[PERSON] lives at [LOCATION]..&lt;/td>
 &lt;td>The labed input text with classified entities listed by name in place of the original sensitive data&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table></description></item><item><title/><link>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/output/sample_response_with_details/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/data-discovery/2.0.0/docs/restapi/transform/text/output/sample_response_with_details/</guid><description/></item></channel></rss>