{"id":11381,"date":"2016-11-28T13:26:00","date_gmt":"2016-11-28T13:26:00","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?page_id=11381"},"modified":"2021-01-19T11:33:49","modified_gmt":"2021-01-19T18:33:49","slug":"accuracy-keyword-based-classification","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/install-and-upgrade\/4-1-0-0\/accuracy-keyword-based-classification\/","title":{"rendered":"Accuracy | Keyword Based Classification"},"content":{"rendered":"
<\/p>\n
In Keyword Classification, unique operator checks for uniqueness in all page level field values and operator returns true only for first occurrence of the page level field value.<\/p>\n
<\/p>\n
This is changed to check for uniqueness only with last occurrence of page level field value, instead of uniqueness across all occurrences i.e. operator will return true, if the current page level field value is different from previous value for this page level field.<\/p>\n
<\/p>\n
These changes would correct the following issue:<\/p>\n
<\/p>\n
Previous Unique Operator Implementation:<\/strong><\/p>\n For example, if using invoice number examples (1111, 1111, 1111, 2222, 2222, 3333, 3333, 1111, 1111) will result in the following breakdown:<\/p>\n Document One Document Three <\/p>\n Improved Unique Operator Implementation:<\/strong><\/p>\n For example, if using invoice number examples (1111, 1111, 1111, 2222, 2222, 3333, 3333, 1111, 1111) will result in the following breakdown:<\/p>\n Document One Document Two Document Three Document Four<\/p>\n 1111 <\/p>\n<\/div>\n","protected":false},"featured_media":0,"parent":23804,"menu_order":24,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"yoast_head":"\n
\n1111
\n1111
\n1111
\nDocument Two
\n2222
\n2222<\/p>\n
\n3333
\n3333
\n1111
\n1111<\/p>\n
\n1111
\n1111
\n1111<\/p>\n
\n2222
\n2222<\/p>\n
\n3333
\n3333<\/p>\n
\n1111<\/p>\n