This is an add-on module for Apache Solr Search Integration that logs each query including keywords, fields and sort options used, the Solr service response times, spellchecker suggestions and number of results returned.

Requirements

Requires Apache Solr Search Integration.

The charts are generated with the Google Charts API, so while you don't need an API key, you will need a live internet connection to view the charts.

Instructions

Install and enable module. You must first enable logging at admin/settings/apachesolr/stats before viewing any results.

After a few searches you can see results under admin/reports/apachesolr/stats. Below the report header you can select the report's granularity: per minute, per hour or per day. The reports only include recent activity depending on granularity.

Optionally:

• you can enable a block that will show users popular searches (but only those that returned any results). The block is cached and refreshed after 10 minutes to ensure performance.
• you can enable a Google gadget that will allow to you to embed a report into iGoogle or other pages; the provides a secret key that can be "revoked" at any time to disable already-installed gadgets. Configure this in admin/settings/apachesolr/stats.

This module provides a method for users with the necessary permissions to manually override the results being returned by Search API Solr.

This module adds the ability to use elastixsearch suggester, which improves suggester results for search_api, elasticsearch_connector and search_api_autocomplete module.

The Entity Search API Autoindex module is used to automatically generate an index and a view with just a few clicks.

This module uses Drupal's core search api to index taxonomy terms.

Provides a structured approach to periodically or manually check the status of an endpoint entirely from configuration and code.

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.

The core Search module provides a simple list of top search phrases from the watchdog log using the function dblog_top. However, most sites clear watchdog frequently. Search log stores search terms indefinitely and provides more robust reporting.

INTRODUCTION

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

This module extends the search box so it gives back search results while typing. It currently supports two ways of displaying these search suggestions: clickable title or by an extra view mode 'live results search'. With the view mode support you have full control on how you will show the live results.

It's fully inspired by the Search API autocomplete module, but instead of giving back keywords, this module will give back content matches.

Solr

This module is mainly being tested with Solr.

Important: To have partial string search, you have to enable fuzzy search in your solr configuration (schema.xml). You can find more info on how to enable this here.

Performance

There is experimental support to cache the results in memcache (check search_api_live_results.results.php) so you don't have to do a full drupal bootstraps, making it 50% faster for cached searches.

The best results are achieved when the live search query urls are cached with varnish. Getting almost an instant search suggestion while typing.

Sponsors

The WordStream module integrates WordStream keyword tools into your Drupal site. The WordStream service provides a keyword research api (with a free account option). The WordStream module provides access to both classes of keyword tools.

With this module you can explore how often certain terms are searched for and the popularity of keyword variants.

The WordStream module also acts as a data source for the Keyword Research module which provides a rich user interface for keyword analysis and management.

Currently the module is operational, future plans are to implement additional WordStream reporting.

For installation, follow the instructions in the README.txt file.

Requirements & recommendations

Required modules:

• None

Recommended modules:

• Keyword Research - Enables keyword management and integration with other keyword research data sources
• Drupal SEO Tools - integrated dashboard for SEO reporting, analytics and optimization

Sponsorship

Search API Views Ajax faciliates updating a search view asynchronously when using an AJAX enabled view with the Search API module.

DRUPAL COPILOT

This would be a module to be a sort of Editor Drupal Copilot.

The simple form module is designed to make it easy for website administrators to create and customize forms on their site.

This light-weight module extends the core Search module's functionality by providing a new admin configuration to exclude content types and individual nodes from search indexing.

Full text content admin search

This module adds full search to the content admin with the possibility to add custom filters on content fields (Status, Node types, etc).
It's based on top of Search API.

This modules provides a Search API Backend for OpenSearch.

This project will create a sitemap for google and provide information about images on your site. You can also update an existing Sitemap.

The module offers a Search API display plugin for flexible search result presentation, enabling decoupled search experiences with configurable endpoint blocks supporting autocomplete and facets.

Overview

This module allows Search API Solr to connect to the Acquia Search service. It requires the Acquia Connector module and a valid subscription.

Despite the wonderful site building tools that Search API provides, Acquia strongly recommends that you use the Apache Solr Search Integration and related modules instead. Based on our extensive experience helping Acquia Search customers with both the Apache Solr Search Integration and Search API modules, we have found that using the Apache Solr Search Integration module results in a search solution that is more scalable, better performing, more reliable, and better integrated with Apache Solr. If, despite these factors, you want to use the Search API module with Acquia Search, follow the instructions on the Acquia Search Documentation site to get connected.

Compatibility

If you are using Search API Solr RC4 or higher you should use 7.x-2.0

This module (intends to) provides a framework to assist content editors with the task of classifying content in a complex site with several search hierarchies and facets.

When searching for content in a multilingual website, Drupal core node search displays results in all languages.

Sarnia allows a Drupal 7.x site to interact with and display data from Solr cores with arbitrary (non-Drupal) schemas, mainly by building Views. This is useful for Solr cores that index large, external (non-Drupal) datasets that are either not practical to store in Drupal or may already be indexed in Solr.

Drupal 8/9 Support: This module's functionality is now included in Search API Solr module for Drupal 8, version 8.x-3.0 and later, as the "Solr Document" datasource support. Search API Solr 8.x-4.0 and later support Drupal 9.

Sarnia treats records from Solr as Drupal entities, although listing, filtering, and displaying Sarnia entities should be done using Views. Solr properties can be formatted within Views fields using field formatters (hook_field_formatter_info(), hook_field_formatter_view()).

This module is a dependency of Search API Federated Solr, but is also usable on its own.

This module allows you to boost search results that do exactly match the search keys on specific indexed fields. The exact matches will be put on top of the list.