So I'm hearing we may have a contender for 'big changes to the ZRR' then ;).
This seems to reinforce the 'big features, not small config changes'
approach to the problem.
On 26 August 2015 at 19:34, Trey Jones wrote:
> And that's in line with the previous experiment. If you have a 32% zero
> res
Thanks so much Adam! :). And thank you to Max for surfacing the issue
- this kind of consistent and practical attention to our end goal,
which is not KPIs about user satisfaction but actual user
satisfaction, is precisely what we need, and I am glad to see it
coming out.
On 26 August 2015 at 19:42
Awesome analysis. Thanks!
Can you put together a quick breakdown of zero-results per-wiki, e.g.
enwiki zero results rate is X%, dewiki zero results rate is Y%, before and
after our changes? Would be great to have that for the presentation!
Thanks,
Dan
On 26 August 2015 at 17:21, Trey Jones wrot
Hey everyone,
I've re-run my "big" wiki zero result rate numbers to see what has changed
in the last month. The results are here:
https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Survey_of_Zero-Results_Queries#One_Month_Followup
Since I was only looking at the big 52 wikis (100K+ articles)
Thats an excellent idea, thanks Adam. Talked about it w/ max and updated
the patch, i think this will work out just fine.
Erik B.
On Wed, Aug 26, 2015 at 4:23 PM, Adam Baso wrote:
> It may not be the *appropriate* parameter name to use, but this sort of
> technique may help:
>
> https://wikite
On Wed, Aug 26, 2015 at 3:58 PM, Chad Horohoe
wrote:
> Aren't we uncached here anyway? Special pages and all.
>
> -Chad
>
Actually the events we are recording here measure the users interaction
with the pages they found. The current idea is to add a query parameter to
all search results (only for
And that's in line with the previous experiment. If you have a 32% zero
results rate, reducing it by 38% (32% * (1-.38)) gives 19.84%. So, allow a
little rounding error in the "32", "38" and "19", and this is right on the
money.
—Trey
P.S.: 2 + 2 = 5, for very large values of 2.
Trey Jones
Softwa
It may not be the *appropriate* parameter name to use, but this sort of
technique may help:
https://wikitech.wikimedia.org/wiki/Provenance
You'd want to look at the *current* VCL in templates/varnish in the
operations repo to see how it's presently done for *wprov*.
-Adam
On Wed, Aug 26, 2015
Aren't we uncached here anyway? Special pages and all.
-Chad
On Aug 26, 2015 3:48 PM, "Kevin Smith" wrote:
> We could make the new experience equally uncomfortable for both A and B,
> by uncaching the results in both cases. Not ideal, but at least would be
> apples to apples.
>
>
>
> Kevin Smith
I ran some zero result rate tests against this API today, it is a huge
reduction in the zero result rate over the existing prefix search. from
32% to 19% (on a 1% sample of prefix searches for an entire day)
On Wed, Aug 26, 2015 at 12:34 PM, Stas Malyshev
wrote:
> Hi!
>
> > I uploaded a small H
Hi!
> We couldn't come up with a solution when discussing this with Erik,
> hence this thread.
I wonder if this can not be solved by some kind of redirect
configuration, i.e. the initial URL U is modified to U' so that when U'
is accessed, it is recorded and then redirected to cacheable URL U. Th
We could make the new experience equally uncomfortable for both A and B, by
uncaching the results in both cases. Not ideal, but at least would be
apples to apples.
Kevin Smith
Agile Coach, Wikimedia Foundation
On Wed, Aug 26, 2015 at 2:30 PM, Max Semenik wrote:
> We couldn't come up with a s
We couldn't come up with a solution when discussing this with Erik, hence
this thread.
On Wed, Aug 26, 2015 at 2:11 PM, Dan Garry wrote:
> Nice catch Max. Thanks for reporting it. Do you have any suggestions for
> how we could alleviate this issue?
>
> Thanks,
> Dan
>
> On 26 August 2015 at 13:3
Nice catch Max. Thanks for reporting it. Do you have any suggestions for
how we could alleviate this issue?
Thanks,
Dan
On 26 August 2015 at 13:30, Max Semenik wrote:
> While doing CR for
> https://gerrit.wikimedia.org/r/#/c/232896/3/modules/ext.wikimediaEvents.search.js
> I came to have seriou
Can you think of a way of consistently identifying a user from page to
page, but only in the trace following them landing on the search page,
that does not include page parameters?
On 26 August 2015 at 16:30, Max Semenik wrote:
> While doing CR for
> https://gerrit.wikimedia.org/r/#/c/232896/3/mo
While doing CR for
https://gerrit.wikimedia.org/r/#/c/232896/3/modules/ext.wikimediaEvents.search.js
I came to have serious doubts about this approach.
In brief, it attempts to track user satisfaction with search results by
measuring how long do people stay on pages. It does that by appending
from
Hi!
> I uploaded a small HTML page to compare both approaches:
> http://cirrus-browser-bot.wmflabs.org/suggest.html
This is very cool! From my very short testing, seems that it works
pretty nicely.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikimed
Thanks Kevin!
yes you're right it's a missing feature, prefix search run a specific
query to find the exact match.
I'll try to add it.
Le 26/08/2015 19:48, Kevin Smith a écrit :
Thanks David! That page is awesome for anecdotal testing.
I notice that a search for IOL (or iol) would also bene
Thanks David! That page is awesome for anecdotal testing.
I notice that a search for IOL (or iol) would also benefit from
prioritizing an exact match. The prefix autocomplete brings up IOL near the
bottom, but the suggester misses it entirely. Same for XP, CPU, etc.
Kevin Smith
Agile Coach, Wik
BTW, the question set used in the paper can be found here, in a
multilingual version with answers:
https://github.com/AKSW/hawk/blob/master/resources/qald-4_multilingual_train_withanswers.xml
(but not the keywords that the authors extracted for the Wikipedia search
here, like in the "Claudia Schiff
So I got a copy of the paper (thanks, Phoebe!) and skimmed it quickly, and
I'm not thrilled with the result.
Their translation of questions into Wikipedia queries was sophisticated
from a language processing point of view, but naive from a search point of
view. "How tall is Claudia Schiffer?" beca
Thanks Erik!
I uploaded a small HTML page to compare both approaches:
http://cirrus-browser-bot.wmflabs.org/suggest.html
Le 26/08/2015 00:38, Erik Bernhardson a écrit :
We have been working on a replacement autocompletion API that is more
forgiving than a strict prefix search. The scoring a
Hey all,
Several weeks ago we ran an A/B test to try and decrease the number of
searches on Wikipedia returning zero results. This consisted of a
small config change that reduced the confidence needed for our systems
to provide search results, along with a change to the smoothing
algorithm used to
23 matches
Mail list logo
