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

[REQUEST] Optimize reference search algorithm #355

Open
erinehall opened this issue Nov 18, 2024 · 1 comment
Open

[REQUEST] Optimize reference search algorithm #355

erinehall opened this issue Nov 18, 2024 · 1 comment

Comments

@erinehall
Copy link

The search on the "Reference Manager" page inconsistently displays results. Sometimes searching for a token does not return the expected results, or relevant entries are listed far down on the list of results, making it difficult to find what the users need.

image

Solution:
Enhance the References search functionality to consistently return relevant results for all fields and improve the overall search experience.

Potential Solutions:

  1. Optimize the search algorithm to rank more relevant results (e.g., exact matches) higher in the results list.
  2. Implement smarter filtering to ensure searches for search names consistently return appropriate results.
  3. Display a preview or highlight matching text within the search results for easier identification.
@erinehall erinehall added the bug Something isn't working label Nov 18, 2024
@clemiller clemiller changed the title [BUG] [REQUEST] Optimize reference search algorithm Dec 5, 2024
@clemiller clemiller removed the bug Something isn't working label Dec 5, 2024
@clemiller
Copy link
Contributor

clemiller commented Dec 5, 2024

Couple of updates:

  1. Removed the bug label as the issue with the source_name query not returning relevant results was resolved back in September.
  2. Keeping this open as a new request to optimize the search query to rank relevant results higher in the list.
  3. Moving this issue to the REST API repo, as the search algorithm is handled by the backend.

@clemiller clemiller transferred this issue from center-for-threat-informed-defense/attack-workbench-frontend Dec 5, 2024
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