Hi Nuria and others,
For context: Stas and I are points of contact in the WMF for Markus et
al.'s project. That's why I'm commenting here. :)
* The project and its goals at the proposal level are described at
.
* As Markus said, they are not looking for global solutions, they're trying
to increase signal in the data and comments seem to be one natural and
relatively cheap place to begin with, given that query owners can add them
if they're aware of this conversation and that already helps.
* I suggest that we move discussions about possible changes of X-Analytics
header to a new thread, if there is a need for it (long term or short term)
given that we don't need those changes for this research, at least for now.
Thanks,
Leila
On Tue, Oct 4, 2016 at 7:56 AM, Nuria Ruiz <nuria(a)wikimedia.org> wrote:
mmm...There are several things here that are already
taken care of by our
user agent policy, for example: if you are using a bot or automated tool we
already ask you to please include bot in the user agent plus contact info.
Please see:
https://meta.wikimedia.org/wiki/User-Agent_policy
Now, we do not keep this information long term, after 60 days it gets
deleted.
X-Analytics is used for bits of info of analytics value, and the contact
info of a tool developer doesn't seem to be one of those. Can we backtrack
a little bit? What is the goal of this project? To keep tally of who is
queying wikidata query service? Anything else?
Thanks,
Nuria
On Mon, Oct 3, 2016 at 10:05 PM, Yuri Astrakhan <yastrakhan(a)wikimedia.org>
wrote:
For consistency between all possible clients, we
seem to have only two
options: either part of the query, or the X-Analytics header. The
user-agent header is not really an option because it is not available for
all types of clients, and we want to have just one way for everyone.
Headers other than X-Analytics will need custom handling, whereas we
already have plenty of Varnish code to deal with X-Analytics header, split
it into parts, and for Hive to parse it. Yes it will be an extra line of
code in JS ($.ajax instead of $.get), but I am sure this is not such a big
deal if we provide cookie cutter code. Parsing query string in varnish/hive
is also some complex extra work, so lets keep X-Analytics. Proposed
required values (semicolon separated):
* tool=<name of the tool>
* toolver=<version of the tool>
* contact=<some way of contacting you, e.g. @twitter, email(a)example.com,
+1.212.555.1234, ...>
Bikeshedding ? See also:
https://wikitech.wikimedia.or
g/wiki/X-Analytics
On Tue, Oct 4, 2016 at 12:45 AM Stas Malyshev <smalyshev(a)wikimedia.org>
wrote:
Hi!
Using custom HTTP headers would, of course,
complicate calls for the
tool authors (i.e., myself). $.ajax instead of $.get and all that. I
would be less inclined to change to that.
Yes, if you're using browser, you probably can't change user agent. In
that case I guess we need either X-Analytics or put it in the query. Or
maybe Referer header would be fine then - it is also recorded. If
Referer is distinct enough it can be used then.
--
Stas Malyshev
smalyshev(a)wikimedia.org
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata