Research: Case sensitivity gear option.

[roamye]

Problem Description: The gear option, case sensitivity, is only applied at the top level rather than all levels which causes an issue for multi-word entries in the single field.

This issue will serve as a research ticket to determine how to fix this issue.

Expected Behavior/Solution: TBD - Conduct research onto why this is happening at the top level instead of all levels.

Requirements: TBD

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

• [ ] Wireframe/Mockup - Mike
• [ ] Committee discussions - Sarah
• [ ] Feasibility/Team discussion - Sarah
• [ ] Backend requirements - TBD
• [ ] Frontend requirements- TBD
• [ ] Are new regression tests required for QA - Amy
• [ ] Questions
• List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

• TST: https://lux.collections.yale.edu/view/results/objects?q=%7B%22AND%22%3A%5B%7B%22name%22%3A%22andy+Warhol%22%2C%22_options%22%3A%5B%22unstemmed%22%2C%22unwildcarded%22%2C%22case-sensitive%22%5D%7D%5D%7D

Dependencies/Blocks: N/A

Related Github Issues: N/A

Related links: Bugherd: https://www.bugherd.com/projects/284041/tasks/2613

Wireframe/Mockup: N/A

[clarkepeterf]

@roamye although labels and help text for search terms are handled in MarkLogic, the labels and help text for "Equals" and "Not Equals" are handled in the Frontend. This can all be done in https://github.com/project-lux/lux-frontend/issues/402

[roamye]

ahhh okay, I will re-purpose this issue then with something else. @clarkepeterf

[brent-hartwig]

@roamye and @clarkepeterf, if this ticket is asking for a user-specified case-sensitivity option to cascade down, I think this is where it could be implemented. Note that parentSearchTerm is a parameter into _parseAndValidateTerm.

[roamye]

@brent-hartwig - I am unsure what this means "user-specified case-sensitivity option to cascade down". Could you reiterate?

[roamye]

Meeting with Brent 10/16: Marklogic can support this. Our custom code is what is causing this behavior. We have code where if a query can be tokenized to tokenize it.

You cannot do a lower case case-sensitivity search because when the terms are indexed, it will always index those terms as lower case. When you do a phrase "" it honors this case sensitivity. (but not lower case).

You have to have at least one upper case to have a case sensitive search.

@brent-hartwig - to provide documentation on the ML limitations.