We currently have a lot of extreme biases, which are drowning out other factors in search results, such as #2558663: Favor exact title matches in site search. Let's scale them back.

Type biasing:

  • Translation project 21 → ignore: these are deprecated in favor of localize.drupal.org.
  • Other project types 21 → 13: results shouldn't be a pile of projects, they should be a pile of relevant projects.

Field biases:

  • Path alias 21 → 13: path alias catches any match within the path, for example project/rules_set_site_variables gets a bias when searching for rules. For projects, this drowns out the module itself. However, we still need a decently strong bias because higher-quality book pages tend to have aliases.

Comments

drumm created an issue. See original summary.

drumm’s picture

Issue summary: View changes

Add notes on path alias bias.

drumm’s picture

Issue summary: View changes

Adding notes on type biasing.

drumm’s picture

Status: Active » Needs review
drumm’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +needs drupal.org deployment

Tracked improvements:

  • glossary: the book page goes from result #8 to #1
  • rules: the module goes from 48 to 2, and the documentation page goes from 100 to 1
  • zen: documentation page goes from 10 to 8
  • views: the module goes from 26 to 2
  • apachesolr: the module goes from 28 to 1
  • apache solr: the module goes from 61 to 51
  • media: the module goes from 52 to 5
  • redirect: the module goes from 23 to 1
  • xml sitemap: the module goes from 33 to 7
  • drupal core: core goes from 24 to 1
  • tag1: the consulting company goes from 41 to 1
  • drupal geeks: the organization enters the top 100 at #16

There are no significant tracked regressions.

drumm’s picture

Status: Reviewed & tested by the community » Fixed
Issue tags: -needs drupal.org deployment

This is now updated on our current production core.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.