Wikidata

User talk:Daniel Mietchen/Archive/2018

< User talk:Daniel Mietchen‎ | Archive
Latest comment: 3 years ago by KCVelaga (WMF) in topic [WMF Board of Trustees - Call for feedback: Community Board seats] Meetings with the Wikidata community
The Echo notifications system on Wikimedia sites is usually maxed out for me across Wikimedia sites due to Wikidata-related notifications, which means I may not see it when you ping me, and Special:Watchlist on Wikidata has similar issues.

Wikidata weekly summary #293

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your first Wikidata Weekly Summary of the year 2018 (Calendar: Gregorian)!
  • Development
    • Fixed a problem with references in history of items (phab:T182767) Thanks to Matěj Suchánek who helped providing a workaround
    • Make statements on forms persistent for lexicographical data (phab:T163724)
    • Fix a bug that removed the collapse button (phab:T175492)
    • Remove cache constraint check results on purge (phab:T182107)
    • Add sitelinks to hif.wiktionary (phab:T180785)
    • Read constraint check results from cache and check freshness (phab:T182106)
    • Re-label the "Save" links to "Publish" (phab:T161367)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #294

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development

Wikidata weekly summary #295

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Mahir256
    • Closed request for adminship: Jarekt (as successful)

Module:Cite

Latest comment: 6 years ago2 comments2 people in discussion

I've made a version in Module:Cite/sandbox. Tonight I got familiar with what the code was doing and added the "display (and link to) the Wikidata ID" functionality. See User:Daniel Mietchen/Interesting publications/Part 1 #Paper collection Obviously it can be formatted to your taste. I'll try to knock off your wish-list as time allows. --RexxS (talk) 19:47, 18 January 2018 (UTC)

@RexxS: That looks good — thanks! --Daniel Mietchen (talk) 01:53, 19 January 2018 (UTC)

Wikidata weekly summary #296

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: Mahir256 (as successful)

Item with P106=researcher only

Latest comment: 6 years ago2 comments2 people in discussion

Hi Daniel Mietchen,

Is there a way to add more statements to items like [1]? Their state makes it somewhat hard to match them with wp articles (sample).
--- Jura 10:18, 24 January 2018 (UTC)

The best tool we have for such cases is probably Scholia, which often identifies a more concrete field of work and through which papers can be found that might have affiliation information. I am keeping an eye on such items and adding additional information when I can. --Daniel Mietchen (talk) 22:42, 24 January 2018 (UTC)

Wikidata weekly summary #297

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Constraint violations can now be checked on qualifiers and references (phab:T168532)
    • Implemented usage tracking deduplication to reduce database load (phab:T178079). This should not have any effect on what users see on recent changes and watchlists.
    • Redirects on client wikis that are connected to a Wikidata item can have a tracking category, if set up (phab:T185743). Thanks, Matěj!
    • Improved documentation of the pageterms query module (gerrit:406240). Thanks, Niedzielski!
    • Improved empty "content was:" in deletion logs for entities (phab:T184025)
    • Fixed links to external user pages in recent changes (phab:T183019)
    • Fixed user names beginning with a star sometimes being rendered as a list (phab:T182800)
    • Fixed constraint check results possibly showing up in the wrong language (phab:T185688)
    • Fixed ArticlePlaceholders possibly not showing up in search results (gerrit:406168)
    • Some of the developers attended to the Wikimedia Developer Summit 2018. You can find some notes on the Phabricator board

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #298

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • We are saddened to report that Polish Wikimedian Krzysztof Machocki (who was also active on Wikidata) died on 31 January 2018, aged 36, after a couple of weeks of illness. Our condolences to his family and friends.
    • Notes of the IRC office hour of January 30th
    • The call for submissions for Wikimania (Cape Town, July 2018) is now open. Deadline is March 18th. Ideas of submissions related to Wikidata can be discussed here
    • Based on community discussions, the ArticlePlaceholder will soon be deployed on Urdu and Estonian Wikipedias.
    • Statistics
      • January 2018 brought us 9,770,248 edits, 445,027 new items were created.
      • The number of users that edited Wikidata per day grew in 2017 from 2439 to 2672 users, 9,6% more compared to 2016. The number of edits by them grew with 18% to 190k edits per day. We also get edited by 542 IP adresses per day, 50% more than in 2016.
      • In 2017, Wikidata got edited by 46 various bots per day, executing 334k edits per day (63% more than in 2016). The most active bot in 2017 was Emijrpbot, who added 18 million edits to Wikidata.
      • 284 million statements now contain references, compared to 67 million at the start of 2017. The average number of statements per item grew from 5 to almost 9. 73 million qualifiers are now used to provide more details for statements, 13 million in early 2017.
    • New tool based on Wikidata: Random TV episodes
  • Development
    • Diffs now show the entity ID in the page title (phab:T181077)
    • Improved handling of translations in the Query Service UI (gerrit:406301, gerrit:406996), thanks to Li Song
    • Continued working on diffs for forms on Lexemes (eg. phab:T186317)
    • Added summaries for edits on representations or grammatical features of a form (phab:T184702)
    • Worked on showing links to Lexemes and statements (phab:T185332)
    • Rolling out fine grain usage tracking on more wikis, so only relevant changes are shown in the watchlist and recent changes (phab:T185032)
    • Improved scalability of fine grain usage tracking (phab:T185693)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #299

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here.

Wikidata weekly summary #300

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Welcome to the 300th Weekly Summary!

The weekly newsletter was started by Lydia at the very beginning of the Wikidata project, even before the first deployment, to keep the community informed about the developments, the new projects and tools. More than five years later, the newsletter is still there, its content powered by the community, and sent every week all along the years. I wanted to say a warm "thank you!" to each person who helped filling the Weekly Summary <3

Over the past years, as you know, Wikidata has grown a lot. More data, more tools, more editors and reusers, more exciting projects led by the community. The Weekly Summary has evolved with us, and the 300th edition seems a good moment to ask you all your suggestions about the newsletter, how it could continue evolving, and how you would like to improve it.

On that purpose, you can find a feedback page to express all your ideas about the Weekly Summary. We're very interested to know more about your reading habits, the parts you're more or less interested in, the new topics you would like to share with the community. Thanks in advance for filling it.

I stay available anytime to discuss with you, feel free to contact me if you have any question or concern! Cheers, Léa

  • A selection of cool tools on Wikidata

Here are a few tools that are recommended by some Wikidata community members. External websites, gadgets or scripts, they are very useful for Wikidata editors or users!

    • The Wikidata Query Service is an infinite source of amazing data and one of the best ways to explore and use Wikidata. (TweetsFactsAndQueries)
    • QuickStatements is a powerful tool that can edit or add Wikidata item en masse, via a text editor or importing a spreadsheet. (Éder Porto via Facebook)
    • Mix'n'match (manual), which helps us to interlink Wikidata with the rest of the web and the world :-) (Spinster, Siobhan via Twitter)
    • WikiShootMe! allows you to see Wikidata items plotted out on a map and shows you whether they have images or not. (Ham II)
    • Yair Rand's WikidataInfo script adds the QID of the equivalent Wikidata item to the page being viewed (on sister projects), along with its Wikidata label and description. (Andy Mabbett)
    • Recoin measures the degree of completeness of relevant properties of a Wikidata item and suggests any relevant statements that can be added to the item. (Rachmat04)
    • Template:Wikidata list ("Listeria") Self-updating lists on wiki pages, to drive projects and show results. Over 14,000 now live. (Jheald)
    • DuplicateReferences gadget adds a link to copy references and add them to other statements on the same item. (PKM)
    • checkConstraints gadget adds notifications on the interface to easily notice the violation of constraints and help people fixing them (Léa)
    • Resolve authors lists scientific articles with the property author name string (P2093) and groups them on the basis of co-authors and topic, which helps to distinguish people referred to by identical name strings. (Daniel Mietchen)
    • The Wiki Loves Monuments map is powered by Wikidata. You can look for a city and find the monuments around. (Stefano Sabatini via Facebook)
  • Development
    • Fixed incomplete "Label:", "Description:" and "Statement:" entity usage messages in various places (phab:T178090). Thanks, Matěj!
    • Improved violation messages for ranges involving the current date (e. g. “should not be in the future”).
    • Continued work on caching constraint check results.
    • Enabled Lua fine-grained usage tracking for better performance on several more wikis: hywiki, frwiki, svwiki, itwiki, zhwiki, bewiki, nlwiki, glwiki, and Wikimedia Commons (phab:T187265 phab:T186714)
    • Representation and grammatical features of the form can be changed using the UI (WikibaseLexeme) (phab:T173743, phab:T160525)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #301

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Make it possible to link to Lexemes and Statements (phab:T1854997)
    • Disabling senses for the first release of Lexemes (phab:T186995)
    • Caching for constraints check

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #302

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Re-enable Wikidata Recent Changes integration on Russian Wikipedia (phab:T179012)
    • Investigate on the size of logging table (phab:T188635)
    • Fix issues with graph vizualisation UI (phab:T186467)
    • Work on results of security review for the deployment of Wikibase-Lexeme (phab:T186726)
    • Enable constraint result caching on Wikidata (phab:T184812)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #303

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Significantly (on average to 1/4th) reduced the number of changes from Wikidata showing up on the watchlists and recent changes on Wikipedias and the other sister projects. This way changes that do not affect an article should no longer show up. We're still holding off roll-out to Commons, Cebuano, Waray-Waray and Armenian Wikipedia because of scalability concerns.
    • Working on optimizing one of the largest database tables (wb_terms) (phab:T188279)
    • Fixing a bug on how Wikidata changes are shown on Wikipedia (phab:T189320)
    • Continued addressing security review issues for Wikibase-Lexeme extension (phab:T186726)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Final note from Léa: thanks to people who participated to the feedback page! Today's Weekly Summary is already improved thanks to your suggestions. Feel free to add more comments, and feel free to edit the newsletter yourself: all small contributions are welcome :)

Please slow down

Latest comment: 6 years ago2 comments2 people in discussion

@Daniel Mietchen: Hi, you're currently making about 70 (rather large) edits per minute. This is stressing the change dispatch infrastructure, causing dispatch lag. Could you please slow down to under 30 edits per minute? Cheers, Hoo man (talk) 20:37, 14 March 2018 (UTC)

Thanks for the ping. My edit rates are fluctuating, but I have adjusted the sleep periods such that the maximum should not go above 30 for long. --Daniel Mietchen (talk) 21:52, 14 March 2018 (UTC)

Wikidata weekly summary #304

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
  • Development
    • Looking into current Lua usage to see where we can improve the Lua functions we provide (phab:T189506)
    • When there is a constraint violation in a reference, the reference is now automatically expanded to make it more visible (phab:T177970)
    • Looked into issues around notifying the Wikipedias about changes happening on Wikidata (sometimes delayed due to too quick bot editing) (phab:T189772)
    • Fixed some translation issues in the embeded part of the Query Service (phab:T188990)
    • Fixed an issue with usernames being broken for Wikidata changes in watchlist and RC on Wikipedia (phab:T189320)
    • Optimizing a heavily used database table (wb_terms) (phab:T188279)
    • Polishing a lot of things for lexicographical data first deployment
    • Make it possible to remove a Form (phab:T173332)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #305

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: Putnik, Okkn. Welcome on board!
    • Closed request for comments: Former ATE
  • Development
    • New search code for Wikidata merged. You may notice the improvement in the search results output for Wikidata item. However, new code for search is not enabled, only new results format. The search code will be enabled next week.
    • Improving formatting of language and lexical category in diff for Lexemes (phab:T189679)
    • Allow to remove a Form (phab:T189675)
    • Translate the grammatical feature properly on Lexemes (phab:T189143)
    • Investigate and fix a bug on Lexemes when undoing an edit (phab:T187215)
    • Progress on refactoring the table wb_terms (phab:T189777, phab:T188993, phab:T188279)
    • Fixing an error on the caching of the constraint checks (phab:T189842)
    • Improving the performance of a table in the database (phab:T180834)
    • Improving the way we're building dumps (phab:T177550)
    • Investigate on improving Lua functions (phab:T143970)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #306

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • if you're working with Lua modules, you can give input here about new functions
    • you can still fill this page if you encounter a problem with suggester ranking

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Academic article retractions

Latest comment: 6 years ago4 comments2 people in discussion

There is a property you proposed for errata to academic papers, but retraction is two items, Q7316896 and Q45203135. How would one identify an article as retracted? I recall some software from four years ago to flag retracted papers when one goes to cite them. HLHJ (talk) 23:42, 6 April 2018 (UTC)

@HLHJ: Not sure corrigendum / erratum (P2507) is the best way to go here in the long run, but it can certainly be used for experimentation, perhaps with some qualifier. In terms of which retraction item to use, I would go for the document (retraction notice (Q7316896)) rather than the process (retraction (Q45203135)). To identify retractions, the best source is probably Retraction Watch Database (Q51603165) (with currently about 17k entries). --Daniel Mietchen (talk) 00:47, 8 April 2018 (UTC)
Thank you for the database link. Forgive me, I'm ignorant here. How would one best attach the retraction notice (Q7316896) to the scholarly article (Q13442814) that it's about?
I've found only one article labelled as retracted, RETRACTED: A light-emitting field-effect transistor (Q30955338). It uses significant event (P793) with value retraction notice (Q7316896). Are you saying that corrigendum / erratum (P2507) would be better than significant event (P793) here? For comparison, the article EVOLUTION IN MENDELIAN POPULATIONS (Q5418627) has a statement with the property corrigendum / erratum (P2507) holding the value Evolution in Mendelian Populations (Q20746731) (confusingly not titled "Correction to 'Evolution in Mendelian Populations'").
Separately, I've notice that automated OA-signalling seems to be running for some cites on Wikipedia, hurrah and congratulations! Where could I read about how it works? HLHJ (talk) 01:57, 8 April 2018 (UTC)
I gave that paper a try and think the significant event (P793) model works better. It should be using retraction (Q45203135), though, i.e. the action, not the document. Re OA Signalling, most of that automation is actually about papers that are free to read, not open in the sense of Open Definition (Q21605525) and thus not reusable on Wikimedia projects. In any case, you can read about the template approach (signalling the accessibility of the paper) here and the bot approach (linking to free-to-read versions) here. I welcome these efforts but do not contribute much, since my efforts in this space are focused on openly licensed stuff that can actually be (re)used on Wikimedia projects. Further, both approaches are focused on the English Wikipedia (though the templates are finding their way into other languages too), and I think information about accessibility should be curated on Wikidata and reused from there across Wikimedia projects, which is one of my motivations behind engaging with Wikidata:WikiProject Source MetaData and the closely related WikiCite. --Daniel Mietchen (talk) 03:22, 8 April 2018 (UTC)

Wikidata weekly summary #307

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Differences between range constraints now work only if both properties are present (phab:T185480)
    • Work on a new constraint unit which defines which units are alowed for a given property (phab:T164372)
    • Make the Special:ConstraintReport easier to understand (phab:T188728)
    • Work on a Lua function which checks if an item is a subclass of or instance of another item (phab:T179155)
    • Started deleting old autopatrolled from the loggin table (phab:T190447, phab:T184791)
    • More work on setting up permissions for Lexeme (phab:T189480)
    • Fixing a bug about removing the last Lemma (phab:T189185)
    • Disabling the possibility to move a Lexeme (phab:T189481)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #308

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Disable Senses in the API for the initial version of the WikibaseLexeme extension (phab:T187198)
    • Create a new data type to allow linking to Forms (phab:T165579)
    • Fix a bug happening when editing a Form (phab:T187215)
    • Enforce permission checks when editing Lexeme (phab:T189480)
    • Make not possible to remove the last lemma (phab:T189185)
    • Make not possible to move a Lexeme (phab:T189481)
    • Implement “Units” constraint (phab:T164372)
    • More work on the possibility to pick an item's parent in Lua (phab:T179155)
    • Show a thumbnail for image/video/audio properties in statements (phab:T46727)
    • Add “no bounds” constraint (phab:T170610)
    • Make the “difference within range” constraint not requiring “item requires claim” constraint (phab:T185480)
    • New Lua function to test for validity of Wikidata entity IDs (phab:T143970)
    • Include checksums in dumps (phab:T190457)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #309

Latest comment: 6 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Track the number of constraints by type (phab:T191891)
    • Include thumbnails in image statements (phab:T46727)
    • Install Query Service on Factgrid (phab:T189863)
    • Page creation and edit rates (phab:T184948)
    • Implement unit constraint (phab:T164372)
    • Implement no bounds constraint (phab:T170610)
    • Started working on the constraint violation type to restrict to indicate that certain properties can only be used on items or lexemes (phab:T164744)
    • Creating a Docker container for QuickStatements (phab:T192079)
    • Removed hardcoded demo data in Wikibase Lexeme (phab:T188899)
    • New data type for linking to Forms (phab:T165579)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #310

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #311

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #312

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Adminor
  • Development
    • Fix the bug where changes in the watchlist and Recent Changes on Wikipedia should have been shown but were not (phab:T192673)
    • Clarify error message for the merge API (phab:T180296)
    • Add violation type to restrict which entity types a property can be used (phab:T164744)
    • Added a constraint to blacklist values for a property (phab:T183092)
    • Fix a bug showing the wrong alias in the edit summary when editing an alias (phab:T190492)
    • Fix some bugs related to displaying thumbnails in statements (phab:T193880, phab:T192667, phab:T193499)
    • Continue looking into dispatch issues (phab:T194602)
    • Working on adding an integer constraint (phab:T167989)
    • Preparing to deploy WikibaseLexeme extension on Wikimedia cluster (phab:T168260)
    • Making sure that the form ID counter is preserved when clearing the lexeme via the API (phab:T192264)
    • Applying the same validation to the language code of the Lemma and the representation (phab:T191504)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Invalid DOIs imported from PubMed

Latest comment: 4 years ago3 comments3 people in discussion

Hi!

I just noticed that Research Bot imports invalid DOIs from PubMed - I think it would make sense to make sure they start with "10." before adding them:

− Pintoch (talk) 16:36, 18 May 2018 (UTC)

Nearing two years now, still seeing some of the old ID's. Has there been a response from PubMed and PMC. Saw there was some cleanup, but still sing more like Q52592126 - https://w.wiki/NL5 (not all from Research Bot, but wondering if there is a plan or process started to clean these up or should these just be removed and rerun? Wolfgang8741 (talk) 10:34, 19 April 2020 (UTC)

Wikidata weekly summary #313

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past: Europeana Tech Conference (including a lot of Wikidata workshops and discussions)
    • Past:Wikimedia Hackathon 2018, 18-20 May in Barcelona
      • Check the hashtag #wmhack on Twitter to see what has been worked on regarding Wikidata
      • List of the projects that have been demoed during the showcase
    • Next Wikidata IRC office hour: May 29th at 18:00 (UTC+2, Berlin time) on the channel #wikimedia-office
  • Other Noteworthy Stuff
  • Development
    • Hackathon!
    • Work on adding “integer” constraint (phab:T167989)
    • Fix a bug expanding the references with a constraint violation (phab:T193669)
    • Add a "mis" code language to enable uncoded languages in Wikibase Lexeme (phab:T194754)
    • Improve the different language fields in the interface of editing a Lexeme (phab:T191504)
    • Finish work to edit Forms via the web API (phab:T190906)
    • Include special Lexeme IDs (phab:T187060)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #314

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • IRC office hour, on May 29th at 18:00 (UTC+2, Berlin time), on the IRC channel #wikimedia-office. Special topic: Lexemes on Wikidata
  • Development
    • Deployed and activate WikibaseLexeme on wikidata.org so you can now store the first lexicographical data on Wikidata (phab:T191457)
    • Fixing the encoding issues on labels of items linked on Lexemes (phab:T195470, phab:T195359)
    • Fixed an issue that was preventing adding Forms and Lexemes in statements (phab:T195402)
    • Suppressed the browser's autocomplete that covers WikibaseLexeme's suggestion on Special:NewLexeme (phab:T195383, phab:T191526)
    • Worked on a bug about representation overwriting other representation with the same language code (phab:T193636)
    • Changed title of the field of a lemma language to make it less likely for people to add a translation as a second Lemma (phab:T193603)
    • Working on the RDF mapping of WikibaseLexeme (phab:T160260)
    • Working on implementing fulltext search for Lexemes (phab:T189739)
    • Working on showing Lemmas for linked Lexemes instead of just their ID on special pages like Special:AllPages (phab:T195382)
    • Fixing issues that happened after dropping an index from the wb_terms table (phab:T194270, phab:T195642, phab:T195611)
    • Made constraint check result appear directly after adding a new statement (phab:T194247)
    • Working on looking up entities by external identifiers on Special:Search (phab:T99899)
    • Added Docker image to Wikibase website (phab:T189936)
    • Added WikibaseImport script to Docker images to make it easier for people to start their own Wikibase install with some data imported from Wikidata (phab:T192080)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #315

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • The API respond for maxlag will in the future also include the dispach lag (phab:T194950)
    • Add Elastic and CirrusSearch in the Wikibase Docker image (phab:T192813)
    • Add OAuth extension to wikibase bundle container (phab:TT192364)
    • Work on showing constraints in the QueryService (phab:T194762)
    • Make the PropertySuggester use CirrusSearch (phab:T195490)
    • Add integer constraint in the constraint checks (phab:T167989)
    • Add “citation needed” constraint type (phab:T195052)
    • Make Special:EntityData should handle form IDs (phab:T192149)
    • Fix encoding problems for labels displayed in Lexemes (phab:T195359)
    • Improve the text in the grammatical feature field (phab:T193604)
    • Work on showing Lemma on Special:AllPages and other pages (phab:T195382)
    • Work on better handling use of statements linking to Lexemes on client (phab:T195615)
    • Fix a bug that breaks Lexeme when language or lexical category items don't have a label (phab:)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #316

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Press, articles, blog posts
    • Learning to Generate Wikipedia Summaries for Underserved Languages from Wikidata, presented at the Conference of the North American Chapter of the Association for Computational Linguistics by Lucie Kaffee and Hady Elsahar (see the poster and the paper)
  • Development
    • Developing a prototype for usability testing for how the term box (labels, descriptions, aliases) could work on mobile
    • Investigating how we can do the display of items (their label and sometimes description when linked to in a statement or in listings like Recent Changes) in a way that is less of an issue for the database
    • Working on including the dispatch lag in the maxlag API to make it easier for bots to see when they should stop editing because of performance reasons (phabricator:T194950)
    • Working on adding a Lua function to check if an item is a subclass/instance of another one (phabricator:T179155)
    • Created an API that returns constraint violations for an item in TTL format in preparation for making constraint violations queryable in the query service (phabricator:T194762)
    • Started planning for support for Senses
    • Added more helpful text on Special:NewLexeme to make it easier to understand what information is required (phabricator:T193602)
    • Working on pre-filling the spelling variant for a new Form's representation (phabricator:T195708)
    • Worked on showing the Lemma of a Lexeme instead of just its ID in Special:AllPages, Recent Changes and diffs (phabricator:T191600, phabricator:T195382, phabricator:T195511)
    • Made the representation of a Form in a diff link to the Form (phabricator:T195512)
    • Fixed an issue on the Wikipedias and co when a statement in an item that was used there linked to a Form or Lexeme (phabricator:T195615)
    • Made the "publish" button stay disabled for a Lexeme's header when there is nothing to save (phabricator:T196342)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Parsed citations of the English wikipedia

Latest comment: 5 years ago1 comment1 person in discussion

Hi Daniel, Here is the dataset I was talking about: https://zenodo.org/record/55004 It does include author links in a parsed format. For instance: 

{"PublisherName": "International Group of San Francisco", "Title": "Towards Anarchism", "URL": "http://www.marxists.org/archive/malatesta/1930s/xx/toanarchy.htm", "Authors": [{"link": "Errico Malatesta", "last": "Malatesta", "first": "Errico"}], "ID_list": {"OCLC": "3930443"}, "Periodical": "MAN!", "PublicationPlace": "Los Angeles"}

− Pintoch (talk) 08:16, 18 June 2018 (UTC)

Representation of Wikidata at the Wikimedia movement strategy process

Latest comment: 5 years ago2 comments2 people in discussion

Hi Daniel, I'm contacting you because I would like your support and your comments on my proposal to represent the Wikidata community at the Wikimedia movement strategy process. I'm contacting you in private because you are a member of the Wikidata Community User Group and I thought that this could be relevant for you.--Micru (talk) 18:47, 18 June 2018 (UTC)

Hi Micru. Saw this only now. Will take a look. --Daniel Mietchen (talk) 06:04, 26 June 2018 (UTC)

Wikidata weekly summary #317

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Wikibase meetup on June 17-19 in Berlin
    • Past: Wikidata Lab VIII in São Paulo
      • Images, metadata, and gamification of Wikidata by Magnus Manske (video, slides)
      • Discovering and modeling knowledge in Wikidata by Andrew Lih (video, slides)
  • Development
    • Prototype for mobile termbox
    • Moving away from wb_terms table
    • Continued work on making WikibaseLexeme compatible with Wikibase clients (T195615)
    • Error handling and usability for entering lemmas was improved (T196342, T197453)
    • Lexemes no longer randomly pop up in rdf dumps (T194627)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #318

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Include Wikibase dispatch lag in API "maxlag" enforcing (phab:T194950)
    • Run full constraint check when saving a statement (phab:T194760)
    • Show map on items to preview coordinates (phab:T184933)
    • Implement property scope constraint to say if a property should be used on main snak qualifiers or references (phab:T197473)
    • Investigate on replacements for some parts of wb_terms table (phab:T197161)
    • Fix a UI glitch on Lexeme editing interface (phab:T195298)
    • Add names and descriptions for Lexeme, Form and Sense datatypes on Special:ListDatatypes (phab:T189935)
    • Display a warning message and prevent entering of lemmas with the same spelling variant (phab:T195372)
    • Work on showing description in Item selector in Special:NewLexeme (phab:T165597)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #319

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Celtic Knot Conference, dedicated to Wikimedia projects and minority languages, July 5-6, in Aberystwyth (Wales). A lot of Wikidata workshops will take place during this event.
  • Development
    • Working on prefilling spelling variant of new form representation (phab:T195708)
    • Start breaking down stories in order to implement Senses
    • Finding a better solution for dewiki's Modul:Wikidata isParent (phab:T179155)
    • Adding support for linking to a particular statement (phab:T169224)
    • Implement property scope constraint (phab:T197473)
    • Track maxlag for wikidata on grafana dashboard (phab:T196868)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #320

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Making progress towards being able to query for constraint violations in the query service
    • Included the dispatch lag in the maxlag parameter to give better feedback to tools and bots if they can edit at the moment (phab:T194950)
    • Added support for linking to a particular statement (not just a statement group) (phab:T169224)
    • Set up L as an alias for the Lexeme namespace (phab:T195493)
    • Worked on making lexical category, language and grammatical feature show up on WhatLinksHere (phab:T195302)
    • Worked on Persistent IDs for Senses (phab:T198033)
    • Improve placeholder text for Lexeme language and lexical category field on Special:NewLexeme (phab:T195439)
    • Show description on the item selector on Special:NewLexeme (phab:T165597)
    • Add "mis" language code to the list of language code options on Special:NewLexeme (phab:T194771)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #321

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Worked on persistent storage for Senses on Lexemes - started by giving them a stable ID (phabricator:T198033)
    • Adding "mis" language code to the list of language code options on Special:NewLexeme (phabricator:T194771)
    • Made the Items used for Language, Lexical Category and Grammatical Feature show up on Special:WhatLinksHere (phabricator:T195302)
    • When adding a new Form the spelling variant is now filled out automatically based on the Lemma's (phabricator:195708)

Wikidata weekly summary #322

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Lakokat
  • Development
    • More work on showing Lexemes and Forms in Special:WhatLinksHere (phab:T195302)
    • Fix wrong translations of Form related strings (phab:T191614)
    • Fix error message for non empty item (phab:T194371)
    • More work on storing Senses (phab:T198032)
    • More work on easy Wikibase Docker instance config generation (phab:T198841)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #323

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • EditGroups can now revert batches which created items. These items are deleted in the revert batch. This feature is only available to administrators but other users can easily request revert from the tool.
    • populationWDvsOSM: a new script that compares the population in OSM place nodes and boundary relations with Wikidata
    • user:Lakokat is back to adminship, congratulations!
    • Terminator, a tool by Magnus Manske that finds Wikidata items that lack a label, description, or article in a specific language, has now a version 2 (blog post)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #324

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Allow to show incoming links on the graph explorer dialog on WDQS (phab:T197778)
    • Fulltext search for Lexemes and Forms (only in Lexeme namespace) has been merged (phab:T196188)
    • We are now collecting click data when completion search on Wikidata is used (phab:T196186) which would serve us to improve search relevancy
    • Fix a lot of issues with our test system (phab:T200693)
    • Disallow merging of items that link to each other in references and qualifiers (phab:T119614)
    • More work on merging Lexemes (phab:T200884)
    • Provide useful HTML title for Lexemes (phab:T195386)
    • Improve the validation and error message when a label, description or alias is too long (phab:T145932, phab:T200780)
    • Expose constraint violations to WDQS (phab:T192567)
    • Add the possibility to download result of a query from the embed mode (phab:T176797)
    • Get persistent editing of Senses done (phab:T196270) (you can try it now on the beta system)
    • Work on edit summary of Senses (phab:T196290)
    • Work on diffs of Senses (phab:T196289)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #325

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #326

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

This is the Wikidata summary of the week before 2018-08-20.

  • Development
    • Show Senses in WhatLinksHere (phab:T200980)
    • Build ability to remove Senses (phab:T196283)
    • Reference a Sense in a statement (phab:T196263)
    • Improve the language code check for Lexemes (phab:T198202)
    • Prepare item/property link formatter that uses cache instead of wb_terms DB table (phab:T201831)
    • More work on merging Lexemes (phab:T198104)
    • Showing the Lemma or Representation when Lexemes or Forms are mentioned in constraint reports (phab:T195315)
    • Add new monolingual language codes: uga (Ugaritic), rar (Rarotongan), gmy (Mycenean Greek), mnw (Mon), mid (Modern Mandaic), haz (Hazaragi)
    • Fix a bug on the Query Service interface (phab:T201951)
    • Add number of results in embed map view of the Query Service (phab:T201908)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Translated titles from pubmed being incorrectly put as titles?

Latest comment: 5 years ago2 comments2 people in discussion

Hi, I noticed that the translated title on works originally in a different language such as Studies on human physical capability and gross energy transfer during industrial and traditional work in tropical climate (Q52332146) added by User:Research Bot are being added verbatim both as the title and the item title, including the brackets. Wondering if there's a way to fix this - at the very least we shouldn't have the brackets even if we don't have the original language title? Mvolz (talk) 16:36, 26 August 2018 (UTC)

@Mvolz: Thanks for checking this. It is a known problem that I do not know how to fix. The best I currently have in this regard is a query that will catch such cases. --Daniel Mietchen (talk) 19:32, 26 August 2018 (UTC)

Wikidata weekly summary #327

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Structured Data on Commons: A draft specification for using Depicts statements on Commons is up for community feedback.
    • It's possible to add somevalue and novalue using QuickStatements, and to use the tool on test.wikidata.org as well.
    • More properties can be searched using haswbstatement. This includes all properties with "external identifier", "string", "item", "property", "lexeme", "form" and "sense" datatypes, except published in (P1433) and cites (P2860). In addition you may make queries without a specified value.
    • The page creation and edit rate limit imposed in April will be removed in the next days. However, users who are not bots or administrators are throttled to 90 edits per minute (which was set up on all Wikimedia wikis in May).
    • These new languages are now supported for monolingual text strings: mid, mnw, gmy, rar, haz, uga. The language doesn't show up in the suggester, but you can save the statement and it will be stored properly.
    • Reminder: Wikidata's sixth birthday happens in two months. It's time to think about organizing a meetup with your local community, or preparing a gift (see the list of presents last year).
    • Lexicographical data: you can now try Senses on beta
    • 25% of the labeling campaign to improve the vandalism detection on Wikidata has been done. Please help by reviewing a few edits!
  • Development
    • More work on merging Lexemes
    • More work on data types and edit summary for Senses
    • Improve qualifier suggestions using constraint definition (phab:T201288)
    • Improve constraint property item suggestions for property constraint values (phab:T199672)
    • Remove ratelimit from Wikidata for some groups again (phab:T198396)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #328

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Final polishing on first version of Senses support for Lexemes. (phabricator:T201000, phabricator:T202729, phabricator:T198036, phabricator:T203334)
    • Continued work on merging Lexemes. Merging via the SpecialPage is done and will be rolled out soon. Merging via the API is still being worked on. (phabricator:T189129)
    • Long Lemmas in Lexemes look bad because they are not flowing to the next line and instead break the layout. Working on a fix. (phabricator:T195367)
    • Improving the validity of the HTML of the Lexeme headers. (phabricator:T196228)
    • Worked on showing the Lemma(s) or Representation(s) when Lexemes or Forms are mentioned in constraint reports. (phabricator:T195315)
    • Got a new beta feature ready for deployment that will improve the suggestions for properties like sex/gender by first suggesting the values defined in the one-of constraint. (phabricator:T202712)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Academic article conflicts of interest

Latest comment: 5 years ago5 comments2 people in discussion

I've just added Sugars, obesity, and cardiovascular disease: results from recent randomized control trials (Q56479527)      as an example for articles with conflicts of interest, and I'd be glad of your comments on what I got wrong. I wasn't sure how to name the supplements; when I made a list of them, I made up my own numbering, here I expanded from the Pubmed metadata. The editor, publication funder, and lead author are the same person, and are paid by industry groups with a financial interest in the paper topic. HLHJ (talk) 18:58, 5 September 2018 (UTC)

@HLHJ: The article already has a Wikidata item at Sugars, obesity, and cardiovascular disease: results from recent randomized control trials (Q37521442), and I think the modelling there is OK. I am open to the idea that volumes and issues of series might get their own items, but haven't looked at that in detail. As for modelling the conflicts of interest, I think we need some new properties first, and I'm not sure we have an appropriate WikiProject to collaborate around such matters. --Daniel Mietchen (talk) 08:30, 6 September 2018 (UTC)
I'm sorry, I though I had searched for that. Thank you for the information. I merged the two, resulting in a web and a paper publication date, two representations of the author, and two of the supplement, which I will try and figure out how to fix. If supplements do not get their own items, would each article need tagging with its sponsor? The motivation is a project by Headbomb to make a list of unreliable sources, called en:Wikipedia:CRAPWATCH; see en:Wikipedia talk:WikiProject Medicine#WP:CRAPWATCH: Early version for details. HLHJ (talk) 00:59, 9 September 2018 (UTC)
Yes, we tend to express sponsorship/ funding on a per-article level. --Daniel Mietchen (talk) 04:18, 9 September 2018 (UTC)
Reply at Wikidata talk:WikiProject Source MetaData#Conflict-of-interest metadata. I had previously written about COI metadata there, as it seemed the most relevant Wikiproject, but got no response, and as I obviously don't know what I'm doing, I was hesitant to do much unadvised. Least you are wondering why I am bothering you, en:Conflicts of interest in academic publishing has a photo of you discussing this unphotogenic topic, so I knew you took an interest in it. Thank you for your patience. HLHJ (talk) 19:36, 9 September 2018 (UTC)

Wikidata weekly summary #329

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #330

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Continuing through September and early October: Andy Mabbett is touring Australia for a series of open-science and GLAM Wiki-focused talks, workshops, and meetups.
    • New events added for the sixth birthday of Wikidata: Berlin, Oslo, Tehran, Beijing
  • Development
    • Fix a problem with the language of the lemma (phab:T194347)
    • Improving the diffs for Lexemes (phab:T185481)
    • Exclude es-formal and hu-formal from monolingual text codes (phab:T203311, thanks to MarcoAurelio)
    • Implement the contemporary constraint (phab:T141859, thanks to Abiàn)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #331

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Work on editing Form statements using the API (phab:T194732)
    • Show the Lemma(s) or Representation(s) when Lexemes or Forms are mentioned in constraint reports (phab:T195315)
    • Add hyphenation for long Lexeme lemmas and representations (phab:T195367)
    • Normalize SPARQL queries (phab:T204122, thanks to Abiàn)
    • Fix a bug on the Query Service about exported query results being different from the displayed result (phab:T195258)
    • Fix a bug on the Query Service about empty map results returning error (phab:T178786)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #332

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Fix a bug when the "language of Lemma" box doesn't appear after failed submit of Special:NewLexeme (phab:T194347)
    • Fix the order of elements in Lexeme edit diffs (phab:T185481)
    • Enable constraint checks for Lexemes and Forms (phab:T195828)
    • More work on editing Form Statements using API (phab:T194732)
    • More work on a beta feature for suggestions based on constraints (phab:T202712)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Suggestion for Research Bot

Latest comment: 5 years ago5 comments2 people in discussion

I have a suggestion regarding your bot when creating articles like Q38917924: is there a way for you to automatically include the Google Scholar paper ID (Property:P4028)? When you search for the article title on Google Scholar, it can be found in hidden in the "Cited by..." link: https://scholar.google.com/scholar?cites=1451297973973942230&as_sdt=5,50&sciodt=0,50&hl=en. Maybe you can think of a way to automatically extract it and include it during entry creation. --Bender235 (talk) 22:06, 3 October 2018 (UTC)

I can think of such ways, but Google does not welcome their implementation. --Daniel Mietchen (talk) 05:49, 4 October 2018 (UTC)
You mean when the scrapping is done at high frequency, or in general? If so, what shall we do about it? Google Scholar is certainly and popular and helpful tool. We should include this identifier (somehow) in my opinion. --Bender235 (talk) 14:21, 4 October 2018 (UTC)
They basically block anyone who tries to do such things at scale. --Daniel Mietchen (talk) 21:21, 4 October 2018 (UTC)
That's unfortunate. I posted a question on WikiProject Google about this. Maybe somebody is aware of a way to circumvent this. --Bender235 (talk) 13:53, 5 October 2018 (UTC)

Wikidata weekly summary #333

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

Other Noteworthy Stuff

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Unused researcher items

Latest comment: 5 years ago2 comments2 people in discussion

Any reason not to delete Q56960351 and Q56960986, which were part of one of your QS batches? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:34, 12 October 2018 (UTC)

No. Thanks for checking. --Daniel Mietchen (talk) 16:06, 13 October 2018 (UTC)

Karel Berka

Latest comment: 5 years ago9 comments2 people in discussion

Karel Berka (Q43370830) has an ORCID iD, so cannot be Karel Berka (Q884500), who died in 2004. I have demerged them. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:29, 13 October 2018 (UTC)

For a similar reason, I reverted you here. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:35, 13 October 2018 (UTC)
@Pigsonthewing: Thanks for checking, in both cases. --Daniel Mietchen (talk) 16:07, 13 October 2018 (UTC)
And again, twice more, on Q884500. Please can you find a way to exclude it from whatever is triggering these edits? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:37, 18 October 2018 (UTC)
These are ORCIDator batches that I started weeks ago, so cannot change them now. The problem seems to be that some papers have been assigned to the wrong person here, and the tool then associates the Wikidata entry for the author with the ORCID where the DOI of the paper is listed. So about some 70 paper items need to be cleaned regarding authorship — I put this on my to do list. --Daniel Mietchen (talk) 20:01, 19 October 2018 (UTC)
I have now fixed the authorship for all 77 papers currenttly indexed in Wikidata. --Daniel Mietchen (talk) 23:51, 20 October 2018 (UTC)

There's a similar issue on Alessandro Zorzi (Q2832828). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:40, 8 November 2018 (UTC)

And again on Q2832828. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:12, 13 November 2018 (UTC)
This seems to stem from multiple papers having been linked to this person: Special:WhatLinksHere/Q2832828. On that basis, ORCIDator then infers that this person must be the one on whose ORCID profile the papers were listed. The P50 statements on the papers need to be fixed. --Daniel Mietchen (talk) 19:44, 13 November 2018 (UTC)

Wikidata weekly summary #334

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #335

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • A Wikidata workshop will be led by Shani Evenstein, in collaboration with Wikimedia Israel & and the Israel Internet Association, on 18th & 25th of October in Tel Aviv. The first meeting will be dedicated to an introduction and adding information to WD, and the second meeting will focus on querying & SPARQL.
    • An Introduction to Wikidata by Harmonia Amanda, an Introduction to Wikibase by Sandra Müllrick and a Wikicite workshop by Miriam Redi at the Wiki Techstorm in the Dutch National Library in the Hague on the 26th & 27th of October
    • Many events to celebrate Wikidata's birthday around the world. You can check the full list and the map to find one near you

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #336

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Several developers and members of the team attended to the Wikimedia Technical Conference
    • Fix an issue with interwikilinks and connection between Wikidata and sister projects (phab:T208077, phab:T208124)
    • Refactor Wikibase so that it can use alternative termbox views (phab:T206863)
    • Pass the entity data on the client side (phab:T207462) and server side (phab:T207467)
    • Investigate an error on some Wikidata pages (phab:T208142)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #337

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Helped get MediaInfo deployed on Commons
    • Reduced load on the query service from the constraint checks (phabricator:T204469)
    • Worked on getting constraints checks run regularly in the background so their results are complete in the query service (phabricator:T204714)
    • Enabled access to arbitrary items and properties for Wiktionaries
    • Working on infrastructure parts of the new termbox (the one showing labels, descriptions and aliases) on mobile

How to note an author's correction

Latest comment: 5 years ago2 comments2 people in discussion

@Daniel Mietchen: Greetings. Can you tell me which property I should include in an item, e.g. a scholarly article, if there is a later published revision or change? I'm referring to those events not where the original is completely replaced, just where the author publishes an addendum. Thanks. I hope you dn't mind my adding this topic. I didn't see any others here, but thought it was the right place.

Example:

I think the question might be related to when a subsequent author replies to, comments on, another. Important as references should consider follow-ups to the original citation.

Thank you for any recommendation. -Trilotat (talk) 14:16, 8 November 2018 (UTC)

@Trilotat: Sounds close corrigendum / erratum (P2507) to me, though that does not capture all te possible nuances. If you're looking for properties, try the Property Browser. --Daniel Mietchen (talk) 13:44, 14 November 2018 (UTC)

Wikidata weekly summary #338

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Displaying Senses before Forms (phab:T208592)
    • Making quality constraints play nicer with the Query Service
    • Putting in the ground work to have quality checks run in jobs
    • Enabling arbritrary access on oldwikisource
    • Allowing configuration of the licence in .ttl output
    • Configuration of more string limits, such as URL and mono / multilingual texts
    • Moving wdqs frontend to a blubber deployment (phab:T192006)
    • Asserting a users name so they can't edit when accidently logged out (phab:T124451)
    • Showcase a termbox placeholder in the mobile frontend of m.wikidata.org (phab:T206200)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Creating Duplicate P50 in articles

Latest comment: 5 years ago3 comments2 people in discussion

@Daniel Mietchen: Hello again. It seems I have added authors to articles that already exist. Some other info, in case it's helpful for the forensics: it's happening as a result of a stalled batch, 2627; it's creating them without "stated as" and "series ordinal" qualifiers; it appears that batch is running at the same time you created the article. I started to remove them, so there wouldn't be two authors, but now I'm trying to figure out WHY it happened so I avoid it. Deleting these duplicate authors is no fun; is there a bot that removes duplicate authors (and less informative, i.e. no stated as, no series ordinal) from articles? This is the article where I stopped deleting the duplicates without completion. Please let me know if I need to return to the effort. It has to be done, bot or not.

Thank you. -Trilotat (talk) 13:01, 14 November 2018 (UTC)

@Trilotat: Not sure what the problem is/ was, but what about pausing that stalled batch? My batch 82 that worked on the item is still ongoing. We currently don't have tools to fix superfluous author (P50) or missing object named as (P1932) statements, but I think we should have some in the long run. --Daniel Mietchen (talk) 13:48, 14 November 2018 (UTC)
@Daniel Mietchen: Yes; paused it as soon as I realized it was happening. I'll go through item that were completed in that batch to remove the superfluous authors. Thanks for reply. You appear to be very busy. I watched the video of you at 2017 wikicite event. Very informative and it motivated me to work on the geology and earth science articles and disambiguation of authors (moving from author name string (P2093) to author (P50)). -Trilotat (talk) 14:16, 14 November 2018 (UTC)

Problema with Source MD and Doi

Latest comment: 5 years ago2 comments2 people in discussion

Hello!I'm trying to import scientific articles from the journal Bibliothecae.it inserting the Doi on SourceMD, one per row,but all the attempts fail. What am I doing wrong? the doi should be inserted in full, starting from http: .... or starting from 10 ...?Thank you for your attention, Alessandra Boccone (talk) 23:09, 17 November 2018 (UTC)

@Alessandra Boccone: Starting with 10. You can test things using the old version, which has the same functionality in this regard (but not in others). --Daniel Mietchen (talk) 23:58, 17 November 2018 (UTC)

Wikidata weekly summary #339

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • A new tool to display Wikimedia Commons categories (and Wikipedia/Wikidata tags) with coordinates on the OSM map
    • The Association of Research Libraries published the draft of a Wikidata Task Force White Paper on how libraries and Wikidata/ Wikibase con join forces aroud linked open data for both library discovery systems and Wikipedia, and advancing a diversity and inclusion agenda in the cultures of both libraries and Wikimedia. The draft is open for public comment until 30 November.
  • Development
    • Fixed a bug that was saving the statement too early when trying to add a qualifier with the keyboard (phab:T154869)
    • Made changes to disallow edits (until the user reloads) if they accidentally get logged out. (phab:T124451)
    • Turn the new change tag back on wikidatawiki (phab:T208846)
    • Better linting against things that don't work in IE11
    • Fixed the wdqs-frontend docker image (phab:T208681, phab:T209206)
    • Fixed html elements in the table result of wdqs (phab:T207257, thanks to user:Frog23)
    • Getting ontology changes deployed to wikiba.se
    • Using maplink or mapframe to view coords on wikidata (phab:T184933)
    • Consistent capitalization of Lexeme/Form/Sense/Item/Property in UI messages
    • Make Lexemes appear in global usage of Commons files (phab:T204066)
    • Work on a new interface for the termbox on mobile (phab:T207150)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #340

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Fix an error when entering an incomplete filename (phab:T199420)
    • Fix the unreadable references for unpriviledged users (phab:T186006)
    • Create new page properties for number of Forms and Senses of a Lexeme (phab:T199611)
    • Adapt the API to efficiently format large numbers of entity IDs (phab:T207484)
    • Switch "save" to "publish" in the Lexeme interface (phab:T203354)
    • Fix a bug showing outdated link formats in the history of Lexemes (phab:T208423)
    • Add Special:MergeLexemes to Special:SpecialPages (phab:T204397)
    • Add Wikipedia link in the other projects sidebar of Wikisource (phab:T180303, thanks to Tpt)
    • Work on displaying the language of the gloss with the language name, both in reading and editing mode (phab:T203457, phab:T209931)
    • More work on improving the interface of the termbox on mobile

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #341

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: "Researcher meets Curator", with a subquestion: "What are the consequences of collecting born digital sources, working with digital network analysis and engaging with linked open data initiatives such as Wikidata", in Maastricht on 22 March 2019. Call for papers
    • Upcoming: Advanced Wikidata Training in India, December 15-16
    • Past: "Wikibase: configure, customize, and collaborate" workshop at SWIB 18 in Bonn, Germany on November 26, 2018. Workshop materials
    • Past: EveryPolitician event to identify political data sources for Wikidata in Madrid, Spain, on December 1, 2018.
  • Development
    • Add Lexeme to Wikibase's ontology.owl (phab:T195368)
    • Prepare to drop change_tag.ct_tag column (phab:T194163)
    • Create Federated Wikibase instance on Beta Commons (phab:T204748)
    • More work on preparing a new termbox for the mobile version of Wikidata

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Your sourcemd batches

Latest comment: 5 years ago3 comments2 people in discussion

Hi Daniel,

Just making sure you are aware of this discussion: Wikidata_talk:WikiProject_Source_MetaData#Questions_about_"scholarly_articles". As you are still running various publication imports, it would be great if you could chime in there.

All the best − Pintoch (talk) 00:03, 7 December 2018 (UTC)

@Daniel Mietchen: did you see this? − Pintoch (talk) 05:30, 17 December 2018 (UTC)
@Pintoch: Yes, but not sure what to say there. My focus is not on imports these days but on cross-linking papers with authors and topics. --Daniel Mietchen (talk) 23:39, 21 December 2018 (UTC)

Wikidata weekly summary #342

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • We are now showing the language name instead of the language code of a Gloss (phabricator:T203457, phabricator:T209931)
    • We added a Page property for easier programmatic access to the number of Senses and Forms of a Lexeme (phabricator:T199611)
    • The code samples in the query service have been improved (phabricator:T207749, thanks abian!)
    • We're working on tracking how often the different Lua functions that Wikibase provides are used in the Wikimedia project to see how that changes over time (phabricator:T191416)
    • We worked on and fixed a security incident related to blocking (phabricator:T210953)
    • We are continuing to bring the termbox (showing labels, descriptions, aliases) to mobile viewers

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #343

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
  • Test that the issue with blocked users will not happen anymore (phab:T211120)
  • Finish up on showing Language and Language codes when editing glosses (phab:T209931)
  • Work towards having QualityContraints on Beta (phab:T209957)
  • Work on tracking usage of Wikibase Lua Functions (phab:T191416)
  • Some more work on string length limits (phab:T154660)
  • Work on some Wikidata toolkit improvements (phab:T209399)
  • Fix some errors happening in production (phab:T208924)
  • More under-the-hood work for the termbox on mobile

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wissenschaftliche Artikel finden

Latest comment: 5 years ago2 comments2 people in discussion

Hallo Daniel,

ich ergänze in letzter Zeit deutsche Beschreibungen zu Datenobjekten und nebenbei beschäftige ich mich mit Wegen Außenstehenden einen einfachen Zugang zu Wikidata zu geben. Inzwischen gibt es in Wikidata viele Datenobjekte über wissenschaftliche Artikel. Solche Artikel sind sehr interessant, jedoch sucht man nach einem Thema normalerweise mit Schlagworten und mir fällt es schwer einen bestimmten Artikel in Wikidata zu finden. Gibt es konkrete Überlegungen, wie man die Suche nach wissenschaftlichen Artikeln verbessern kann. Ich würde es schön finden, wenn man nach einem Schlagwort suchen kann und dann einem alle Artikel mit diesem Schlagwort angezeigt werden. Ich selbst kann nicht programmieren, nutze jedoch viel den Queryservice und denke, dass man für den Anfang mit Abfragen vom Query-Service gut arbeiten kann. Mein Vorschlag ist nun hier in Wikidata eine Seite zu erstellen, die hilft einen Überblick über wissenschaftliche Artikel zu bekommen mit Erklärungen, was diese Artikel beinhalten und Abfragen zu verlinken mit denen man sich spezielle Artikel, beispielsweise die in einem bestimmten wissenschaftlichen Verlag veröffentlicht wurden anzeigen lassen kann. Bitte teile mir mit, was du dazu denkst und ob es schon Versuche in die Richtung gibt, ich würde gerne etwas in diesem Bereich machen. In einem Tabellenkalkulationsprogramm sollte es möglich sein, die Abfragen schnell mithilfe der Verkettenfunktion anzupassen und so auf einmal alle benötigten Abfragen einer bestimmten Struktur zu erstellen. Also wenn man nach einem wissenschaftlichen Artikel, der ein bestimmtes Schlagwort enthält sucht, dann kann wenn man die Q-Nummern der Schlagworte weiß, diesen Bereich jeweils abändern und man hat schnell die Abfragen als Link. -- Hogü-456 (talk) 20:54, 21 December 2018 (UTC)

@Hogü-456: Hast du dir Scholia dazu mal angeguckt? Es zeigt z.B. via https://www.wikidata.org/wiki/Q202864 Informationen rund um Publikationen zum Thema Zika virus (Q202864), und unter https://tools.wmflabs.org/scholia/topic/Q202864/missing gibt's dann Hinweise dazu, wo Kurationsbedarf besteht, z.B. auch hinsichtlich der Verschlagwortung. Um die entsprechenden Daten in Wikidata einzubringen, nutze ich Abfragen wie diese hier. --Daniel Mietchen (talk) 23:36, 21 December 2018 (UTC)

Possible to delete stopped SourceMD batch?

Latest comment: 5 years ago1 comment1 person in discussion

Hello. I don't know if this is an issue I should be concerned with. I've accumulated quite a list of "stopped queries" using SourceMD. I don't intend to restart them. Can I delete or hide them in my batch history? If not, can I sort my batch history so I see the running and recently completed ones on the top of the list? Thank you. Trilotat (talk) 15:51, 22 December 2018 (UTC)

Source Meta: Add authors to publication?

Latest comment: 5 years ago1 comment1 person in discussion

Happy holidays. What is the purpose or use for this tool? I haven't been successful in my efforts to apply the tool. Can you point me to instructions or explain briefly here? Thanks. Trilotat (talk) 00:19, 26 December 2018 (UTC)

Wikidata weekly summary #344

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Writing a maintenance script to make configuring WikibaseQualityConstraints easier (phab:T209958)
    • Working on new ID generator using different SQL to attempt to stop lock errors when creating lots of items (phab:T194299)
    • Making more parts of the Query Service UI more configurable such as the copyright page, title, and started work on the favicon / logos (phab:T194175)
    • Adding tracking for Wikibase Lua functions so we can see how they are used on various different projects (phab:T191416)
    • Working on fixing alignment issues with glosses (phab:T207401)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #345

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Not much happened this week because we took some time off over the holidays. Getting back to full speed again in the next days.

Wikidata weekly summary #346

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Working on getting final pieces in place to regularly run constraint check jobs so all constraint violations get fed into the query service (phabricator:T204031)
    • Fixed alignment issues with Glosses on Lexeme pages (phabricator:T207401)
    • Working on getting the layout right for the termbox in the mobile view so that in the future you can also see labels, descriptions and aliases in different languages on mobile (phabricator:T207150)
    • Getting ready to start working on basic Shape Expression support

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #347

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Structured data for Commons: multilingual captions are deployed on Commons on January 10th (documentation)
    • The Wikidata Query Service has been encountering some data corruption issues that impact the results you can see when running a query. Some may still be running. You can check the current ticket for more updates.
    • New dashboard for percentage of pages on a Wikimedia project make use of data from Wikidata (doesn't include sitelinks, doesn't include Commons file and category pages for now)
    • Science Stories, a project highlighting women in sciences, uses Wikidata
  • Development
    • Solving an issue that blocked deployments over the past weeks (phab:T212427)
    • Improved the visual appearance of glosses (phab:T207401)
    • Fixing problems with reverting Sense addition (phab:T211438)
    • Improving our Javascript to be more standard (phab:T210744)
    • Working on performing more constraint type checks in PHP before falling back to SPARQL (phab:T209504)
    • Making the query service logo and favicon configurable in one's own Wikibase (phab:T212210)
    • More work on displaying the termbox on mobile (phab:T207150)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Duplicate DOI's

Latest comment: 5 years ago2 comments2 people in discussion

Hi Daniel - I was experimenting with some author disambiguation work, and ran across Hierarchical Decentralized Network Reconfiguration for Smart Distribution Systems—Part I: Problem Formulation and Algorithm Development (Q57978745) and Hierarchical Decentralized Network Reconfiguration for Smart Distribution Systems—Part I: Problem Formulation and Algorithm Development (Q57978728) - and a number of other pairs that looked very similar, added by you via Quickstatements. They have identical DOI's (as indicated by the constraint violation shown on the DOI!) and if you look at the "unique value" constraint violations for DOI's you'll see there are over 30,000 of them... I merged a few but it's a pretty major task, any idea what happened, and how best to fix it? ArthurPSmith (talk) 17:06, 15 January 2019 (UTC)

Thanks for checking — I have an eye on this and am doing regular cleanups. For details, see this ticket. --Daniel Mietchen (talk) 20:21, 21 January 2019 (UTC)

Item 53 above is a heading, rather than a bullet

Latest comment: 5 years ago2 comments2 people in discussion

@Daniel Mietchen: In item 53 in your table of contents (TOC) above, the "other noteworthy stuff" is a heading whereas ever other "other noteworthy stuff" is a bullet. I guess I'm a bit obsessive as I notice that change in your TOC each time I visit. I'd be happy to adjust it with your permission.   Trilotat (talk) 23:38, 19 January 2019 (UTC)

Kinda fixed — thanks. Was a problem in the newsletter, so is probably present on many other pages. --Daniel Mietchen (talk) 20:21, 21 January 2019 (UTC)

PubMed imports

Latest comment: 5 years ago2 comments2 people in discussion

Hi Daniel,

I left a notice on Research Bot's page under Problematic Items, but perhaps you haven't seen it. The Research Bot is busy importing some *very* dirty data from PubMed. There are numerous issues with importing their metadata into Wikidata, as it is provided by publishers. They do not use an authority file and very few authors have ORCID-Ids. Thus there are many different spellings of author names. Predatory publishers are also mis-using the pre-print format to publish their work, making it appear to be legitimate publication. Most problematic is that you are NOT registerin when a retraction notice has been published about an article and flagging the retraction notice as such.

One example is https://www.wikidata.org/wiki/Q43219180, which is a retraction notice. I put the property in by hand, as this is one of the glaring mistakes in PubMed: I informed the publisher about the problem, they entered my name as the author (!) in the metadata and I have been unable to get this fixed! You really need to deal with at least these problems, there are many others. --WiseWoman (talk) 10:03, 21 January 2019 (UTC)

@WiseWoman: Thanks for your note, and sorry I had not noticed your edit on the bot's user page. Yes, some of the imported data is quite dirty — cleanup happens in various ways but is far from complete. Yes, way too few authors have ORCIDs, and of those who do, way too few have content in their profile, and of those who do, way too few make their profile public. However, if there is useful public content in an ORCID profile, we often make use of it (e.g. see WD:SourceMD). Yes, there are lots of ways in which authorship by the same person is indicated, and we have tools like the Author Disambiguator, Scholia's missing pages (which exist for authors and some other aspects, e.g. topic) or dedicated Listeria pages (example) that are beginning to address the issue. Yes, retractions need to be signaled properly — WikiProject Retractions is working on this but there is a long way to go still, and we don't have clean data to start with. No, this bot is not currently busy, but similar imports are ongoing. Yes, we don't have a good handle on preprints at the moment, but I don't think predatory publishers are much of a problem here yet. --Daniel Mietchen (talk) 20:31, 21 January 2019 (UTC)

Wikidata weekly summary #348

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Fixed a small bug that we introduced with editing badges on wd.org (phab:T213998)
    • Finished collecting data about the user of the termbox (phab:T211015)
    • Fixed an i18n message (phab:T206416)
    • Created some maintenance scripts for creating and approving oauth consumers (phab:T211568)
    • Checked for possible data coruptions due to an issue with change tags (phab:T213281)
    • Fixed an issue with restoring merge revisions in Lexeme (phab:T204041)
    • Configured WikibaseQualityConstraints on test.wikidata (phab:T209922)
    • Turned on the new entity id formatting for properties (phab:T201838)
    • Continued work on glosses, displaying the language name also in edit mode (phab:T209931)
    • Starting investigating on Shape Expressions
    • Mobile termbox: showing language, description and aliases (phab:T207150)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


inferred from (P3452)=title (Q783521)

Latest comment: 5 years ago2 comments2 people in discussion
  1. This should be used as references, not qualifiers.
  2. The property you used is incorrect - should be based on heuristic (P887) instead.

--GZWDer (talk) 21:45, 21 January 2019 (UTC)

@GZWDer: Thanks — will look into it. --Daniel Mietchen (talk) 00:48, 22 January 2019 (UTC)

Wikidata weekly summary #349

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Started development on Shape Expressions
    • Termbox: show an expanded-by-default section for the user's preferred languages (phab:T211865)
    • Provide visualization LUA usage on a dashboard (phab:T211768)
    • Fixed issues with sense ID wrapping (phab:T210502)
    • Background work to support the deployment of the next pieces for Structured Data on Commons

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #350

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

Import of links

Latest comment: 5 years ago3 comments3 people in discussion

Hi Daniel, this item Barriers to Accessing HIV Testing Services - A Systematic Literature Review (Q57462812) was created without a title and with no description. A ghost item. --Kolja21 (talk) 15:02, 9 February 2019 (UTC)

  Fixed I followed the PubMed ID link and added the English title. Perhaps it has a German title? I don't know. Trilotat (talk) 15:13, 9 February 2019 (UTC)
@Kolja21, Trilotat: Thanks both. PubMed does not treat non-English titles very well, and one side effect is that there are many of such ghosts here. Thankfully, this can be — and sometimes actually is — fixed. --Daniel Mietchen (talk) 19:53, 9 February 2019 (UTC)

Wikidata weekly summary #351

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Working on the "in more languages" and "all entered languages" parts of the termbox on mobile
    • Working on making undo, revert, edit summaries and more work for Shape Expressions
    • Fixed an error when detecting the same label and description in another Item (phabricator:T194770, thanks Matěj)
    • Making Lemma input on Lexeme pages save your input when you press enter (phabricator:T206140)
    • Making QuickStatements work more easily for other Docker-powered Wikibase instances (phabricator:T205606)
    • Worked more on making Federation work for making Statements on Wikimedia Commons (phabricator:T214557)
    • Working on stripping whitespaces at the beginning and end of Glosses when saving them (phabricator:T212019)
    • Looking into adding more signals to ORES' vandalism detection model so we can detect bad edits more accurately (phabricator:T194737)
    • Preventing a redirect of an Entity onto itself (phabricator:T214775)
    • Fixed an issue with adding sitelinks from Wikimedia Commons (phabricator:T213975)
    • Unified the separators between language and lexical category in different places (phabricator:T201808)

Wikidata weekly summary #352

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Erroneous title of scientific article with mathematical symbol

Latest comment: 5 years ago2 comments2 people in discussion

Hi Daniel, I corrected several scientific article title (1, 2, 3 for now). There are probably much more cases. The shared trait between these 3 titles is they contain mathematical symbol (LateX or MathText) in their title (  and so on). Do you have a way to find all the articles you imported and that may suffer of this problem? Pamputt (talk) 19:00, 18 February 2019 (UTC)

Thanks for checking, Pamputt! Yes, we have quite a few cases where formatting in the title is garbled. No, I don't have a way to find all of them, though I have been looking into subsets, e.g. for HTML (&amp, &lt etc.), other markup (e.g. <), brackets or even "Formula: see text". Similar issues affect chemicals and taxonomic names too. I have done a bit of cleanup here and there but don't have a good idea on how to do this at scale. --Daniel Mietchen (talk) 18:36, 19 February 2019 (UTC)

Wikidata weekly summary #353

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Updated some icons with the new WikimediaUI icon set (phab:T209259)
    • Fixed an issue that was causing occasional failures when creating new Items (phab:T194299)
    • Investigated Wikidata Tours not loading correctly (phab:T215919)
    • Adjusted spacing between Sense ID, bar and Gloss (phab:T215502)
    • Fixing a long time issue with introducing new data types in production (phab:T216728)
    • Fixing docs for backup of wikibase container images (phab:T214941)
    • Making undo, rollback and restore work on schema content pages (phab:T214399)
    • Improving edit summaries for schema content pages (phab:T213724)
    • Tightening up the process for editing "identifying information" for Schemas (phab:T214466)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #354

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Added monolingual language code tlb (Tobelo), thanks User:Mbch331! (T216798, will be deployed next week)
    • Integrating the termbox with Wikibase (phab:T214679)
    • Viewing historic revisions and fetching the termbox data from Special:EntityData (phab:T210615)
    • Fixing emoji breaking the termbox (phab:T217244)
    • Renamed special pages under Wikibase to avoid confusion with Schemas special pages (phab:T216719)
    • Removed unsupported php 7 constant in production, causing a notice and potential undefined behavior ([[phab:T217241
    • Investigated wb_term normalization solution (phab:T215902)
    • Fix for outdated cached WB datatypes on client-side (phab:T216728 (blocks enabling new datatypes, e.g. phab:T216730))
    • Allowing access to wikibase entities from multiple (wikibase) databases (phab:T214557)
    • Allowing to return a proper API error on 'wbformatvalue' action (phab:T207479)
    • Providing open-graph title and discretion meta-tags for lexemes (phab:T206414)
    • Allowing quickstatements to work out-of-the-box in wikibase-quickstatments docker image (phab:T205606)
    • Implementing “undo” for Schemass (phab:T214914, making it work via the API (phab:T217250)
    • Implementing “restore” for Schemas (phab:T214915)
    • Adding created and edited Schemas to the watchlist according to the user’s preferences (phab:T213725)
    • Splitting edit parts on Schemas (phab:T215395, phab:T215393, phab:T215392, phab:T215394)
    • Improving support for multilingual edit comments in MediaWiki (phab:T215637)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Angewandte Chemie ingest problems

Latest comment: 5 years ago3 comments3 people in discussion

Hi Daniel,

There are some data quality issues with Angewandte Chemie articles. In general, papers published in Angewandte Chemie (Q538683) and Angewandte Chemie. International edition in English (Q29043732) are being conflated during SourceMD batch processing. This query is articles published in Angewandte Chemie but if you look at the results, the DOIs starting with 10.1002/ANIE should be published in Angewandte Chemie. International edition in English (Q29043732).

Another problem is duplicates being created with incorrect DOIs for the older articles. For example, your batches appear to have created A New Phase-Switch Method for Application in Organic Synthesis Programs Employing Immobilization through Metal-Chelated Tagging (Q56953042), A New Phase-Switch Method for Application in Organic Synthesis Programs Employing Immobilization through Metal-Chelated Tagging (Q57337870), A New Phase-Switch Method for Application in Organic Synthesis Programs Employing Immobilization through Metal-Chelated Tagging (Q58373467), A New Phase-Switch Method for Application in Organic Synthesis Programs Employing Immobilization through Metal-Chelated Tagging (Q59101398), A New Phase-Switch Method for Application in Organic Synthesis Programs Employing Immobilization through Metal-Chelated Tagging (Q60216393), and A New Phase-Switch Method for Application in Organic Synthesis Programs Employing Immobilization through Metal-Chelated Tagging (Q60324889) with the doi 10.1002/1521-3773(20010316)40:6 3.0.CO;2-D, which does not resolve - the correct doi is 10.1002/1521-3773(20010316)40:6<1053::AID-ANIE10530>3.0.CO;2-D. Presumably, this is a problem with parsing the unusual doi format. I've previously merged a number of duplicates with similar DOIs that I've unknowing created but I don't know what needs to happen to stop this from happening. Simon Cobb (User:Sic19 ; talk page) 16:01, 9 March 2019 (UTC)

Geology (Q5535339) journal does the same thing. SourceMD deletes the data between the less than and greater than symbols when it creates the articles from the DOI. When you or someone else attempt that same article, SourceMD won't filter it as a duplicate since the correct DOI isn't present. It's frustrating, to be sure. Trilotat (talk) 21:32, 9 March 2019 (UTC)
Thanks both. Can't look into this right now but have stopped my SourceMD batches. --Daniel Mietchen (talk) 02:52, 10 March 2019 (UTC)

Wikidata weekly summary #355

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Dimon2711
    • Closed request for adminship: Esteban16, welcome onboard!
  • Other Noteworthy Stuff
    • Client wikis calling geocoordinate statements from Wikidata using mw.wikibase.entity:formatStatements or the #statements parser function will now have it displayed using a Kartographer <maplink> if available. In case of bug or question, feel free to ask in phab:T210926. Thanks to Tpt for the change!
    • A Google Summer of Code/Outreachy project seeks to add structure to the Commons app. Photographers will be able to pick Wikidata items that are depicted by the picture they upload.
    • Suggestions based on constraints can be enabled for all users

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.



Wikidata weekly summary #356

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Prepare new constraint icons (phab:T191322)
    • View history revisions of entities on new termbox mobile (phab:T210615)
    • Caching termbox output on the Wikibase side (phab:T214679)
    • Fix emojis breaking the termbox layout in Chrome (phab:T217244)
    • Work on multilingual support for schemas (phab:T215387)
    • Implement a length limit for the schema text (phab:T216148)
    • Replace the heading/title for schema pages similar to what Wikibase does (phab:T215759)
    • Deploy the shex-simple website, which can be used to check entities against a schema in the browser, on Toolforge (phab:T217333)
    • Deploy the score data type to production

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Problems with SourceMD and AIP Conference Proceedings

Latest comment: 5 years ago4 comments2 people in discussion

Hi - I've been cleaning up a bunch of items for articles from AIP Conference Proceedings, where SourceMD seems to have imported a bunch of extra authors at the end of each article. Do you have any idea where this is coming from? Example is Investigation of [sup 246]Fm : in-beam spectroscopy at the limits (Q60542297) - it was imported with 3 extra authors at the end, not listed on the original article. Those same 3 authors have been appended to a lot of other author lists too; I'm working on cleaning those up. ArthurPSmith (talk) 15:32, 22 March 2019 (UTC)

@ArthurPSmith: I don't know for this specific case, but I have seen similar cases with other sources where authors had been confused with editors of the work in question. --Daniel Mietchen (talk) 17:29, 22 March 2019 (UTC)
That's a possible explanation. Where does SourceMD get author lists from? A problem in the original source somewhere? ArthurPSmith (talk) 18:05, 22 March 2019 (UTC)
Depends. In this case probably Crossref. --Daniel Mietchen (talk) 21:09, 22 March 2019 (UTC)

Wikidata weekly summary #357

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Stanglavine
    • An open discussion on how to model one-way train routes is now taking place, and everyone is welcome to pitch in
  • Development
    • Update property suggester data (phab:T216270)
    • Add a link to the shex-simple tool to make it easier to check entities against a Schema (phab:T217331)
    • Make the placeholders on Special:NewSchema now match the ones on Special:NewItem (phab:T215386)
    • Check for edit conflicts when editing schemas (phab:T217338, phab:T218300)
    • Enable the parser cache for Schema pages (phab:T218459, phab:T218769)
    • Use the FormatAutocomments hook for Schemas to implement translatable edit summaries (phab:T218889)
    • Implement a proper Wikibase-Termbox-Integration according to the ADR (phab:T214679)
    • Fix the emoji breaking the termbox column layout (phab:T217244)
    • Correctly showing revisions with the new termbox (phab:T210615)
    • Correctly handle user-specific language settings in the new termbox (phab:T218111)
    • Fix an issue for score extension (phab:T218535)
    • Turn off RDF support for entity types that doesn't support it (phab:T213483)
    • Respect nofollow config on wikidata identifier links (phab:T175230)
    • Allow accessing Wikibase entities from multiple (Wikibase) databases (phab:T214557)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


ASGE Technology Committee (Q62515530)

Latest comment: 5 years ago1 comment1 person in discussion

is not a human. 129.13.72.197 11:53, 29 March 2019 (UTC)

Author name string => Author

Latest comment: 5 years ago6 comments3 people in discussion

Hi, most of the imported scientific studies still have authors listed by using author name string (P2093), while the prefered solutions would be to use author (P50). Converting this manually would take a lot of time, then I'm wondering if there could be anything to do to make this process more (semi-)automated. Before diving into this I would ask you if you know if this has already been discussed or if anyone is working on this case. --Cavernia (talk) 12:12, 29 March 2019 (UTC)

@Cavernia: See Author Disambiguator tool at https://tools.wmflabs.org/author-disambiguator/?name= Trilotat (talk) 19:43, 29 March 2019 (UTC)
@Trilotat: Nice tool to help with the part of the process that must be done manually to connect the text strings in author name string (P2093) to the correct elements of the authors. What I desire is a tool that could pick the names from author name string (P2093) - qualifiers and references included, create author (P50) entries and then delete the author name string (P2093) entries. I've tried to do this by pasting the information into an Excel sheet which generates code to import the data using the QuickStatements tool, but this doesn't allow references to be included. --Cavernia (talk) 11:05, 1 April 2019 (UTC)
It is not possible for a tool to relate an author name string automatically to an author. So what you want will probalby not work. 129.13.72.197 11:58, 3 April 2019 (UTC)
That's correct, it can't be automatically done. Example: In The science and policy of identifying and controlling industrial cancer hazards (Q45169961) the text string «Devra Lee Davis» is used as author name string (P2093). I know that this author matches Devra Davis (Q5267942), then it takes me between 1 and 2 minutes to add Devra Davis (Q5267942) to author (P50), then use qualifiers to add «1» as series ordinal (P1545) and «Devra Lee Davis» as object named as (P1932), add a reference by cutting and pasting Europe PubMed Central (Q5412157) into stated in (P248), «7313616» into PubMed ID (P698), and a date into retrieved (P813), and delete the entry in author name string (P2093). Some studies have 10 or 20 different authors, then it will take a lot of time to do this manually. The tool must then have a matrix which converts the text strings into entries, and this matrix must be made manually. One possible problem is that authors with common surnames will use the same name string, i.e. «Davis D» for both Daniel Davis (Q49962435) and Devra Davis (Q5267942). But maybe there is any alternative way of identification in the source from which the data was imported? --Cavernia (talk) 16:04, 10 April 2019 (UTC)
The disambiguator tool I mentioned above automatically copies all the qualifiers from author name string to author. You need only designate which articles should go through the process. I find "grouping by co-authors" (option at top of the tool's screen) to be useful since there's a higher probability that the author whose name (or initials) appears with the same co-authors is indeed the same. It's a great tool.Trilotat (talk) 19:36, 10 April 2019 (UTC)

Wikidata weekly summary #358

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Work on a dashboard for external identifiers (phab:T204440)
    • Add baserevid to WikibaseLexeme API modules (phab:T217243)
    • Add tests for embed.html (phab:T212649)
    • Improve features for wikibase vandalism detection model (phab:T194737)
    • Improve Property Info cache performance (phab:T218115, phab:T218197)
    • Adding nofollow to external identifiers links (phab:T175230)
    • Hide query helper by default in Query Service (phab:T217886)
    • More work on wb_terms normalization (Phab board)
    • Enable trimming whitespace around Label/Description/Aliases and Schema text (phab:T215761)
    • Prevent moving Schemas between namespaces (and generally) (phab:T219313)
    • Limit the length of Schema labels, descriptions, aliases, and schema text in the frontend (phab:T218867)
    • Add tracking for clicks on the “check entities against this Schema” link (phab:T218899)
    • Disallow importing of Schemas from another wiki or XML files to avoid ID conflicts (phab:T218181)
    • Make sure RTL text is being handled correctly in the Schema labels, descriptions and aliases table (phab:T219136)
    • Add a publish button on mobile termbox: (phab:T218573)
    • Building the wbeditentity request to be fired on save request: (phab:T218577)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


More duplicates

Latest comment: 5 years ago5 comments4 people in discussion

Hi Daniel - I just merged a bunch of scholarly articles with duplicate DOI's that you recently created via Quickstatements - one example is Q62592691 which was a duplicate of Optical conductivity from cluster dynamical mean-field theory: Formalism and application to high-temperature superconductors (Q62592690) but there were many more (Q62499965, Q62592704, Q62592695, Q62592698, ...) I just happened across those due to a common author name string; I suspect you may have accidentally created others. Can you double-check on this, and preferably check the process you're using to generate these files so we don't get so many duplicates? Is this another SourceMD problem? ArthurPSmith (talk) 14:44, 5 April 2019 (UTC)

Thanks for checking. Yes, this is again the problem that SourceMD relies on SPARQL queries for duplicate detection, which yields inconsistent and/ or outdated results when there are server lags, as was the case during that period. The relevant batch was 6608, which I have stopped, since the lags are ongoing. I am regularly cleaning up subsets of duplicates but we still have way too many. --Daniel Mietchen (talk) 02:33, 6 April 2019 (UTC)
Hi Daniel. I think it would be reasonable that both you and GerardM stop using sourcemd. As you seem to have his confidence, can you ask him to stop? I think we have spent enough time discussing this. Unless someone has a particular medical condition that requires the daily use of sourcemd for their survival, I see no basis for continued use of this tool. I would be very happy if we could avoid blocking anyone for this. Many thanks for your kind cooperation! − Pintoch (talk) 17:45, 7 April 2019 (UTC)
I don't think giving up the use of the tool entirely is the way to go here. For instance, we do not have another scalable way to update the Zika corpus (or any other, for that matter) with new publications. Most of the problems stem from the part that used to be the ORCIDator. I am happy to give that one a pause for a while. --Daniel Mietchen (talk) 14:22, 8 April 2019 (UTC)
Pintoch, you have been talking at me, you have not been talking with me. Your notions of quality are easy to discuss. Yes, duplicates are created and this is to be avoided. I have demonstrated my involvement by changing my MO. However there is no understanding and acknowledgement of what IS the problem. What I have experienced is personal vilification. In my opinion you fail to appreciate the relevance of Wikicite. It becomes impossible without tools like SourceMD. But you did not think about that I hope. Thanks, GerardM (talk) 16:09, 8 April 2019 (UTC)

Wikidata weekly summary #359

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • More work on documenting and preparing the announcement for the Wikidata External Landscape dashboard (phab:T204440)
    • Improved the documentation of WMDE analytic documents (phab:T219844)
    • Set up translatable schema edit summaries using the FormatAutocomments hook (phab:T218893)
    • Improved right-to-left support on schema pages (phab:T219298)
    • Protected schemas against imports (phab:T218181) and page moves (phab:T219313) and disabled the useless “move” and “create” protections for them (phab:T219980)
    • Improved schema edit conflict detection to allow merging of non-conflicting edits (phab:T218300, phab:T219173)
    • Improved the Extension:WikibaseSchema documentation on mediawiki.org (phab:T219979)
    • Fixed a bug on Lexicographical Data when editing existing grammatical features (phab:T219318)
    • Increased musical notation datatype string length limit to 1500 characters (phab:T218767)
    • Got ready for the last steps of new constraint level for suggestions (phab:T204439)
    • More work on allowing editing of mobile termbox fields (phab:T216987)
    • Let term value fields grow with their content (phab:T220185)
    • More work on migrating away from wb_terms

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #360

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Added Sámi monolingual language codes sia (Akkala), sjk (Kemi) and sjt (Ter), thanks to Jon Harald Søby (phab:T217521)
    • Moving forward with enabling constraints suggestions for everyone and remove beta feature (phab:T220609)
    • Fixing an issue with displaying mapframes for geocoordinate on client (phab:T220122)
    • Make it impossible to set the same content in the same language for label and description (phab:T212869)
    • Catch Exceptions where the entity can not be serialized due to being too big (phab:T217741)
    • Fix the order of value suggestions based on constraint (phab:T220587)
    • Add links on entity suggestions from constraint definitions (phab:T207363)
    • Increase musical notation datatype string length limit to 1500 characters (phab:T218767)
    • More work on making the new mobile termbox editable (phab:T216987)
    • More work on migrating away from wb_terms

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #361

Latest comment: 5 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Improved the external identifiers landscape (phab:T204440)
    • Prepare process and announcement for the wb_terms migration to come
    • Allow configuring WDQS UI without changes to files under version control (phab:T194179)
    • Configure suggestion constraint level on Beta (phab:T221107)
    • Graduate suggestions based on constraints beta feature out of beta features (phab:T209879)
    • Editing of labels and descriptions on mobile (phab:T216987)
    • Editing aliases on mobile (phab:T218690)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Editing speed

Latest comment: 4 years ago8 comments3 people in discussion

Hi Daniel,

WDQS is struggling a bit at the moment, and it seems that your batches could have a role in that, since the diff volume is relatively large. Could you please avoid running multiple QS batches in parallel?

Thank you! − Pintoch (talk) 13:02, 24 April 2019 (UTC)

There doesn't seem very much improvement yet, could you please take a look at this? Sjoerd de Bruin (talk) 13:40, 24 April 2019 (UTC)
Hi Daniel, it seems that you started three batches again shortly before noon UTC today, and this coincides with a new episode of WDQS lag increase.
Could you please stop running multiple QS batches in parallel? I realize that my previous message might be ambiguous: could you avoid to do this not just today, but also in the future?
The problem is that you are making edits to items that are relatively large, so the size of the updates is quite big (see https://wikidata.wikiscan.org/hours/24/users).
Thank you! − Pintoch (talk) 13:34, 25 April 2019 (UTC)
I have blocked your account to let WDQS recover. − Pintoch (talk) 14:18, 25 April 2019 (UTC)

@Pintoch, Sjoerddebruin: Just a brief ping that I am back. I note that the current lag is significantly larger than the one we had at the time of my block — did my inactivity during this period give you any insights into the precise mechanisms causing the lag, and my potential role in that? I did some test edits that did not seem to correlate with any of the lag fluctuations. Are you aware of anyone planning a WikiDataCon session on the technical limits to Wikidata? If not, maybe we could put one in together? --Daniel Mietchen (talk) 13:53, 27 April 2019 (UTC)

Yeah, it seems that Renamerr and Florentyna are also impacting big items at the moment, and that probably explains the current lag. When we blocked you, you were the only one with a "total size" of a few gigabytes on Wikiscan. I am not sure to attend WikidataCon but I would be happy to participate in the discussion if I come. − Pintoch (talk) 08:35, 28 April 2019 (UTC)

@Pintoch, Sjoerddebruin: I have done various additional tests — mostly when the lag was within 5 min and occasionally when it was larger but going down — but have not seen anything that would lead me to conclude that starting or stopping my batches is contributing anything significant to the total lag. For example, I have been running four QuickStatements batches in parallel for the last hour (and for some minutes even five), and the largest lag we had during that period was under 3 min. I have also had at least one batch running for most of April 30 and May 1, and the largest lag we had during that period was under 15 min. I understand that editing large items is a strain on the system in principle, and I welcome efforts to reduce that strain by only propagating affected triples rather than the entire page, but I think that type of strain is outweighed by other aspects, e.g. the number of client wikis actually making use of data from a given item. I hope that data from bibliographic items will be used more in the future, so I see conversations like this one as something that has to be kept in mind for such future contexts. For the moment, though, I plan to return to my pre-block habit of running up to three batches in parallel. I will keep an eye on the lag and try not to run my batches during periods when the lag is high. --Daniel Mietchen (talk) 21:51, 2 May 2019 (UTC)

Hi Daniel, thanks for doing these tests. Of course, WDQS lag is a function of the total activity on Wikidata, and the fact that other users also start and stop batches at the same time makes it hard to measure effects accurately. I do not think the dispatch lag is to blame here (WDQS updates and sister sites updates are distinct, non-competing processes), but there are definitely other factors to consider (such as SPARQL query rates). It is great that you will keep an eye on the lag. I also hope that you will also keep in mind the bigger picture: this particular episode is far from being the only obstacle to scaling Wikicite. I think it is really urgent to step back and think about what the project is really aiming for, and how to get there without disrupting Wikidata's infrastructure and community. − Pintoch (talk) 10:55, 3 May 2019 (UTC)

Wikidata weekly summary #362

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: BRPever
  • Development
    • Displaying mapframes for geocoordinate on client requires preprocessing by the user (phab:T220122)
    • Fixing cursor jumping to next field and overlapping of menus (phab:T172937)
    • Wikidata a focus issue on grammatical features field (phab:T218229)
    • Add language codes rm-rumgr, rm-sursilv, rm-surmiran, rm-sutsilv, rm-vallader, rm-puter for Lexemes (phab:T210293)
    • Align RTL languages in glosses to right (phab:T203081)
    • Add new monolingual codes: qya + sjn, el-cy, syc, abq, hbo) (phab:)
    • Fix a bug with NewLexeme suggester menu (phab:T199409)
    • Created a dedicated Phab board to help tool builders with the changes on wb_terms
    • More internal work to get the first version of mobile termbox ready for deployment

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #363

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: BRPever, welcome on board!

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Robert Bauer

Latest comment: 4 years ago4 comments2 people in discussion

Hi Daniel, there are many researchers called Robert Bauer but your Robert Guggenberger (Q42059709) is special, because in the only source given (ORCID 0000-0003-0970-9705) he calls himself "Robert Guggenberger". Has ORCID changed or do your bot has problems? --Kolja21 (talk) 02:06, 7 May 2019 (UTC)

PS: PubMed-ID 27474965 has a Robert Bauer with a link to ORCID Robert Guggenberger. This might be the problem. --Kolja21 (talk) 02:14, 7 May 2019 (UTC)
  OK Problem solved: "I married in 2017. Since then i am publishing as Robert Guggenberger."[3] --Kolja21 (talk) 21:14, 7 May 2019 (UTC)
Thanks, Kolja21, for noticing the issue, digging into it and solving it. Keep up the good work! --Daniel Mietchen (talk) 02:41, 9 May 2019 (UTC)

Wikidata weekly summary #364

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Finish renaming WikibaseSchema to EntitySchema
    • Investigate how to port Wikibase Selenium tests from Ruby to Node.js (phab:T221638)
    • Include a clear two step process in shex simple tool (phab:T221612)
    • Fix the "edit visually" on the Query Service interface (phab:T222181)
    • More work on wb_terms redesign (see documentation on phab:T221764)
    • More work on mobile termbox
    • Investigate on a bug found on wbeditentity not removing all aliases (phab:T203337)
    • Getting ready for the Wikimedia hackathon

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Contributor contact details

Latest comment: 4 years ago4 comments3 people in discussion

Hi Daniel, I just noticed you created and edited Contributor contact details (Q57897148)... there are a couple of these on Wikidata. If I were to delete these (because they are not actually relevant), would they be re-imported? Do we have a way to describe these properly (link the DOI somewhere else so that they don't get imported?). Cheers, Hoo man (talk) 22:45, 17 May 2019 (UTC)

I agree these seem a bit erratic because they are more like book chapters but have been shoehorned into our scholarly articles data model because they have a DOI. However, I think they are relevant because they provide detailed affiliation information for the people concerned, which could serve as a source for statements involving things like employer (P108) or affiliation (P1416). I have not run anything in the last month or so that would reimport something like this, but I cannot exclude this for the future, and I do not know precisely how other people go about deciding what they import/ curate/ otherwise work on. --Daniel Mietchen (talk) 03:06, 18 May 2019 (UTC)
Yeah, that makes sense… I created a new Item contributor list (Q63975091) for this and changed the instance of in https://www.wikidata.org/w/index.php?title=Q57897148&type=revision&diff=946077106&oldid=899254744 to that (but only there yet). Do you think it makes sense to do go ahead with that? Cheers, Hoo man (talk) 13:25, 21 May 2019 (UTC)
@Hoo man: Were you able to sort it out? The new item could have scientific publication (Q591041) sub-class too? What is the telling characteristic of this type of publication that makes it unworthy as an article? What was it a problem for you that it was in the article class? It helps knowing if there is a practical problem or if the change was more a structural design decision. Jagulin (talk) 04:57, 3 July 2019 (UTC)

Wikidata weekly summary #365

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Added lastrevid of entities to JSON dumps – thanks Pintoch!
    • Working to scale the Wikidata Concepts Monitor system (phab:T203366)
    • Imrpove logging in on mobile (phab:T215913)
    • More work on mobile termbox
    • Several developers from the Wikidata team attended to the hackathon, discussed with the community, gathered feedback, hacked on things together with volunteers :)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #366

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past: Wikidata Labs XV in Brazil, with an introduction to lexicographical data (slides)
    • Past: Workshop for experienced editors of nl.wiktionary to explore the possibilities of lexicographical data.
  • Other Noteworthy Stuff
    • The US Library of Congress are integrating Wikidata QIDs into their authority files (blog post)
  • Development
    • Deploy the EntitySchema extension on test.wikidata.org and beta.wikidata.org
    • Remove the remaining beta feature config for constraint-suggestions (phab:T220609)
    • Introduce baserevid for conflict checking in Lexeme (phab:T217245)
    • Fix a bug making impossible to get Lexeme Forms and Senses via the API (phab:T223995)
    • Add Wikidata query service lag to Wikidata maxlag (phab:T221774)
    • Allow accessing Wikibase entities from multiple Wikibase databases (phab:T214557)
    • More work to get termbox ready for deployment
    • Add a login warning on mobile termbox editing (phab:T221831)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.



Wikidata weekly summary #367

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Specify license of mediawiki/Wikibase/WikibaseLexeme ontology (phab:T216842)
    • Enable bugfix on beta for wbeditentity setting aliases to empty array (phab:T223300)
    • Use correct validator in alias changeop and provide error messages if alias is too short (phab:T223311)
    • More work on the use of special pages Special:SetAliases and Special:SetLabelDescriptionAliases with aliases containing | character (phab:T223270)
    • Add Wikidata query service lag to Wikidata maxlag (phab:T221774)
    • Fix BadMethodCallException wbgetentities when getting Lexeme subentities (forms, senses) (phab:T223995)
    • Scale the machine learning components of the WDCM system w. {text2vec} WarpLDA implementation (phab:T203366)
    • Inspect strange behavior of the WD_percentUsageDashboard (phab:T217994)
    • WDCM dashboards maintenance: eliminating the need to use the wdcm.maintable in Hive, WDCM Geo is now independent of it (with its update engine running Spark instead) and re-designed to match the WDCM standards (phab:T217994, phab:T214586, phab:T217997)
    • Further preparations for the Wikidata Languages Landscape project (phab:T221965)
    • More progress in order to get the mobile service deployed
    • Adding an IP edit warning popup for mobile termbox (phab:T221831)
    • Allowing users to ignore this popup permanently (phab:T221833)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

sourcemd_batch_processing - batch 8020

Latest comment: 4 years ago3 comments3 people in discussion

Hi there! Re: https://www.wikidata.org/w/index.php?title=Q30988215&diff=955276402&oldid=prev - it seems your bot confuses the concept of a "new species" with the record company New Records and a scholarly article named New Species. Could you have a look-see when you get the time? Moebeus (talk) 12:03, 4 June 2019 (UTC)

@Daniel Mietchen: Should the subject for "new species" be species nova (Q27652812)? Trilotat (talk) 00:28, 5 June 2019 (UTC)
Thanks both. I have changed the topic tagging to species nova (Q27652812) for the ca. 50 articles affected. Can't do much else other than pinging Magnus. --Daniel Mietchen (talk) 01:30, 5 June 2019 (UTC)

Wikidata weekly summary #368

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

How's ORES working out for you?

Latest comment: 4 years ago1 comment1 person in discussion

Hi Daniel Mietchen, I'm working with User:EpochFail (@halfak on irc) on a research study to look into how mw:ORES is working out on wikis where it has been enabled. I was hoping to talk a little about what the kind of work you do on Wikidata and about how the ORES edit filters and classifiers have been working out. Do you use any tools other than Special:RecentChanges or Special:Watchlist that take advantage of ORES? Do you know of any other tools that are used to patrol that do not use ORES? I'm also interested in any other observations you may have about how the ORES scores are working out. Thank you! Groceryheist (talk) 23:53, 12 June 2019 (UTC)

preprints described as scholarly article

Latest comment: 4 years ago2 comments1 person in discussion

Hi, I found Closed-loop feedback control for microfluidic systems through automated capacitive fluid height sensing (Q59616999) which was created by User:QuickStatementsBot in your name (batch 1899). The item is a preprint (Q580922) published in bioRxiv (Q19835482) (a detail ommited by the bot) and later published as a proper scholarly article (Q13442814) described in identically titled Closed-loop feedback control for microfluidic systems through automated capacitive fluid height sensing. (Q50045828). Could you fix similar items so they are described in instance of (P31) as preprints and not as "proper" scholarly articles? Thanks, DGtal (talk) 07:23, 17 June 2019 (UTC)

HI, did you understand my request? DGtal (talk) 06:22, 8 July 2019 (UTC)

Wikidata weekly summary #369

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #370

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Beginning of wb_terms migration (phab:T221764)
    • Fixed a bug with phan on Wikibase (phab:T226083)
    • Enable bugfix for wbeditentity setting aliases to empty array (phab:T223303)
    • Fix an issue with pipe character on some special pages (phab:T223270)
    • Fix an issue with removed constraint still displayed on Lexeme (phab:T223372)
    • Make edits to EntitySchema pages autopatrolled (phab:T224495)
    • Work on creating better edit summaries for wbeditentity API endpoint (phab:T224010)
    • Deploy the work environment for new mobile termbox
    • Start setting up the technical environment for Wikidata bridge

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Mostly blank items about articles

Latest comment: 4 years ago6 comments2 people in discussion

Hi Daniel Mietchen,

I found a couple mostly blank ones from 2017, e.g. Q28681089, Q28705231, Q28661357. Maybe there is a way to identify all of them and fill in the missing info by bot. --- Jura 09:48, 25 June 2019 (UTC)

Thanks both for checking and providing the query. These items are about articles where PMC has scans rather than proper full text, and this seems to correlate with poor metadata. In principle, we have tools to fix such things (example), but they can only work with the metadata that is being made available. Things are complicated further by an apparent block of Toolforge servers by NIH, as per this Phabricator ticket. --Daniel Mietchen (talk) 03:52, 26 June 2019 (UTC)
  • No problem. Compared to the number of entries, it seems marginal even if it might possibly apply to any such item without a title statement. Sample: Q57728434. --- Jura 11:08, 26 June 2019 (UTC)
  • Looks like sometimes also "published in" is omitted: Q24799245. It's a bit of a mystery to me how the script could generate multiple items with identical label+description combinations. --- Jura 18:14, 26 June 2019 (UTC)
Missing "published in" is usually due to the item for the publication venue not existing at the time of creation of the item for the article. In this case, it seems to be due to a mismatch between the journal's official title and the title used in PubMed. --Daniel Mietchen (talk) 05:57, 27 June 2019 (UTC)

Wikidata weekly summary #371

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • More work on preparing the technical setup for Wikidata Bridge development
    • Implement Feature Flag for Wikidata Bridge (phab:T225935)
    • Discuss the best way to connect template parameter to corresponding Wikidata property (phab:T224832)
    • Improve the documentation for Wikibase sites setup (phab:T218282)
    • Prepare the last steps for reading from new term store implementation (phab:T225603) according to the migration plan (phab:T221765)
    • Fixed a bug and reduced significantly the amount of addUsagesForPage jobs in our jobs queue (phab:T205045)
    • Removed feature flag for the bugfix for wbeditentity setting aliases to empty array (phab:T223305)
    • Decreased EntityUsageTable addUsage batch size to 100 (phab:T225500)
    • Configured query service lag for Wikidata maxlag (phab:T222193)
    • Helped fixing an issue with moving files on Commons (phab:T226672)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wiki Science Competition 2019

Latest comment: 4 years ago7 comments2 people in discussion

Your massive creation of links to Ferenc Bánhidy (Q41693708), an item I created in order to use the uploaded files from the European Science Photo Competition 2015, reminded me to ask you if you want to be a juror for Wiki Science Competition 2019 (WSC is the evolution of the previous European edition).

I am starting to draft the international jury. Would you be interested in joining the new one? here.

Please notice that during the 2017 edition I put on purpose links to wikidata item of all people in the jury as a tool for wikidata literacy, I suppose you could enjoy this aspect. This time I will be also sure that their publications are updated if they are active researchers.

Plus, I did not have the time to verify all top images and the related wikidata items here because there were so many last-minute problems (Saudi Arabia and Poland needed me to step in to be fixed), but this edition I will probably like to do so and stress it as a part of our campaign. Like tweeting about an updated item every time a new picture is uploaded.

Let me know if you are interested. If so, I will inform the main organizers.

If you don't want to be a juror, I can put you in the academic committee or create a volunteer committee. We are quite selective with the uploaded images and we verify them carefully. I would like to write a post for the website discussing also about the use of wikidata.

I can go on, but if you join, we will simply make some skype call soon about it.

WSC starts in November and goes on until the following year.--Alexmar983 (talk) 19:57, 7 July 2019 (UTC)

Thanks, Alexmar983 — count me in. --Daniel Mietchen (talk) 03:02, 8 July 2019 (UTC)
Good.--Alexmar983 (talk) 10:03, 8 July 2019 (UTC)
I am going to insert your name here. ok?--Alexmar983 (talk) 13:25, 25 September 2019 (UTC)
Fine with me. --Daniel Mietchen (talk) 16:28, 25 September 2019 (UTC)
If you were not contacted, the manager/editor of the webpage User:Reosarevok would like to know which image should be used here. Any preference from Commons?--Alexmar983 (talk) 13:19, 4 October 2019 (UTC)

Hi.Russia completed the WSC2019 upload months in advance, here there are portraits that should be linked or integrated in wikidata. I certainly do not have the time to do it now (maybe one or two), so if you want you can take a look. Please if you are going to help on the wikidata integration of bibliometri item, I would like to describe this work (that I have also done last edition) on the WSC main website in a concise post. Thank you!--Alexmar983 (talk) 13:13, 3 November 2019 (UTC)

Wikidata weekly summary #372

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: ZI Jony
  • Other Noteworthy Stuff
  • Development
    • Enabled JSONLD support for entity data (example)
    • Fixed JSON dump issue (phabricator:T226601)
    • Readded qualifier hashes in JSON output that accidentally got lost (phabricator:T227207)
    • Made sure changes on Entity Schema pages by autoconfirmed users are autopatrolled (phabricator:T224495)
    • Looked into issues with partial blocking on Wikidata entities (phabricator:T207893)
    • Adding MediaInfo as an entity type that can be used in the "allowed entity types"-constraint (phabricator:T224362)
    • Investigating an issue with the tours on Wikidata (phabricator:T223999)
    • Initial work for the edit dialog that is needed for editing of Wikidata's data from Wikipedia (Wikidata Bridge)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #373

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Structured Data on Commons: RDF output for MediaInfo is now available (example)
    • Edits with the tag #suggestededit-add 1.0 come from the suggested edit feature on Wikipedia's Android app: see the FAQ for more information
    • Property number 7000: DigitalNZ ID is live. This data aggregator has over 30 million records. The proposal was the first from Ambrosia10, a New Zealand editor.
  • Development
    • Create docker image for wdqs version 0.3.2 (phab:T226939)
    • Fix an issue with JSON output lacking qualifier hashes (phab:T227207)
    • Track number of links to schema pages (phab:T218903)
    • Disable Wikidata sitelinks in ProofreadPage namespaces (thanks to Matěj Suchánek) (phab:T227201)
    • Fix a cache issue with the language of the "check entities against this schema" link (phab:T224594)
    • Add EntitySchema extension to wikibase-docker bundle image (phab:T226152)
    • Enable JSON-LD support for Wikidata (phab:T220696)
    • Add baserevid to WikibaseLexeme API module (phab:T225073)
    • Extracting (and logging) Data Bridge parameters from edit links (phab:T226994)
    • Opening a modal with edit this link information (phab:T226996)
    • Showing the current Wikidata value in edit modal (phab:T226997)
    • Disabling interactive elements while saving on mobile termbox (phab:T222886)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #374

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: 1997kB
  • Events
    • Past: IRC office hour, July 16th (log)
    • Upcoming: Wikidata Tainan Meetup in Taiwan, July 31st (Facebook event)
  • Development
    • Fix a bug that was preventing to add multiple glosses (phab:T228080)
    • Show number of senses and forms on page information for WikibaseLexeme entities (phab:T224844)
    • Show number of statements and external identifiers on page information for Wikibase entities (phab:T224842))
    • Track number of external identifiers on Wikidata over time (phab:T224129)
    • Fix a few queries on Grafana (phab:T227788)
    • Update the query host for Grafana (phab:T218710)
    • Add support for "MediaInfo" as value for "allowed entity types"-constraint (phab:T224362)
    • Data bridge: open a modal with edit link information (phab:T226996)
    • Show the current Wikidata value in edit modal (phab:T226997)
    • Extract data bridge parameters from edit links (phab:T226994)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Dieses ist mir lustig...

Latest comment: 4 years ago1 comment1 person in discussion

I got a kick out of L50000. Subtle and nicely done. —Scs (talk) 23:48, 27 July 2019 (UTC)

Wikidata weekly summary #375

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Re-evaluate supporting dcatap namespace (feel free to give feedback)
    • Data bridge: open modal with edit link information (phab:T226996)
    • Show the current Wikidata value in the modal (phab:T226997)
    • Add editing widget/input to client edit modal (phab:T226998)
    • supporting baserevid request param in lexeme api endpoints (phab:T217245)
    • Fix new store code in order to continue the terms migration (phab:T226008)
    • Fix an issue with broken WikibaseQualityConstraints tests (phab:T228855)
    • Fix issue that used to cause many fatals on production (phab:T227450)
    • Drop wbEntity config in entity pages (phab:T85499)
    • Fix an Internal error in Recent Changes for Lexeme (phab:T228996)
    • Create better summaries for our wbeditentity endpoint (phab:T220696)
    • Respect user's preference for thumbnail sizes on Wikidata (phab:T224189)
    • Allow linking to Schemas in statements (phab:T214884)
    • Fix a bug with Wikidata Tours (phab:T223999)
    • Update accounting for WDQS lag in wikidata maxlag param (phab:T221774)
    • More work on allowing accesing one wikibase instance from another (phab:T214557)
    • Deploy the mobile termbox on test.wikidata.org and fix various bugs
    • Show progress/activity on termbox mobile if a save request is still being processed (phab:T222890)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #376

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Fix logging for errors on wbcontentlanguages requests (phab:T228888)
    • Add request information to request timeout errors (phab:T228885)
    • Show an error message when saving fails on mobile termbox (phab:T222884)
    • Add editing widget/input to client edit modal (phab:T226998)
    • Show the current Wikidata value in the Bridge modal (phab:T226997)
    • EntitySchema datatype (phab:T214884)
    • Reduce the number of ResourceLoader modules that WikibaseClient register: (phab:T203696)
    • Reduce text returned by EntityContent::getTextForFilters (phab:T226216)
    • Fixed a bug with PHP Warning (phab:T229482)
    • Fixing a bug about value pickers being broken (phab:T229604)
    • Fixed BadMethodCallException wbgetentities when getting Lexeme subentities (phab:T223995)
    • Investigate on Graphoid issues (phab:T229236)
    • Fix issues on Wikidata Tours (phab:T214884)
    • Make logging warning or info of not finding entity for revision configurable (phab:T229574)
    • Fix Grafana Datamodel References dashboard (phab:T214894)
    • Move "Wikidata item" link outside of "toolbox" sidebar to "other projects" sidebar (phab:T66315)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Leslie Barclay (Q61216213)

Latest comment: 4 years ago2 comments2 people in discussion

Hello Daniel, in January, you created the object Q61216213 containing no further information than a name. It was later expanded by another user, adding information about Leslie W. Barclay, a British electrical engineer. Today, I further expanded the object based on a recent obituary. However, a look at the links to this object indicates that it's a different Leslie Barclay you had in mind, so you may want to create another object about that person. Regards, Axolotl Nr.733 (talk) 12:30, 10 August 2019 (UTC)

@Axolotl Nr.733: Done: Leslie Barclay (Q66702520) — thanks for the ping! --Daniel Mietchen (talk) 03:14, 23 August 2019 (UTC)

Wikidata weekly summary #377

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • The open source geocoder w:en:Nominatim used by the OpenStreetMap project is participating in the Google Summer of Code with an internship working on integrating Wikidata as a ranking metric for its search results. Check the development blog.
  • Development
    • Fix a caching problem on termbox (phab:T228978)
    • Investigate options for termbox load testing (phab:T229790)
    • Use thumbnail preferences for thumbnail of Commons media file (phab:T224189)
    • Add tags parameter to Wikibase APIs that edit entities (phab:T229917)
    • Move "Data item" link outside of sidebar toolbox (phab:T66315)
    • Create Maintenance Script to Remove Terms in a Language from Current Revision (phab:T222606)
    • Fix Grafana Datamodel References dashboard (phab:T214894)
    • Add editing widget/input on Bridge (phab:T226998)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #378

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • In this new section, you can share your favourite tool with the other Wikidata users. You can add some suggestions here.
    • NameGuzzler allows you to automatically add an identical label or alias into many languages (for example, the name of a person or a place). You can define your own custom list of languages that you want to add.
  • Development
    • Fix an issue with the pop up of Wikidata Tours (phab:T223999)
    • Call WikibaseLexeme API with baserevid parameter from the UI (phab:T217245)
    • Fix a bug with CheckConstraintsJob (phab:T227450)
    • Fix a bug with wbgetentities when getting Lexeme subentities (phab:T223995)
    • Add editing widget/input to client edit modal: (phab:T226998)
    • Add tags parameter to Wikibase APIs that edit entities: (phab:T229917)
    • More work on the the production Termbox service
    • tidying up our browser test suite (phab:T229910)
    • adding browser tests for basic editing (phab:T230187)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Strange dup

Latest comment: 4 years ago4 comments2 people in discussion

Hi Daniel Mietchen, Found a strange dup: Q38563811 and Q41924800. One came up on Wikidata:WikiProject Random.

Is there a place where we could list the different types of issues that come up with these imports? Might make it easier to find people who can identify all similar cases and/or fix them.

In any case, I think it would be good to continue the imports. --- Jura 12:40, 20 August 2019 (UTC)

I set up User:Research Bot/issues to discuss these things. New imports are not a priority for me right now but I hope we can resume soon. --Daniel Mietchen (talk) 23:04, 20 August 2019 (UTC)

Adding articles in the Post-SourceMD era?

Latest comment: 4 years ago4 comments2 people in discussion

Daniel, are you by chance still adding articles since SourceMD has been shut down? If so, are you doing so with any special tools? I'm adding them individually and find it to be quite tedious. I'm just wondering if there's a better tool. Thanks, Trilotat (talk) 21:19, 20 August 2019 (UTC)

I haven't imported scholarly articles in over a month, yet I think Wikidata:Fatameh still works. It has its own problems and works best with PMCID (P932) for articles not in Wikidata yet. Note that as far as I can tell, it only has a passive understanding of DOI (P356), i.e. it can add it if triggered by PubMed ID (P698) or PMCID (P932) but cannot be triggered by DOI (P356). --Daniel Mietchen (talk) 23:11, 20 August 2019 (UTC)
This is awesome! thanks. Another tool for me to use. Thank you!! Trilotat (talk) 04:37, 21 August 2019 (UTC)
Looks like the old SourceMD is up again. It understands DOI, PMID and PMCID and works fine for single publications or up to a few dozens. --Daniel Mietchen (talk) 05:07, 22 August 2019 (UTC)

Wikidata weekly summary #379

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4-Wikidata Affinity Group call: Wikimania recap, 27 August. Agenda
  • Development
    • Deploy mobile termbox, follow-up and bug fixing
    • Deploy then rollback the move of "Wikidata item" link on clients due to cache issues (phab:T66315)
    • Work on adjusting the save button of the Entity Schema editor (phab:T230398)
    • Work on the bridge emitting button (phab:T230326)
    • Introduce a header for the bridge modal (phab:T230328)
    • Produce initial statistics/indicators for the Wikidata Languages Landscape (phab:T223119)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #380

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Adjust label of save button of the Entity Schema and add accesskey for easier editing editor (phab:T230398)
    • Get Grafana Datamodel References dashboard back up and running (phab:T214894)
    • Fix an issue in EntitySchema tests that caused some CI failures (phab:T231065)
    • Localize Wikibase API help links (phab:T231269)
    • Support tags parameter on Wikibase APIs that edit entities (phab:T229917)
    • Add in Wikidata support for sitelinks to https://nap.wikisource.org (phab:T212886)
    • Reading property terms from new store in production now (phab:T225053)
    • Adding WDQS lag to maxlag info, to avoid stress on WDQS machines (phab:T221774)
    • Implementing the fallback version of the new better edit summary messages on items through API (phab:T224010)
    • Fixing the issue of an invisible quality constrain violation indicator (phab:T227866)
    • Switching item terms to migration stage of writing to both wb_terms and the new store (phab:T225055)
    • Preparing to run migration of item terms (phab:T219123)
    • Allowing to access Wikibase entities from multiple (Wikibase) databases (phab:T214557)
    • Hiding non-supported languages in old termbox (phab:T227083)
    • Work on a new solution to move "Data item" link outside of sidebar toolbox avoiding the cache issues (phab:T66315)
    • Bridge: saving the Wikidata edit when submitting (phab:T226999)
    • Showing the current Wikidata value in the edit modal (phab:T226997)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Add P407 to scientific articles

Latest comment: 4 years ago3 comments2 people in discussion

Hi,
Do you think you can add language of work or name (P407) to new items dedicated to scientific articles created by Research_Bot ? Simon Villeneuve (talk) 13:53, 4 September 2019 (UTC)

Not at the moment, sorry. --Daniel Mietchen (talk) 02:17, 5 September 2019 (UTC)
Please, at least for P407:Q1860. I'm pretty sure is'nt more than 2 lines of code in your script.
I can't do this alone anymore. I have a wife and a kid man. Simon Villeneuve (talk) 01:45, 23 September 2019 (UTC)

More duplicate DOI's

Latest comment: 4 years ago2 comments2 people in discussion

Hi Daniel, I've pretty much finished the cleanup of items with duplicate DOI's (the remaining cases are ones where the labels/titles of the two articles are quite different, suggesting either one of the DOI's is wrong or the journal really issued the same DOI to multiple papers). However, I noticed again even some very recent quickstatements entries by you among these duplicates - I thought this would have been fixed by now. An example is Data sharing in the sciences (Q66677611) and Data sharing in the sciences (Q66677610) (both created by you within the same minute on August 22). ArthurPSmith (talk) 13:55, 9 September 2019 (UTC)

Thanks, Arthur, for the merges and for keeping an eye on such issues. I'm not sure precisely what might have gone wrong here, but I think that batch contained DOIs scraped from various sources, and while I did check for duplicates, I probably did not normalize by case before that. --Daniel Mietchen (talk) 01:31, 10 September 2019 (UTC)

Wikidata weekly summary #381

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: References in Wikidata, 10 September. Agenda
  • Tool of the week
    • moveClaim allows you to move or copy claims from one item to another. This is especially useful when splitting items, or creating lots of similar items.
  • Other Noteworthy Stuff
    • Seventh birthday of Wikidata: you can start thinking about organizing a meetup in your area to celebrate the birthday, or about a present for the community!
    • The first draft of the program of the WikidataCon is now available. The content of the three main session rooms will be live-streamed and recorded for people who cannot participate in the conference.
    • Because of a database switch, Wikidata will be in read-only more on September 10th at 05:00 UTC, for max. 30min (phab:T230762)
    • Recent tool: @Wikidatabot, a Telegram bot that allows you to search for something on Wikidata from Telegram
    • New game: Wikidata Mall, a Telegram management simulation game where content is generated from Wikidata
  • Development
    • Wikidata got a high-resolution logo, thanks to Odder (phab:T230120)
    • New monolingual code languages are added, thanks to Jon Harald Søby: TLI (Tlingit), clc (Tsilhqotʹin), alc (Kawésqar), kld (Gamilaraay), peo (Old Persian)
    • Fixed a bug in constraint violations indicator that was not showing up sometimes (phab:T227866)
    • Make Lua's function mw.wikibase.entityExists return true for redirects (phab:T192462)
    • Reviewed and followed up on highlighting statements when using "#P" in URL (phab:T178745)
    • Wikidata Bridge: saving the Wikidata edit when submitting (phab:T226999)
    • Showing the label for the Property instead of the id (phab:T227759)
    • Overcoming a conceptional oversight between mediawiki and standard language codes (phab:T231833)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Community Insights Survey

Latest comment: 4 years ago1 comment1 person in discussion

Share your experience in this survey

Hi Daniel Mietchen/Archive/2018,

The Wikimedia Foundation is asking for your feedback in a survey about your experience with Wikidata and Wikimedia. The purpose of this survey is to learn how well the Foundation is supporting your work on wiki and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 17:37, 10 September 2019 (UTC)

Source MD down again?

Latest comment: 4 years ago3 comments2 people in discussion

Does it work for you? I keep getting a "504 Gateway Time-out" error. Trilotat (talk) 21:38, 10 September 2019 (UTC)

Got lots of these today as well (using the old one — haven't touched the new one in a while), but it occasionally works in between. Not sure what the problem is. --Daniel Mietchen (talk) 02:57, 11 September 2019 (UTC)
Seems to be working again. Trilotat (talk) 04:35, 11 September 2019 (UTC)

SourceMD scholarly articles without P1433

Latest comment: 4 years ago3 comments3 people in discussion

Hi there!

Oddly, it seems that some SourceMD scholarly articles (see e.g. Corinne Leveleux-Teixeira (Q30135205)'s Q60515751) have no published in (P1433) claim...

Nomen ad hoc (talk) 11:38, 14 September 2019 (UTC).

Validating and adjusting Medical information in Wikidata with SPARQL and PubMed

Latest comment: 4 years ago5 comments2 people in discussion

Dear Sir,

I thank you for your efforts. I was absolutely honoured to discuss with you last year. As promised, I am beginning this month my work to develop a method for validating amd enriching Medical information in Wikidata. As said, the method uses Wikidata query service and PubMed Entrez API to adjust and enrich Wikidata. I ask if you can join the work. If you like that, I can send you an overview about the work by email.

Yours Sincerely,

--Csisc (talk) 14:01, 14 September 2019 (UTC)

@Csisc: Thanks for the note. Yes, please share details, and preferably in public — I do not find it fruitful to discuss such things via email unless there is a specific reason for that. --Daniel Mietchen (talk) 04:51, 15 September 2019 (UTC)
I thank you for your answer. I already discussed this work in Wikimania 2019. For details, please see presentation slides. After that, I did several discussions on talk pages about this important topic. Currently, we have decided the used method and we are working on the practice of this idea. That is why we use emails for discussion. We do not like to disturb people on the mailing list with our messages as we are working on daily basis. However, we will publish the method in the Wikidata mailing list when we finish working on it to have comments. As well, emails are more practical for me as this allows me to send datasets and documents to the participants. However, I can create a talk page on Meta to discuss the work if you like that. --Csisc (talk) 14:40, 15 September 2019 (UTC)
@Csisc: Well, then let's go for email. I had seen your Wikimania slides before you gave the talk and would indeed like to know more, especially around the PubMed part. --Daniel Mietchen (talk) 06:58, 16 September 2019 (UTC)
Email sent. I will be absolutely honoured to receive your opinion about the work. --Csisc (talk) 12:48, 17 September 2019 (UTC)

Wikidata weekly summary #382

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Hauki lets you browse existing Lexemes, add Senses to them, and easily create new Lexemes for common languages and lexical categories.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Reminder: Community Insights Survey

Latest comment: 4 years ago1 comment1 person in discussion

Share your experience in this survey

Hi Daniel Mietchen/Archive/2018,

A couple of weeks ago, we invited you to take the Community Insights Survey. It is the Wikimedia Foundation’s annual survey of our global communities. We want to learn how well we support your work on wiki. We are 10% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! Your voice matters to us.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 19:53, 20 September 2019 (UTC)

Wikidata weekly summary #383

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Namescript fills in labels, descriptions and aliases of items about names, making it easier to create such items (you only need to provide a few statements).
  • Development
    • Wikidata Bridge: add an edit tag parameter when saving (phab:T227003)
    • Adapt buttons' texts to UI language (phab:T228259)
    • More work on setting up the technical background to work on tainted references
    • More work on reducing the resources needed to load pages
    • Create a dependency graph of existing RessourceLoader modules (phab:T232728)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

instance of (P31) recommendation for Comment and for Reply?

Latest comment: 4 years ago3 comments2 people in discussion

@Daniel Mietchen: What instance of (P31) would use use for a comment and a reply to scholarly article? Also, do you have any suggestions how to connect the comment and the reply to the item(s) to which they are related? Trilotat (talk) 20:34, 26 September 2019 (UTC)

I would probably keep this P31 and add a genre (P136) statement but am not sure about that either. --Daniel Mietchen (talk) 22:09, 26 September 2019 (UTC)
In terms of linking back to the item(s) commented about or replied to, I think we could use main subject (P921). --Daniel Mietchen (talk) 02:05, 27 September 2019 (UTC)

Wikidata weekly summary #384

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • This Recent changes tool allows to get a list of unpatrolled Wikidata changes with enhanced filters that are more adapted to Wikidata than the standard Recent Changes page. Available actions include mass patroling and easier revert interface.
  • Other Noteworthy Stuff
    • The state library of Berlin is using Wikidata to display a map of pictures from their architecture journals: Berlin um 1900 - eine fotografische Zeitreise
    • Edit summaries coming from the wbeditentity API (for example from the mobile termbox) will be improved from October 2nd (announcement, ticket)
    • You can nominate your favourite Wikidata and Wikibase projects for the WikidataCon Award until October 7th
  • Development
    • More work done on removing some resource loader modules in order to speed up the load of pages
    • Wikidata Bridge: add an edit tag parameter when saving (phab:T227003)
    • Adapt buttons' texts to UI language (phab:T228259)
    • research regarding permissions/protection (phab:T231209)
    • More preparation work for improving references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #385

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • soweego links Wikidata to large third-party catalogs. Together with its friend Mix'n'match, it helps Wikidata to become the universal linking hub of open data.
  • Development
    • Continue work on removing and optimizing resource loader modules
    • Wikidata Bridge: obey wgEditSubmitButtonLabelPublish (phab:T228260)
    • Canceling the modal (phab:T231282)
    • Research regarding permissions/protection (phab:T231209)
    • Investigation to ensure editing with the same credentials (phab:T231887)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Books metadata in Wikidata

Latest comment: 4 years ago4 comments3 people in discussion

Hi Daniel, I have difficulty inserting bibliographic metadata related to books through ZotKat: it gives me error, but it is fine with the articles of scientific journals. What can I do? do i need to correct something? If Zotkat is not adequate, which tool do you suggest to automatically create the items of the books starting for example from the ISBN?Alessandra Boccone (talk) 15:02, 8 October 2019 (UTC)

@Alessandra Boccone: I don't do books much, so pinging User:Zuphilip on this one. --Daniel Mietchen (talk) 03:33, 9 October 2019 (UTC)
@Daniel Mietchen: Thanks!Alessandra Boccone (talk) 08:56, 9 October 2019 (UTC)
Discussion continued in https://www.wikidata.org/wiki/User_talk:Zuphilip#Books_metadata_in_Wikidata . Thanks for the ping! --Zuphilip (talk) 19:13, 11 October 2019 (UTC)

Wikidata weekly summary #386

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • ShowTalkLabels: with this script enabled, when a talk page is shown on your watchlist or similar pages, the label of the related entity is shown.
  • Development
    • Abuse filter has been improved so saving an edit should be a bit faster now. (phab:T156095)
    • A new Lua function is providing the site's global ID of the wiki where this function is used (phab:T194023)
    • Wikidata Bridge: test data for the demo system (phab:T224834)
    • Research regarding permissions/protection (phab:T231209)
    • Investigate of the purging strategy (phab:T227758)
    • Restyling of mobile termbox (phab:T223452)
    • Adding "fewer languages" button at the end of the expanded list of "all entered languages" (phab:T232595)
    • More work on reducing the resource loader modules
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #387

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • The Wikidata Wor(l)dmap is showing translations of the same concept on a world map. To use it, type a word (for example "water") in the search field, then observe the map. You can zoom in the map. The data comes from Wikidata item labels and the coordinate location property of the language.
  • Other Noteworthy Stuff
    • Wikidata won an Open Publishing Award (description).
    • Panandâ, a mobile app powered by Wikidata (and Wikimedia Commons), was selected as one of the five finalists in the App for Social Good category in the Android Masters 2019 competition organized by Google Developer Group Philippines. The final event will be held on November 16.
    • Issue with Wikidata Query Service: aggregate variables can no longer reuse the names of other variables (T235540).
    • You can translate labels in the background image of Wikidata front page by adding translation to this file
  • Development
    • Fixed the DuplicateReferences gadget that was broken due to refactoring work needed to make pages load faster and development easier (phab:T234094)
    • Wikidata Bridge: restricting the length of string value inputs (phab:T229241)
    • research delayed kicking in of Bridge (phab:T233305)
    • enable/disable save button depending on Bridge state (phab:T230342)
    • More work on reducing the resource loader modules
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Asking for a letter of support to create a research unit in Tunisia

Latest comment: 4 years ago4 comments2 people in discussion

Dear Sir,

I thank you for your efforts. We are managing to create a research unit called "Data Engineering and Semantics" in the University of Sfax, Tunisia. The purpose of this research unit is to gather Wikiresearchers from University of Sfax into a recognized research structure and have funding from Tunisian Ministry of Higher Education. In order to do that, we need to have a letter of support from institutions all over the world. I ask if you or the director of your research department can write a letter of support for us so that we can have our application approved. This will be acknowledged. --Csisc (talk) 14:25, 23 October 2019 (UTC)

OK, just confirming that I've seen this. Happy to do this, and I have ideas on what we could be doing together. What's the deadline? --Daniel Mietchen (talk) 13:49, 24 October 2019 (UTC)
I thank you for your answer. I look forward to collaborating with you. This is absolutely an honour for our team. I just sent an email this morning in which I gave detailed information about the research unit. Concerning the deadline, it will be on November 1, 2019. --Csisc (talk) 20:20, 25 October 2019 (UTC)
I thank you for your efforts. I ask if you can send us the letter of support by tomorrow afternoon as the deadline to send the research unit application is on Friday. --Csisc (talk) 12:16, 30 October 2019 (UTC)

Jessica W. Lynch Alfaro / automatisierte Autorenverlinkung?

Latest comment: 4 years ago3 comments2 people in discussion

Hallo Daniel, ich habe Q72180638 zur Primatenforscherin Jessica W. Lynch Alfaro angelegt und angefangen, sie in ihren Publikationen zu verlinken. Geht das auch irgendwie halbautomatisiert? Denn diese händische Übertragung kostet derart viel Zeit, dass ich bei über 100 Suchtreffern (und somit potenziellen Ergebnissen) schon am Anfang kapituliere. Wenn ich dann mitbekomme, dass der gerade eben noch verlinkte Michael E. Alfaro (angesichts der gleichen Arbeitsstätte und ihrer früheren Autorenangabe Jessica W. Lynch vermutlich ihr Mann) im Artikel Q44302860 ebenfalls nicht verlinkt ist, wächst der Berg an Arbeit gleich noch einmal an. -- Gruß, 32X (talk) 15:24, 24 October 2019 (UTC)

@32X: Probier mal den Author Disambiguator. Als Startpunkt eignet sich ein Artikelitem (Beispiel), ein Autorennamenstring (Beispiel), ein Autorenitem (Beispiel) oder eine /missing page in Scholia, z.B. für ein Thema (Beispiel). --Daniel Mietchen (talk) 20:28, 24 October 2019 (UTC)
PS:
--Daniel Mietchen (talk) 20:36, 24 October 2019 (UTC)

New page for catalogues

Latest comment: 4 years ago1 comment1 person in discussion

Hi, I created a new page for collecting sites that could be added to Mix'n'match and I plan to expand it with the ones that already have scrapers by category. Feel free to expand, use for property creation. Best, Adam Harangozó (talk) 21:30, 26 October 2019 (UTC)

Wikidata weekly summary #388 & Wikidata Birthday

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • MachtSinn is a game to easily add Senses to Lexemes, based on suggestions from Items labels. It helps improving the data about languages in Wikidata.
  • Development
    • Wikidata Bridge: Create progressive disabled version of save button (phab:T235055)
    • Save original revision data in store (phab:T235052)
    • Add interface for tracking/logging (phab:T236233)
    • Make app change button attributes depending on state of store (phab:T235056)
    • More work on reducing the resource loader modules
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #389

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • SPARQL RC is showing the recent changes on items that are listed from a specific query. It is very useful to monitor the changes on a specific subset of data, for example data that you recently imported in Wikidata.
  • Development
    • Made the Lua functions mw.wikibase.getBestStatements and mw.wikibase.getAllStatements faster if called more than once for the same statement on a single page
    • Fix a bug on the mobile termbox (phab:T236677)
    • Update Wikibase Lua documentation (phab:T225497)
    • Highlight individual statements when selecting them in the URL (phab:T234079)
    • Add monolingual language code "sa-Sidd", "pi-Sidd", tnq (Taíno), car (Kalinago) and bdr (phab:T230881, phab:T220284, phab:T234330)
    • Make it possible to collapse the "All entered languages" section when at the end of the section (phab:T232595)
    • Cache php.getEntityStatements in mw.wikibase (phab:T236491)
    • Tracking Wikidata Bridge openings by Datatype in Grafana (phab:T231204)
    • Not showing Bridge edit pens when the editor cannot edit the article (phab:T235152)
    • A bugfix to only show scrollbars where they are supposed to be shown (phab:T235622)
    • Enabling/Disabling the Save button depending on the bridge state (phab:T230342)
    • More work on tainted references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Label of Q57696956

Latest comment: 4 years ago4 comments2 people in discussion

Hi Daniel Mietchen, seems something went wrong at Q57696956. BTW, you might want to look into ISSN donation. --- Jura 09:40, 6 November 2019 (UTC)

Thanks. I fixed Maria Filomena F. Nave (Q57696956). Don't have bandwidth for ISSN right now. --Daniel Mietchen (talk) 04:43, 11 November 2019 (UTC)
If I was sure that just Q57696956 went wrong, I would have fixed it directly. The problem with bot edits is that not only there are generally several to fix, but also it's likely to happen again once one fixed. --- Jura 09:23, 12 November 2019 (UTC)
Yes. The problem here was that the person had put multiple aliases into their author field on ORCID. This is rare but she was probably not the only one. --Daniel Mietchen (talk) 11:51, 12 November 2019 (UTC)

Expanding author profiles in Scholia

Latest comment: 4 years ago3 comments2 people in discussion

Thanks for your presentations at the WikiConference such as this talk on Wikidata and Scholia. I was looking at the 1979 chemistry Nobel laureate Georg Wittig, and Scholia lists him as having no publications. See Georg Wittig and Wittig reaction. Is there some way to expand profiles of important scientists like this, and important general topics? Is there a tool to allow us to (say) important all the citations from the corresponding WIkipedia articles? Thanks, Walkerma (talk) 19:47, 10 November 2019 (UTC)

@Walkerma: I just ran a batch for him, and more can be done based on his "missing" page. We have WD:SourceMD and WD:Fatameh for imports, but both are not really usable right now, so the best option for starting an item based on a DOI, PMID or PMCID is the old SourceMD, which sits here. --Daniel Mietchen (talk) 17:28, 11 November 2019 (UTC)
Thanks a lot Daniel! I'll give it a go this weekend. Walkerma (talk) 04:10, 16 November 2019 (UTC)

Wikidata weekly summary #390

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Speedpatrolling is a tool to easily patrol Wikidata recent changes, typically on mobile devices.
  • Development
    • In order to decrease the size of what we store in caches we stopped storing the actual EntityUsage objects in ParserOutput and now just store minimal identifier strings (phabricator:T236749)
    • Investigated why Termbox broke on an update (phabricator:T235261)
    • Removed auto jump of focus from Property field to value field (phabricator:T234322 - thanks to Envlh for the patch)
    • Removed non-functional site link groups for other Wikibase installations that don't need them (phabricator:T232248)
    • Continued working on the migration of the wb_terms table to address scalability issues
    • Continued working on the shortened version of edit summaries for edits made through the mobile termbox (phabricator:T224013)
    • For the Wikidata Bridge we are not showing edit pens when the user can not edit the article anymore (phabricator:T235152)
    • Working on viewing existing references in the Wikidata Bridge (phabricator:T233397)
    • Worked on showing an information popup when clicking the tainted reference icon to tell you what went wrong and how to solve it.
    • Worked on defining first version of Federation for wikis outside Wikimedia
    • Commons search have stopped indexing statements (structured data) since 30 October 2019 (phabricator:T237849)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

SourceMD batch cleanup

Latest comment: 4 years ago1 comment1 person in discussion

If you're not already aware there are paper corrections imported via sourcemd that are only being imported as "Correction:" when the remainder of the title is in italics. Example: 10.1136/bcr-2018-224213corr1 - Q58770311. This issue is reported in sourcemd as issue 7, but this means there are a handful of DOIs that will need to be rerun from various previous batches or manual fix.Wolfgang8741 (talk) 09:51, 17 November 2019 (UTC)

wrong heuristic

Latest comment: 4 years ago4 comments3 people in discussion

Please STOP using "title" as heuristic for references. The right item would be inferred from title (Q69652283). Thank you. --SCIdude (talk) 16:07, 18 November 2019 (UTC)

OK, will do. inferred from title (Q69652283) makes more sense indeed but it wasn't around when I started doing this, and I followed the recommendations from back then. What are your plans in this space? --Daniel Mietchen (talk) 21:50, 18 November 2019 (UTC)
Nothing specific, just pragmatism like yesterday I created inferred from abstract (Q75484171) because I needed it. Earlier I used TCDB BLAST (Q69893291) extensively. I am certain that with enough items of this type someone will write a paper with a classification. --SCIdude (talk) 06:38, 19 November 2019 (UTC)
I've used this heuristic as a reference. Will you mass replace or should I try to find all the instances where I've used it? Trilotat (talk) 22:05, 19 November 2019 (UTC)

Bad extraction

Latest comment: 4 years ago5 comments4 people in discussion

Hi there can you check this item review of Egypt and Africa. Joyce Tyldesley. Chronicle of the Queens of Egypt from Early Dynastic Times to the Death of Cleopatra (Q58890343) and the ones immediately before and after it? I think they are badly extracted sections of text from a Review article and should not be individual items. Thanks. -- Fuzheado (talk) 17:46, 18 November 2019 (UTC)

Looks like those titles are aberrant in the respective journal too. Pinging User:Richard Nevell who might know more. --Daniel Mietchen (talk) 21:54, 18 November 2019 (UTC)
Hi folks. With that particular item, the whole title from the publisher would be Egypt and Africa - Joyce Tyldesley. Chronicle of the Queens of Egypt from Early Dynastic Times to the Death of Cleopatra. 224 pages, 273 b&w & colour illustrations. 2006. London: Thames & Hudson; 978-0-500-05145-0 hardback £19.95. - Charlotte Booth. People of Ancient Egypt. 290 pages, 75 illustrations, 25 colour plates. 2006.Stroud: Tempus; 0-7524-3927-8 hardback £20. - Stephanie Moser. Wondrous curiosities: Ancient Egypt at the British Museum. xvi+328 pages, 89 illustrations, 13 colour plates. 2006. Chicago & London: University of Chicago Press; 978-226¬54209-6 hardback. - Jean-Luc Chappaz (ed.) with Nora Ferrero, Sandra Deglon, Delphine Petro & Marie Vandenbeusch. Kerma et archéologie nubienne.60 pages, 69 b&w & colour illustrations. 2006. Geneva: Musée d’artet d’histoiredeGenève/Infolio; 978-2¬8306-0234-0 & 978-2-88474-128-6 paperback. - Graham Connah. Forgotten Africa: an introduction to its archaeology. xiv+194 pages, 67 illustrations. 2004. Abingdon & New York: Routledge; 0-415-30590-X hardback £60; 0-415-30591-8 paperback £18.99. - Saul Dubow. A Commonwealth of Knowledge: Science, Sensibility, and White South Africa 1820-2000. xii+296 pages, 11 illustrations. 2006. Oxford: Oxford University Press; 978-0-19-929663-7 hardback £60.
That's a bit of a mouthful, and more than Wikidata can cope with, so the tool truncates it. Richard Nevell (talk) 23:14, 18 November 2019 (UTC)
I modified it to end in "..." to indicate incompleteness. --Daniel Mietchen (talk) 22:29, 19 November 2019 (UTC)
I took the liberty of further truncating the title, moving Daniel's edited title to the "also known as" field, and I hope appropriately, I added the entirety of the remaining "mouthful" into the subtitle field. Also listed it as British English. Trilotat (talk) 20:59, 22 November 2019 (UTC)

Wikidata weekly summary #391

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Recap of WikidataCon and WikiConference North America, 19 November. Agenda
  • Tool of the week
    • The Mix'n'Match gadget displays on an item all unconfirmed matches on Mix'n'match, allowing to quickly add them.
  • Development
    • Tainted references: Show warning icon if statement value is changed but reference is not changed in the same edit (phab:T231728)
    • Make WikibaseQualityConstraints link using SpecialMyLanguage (phab:T233003)
    • Work on the issue of property labels not showing up on some pages (phab:T237984)
    • Track Bridge openings by property datatype (phab:T231204)
    • Viewing existing references in the Bridge (phab:T233397)
    • Attaching the link listener sooner, so the user gets a bit less often wrongly forwarded to wikidata (phab:T235765)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #392

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Cradle enables editors to create a new item by completing a form. You can create a new form on the Cradle help page. Cradle forms can be used as templates to ensure that similar new items are structured the same way. This can be especially helpful for specific WikiProjects or datathons, and is a great timesaver if you are creating many similar items by hand.
  • Other Noteworthy Stuff
    • 570k VIAF identifiers have been added to Wikidata items in an effort of synchronisation between the two databases, thanks to Bargioni. In order to report errors in VIAF an apposite page has been created. More information here.
    • Query Service lag now affects maxlag. You may need to retry/reset error multiple times when you run QuickStatement or OpenRefine in busy hours.
    • Wikidata now documented more than six million people, more than the number of articles in English Wikipedia
    • New documentation page: Wikidata:Map data
  • Development
    • Add Wikidata query service lag to Wikidata maxlag (phab:T221774)
    • More work on tainted references and getting the feature ready to be tested
    • Fix a bug with Wikibase test builds (phab:T238575)
    • More work on improving the edit summaries (phab:T224013)
    • Bridge: Viewing existing references (phab:T233397)
    • Preserving native behavior on key+click (phab:T234060)
    • Speeding up initialization, by attaching link listeners sooner (phab:T235765) and reducing the size of the init module (phab:T235771)
    • Recording metrics for bridge opening performance (phab:T237368)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


WikiCite Satellite 2020 Keynote?

Latest comment: 4 years ago2 comments1 person in discussion

Hey Daniel,

hast du meine Email (8.11.)mit der Anfrage, ob du eine Key-Note bei der WikCite Satellite am 6.-8. Mai in Köln halten möchtest bekommen? Es wäre toll, wenn du dort zum Beispiel was zu Scholia sagen würdest. Gerne kann das aber auch eine adere Metareflexion sein. Meld dich doch, ob wir mit dir rechen können - oder auch nicht.

Herzliche Grüße! Eva

@EvaSeidlmayer: Sorry, hab ich noch nicht gesehen. Ich guck mal nach. --Daniel Mietchen (talk) 18:03, 28 November 2019 (UTC)
OK, hab gerade "Ja, gern" geantwortet. --Daniel Mietchen (talk) 18:08, 28 November 2019 (UTC)

Thanks

Latest comment: 4 years ago1 comment1 person in discussion

Hi, I see you work a lot on the lexemes. Thanks!--So9q (talk) 10:25, 1 December 2019 (UTC)

Wikidata weekly summary #393

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Gadgets, 3 December. Agenda
  • Tool of the week
    • Alt Labels displays item labels in other languages when there is no label in your default language. You may click a label to add it as the label for your language. This tool is very helpful for labels for people, books, articles, or films that do not need their labels to be translated.
  • Development
    • Fix security issues impacting the Query Service GUI (more details)
    • Work on a a new Parser function (commaSeparatedList) (phab:T224013)
    • Implement Shortened version for edit summary (phab:T224013)
    • Add user agent to Wikidata Query UI code examples (phab:T226709)
    • Add label and description collision detectors for new terms store (phab:T232040)
    • Wikidata Bridge: showing a loading bar during initialization (phab:T232468)
    • Showing an error dialog if users can’t edit on Wikidata (phab:T235154)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Thomas Koschny

Latest comment: 4 years ago6 comments3 people in discussion

Hello Daniel!

Who is Q63005302? Some information would be helpful, otherwise I suggest the record for deletion.

Greetings, --HarryNº2 (talk) 14:24, 5 December 2019 (UTC)

I think it's premature to delete. A number of articles link to the author. I presume he is this person [6]. Trilotat (talk) 15:27, 5 December 2019 (UTC)
@HarryNº2, Trilotat: Thanks, both, for checking. I added what I could, largely based on the link given above. Always good to check for links and what the Scholia profile says. --Daniel Mietchen (talk) 16:34, 5 December 2019 (UTC)
I followed up with some additional articles from results at [7]. I'll try to disambiguate, but I am not familiar with this author or their field of work. Trilotat (talk) 16:47, 5 December 2019 (UTC)
Thanks! Turns out that all the publications with author name string (P2093) equal to the label or aliases of Thomas Koschny (Q63005302) were actually by the same person, so no need to disambiguate them further unless new publications come in. However, curation of their co-authors, the topics of the publications etc. is still most welcome. --Daniel Mietchen (talk) 21:48, 5 December 2019 (UTC)
Seems your activity has led this item to appear on the Current Highlights section of the main page. Well done! Trilotat (talk) 19:53, 6 December 2019 (UTC)

Wikidata weekly summary #394

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • overpass: Embeds a map displaying features tagged with the current item in OpenStreetMap. Powered by overpass turbo. It helps check if the Wikidata object is mapped in OSM and also if it's correct.
  • Other Noteworthy Stuff
  • Development
    • Implement Shortened version for edit summary (phab:T224013)
    • Add monolingual language code WLS (Wallisian) (phab:T239411)
    • DumpRDF for MediaInfo entities loads each page individually (phab:T222497)
    • Add user agent to Wikidata Query UI code examples (phab:T226709)
    • Wikidata Bridge: Showing a loading bar during initialization (phab:T232468)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Summary #395

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Recoin displays information about the relative completeness of a Wikidata item by comparing its statements with those found on other similar items. Especially useful for editors working in a knowledge area that is new to them.
  • Development
    • Work on deploying the first version of tainted references on test Wikidata
    • Bridge: show an error dialog if users can’t edit on the repo wiki (phab:T235154)
    • Set up a shared Vue component library for Wikibase (phab:T240329)
    • More work on the new term store
    • Add Wikidata support for mnwwiki" (phab:T235745)
    • New languages for monolingual strings: mfa, ckt, abq-Latn, dag
    • Help identifying an issue with QuickStatements when one user is blocked on Wikidata (phab:T240316)
    • Hide non-supported languages in the termbox (phab:T227083)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Ontology Evaluation with SPARQL

Latest comment: 4 years ago1 comment1 person in discussion

Dear Sir,

I thank you for your support. We have sent our research unit application and will shortly know about the final decision. Concerning ontology evaluation with SPARQL, we are working as you already know on developing queries to assess the usage of relation types in Wikidata. Today, I have sent you an updated edition of the work. I ask if you can write "Wikidata as a collaborative ontology: An overview" and "SPARQL in a nutshell" parts and review the work for us. Please reply me soon. --Csisc (talk) 21:37, 29 December 2019 (UTC)

Wikidata weekly summary #396

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last 2 weeks.
  • Tool of the week
    • The revised version of the very powerful PetScan offers to edit or create items based on Wikipedia categories, search, SPARQL, links with filters by label or properties
  • Development
    • Worked on better error dialogues for the Wikidata Bridge
    • Investigated and fixed labels for some Properties not being shown (phabricator:T237984)
    • Continued working on the new database tables that replace wb_terms
    • Expanded documentation for 3rd party Wikibase installs
    • Continued working on making sure components in different areas of Wikibase can easily be shared to make development easier (phabricator:T240329)
    • Enjoying the holidays. Hope so are you :)

WikiProject India Newsletter #2

Latest comment: 4 years ago1 comment1 person in discussion
 

Hi Daniel Mietchen/Archive,

Happy New Year for those who are living in UTC+05:30 (Q6828) (in advance or belated for the rest!). You are receiving this message as you are one of the participants of WikiProject India on Wikidata and/or a subscriber of the Wikidata India newsletter. You can find our second issue of the quarterly newsletter here, where you can get a quick overview of the Wikidata activities related to India over the last 3 months. If you do not want to receive this kind of notification further, you can remove your username from here.

Regards,
MediaWiki message delivery (talk) 18:46, 31 December 2019 (UTC)
(on behalf of WikiProject India on Wikidata.)

Wikidata weekly summary #397

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Resolver allows you to quickly find an item based on a property+value string pair. It is especially useful for checking whether an external identifier such as a VIAF ID (P214) or Getty AAT ID (P1014) is already in use in Wikidata.

Wikidata weekly summary #398

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Tabernacle creates a tabular view of a set of data items from a SPARQL query, PagePile list, or manual list of items. You can select which languages and properties to display. The tool lets you drag-and-drop statements from one item to another, and manually add or edit statements without leaving the page. Tabernacle is great for harmonizing a set of related items or identifying items that need their labels and descriptions translated.
  • Development
    • More work on finishing the migration of wb_terms table
    • Don’t check constraints on “Wikidata property example for media” statements (phab:T227865)
    • Warn users that they're not nogged-in before performing restore or undo (phab:T234430, thanks to Matěj Suchánek)
    • Remove edit link from Special:NewPages if page is not directly editable (phab:T240561, thanks to Matěj Suchánek)
    • Introduce MwEraParser and improve i18n of dates BCE (phab:T140541, thanks to Matěj Suchánek)
    • Bridge: show error dialog if the user isn't allowed to edit Wikidata (phab:T235154)
    • Bridge: ask the user if the change is a fix or an update (phab:T237333)
    • Enabled tainted references on test.wikidata.org

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #399

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Other Noteworthy Stuff
    • New gadget added to Preferences, "Show UnpatrolledEdits" (see discussion): it shows if the last edit to the item has not been patrolled
    • Pywikibot deprecates Python 2 support. Any scripts running via Python 2 should be migrated soon, see more at [8]
    • The next Weekly Summary (January 27) will be the issue #400. Please help us collecting interesting Wikidata-related facts around the number 400!
  • Development
    • More work on wb_terms table migration: information about property terms is no longer updated and removed from wb_terms table.
    • Add "wikibase-statementsection-identifiers i18n message key to Wikibase (phab:T240356)
    • Stop using $wgUser in Wikibase (phab:T241947)
    • Document possible configuration options for Wikibase Repository and Wikibase Client installations (phab:T165973)
    • Document Wikibase Usage Aspects (phab:T236772)
    • Document Wikibase tables (phab:T124603)
    • Wikidata Bridge: add the RadioButton to the component library (phab:T239799)
    • Showing error dialogs if users can’t edit on the repo wiki (phab:T235154)
    • Tainted references: work on keeping the warning visible when users cancel an edit

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #400

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Duplicate Item copies the current item (without descriptions or sitelinks) to a new item. This tool is useful for splitting items and for making sets of similar items. Recommended for experienced users.
  • Development
    • More work on wb_terms migration
    • Units support for quantity datatype (phab:T239474)
    • Fix the link to rawgraphs.io from WDQS (phab:T222257)
    • More work on showing messages related to permissions on the Wikidata Bridge
    • Tainted references: fix minor alignment issues (phab:T243269, phab:T242212)
    • Add a "remove warning" button to confirm a correct reference (phab:T234789)
    • Preparing the ground for a unified component library for the Wikidata UI

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #401

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
  • Tool of the week
    • VizQuery allows you to use the Wikidata Query Service without having to know SPARQL. Simply use a couple of autocomplete input boxes and you can do most basic queries.
  • Development
    • Enable the first version of tainted/mismatched references on wikidata.org
    • Work on adding a button to hide the notification (phab:T234789)
    • Show the icon after canceling editing if the icon was shown before (phab:T234790)
    • More work on Wikidata Bridge (restrict editing based on user rights or data types)
    • More work on wb_terms migration

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Open infectious disease guide

Latest comment: 4 years ago3 comments2 people in discussion

Hey there! I'm a physician and researcher at the University of Cologne. Yesterday I had a conversation with Jens Ohlig from Wikimedia Germany about a project I am working on. Supported and partly funded by the German Society for infectious diseases we are creating an open platform (based on mediawiki and hopefully wikidata) with information on how to diagnose and treat the most prevalent infectious diseases. We call it 'infektiopedia'. Jens recommended talking to you :) Currently most of our documents are in German so I cannot share much at this point but happy to have a call and talk about the project. --Max.schons (talk) 09:43, 6 February 2020 (UTC)

Hi Max, happy to talk. I'll send you an email with my contact details. --Daniel Mietchen (talk) 11:11, 6 February 2020 (UTC)
Email sent. --Daniel Mietchen (talk) 11:18, 6 February 2020 (UTC)

Wikidata weekly summary #402

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Reasonator offers a visual formatted display of Wikidata information. It is useful for introducing Wikidata to new audiences and can help find missing or incorrect data by presenting a different view than the standard editing interface.
  • Development
    • Wikidata Bridge: more work on enabling error messages for various cases (datatype not supported, user can't edit on client or repo, etc.)
    • Including the property label in the title of the Data Bridge dialog (phab:T233295)
    • Mismatched references: follow-up of the deployment in production, adding the "remove warning" button
    • Monitoring the number of times the feature reference warnings are being triggered and opened (phab:T231731)
    • Fixing some issues connected to the train deployment
    • Fixing an issue with new edit summaries not being displayed on client wikis (phab:T244129)
    • Fixing an issue with ittem having label conflict with itself (phab:T243158)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #403

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Looking for one of the 7000+ Wikidata properties? Try Propbrowse to search and browse all properties.
  • Development
    • Wikidata Bridge: more work on unsupported edit cases (unsupported datatypes phab:T235753, ambiguous statements phab:T240212, deprecated statements phab:T238660, unknown value or no value statements phab:T242747)
    • Including the property label in the title of the Data Bridge dialog (phab:T233295)
    • Making the edit based on the user's fixed/updated choice (phab:T238662)
    • Style fixes and font size adjustments (phab:T239421, phab:T243192)
    • Create Grafana boards to track the results of the tainted references feature
    • Increase factor for query service that is taken into account for maxlag (later reverted) (phab:T244722)
    • Fix edit summaries not displayed on client wikis (phab:T244129)
    • Fixed some issues causes by the wb_terms migration

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #404

Latest comment: 4 years ago1 comment1 person in discussion
 
404 - newsletter not found
  • Development
    • Provide better redirect for statement nodes (phab:T203397)
    • Wikidata Bridge: style fixes and font size adjustments (phab:T239421, phab:T243192)
    • making the edit based on the user's fixed/updated choice (phab:T238662)
    • research how to do reference rendering (phab:T244987)
    • showing the loading bar while saving (phab:T237433)
    • More work on wb_terms table and fixing various issues
    • Removing all of pre-entity source based federation code
    • Fixing various issues causing errors in production
    • Investigate on an issue with pasting exact Commons file title (phab:T196165)
    • Update the APIs to specify an errorformat and a uselang parameter (phab:T242769)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Main subject through MAG FOS

Latest comment: 4 years ago2 comments2 people in discussion

HI Daniel, I saw through the Quick Statements logs that you are adding main subject props Property:P921 to academic publications.

It might be of interest to you that I am currently adding Microsoft Academic's Fields of Study. It is a semi-automatically constructed hierarchy of 220K Topics, extracted from Wikipedia to which they map all the articles in their knowledge graph. See [[9]]

Given that they use Wikipedia, the mapping to Wikidata is straightforward and the MAG ID's are currently being added to the corresponding items. For example, "carbon naonotubes" carbon nanotube (Q1778729) is currently a subject of 180K publications [on MAG]. So long story short, maybe there is a more optimal and thorough way to categorize the publications you are interested in.

Drop me a message if you want to discuss it further. Cheers!


Nikola Tulechki (talk) 07:03, 29 February 2020 (UTC)

@Nikola Tulechki: Благодаря, Никола. Да, щастлив да обсъдим това допълнително. Маппинг е полезно, но лицензът им предотвратява по-нататъшното интегриране. --Daniel Mietchen (talk) 15:29, 29 February 2020 (UTC)

Wikidata weekly summary #405

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Other Noteworthy Stuff
  • Development
    • Started working on Federated Properties for Wikibase
    • Bridge: more style adjustments
    • Research on reference rendering for the Bridge (phab:T244987)
    • Disable WDQS jump to focus when used in an iframe (phab:T245637)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #406

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • WikiGap Challenge, online editing challenge to improve the coverage of women on Wikipedia and Wikidata, from March 8th to April 8th
  • Development
    • Querying the URL datatype with haswbstatement is now possible (phab:T243693). It will take two to three months before URLs are indexed for all Wikidata items.
    • Wikidata Bridge: more style fixes, preparing a prototype to show how we will display references
    • Fixing various production errors
    • Monitoring the run of wb_terms migration
    • Fixing an issue with the Commons files search field (phab:T196165)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Would you like to contribute to a WikiProject COVID-19 ?

Latest comment: 4 years ago6 comments2 people in discussion

Hello,

I am a big fan of your contributions to Wikidata, via the WikiProject Zika Corpus, Scholia, and much more. I was wondering if you would be interested in helping to create a Wikidata WikiProject COVID-19.

The goals would be initially (of course, they can be changed):

create a data model for instances of disease outbreak (Q3241045).

monitor the quality of the pages about national outbreaks listed in 2019–20 COVID-19 outbreak by country and territory (Q83741704).

curate the wikidata items relevant for describing the outbreaks and the virus itself.

curate and improve the information on Wikidata about scientific articles regarding the coronavirus (similar to the Wikidata:WikiProject_Zika_Corpus).

think and develop ways to process these items to improve access to information (for example, via automated articles in languages that currently do not have pages about country-specific outbreaks).

Would you like to participate in this effort?

I am trying to gather the Wikidata editors actively involved in the topic.I believe that if we act together, we can have a shot at aiding the global effort in containing the pandemic.

Thanks!

TiagoLubiana (talk) 00:26, 16 March 2020 (UTC)

@TiagoLubiana: Based on experience with Wikidata:WikiProject Medicine, Wikidata:WikiProject Zika Corpus and Wikidata:WikiProject Humanitarian Wikidata, I think a separate WikiProject for COVID-19 is not necessarily the best way to handle this on the Wikidata end. My preference would be for a COVID-19 Task Force under the umbrella of the Medicine or Humanitarian Wikiproject (or perhaps both — with the former focusing on the medical aspects, the latter on socioeconomics, logistics and such). In any case, I am working on the topic already and shall be very happy to join forces with others who are similarly engaged! --Daniel Mietchen (talk) 00:46, 16 March 2020 (UTC)
@Daniel Mietchen: Thanks for the quick response! I trust your preferences, sounds like a great solution. I like the idea of the Humanitarian part, but I feel that two pages could be a bit too confusing, and I do not know if it is possible to have a task force as a subpart of two projects. What do you think about a https://www.wikidata.org/wiki/Wikidata:WikiProject_Medicine/COVID-19_Task_Force? Are there any steps I should take before starting a page about such a task force? Thank you! TiagoLubiana (talk) 00:58, 16 March 2020 (UTC)
@TiagoLubiana: That sounds like a good place to get things going. We can sort out the syncing with the Humanitarian pages and similar resources later. --Daniel Mietchen (talk) 01:36, 16 March 2020 (UTC)
@Daniel Mietchen: In the meanwhile, a different user created a WikiProject (Wikidata:WikiProject_COVID-19). I started putting content there, but already opened in the the talk page a discussion about moving it to a task force page. TiagoLubiana (talk) 01:39, 16 March 2020 (UTC)
Thanks — I commented there. --Daniel Mietchen (talk) 01:45, 16 March 2020 (UTC)

Wikidata weekly summary #407

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development
    • Add monolingual codes nrf-gg (Guernésiais), nrf-je (Jèrriais), thanks to Mbch331! (phab:T165648)
    • Article Placeholder: make the entity field required (phab:T247478)
    • Remove legacy Wikibase service containers (phab:T245865)
    • Fix an error UnresolvedEntityRedirectException when viewing certain Wikidata item pages (phab:T243779)
    • Fix an issue with new edit summaries not always showing what expected (phab:T246873)
    • Federated properties: enable search with remote properties (wbsearchentities) (phab:T246349)
    • showing the updated Wikipedia article after changing a value via Bridge (phab:T235208)
    • research how to do reference rendering (phab:T244987)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Corpus of COVID-19 articles

Latest comment: 4 years ago2 comments2 people in discussion

Hello again,

I am thinking about how to organize the curation of the articles related to COVID-19 within the scope of the WikiProject COVID-19. The goal would be similar to the Zika Corpus project, but on a smaller scale, at least at first. Any tips on where to start? Thanks again! TiagoLubiana (talk) 23:22, 16 March 2020 (UTC)

@TiagoLubiana: I see Scholia profiles (e.g. for the SARS-CoV-2 virus, for the COVID-19 disease, for the COVID-19 pandemic, for the transmission of the virus or for social distancing) as good starting points to curate scholarly articles and perhaps news on the topic, as mentioned yesterday. For Wikipedia articles, I am hoping for a Wikidata version of Template:COVID-19 pandemic (Q83761248). In a longer term, I am also thinking about an outbreak aspect for Scholia, but that would mean we get a decent data model for outbreaks first. --Daniel Mietchen (talk) 02:00, 17 March 2020 (UTC)

Research Bot

Latest comment: 4 years ago2 comments2 people in discussion

Can you stop Research Bot replacing 'scientific article published on 1st January 1970' to just 'scientific article' in the item descriptions like it did here

Thanks Nintendofan885T&Cs apply 10:48, 23 March 2020 (UTC)

@Nintendofan885: Thanks for checking. As you can see from its contributions, that day was the last day it made an edit. --Daniel Mietchen (talk) 13:24, 23 March 2020 (UTC)

Wikidata weekly summary #408

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Wikidata Lexeme Forms allows quickly generating a new lexeme with all its forms in selected languages; you can also use the tool to add forms to an existing lexeme, or bulk upload many lexemes and forms at once.
  • Development

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

SAR

Latest comment: 4 years ago2 comments2 people in discussion

You have added main subject (P921) based on its title, but for example in Metallic electrodes and leads in simultaneous EEG-MRI: specific absorption rate (SAR) simulation studies. (Q51682249) "SAR" means "specific absorption rate".--GZWDer (talk) 23:57, 27 March 2020 (UTC)

Yes, thanks for checking. Should be clear now. --Daniel Mietchen (talk) 00:33, 28 March 2020 (UTC)

Wikidata weekly summary #409

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • IdentifierInput: when adding identifiers, it lets you paste the full URL, and extracts the ID part
  • Development
    • Fix an issue with the Wikidata dumps (phab:T248612)
    • Migrate to and read from new store for item terms (phab:T219123)
    • Create wb_terms_no_longer_updated to ease the transition to the new tables
    • Bridge: improve the rendering of references (phab:T238661)
    • More work on editing references (phab:T240333)
    • Continue setting up a test system to work on federated properties
    • More research on suggesting references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

WikiProject India Newsletter #3

Latest comment: 4 years ago1 comment1 person in discussion
 

Hi Daniel Mietchen/Archive,

You are receiving this message as you are one of the participants of WikiProject India on Wikidata and/or a subscriber of the Wikidata India newsletter. You can find our third issue of the quarterly newsletter here, where you can get a quick overview of the Wikidata activities related to India over the last 3 months. If you do not want to receive this kind of notification further, you can remove your username from here.

Regards, Bodhisattwa (CIS-A2K) and Mahir256
(on behalf of WikiProject India)
Sent through MediaWiki message delivery (talk) 18:35, 31 March 2020 (UTC)

Citation metrics in Scholia

Latest comment: 4 years ago7 comments2 people in discussion

Dear Sir,

As I stated in a previous email, Scholia does not support citation metrics for scientists, papers and institutions. However, such metrics (such as the number of citations) are important to give an overview of the citation activity of the analyzed scholarly entity. That is why I ask if we can integrate SPARQL queries computing citation metrics for a scientist. I already adapted some of the Scholia queries for that:

I am still working on a query to generate the h-index and even the g-index of a scientist. I am also working to apply these metrics on other types of entities.

Yours Sincerely,

--Csisc (talk) 20:53, 2 April 2020 (UTC) Csisc (talk) 21:23, 2 April 2020 (UTC)

Hi Csisc, the main reason we have not highlighted citation information in Scholia as much is that it is very incomplete, and almost entirely missing for the last two years. Do you have any plans to bring in citation information at scale, e.g. from Open Citations? I checked all four of your example queries, and they all look fine, so feel free to open tickets and pull requests for them in our GitHub repo. --Daniel Mietchen (talk) 21:56, 2 April 2020 (UTC)
Yes, we studied various options to mass upload citations to Wikidata. The first option is to use OpenCitations. However, we can miss many citations with this option. This is just what is currently happening in Wikidata. The second option is the use of Net Scraping. As you already know, this technique can be used to directly retrieve references from the websites of publishers. However, there is a legal concern about this method. But, before dealing with citations, we found another problem in Scholia. The problem is the static data about affiliations. Most of the affiliations of included scientists are not explained in details. What we propose is to involve scholarly affiliations as qualifiers to authors' list of each publication. An example of how to do that can be https://www.wikidata.org/wiki/Q68471881. Such simple data can be easily found for each publication and can be used later to infer the changes of affiliations of scientists over years. Concerning h-index, the problem is that LIMIT in SPARQL does not support variables. What I propose is to create i20-index and i40-index using the same method as i10-index. Like this, we will have the same information about citation patterns as the h-index. I ask about your opinion of that. --Csisc (talk) 22:20, 2 April 2020 (UTC)
@Csisc: You touch on a number of problems here, and they tend not to have short answers, but I'll try nonetheless:
  • Ad citations:
    • OpenCitations is a natural starting point. Their materials are compatibly licensed and machine readable, and the communities know each other. Yes, their corpus is incomplete, but at this point, we do not know whether Wikidata would be able to handle a scholarly citation graph that is anywhere near completeness, so starting with a smaller set (which is still hundreds of millions and thus a multiple of what we have right now) would seem more reasonable than going for anything more comprehensive.
    • We want to avoid legal trouble, so are staying away from any grey areas, and including netscraped data (except from sites under CC0/ public domain) is thus not an option. Scraping has non-legal issues as well (e.g. entity recognition, especially in multilingual contexts) but could be useful in a number of ways, particularly for quality control and for finding suitable references for unsourced Wikidata statements. For instance, I could imagine a scraping-based tool that flags issues with information in Wikidata, e.g. missing (or inconsistent, incomplete, unreferenced) publications, authors, author orders, affiliations, citations, keywords, journals, publication dates, identifiers etc. Scholia could then use such information either directly, i.e. by displaying information from the tool (similar to how Wembedder is integrated) or indirectly, i.e. by linking to the tool (similar to how the Author Disambiguator is integrated), and either on the profile page itself or on the corresponding /missing page.
  • Ad affiliations:
    • We are currently lumping together information regarding things like employer (P108), educated at (P69), member of (P463) and affiliation (P1416), and we do not distinguish much between current and past values, in part because all of these properties (and their qualifiers) are still sparsely populated, but also in part because the impact of an organization is not limited to whoever is on staff now. Yes, once the data becomes more complete, we could tease out these details more.
    • When mining affiliation data, largely the same comments as above apply: it may be very useful for sites that are licensed compatibly with Wikidata, but for anything else (i.e. the vast majority of potential sites to mine), the main value would be as a basis for quality control, primarily by flagging inconsistencies and gaps that can then guide further curation on Wikidata.
    • Yes, it would be very useful to have affiliation data at a per-publication granularity (as in your example Wikidata: A large-scale collaborative ontological medical database (Q68471881)), and we could harvest that in principle for more fine-grained Scholia queries, but the way the Wikidata Query Service (Q20950365) query time-out works does not usually allow such granularity to be harvested on the scale of, say, institutional profiles. It should usually (except perhaps for publications with thousands of authors) work on work profiles, and it may be displayed in panels like the one for most recent or earliest publications on a topic.
    • Yes, we are very much aware of many of the limits of the WDQS, and as per Wikidata:WikiProject Scholia/Robustifying, we are actively exploring what can be done about them. As for variable with LIMITS, we could try to use ASK queries before SELECT queries to address that (see ticket for that).
  • Ad metrics:
    • I am not too keen on replicating flawed metrics like impact factor (Q5330) or h-index (Q310663), but yes, there is value in being able to reproduce these metrics based on open data, and we hint at that, for instance, with the "As function of number of published works" panel in the Citations section of a publisher profile (example), which essentially replicates the JIF.
    • In the long run, I think Scholia can help establish new and more sensible metrics. One that I like is the number of statements supported by a given work, and once that is more populated (as per above, mining could be very useful for that!), we could show variants of it on profiles for authors, institutions, topics etc. But any single measure is likely to be gamed once it becomes a measure, so we should also look at more systemic indicators that are harder to game, and the way Scholia is set up allows to explore such things rather flexibly in principle, albeit within the limits of the query service.
--Daniel Mietchen (talk) 00:35, 3 April 2020 (UTC)
Interesting ideas. I will see how we can directly integrate OpenCitations into Wikidata. Concerning citation metrics, I will open a ticket about the queries in GitHub. After that, we will definitely see what we can do. --Csisc (talk) 11:56, 3 April 2020 (UTC)
  Done. Added four tickets to https://github.com/fnielsen/scholia/issues. Concerning editorial delay, we can add editorial dates for research publications using web scraping of PubMed Central Database. I can add a ticket about that if you like it. Csisc (talk) 16:17, 3 April 2020 (UTC)
Just an update concerning what we have discussed about Scholia, I raise these points:
  • I ask if you can adapt the citation metrics I involved in https://github.com/fnielsen/scholia/issues/1097 and include them in a pull request. I can adapt them to other types of entities like journals, publications and prizes.
  • We can include DOI to DOI references of OpenCitations. However, the CSV dump is currently 106 GB as shown at https://opencitations.net/download#coci. Unfortunately, we do not have the means to store data in a local server. The only solution can be the use of Wikimedia Cloud Services.
  • I ask if you can adapt and include the scholarly networks of single publications as available at https://github.com/fnielsen/scholia/issues/1100 in a pull request.
Yours Sincerely,
--Csisc (talk) 21:06, 7 April 2020 (UTC)

Wikimedians for Sustainable Development - March Newsletter

Latest comment: 4 years ago1 comment1 person in discussion
This is our fourth newsletter, covering March 2020. This issue has news related to SDGs 3 and 11.

Becoming a User Group

  • Wikimedians for Sustainable Development are recognized as a Wikimedia user Group [5]

In the news

  • Wikipedia is flooded with information — but it has a blind spot (SDG 11) [1]

New WikiProjects

  • Wikidata:WikiProject COVID-19 (SDG 3) [9]
  • (Arabic) ويكيبيديا:مشروع ويكي طب/فريق عمل كوفيد-19 (SDG 3) [10]
  • (Czech) Wikipedie:WikiProjekt SARS-CoV-2 (SDG 3) [11]
  • (English) Wikipedia:WikiProject COVID-19 (SDG 3) [12]

Academic studies

  • Uneven Coverage of Natural Disasters in Wikipedia: the Case of Floods (SDG 11) [2]

Events

  • The COVID-19 pandemic halts all in-person events funded through the Wikimedia Foundation (SDG 3) [6]
    • Which lead to a renewed interest in remote events (SDG 17) [8]

Information from the Wikimedia Foundation

  • COVID-19 (SDG 3) [20]

The Sustainable Development Goals

  • The United Nations adopt changes to the Sustainable Development Goal Indicators (SDG-all) [7]

New Wikidata properties

  • GreatSchools ID (SDG 4) [4]
  • food energy (SDG 1) [14]
  • number of recoveries (SDG 3) [15]
  • number of clinical tests (SDG 3) [16]

New Wikidata example queries

  • Updated chart of the number of infections and deaths caused since the outbreak of SARS-CoV-2, as reported by the World Health Organisation (SDG 3) [3]
  • World map of hospitals (SDG 3) [13]
  • Notable people with COVID-19 by number of sitelinks (SDG 3) [17]
  • COVID-19 case statistics for India (SDG 3):
    • State-level map [18]
    • State-level line graph [19]

Links

This message was sent with Global message delivery by Ainali (talk) 20:57, 3 April 2020 (UTC) • Contribute • Unsubscribe

Wikidata weekly summary #410

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Scholia highlights the scholarly data in Wikidata, including scholarly works, projects, topics, and individual researchers, including their relationships and statistics. It encourages further enrichment of Wikidata through links on the "missing" pages.
  • Development
    • Working on a first prototype for automated finding references (board)
    • Bridge: improve rendering of references (phab:T238661)
    • Only send incremental changes through the API (phab:T230343)
    • Adding a screen allowing people to go edit the references on Wikidata (phab:T240333)
    • Reducing the size of the extra Javascript that the user has to download for Bridge (phab:T228857)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #411

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • COVID19 Dashboard is a Wikidata-powered one-stop information/visualization service for COVID19-related topics such as COVID19's outbreak map, deaths, symptoms, taxonomy, and publications.
  • Development
    • Move wb_terms data in cloud replicas to wb_terms_no_longer_updated (phab:T248592)
    • Rebuild wb_items_per_site, after incident where wb_items_per_site was dropped (phab:T249596)
    • Purge / Reject client pages that were cached in parser cache during the incident (phab:T249595)
    • More work on Automated finding references
    • More work on federated properties: create and save a statement with federated properties
    • Bridge: improve the generic error screen (phab:T241126) and on save (phab:T248087)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Updates about our work

Latest comment: 4 years ago2 comments2 people in discussion

Dear Sir,

I have the honour to inform you about these updates:

  • Our paper about ontological validation of Wikidata has received a positive decision from CSCW Journal. We have to provide significant adjustments to the paper and send it again for review. I have send you an email a few hours ago about the matter. Please see it and reply me very soon.
  • Concerning Scholia, we have organized meetings about this Wikidata tool and developed a report about it. Please find the report at https://commons.wikimedia.org/wiki/File:Wikimedia_TN_-_Robustifying_Scholia,_A_viewpoint.pdf.
  • We have added support of COVID-19 status in Tunisia to Wikidata. We think of writing a research paper about that. If this work is interesting for you, I can send you further details about what we have done.

Yours Sincerely,

--Csisc (talk) 14:53, 18 April 2020 (UTC)

@Csisc: Sorry, saw this only now.
  • Re CSCW, I had already replied via email.
  • Re your report, thanks for this detailed analysis! As previously discussed, the issues you raise fall into several categories:
    • some (e.g. coverage of citations, affiliations and email addresses) are a matter where we need to engage the Wikidata / WikiCite community, rather than decide them on our own — this is especially important for things like the citations, since their scale (billions if we strive for comprehensiveness of any sort) is reaching the limits of Wikidata (speaking of which, your contributions to WikiProject Limits of Wikidata would be much appreciated).
    • some are things that enhance Scholia's functionality but not within the Scholia team's current priorities, since these revolve around figuring out how to deal with the fact that existing functionality already hits bespoke Wikidata limits on a regular basis, e.g. as per this GitHub project and these on-wiki notes.
    • some are things that we already work on, e.g. a country-level citation graph per topic.
  • Re COVID, yes, happy to collaborate, as discussed in the call on Monday.
--Daniel Mietchen (talk) 23:28, 25 April 2020 (UTC)

Needs assessment for Wikidata Movement Resource

Latest comment: 4 years ago1 comment1 person in discussion
 

Hi Daniel Mietchen/Archive,

CIS-A2K is planning to invest some resources from May-June 2020 to create community movement resource (CMR) materials in English and different Indic languages for Wikidata in the form of tutorials, handbooks, infographics, videos, animations etc. The aim of this initiative is to build a pool of resource materials for Wikidata eventually, which will serve as ready-made handy references for new as well as experienced users. You are requested to fill up this form, so that we can understand your needs on different topics of Wikidata. You are also very welcome to actively participate in the process and help us build the CMR with your different areas of expertise.

You are receiving this message as you are one of the participants of WikiProject India. If you do not want to receive this kind of notification further, you can remove your username from here.

Regards, Bodhisattwa (CIS-A2K)
Wikidata Advisor, CIS-A2K
Sent through MediaWiki message delivery (talk) 06:05, 20 April 2020 (UTC)

Wikidata weekly summary #412

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Ordia generates statistics from Wikidata lexeme information, and through the "Text to Lexemes" feature allows linking a document to the associated lexemes, and highlighting missing lexemes that can be added.
  • Development
    • Prototyping week: the Wikidata team at Wikimedia Germany spent one week working on some quick experiements. The projects developed during this week are not necessarily going to be added to the maintained codebase. Among those projects:
      • try to use GraphQL for the API providing access to Wikibase/Wikidata data
      • allow to programmatically access different configuration variables of a Wikibase instance to make it easier for tools to built on top of it
      • investigate ranking for Items to order them by their relevance in a query result
      • com up with a workflows for editing statements linking to other Items in the Wikidata Bridge
      • identify how to improve Wikidata's accessibility
      • create design system components to continue improving consistency

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

About publishing a letter in Lancet Infectious Diseases

Latest comment: 4 years ago3 comments2 people in discussion

Dear Sir,

I have recently seen that there are several dashboards and datasets related to COVID-19 that were published in Lancet Infectious Diseases. An example of this research items are An interactive web-based dashboard to track COVID-19 in real time (Q87456354) and Open access epidemiological data from the COVID-19 outbreak (Q89000034). I think that not publishing an item about WikiProject COVID-19 will be a waste. Correspondence items for this journal are 400 words length and only involve five references. I ask if you agree on writing with us a correspondence letter about WikiProject COVID-19 in Wikidata. Please reply me soon.

Yours Sincerely,

--Csisc (talk) 12:59, 25 April 2020 (UTC)

@Csisc: I shall be most happy to join in on writings around COVID-19 (I just did so this week), but I signed The Cost of Knowledge (Q1340139) and will thus not publish with Elsevier journals. --Daniel Mietchen (talk) 00:27, 26 April 2020 (UTC)
I thank you for your answer. I understand your concern with Elsevier. We are writing two other papers to be sent to ISWC. One of these papers is about adding support of COVID-19 datasets to Wikidata. We will be honoured if you join us. Concerning Scholia, I know that some of the points I raised are more linked to WikiProject Source Metadata and to WikiProject WikiCite. You can take your time which points are to consider by Scholia Project. However, from what we have seen, there are many SPARQL queries that can be built to ameliorate the output of scholarly profiles on Scholia. What I think is that Scholia does not have only to generate a brief report about scholarly items but also to discuss the output by automatically comparing it with other close profiles. This is what I have called a living scientometric study. This means a research evaluation study that is updated in real time and that involves a critical discussion of its output. Concerning scholarly databases support, I have recently attended BIR Workshop and I presented there Wikidata and Scholia Project as a part of a brief discussion. People there gave me a list of CC0 databases that can be used as a reference for scholarly information in Wikidata. I can give the full list to you if you like that. The fact of having high-scale bibliographical databases to integrate to Wikidata was easier than we have thought. Concerning SPARQL, we need to work on the paper next week so that we can resend it to CSCW journal soon. I will send you an email by Tuesday morning to inform you what we have to do. --Csisc (talk) 02:52, 26 April 2020 (UTC)

Wikidata weekly summary #413

Latest comment: 4 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • zotkat's exporter for Zotero (a software to manage bibliographic data) allows you to export bibliographies to the QuickStatements format. It is helpful to easily create bibliographical entries, especially as Zotero can read metadata about works from dozens of other websites, and can thus be used as intermediary.
  • Development
    • More work on error screens for the Bridge
    • Use updated data for the Bridge (phab:T240223)
    • Display statements made with federated properties on item pages (phab:T246606)
    • Automated references: normalizing data that the extractor gets out of HTML pages (phab:T249004)
    • Create a distributed game so people can vet references easily (phab:T248997)
    • Cleanup rows from wb_items_per_site (phab:T249613)
    • Don't suggest initial uppercase in mobile termbox (phab:T241978)
    • Have the focus on field when adding new element on Sense (phab:T203461)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikimedians for Sustainable Development - April Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our fifth newsletter, covering April 2020. This issue has news related to SDGs 3, 6, 9, 10, 11, 13, 14 and 15..


News

  • GLAM Newsletter Special report on COVID-19 (SDG 3) [1]
  • Wikidata and the bibliography of life in the time of coronavirus (SDG 3) [7]
  • Video: Wikidata Lab XXII - Wikiprojeto COVID-19 (SDG 3) [20]
  • How Wikipedia is Covering the Coronavirus Pandemic (SDG 3) [21]
  • Open data and COVID-19: Wikipedia as an informational resource during the pandemic (SDG 3) [23]
  • Using CC Licenses and Tools to Share and Preserve Cultural Heritage in the Face of Climate Change (SDG 11) [25]
  • Video: Mapping against COVID-19 (SDG 3) [26]
  • Student-created immunology content on Wikipedia receiving a lot of attention this month (SDG 3) [34]
  • How Wikipedia shows disability matters (SDG 10) [35]

Tools

  • COVID-19 dashboard (SDG 3) [2]
  • COVID-19 dashboard for Tunisia (SDG 3) [22]

In the news

  • Why Wikipedia Is Immune to Coronavirus (SDG 3) [3]

Research

  • Why and how medical schools, peer-reviewed journals, and research funders should promote Wikipedia editing (SDG 3) [4]
  • A protocol for adding knowledge to Wikidata, a case report (SDG 3) [5]
  • Multilingual enrichment of disease biomedical ontologies (SDG 3) [6]

New Wikidata properties

  • FHF establishment ID (SDG 3) [8]
  • FHF hospital group ID (SDG 3) [9]
  • Spanish National Catalog of Hospitals ID (SDG 3) [10]
  • Forest Stewardship Council Certificate Code (SDG 9) [24]
  • Forest Stewardship Council License Code (SDG 9) [27]
  • Psocodea Species File ID (SDG 15) [28]
  • Swedish Glaciers ID (SDG 13) [29]

New Wikidata query examples

  • Infectious diseases and their number of cases (SDG 3) [11]
  • The longest river that feeds into another river (SDG 6 & 14) [30]
  • Longest rivers that do not feed into a sea or ocean (SDG 6 & 14) [31]
  • Recently published works on COVID-19 (SDG 3) [32]
  • Welsh hospitals, health centres, doctors surgeries and temporary Covid19 hospitals (SDG 3) [33]

New Wikidata schema examples

  • pandemic (E184) (SDG 3) [12]
  • hospital (E187) (SDG 3) [13]
  • 2020 coronavirus pandemic local outbreaks (E188) (SDG 3) [14]
  • clinical trial (E189) (SDG 3) [15]
  • Lockdown (E190) (SDG 3) [16]
  • lockdown part of the 2019-2020 coronavirus disease pandemic (E191) (SDG 3) [17]
  • virus taxon (E192) (SDG 3) [18]
  • contact tracing app (E195) (SDG 3) [19]

Links

This message was sent with Global message delivery by Ainali (talk) 18:58, 1 May 2020 (UTC) • Contribute • Unsubscribe

Wikidata weekly summary #414

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Competition for the International Museum Day is about improving data about museums in Austria, France, Germany, Italy and Switzerland on Wikidata, from 3 May 2020 to 18 May 2020, more information on Museum Day 2020/Wikidata Competition
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Alex Jung on Wikidata and Wikipedia Infoboxes, 05 May. Agenda
    • Upcoming: live SPARQL queries in French by Vigneron, Tuesday May 5 at 20:00 CEST (UTC+2)
  • Tool of the week
    • ProWD explores completeness for entities and classes.
  • Other Noteworthy Stuff
    • MachtSinn, a tool that allows you to easily add Senses to Lexemes, has lately been improved significantly
    • 33,000 values of British Museum person or institution ID (d:Property:P1711) now have a useful target again. After their being mostly inoperative for several years, the new British Museum website now has information pages matching these values, with links to related objects. (Example). To work around bug T112081, a script by Andrew Gray is going through the items making null edits to update the relevant URLs.
    • Outdated copy of wb_terms has been dropped on April 29th
  • Development
    • Add monolingual language codes rm-rumgr, rm-surmiran, rm-sursilv, rm-sutsilv, rm-vallader, rm-puter (phab:T222426)
    • More work on the test system for federated properties
    • More work on displaying statements with federated properties (phab:T246606)
    • Bridge: more work on generic error screens (phab:T241126)
    • Bridge: warn the user that they are about to edit anonymously (phab:T246676)
    • Work on a Wikidata distributed game for automated finding of references
    • Automated finding references: build a scraper, simple value matching, item analyzer
    • Have the focus on field when adding new element on Sense (phab:T203461)
    • Add more properties to the PageImages list (phab:T249811)
    • Use strict types everywhere in Wikibase (phab:T251382)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

WM Hackathon

Latest comment: 3 years ago1 comment1 person in discussion

Hello, Daniel,

I'm trying to gather the covid-19 related info happening on the WM Hackathon at Wikidata:WikiProject_COVID-19/Status_updates/Wikimedia_Hackathon_2020

If you have some tips on how to shape these updates, or want to add something there, it would be great!

Thanks,

Best,

TiagoLubiana (talk) 13:16, 9 May 2020 (UTC)

Wikidata weekly summary #415

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Press, articles, blog posts, videos
    • Webinar introducing Wikidata and adding wikidata=* tags into OpenStreetMap objects for OpenStreetMap contributors in the Philippines (in English and Tagalog): YouTube
    • Wikidata Course at TAU: Hosting Mark Graham from the Internet Archive
      • Part 1 - Meet the Archive: YouTube
      • Part 2 - The IA & Wikimedia: YouTube
    • Wikidata Course at TAU: Hosting Lydia Pintscher from Wikimedia Deutschland
      • Part 1 - Wikidata - current state: YouTube
      • Part 2 - Wikibase & Lexemes: YouTube
      • Part 3 - Shape Expressions & Schemas: YouTube
    • How to create external identifiers on Wikidata (in Italian): YouTube
    • Open Data and Wikidata training (in Mandarin Chinese): YouTube
    • Bandaid: using Wikidata to generate band names
  • Tool of the week
    • WikidataExtract extracts schemas (shape expressions) from Wikidata entities
  • Development
    • Display statements with federated properties (phab:T246606)
    • Federated properties: fix a bug that caused some properties to not appear in search results (phab:T252024)
    • Wikidata Bridge: more work on error messages
    • Prevent Wikibase schema updaters to modify database directly (phab:T249598)
    • Write a technical RFC about site-wide edit rate limiting (phab:T247459)
    • Fix an issue on Wikibase: property names are missing when rendering (phab:T247196)
    • More work on automated references

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Not Available

Latest comment: 3 years ago3 comments3 people in discussion

Hi! In MARIE C. STOPES (Q28761166), you asserted that the title of this article was "[Not Available]", which I believe to be a false claim. I invite you to participate in cleaning up this, and any other cases. Cheers, Bovlb (talk) 19:57, 11 May 2020 (UTC)

@Bovlb: Thanks for checking. The claim is supported by the indicated source, but I just deprecated that and added the actual title. Not sure yet how best to reference that, but there are more of these, so I have added this to my maintenance queries. --Daniel Mietchen (talk) 23:21, 11 May 2020 (UTC)
I looked a bit closer so I could disambiguate the author and found this is actually an obituary for MARIE C. STOPES, not an article by her. I changed the title to reflect her name. Trilotat (talk) 22:32, 16 May 2020 (UTC)

Please don't add content-free entities

Latest comment: 3 years ago2 comments2 people in discussion

I don't understand the point of adding something like Roy Herbst (Q89006575) which consists of nothing more than a name. Without any disambiguating information or strong identifiers, it's completely worthless and confuses reconciliation processes which are attempting to find a valid Wikidata entity. I ran across some older ones today and dismissed them as artifacts of obsolete processes, but this one was created just a couple of months ago. Is there some benefit that I'm missing here? Why do they never contain references to the data source that caused them to be created? Tfmorris1 (talk) 21:29, 12 May 2020 (UTC)

@Tfmorris1: Thanks for taking a look and sharing your observation. The bit that you are missing is that while an item may itself be bare-bone, this does not automatically mean that it is "content-free", nor useless in reconciliation processes. We are talking linked open data (Q18692990) here — information about entities is not just stored on their pages but also by way of links to and from them. This item is linked from various other items, as per the corresponding WhatLinksHere. Specifically, those other items have author (P50) statements, on the basis of which we can construct a WD:Scholia profile for the author, which you can access, e.g., via the icon in Roy S. Herbst (Q89006575)  . Such profiles can in turn assist in enriching the author's item, e.g. via Stress hormones promote EGFR inhibitor resistance in NSCLC: Implications for combinations with β-blockers. (Q47423597), I found affiliation information that I added, and from there, I quickly found more bits and pieces. --Daniel Mietchen (talk) 06:21, 15 May 2020 (UTC)

Indian scientists datathon

Latest comment: 3 years ago1 comment1 person in discussion
 

Hi Daniel Mietchen/Archive,

You are receiving this message as you are one of the participants of WikiProject India on Wikidata and/or a subscriber of the Wikidata India newsletter.

Hope you and your loved ones are safe and sound during this ongoing COVID-19 pandemic situation.

This is for your kind information that, from 22nd May, 2020 Friday to 24th May, 2020 Sunday, a datathon will be happening on Indian scientists on Wikidata. The lack of data about Indian scientists, their works and publications on Wikidata is the reason behind conducting the datathon. Considering the ongoing pandemic, the datathon will also focus on scientists working on SARS-CoV-2 and COVID-19.

The tasklist of the datathon is flexible. Participants can choose their own preferred task on this topic

Hoping for your active participation.

Take care and stay safe,

Bodhisattwa (CIS-A2K)
Sent through MediaWiki message delivery (talk) 06:12, 17 May 2020 (UTC)

Call Wikiproject COVID-19 tomorrow (Monday, May 18th)

Latest comment: 3 years ago1 comment1 person in discussion

Hello, Daniel,

How are you doing?

I can imagine you have been busy, but I am here to invite you for the Wikiproject COVID-19 call tomorrow (Monday, May 18th). If you are able to meet, the call (in this link: https://meet.google.com/vtp-ighz-npx) will happen tomorrow at 15:00 UT.

As a note, 15:00 UTC is:

  • 11:00 AM in New York, USA
  • 12:00 AM in São Paulo, Brazil
  • 4:00 PM in Tunisia
  • 6:00 PM Eastern European Summer Time (EEST)

If you want, also feel free to add topics at the meeting page.

Thanks!

Cheers, TiagoLubiana (talk) 23:40, 17 May 2020 (UTC)

Wikidata weekly summary #416

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • WikidataTrust.jsP updates the interface with the contributors to each statement, label, description and sitelink. It is similar to the “blame” tool on text-based wikis.
  • Development
    • In the query service, variable names with non-“Latin” characters (e. g. ?fiancé, ?π) can now be used more easily. (T227952)
    • Wikidata Bridge: more work on error messages and warnings (phab:T246676, phab:T247250, phab:T244361)
    • Federated properties: display statements made with deleted properties (phab:T250785)
    • More work on fixing error messages on Wikidata's edit interface (phab:T247690)
    • Form grammatical features: connect labels and inputs (phab:T198703)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


User:Research_Bot and QuickStatements

Latest comment: 3 years ago3 comments2 people in discussion

Hey Daniel Mietchen, can you please reduce the number of parallel QuickStatement batches that you execute with User:Research_Bot? It goes at ~300 edits/min (maxlag<5) and ~60/min (maxlag>5). Unfortunately, our server capacities are limited and other users do want to use their fair share as well. QuickStatement unfortunately does not throttle properly while maxlag>5, and in general values such as 300/min are undesirable anyways. Thanks, —MisterSynergy (talk) 20:48, 20 May 2020 (UTC)

@MisterSynergy: I am using QuickStatement in background mode, in which the user submits batches into a queue, and the tool then decides which batches from the queue to execute and when. So do you want me to limit the number of batches I have in the queue? If so, to what number? Right now, three batches are running, but I have dozens in the queue (no simple way to know how many, though I am keeping tabs on the range to check). Also pinging Magnus for comment. --Daniel Mietchen (talk) 00:57, 21 May 2020 (UTC)
With currently three active batches (per QS batches list) you are going at ~200 edits/min, which is already a pretty high value considering that the servers tend to overload at values of 600–1000 edits/min for all users+bots. I would recommend to ensure that not more than 3 batches run actively at the same time. I am not sure whether Magnus sees this ping, as his notification indicators are usually saturated at 99+ :-) —MisterSynergy (talk) 08:08, 21 May 2020 (UTC)

Wikidata weekly summary #417

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.

This is the Wikidata summary of the week before 2020-05-25.

  • Tool of the week
    • If you're looking for even more tools, the Tools Directory indexes over 130 Wikidata tools.
  • Development
    • Federated properties: Linking to the source wiki immediately after saving a statement (phab:T251776)
    • Properly display federated properties on a local item's Revision History page (phab:T249836)
    • Documentation for federated properties (phab:T252991, phab:T252861)
    • Last steps of getting the distributed game "Reference hunt" ready
    • Wikidata Bridge: more work on error messages
    • Track errors people encounter when using the Bridge (phab:T252683)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Main subject

Latest comment: 3 years ago2 comments2 people in discussion

Hi Daniel, thanks for the work you've been doing adding subjects to publications. Most of my editing is around the humanities, but I have noticed a couple of odds tags in other areas. For instance, Thirteen Reasons Why: The impact of suicide portrayal on adolescents' mental health (Q58593607) has its main subject (P921) given as veteran suicide (Q45382729). It looks like a lot of the publications with that main subject (P921) may be suited to a more general topic. What do you think? Richard Nevell (talk) 11:05, 27 May 2020 (UTC)

@Richard Nevell: Sorry, saw that only now. Thanks for checking. Yes, that tagging seems not ideal. I put that edit batch on my to do list for review. --Daniel Mietchen (talk) 10:24, 24 July 2020 (UTC)

Wikiproject COVID-19 call tomorrow (1st of June) - reminder

Latest comment: 3 years ago1 comment1 person in discussion

Hello, Daniel,

How are you doing?

I have been doing some work trying to organize properties related to peer reviewed articles; maybe this page will be of your interest: Wikidata:WikiProject_COVID-19/Data_models/Peer-reviewed_articles

This is a friendly reminder of tomorrow's (Monday, 01 of June) Wikiproject meeting, at 15:00 UTC as usual, and at the usual link: https://meet.google.com/vtp-ighz-npx .

If you want to add something to the agenda in advance, feel free to just edit Wikidata:WikiProject_COVID-19/Project_meeting.

I hope you can make it! :)

Best,

TiagoLubiana (talk) 20:39, 31 May 2020 (UTC)

Wikidata weekly summary #418

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • wdumps allows you to create a limited RDF dump from Wikidata, for those times when your SPARQL queries keep timing out. It is not particularly user-friendly, and it typically takes several hours to get a complete dump, but it is the best way to for example get a list of all English names of humans in Wikidata, or a list of every scientific article with its title and DOI.
  • Other Noteworthy Stuff
    • The former WikiProject iNaturalist was renamed WikiProject Biodiversity to allow discussions beyond iNaturalist.
    • Special:FewestRevisions to be disabled, if you are currently using it, please leave a comment
    • Winners of the Wikidata competition during Museum Day 2020: VIGNERON, Alexmar983, Braveheart, Pasleim, Benoît Prieur, Uli.ch, Nono314, Sukkoria and Airon90. Congratulations!
    • As part of a thesis project, the search engine "Lister" has been developed to make it easier for the general public to access data on the Semantic Web in general, and WikiData specifically. It's in a usability test-phase right now, and if you'd like to try it out and help improve it, you can do so at this link. The test should at most 15 minutes.
    • Follow the discussion about restricting editing of properties to autoconfirmed users.
    • New domain toolforge.org to be adopted by our Toolforge community. New domain/scheme for Toolforge-hosted webservices will change from tools.wmflabs.org/toolname to toolname.toolforge.org with the aim to introduce permanent redirects for the legacy URLs on 2020-06-15.
    • Wikidata development team is currently running a survey until June 9th to understand better how people access and reuse Wikidata’s data from the code of their applications and tools (for example through APIs), and how we can improve the tools to make your workflows easier. If you would like to participate, please use this link (Google Forms, estimated fill-in time 5min).
  • Development
    • More documentation for federated properties
    • Properly display federated properties on a local item's Revision History page (phab:T249836)
    • More improvements on the Wikidata Bridge
    • Add Wikidata support for awawiki (phab:T252870)
    • Fix various bugs on Wikibase
    • Work on improving the unclear error messages (phab:T247690)
    • Create reports for the reference hunt game

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikimedians for Sustainable Development - May Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our sixth newsletter, covering May 2020. This issue has news related to SDGs 3, 4, 5, 15 and 16.

Meetings

  • Next meeting for Wikimedians for Sustainable Development is Sunday, 7 June 18.00-19.00 UTC (SDG-all) [17]

News

  • Wikimedia and COVID-19: April overview (SDG 3) [1]
  • Extract Knowledge from Wikidata to Wikipedia articles related to Coronavirus (SDG 3) [8]
  • How Wikipedia became a trusted source for COVID-19 information (SDG 3) [15]
  • Future Historians Will Rely on Wikipedia’s COVID-19 Coverage (SDG 3) [16]
  • Students document workplace health risks on Wikipedia amidst global pandemic (SDG 3) [18]

New Wikidata properties

  • COVIDWHO ID (SDG 3) [2]
  • DGHS facility code (SDG 3) [3]
  • DPVweb ID (SDG 15) [4]
  • RPPS ID (SDG 3) [5]
  • hardiness of plant (SDG 15) [9]
  • hardiness zone (SDG 15) [10]
  • voting system (SDG 16) [11]
  • DPE school code (SDG 4) [12]

New Wikidata query examples

  • Map of countries receiving the Nobel peace prize (SDG 16) [6]
  • Map of geolocated Argentine libraries (SDG 4) [7]
  • Map of hospitals (blue) and health centers (green) of Argentina (SDG 3) [13]
  • Map of National parks in Sweden (SDG 15) [14]
  • Universities ranked by PageRank on English Wikipedia (SDG 4) [19]

New Wiki projects

  • Wikidata:WikiProject Schools (SDG 4) [20]
  • Swedish Wikipedia: Projekt HBTQI (SDG 5) [21]

Links

This message was sent with Global message delivery by Ainali (talk) 16:39, 1 June 2020 (UTC) • Contribute • Unsubscribe

Keywords as main subjects

Latest comment: 3 years ago3 comments2 people in discussion

These are really quite awkward, and I think another property, rather than main subject (P921), is justified. A keyword/index term is actually of string type: if a link is used, then a change of label means the original term is lost. I certainly see numerous cases where there are main subject originating from keywords that are incorrectly disambiguated.

I'm using a qualifier to tag such main subjects, at present. What do you think?

Charles Matthews (talk) 13:44, 5 June 2020 (UTC)

@Charles Matthews: Sorry, saw that only now. We could perhaps use object named as (P1932) as an additional qualifier on main subject (P921) statements. --Daniel Mietchen (talk) 10:20, 24 July 2020 (UTC)

Not so urgent. I'm using now both "object has role" and "named as" qualifiers: object named as (P1932) is probably an improvement on "named as".

In the main subject (P921) statements, there are now imports from NIOSH and GOA release 2020-03-11 (Q96105165), for example, as well as PubMed, so the situation is becoming complicated. My main concern is clarity in sourcing.

That is all on the article items. The clinical trial items potentially have the same issues, and something interesting could be done there.

I am concentrating on further MeSH information now, as a general way forward on main subjects.

Charles Matthews (talk) 10:37, 24 July 2020 (UTC)

Wikidata weekly summary #419

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • QuickStatements lets you edit thousands of Wikidata items at a time. Add labels and descriptions, or statements with sources and qualifiers, add sitelinks, create or merge items, or remove statements that were created in error. Batches can be discussed and, if necessary, reverted in full through the EditGroups tool.
  • Development
    • Wikidata Bridge: Made a number of technical improvements to wrap up the work in the first version.
    • Reference Hunt: Making final technical improvements and are now running the process to find references on the whole of Wikidata (as opposed to the initial small subset for testing). Once that's done we'll release them as a dump.
    • Easier access to data for programmers: Researching and interviewing ways to improve the APIs in preparation for working on them.
    • Query builder: Working on defining the first version and creating mockups based on the feedback we received.
    • Use modern TypeScript syntax (3.2 -> 3.9) (phab:T253211)
    • More technical documentation for Federated Properties (phab:T252991) & preparing for the next steps
    • Convert some properties to external identifiers (phab:T253722)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Reminder of the WikiProject COVID-19 call tomorrow (15 of June)

Latest comment: 3 years ago1 comment1 person in discussion

Hello Daniel,

I hope you are doing well there.

I know you have been tremendously busy, butI am here to send you this friendly a reminder of tomorrow (15 of june) call at 15:00 UTC!

This is the link for the call: https://meet.google.com/vtp-ighz-npx

This is the link for the etherpad: https://etherpad.wikimedia.org/p/wikidata_covid_notes

The WikiProject seems to be losing momentum. Perception of the size of COVID-19 as an enormous problem is fading. That is good, but it is also dangerous.

In tomorrow's call, I would like to discuss with you two important and related questions: - How can this WikiProject best serve the anti-covid-19 effort? - what does this project can offer for the post-COVID-19 Wikidata world?

As usual, if you have any topics to add, you can do so either before at the Project Meeting Page or at the meeting.

I hope you can make it!

All the best,

Tiago TiagoLubiana (talk) 23:58, 14 June 2020 (UTC)

Wikidata weekly summary #420

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Mix'n'match lets you match lists of external identifiers to Wikidata items, or create new items if necessary. Thousands of catalogs already exist, in dozens of different topic areas, and it's easy to import new ones.
  • Development
    • Collecting a lot of feedback and doing research around how to improve our APIs to start making it easier to access Wikidata's data for programmers
    • Finalized the initial feature list for the query builder and working on designs and prototypes for testing
    • Doing user research on the Merge gadget to prepare for making it part of the proper code-base so that other Wikibase instances also benefit from easier merging
    • Federated Properties: continued working on the first version of Federation that will make it possible to use Wikidata's Properties in another Wikibase installation
    • Start of a new project (Wikibase Decoupling & Extension Registration) in order to clean up our codebase a bit and make it easier to extend with new features in the future
    • More work on the design system to have a set of unified components for Wikidata that will make it easier to develop new features in the future because we don't have to rewrite components that are used in a lot of places
    • Some MediaWiki skin changes meant broken edit links on Wikipedia and co. Fixed now. (phabricator:T252800)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Proposition of « parent language » property

Latest comment: 3 years ago1 comment1 person in discussion

Hello, I see you on Wikidata:WikiProject Linguistics. I’m french wiktionarian who want to work on languages on Wikidata. After testing some properties, I decided to propose a new propety « parent language » to link langagues as natural thing (not like construct thing with based on (P144)). I would like to have your opinion on the issue. Thanks ! Lyokoï (talk) 21:26, 19 June 2020 (UTC)

Wikidata weekly summary #421

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • The currentDate gadget automatically adds the current date when using retrieved in a reference.
  • Development
    • Continue working on the infrastructure review, in order to address the most pressing infrastructure issues
    • Make the Wikibase.git code base PSR-4 compatible (phab:T172368)
    • Work on an overview of existing types of coupling in Wikibase between Repo and Client (phab:T254902)
    • More work on consistency of UX components
    • Handle failed requests to the federation source wiki when saving statements (phab:T254889)
    • Catch federated properties exceptions in getParserOutput and display error page (phab:T255010)
    • Improve the permissions for Blazegraph in wdqs docker image (phab:T237248)
    • Create entitySources config for WMF production wikis (phab:T254315)
    • Participate in fixing several incidents (phab:T255855, phab:T255410)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Bibliography of Wikidata

Latest comment: 3 years ago1 comment1 person in discussion

Hi Daniel,

Thanks for editing the Wikidata:Bibliography of Wikidata page! I think to avoid it getting outdated it could have the full automatically generated list that you linked under the chronological section. Could you please edit that into the article? It could still have a featured articles section where we can put the most important publications. Also, could you add an author column to the list? Thanks!

Best, Adam Harangozó (talk) 19:33, 22 June 2020 (UTC)

Wikidata weekly summary #422

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Other Noteworthy Stuff
    • Wikibase Live sessions is coming back with the first call about Data Modeling in the context of Libraries happening on Thursday, July 2nd at 1600 UTC.
  • Development
    • It is now possible to search for EntitySchema pages using a shortcut “E:”, similar to “P:” for Properties and “L:” for Lexemes. For example: E:E10 or E:kakapo. T245529
    • Continued working on the first version of Federation, which will allow other Wikibase installations to use Wikidata's Properties - getting closer to a first testable version
    • More work on consistency of user interface components
    • Finalizing the click-dummy for the first version of the Query Builder so we can start testing it with some editors soon and get feedback.
    • Continuing to investigate how to improve our APIs and other ways to improve access to the data in Wikidata for programmers
    • Discussed the future of the Wikidata Query Service and ideas for next steps we can take to make it scale better. Guillaume will join the next office hour to talk about it.
    • More work on clearer separation of Wikibase repository and Wikibase client code in order to improve maintainability

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

WikiProject India Newsletter #4

Latest comment: 3 years ago1 comment1 person in discussion
 

Hi Daniel Mietchen/Archive,

You are receiving this message as you are one of the participants of WikiProject India on Wikidata and/or a subscriber of the Wikidata India newsletter. You can find our fourth issue of the quarterly newsletter here, where you can get a quick overview of the Wikidata activities related to India over the last 3 months. If you do not want to receive this kind of notification further, you can remove your username from here.

Regards, Bodhisattwa (CIS-A2K) and Mahir256
(on behalf of WikiProject India)
Sent through MediaWiki message delivery (talk) 18:34, 30 June 2020 (UTC)

Wikimedians for Sustainable Development - June Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our seventh newsletter, covering June 2020. This issue has news related to SDGs 3, 4, 5, 8, 10, 16 and 17.

Meetings

  • Upcoming: 5 July, Wikimedians for Sustainable Development online meeting (SDG 17) [12]
  • Upcoming: 18 July, Wikimedians for Sustainable Development online meeting (SDG 17) [12]
  • Past: 7 June, Wikimedians for Sustainable Development online meeting (SDG 17) [13]

News

  • Webinar: COVID-19 and human rights: How to share the facts on Wikipedia (SDG 3) [1]
  • Vad menas egentligen med öppenhet? (Swedish) (SDG 4) [2]
  • How Wikipedia Has Responded to the George Floyd Protests (SDG 10) [3]
  • 50 000 kvinnor på svenskspråkiga Wikipedia! (Swedish) (SDG 5) [4]

Videos

  • COVID & health topics on Wikidata (SDG 3) [9]

New Wikidata properties

  • curriculum topics (SDG 4) [5]
  • ISCO-08 occupation code (SDG 8) [6]
  • FEMA number (SDG 2) [7]
  • Democracy Index (SDG 16) [10]

New Wikidata query examples

  • Species of birds (SDG 15) [8]
  • Wikidata Queries around the SARS-CoV-2 virus and pandemic (SDG 3) [11]

Links

This message was sent with Global message delivery by Ainali (talk) 20:50, 2 July 2020 (UTC) • Contribute • Unsubscribe

Wikidata weekly summary #423

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Ptable displays the periodic table automatically extracted from information provided by Wikidata; it also provides a check that all the elements are there with some basic properties. Additional pages provide charts of the nuclides under different criteria such as half-life. Each element or nuclide is linked to its Wikidata item for more information or to edit if necessary.
  • Development
    • More work on the consistent design system (Phabricator board)
    • More work on decoupling the different Wikibase extensions from each other
    • Polishing the first step of Federation (using Wikidata's Properties in another Wikibase installation) (incl. preventing users from selecting a federated property with a non-supported data type (phab:T252012) and preventing users from accessing Special:NewProperty when federation is enabled (phab:T255576) and viewing a list of all properties when federation is enabled (phab:T246339))
    • Continuing research and interviews around the topic of making it easier to access Wikidata's data for programmers
    • Doing first testing of mockups and prototypes of the first version of the Query Builder - coding can start soon
    • Convert a few properties from string to external identifier: Linguasphere code (P1396), KOATUU identifier (P1077) and ISIN (P946)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #424

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: New co-facilitator introductions and tools for editathons, 14 July. Agenda
    • Upcoming video: Wikipedia Weekly Network - LIVE Wikidata editing #12, 18 July Facebook, YouTube
    • Past: Celtic Knot Wikimedia language conference, online, July 9-10. Videos, documentation and slides of sessions are accessible from the program page.
  • Tool of the week
    • DragNDrop.js makes it possible to show a Wikipedia article and drag items to Wikidata.
  • Development
    • Continued building out documentation for Federated Properties (phabricator:T255651) and making interface improvements to the first stage of the feature (incl. phabricator:T246886, changes to special pages that interact with both Items/Properties, and phabricator:T255581, changes to Special:ListDataTypes when federation is enabled)
    • More work on the consistent design system
    • More work on decoupling the different Wikibase extensions from each other to make development easier
    • Finalizing research and interviews to better understand what could be improved in the way developers access Wikidata's data (APIs, SPARQL)
    • Testing the first prototype of the Simple Query Builder with some editors to get final input before coding starts
    • Sorting of language links on Wikipedia and the other Wikimedia projects was broken (presumably by a change in MediaWiki core). A fix is being worked on. (phabricator:T257625)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

wrong main subject

Latest comment: 3 years ago2 comments2 people in discussion

Hello Daniel, your bot appears to take "novel human coronavirus EMC" (e.g. Q36872701) and interpret it at SARS (I fixed already). But EMC is an early name for MERS. --SCIdude (talk) 16:55, 14 July 2020 (UTC)

@SCIdude: Thanks for checking. I took another look at Cell host response to infection with novel human coronavirus EMC predicts potential antivirals and important differences with SARS coronavirus (Q36872701) and do not think that "novel human coronavirus EMC" was interpreted as SARS — SARS was in the title too, and I fixed your fix. --Daniel Mietchen (talk) 10:16, 24 July 2020 (UTC)

Wikidata weekly summary #425

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: The First Wikidata Workshop: Second Call for Papers. Papers due: August 10, 2020 | Workshop date: October 29, 2020
    • Upcoming: next Wikidata office hour, July 21st at 16:00 UTC (18:00 CEST) in the Wikidata Telegram group. Query Service special with guests from WMF Search Team.
    • Upcoming: Wikidata Lab XXIV: Posicionamento digital relativo with Ederporto - July 23 17:00 UTC (14:00 BRT). In this technical training, we'll study the possibilities and functionalities of relative digital positioning in images and do practical activities on this topic using historical photographs of the city of São Paulo. The event will be held in Portuguese. Join us!
    • Upcoming video: July 21 - Wikipedia Weekly Network - Entity Schemas and Shape Expressions (ShEx) Facebook YouTube
    • Upcoming video: July 25 - Wikipedia Weekly Network - LIVE Wikidata editing #13 Facebook YouTube
    • Upcoming: Kidok-Workshop, online workshop about church building data. In German, non-native users welcome. Currently looking for a date in the upcoming week and people to help!
    • Upcoming video: Beyond Wikipedia - Knowledge that even a computer can understand. July 22, 2020 at 17:00 UTC. In this talk, Zbyszko Papierski will present Wikidata Query Service as one way that developers can interact with Wikidata.
  • Development
    • More work on the consistent design system
    • More work on decoupling the different Wikibase extensions from each other to make development easier:
    • Prepare the first development phase for the Simple Query Builder
    • Reference game: run a scraper, work on a dashboard that will gives an overview of the potential references that have already been judged in the game
    • Fix a bug related to maximum limit of search results (phab:T256885)
    • Resolve some configuration issues regarding Entity Sources (phab:T254315)
    • Federated Properties:
      • Changes to special pages that interact with both items/properties when federation is enabled (phab:T246886)
      • Changes to Special:ListDatatypes when federation is enabled (phab:T255581)
    • Add new monolingual language codes: mic (Miꞌkmaq), gil (Kiribati)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Ideas about Using ADS Bibcode

Latest comment: 3 years ago1 comment1 person in discussion

I think it would be useful if one could enter an ADS bibcode (P819) to the Source Metadata tool (at https://sourcemd.toolforge.org/index_old.php) and have it generate an item based on the DOI (or return a "Other sources with these identifiers exist" response and add the ADS Bibcode to the item). This would add to the brilliant work it already does when a PMID/DOI/PMCID is entered.

Not sure how to take it to the next step, but cites work (P2860) could benefit from ADS Bibcode. Using Aftershock asymmetry on a bimaterial interface (Q58196207) as an example, the citation and reference pages noted below could be the reference url when adding the item to cites work.

I have no idea where to go with this suggestion. I presume it might be something for Magnus Manske, but I'm not savvy enough to propose it well. Trilotat (talk) 21:17, 25 July 2020 (UTC)

Wikidata weekly summary #426

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • We would love suggestions for tools to include in this section of the weekly summary. Please add your suggestions directly under Status updates/Next#Backlog after checking that the tool isn't already listed.
  • Development
    • Changed the size of image previews to 1024 in the gallery view of the query service to avoid some images not loading sometimes (phabricator:T258241)
    • Added an actual space between the entity title and the name of the fallback language (if any), so that the fallback language isn't selected anymore when double-clicking the entity title for copying (phabricator:T256857)
    • Fixed the directionality of text pieces in placeholders that mix LTR and RTL (phabricator:T253812)
    • Continued work on first pieces of design system to make coding new features easier in the future
    • Continued untangling the code of Wikibase Client and Wikibase Repo to make it easier to develop on them
    • Finished first piece of research on how to make it easier to access Wikidata's data for programmers - more work to be done
    • Preparing to start coding on the Query Builder to make it easier to create queries without having to know SPARQL
    • Finished running the scraper that gets potential new references for unreferenced statements and preparing it for publishing

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

RNA + analysis = "RNA analysis"?

Latest comment: 3 years ago1 comment1 person in discussion

Hello, apparently your bot takes a paper title, looks if the words "RNA" and "analysis" appear, and adds the main subject "RNA analysis". I just deleted two such statements that were completely off the mark. Stop these and similar heuristics, please. This is not helpful.

--SCIdude (talk) 16:15, 27 July 2020 (UTC)

Wikimedians for Sustainable Development - July Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our seventh newsletter, covering June 2020. This issue has news related to SDGs 3, 5, 7, 10, 11, 15 and 16.

Meetings

  • Upcoming: Wikimedians for Sustainable Development online meeting August 2 (SDG all) [19]
  • Upcoming: Wikimedians for Sustainable Development online meeting August 16 (SDG all) [20]
  • Past: Wikimedians for Sustainable Development online meeting July 5 (SDG all) [18]

News

  • Another Wikipedian is cultivated (SDG 3) [1]
  • Wikijournal of Medicine to be indexed in SCOPUS (SDG 3) [2]
  • How Wikipedia Became a Battleground for Racial Justice (SDG 10) [3]
  • Sask. doctor keeps COVID-19 Wikipedia info accurate with encyclopedic dedication (SDG 3) [4]
  • We stand for racial justice (SDG 10) [10]
  • Edit Loud, Edit Proud: LGBTIQ+ Wikimedians and Global Information Activism (SDG 10) [15]
  • WikiProject Black Lives Matter (SDG 10) [16]
  • The Power of Knowledge: A Look at the AfroCROWD Juneteenth Conference on Civil Rights (SDG 10) [24]
  • #WikiHerStory: a month-long initiative to amplify gender equity work on Wikimedia projects (SDG 5) [25]
  • How the internet will change our coronavirus memories (SDG 3) [26]
  • How volunteers created Wikipedia’s world-beating Covid-19 coverage (SDG 3) [30]
  • COVIWD - A Covid-19 Wikidata dashboard (SDG 3) [31]

Research

  • COVID-19 research in Wikipedia (SDG 3) [11]
  • A Quantitative Portrait of Wikipedia's High-Tempo Collaborations during the 2020 Coronavirus Pandemic (SDG 3) [12]
  • COVID-19 mobility restrictions increased interest in health and entertainment topics on Wikipedia (SDG 3) [13]
  • A protocol for adding knowledge to Wikidata, a case report (SDG 3) [14]

Videos

  • Wikimedia Research: Medical knowledge on Wikipedia (SDG 3) [23]
  • More black stories need to be told -- and more black contributors need to tell them! (SDG 10) [29]

New WikiProjects

  • Wikipedia:WikiProject Black Lives Matter (SDG 10) [17]

Featured content

  • Alpine newt (SDG 15) [5]
  • Dementia with Lewy bodies (SDG 3) [6]
  • Secretarybird (SDG 15) [7]
  • List of procyonids (SDG 15) [8]
  • List of Sites of Special Scientific Interest in Berkshire (SDG 15) [8]

New Wikidata properties

  • thefreedictionary medical term ID (SDG 3) [21]
  • Naturvårdsverket Anordningar OBJECTID (SDG 15) [22]
  • public transport stop (SDG 11) [27]
  • energy consumption per transaction (SDG 7) [28]
  • BTI Governance Index (SDG 16) [32]
  • BTI Status Index (SDG 16) [32]
  • distribution map of taxon (SDG 15) [34]
  • Queensland Biota ID (SDG 15) [35]
  • Australian Weed ID (SDG 15) [36]

Links

This message was sent with Global message delivery by Ainali (talk) 17:37, 1 August 2020 (UTC) • Contribute • Unsubscribe

Wikidata weekly summary #427

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Wiki13
  • Tool of the week
    • SQID allows you to analyse, browse and query Wikidata. SQID is inspired by Magnus Manske's Reasonator, but focuses on prominently featuring information about Wikidata classes and properties.
  • Development
    • The last week was our quarterly prototyping week. We worked on the following projects. None of them are ready for prime-time yet but we'll continue with them.
      • Slices: We've had a lot of requests for accessing dumps of a smaller part of Wikidata's data since rarely anyone needs the complete data in Wikidata. The tricky part is figuring out which part is needed and if any of that can be generalized. We looked into for example how to make dump generation faster so we could potentially produce more smaller dumps that only cover a part of Wikidata's data, either thematically (e.g. humans) or by type of data (e.g. only statements and English labels and aliases but not sitelinks or descriptions).
      • REST API: As part of our effort to make it easier to access Wikidata's data for programmers we looked into a REST API. We tried to see if we could cover the existing action API modules in a REST API. We could. We'll take this as input for our ongoing API work now.
      • Improving quality ratings through ORES: ORES can judge the quality of an Item automatically. It is currently not very good at it however. We tried a few things to make it more accurate and found some easy wins we'll probably make happen in the next weeks.
      • Query manipulator: One of the ways we could potentially improve the load situation of the Wikidata Query Service is by automatically analyzing and then redirecting a bunch of queries to other systems that are more suitable for that particular type of query. The nice thing about that would be that the person/program sending the query wouldn't have to care about it but it'd be done automagically for them. We tried to build such a system and the results look very promising but more work/experimenting is needed, especially together with the WMF Search team.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #428

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past: Wikibase Live Session - August 2020. This session had a few people present on some of their work with modeling GLAM data in Wikibase or Wikidata. (replay)
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Daniel Mietchen and Lane Rasberry about Scholia, a project to present bibliographic information and scholarly profiles of authors and institutions, 11 August. [Agenda]
    • Upcoming: Online Wikidata editathon in Swedish #25, August 16
  • Development
    • finalized designs for the query builder to start coding at the beginning of September
    • wrapping up the initial work on the design system so that we can start using the first pieces of it in the query builder development
    • working on properly linking redirects in recent changes, watchlist and co (phabricator:T255387)
    • addressed remaining security review comments about the Wikidata Bridge so that we can deploy it finally on the first Wikipedia
    • fixed a bug where string values had the wrong length limit (phabricator:T259440)
    • finishing the work of untangling Wikibase Client and Wikibase Repository extensions to make development easier

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #429

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Entity Explosion: a new multilingual Chrome browser extension. "Taking the power of Wikidata with me wherever I go across the web!". Uses API calls to the Wikidata Query Service to match the URL you are browsing on to a Wikidata item, and then displays data and links to other sites about the same entity. (Video)
  • Development
    • Fixed a bug where a length limit for strings seems to have reverted itself back from 1500 to its default 400 (phabricator:T259440)
    • Fixed a bug that Wikibase is not always adding &redirect=no in situations when MediaWiki usually does (phabricator:T255387)
    • Wrapping up the initial work on the design system so it is ready for use in the first new feature (Query Builder)
    • Fixed the serialization of statements on Forms and Senses not containing the datatype (phabricator:T249206)
    • Wrapping up work on the first version of Federated Properties so that other Wikibase installations can use Wikidata's Properties instead of having to maintain their own
    • Worked on ensuring the data from the linked data interface at Special:EntityData is always up to date after an edit has been made (phabricator:T128486)
    • Enabling clients to use Lua to request labels, descriptions and aliases in some (often minority) languages even when they are not content languages (phabricator:T259340, phabricator:T260118)


You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Research Bot adds statement duplicated

Latest comment: 3 years ago1 comment1 person in discussion

Hi Daniel, Research Bot adds duplicated author statements, if corresponding author statements and author name string statements exist (which of course should not be the case). Example: https://www.wikidata.org/w/index.php?title=Q35783352&diff=prev&oldid=1260959288 Maybe Research Bot could just remove the author name string statements in such a case? --jmkeil (talk) 09:42, 20 August 2020 (UTC)

Wikidata weekly summary #430

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Sophox allows for SPARQL querying of Wikidata and OpenStreetMap in a single query
  • Other Noteworthy Stuff
    • Two new grant programs from WikiCite, in support of open citations and linked bibliographic data.
Full documentation, eligibility requirements, selection criteria, program design principles, and contacts at the links. Apply by 1 October.
  1. Project & events [$2-10k]
  2. e-Scholarships [per-diem calculated on your city; 1-5 people (single, or as a 'remote group') for 2-4 days, for COVID-era "stay at home" projects. Paid in advance living allowance, no expense report required.]
  • Development
    • Deployed the first version of the Wikidata Bridge to Catalan Wikipedia
    • Creating Grafana Dashboards for the new Wikidata Bridge so we have some data to help us determine which datatypes to support next for example (phabricator:T260532)
    • Finished working on ensuring Labels of Items in some unusual, often minority, languages are still available on Wikipedia and other clients (phabricator: T259340)
    • Fixed error messages for API modules that will not work with the first version of Federated Properties (phabricator:T258558)
    • Working on improving how ORES judges the quality of an Item to make it more accurate
    • Started coding on Automated Configuration Discovery to make it easier for tool builders to make their tools work for other Wikibase instances as well

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #431

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Wikidata for Firefox is a browser extension that displays Wikidata items while browsing the web, adds missing IDs and extracts information from websites to Wikidata.
  • Development
    • Working on Automated Configuration Discovery to make it easier for tool builders to make their tools work for other Wikibase instances as well
    • Polishing remaining pieces of the first version of Federated Properties to make it possible to use Wikidata's Properties in other Wikibase instances
    • Continuing to work on improving the way ORES automatically scores the quality of an Item to make it more accurate

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikimedians for Sustainable Development - August Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our ninth newsletter, covering August 2020. This issue has news related to SDGs 3, 4, 6, 11, 13, 14, 15 and 17.

Meetings

  • Upcoming: Online meeting - 2020-09-06 (SDG all) [1]
  • Upcoming: Online meeting - 2020-09-20 (SDG all) [1]
  • Past: Online meeting - 2020-08-02 (SDG all) [2]

Activities

  • Ongoing: The 'Climate Translation Project' celebrated its first published translation: 'Réchauffement climatique en Afrique', a French translation of the English Wikipedia article 'Climate change in Africa' by User:J. N. Squire in French (SDGs 4, 13) [20]
  • Past: World Water Week ISA campaign (SDG 6) [21]
  • Past: Editathon about Covid-19 in Swedish (SDG 3) [22]
  • Past: Editathon about water in Swedish (SDG 6) [23]

News

  • Covid-19 is one of Wikipedia’s biggest challenges ever. Here’s how the site is handling it. (SDG 3) [12]
  • Adding biographies of female oceanographers (SDG 14) [13]
  • Wiki Education participants improve COVID-19 local response articles (SDG 3) [14]
  • Wikimedia Policy Brief - COVID-19 - How Wikipedia helps us through uncertain times (SDG 3) [15]
  • Personal perspective on the forming of the user group (SDG all) [19]

Research

  • Wikipedia, The Free Online Medical Encyclopedia Anyone Can Plagiarize: Time to Address Wiki-Plagiarism (SDG 3) [3]
  • Wikidata-focused presentations at the Workshop "Data Science in Climate and Climate Impact Research" taking place on 20-21 August 2020 in Zurich and online. (SDGs 4, 13, 17) [16] [17]

Videos

  • Multilingual Structured Climate Research Data in Wikidata - The Data Perspective (SDGs 4, 13, 17) [18]
  • Video: Wikipedia Weekly Network - LIVE Wikidata editing about water #17 (SDG 6) [24], [25]

Featured content

  • Vermilion flycatcher (SDG 15) [4]
  • Canada lynx (SDG 15) [5]
  • Meteorological history of Hurricane Dorian (SDG 11) [6]
  • Leeches (SDG 15) [7]
  • Gigantorhynchus (SDG 15) [8]
  • List of World Heritage Sites in Iceland (SDG 11) [9]
  • Ursidae (SDG 15) [10]
  • Mephitidae (SDG 15) [11]
  • Orangutan (SDG 15) [32]
  • Horseshoe bat (SDG 15) [33]
  • Hurricane Willa (SDG 11) [34]
  • List of World Heritage Sites in Lithuania (SDG 11) [35]

New Wikidata properties

  • extinction date (SDG 15) [26]
  • Monumentbrowser ID (SDG 11) [27]
  • Nasjonalt skoleregister ID (SDG 4) [28]
  • American Folklore Society Ethnographic Thesaurus ID (SDG 11) [29]
  • Sculptures and cities database ID for sculptures (SDG 11) [31]

New Wikidata query examples

  • Bar chart showing the number of research output (articles, etc) annotated with a SARSCoV2 proteins as 'main subject' (SDG 3) [30]

Links

This message was sent with Global message delivery by Ainali (talk) 10:50, 4 September 2020 (UTC) • Contribute • Unsubscribe

Wikidata weekly summary #432

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Rob Fernandez (Wikimedia District of Columbia) on Listeria, a tool that uses SPARQL queries to define a list, and provides a bot that will update a wiki page containing that list if the results of that SPARQL query change, all based on Wikidata, 08 September. Agenda
    • Upcoming: live SPARQL queries on Twitch and in French by Vigneron, September 8 at 18:00 CEST
    • Upcoming video: Wikipedia Weekly Network - LIVE Wikidata editing #19 Facebook, YouTube, September 10
    • Upcoming: Online Wikidata editathon in Swedish #29, September 13
  • Development
    • Added Wikidata support to Japanese Wikivoyage. phab:T261451
    • Investigating the nature of our training outliers to improve the way ORES automatically scores the quality of an Item.
    • Working on error that sometimes causes Wikidata UI to report 2 error messages when saving a sitelink in an item. phab:T260869
    • Completed various investigations to make an informed decision on the output format of WikibaseManifest files (automated configuration detection for toolbuilders) phab:T261285
    • Completed various bug fixes and wrap-up tasks to conclude the major engineering work on the Federated Properties project
    • More work on Item Quality Scoring and Federated Properties

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #433

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Mbabel is a tool that simplifies article creation by providing pre-made sentences based on Wikidata statements.
  • Development
    • Fixing an error that sometimes causes Wikidata UI to report 2 error messages when saving a sitelink in an Item instead of just one. (phabricator:T260869)
    • Development of version one of Federated Properties has concluded! Expect an announcement with timing of the release of this feature soon. Wikibase users who want an early look at the feature are invited to reach out to participate in the pre-release testing round.
    • Development of the WikibaseManifest extension has continued into its second sprint; we focused on determining a product specification for the Manifest output.
    • Finishing a draft documentation for a REST API to get it ready for a feedback round before implementation.
    • Finished improvements to the automated scoring of the quality of Items with ORES. Still need to retrain ORES and deploy the changes before the scores are actually different though.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata 8th birthday events in India

Latest comment: 3 years ago1 comment1 person in discussion
 

Hello Daniel Mietchen/Archive/2018!,

I am happy to inform you that we are organizing a series of events on the occasion of the 8th birthday of Wikidata on behalf of WikiProject India in the form of webinars, datathon and merchandise distribution. Details of the events can be found here.

  1. Webinars- 3 sessions on 3 very interesting topics will be conducted as follows. The sessions will be open for all.
  • October 11 2020, 6 pm IST:- Jane023 will talk about Sum of all Paintings, describe and demonstrate the workflow on improving data about paintings on Wikidata. A data-thon on Indian paintings will follow for the next 16 days.
  • October 17 2020, 7 pm IST:- DVrandecic (WMF) will be introducing the newest sister project of the Wikimedia universe, the Abstract Wikipedia and WikiLambda to the Indian community and how as a community, we need to be prepared for this upcoming exciting and ambitious project.
  • October 18 2020, 7 pm IST:- Mahir256 will conduct a session on the Wikidata Lexeme. He will explain the importance of lexicographical data and demonstrate the workflow.
  1. Datathon - October 12 to October 28, 2020:- A 16-days long online datathon will be conducted on Indian paintings. The output of the datathon will be given as a birthday gift to Wikidata on October 29.
  1. Merchandise distribution- During the month of October, CIS-A2K will be sending Wikidata special merchandise to Indian affiliates and communities upon request as well as active contributors of Wikidata residing in India. Details on how to request merchandise can be found here.

The above mentioned activities are already finalised. If any of the Indian communities or affiliates are planning activities on the occasion of Wikidata's 8th birthday, please feel free to enlist them here.

Regards,
Bodhisattwa (CIS-A2K)
Wikidata Co-ordinator, CIS-A2K
Sent through MediaWiki message delivery (talk) 16:10, 15 September 2020 (UTC)

Wikidata weekly summary #434

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Online Wikidata Introduction Workshop (German) (September 29)
    • Upcoming: live SPARQL queries on Twitch and in French by Vigneron, September 21 at 18:00 CEST
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: A starting point for newer institutions to think through what is involved in coordinating a Wikidata project, including shared infrastructure, training, and documentation, 22 September. Agenda
    • Upcoming video: Wikipedia Weekly Network - LIVE Wikidata editing #21 WikiDojo: Facebook, YouTube, September 25
  • Tool of the week
    • copy-qid is a user script by Abbe98 that allows you to copy the Qid with one click.
  • Other Noteworthy Stuff
  • Development
    • WQS now supports mwapi service request for Wikibooks (phab:T261125)
    • The language codes lij-mc, ja-Hira, ja-Kana, ja-Hrkt, ja-Hani, ojp, ojp-Hira and ojp-Hani" have been added for use in monolingual text property values (phab:T254968, phab:T195816)
    • The language codes de-1901, eo-hsistemo and eo-xsistemo, ja-hira, ja-kana and ja-hrkt have been added for Lexemes (phab:T262330,phab:T257422, phab:T250559)
    • P1438 has been converted from string to external ID datatype (phab:T262198)
    • Worked on fixing an input issue with invisible characters (phab:T261071)
    • Investigating what work would be needed to get the new termbox that's available on mobile to also work on desktop
    • Fixing several issues with Special:Undelete (phab:T261747)
    • Fixing an error message being shown twice (phab:T260869)
    • Starting the coding work on the Query Builder
    • Continuing to write a draft for a REST API specification
    • Finishing the remaining work needed to get the improved quality scoring for Items deployed to ORES
    • Continuing work on WikibaseManifest: Determined the essential metadata that will be included in the WikibaseManifest file, added some new features (mostly MediaWiki metadata) to the Manifest that were requested by the OpenRefine team (phab:T262805 and phab:T262804) and set up a test system that will soon be ready for tool builders to use for testing the integration of their tools with WikibaseManifest


You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

We sent you an e-mail

Latest comment: 3 years ago1 comment1 person in discussion

Hello Daniel Mietchen/Archive/2018,

Really sorry for the inconvenience. This is a gentle note to request that you check your email. We sent you a message titled "The Community Insights survey is coming!". If you have questions, email surveys@wikimedia.org.

You can see my explanation here.

MediaWiki message delivery (talk) 18:45, 25 September 2020 (UTC)

Wikidata weekly summary #435

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • The Wikidata development team is seeking to evaluate and improve the process of collecting and reacting to bug reports and feature requests. You can give feedback about your experience using this anonymous form until September 30th or add feedback publically to Wikidata talk:Contact the development team/Process review 2020.
    • Nominate your favorite tools for the Coolest Tool Award 2020 before October 14th.
    • Wikidata Walkabout is a new site that lets you browse and drill down through different "classes" of data on Wikidata: wikidatawalkabout.org
    • Como is a new Android app, that uses Wikidata lexemes and senses to create a word-guessing game. It let's players create new senses and tests them on other players to finally save them in Wikidata. The app is developed as part of a BA thesis, to determine if this concept is useful to create more lexicographical data, and testers would be very welcome.
  • Development
    • A long-standing bug has been fixed (T217144) where Items and Lexemes created via OAuth would not be added to the user’s watchlist even if the user had the Add pages I create and files I upload to my watchlist setting enabled. (The Add pages and files I edit to my watchlist setting was probably likewise ineffective, but this was not tested specifically.) Affected tools include QuickStatements, Mix'n'Match, and Wikidata Lexeme Forms; users of these and other tools may see more pages being added to their watchlists now. (This only applies to new edits and page creations; previously created or edited pages will not be automatically added to the watchlist retroactively.)
    • Working on the basic building blocks of the Query Builder towards making it possible to create the first very simple query with it
    • Talking to people about comparing Wikidata's data against other databases and flagging mismatches
    • Fixing an issue with Item creations via the API by blocked users leading to skipped entity IDs (phab:T232620)
    • Fixed an input issue with invisible characters (phab:T261071)
    • Finishing the draft of the REST API spec to get it ready for feedback
    • WikibaseManifest: created a separate key for local entities and decided what we do about non-local entity sources based on tool-builder feedback (phab:T263527) and specifying the API in OpenApi format (phab:T262919)


You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

WikiProject India Newsletter #5

Latest comment: 3 years ago1 comment1 person in discussion
 

Hi Daniel Mietchen/Archive,

You are receiving this message as you are one of the participants of WikiProject India on Wikidata and/or a subscriber of the Wikidata India newsletter. You can find our fifth issue of the quarterly newsletter here, where you can get a quick overview of the Wikidata activities related to India over the last 3 months. If you do not want to receive this kind of notification further, you can remove your username from here.

Regards, Bodhisattwa (CIS-A2K) and Mahir256
(on behalf of WikiProject India)
Sent through MediaWiki message delivery (talk) 18:35, 30 September 2020 (UTC)

Wikimedians for Sustainable Development - September Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our tenth newsletter, covering September 2020. This issue has news related to SDGs 3, 5, 6, 10, 11, 13 and 15.

Meetings

  • Online meeting October 4 (SDG all) [1]
  • Online meeting October 18 (SDG all) [1]

Activities

  • Ongoing: The 'Climate Translation Project' (SDG 13) [17]
  • Ongoing: Survey on gender equality on Wikipedia (SDG 5) [12] [13]
  • Ongoing: The 'Gender equality 2020' editing week (SDG 5) [15]
  • Ongoing: Wiki Loves Fashion 2020 (SDG 5) [16]
  • Past: Climate Justice Editathon (SDG 10 & 13) [3]
  • Past: Wikimedia Foundation hosts Sustainability Community Roundtable Discussion about carbon credits (SDG 13) [8]
  • Past: Wiki loves SDGs - Global Goals Week online edit-a-thon on SDG topics (SDG all) [9] [10] [11]
  • Past: WikiGap Skopje 2020 online edit-a-thon (SDG 5) [14]
  • Past and ongoing: Wiki Loves Monuments (SDG 11) [22]

News

  • Humaniki: Wikimedia Diversity Data Tools (SDG 5) [2]
  • How can I get data on all the dams in the world? Use Wikidata (SDG 6) [4]

Research

  • Using logical constraints to validate information in collaborative knowledge graphs: a study of COVID-19 on Wikidata (SDG 3) [6]
  • Representing COVID-19 information in collaborative knowledge graphs: a study of Wikidata (SDG 3) [21]

Videos

  • Wikipedia Weekly Network - LIVE Wikidata editing #21 - WikiDojo on the Global Climate Strike (SDG 13) [18]

Featured content

  • Zebra (SDG 15) [23]
  • Tropical Storm Vicente (SDG 11) [24]

New Wikidata properties

  • National Park Service place ID (SDG 15) [19]
  • Symptom Ontology ID (SDG 3) [20]

New Wikidata query examples

  • Map of organisations/companies developing/manufacturing a vaccine in trials (SDG 3) [5]
  • Top World Heritage sites by number of paintings depicting them (SDG 11) [7]

Links

This message was sent with Global message delivery by Ainali (talk) 20:10, 1 October 2020 (UTC) • Contribute • Unsubscribe

Wikidata weekly summary #436

Latest comment: 3 years ago1 comment1 person in discussion
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Professor Toby Hudson on Entity Explosion, a browser extension which allows you to get information about entities on the web page you’re visiting, 06 October. Agenda
    • Upcoming: Wikidata & Wikibase office hour, October 27th at 17:00 CEST (15:00 GMT)
    • Upcoming: plenty of events for the Wikidata birthday, check the calendar and feel free to organise one!
  • Tool of the week
    • IllWill.js is a userscript that searches Wikidata for foreign-language sitelinks, to populate Template:ill and replace plain red links on other Wikimedia projects.
  • Other Noteworthy Stuff
    • omeka-s-wikidata is a new module for the open source GLAM collection management software Omeka, that allows cataloguers to use Wikidata as a vocabulary for persons, places, subjects, etc.
  • Development
    • First pieces of the Query Builder are coming together and we are working towards making it generate the first dumb query
    • Talking to people about their thoughts on checking Wikidata's data against other databases. If you're interested reach out to Mohammed.
    • Got some first internal feedback for the REST API specification draft. We'll publish it for feedback in the next days.
    • Fixing an issue with certain language codes no longer being available (phab:T264294)
    • Working on making sure blocked bots don't waste Item IDs when trying to create new Items (phab:T232620)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

India-specific properties datathon

Greetings Daniel Mietchen/Archive/2018!

 

As part of Wikidata's 8th birthday celebration a 5 days long India-specific properties datathon from October 25, 2020, 00:00 to October 29, 2020, 23:59 (both times Indian Standard Time) being organised to improve India-specific properties and celebrate Wikidata's Birthday by contributing to the free open data movement. Currently there are 76 India-specific properties available in Wikidata. The primary objective of this datathon is to add / improve the usage of Wikidata Properties related to India in Wikidata.

Details of the events can be found here. Please have a look at the event page and please consider joining the datathon by adding your name at the participant's list here

You are receiving this message as you are one of the participants of WikiProject India on Wikidata. If you do not want to receive this kind of notification further, you can remove your username from here.

Regards,

Gnoeee

Démonstration de Scholia comme un outil ouvert d’analyse scientométrique

Latest comment: 3 years ago1 comment1 person in discussion

Je n'ai pas pu participer qu'à la 2e partie de votre exposé. Super interessant. J'avais entendu parle de Scholia sans jamais l'avoir utilisé. Merci beaucoup pour cette démonstrationLaMèreVeille (talk) 18:13, 27 October 2020 (UTC)

Wikimedians for Sustainable Development - October Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our eleventh newsletter, covering October 2020. This issue has news related to SDGs 3, 4, 8, 11, 13, 15 and 16.

Meetings

  • Online meeting November 1 (SDG all) [1]
  • Online meeting November 15 (SDG all) [1]
  • Past: Prioritization event survey (SDG all) [26]

Activities

  • Ongoing: The 'Climate Translation Project' (SDG 13) [2]
  • Upcoming: Enriching parliamentary documents metadata editathon (in Swedish) (SDG 16) [27]
  • Past: Wiki for UN writing campaign (SDG 17) [28]

News

  • Wikipedia and Sustainable Development Goals: Engaging smaller Wikipedias (SDG all) [3]
  • The World Health Organization and Wikimedia Foundation expand access to trusted information about COVID-19 on Wikipedia (SDG 3) [10]
  • Improving reproductive health articles on Wikipedia (SDG 3) [11]
  • Wiki Loves SDGs: A community of Global Goals factivists (SDG all) [12]
  • Analyze Swedish politics with Wikidata (SDG 16) [17]

Resources

  • GUIDE: How to contribute climate change information to Wikipedia (SDG 13) [25]

Videos

  • 2020-09-29 Houcemeddine Turki, U of Sfax: Wikidata & COVID-19, a collaborative KG from CORD-19 (SDG 3) [4]
  • WikiCite 2020: OpenVirus and Scholia interfaces (SDG 3) [13]
  • WikiCite 2020: Citations in Swedish Parliamentary documents (SDG 16) [18]
  • WikiCite 2020: Gene Wiki (SDG 3) [19]

New Wikidata properties

  • Symptom Ontology ID (SDG 3) [6]
  • SSYK 2012 The Swedish Standard Classification of Occupations (SDG 8) [7]
  • Native Plants Database ID (SDG 15) [8]
  • NBIC taxon ID (SDG 15) [14]
  • Danish educational institution number (SDG 4) [15]
  • economy of topic (SDG 8) [20]
  • American Heritage place ID (SDG 11) [21]
  • DC Historic Sites place ID (SDG 11) [22]

New Wikidata query examples

  • Map of trees whose species is categorized as threatened on the IUCN Red List (SDG 15) [5]
  • Map of outdoor warning sirens, color-coded by manufacturer (SDG 11) [9]
  • Scientific papers explaining backward contact tracing (SDG 3) [16]
  • Invasive species in EU and whether they have articles in different languages (SDG 15) [23]
  • COVID-19 deaths by month (SDG 3) [24]

Links

This message was sent with Global message delivery by Ainali (talk) 12:35, 1 November 2020 (UTC) • Contribute • Unsubscribe

WikiProject India Newsletter #6

Latest comment: 3 years ago1 comment1 person in discussion
 

Hi Daniel Mietchen/Archive,

Happy New Year 2021!

You are receiving this message as you are one of the participants of WikiProject India on Wikidata and/or a subscriber of the Wikidata India newsletter. You can find our sixth issue of the quarterly newsletter here, where you can get a quick overview of the Wikidata activities related to India over the last 3 months. If you do not want to receive this kind of notification further, you can remove your username from here.

Regards, Bodhisattwa (CIS-A2K) and Mahir256
(on behalf of WikiProject India)
Sent through MediaWiki message delivery (talk) 03:04, 1 January 2021 (UTC)

Altmetric

Latest comment: 3 years ago3 comments2 people in discussion

Hi Daniel,

I am currently working on a project to create the links between the 26 million Wikidata element with a DOI and their Altmetric DOI (P5530). I am about to contact Altmetric to get their approval (their API is limited to 1 request per second and does not allow extraction like I want to perform), and since you've imported most of the scientific papers on Wikidata, I was wondering if you would have any comment or suggestion about this initiative.

Thanks, Dirac (talk) 19:51, 3 January 2021 (UTC)

@Dirac: Thanks for working on this, and your notes are great. I would certainly like to see closer integration with Altmetric, but not sure what their take on this is. In terms of suggestions, a simple one would be to use Underestimating the Challenges of Avoiding a Ghastly Future (Q105082215) as an example. More complex ones would require some more digging on my end — not sure when that may happen. There are also questions I would have for them, e.g. I would be interested in whether and how they are using Wikidata, how many Wikipedia languages they are covering now (I think they had a time with English only, then about a dozen languages, but I haven't looked into this lately, so there may well be more) and whether they pick up anything from Wikimedia Commons or other Wikimedia sites. --Daniel Mietchen (talk) 04:18, 31 January 2021 (UTC)
@Daniel Mietchen: I received an answer from Altmetric that might change the way we use this metric. I've posted the answer, and my proposal to fix this, on the Almetric ID talk page. Feel free to jump in and give your opinion. And now that I have a contact that is answering my emails, I will ask them your questions about the usage the do of Wikipedia/Wikidata. Thanks, Dirac (talk) 18:53, 1 February 2021 (UTC)

L2927

Latest comment: 3 years ago2 comments2 people in discussion

You created چِلتن/Чилтан/Chiltan (L2927). I pinged you on its talk page, but I see that you do not respond to pings. What is that lexeme supposed to mean (if you added a sense, what would it be)? Mahir256 (talk) 22:44, 27 January 2021 (UTC)

@Mahir256: I see this as a spelling variant of "چلتن". I have seen both (across several languages) in reference to the story of the fourty beings that has been told in the region in many variants and who have quite a few things named after them, e.g. Koh-i-Chiltan (Q6425850). The best published description I am aware of is here, transliterated into چل‌تن/Чилтан (L226820), which is the spelling most familiar to me, since my exposure to variants of this story has been mostly through Tadjik, Uzbek and Russian sources. --Daniel Mietchen (talk) 04:05, 31 January 2021 (UTC)

Wikimedians for Sustainable Development - January 2021 Newsletter

Latest comment: 3 years ago1 comment1 person in discussion
This is our fourteenth newsletter, covering January 2021. This issue has news related to SDGs 1, 3, 4, 5, 10, 13 and 15 .

Meetings

  • Online user group meeting February 7 (SDG all) [1]
  • Online user group meeting February 21 (SDG all) [1]
  • Wikimedia Strategy Follow-up calls: Alignment with environmental sustainability February 7 (SDG 13) [10]
  • Wikimedia Strategy Follow-up calls: Identify Topics for Impact February 5 (SDG all) [23]

Activities

  • Ongoing: The 'Climate Translation Project' (SDG 13) [2]

News

  • The Vaccine Safety Project on Wikipedia (SDG 3) [3]
  • Wiki for COVID-19: 2020, the year of Information (SDG 3) [6]
  • One Page At A Time, Jess Wade Is Changing Wikipedia (SDG 5) [18]
  • The Women of Wikipedia Are Writing Themselves Into History (SDG 5) [19]

Research

  • Building a biological knowledge graph via Wikidata with a focus on the Human Cell Atlas (SDG 3) [7]
  • Open Wikipedia Dataset on COVID-19 from IBS Data Science Group (SDG 3) [8]
  • A protocol for adding knowledge to Wikidata: aligning resources on human coronaviruses (SDG 3) [9]
  • Wikipedia, The Free Online Medical Encyclopedia Anyone Can Plagiarize: Time to Address Wiki-Plagiarism (SDG 3) [20]
  • Multilingual Contextual Affective Analysis of LGBT People Portrayals in Wikipedia (SDG 10) [21]
  • Wikipedia as OER: the "Learning with Wikipedia" (SDG 4) [22]

New Wikidata properties

  • derived from organism type (SDG 15) [14]
  • number of aid beneficiaries (SDG all) [15]
  • Australian Fungi ID (SDG 15) [16]
  • Red Cross FDRS ID (SDG 3) [17]

New Wikidata query examples

  • Number of people who have died, or been diagnosed, of COVID-19, grouped by occupation (SDG 3) [4]
  • Map of gram panchayats in Kerala by literacy rate in 2001 (SDG 4) [5]
  • Map of Kolkata wards by number of schools (SDG 4) [11]
  • Red Cross and Red Crescent societies (SDG 3) [12]
  • Mangifera species and mango cultivars (SDG 1) [13]

Links

This message was sent with Global message delivery by Ainali (talk) 20:32, 1 February 2021 (UTC) • Contribute • Unsubscribe

[WMF Board of Trustees - Call for feedback: Community Board seats] Meetings with the Wikidata community

Latest comment: 3 years ago1 comment1 person in discussion

The Wikimedia Foundation Board of Trustees is organizing a call for feedback about community selection processes between February 1 and March 14. While the Wikimedia Foundation and the movement have grown about five times in the past ten years, the Board’s structure and processes have remained basically the same. As the Board is designed today, we have a problem of capacity, performance, and lack of representation of the movement’s diversity. Our current processes to select individual volunteer and affiliate seats have some limitations. Direct elections tend to favor candidates from the leading language communities, regardless of how relevant their skills and experience might be in serving as a Board member, or contributing to the ability of the Board to perform its specific responsibilities. It is also a fact that the current processes have favored volunteers from North America and Western Europe. In the upcoming months, we need to renew three community seats and appoint three more community members in the new seats. This call for feedback is to see what processes can we all collaboratively design to promote and choose candidates that represent our movement and are prepared with the experience, skills, and insight to perform as trustees?

In this regard, two rounds of feedback meetings are being hosted to collect feedback from the Wikidata community. Two rounds are being hosted with the same agenda, to accomodate people from various time zones across the globe. We will be discussing ideas proposed by the Board and the community to address the above mentioned problems. Please sign-up according to whatever is most comfortable to you. You are welcome to participate in both as well!

Also, please share this with other volunteers who might be interested in this. Let me know if you have any questions. KCVelaga (WMF), 14:32, 21 February 2021 (UTC)

Retrieved from "https://www.wikidata.org/w/index.php?title=User_talk:Daniel_Mietchen/Archive/2018&oldid=1537339231"
Return to the user page of "Daniel Mietchen/Archive/2018".