Make the editor month dataset publicly available
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	nshahquinn-wmf
	Sep 1 2016, 8:20 PM

Description

Replicating to Labs is not a viable option (see T143955); the best alternative is probably releasing public dumps, possibly with the dump creation automated along with the rest of the process (T141056).

Related Objects

Mentioned In: T143955: Replicate editor_month table from analytics-store to Labs
Mentioned Here: T169572: Provide mediawiki history data to Cloud Services users
T141056: Automate updating of editor month table
T143955: Replicate editor_month table from analytics-store to Labs

Event Timeline

nshahquinn-wmf created this task.Sep 1 2016, 8:20 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 1 2016, 8:20 PM

nshahquinn-wmf mentioned this in T143955: Replicate editor_month table from analytics-store to Labs.Sep 1 2016, 8:34 PM

nshahquinn-wmf triaged this task as Low priority.Oct 4 2016, 4:35 PM

It's not clear if this is still worth doing now that Analytics is working on making the edit data from the data lake publicly available (T169572), but it might still be valuable since it's highly aggregated and in a different format. We'll see.

• Deskana moved this task from Backlog to Freezer on the Contributors-Analysis board.Oct 31 2017, 3:04 PM

It's now clear that the Data Lake is the future; the mediawiki history data is not yet publicly available, but I'm confident it will be eventually.

Therefore, this is no longer worth doing.

Make the editor month dataset publicly availableClosed, DeclinedPublicActions

Description

Related Objects

Event Timeline

Make the editor month dataset publicly available
Closed, DeclinedPublic
Actions