{"id":8766,"date":"2016-09-12T11:28:43","date_gmt":"2016-09-12T11:28:43","guid":{"rendered":"https:\/\/dev.railscarma.com\/search-kick-gem-to-make-your-search-intelligent-on-rails-app\/"},"modified":"2021-06-06T11:33:16","modified_gmt":"2021-06-06T11:33:16","slug":"search-kick-gem-to-make-your-search-intelligent-on-rails-app","status":"publish","type":"post","link":"https:\/\/www.railscarma.com\/es\/blog\/articulos-tecnicos\/search-kick-gem-to-make-your-search-intelligent-on-rails-app\/","title":{"rendered":"Search Kick Gem – To Make Your Search Intelligent On Rails App"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tSearch kick Gem is a Ruby gem that runs on top of Elasticsearch and makes it easy to make searches in a Rails-friendly fashion. In addition, it allows you to add more features including analytics, autocomplete, and personalized results.\n\nSearchkick realizes what your users are searching for. As more individuals hunt, it gets more brilliant and the outcomes improve. It’s benevolent for designers – and supernatural for your users. It handles stemming, special characters, extra whitespace, misspellings, custom synonyms.\n\nTo get started, make sure that you have Elasticsearch installed on your home computer. Depending on your operating system, the installation process is slightly different and make sure you have at least Java 7.\n\nOnce you have that done, add and install searchick to your Rails application by adding the following to your Gemfile and running bundle install.\n
gem ‘searchkick’<\/blockquote>\nWhen you have both installed and ready to go, you need to indicate which models you might want to be able to search through in your application. Just add searchkick to the model file to make it work. Then, we need to reindex the models so that Elasticsearch can run properly. In your terminal, run:\n
rake searchkick:reindex:all<\/blockquote>\nSeeking with searchkick is entirely straightforward. Basically run YourModel.search, trailed by the parameters of the search and any filters that you want to add on. For instance, one of more complex searches is below:\n\n@offers = Offer.search params[:search],\npage: params[:page], per_page: 10,\norder: {starttime: :desc},\nfields: [{offer_name: :word_start}, {offer_request_name: :word_start}:price],\nwhere: {\nstarttime: {\ngte: DateTime.strptime(params[:fromdate], ‘%m\/%d\/%Y’),\nlte: DateTime.strptime(params[:todate], ‘%m\/%d\/%Y’)\n}\n}\n\nIn this search, we take the search query of the user with params[:search], and look through of the lessons with the following conditions:\n\nPagination:<\/strong>\n\nThis portion of code returns the results of the search into pages of 10. You can alter what number of list items you need on every page using this method. This works with both will_paginate and kaminari.\n\nOrder:<\/strong>\n\norder: {starttime: :desc}- This method determines what order the results are returned in. By using this we can change the result display with ascending order or descending order. In this case, we returned the most recent results first.\n\nFields:<\/strong>\n\n[{offer_name: :word_start},{offer_request_name: :word_start} :price]- In this method, we allowed users to search by offer name, offer type, or the offer price. The word_start method allows for users to only type in the first part of the offer name and still get the offer in search results. For example, a search of “ch” would still reveal “chat”. You can also use word_middle and word_end. For longer text, searchkick also supports text_start, text_middle, and text_end.\n\nWhere:<\/strong>\n\nstarttime: {gte: DateTime.strptime(params[:fromdate], ‘%m\/%d\/%Y’), lte: DateTime.strptime(params[:todate], ‘%m\/%d\/%Y’)}. It allows users to easily use filters in their application. We wanted to filter between dates we used starttime to find the offers\n\nSetting Custom Search Attributes<\/strong>\n\nOne last great feature in searchkick is the search_data method that you can add to your models. This allows you to add or replace attributes that the user can search for. By doing this, you can create custom search parameters or search based on the associations of a model. Below is an example of one of the search_data methods we implemented.\n\ndef search_data<\/strong>\n\u00a0\u00a0\u00a0\u00a0\u00a0 attributes.merge(<\/strong>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 offer_request_name: offer_requests.map(&:name),<\/strong>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 )<\/strong>\nfin<\/strong>\n\nMultiple Indices<\/strong>\n\nSearch across multiple indices with:\n
Searchkick.search \u201csearch_query\u201d, index_name: [Offer, OfferRequest]<\/blockquote>\nNuestro\u00a0Desarrolladores de Ruby on Rails<\/a>\u00a0here at RielesCarma<\/a> don\u2019t just create applications but they create phenomenon. Making use of the futuristic techniques, they deliver brilliant applications, design beautiful and engaging UI\/UX, develop clear front ends, build scalable applications & manage them on Cloud. In short, our Ruby on Rails developers \u2013 \u201cGive Life to Your Ideas\u201d.\n\nComment below or Cont\u00e1ctenos<\/a> in case of any query.\n
Katneni Naga Sai Tejaswi<\/strong><\/div>\n
Desarrollador de software s\u00e9nior<\/strong><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Suscr\u00edbete para recibir las \u00faltimas actualizaciones<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\t\t\t\t\t