Open fjoxide opened 2 years ago
Module for reference - https://www.drupal.org/project/search_api_autocomplete
Hi @thisisalistairsaccount - this issue is different to the #489. A little confused.. thanks
Frank
Hi @fjoxide apologies on the previous linking and closing. They are related to search but different.
Seeking more interest from the community before we progress any further.
+1 to this.
+1
+1. However, there are already alternative solutions such as using facet API with a Vue.js app if this feature is urgently needed.
+1 again
+1, surprised it's not in already
Hi All,
We're going to take a look at this functionality. In positive news, it's already Drupal 11 ready for when we think about those upgrades in 2025.
+1 also..
** What value does this module/package add to GovCMS?
This module provides autocomplete functionality for Search API searches.
** Please provide a brief outline of what this module does.
Autocompletion can be activated and configured for each search (all search views and pages) individually, so you have fine-grained control over where autocompletion can be used – and by whom.
** Who does this module benefit:
This module will assist the end users to more effectively find the content they are looking for.
** How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
Currently there is no way to replicate this functionality, even via the theme layer.
** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
This module provides multiple theme templates that can be used to style the theme.
** What is the maintenance and support status of the module. Describe the issue queue activity.
It has a stable release and currently being used by 25,168 websites. It has minimal bugs and heavily supported by the community.
** What permissions are needed to utilise the module (and are any new permissions provided by the module)?
no permission are provided by this module. Views provides the permissions.
** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?
Currently there is no way to replicate this functionality, even via the theme layer. It uses already indexed data via apache solr.
** Is the module designed to capture anonymous user data? It does not capture anonymous data.
** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.
This module is cacheable through the views module, as it is only a plugin that you can use for views.
** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?
It has a stable release and currently being used by 25,168 websites. It has minimal bugs and heavily supported by the community.
** Additional information
I plea that this module is installed and enabled as part of the GovCMS 9 SaaS distribution, as it provides additional functionality to the already search Api, Search API Solr. It will enhance the user experience with is a must with government websites. Having worked with government websites for the last 17 years, i truely believe this will assist agencies and users find content more accurately.