Case Insensitive Search - Revision history

Jderrick: A series of small fixes - referenced IBM CMOD and moved table of contents.

2017-06-16T04:22:51Z

A series of small fixes - referenced IBM CMOD and moved table of contents.

← Older revision		Revision as of 04:22, 16 June 2017
Line 1:		Line 1:
			{{TOCright}}
	== Case Insensitive Search ==		== Case Insensitive Search ==

Jderrick: /* Introduction */

2017-06-16T04:22:05Z

Introduction

← Older revision		Revision as of 04:22, 16 June 2017
Line 3:		Line 3:
	=== Introduction ===		=== Introduction ===

	When loading data into CMOD with the built-in Indexers like [[Glossary#OnDemand_Indexing_Tools\|ACIF]] or the [[Glossary#OnDemand_Indexing_Tools\|PDF Indexer]], some data like [[Customer statements]], [[Invoices]] or [[Statements]] will be generated as 'Mixed Case', that is, containing both uppercase and lowercase characters. OnDemand Administrators might index the data as it appears in the document, but end-users could search for the same word, with different capitalization -- and this presents a problem. Searching for 'smith' or 'SMITH' doesn't match 'Smith', as it might appear in a report, statement or invoice, frustrating the attempt to find data on the server.		When loading data into IBM CMOD with the built-in Indexers like [[Glossary#OnDemand_Indexing_Tools\|ACIF]] or the [[Glossary#OnDemand_Indexing_Tools\|PDF Indexer]], some data like [[Customer statements]], [[Invoices]] or [[Statements]] will be generated as 'Mixed Case', that is, containing both uppercase and lowercase characters. OnDemand Administrators might index the data as it appears in the document, but end-users could search for the same word, with different capitalization -- and this presents a problem. Searching for 'smith' or 'SMITH' doesn't match 'Smith', as it might appear in a report, statement or invoice, frustrating the attempt to find data on the server.

	=== Explanation ===		=== Explanation ===

Jderrick: /* Resulting Issues */

2017-06-16T04:21:43Z

Resulting Issues

← Older revision		Revision as of 04:21, 16 June 2017
Line 19:		Line 19:
	=== Resulting Issues ===		=== Resulting Issues ===

	If the data you're indexing, searching for, and storing in CMOD requires case-sensitivity, there is no good solution to this issue, and end users should be instructed to pay close attention to proper capitalization.		If the data you're indexing, searching for, and storing in IBM CMOD requires case-sensitivity, there is no good solution to this issue, and end users should be instructed to pay close attention to proper capitalization.

	The capitalization of a field cannot be changed after an Application Group has been created. It is possible to update database tables manually, but this is not supported by IBM.		The capitalization of a field cannot be changed after an Application Group has been created. It is possible to update database tables manually, but this is not supported by IBM.
Line 27:		Line 27:
	Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually.		Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually.

	An IBM Developerworks article exists on [https://www.ibm.com/developerworks/data/library/techarticle/0203adamache/0203adamache.html implementing case-insensitivy in DB2], but it's not clear how this can be integrated into Content Manager OnDemand to provide the desired functionality.		An IBM Developerworks article exists on [https://www.ibm.com/developerworks/data/library/techarticle/0203adamache/0203adamache.html implementing case-insensitivy in DB2], but it's not clear how this can be integrated into IBM Content Manager OnDemand to provide the desired functionality.

Jderrick: Added article on DB2 case insensitvity.

2016-03-09T17:01:30Z

Added article on DB2 case insensitvity.

← Older revision		Revision as of 17:01, 9 March 2016
Line 26:		Line 26:

	Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually.		Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually.

			An IBM Developerworks article exists on [https://www.ibm.com/developerworks/data/library/techarticle/0203adamache/0203adamache.html implementing case-insensitivy in DB2], but it's not clear how this can be integrated into Content Manager OnDemand to provide the desired functionality.

Jderrick: Fixed broken internal links.

2015-04-01T16:58:00Z

Fixed broken internal links.

← Older revision		Revision as of 16:58, 1 April 2015
Line 7:		Line 7:
	=== Explanation ===		=== Explanation ===

	By default, these index values are stored in the database as they appear in the report. In a [[Line Data]] report, all output might appear in "ALL CAPS", whereas a [[PDF]] or [[AFP]] statement might appear in "Mixed Case". The problem occurs when end users search for a term using the wrong 'case' of letters as described above. [[Content Manager OnDemand]] doesn't have the ability to perform "case-insensitve" searches that would give us what we'd expect to see. There are a few ways to resolve this issue.		By default, these index values are stored in the database as they appear in the report. In a [[Glossary#Acronyms\|Line Data]] report, all output might appear in "ALL CAPS", whereas a [[Glossary#Acronyms\|PDF]] or [[Glossary#Acronyms\|AFP]] statement might appear in "Mixed Case". The problem occurs when end users search for a term using the wrong 'case' of letters as described above. [[Introduction\|Content Manager OnDemand]] doesn't have the ability to perform "case-insensitve" searches that would give us what we'd expect to see. There are a few ways to resolve this issue.

	=== Solutions ===		=== Solutions ===

Jderrick: Mentioned manual database updates.

2015-04-01T16:53:41Z

Mentioned manual database updates.

← Older revision		Revision as of 16:53, 1 April 2015
Line 21:		Line 21:
	If the data you're indexing, searching for, and storing in CMOD requires case-sensitivity, there is no good solution to this issue, and end users should be instructed to pay close attention to proper capitalization.		If the data you're indexing, searching for, and storing in CMOD requires case-sensitivity, there is no good solution to this issue, and end users should be instructed to pay close attention to proper capitalization.

	The capitalization of a field cannot be changed after an Application Group has been created.		The capitalization of a field cannot be changed after an Application Group has been created. It is possible to update database tables manually, but this is not supported by IBM.

	Moving all characters to upper or lower makes it impossible to restore proper capitalization (McDonald, de Klock, Van Oster)		Moving all characters to upper or lower makes it impossible to restore proper capitalization (McDonald, de Klock, Van Oster)

	Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually.		Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually.

Jderrick: /* Introduction */

2015-01-17T03:05:19Z

Introduction

← Older revision		Revision as of 03:05, 17 January 2015
Line 3:		Line 3:
	=== Introduction ===		=== Introduction ===

	When loading data into CMOD with the built-in Indexers like [[Glossary#~~OnDemand Indexing Tools~~\|ACIF]] or the [[Glossary#PDF Indexer]], some data like [[Customer statements]], [[Invoices]] or [[Statements]] will be generated as 'Mixed Case', that is, containing both uppercase and lowercase characters. OnDemand Administrators might index the data as it appears in the document, but end-users could search for the same word, with different capitalization -- and this presents a problem. Searching for 'smith' or 'SMITH' doesn't match 'Smith', as it might appear in a report, statement or invoice, frustrating the attempt to find data on the server.		When loading data into CMOD with the built-in Indexers like [[Glossary#OnDemand_Indexing_Tools\|ACIF]] or the [[Glossary#OnDemand_Indexing_Tools\|PDF Indexer]], some data like [[Customer statements]], [[Invoices]] or [[Statements]] will be generated as 'Mixed Case', that is, containing both uppercase and lowercase characters. OnDemand Administrators might index the data as it appears in the document, but end-users could search for the same word, with different capitalization -- and this presents a problem. Searching for 'smith' or 'SMITH' doesn't match 'Smith', as it might appear in a report, statement or invoice, frustrating the attempt to find data on the server.

	=== Explanation ===		=== Explanation ===

Jderrick: /* Introduction */

2015-01-17T03:03:56Z

Introduction

← Older revision		Revision as of 03:03, 17 January 2015
Line 3:		Line 3:
	=== Introduction ===		=== Introduction ===

	When loading data into CMOD with the built-in Indexers (like [[ACIF]] or the [[PDF Indexer]], some data like [[Customer statements]], [[Invoices]] or [[Statements]] will be generated as 'Mixed Case', that is, containing both uppercase and lowercase characters. OnDemand Administrators might index the data as it appears in the document, but end-users could search for the same word, with different capitalization -- and this presents a problem. Searching for 'smith' or 'SMITH' doesn't match 'Smith', as it might appear in a report, statement or invoice, frustrating the attempt to find data on the server.		When loading data into CMOD with the built-in Indexers like [[Glossary#OnDemand Indexing Tools\|ACIF]] or the [[Glossary#PDF Indexer]], some data like [[Customer statements]], [[Invoices]] or [[Statements]] will be generated as 'Mixed Case', that is, containing both uppercase and lowercase characters. OnDemand Administrators might index the data as it appears in the document, but end-users could search for the same word, with different capitalization -- and this presents a problem. Searching for 'smith' or 'SMITH' doesn't match 'Smith', as it might appear in a report, statement or invoice, frustrating the attempt to find data on the server.

	=== Explanation ===		=== Explanation ===

Jderrick: Created page with "== Case Insensitive Search == === Introduction === When loading data into CMOD with the built-in Indexers (like ACIF or the PDF Indexer, some data like Customer st..."

2015-01-17T02:22:13Z

Created page with "== Case Insensitive Search == === Introduction === When loading data into CMOD with the built-in Indexers (like ACIF or the PDF Indexer, some data like Customer st..."

New page

== Case Insensitive Search ==

=== Introduction ===

When loading data into CMOD with the built-in Indexers (like [[ACIF]] or the [[PDF Indexer]], some data like [[Customer statements]], [[Invoices]] or [[Statements]] will be generated as 'Mixed Case', that is, containing both uppercase and lowercase characters. OnDemand Administrators might index the data as it appears in the document, but end-users could search for the same word, with different capitalization -- and this presents a problem. Searching for 'smith' or 'SMITH' doesn't match 'Smith', as it might appear in a report, statement or invoice, frustrating the attempt to find data on the server.

=== Explanation ===

By default, these index values are stored in the database as they appear in the report. In a [[Line Data]] report, all output might appear in "ALL CAPS", whereas a [[PDF]] or [[AFP]] statement might appear in "Mixed Case". The problem occurs when end users search for a term using the wrong 'case' of letters as described above. [[Content Manager OnDemand]] doesn't have the ability to perform "case-insensitve" searches that would give us what we'd expect to see. There are a few ways to resolve this issue.

=== Solutions ===

[[File:FieldCapitalization.gif|500px|thumb|right|A screen capture of the Application Group Configuration window, with the Field Information Tab selected, and the 'Case' pop-up menu highlighted.]]
By default, OnDemand chooses to store all values for field type 'String' as uppercase. The string "Smith" becomes "SMITH" in the database. Index values loaded into the database are converted to uppercase, and searches in folders are also converted to uppercase before database queries are performed.

=== Resulting Issues ===

If the data you're indexing, searching for, and storing in CMOD requires case-sensitivity, there is no good solution to this issue, and end users should be instructed to pay close attention to proper capitalization.

The capitalization of a field cannot be changed after an Application Group has been created.

Moving all characters to upper or lower makes it impossible to restore proper capitalization (McDonald, de Klock, Van Oster)

Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually.