Search

In the D8 Search core conversation at Drupalcon London, we discussed the following high level actions items (listed in no particular order) that are quick wins and would hopefully improve the underlying Search framework in D8 and alleviate some of the maintenance overhead.

• Allow for multiple search pages per module
• Remove menu tab assumption
• Make the preprocess code language / type aware
• Make the highlighting code pluggable
• Make default operator to "OR", start to explore making the parser pluggable.

We are looking for a LAMP Developer in SF Bay Area. This is not a telecommute position.

• You have 5 years experience with PHP, jQuery, Linux, and MySQL.
• 3 - 5 years' experience with LAMP stack Application development (not web site development)
• You understand technology at a deep level and have a knack for solving problems
• You like being part of a team
• You do your own bachelor’s degree
• Good communication skills and interpersonal skills.
• Experience with Drupal will be a plus

I have 5 independent sites on one machine. I also have another machine running just Java. How can I get all 5 sites to use the same 1 java machine for Solr? Would I install Solr 5 times for each of the sites? Would each Solr instance be installed in each of the sites /home directory; instead of say /usr/local/share. When the apachesolr.modules are installed on each site, how would I have it recognize just it's own instance and not the other 4? Or is there a better way to do this?

The Problem

The search community is fragmented. The problem stems from a core search module that doesn't facilitate third party backends, so each project is forced to solve similar problems in slightly different ways. Each contributed module has its own isolated sub-community, which is detrimental to Drupal as a whole.

I am using Drupal 6 and I'm looking to answer two questions. First, the scenario:

I have a project where there are a handful of search terms that we want to "take control of" and insert logic to either prioritize results or redirect users off of the search page and onto a specific page. For most other searches, we just let the Drupal search process continue as normal.

As part of a recent client project at PingV, we needed to develop a method to display search pages with predefined filters that would display results instantly, without the need to enter a query – and without limiting the end users from further filtering the results on their own. Currently, Apache Solr doesn’t provide this level of customization, so it was necessary to build a custom implementation. I decided to use the Search API page module as a starting point and borrowed heavily from that implementation, removing Search API-specific functionality and adding in the ability to use filters.

http://drupal.org/node/1099914

Hello! I'm using D6 and i'd like to be able to do that via a module or a theme.
Thank you.

I wrote a page a while back (occaisionally updated) with ideas for the core Search module in Drupal 8:
http://drupal.org/node/717654
(plus there is the issue queue)

There's also the new Search API project, which makes some strides towards modularizing Search:
http://drupal.org/project/search_api

What I'd like to do here is to start a discussion about what the community thinks the Search module should be for D8. Add your comments here...

[EDIT March 15 2010: added file attachment]