This is an archive of past discussions with User:Lirazelf. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Recently Jimmy Wales has made the point that computer home assistants take much of their data from Wikipedia, one way or another. So as well as getting Spotify to play Frosty the Snowman for you, they may be able to answer the question "is the Pope Catholic?" Possibly by asking for disambiguation (Coptic?).
Headlines about data breaches are now familiar, but the unannounced circulation of information raises other issues. One of those is Gresham's law stated as "bad data drives out good". Wikipedia and now Wikidata have been criticised on related grounds: what if their content, unattributed, is taken to have a higher standing than Wikimedians themselves would grant it? See Wikiquote on a misattribution to Bismarck for the usual quip about "law and sausages", and why one shouldn't watch them in the making.
Wikipedia has now turned 18, so should act like as adult, as well as being treated like one. The Web itself turns 30 some time between March and November this year, per Tim Berners-Lee. If the Knowledge Graph by Google exemplifies Heraclitean Web technology gaining authority, contra GIGO, Wikimedians still have a role in its critique. But not just with the teenage skill of detecting phoniness.
There is more to beating Gresham than exposing the factoid and urban myth, where WP:V does do a great job. Placeholders must be detected, and working with Wikidata is a good way to understand how having one statement as data can blind us to replacing it by a more accurate one. An example that is important to open access is that, firstly, the term itself needs considerable unpacking, because just being able to read material online is a poor relation of "open"; and secondly, trying to get Creative Commons license information into Wikidata shows up issues with classes of license (such as CC-BY) standing for the actual license in major repositories. Detailed investigation shows that "everything flows" exacerbates the issue. But Wikidata can solve it.
Systematic reviews are basic building blocks of evidence-based medicine, surveys of existing literature devoted typically to a definite question that aim to bring out scientific conclusions. They are principled in a way Wikipedians can appreciate, taking a critical view of their sources.
PRISMA flow diagram for a systematic review
Ben Goldacre in 2014 wrote (link below) "[...] : the "information architecture" of evidence based medicine (if you can tolerate such a phrase) is a chaotic, ad hoc, poorly connected ecosystem of legacy projects. In some respects the whole show is still run on paper, like it's the 19th century." Is there a Wikidatan in the house? Wouldn't some machine-readable content that is structured data help?
Most likely it would, but the arcana of systematic reviews and how they add value would still need formal handling. The PRISMA standard dates from 2009, with an update started in 2018. The concerns there include the corpus of papers used: how selected and filtered? Now that Wikidata has a 20.9 million item bibliography, one can at least pose questions. Each systematic review is a tagging opportunity for a bibliography. Could that tagging be reproduced by a query, in principle? Can it even be second-guessed by a query (i.e. simulated by a protocol which translates into SPARQL)? Homing in on the arcana, do the inclusion and filtering criteria translate into metadata? At some level they must, but are these metadata explicitly expressed in the articles themselves? The answer to that is surely "no" at this point, but can TDM find them? Again "no", right now. Automatic identification doesn't just happen.
Actually these questions lack originality. It should be noted though that WP:MEDRS, the reliable sources guideline used here for health information, hinges on the assumption that the usefully systematic reviews of biomedical literature can be recognised. Its nutshell summary, normally the part of a guideline with the highest density of common sense, allows literature reviews in general validity, but WP:MEDASSESS qualifies that indication heavily. Process wonkery about systematic reviews definitely has merit.
Australia report: International Digital Curation Conference 2019
Belgium report: Wiki Loves Heritage; Wikipedian in Residence at the King Baudouin Foundation
Brazil report: "Our experience with Wikimedians has brought collaborative principles of Wikipedia to our work with archival curation": an interview with the coordinator of the GLAM-Wiki initiative with the Brazilian National Archives
Hello and welcome to the March newsletter, a brief update of Guild activities since December 2018. All being well, we're planning to issue these quarterly in 2019, balancing the need to communicate widely with the avoidance of filling up talk pages. Don't forget you can unsubscribe at any time; see below.
January Drive: Thanks to everyone for the splendid work in January's Backlog Elimination Drive. We removed copyedit tags from all of the articles tagged in our original target months of June, July and August 2018, and by 24 January we ran out of articles. After adding September, we finished the month with 8 target articles remaining and 842 left in the backlog. GOCE copyeditors also completed 48 requests for copyedit in January. Of the 31 people who signed up for this drive, 24 copyedited at least one article. Final results, including barnstars awarded, are available here.
Blitz: Thanks to everyone who participated in the February Blitz. Of the 15 people who signed up, 13 copyedited at least one article. Participants claimed 32 copyedits, including 15 requests. Final results, including barnstars awarded, are available here.
Progress report: As of 23:39, 18 March 2019 (UTC), GOCE copyeditors have completed 108 requests since 1 January and the backlog stands at 851 articles.
March Drive: The month-long March drive is now underway; the target months are October and November 2018. Awards will be given to everyone who copyedits at least one article from the backlog. Sign up here!
Election reminder: It may only be March but don't forget our mid-year Election of Coordinators opens for nominations on 1 June. Coordinators normally serve a six-month term and are elected on an approval basis. Self-nominations are welcome. If you've thought of helping out at the Guild, or know of another editor who would make a good coordinator, please consider standing for election or nominating them here.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Miniapolis, Baffle gab1978, Jonesey95, Reidgreg and Tdslk.
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
The term Applications Programming Interface or API is 50 years old, and refers to a type of software library as well as the interface to its use. While a compiler is what you need to get high-level code executed by a mainframe, an API out in the cloud somewhere offers a chance to perform operations on a remote server. For example, the multifarious bots active on Wikipedia have owners who exploit the MediaWiki API.
APIs (called RESTful) that allow for the GET HTTP request are fundamental for what could colloquially be called "moving data around the Web"; from which Wikidata benefits 24/7. So the fact that the Wikidata SPARQL endpoint at query.wikidata.org has a RESTful API means that, in lay terms, Wikidata content can be GOT from it. The programming involved, besides the SPARQL language, could be in Python, younger by a few months than the Web.
Magic words, such as occur in fantasy stories, are wishful (rather than RESTful) solutions to gaining access. You may need to be a linguist to enter Ali Baba's cave or the western door of Moria (French in the case of "Open Sesame", in fact, and Sindarin being the respective languages). Talking to an API requires a bigger toolkit, which first means you have to recognise the tools in terms of what they can do. On the way to the wikt:impactful or polymathic modern handling of facts, one must perhaps take only tactful notice of tech's endemic problem with documentation, and absorb the insightful point that the code in APIs does articulate the customary procedures now in place on the cloud for getting information. As Owl explained to Winnie-the-Pooh, it tells you The Thing to Do.
Working With Wikibase From Go, Digital Flapjack blogpost 26 November 2018, Michael Dales, developer for ScienceSource using golang, with a software engineer's view on Wikibase and the MediaWiki API
Talk of cloud computing draws a veil over hardware, but also, less obviously but more importantly, obscures such intellectual distinction as matters most in its use. Wikidata begins to allow tasks to be undertaken that were out of easy reach. The facility should not be taken as the real point.
Coming in from another angle, the "executive decision" is more glamorous; but the "administrative decision" should be admired for its command of facts. Think of the attitudes ad fontes, so prevalent here on Wikipedia as "can you give me a source for that?", and being prepared to deal with complicated analyses into specified subcases. Impatience expressed as a disdain for such pedantry is quite understandable, but neither dirty data nor false dichotomies are at all good to have around.
Issue 13 and Issue 21, respectively on WP:MEDRS and systematic reviews, talk about biomedical literature and computing tasks that would be of higher quality if they could be made more "administrative". For example, it is desirable that the decisions involved be consistent, explicable, and reproducible by non-experts from specified inputs.
What gets clouded out is not impossibly hard to understand. You do need to put together the insights of functional programming, which is a doctrinaire and purist but clearcut approach, with the practicality of office software. Loopless computation can be conceived of as a seamless forward march of spreadsheet columns, each determined by the content of previous ones. Very well: to do a backward audit, when now we are talking about Wikidata, we rely on integrity of data and its scrupulous sourcing: and clearcut case analyses. The MEDRS example forces attention on purge attempts such as Beall's list.
Two dozen issues, and this may be the last, a valediction at least for a while.
It's time for a two-year summation of ContentMine projects involving TDM (text and data mining).
Wikidata and now Structured Data on Commons represent the overlap of Wikimedia with the Semantic Web. This common ground is helping to convert an engineering concept into a movement. TDM generally has little enough connection with the Semantic Web, being instead in the orbit of machine learning which is no respecter of the semantic. Don't break a taboo by asking bots "and what do you mean by that?"
The ScienceSource project innovates in TDM, by storing its text mining results in a Wikibase site. It strives for compliance of its fact mining, on drug treatments of diseases, with an automated form of the relevant Wikipedia referencing guideline MEDRS. Where WikiFactMine set up an API for reuse of its results, ScienceSource has a SPARQL query service, with look-and-feel exactly that of Wikidata's at query.wikidata.org. It also now has a custom front end, and its content can be federated, in other words used in data mashups: it is one of over 50 sites that can federate with Wikidata.
The human factor comes to bear through the front end, which combines a link to the HTML version of a paper, text mining results organised in drug and disease columns, and a SPARQL display of nearby drug and disease terms. Much software to develop and explain, so little time! Rather than telling the tale, Facto Post brings you ScienceSource links, starting from the how-to video, lower right.
Please be aware that this is a research project in development, and may have outages for planned maintenance. That will apply for the next few days, at least. The ScienceSource wiki main page carries information on practical matters. Email is not enabled on the wiki: use site mail here to Charles Matthews in case of difficulty, or if you need support. Further explanatory videos will be put into commons:Category:ContentMine videos.
Hi, I just see that you changed this user to "confirmed user". For several days now I have been trying to get in touch with this editor, but multiple posts on their talk page have gone unanswered. They don't appear to have email enabled. Given that you are apparently involved in a training event, perhaps you have other means to contact them and ask them to respond to the multiple messages on their talk page. Thanks! --Randykitty (talk) 12:59, 5 June 2019 (UTC)
Hello, Lirazelf. Please check your email; you've got mail! It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
Hello and welcome to the June newsletter, a brief update of Guild activities since March 2019. You can unsubscribe from our mailings at any time; see below.
Election time: Nomination of candidates in our mid-year Election of Coordinators opened on 1 June, and voting will take place from 16 June. Coordinators normally serve a six-month term and are elected on an approval basis. Self-nominations are welcome. If you've thought of helping out at the Guild, or know of another editor who would make a good coordinator, please consider standing for election or nominating them here.
June Blitz: Our June blitz will soon be upon us; it will begin at 00:01 on 16 June (UTC) and will close at 23:59 on 22 June (UTC). The themes are "nature and the environment" and all requests.
March Drive: Thanks to everyone for their work in March's Backlog Elimination Drive. We removed copyedit tags from 182 of the articles tagged in our original target months October and November 2018, and the month finished with 64 target articles remaining from November and 811 in the backlog. GOCE copyeditors also completed 22 requests for copyedit in March; the month ended with 34 requests pending. Of the 32 people who signed up for this drive, 24 copyedited at least one article. Final results, including barnstars awarded, are available here.
April Blitz: Thanks to everyone who participated in the April Blitz; the blitz ran from 14 to 20 April (UTC) inclusive and the themes were Sports and Entertainment. Of the 15 people who signed up, 13 copyedited at least one article. Participants claimed 60 copyedits. Final results, including barnstars awarded, are available here.
Progress report: As of 04:36, 3 June 2019 (UTC), GOCE copyeditors have completed 267 requests since 1 January. The backlog of tagged articles stands at 605 articles.
May Drive: During the May Backlog Elimination Drive, Guild copy-editors removed copyedit tags from 191 of the 192 articles tagged in our original target months of November and December 2018, and January 2019 was added on 22 May. We finished the month with 81 target articles remaining and a record low of 598 articles in the backlog. GOCE copyeditors also completed 24 requests for copyedit during the May drive, and the month ended with 35 requests pending. Of the 26 people who signed up for this drive, 21 copyedited at least one article. Final results, including barnstars awarded, are available here.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Miniapolis, Baffle gab1978, Jonesey95, Reidgreg and Tdslk.
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
Netherlands report: Image donation; Wiki goes Caribbean meeting on slavery and plantations in Suriname; Dutch open public library data; Field study collaboration Wikimedia and Libraries
Norway report: The International Year of Indigenous Languages 2019
Poland report: Documentary photographs from National Archives and WikiPlato
Structured Data on Commons - A Blog Series, written by me, is a five-part posting that covers the basics of the software and features that were built to make structured data happen. The series is meant to be friendly to those who may have some knowledge of Commons, but may not know much about the structured data project.
I hope these are informative and useful, comments and questions are welcome. All the blogs offer a comment feature, and you can log in with your Wikimedia account using oAuth. I look forward to seeing some posts over there. -- Keegan (WMF) (talk) 21:33, 23 September 2019 (UTC)
Hello and welcome to the September newsletter, a brief update of Guild activities since June 2019.
June election: Reidgreg was chosen as lead coordinator, and is being assisted by Baffle gab1978, Miniapolis, Tdslk, and first-time coordinator Twofingered Typist. Jonesey95 took a respite after serving for six years. Thanks to everyone who participated!
June Blitz: From 16 to 22 June, we copy edited articles on the themes of nature and the environment along with requests. 12 participating editors completed 35 copy edits. Final results, including barnstars awarded, are available here.
July Drive: The year's fourth backlog-elimination drive was a great success, clearing all articles tagged in January and February, and bringing the copy-editing backlog to a low of five months and a record low of 585 articles while also completing 48 requests. Of the 30 people who signed up, 29 copyedited at least one article, a participation level last matched in May 2015. Final results and awards are listed here.
August Blitz: From 18 to 24 August, we copy edited articles tagged in March 2019 and requests. 12 participating editors completed 26 copy edits on the blitz. Final results, including barnstars awarded, are available here.
Progress report: As of 03:00, 23 September 2019 (UTC), GOCE copyeditors had processed 413 requests since 1 January. The backlog of tagged articles stood at 599 articles, close to our record month-end low of 585.
Requests page: We are experimenting with automated archiving of copy edit requests; a discussion on REQ Talk (permalinked) initiated by Bobbychan193 has resulted in Zhuyifei1999 writing a bot script for the Guild. Testing is now underway and is expected to be completed by 3 October; for this reason, no manual archiving of requests should be done until the testing period is over. We will then assess the bot's performance and discuss whether to make this arrangement permanent.
September Drive: Our current backlog-elimination drive is open until 23:59 on 30 September (UTC) and is open to all copy editors. Sign up today!
Sweden report: Open cultural heritage; More libraries in Africa on Wikidata; Global MIL Week 2019 Feature Conference; Kulturhistoria som gymnasiearbete; Wiki Loves Monuments
UK report: Oxford, Khalili Collections and Endangered Archives
USA report: Hispanic Heritage and Disability Awareness Month
Special story: Help the Movement Learn about Content Campaigns & Supporting newcomers in Wikidata training courses!
On 22 October 2019, Did you know was updated with a fact from the article Patricia Bagot, which you recently created, substantially expanded, or brought to good article status. The fact was ... that housing expert Patricia Bagot argued with Colonel Muammar Gaddafi over the quality of housing in Libya? The nomination discussion and review may be seen at Template:Did you know nominations/Patricia Bagot. You are welcome to check how many page hits the article got while on the front page (here's how, Patricia Bagot), and it may be added to the statistics page if the total is over 5,000. Finally, if you know of an interesting fact from another recently created article, then please feel free to suggest it on the Did you know talk page.
@Evolution and evolvability: Thanks for this! I've added a missing WiR, and updated some details. The map looks great, but looking at Scotland, we've got dots hiding other dots as there were multiple placements in the same city - is there a way to change this at all? Lirazelf (talk) 11:31, 29 October 2019 (UTC)
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Hello and welcome to the December 2019 GOCE newsletter, an update of Guild happenings since the September edition. Our Annual Report should be ready in late January.
Election time: Nominations for the election of a new tranche of Guild coordinators to serve for the first half of 2020 will be open from 1 to 15 December. Voting will then take place and the election will close on 31 December at 23:59 UTC. Positions for Guild coordinators, who perform the important behind-the-scenes tasks that keep our project running smoothly, are open to all Wikipedians in good standing. We welcome self-nominations so please consider nominating yourself if you've ever thought about helping out; it's your Guild and it doesn't run itself!
September Drive: Of the thirty-two editors who signed up, twenty-three editors copy edited at least one article; they completed 39 requests and removed 138 articles from the backlog, bringing the backlog to a low of 519 articles.
October Blitz: This event ran from 13 to 19 October, with themes of science, technology and transport articles tagged for copy edit, and Requests. Sixteen editors helped remove 29 articles from the backlog and completed 23 requests.
November Drive: Of the twenty-eight editors who signed up for this event, twenty editors completed at least one copy edit; they completed 29 requests and removed 133 articles from the backlog.
Our December Blitz will run from 15 to 21 December. Sign up now!
Progress report: From September to November 2019, GOCE copy editors processed 154 requests. Over the same period, the backlog of articles tagged for copy editing was reduced by 41% to an all-time low of 479 articles.
Request archiving: The archiving of completed requests has now been automated. Thanks to Zhuyifei1999 and Bobbychan193, YiFeiBot is now archiving the Requests page. Archiving occurs around 24 hours after a user's signature and one of the templates {{Done}}, {{Withdrawn}} or {{Declined}} are placed below the request. The bot uses the Guild's standard "purpose codes" to determine the way it should archive each request so it's important to use the correct codes and templates.
@Dthomsen8: Hello there! Thanks for that, much appreciated. The article's due to be moved to mainspace in the next week or so, it was one of a few that were created as part of the Dumfries Stonecarving Project, in partnership with Wikimedia UK (this is my volunteer account, I can also be found at Sara Thomas (WMUK)). We worked with them for around a year, working with photo groups and volunteer archival researchers - more here: Wikipedia:GLAM/Dumfries Stonecarving Project Editathon 30.07.19 and here. If you're interested in adding more to any of the articles, please do, the project and I would be delighted! Lirazelf (talk) 14:18, 17 December 2019 (UTC)
.jpg)
