Closed jduss4 closed 6 years ago
There may very well be issues with the encoding / URL, but it would appear that elasticsearch's default text field isn't set up to think about those characters in searches in some tests I have conducted. I'm closing this issue, as I am under the impression that most collections will not need special character searching, and for those that do, we will need to craft a new type of text field with different factories / considerations.
At the moment, characters like
[
fail to make it from orchid to the API. Investigate whether this is the API not handling the characters correctly, Elasticsearch itself unable to accommodate those characters, or whether it has more to do with how the character is being sent via a URL from orchid.Related to closed issue https://github.com/CDRH/api/issues/23