Page MenuHomePhabricator

Section heading suggestions in search results can point to wrong heading
Open, LowPublic

Description

When searching for a series of words (not in quotes) the search results can suggest a section that may not be relevant.

Example query: https://commons.wikimedia.org/w/index.php?title=Special:Search&profile=advanced&profile=advanced&search=You+seem+to+be+unaware+that%2C+IIRC%2C+there%27s+an+informed%2C+consensus+view&fulltext=Search&ns0=1&ns2=1&ns3=1&ns6=1&ns12=1&ns14=1&ns100=1&ns106=1&searchToken=6rnu2evqnqo35su6uey0ww4xm

Section linked in first result: https://commons.wikimedia.org/wiki/User_talk:Ellin_Beltz/Archive_3#Why_you_delete_my_files_that_I_translate_from_English_to_Khmer

Actual section where that series of words appears: https://commons.wikimedia.org/wiki/User_talk:Ellin_Beltz/Archive_3#Understanding_when_PD-.2AGov.2A_applies_-_e.g._to_unpaid_work._2

The (section: Section heading) suggestion in the first result is not a literal match. The search will highlight a section if one of the search terms is present in the section name. So the words "you", "that" and "to" are the first close-enough (as the search is not exact) results in a section heading, so it suggests that section. Which is wrong. :(

Putting your search in quotes changes to the results to be literal, and removes any section suggestion.

Example screenshot for search as described above. (Note that the User_talk: namespace has been enabled in that search).

Screen Shot 2016-04-06 at 11.07.03 AM.png (102×719 px, 36 KB)

Original report:

https://www.mediawiki.org/wiki/Topic:T0sz0kfwn0kc19zy

Event Timeline

Deskana subscribed.

A legitimate issue, but it's an edge case since it's incredibly unlikely to occur in content namespaces, it can't really be prioritised.

MPhamWMF subscribed.

Closing out low/est priority tasks over 6 months old with no activity within last 6 months in order to clean out the backlog of tickets we will not be addressing in the near term. Please feel free to reopen if you think a ticket is important, but bare in mind that given current priorities and resourcing, it is unlikely for the Search team to pick up these tasks for the indefinite future. We hope that the requested changes have either been addressed by or made irrelevant by work the team has done or is doing -- e.g. upgrading Elasticsearch to a newer version will solve various ES-related problems -- or will be subsumed by future work in a more generalized way.

RhinosF1 removed a project: Discovery-Search.
RhinosF1 subscribed.

Re-opening tasks and removing from team workboard per IRC feedback given yesterday and discussion with MPham.