project-lux / lux-marklogic

Code, issues, and resources related to LUX MarkLogic
Other
3 stars 2 forks source link

Provide convenient means to override select search options, from the simple search context (from 902) #32

Open gigamorph opened 4 months ago

gigamorph commented 4 months ago

Problem Description: Excerpts from this Teams conversation follow.

SP: Use case: find all LUX records that mention the novel The Bluest Eye with a keyword search for "the bluest eye"

SP: Current functionality kind of stinks for this: Keyword search stems and wildcards a quoted search, so that is basically useless here in a book with such common words. I can use advanced search/exact match, but I would have to redo to the search for each entity type.

RS: Except for every time you want it to be exact, there's at least 10 times you want it to do stemming

[Examples of when you would not want exact]

SP: Agree on those, but it's frustrating: there's no way to get these kind of results in simple search. Can't add morrison because she's not in the object records.

There are ways that we could support overriding individual or a set of search options, such as:

  1. The MarkLogic grammar's term-level search options syntax, such as "blue eyes" [unstemmed]
  2. Utilizing the MarkLogic grammar's bound tags feature, such as exact:"blue eyes"
  3. Using an uncommon set of characters instead of quotes, such as [blue eyes] or <blue eyes>

If the choice we make does not specify multiple options but must override multiple options, we'll need to define what those are.

We need to ensure that the same results are returned upon switching from simple search to advanced search. We may not have to support going from advanced to simple search.

Expected Behavior/Solution: TBD

Requirements: TBD

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

- [ ] Wireframe/Mockup - Heather - [ ] Committee discussions - Sarah

UAT/LUX Examples:

Dependencies/Blocks:

Related Github Issues:

Related links: