Let's improve Drupal's core search. With higher MySQL requirements in 6.x we should be able to do better.
Core search modules: search.module, but also node.module and user.module. Existing contrib search modules: views_fastsearch, porterstemmer, semantic search, facted_search, Apache Solr (I'll add more as people point them out to me)
There are a few looming search indexing bugs, and some good ideas about performance, refactoring and better hooking. Please help review the above issues. My preference is to focus on improving the queries and search performance, but if you have other ideas and are willing to jump in with patches, please do so.
Mountbatten Ltd. is a Drupal shop in Uganda where we work on small local and a few big international sites with a fast growing team of 10+ people. Our clients are, amongst others, UNICEF, Worldbank, Fortune top 100 and local companies.
In this team we have an opportunity for an experienced Drupal developer. Your role is to coordinate the work on the range of modules we maintain on Drupal.org with a team of developers and to cooperatively design and write on the most urgent code.Read more
I am trying to use search API with the REST API provided with services. I have a view(as described below), a search index which indexes nodes, and a service endpoint. When i use the browser to directly access the view, the results are correct, but when I send a get request to the rest endpoint, I get something like
$view = new view();
$view->name = 'search_products';
Come and join a fun and progressive organization that is proud to be a 2011 Star Tribune Top Workplaces Employer! We do great things in the community and we are looking for the next ROCK STAR to be a part of a growing and incredibly smart and creative team!Read more
Currently name of entities that could be indexed is restricted by a 16 chars. This could occur cause of performance restrictions, however this does influence on a module developers which want to integrate their entities with a Drupal Core Search.
Here is a patch that solves a problem, please review: http://drupal.org/node/1425622#comment-5615740.
I am not sure how this depend on a Drupal performance. Let's discuss it here.
I want to replicate the search functions of this site http://www.zocdoc.com/ .
1)First,on the front page I want to have a drop down list to select from,as on the site the
"Find a doctor or dentist specialist" drop down select list
2)At the bottom of the page I want to filter by taxonomy terms for example By City etc.
3)By name as here http://www.zocdoc.com/directory .Eg with a search box.
How can I replicate these 3 kind of searches?
Thanks in advance,I would be grateful for every answer
The Entity Translation module is the latest and greatest way to manage multilingual content in Drupal. However, no Drupal search solution currently supports the field based translation it is built on. We'd like to share how we solved this challenge, made field based translations searchable and came up with the brand new Search API Entity Translation module.
Search API Entity Translation is a minimalist approach of making multilingual content managed via entity translations searchable via Search API.Read more
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
It is an exciting time for Drupal search. Thanks to jhodgdon, the search community is finally communicating with each other. Looking at projects such as Search API Facet API Integration, we are actually starting to collaborate as well. With collaboration comes healthy and welcomed differences of opinions, but in order to keep discussions productive we must be working towards common goals.Read more
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?
While I was trying to beat one the oldest opened issue on xapian module IIRC: Index uploaded files, I end up figuring out that it could be useful to have a way generate a plain text representation of any field.
So, I have started a sandbox that have enough code to get a plain text version of file fields: Plain.Read more
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.Read more
I am using Drupal 6 and am trying to figure out this mind-twisting functionality.
User can search for a taxonomy term. Selecting one of the available results will bring up a new node to create content with the taxonomy term already pre-selected as one of the fields.
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.
We looking to hire a full-time developer who is expert in PHP and has a good working knowledge of Drupal. We are located in Santa Monica, California in view of the ocean. Competitive salary, paid vacation, full benefiits.Read more
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.Read more
As some of you might know, in last year's GSoC I created the Search API module, which has already gained some fame since then. It's a highly flexible search solution for Drupal 7, already coming with support for Views and facetted searches out-of-the-box, amongst other things.
Still, like all software, it isn't perfect and there are still a number of known shortcomings, as well as other potential for improvement. So for this Google Summer of Code, I propose to fix some of these shortcomings, and add some additional features.
The tasks I'd have in mind are the following (in order of importance):
- Add autocompletion feature
- Provide ways to index other data than entities
- Add a "More like this" feature
- Add hierarchical facets for taxonomy terms
- Add additional little multi-language features
- Extend test coverage
- Extend documentation
The last two are of course the buffers for any remaining time at the end — even when I'm done with the others, there will always be numerous ways to improve tests and documentation.Read more