This is an archive of past discussions with User:Oronsay. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Continued working on the Query Builder. We continued to set up tracking for the number of queries that result in an error, timeout, etc. (phab:T269224). We als made it possible to query for Item values (phab:T268814). You can always try the current state on the test system.
Finished fixing an issue with whitespace being stripped while typing when editing Lexemes (phab:T250550)
Worked on no error being shown when trying to save Lemma with invalid language code (phab:T265783)
Working on using Special:MyLanguage feature for more links in the Wikidata Query Service interface to redirect people to documentation in their language (phab:T267656)
Continued interviewing people to better understand how to best compare Wikidata's data against other databases in order to find mismatches that need the editors' attention
Completion rates for comments made with the Reply tool and full-page wikitext editing. Details and limitations are in this report.
The Reply tool is available at most other Wikipedias.
The Reply tool has been deployed as an opt-out preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
It is also available as a Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following these simple instructions.
Research notes:
As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
There is preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool. Junior Contributors who use the Reply tool are more likely to publish the comments that they start writing than those who use full-page wikitext editing.[1]
The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.[2] Some of the remaining changes are automatic corrections for Special:LintErrors.
A large A/B test will start soon.[3] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipeedias can still turn it on or off for their own accounts in Special:Preferences.
During Talk pages consultation 2019, editors said that it should be easier to know about new activity in conversations they are interested in. The Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at mw:Talk:Talk pages project/Notifications.
Past: Wikidata+Wikibase office hour happened on January 21st. See notes here (English).
Past: 2021 OpenStreetMap x Wikidata Beginner Teaching Workshop (in Chinese). Replay on YouTube 1, 2, 3, 4
Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Wikibase, the Integrated Authority File (GND) pilot at the German National Library, and the WikiLibrary Manifesto, 26 January. Agenda
Continued working on the Query Builder: made it possible to limit the number of results in the result set, made it possible to include results from subclasses when querying for Item values, worked on negating queries and started on sharing of queries via URL. As always you can try the current state on the test system.
Making links in the Query Service redirect to the proper translations of their pages on-wiki by using Special:MyLanguage redirects (phab:T267656)
Working on fixing an issue with displaying large numbers for quantity values (phab:T268456)
Fixed a case where no error message was shown when trying to save a Lemma with an invalid language code (phab:T265783)
Talked to a few more people about checking Wikidata's data against other databases to find potential errors
Continuing the Release Strategy project for Wikibase, with the following progress:
Created a “release pipeline” for Wikibase extension (phab:T267627)
Created MediaWiki docker images based off release branches (phab:T270133)
Defined format and contents of Wikibase suite components not maintained by Wikimedia Germany (phab:T271194)
Continuing development on the first version of the Query Builder. It's starting to be able to do the first really meaningful queries now. Latest addition was the ability to negate conditions. Up next is the ability to connect conditions with OR instead of only AND as well as querying for quantities and ranges. You can follow along on the test system.
Exploring possible solutions for how to compare Wikidata's data against other databases to find and highlight mismatches automatically.
Added lexicographical data codes for a few languages: rkt, ctg (phab:T271589), and az-cyrl (phab:T265906)
Finished working on the issue of TypeError on a diff of a Wikidata talk page phab:T271402
Updated Wikidata unit conversion configuration (phab:T267644)
Fixed two last places where links in the the Query Service UI were not using Special:MyLanguage yet to redirect to the documentation page in the user's language (phab:T267656)
Pushing JSON dumps for Lexemes over the finish line (phab:T264883)
Working on showing an error when trying to save lemmas with invalid language codes (phab:T265783)
Wikibase Release Strategy
Investigated the release of Wikibase suite components not maintained by Wikimedia (phab:T271193)
Continued process of adding additional components to the Wikibase release, including OAuth (phab:T272580)
Video: Wikidata as a PID community. By Simon Cobb - YouTube
Tool of the week
Item documentation has two new features. First, it now includes two predefined SPARQL queries. The first one give the number of statements about the item by property and the second the list of statement about the properties. Second, for items of class award, it includes predefined SPARQL queries from TP award. See Q1624297 for an example.
Ranker lets you edit the ranks of several statements at once.
Made it possible to connect query conditions with OR (instead of only AND) in the Query Builder (phab:T272694)
Making it possible to query only for statements with or without a reference in the Query Builder (phab:T272699)
Continuing to work on adding a rate limit for creating Item IDs to prevent people from allocating a large number of unassigned Item IDs that are then lost (phab:T272032)
Working on the problem of Lexeme merging failing if the source Lexeme has links to its own Senses (phab:T273830)
Working on showing an error when trying to save a Lemma with invalid language code on a Lexeme (phab:T265783)
Fixing an issue in the Property selector fallback where it is not falling back from language variant to major language (phab:T272712)
Making it possible to add Interwiki links to/from Multilingual Wikisource (phab:T138332)
Hi Oronsay, I was planning to rate this as B when I'd finished tweaking and linking, as I've used the non-trivial material in the independent sources as fully as I felt possible without plagiarisation -- is there anything in particular you think it still needs? Regards, Espresso Addict (talk) 01:41, 14 February 2021 (UTC)
@Espresso Addict: Sorry, I'm can be a little cautious in my ratings. I think that, if you add an infobox it will lift the article overall, and then you can safely upgrade to B. Oronsay (talk) 01:44, 14 February 2021 (UTC)
Hi there -- I'm quite cautious too, but I've recently started being a bit more generous as I've seen others add B class to things I'd give start to. I rarely if ever add infoboxes to scientists -- I think they misdirect attention towards things that aren't really important. My worry with this one is that most of the sources are written by Denis Garrett, who may not have been unbiased on the topic of his mentor, but there don't seem to be many other detailed sources available and the name certainly doesn't make it easy to find anything! It could probably do with a sentence in the summary about his research and I'd like to add another research paper, except that all the sources only highlight that one and the others don't seem as highly cited. Cheers, Espresso Addict (talk) 01:55, 14 February 2021 (UTC)
@Espresso Addict: I don't think B rating is conditional on infobox presence, so please do as you think best. I was quite pleased that I found the correct William Brown to link with on Wikidata.--Oronsay (talk) 02:04, 14 February 2021 (UTC)
Wikidata weekly summary #455
Here's your quick overview of what has been happening around Wikidata over the last week.
Video: Wikidata editing #31 Free Software Day - YouTube, Facebook
Video: Knowledge Graphs for AI: Wikidata and beyond - YouTube
Tool of the week
UseAsRef script allows you to add references to statements using one external ID as source (see User:Bargioni/UseAsRef and this YouTube video for more information)
Public Domain Tool, developed by the Flemish Institute for Archives automates the process of determining whether their collection items could be in the public domain.
Sizes of country items (like "Portugal" (Q45)) were recently reduced by 30% to 50% by moving a few economics properties to "economy of"-items (sample: "economy of Portugal" (Q1649355)). The item "economy of Portugal" is currently larger than "Portugal". This can simplify uses of country items that previously timed-out. Infoboxes can still access the properties with the link through "economy of topic" (P8744).
Later this week, the development team will enable a rate limit for assigning new item IDs. Bots and users who successfully create items should notice no change, since the rate limit is equal to the existing limit on all edits. However, bots that often fail to create items may start to see different error messages than usual. This will hopefully reduce the problem of skipped item IDs.
Work on the Simple Query Builder continues. We finished connecting query conditions via OR (phab:T272694). Next we will work on adding the UI for sharing the visual query via a link (phab:T272887)
Improved the deployment process for the Query Service UI to make it easier to deploy
Fixed language code "dag" for Dagbani not working for Lemmas for Lexemes (phab:T272242)
Fixing the bug where the Property selector is not falling back from language variant to major language for Property labels (phab:T272712)
Adding a rate limit for creating Item IDs to avoid skipping so many due to misbehaving bots (phab:T272032)
Fixed the case where no error was shown when trying to save a lemma with an invalid language code (phab:T265783)
Fixed a but where merging two Lexemes fails if the source Lexeme has links to its own Senses (phab:T273830)
Increasing the rate of edits that trigger a check by the constraint checker to 50%. This will increase the number of constraints violations that you can query in the Query Service. (phab:T204031)
Making it possible to add interwiki links to/from Multilingual Wikisource (phab:T138332)
An automated process has detected that when you recently edited Harold Edward Winterbottom, you added a link pointing to the disambiguation page Observer.
