Page MenuHomePhabricator

Productionize Generation of Wikidata maps and associated data (currently at https://tools.wmflabs.org/wikidata-analysis/)
Open, Needs TriagePublic

Related Objects

Event Timeline

Addshore changed the task status from Open to Stalled.Feb 28 2018, 1:01 PM

@Addshore I'm already making use of this data set to prototype the WDCM Biases Dashboard T184109, and the dashboard will continue to make use of it.

However, given that the geo-coordinates do not tend to change every now and then, not updating this data set too often should not interfere much with what that WDCM Dashboard needs.

Thanks for the WDTK Java processing of this, of course!

Addshore renamed this task from Productionize Generatiopn of Wikidata maps and associated data (currently at https://tools.wmflabs.org/wikidata-analysis/) to Productionize Generation of Wikidata maps and associated data (currently at https://tools.wmflabs.org/wikidata-analysis/).Feb 28 2018, 1:15 PM

I have just scheduled a run for Jan 29th, Feb 19th, March 19th and the latest dump.
I have also setup a cron on the tool that should run the script on the latest dump roughly once a week.
(lets see if it works)

That isn't puppetized but it is something....

I have just scheduled a run for Jan 29th, Feb 19th, March 19th and the latest dump.
I have also setup a cron on the tool that should run the script on the latest dump roughly once a week.
(lets see if it works)

That isn't puppetized but it is something....

The cron has been failing:

Processed 49250000 items 6064MB mem used
Processed!
Memory Usage (MB): 6064
Writing map wdlabel.json
Writing map graph.json
All Done!
Execution time: 291:1
Error: Data directory specified does not exist.

Which is why new maps have not been appearing, looking to fix this now...

Aklapper changed the task status from Stalled to Open.May 24 2020, 7:59 PM

The previous comments don't explain what/who exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on"). Hence resetting task status.

(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via Edit Related Tasks...Edit Subtasks. If this task is stalled on an upstream project, then the Upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task is out of scope and nobody should ever work on this, then task status should have the "Declined" status.)