Last modified: 2013-03-14 13:42:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42169, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40169 - Use stats to automatically redirect either to disambig page or straight to a specific page
Use stats to automatically redirect either to disambig page or straight to a ...
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
Redirects (Other open bugs)
1.21.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: analytics
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-11 18:57 UTC by Jan Ceuleers
Modified: 2013-03-14 13:42 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jan Ceuleers 2012-09-11 18:57:04 UTC
On Wikipedia, many keyword searches for an ambiguous keyword lead to a page about one of the possible meanings of this keyword rather than leading to the disambiguation page. This is desirable in cases where the vast majority of searches for this keyword end up leading to that particular page.

At the moment though, someone (i.e. a human) selects whether to go straight to the disambiguation page or to a particular specific page (which then provides a link back to the disambiguation page to satisfy false hits).

Would it be possible to make this dynamic/automatic based on statistics:

Collect statistics on which of the entries on a disambiguation page are the most popular. If one of them is clearly more popular than all the others, then the keyword search should redirect straight to that. Otherwise the keyword search should point at the disambiguation page.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links