Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exact search #11

Closed
fbstj opened this issue Jun 20, 2019 · 2 comments
Closed

exact search #11

fbstj opened this issue Jun 20, 2019 · 2 comments

Comments

@fbstj
Copy link

fbstj commented Jun 20, 2019

there's a number of concepts or entities in the books which are either using dictionary words or are very short. the old search tool allows regular expression to be used in place of a case-insensitive "dumb" string match. this allows us to find pages mentioning "Pattern" or "Honor" or worse "Red" or "Vo" or "Ka"

this may tie together with #4 or #6 to curate which chapters actually have those "special" terms in then

@fbstj
Copy link
Author

fbstj commented Jun 20, 2019

also be aware of Yelig-nar for example aka potential hyphenated or apostrophied terms amongs maybe others, and preferably the various different curly quotes wouldn't effect results (in either search term or haystack)

@marvin-roesch
Copy link
Owner

This is already addressed with the text.cs field for case sensitivity and the general behaviour of Elasticsearch (with my particular mapping strategy). Searches only show whole words by default, so searching Vo only brings up the character, not Vorinism or similar. If you want those kinds of substring searches, wildcards are the way to go.

As of eb4029c, users also can get an overview of the peculiarities of the search thanks to a help dialog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants