Search

Hi all

I am trying to replace drupals core search with my own views search. the search in views work but only if you type its exact url would you see the views search. and this is where I am having hard time putting the two together.

I am using the function hook_menu_alter to replace the drupal core search with my views search path. heres the code thats on my custom module file:

<?php
function searchy_perm() {

return array('access searchy', 'administer searchy');

} // function searchy_perm

function searchy_menu_alter(&$callbacks) {

Was just catching up on some sessions I missed in Szeged and watched:
http://www.archive.org/details/drupal_search

And it inspired me to find this group here on g.d.o. And while trying to find the group I got this amusing result:

So I have been tasked with solving the issue of stemming, mispellings, multilingual and partial matching for a site. I decided to create a quick prototype for n-gram indexing. (http://en.wikipedia.org/wiki/N-gram among other resources) . It is a relatively proven technique for these issues, but creates a larger index. So of course not sure if it is the best route in terms of performance, but I plan on running tests.

I would like a custom search form with search "input form" to query a certain vocbulary.

I have looked at views, fastsearch, filter block

They are ok to use when you want a drop down, not a "text input". I have about 450 terms, from a vocabulary I want to be queried.

I believe a drop down would not be user friendly, also it would load as fast.

On my site, a directyory listing, the search form would be of this nature

|keyword| |location| |business type| Search Button

Hey everyone. I just finished up work on my Summer of Code project that was targetted at further developing the core search. During the course of the project I created a module for Drupal 6 that back ports DougGreen's hook_ranking() patch that made it into HEAD. The module uses hook_menu_alter() and some other work to override the core search implementation completely. This module also includes some other cool new things listed below. I'd like to get some feedback on the changes that have been made because I want to create some patches for the new features to be integrated into HEAD.

I've posted a first cut at a patch to refactor core search into a generic search module that accepts different backend handlers and a specific handler, core's custom indexing. It's a very basic patch--it just does the minimum to decouple the generic search interface from the backend.

The aim is to permit e.g. apachesolr and other search backends to plug in seamlessly to core search.

Ready for review: http://drupal.org/node/282192.

I've proposed and extended search session for Szeged. The timing of the session is important as a way to keep momentum going from the Minnesota Search Sprint and focus on what we can achieve in Drupal 7. It will also provide a chance for people to talk about alternatives to Drupal core, what core can do to support the growing number of 3rd-party solutions, and what core can learn from things like ApacheSolr.

http://szeged2008.drupalcon.org/sessions/drupal-search-where-are-we-wher...

Please vote if you like the session.

Just wanted to let everyone know that I submitted a patch that allows you to rank nodes with more inbound links than other nodes higher in search results using the new ranking hook.

Take a look, give it a try, and please give feedback.

http://drupal.org/node/257216

I posted some internal benchmarks from the Xapian module we are working on in the Trellon.com blog. This post describes the performance gains using Xapian can have and does some benchmarking on a really, really slow server.

Would love it if someone could verify those results. We are about to take the sample size of the data up to about 1mil nodes and repeat.

M