Last modified: 2013-02-11 11:33:51 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 T40643, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38643 - "found what they were looking for" counted / displays incorrectly
"found what they were looking for" counted / displays incorrectly
Status: RESOLVED DUPLICATE of bug 43887
Product: MediaWiki extensions
Classification: Unclassified
ArticleFeedbackv5 (Other open bugs)
master
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 39043
  Show dependency treegraph
 
Reported: 2012-07-24 15:29 UTC by Oliver Keyes
Modified: 2013-02-11 11:33 UTC (History)
1 user (show)

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


Attachments

Description Oliver Keyes 2012-07-24 15:29:46 UTC
See http://en.wikipedia.org/wiki/Special:ArticleFeedbackv5/Common_snapping_turtle for example; only one of the posts, evidently, is being counted.
Comment 1 Andre Klapper 2013-02-09 13:19:06 UTC
<tl;dr> Calculation of numbers is pretty intransparent currently.

Long version: 

http://en.wikipedia.org/wiki/Special:ArticleFeedbackv5/Common_snapping_turtle
right now states

* 47 posts about this page
* 34% found what they were looking for
Clicking "All comments (41)", in the list there are:
* 12x "found what they were looking for"
* 29x "did not find what they were looking for"

It's pretty unclear how these 34% are calculated, likely because 6 posts about this page are not displayed (as they are empty?).
100 / 41 * 12 is only 29%,
but assuming that some of the 6 hidden posts are positive, 
100 / 47 * (12+6) is 38% so it's likely somewhere in that range.
Comment 2 Matthias Mullie 2013-02-11 11:33:51 UTC

*** This bug has been marked as a duplicate of bug 43887 ***

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


Navigation
Links