Page MenuHomePhabricator

enable fine grained usage tracking on Commons
Closed, ResolvedPublic

Description

In order to have fewer changes from Wikidata show up in recent changes and watchlists on Commons we should enable fine-grained usage tracking there.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Lydia_Pintscher renamed this task from enable fine grained usage tracking to enable fine grained usage tracking on Commons.Feb 12 2018, 9:11 PM
Ladsgroup changed the task status from Open to Stalled.Mar 18 2020, 5:48 PM
Ladsgroup removed Ladsgroup as the assignee of this task.

Commons database is really short on disk space. We should pick this up once our DBAs are comfortable with table expansions. @jcrespo @Marostegui

Michael added a subscriber: Michael.

Let's check if this is something that we should pick up in the current hike

Commons database is really short on disk space. We should pick this up once our DBAs are comfortable with table expansions. @jcrespo @Marostegui

Commons db got slightly better but I still leave it to the DBAs to approve this.

the DBAs to approve this

That should be @Kormat and/or @Marostegui (he is on vacations right now).

I’m not sure what this task is asking for… fine-grained usage tracking (at least the meaning of the phrase that I’m aware of) was enabled on all wikis in February 2018, and more recently we entirely removed this configuration from Wikibase and from the production config (1, 2), unconditionally enabling it everywhere. Is there anything still missing that I’m not aware of, or can we just close this?

At some point we turned off fine-grained usage tracking from Commons because it would have exploded the recent changes table there. I am not sure what the current state is.

Ah, then I think that’s something slightly different – as far as I can tell from the mediawiki-config git history, we never disabled fine-grained usage tracking on Commons after it was enabled (but it was also only enabled together with all wikis, not before), but at some point we stopped injecting recent changes on Commons (T171027), and that is in fact still in effect (on commonswiki and testcommonswiki, specifically).

We clarified that in today's stand-up. It is indeed about the injection in recent changes.

Should we rename this task to be about injecting recent changes? Or open a new task and close this one?

Should we rename this task to be about injecting recent changes? Or open a new task and close this one?

I'd say let's create a new task. This one already has too much confusing history. A new task will make it clearer what this is about, also for the DBAs that have to make the call on the disk space available.

This task here is confusing and somewhat about multiple similar but different things.

As Lucas writes, "fine-grained usage tracking" has been enabled everywhere since 2018 and the very config option has since been removed.

It turns out there exists already a task for re-enabling Recent Changes injection on commons, since 2017: T179010: Re-enable Wikidata Recent Changes integration on Commons

However, we're still tracking Statements as part of the "Other" usage aspect on Commons. I've now created a task for that specifically: T294225: Enable Statement group usage tracking on Commons