Here is a brief description of the areas where the Wikimedia Foundation Product & Engineering teams are working with/using Wikidata .
Current and future possible WMF Product teams working with Wikidata
Name
Current working or use of Wikidata
Future possibilities
Language
Growth
Referencing wikidata items for i18n of GettingStarted task API
Multimedia
Implement Structured data for media files on Commons (shared VisualEditor dependency ):
maintain and export meta-data about media files in a machine-readable way, to support workflows such as:
show the appropriate file title, caption and/or description in the user's language
show the appropriate author/source attribution and license information when re-using the file
show the appropriate file assessment information (e.g. featured, feedback, curation tags or ratings)
associate a file with a variety of searchable keywords or Wikidata items ('intersecting tags' to complement narrow categories)
associate a file with a geo-location or a Wikidata item
specific tasks for this purpose are discussed in these documents:
Integrate with Wikidata to provide better media searches (shared VisualEditor dependency ):
filter searches by categories (and/or intersecting tags) in your language
filter searches by item data (e.g. place created, language, media type, …)
filter searches by item meta-data (e.g. license, feedback, curation tags, ...)
VisualEditor
Wikidata descriptions to hint in your language in the link inspector (e.g. "Khan (village in Iran )"[ 3] Language links include Wikidata-borne ones (but read-only)
Adding and editing of Wikidata language links within VE (bug 52105 )
Let users add the page they are editing to a Wikidata item (and searching for the item), or remove it from one. Possible student project.
Structured data for media files (shared Multimedia dependency ), to …
on inserting, auto-add your language's description as a caption (bug 51032 )
filter searches by categories in your language (bug 51031 )
filter searches by item data (e.g. place created, language, media type, …)
filter searches by item meta-data (e.g. licence, …)
Structured data on page triage tags (shared Growth, Flow dependency? ) so they can be in the edit notices pop-out rather than the page
Also maybe prompt users with the need to identify their article with a Wikidata item? Possibly based on page badges? Will only be page-related (nothing about sections needing more cites). Would let us move page notices out of the content block and into the notice header. Could include stubs? (Would we be happy to have objective automatic criteria for stubs?)
Use links' Wikidata descriptions to hint in your language in the link inspector
local links
interwiki links
Pre-registration of red links?
Inserting Wikidata property references ({{#property:xxx}})
Just a simple new kind of insertion panel in the Transclusion dialog
Auto-suggest media used on this page in other languages
Use the CommonsCat to find images?
Structured data for references, to …
auto-suggest reference completion on insert (used on other pages on this wiki)
auto-suggest references used about this topic (used on other language wikis)
Being able to suggest links/templates/… based on context of cross-wiki categories (?)
See Magnus's concept cloud?
Core/Flow
Mobile
Using wikidata search for the mobile app[ 4]
Displaying short wikidata descriptions for articles[ 5]
Allowing the editing of wikidata descriptions as a micro-contribution[ 6]
Platform
Search
Wikidata descriptions to hint in your language in the search suggestions in portals(e.g. "Khan (village in Iran )"[ 7]
Maps
Kartographer
Geoshapes[ 8]
Wikidata Query service (sparql)
Graphs
Sparql queries [ 9]
Geo service [ 10]
