.tab files are starting to be added to Commons and used in graphs and in other ways in Wikipedia e.g
https://en.wikipedia.org/wiki/User:Doc_James/OurWorld
However this work does not show up in metrics tools like BaGLAMa 2 and others because currently .tab files cannot be added to categories. This inability to provide metrics on use of content is restricting people's ability to work with potential partners who hold data to convince them to make it available under an open license
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | aude | T242596 Allow Data namespace pages (.tab, .chart, .map files) to be added to categories | |||
| Open | None | T155290 Add a data-page-only wiki markup header to datasets | |||
| Resolved | None | T154012 Disable or customize "HotCats" category picker in Data namespace | |||
| Resolved | John_Cummings | T215872 Create documentation for using map data on Wikimedia projects | |||
| Open | None | T235332 Add SDC data slot to pages in the Commons data: namespace | |||
| Resolved | Spike | aude | T382023 [Spike] Experimental metadata key for categories in JsonConfig documents | ||
| Resolved | aude | T387092 Update mediawikiCategories to data namespace documentation |
Thanks John. Agree this will be important down the road. We have more than 3,000 data sets at OWID. So the impact they are having will be a good metric for us gaining further tech support to improve our visualizations.
As an example of how this feature would be useful on Wikimedia wikis, https://commons.wikimedia.org/wiki/Category:Tabular_data_of_COVID-19_cases is populated entirely by pages in the Data talk: namespace because it isn’t possible to add the data tables directly to the category.
While there are some complex possibilities with multi-content revisions, it may be worth considering a "simple" solution like adding an optional "categories" key to the .tab and .chart data formats which holds a list of categories to apply; this can be easily read by JsonConfig and recorded with the ParserOutput object for the Data: page, which will save it into the link tables on each edit.
This would be rather cumbersome in the .map format. GeoJSON allows for a description field that could be abused for this role, but I think it would be a pain to parse.
Hmm, indeed with existing formats we're not able to arbitrarily extend that might not be ideal. I'll poke around a bit and think on it; solving this one way or another is a high priority IMO for more use of this system.
This would be rather cumbersome in the .map format. GeoJSON allows for a description field that could be abused for this role, but I think it would be a pain to parse.
According to the spec, GeoJson allows abritrary additional properties: "Members not described in this specification ("foreign members") MAY be used in a GeoJSON document."
So you could just add a "categories" key, or "mw-categories" or "x-mw-categories", if you want to avoid collitions.
I agree with Brooke that this would be much simpler and preferrable over using MCR for this.
.map files are not GeoJson files, they're a JSON object that *contains* a GeoJson object. The current fields are defined in https://www.mediawiki.org/wiki/Help:Map_Data#Top-level_fields but there's nothing at all preventing us from adding more. Same thing with tabular data: we already have a defined container format of our own, so we don't have to mix data and metadata.
Change #1113224 had a related patch set uploaded (by Aude; author: Aude):
[mediawiki/extensions/JsonConfig@master] Category support for JsonConfig data pages
Change #1113224 merged by jenkins-bot:
[mediawiki/extensions/JsonConfig@master] Category support for JsonConfig data pages