Search

Handle the apache 420 response code "appropriately."

This module extends Search API Solr to be able to use SolrCloud. Because we depend on specific modules to connect to Zookeeper, which most users don't need, support for SolrCloud is built in this separate module.

The 'Tab to Search' feature is described in the article Google Chrome – Tab to Search. How can a website enable the 'Tab to Search' is described on the website of the Chromium project: Tab to Search.

You can test the module on a test site:

Flag Search API module provides flag indexing for Search API.

Use this module to index flags (flagged content) using Search API module. Once indexed, the flags can be used elsewhere, e.g. in Views.

It also has support for reindexing flagged entity on flagging action

UPDATE JULY 2017

The bundle / type boost functionally is now included in Search API core. This module will no longer be maintained!

It is recommend that all sites using this module upgrade to the latest version of Search API, reconfigure the processor settings and remove Search API Bundle Boost!

This module will help Integration of Wizenoze API with Drupal. Following are the major goal for this module:
1. Expose admin settings for Wizenoze API connection.
2. Batch process/Drush command for content ingestion
3. Pull Wizenoze result and implement search plugin based on collection.

This module will provide autocomplete search suggestions.

The module is compatible with standard Drupal search, search views and Apache SOLR, but not reliant on any of them.

Auto-complete suggestions are created from 3 sources:

1. Titles of selected content types. This provides a starting point for suggestions and requires significant content to generate enough autocomplete suggestions.
   1. Strings are tokenized, (lowercased, stopwords removed, short/long words removed and extra spaces removed).
   2. Strings are broken into different length ngrams.
   3. The score of each ngram is tallied and used for ordering.
2. Priority suggestions added via the admin interface. These suggestions have the highest score and allow the admin to create a set of useful suggestions where the initial set created doesn't proved enough quality auto-complete suggestions.
   1. Strings are tokenized, (lowercased, stopwords removed, short/long words removed and extra spaces removed).
   2. Strings are broken into different length ngrams.
   3. Priority ngrams start with the highest score.
3. Surfer searches. These suggestions provide an organic way to create successful autocomplete suggestions.
   1. Surfer searches are sourced when the search is submitted.
   2. Strings are tokenized, (lowercased, stopwords removed, short/long words removed and extra spaces removed).
   3. If the tokenized strings exists as an ngram then the score is increased.
   4. If the tokeized string doesn't exist then it is scored and generated ngrams added.

INTRODUCTION

This module let editors or administrators manage synonyms for Search API
directly in Drupal.

Synonyms can be export using the build in Drupal Console command.
Drush command and automatic export using Drupal cron job is in development.

The module support the synonyms.txt format used in Apache Solr.
Other formats can be added using the Export plugin annotation.

Entity BackReference module provides backreference indexing support for Search API.

Use this module to index backreferences (fields from other entities that reference your indexed entity).

You'll be able to select which backreference fields you want to index and index them and use them in views

Also have support to index directly backreference when updating referenced entity

Avalanche, a collection of Snowballs.

Avalanche is a collection of stemmers (currently from the Snowball project, but not technically limited to those) that help improve Drupal 8 database search by reducing words in searches into their stems. More stemmers can be added as plugins.