My customer IP Infusion has struggled with the library and recommendation engine as their use case frequently involves RFC code/protocols such as:
RFC-1034 or "draft-ietf-bfd-v4v6-1hop-04.txt"
While this may not be the only operative search term in the question, it often is the key detail needed to call up the specific response.
Since hyphens are not supported for search, the system is instead searching on just "RFC" or just "Draft" "v4v6" and so on and that brings back many unrelated search results that are not useful. It prompts the team to have to very specifically manually search frequently and it significantly impedes the usefulness of our search/recommendation functions and it has impacted adoption.
Our current workaround is to try and use Alternate Questions to improve searchability but since hyphens aren't considered for search, the impact of the workaround is limited at best.
My idea is to build in targeted/conditional support for hyphens such that the customers with the need for it can enable hyphens as searchable. Ideally, we can place limits such that the hyphen will only be considered if it directly beside other characters like RFC-1034 and not when it's a standalone hyphen in the content like someone was using an em-dash.
Targeted support of this nature I believe would be a boost to our InfoSec use case broadly and impact more than just my customer.
