ApacheSolr Views has been emerging as a very popular module that compliments core search & Apachesolr modules when site owners want more granular control on what data surfaces for in search requests.
There have been many requests for plugins on ApacheSolr Views module, These requests are result of limited filters that come by default with ApacheSolr Views.
Examples of some of the requests include providing support to Organic Groups,
og (organic groups) argument and filter
Node sticky
Support for Domain Access
While some of the features are candidates to go into Apachesolr project, others might have to live outside of ApacheSolr Views current implementation.
I would like to propose a new project
ApacheSolr Views Assorted Plugins
This module will provide assorted plugins that will provide integration for ApacheSolr views with other modules. Some default candidates for integration that i can think of are Organic Groups, Configurable ApacheSolr Facets integration, Domain Access. I am sure there can be many more. Essentially any such integrations that have to be outside of ApacheSolr Views core engine can go into this module
This module will make ApacheSolr Views awsome!!
I welcome your thoughts and suggestions.
Comments
Handler repo instead?
Instead of creating a large module which could get huge very quickly, I propose a hosted repo of views handlers based on views type instead.
E.g.
Apachesolr Node:
* Field handlers:
* Sort handlers:
* Argument hanlders:
Node:
* Field handlers:
* Sort handlers:
* Argument hanlders:
:
provided as a REST call from the views interface when creating a view.
Use case:
User creates an apachesolr node view.
User goes to add a filter, but does not have anything specific for his purpose. Finds a 'plugins from repo' link and clicks it.
Service call initiated and modal dialog box opens with filter handlers for Apachesolr Node type views compatible with the views version the user is having.
Assuming the handler descriptions are clear enough, user checks the handlers he wants, presses submit. These handlers then get downloaded and exploded in the user's code base and immediately made ready for use in the view.
Downsides: Maybe too fancy? Handler repo needs to be hosted.
Post discussions
After discussions on IRC , i have understand that this module could be more of a repository of assorted handlers rather than plugins.
Also the integration with tac_lite is not required as its already provided by apachesolr_node_access module. There could still be more areas where this kind of module will help, so changed the description slightly and keeping this thread open.
Instead, why wouldn't the
Instead, why wouldn't the module query Luke for the fields in the index and then create handlers for the fields there. Much the same way table wizard works?