Open obigriffith opened 6 years ago
It may be best to implement our search feature using a dedicated search engine/database like ElasticSearch. I worked with it on the old MGI website and it wasn't too difficult as the CMS provided some integration plugins that took care of inserting/updating records into the separate search database. ElasticSearch has an elasticsearch-rails bundle that we can use.
Note that elasticsearch would replace the Quick Search feature, in that it would take a string and then attempt to match it using a search heuristic against all CIViC contents and provide a weighted list of matching queries. We should still keep our Adv. Search b/c it provides users a way of performing very precise queries on specific entities.
It would be great to have google-style search and results page that allows you to find keywords in full text evidence/variant/gene summaries, comments, etc and then links you to the appropriate source page.