Federated searches in the content management system are
relatively disconnected from the upload concept and they depend on datamaps
for searches across repositories. If case insensitive search is chosen
in the user interface, the element in the search predicate would be
“switched” to the one described in the custom property and the search
key would be upper-cased.
About this task
For a case insensitive search, the configured datamap would
be provided with similar mappings called custom properties as described
for adding content.
Procedure
- Add a DataMap.
For example, SearchDM.
- Add an element corresponding to author_name for
the repository.
For example, AUTHOR_NAME_RESERVED.
- Ensure that the datatype defined for these attributes is STRING.
- Ensure that the
AUTHOR_NAME_RESERVED is searchable
and can be returned in a query.
- Ensure that the proper “Supported Operators” are chosen from the
screen.
- Add an element corresponding to author_name_up for
the repository.
For example, UPPER_OF_AUTHOR_NAME_RESERVED.
- Add a custom map between the two elements.
- Save the element and the configurations.
- Restart the Content Integrator so that the changes are
reflected.
- Log in to Product Master and navigate
to an item with a content management system type attribute and open
up the search window.
- Select the content management system attribute on the item
data entry screen. The content management search screen displays.
The dm_author_name is listed.
Note: Product Master adds
two new options for case-insensitive searching in the search operator
drop downs namely equal-ignorecase and like-ignorecase.
- Provide values for the element and choose one of the ignore
case options from the drop-down and search.
- The ignore case searches at the backend and is performed
against the UPPER_OF_AUTHOR_NAME_RESERVED element
and not the dm_author_name element.