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

Enhance global and local search #438

Closed
SamuelHassine opened this issue Jan 22, 2020 · 3 comments
Closed

Enhance global and local search #438

SamuelHassine opened this issue Jan 22, 2020 · 3 comments
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@SamuelHassine
Copy link
Member

Problem to Solve

The search features in the OpenCTI platform is very basic.

Current Workaround

None.

Proposed Solution

We need to implement an intelligent search engine with autocomplete.

Additional Information

None.

@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Jan 22, 2020
@Fred-certeu
Copy link

Good point.
I wanted to create an issue on this matter.
For observables (for example), an advance search would be welcomed - combining:

  • value (equals or contains)
  • type
  • date (=, <, >)
  • creator

@csandu-certeu
Copy link

A couple of aspects to consider for the search:

  • currently the search is looking in all entities which is quite resource consuming; an option could perhaps be the possibility to split the search into:
    • search for indicators/observables
    • search for all other entities.

This way, if the user is not interested in searching for an observable/indicator, the platform won't consume resources to search those.

  • in case of searching multiple words, one thing that helps is wrapping the search term in between "". Ex: "ANTHROPOID SPIDER"

@SamuelHassine SamuelHassine added this to the Release 4.3.0 milestone Aug 21, 2020
@manonviallet
Copy link
Contributor

Ideas for the search field :

  • be able to save a search for later re-run ;
  • have a search history (who searched what) --> could be in the admin pannel

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

4 participants