[Improvement] - Update search queries to use ranking

[InManuBytes]

As a user searching for lavender book, I want the results to be sorted by relevancy to my original search query

AC

• Use a relevancy score anytime a user's search query is queried against the database
• Apply this to:
• Search for spaces
• Dropdown autofill for category/name

Notes

• SO Thread https://dba.stackexchange.com/questions/66356/in-postgresql-is-there-a-way-to-rank-weigh-columns-so-as-to-order-the-results
• Postgres documentation https://www.postgresql.org/docs/current/textsearch-controls.html#TEXTSEARCH-RANKING

[gknorman]

@IreneHodge THIS article is helping ALOT - https://pganalyze.com/blog/full-text-search-ruby-rails-postgres

[gknorman]

TODO - Determine better configuration for the current IF ELSE search conditions
-- Are empty boxes actually evaluating to false? Why does searching on just Categories return no results?
TODO - Disambiguation for User about that “SPACE” means “NAME” of Location
TODO - Disambiguation for User that category is space with that attribute
TODO - Search on multiple terms provided by user for either SPACE or CATEGORY
TODO - Tell Users they have the option of searching by Decimal Degrees with Northing and Easting

[gknorman]

@InManuBytes @InManuBytes Ok after MANY months I think I finally have some idea of how to use the pg_search gem to perform "full text searching" -- but on just the names of spaces.

I pushed the very slight changes to space.rb and spaces_controller.rb to this branch (please ignore all of the messy comments)

https://github.com/outintech/nbjc-app/tree/full_text_search

A major issue though is that this is based on pg_search's "single model" mode, where it can only search against the fields of the Space object or the spaces table. If we want the search terms used by the user to also be compared against the category_buckets descriptions or to do a backup search against other tables (like should searching for "San" only find names of businesses or all businesses in San Francisco for instance), we'd have to use the Multi Model version of pg_search and lose the "order_within_rank" feature.

You'll also notice that since all avg_ratings are "null" right now for all spaces, pg_search does some other kind of ordering on the results it finds that lexically match the name provided.

Searching on multiple parameters in the future would also be much easier if we could have a single table that is the join of all of the other tables, but I'm sure there's good architectural reasons against this...