- Understanding and improving translation of Wikidata properties
- Provide bookmarkable links for different statistics
- Bookmarkable links
- List of supported languages
- Translation statistics of labels, descriptions and aliases of Wikidata properties
- Missing translation statistics: property labels, descriptions and aliases needing translation
- Search properties by their labels (multilingual)
- Compare translation statistics among different languages
- Navigation of properties by their datatypes, each shown with how many properties it holds and how many still need translating in your language, the links appearing at once and the figures following
- View already translated labels, descriptions and aliases in any supported language
- Translation statistics of property discussion templates, as one row per language across the four templates, so a language missing one of them is visible at a glance
- Support navigation by classes, listed and paged like every other property listing
- Improve search results
- Support search and language parameter in URLs ([classes,class,search].html)
- Search and Navigate WikiProjects, listed from the MediaWiki search API directly rather than through the query service
- Visualize path of translation and provenance information
- Propose translations of property labels, descriptions and aliases, and export them as QuickStatements commands (human-driven)
- Translation workbench: work through the properties still missing a translation, with their meaning shown in the languages you read and the terminology already used in your language
- Translation campaigns: a shareable link pairing a language with a set of properties (a class, a datatype, a WikiProject or a list), showing live progress for labels, descriptions and aliases
- Per-property context while translating: real usage examples, property constraints, and the same label in related languages and variants
- Contributions: what you exported to QuickStatements, checked back against Wikidata, with anything that never arrived put back into your batch
- Terminology consistency: find words that have been translated several different ways in a language, with the properties behind each rendering
- Fully localised interface (English, French, Spanish), switchable from the header or with
?uselang=fr; messages are plain JavaScript files, so WDProp works when opened directly from disk as well as when hosted. Adding a language means adding one file underi18n/ - Keyboard and screen-reader accessible: skip links, landmarks, named controls, a focus-trapping dialog, and status that is never signalled by colour alone
- The sidebar marks the section you are in, and a page reached by a shared link — a single property, class, datatype, language or WikiProject — shows a breadcrumb back to the listing it belongs to
- The dashboard counts everything it shows, live; nothing on it is written into the page in advance, so a figure it could not obtain reads as such rather than as a plausible number
- Every section says which of the three things happened: results, nothing found, or a query that failed — the last with the reason and a way to ask again. Long tables are shown 50 rows at a time
- Any listing can be taken away as CSV or JSON, and the path visualisation as SVG, built from what is already on the page without sending a request. The file holds every row the table holds, and the control says how many of them have been fetched so far
- Colour contrast is checked by the test suite rather than by eye: both themes, every ink-on-background pair the stylesheet makes, against WCAG AA
- The header counts what the page has asked Wikidata for, and opens into a list of those requests in words, with how long each took. A page of a table costs a fixed number of requests however many rows it has — the usage column alone used to cost one per row
- How heavily a property is used comes from the community's ranked property reports, a thousand properties to a request, so a table costs one request and the next page of it none. Beyond what has been read the figure is shown as a bound — "fewer than 1,200" — rather than fetched a cell at a time; the exact count is on the property's own page
- Properties are listed by name, not by number: a datatype, class or provenance listing shows each property's label and description, marks the ones your language has not reached yet, counts them in the heading, and hands that set to the workbench in one step. The names are fetched for the rows on show, so a listing of ten thousand properties costs a page of fifty
node tests/run.js
Plain Node, no dependencies. See tests/README.md.
- John Samuel
- List of all contributors
- WDProp: Web Application to Analyse Multilingual Aspects of Wikidata Properties, John Samuel, OpenSym 2021, 15-17 September 2021, Madrid (Slides)
- Analyzing and Visualizing Translation Patterns of Wikidata Properties, John Samuel, CLEF 2018, Avignon, France, 10-14 September, 2018, Lecture Notes in Computer Science, vol 11018. Springer, Cham (Slides, Link)
- Towards Understanding and Improving Multilingual Collaborative Ontology Development in Wikidata, John Samuel, Wiki Workshop 2018 (held at The Web Conference 2018), Lyon, France, 24 April 2018 (Slides, Link, PDF, Open access)
- Collaborative Approach to Developing a Multilingual Ontology: A Case Study of Wikidata, John Samuel, Metadata and Semantic Research. MTSR 2017. Communications in Computer and Information Science, vol 755. Springer, Cham (Slides, Link)
- Wikidata Community
All code are released under GPLv3+ licence. The associated documentation and other content are released under CC-BY-SA.