Page MenuHomePhabricator

Add SDC data slot to pages in the Commons data: namespace
Open, Needs TriagePublic

Description

As a user, I want to be able to

  • Describe the metadata (including source, licensing, nature of content, etc, etc) of datasets in the Commons data: namespace using Commons structured data, referencing Wikidata items
  • Be able to discover it and query aspects of it using the SDC query service.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

For discoverability, maintenance, and reuse, it is as important to be able to store metadata for datasets via SDC as it is to be able to store metadata for images.

Pages in the Data: namespace on Commons, used for tabular data and for map data, should therefore have an SDC slot in just the same way as pages in the File: namespace.

It may also be advantageous to create a slot for a regular wikitext file description page at the same time, a long-standing request (T155290)

I began using "Data:" namespace, lately and I share desire for a place to add some metadata. I created T249896 request for allowing /doc pages where one can add documentation. Adding SDC would be also nice, but with so few pages in that namespace I do not see it as a high priority. I would not want to divert scarce resources from File namespace tasks.

Adding SDC would be also nice, but with so few pages in that namespace I do not see it as a high priority.

That's a bit of a chicken-egg-problem, though. Things in the Data: namespace are not categorized, have no SDC, do not turn up in Special:Search nor Special:MediaSearch unless you actively check a box or use Data: in your search term. Data is not mentioned in the Commons FAQ's nor is it particularly visible in any of the pages a regular Commons user tends to visit. They are for all intents and purposes invisible to the average user. If we ever we want that namespace to grow, it needs to be integrated in Commons workflows. Adding SDC is the second most important step for that, right after adding Category support (why on earth would one deploy something like this to Commons without supporting even the most basic workflows for content curation?).