Thu, May 24
@mforns can you help with this? Thank you!
Please understand, though, that we Analytics are trying our best on our side as well. And that in the view of this situation where conflicts already exist between some of us, aggressive comments do usually not help reach results, but rather make the conflicts bigger.
Agreed. While we seem to have different a priori views of what counts as aggressive (I would have regarded the wording at the center of your concerns, "creatively reinterpreting this task", as perhaps unnecessarily flippant but not as an attack), the perception of the recipient and how it makes them feel is important, and I will try to be more careful about this in our future discussions. In turn, I would still love to also see improvements or at least acknowledgments regarding the IMHO problematic communication patterns from your team that I tried to describe in this one example above. But maybe we should take this conversation offline now.
Wed, May 23
Oh, cool. Yea, definitely useful. Thanks!
As @Ladsgroup knows, I worked on this task during the BCN Hackathon.
It was super-interesting and I learned a lot about Wikidata :]
Thanks for the opportunity!
Here's a summary about what I did, issues I had, and next steps:
Tue, May 15
Virtualpageviews_hourly is in druid!
I understand your position now, thanks.
Mon, May 14
As discussed in the tasking meeting, one idea could be having a set of pages on-wiki under a json namespace that store the annotations.
Those would be divided in 3 levels:
Level 1 (one page): re. all metrics
The new timeline looks great.
I wish you an awesome coding period :]
Fri, May 11
Thanks for posting this here. It helped me understand how you use that field.
I can totally see the benefits of keeping appInstallId, and also the drawbacks privacy-wise that we have been discussing.
I was trying to think of a way we can perform the analyses you described with alternative fields or methods.
Listed my thoughts below. Please, let me know if they make sense.
The data set with the source fields is ready, accessible in hive: wmf.virtualpageview_hourly.
It is updated with new events every hour. There will be a lag of a couple hours, due to EventLogging import, refinement and aggregation into the final table.
I vetted the data and looks good, but please review!
Tue, May 8
The data set is regenerating into mforns.virtualpageview_hourly.
From my manual checks, it looks good.
It will take around one more day to finish.
Then I will move it to wmf.virtualpageview_hourly.
Let's first work on 1) and 2). And once this is done, we can commit some time to having a popup that pulls the first paragraph from on-wiki.
Thanks, I understand it better now.
We'll work on this task in the upcoming weeks.
Mon, May 7
Line chart problem is already solved, but map problem is still present.
I think #2 is still an untackled issue:
Even if you merged this patch, I understand that this task is not done yet, because there are still changes to be applied in other sections of the code. Is that correct?
This was resolved by T188277.
Is there any work to be done here before we can close this task?