Jump to content

User talk:Fuzheado/Archive 8

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia


Facto Post – Issue 8 – 15 January 2018

Facto Post – Issue 8 – 15 January 2018

Metadata on the March

From the days of hard-copy liner notes on music albums, metadata have stood outside a piece or file, while adding to understanding of where it comes from, and some of what needs to be appreciated about its content. In the GLAM sector, the accumulation of accurate metadata for objects is key to the mission of an institution, and its presentation in cataloguing.

Today Wikipedia turns 17, with worlds still to conquer. Zooming out from the individual GLAM object to the ontology in which it is set, one such world becomes apparent: GLAMs use custom ontologies, and those introduce massive incompatibilities. From a recent article by sadads, we quote the observation that "vocabularies needed for many collections, topics and intellectual spaces defy the expectations of the larger professional communities." A job for the encyclopedist, certainly. But the data-minded Wikimedian has the advantages of Wikidata, starting with its multilingual data, and facility with aliases. The controlled vocabulary — sometimes referred to as a "thesaurus" as term of art — simplifies search: if a "spade" must be called that, rather than "shovel", it is easier to find all spade references. That control comes at a cost.

SVG pedestrian crosses road
Zebra crossing/crosswalk, Singapore

Case studies in that article show what can lie ahead. The schema crosswalk, in jargon, is a potential answer to the GLAM Babel of proliferating and expanding vocabularies. Even if you have no interest in Wikidata as such, simply vocabularies V and W, if both V and W are matched to Wikidata, then a "crosswalk" arises from term v in V to w in W, whenever v and w both match to the same item d in Wikidata.

For metadata mobility, match to Wikidata. It's apparently that simple: infrastructure requirements have turned out, so far, to be challenges that can be met.

To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see below.
Editor Charles Matthews, for ContentMine. Please leave feedback for him. Back numbers are here.
Reminder: WikiFactMine pages on Wikidata are at WD:WFM.
If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 12:38, 15 January 2018 (UTC)

Wikidata weekly summary #295

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)

Wikidata weekly summary #296

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: Mahir256 (as successful)

BitConnect

Not sure if I'm missing some context here, but shouldn't you have sent the article to WP:DRV rather than unilaterally restoring it? I've tagged it as G4. Rentier (talk) 23:19, 17 January 2018 (UTC)

  • I agree that this was an out of process restoration and that Premeditated Chaos should have been consulted first as the closing admin. Under policy, it should be G4 eligible, but any admin who deletes it now could be accused of wheel warring. Unilateral restoration of articles deleted by other administrators as the result of an XfD is not normal. Also, having reviewed that XfD, it was a great close. The only keep !votes were from obviously recruited and affiliated SPA IPs that did not give any policy based rationale and misrepresented their sourcing. The close would likely be endorsed in a heartbeat at a DRV. TonyBallioni (talk) 23:33, 17 January 2018 (UTC)
    • I'm normally fine with people challenging my actions, even in an IAR kind of way, but most admins doing things out-of-process leave a note to the original admin explaining themselves. I'm disappointed that you didn't do so anywhere. AfD is not a numerical vote and restoring this article out-of-process with no discussion because there were more keep votes (which as Tony noted were affiliated SPAs with no policy arguments to stand on) is way out of line. I would appreciate you reversing yourself; I will be taking it to DRV if you choose not to do so. ♠PMC♠ (talk) 23:49, 17 January 2018 (UTC)
It's simple. This company has been in the news in the last 24 hours with coverage on Bloomberg, NY Magazine, Gizmodo, Techcrunch, Fortune, The Verge, Motley Fool, among others. These are not fringe sites or Bitcoin industry newsletters. BitConnect has been highlighted related to the recent crash in cryptocurrency values as regulators put pressure on blockchain operators. I go to check Wikipedia's article about it. It doesn't exist. I check the AfD, and see it's been closed as delete when there's more keep than delete votes. I have a chance to re-create the article given this new notability or start from scratch. I choose the former. This is not a protest of the deletion decision but rather a recognition that BitConnect is notable and the public is served by being able to read about it. I've re-created articles from the depths of deletion without controversy many times for more than a decade. If you concur that the firm is notable (do a quick Google News search) let's get back to writing articles and forgo pointless deletion debates. WP:NOTBUREAUCRACY. -- Fuzheado | Talk 00:05, 18 January 2018 (UTC)
Ok, so, to be clear, you are aware of, and chose to disregard, the fact that AfD is not a numerical vote? And you chose to restore unilaterally rather than discussing it either with me, the closing admin, or taking it to DRV to contest the close? ♠PMC♠ (talk) 00:10, 18 January 2018 (UTC)
With all due respect – it's not about you. Read the above and read Google News. Events of the past week mean BitConnect notability has shot through the roof. An article about BitConnect is justified using very basic WP:Notability standards. Rather than getting hung up on AfD technicalities and bureaucracy, can you recognize that it's about the articles and the reading public? The landscape has changed and the conditions around this article's notability have changed. WP:BEBOLD and let's get back to writing an encyclopedia. -- Fuzheado | Talk 00:23, 18 January 2018 (UTC)
With all due respect - you unilaterally restored an article which at least in part is based on UDPE, making it a violation of the TOU, rather than writing new content of your own (speaking of "let's get back to writing"). At the very least that's irresponsible of you. We're not a bureaucracy, but we do have processes for a reason, and admins are expected to follow them, and to account for themselves fully when they don't. I see now that Anachronist has deleted it under G4. I would suggest that you not restore it again, and I invite you to take it to DRV if you continue to have issues with the closure. ♠PMC♠ (talk) 00:33, 18 January 2018 (UTC)
Not to belabor the point, but I wanted to clarify - are you talking about this Action1212 SPI as the source of the supposed undisclosed paid editing [1] It came back as inconclusive. -- Fuzheado | Talk 01:48, 18 January 2018 (UTC)
Uh Wikipedia:Sockpuppet_investigations/Action1212/Archive#16_October_2017 has them confirmed to be a part of a sock farm using proxies. Sorry to butt in again, but since I'd mentioned it also below, I'm also trying to figure out what you're talking about in case this does go to a DRV. TonyBallioni (talk) 02:10, 18 January 2018 (UTC)
Thanks, I didn't see the additional info below the first section. -- Fuzheado | Talk 02:18, 18 January 2018 (UTC)

Apologies.... I re-deleted the article before I came across this conversation. Had I seen this first, I would have moved on. But so be it.

The proper procedure would be to first ask the deleting admin for an explanation and restoration, and if the response isn't satisfactory, take it to WP:DRV. None of that was done here. My reading of the AFD discussion suggested to me that the close discounted comments from single-purpose editors and block evaders, in which case the consensus would be to delete. This is definitely something to take to DRV, or if Premeditated Chaos agrees the topic is now notable, he can restore it. ~Anachronist (talk) 00:36, 18 January 2018 (UTC)

Anachronist While I think I would be perfectly justified in restoring the article at this point, out of courtesy I am going to ask you to reconsider this deletion first. While the initial restoration may have been out of process, and PC should have been notified first, the most paramount consideration is the encyclopedia itself, not procedures. IAR is a policy and was properly invoked in this case to take an action that this particular admin considered in the best interests of the encyclopedia. You would have been within your rights to delete the article again were it still in the state that it was at the time of its initial deletion, but once Fuzheado added numerous mainstream media sources and original text, the article became a substantially new one that should have been considered on its own merits, and thus your deletion was out of process. Gamaliel (talk) 00:43, 18 January 2018 (UTC)
There are considerations about the article history here as well as PMC noted, and this content is actively harmful to the encyclopedia. You might not agree with my view on that, but it is a view that many people hold and is a valid consideration to take into account at an XfD. The fact that immediately after a G4 tag was placed an apparent SPA came up to remove it demonstrates this. If Fuzheado wants the history back, he should take it to DRV. If he thinks he can write an article on a notable topic on his own without the issues that the first article had, he should write it. The restoration here was the controversial use of the tools, and it is the restoration that needs to gain consensus. TonyBallioni (talk) 00:49, 18 January 2018 (UTC)
The article was properly nominated as WP:G4. There was an AFD, closed as delete, and the article looked to me identical to the deleted one (in fact it was, since it had been restored). In my years on Wikipedia, and 7+ years as an admin, I have never seen a reason to invoke IAR. I find it to be an unnecessary policy. However, now that the article has been re-started afresh, I can restore the history if Fuzheado believes it would be useful. Doing that for a rewritten article is usually not controversial. ~Anachronist (talk) 05:16, 18 January 2018 (UTC)
Anachronist, restoring the history of a page created by a UPE sock farm would be controversial, and is typically not done even when the article is recreated by good faith editors. That was I’m assuming what Rentier and PMC’s main objections were. TonyBallioni (talk) 05:22, 18 January 2018 (UTC)
Got it. The new article is an improvement, IMO. And it contains a lot of sources already. The latest deleted source text can still be emailed or put in user space for reference if it's useful. ~Anachronist (talk) 05:25, 18 January 2018 (UTC)
Anachronist So you criticize Fuzheado for not following procedure and then state that we should ignore an actual policy dating to 2002. Wow. Gamaliel (talk) 17:09, 18 January 2018 (UTC)
Sorry, drawing a blank here. Which policy am I ignoring? ~Anachronist (talk) 17:51, 18 January 2018 (UTC)
@Anachronist and Premeditated Chaos: Sigh. Might we solve this here then, without a lengthy DRV? Would you consider undeleting, Premeditated Chaos, by recognizing that the delete votes in Wikipedia:Articles_for_deletion/BitConnect are no longer on point? The sources now talking about BitConnect are not "few minor trade publications" or "press releases." They are major publications:
Thanks. -- Fuzheado | Talk 00:53, 18 January 2018 (UTC)
I am not going to undelete the article. If you want to write a new article, without the contamination of content written by UDPE, then by all means go ahead. I have zero interest in pursuing an AfD or any other deletion process in that case. It's what you should have done in the first place; we would not be having this conversation if you had. If you want to contest the initial deletion, I invite you to go to DRV so the closure can be scrutinized and discussed by the community. ♠PMC♠ (talk) 02:03, 18 January 2018 (UTC)
I'll create a new article. Thanks. -- Fuzheado | Talk 02:09, 18 January 2018 (UTC)

This is tangential, but still related to BitConnect so I'll add it here: Fuzheado, I've asked this in a couple of other places but no one seems to agree or want to address it. It seems that sometimes, when Google'ing BitConnect Wikipedia, the result comes up pointing to the AfD page which clearly states the article was AfD'd and the conclusion is Delete, and that the page should not be edited, final decision etc. Shouldn't AfD's that have been revised, or otherwise overturned for whatever reason such that the article now actually exists reflect that? Currently the landing page after googleing Wikipedia BitConnect says the following: "The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. ... The result was delete." no further indication the page exists, is there any policy that wikipedia has to put an indication that the page in fact does exist? wouldn't this make sense somewhere at the top of the AfD -> Delete page? Cheesy poof (talk) 02:42, 23 January 2018 (UTC)

(talk page stalker) (Sorry I still had this on my watchlist and thought I'd jump in, feel free to remove if unwanted) Cheesy poof, the AfD page provides a historical record of the decision made at the time of the AfD, which is why the header says not to modify the page. AfD's don't get modified after the fact if the page later gets recreated (which does happen; things change). In contrast, the AfD page will be changed if the result was reversed by the original admin or at DRV.
In this case, the AfD for BitConnect wasn't reversed or overturned. It was closed as delete and it still remains closed as delete - the old content has not been restored even in the history. The article as it exists now is a wholly new work written by Fuzheado, free of the undisclosed paid editing that made the previous content a violation of the TOU, with additional sources to confirm notability. His version of the article basically overcomes all the issues that were raised at the AfD. The AfD decision still applies to the old content, but has no bearing on the existence of the new content. People will be able to tell the article exists again even looking at the AfD because it'll be a blue link, rather than a red one. ♠PMC♠ (talk) 03:42, 23 January 2018 (UTC)
So you are agreeing that there should be an indication that the page exists and the indication that it exists is the font color of the link to the page, correct? (Blue vs Red)? So one issue with that is that the vast majority of wikipedia users don't know what the font color represents, there is absolutely no precedent or similar use of the color red to indicate a page that doesn't exist for most users, and unless they are active wikipedians or have otherwise read through the help pages and such will not know to interpret the font color as such. Also I keep hearing this argument that in fact that page still doesn't exist - I understant the page as written and corresponding history still do not exist, but the *page* exists, it is a wikipedia page, it has the identical web address, identical page article name etc - the point I'm making here is that from a user experience perspective, someone that comes across this page (especially in this case where for whatever reason google is indexing the AfD instead of the actual page) but actually just for any AfD page in which a page of the same name ends up on the encyclopedia, there really should be an indication somewhere indicating it now exists (for example under the Delete item, it could say since this AfD was closed it was decided to create a new page or something along those lines) anyways just a thought Cheesy poof (talk) 05:33, 23 January 2018 (UTC)
AfD is an obscure back office process that the overwhelming majority of people never see. There are very good reasons that we don’t use anything like the system you describe (as has been explained to you now by multiple administrators.) Your pushing this point on multiple pages is starting to become disruptive, as everyone who has talked to you has told you in no uncertain terms that you are wrong. I’m sorry for being this blunt (especially on another user’s talk page), but this is the third place you’ve raise this question and PMC is the third admin to patiently explain to you why we do it this way. You really need to drop this. TonyBallioni (talk) 05:48, 23 January 2018 (UTC)
@TonyBallioni why are you even responding here? I am asking Fuzheado a question on their talk page, if I could have DM'd them I would have. I appreciate your response and time on this, but I don't think Fuzheado's talk page is the place to get aggressive like this? It is totally up to Fuzheado if they want to respond or not to my inquiry, I am not asking anything of you here. Also if you could actually point me to the page explaining why the system I am describing is not used instead of just getting aggressive about it so I can understand I'd greatly appreciate it. Otherwise I don't think we have anything to talk about on this point. Cheesy poof (talk) 11:13, 23 January 2018 (UTC)
Because you’ve been forumshopping this anywhere you can, and you took the response of an arbitrator above to mean the exact opposite of what she said, and I knew that it wasn’t likely that she had all three pages you’ve asked this question on watchlisted. The reason we don’t follow your system is simple: it reflects the consensus at the time of deletion to delete the article, and is kept as a record. Fuzheado unilaterally recreated this page in an entirely new form, so the discussion about the previous article has not been overturned. TonyBallioni (talk) 12:34, 23 January 2018 (UTC)
TonyBallioni, I am new to editing on wikipedia, and I honestly didn't know that it was frowned upon to comment in more than one place - I apologize for doing that. I understand your perspective, although I disagree that I took the response of an arbitrator mean the opposite of what she said. Also, I understand your perspective but you are not the only user/editor/admin on wikipedia. It is possible and likely that others will have a different opinion than you and you should be open to that. I'm pointing out a design flaw or bug and just hoping that someone with more in-depth knowledge has an open mind to pick up on this and one day address it. I am not going to continue engaging with you - your points are all gratefully acknowledge and taken into account. I will point you to the response from user Lourdes who looked into page views and pointed out that the AfD I mentioned had over a thousand page views around the time that I addressed this, and this includes the time when the article actually re-appeared. Most people probably were not aware of the blue vs red color scheme feature and most assumed that because the AfD says Deleted and closed that there was no new page created. I understand this is a fairly fringe case, but it is a fringe case that is likely to happen every time a controversial topic that was previously AfD'd had a new page created will experience, and will experience during the peak in page views and google searches, so that is why I think it is relevant. There are two issues: one is why is Google indexing the AfD instead of the actual page, and two is why is the template so misleading to novice wikipedians in terms of the article not existing. Just trying to help here! here's the link to Lourdes observation: https://en.wikipedia.org/wiki/Wikipedia_talk:Deletion_process#Relisted_AfD_that_ends_up_Keep Cheesy poof (talk) 20:50, 25 January 2018 (UTC)

Wikidata weekly summary #297

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.


Facto Post – Issue 9 – 5 February 2018

Facto Post – Issue 9 – 5 February 2018
m:Grants:Project/ScienceSource is the new ContentMine proposal: please take a look.

Wikidata as Hub

One way of looking at Wikidata relates it to the semantic web concept, around for about as long as Wikipedia, and realised in dozens of distributed Web institutions. It sees Wikidata as supplying central, encyclopedic coverage of linked structured data, and looks ahead to greater support for "federated queries" that draw together information from all parts of the emerging network of websites.

Another perspective might be likened to a photographic negative of that one: Wikidata as an already-functioning Web hub. Over half of its properties are identifiers on other websites. These are Wikidata's "external links", to use Wikipedia terminology: one type for the DOI of a publication, another for the VIAF page of an author, with thousands more such. Wikidata links out to sites that are not nominally part of the semantic web, effectively drawing them into a larger system. The crosswalk possibilities of the systematic construction of these links was covered in Issue 8.

Wikipedia:External links speaks of them as kept "minimal, meritable, and directly relevant to the article." Here Wikidata finds more of a function. On viaf.org one can type a VIAF author identifier into the search box, and find the author page. The Wikidata Resolver tool, these days including Open Street Map, Scholia etc., allows this kind of lookup. The hub tool by maxlath takes a major step further, allowing both lookup and crosswalk to be encoded in a single URL.

To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see below.
Editor Charles Matthews, for ContentMine. Please leave feedback for him. Back numbers are here.
Reminder: WikiFactMine pages on Wikidata are at WD:WFM.
If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 11:50, 5 February 2018 (UTC)

Wikidata weekly summary #298

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.


You got mail

Hello, Fuzheado. 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.

about deleting some photos on Commons. Geraldshields11 (talk) 18:30, 8 February 2018 (UTC)

This Month in GLAM: January 2018



Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #299

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

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

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

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.


This Month in GLAM: February 2018



Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Facto Post – Issue 10 – 12 March 2018

Facto Post – Issue 10 – 12 March 2018

Milestone for mix'n'match

Around the time in February when Wikidata clicked past item Q50000000, another milestone was reached: the mix'n'match tool uploaded its 1000th dataset. Concisely defined by its author, Magnus Manske, it works "to match entries in external catalogs to Wikidata". The total number of entries is now well into eight figures, and more are constantly being added: a couple of new catalogs each day is normal.

Since the end of 2013, mix'n'match has gradually come to play a significant part in adding statements to Wikidata. Particularly in areas with the flavour of digital humanities, but datasets can of course be about practically anything. There is a catalog on skyscrapers, and two on spiders.

These days mix'n'match can be used in numerous modes, from the relaxed gamified click through a catalog looking for matches, with prompts, to the fantastically useful and often demanding search across all catalogs. I'll type that again: you can search 1000+ datasets from the simple box at the top right. The drop-down menu top left offers "creation candidates", Magnus's personal favourite. m:Mix'n'match/Manual for more.

For the Wikidatan, a key point is that these matches, however carried out, add statements to Wikidata if, and naturally only if, there is a Wikidata property associated with the catalog. For everyone, however, the hands-on experience of deciding of what is a good match is an education, in a scholarly area, biographical catalogs being particularly fraught. Underpinning recent rapid progress is an open infrastructure for scraping and uploading.

Congratulations to Magnus, our data Stakhanovite!

3D printing
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see below.
Editor Charles Matthews, for ContentMine. Please leave feedback for him. Back numbers are here.
Reminder: WikiFactMine pages on Wikidata are at WD:WFM.
If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 12:26, 12 March 2018 (UTC)

Wikidata weekly summary #303

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 :)

Wikidata weekly summary #304

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.


DYK for 1838 Georgetown slave sale

On 24 March 2018, Did you know was updated with a fact from the article 1838 Georgetown slave sale, which you recently created, substantially expanded, or brought to good article status. The fact was ... that in 2017 Georgetown University named a building after Isaac Hawkins because his name appeared first on the list of enslaved people sold by them in 1838? The nomination discussion and review may be seen at Template:Did you know nominations/1838 Georgetown slave sale. You are welcome to check how many page hits the article got while on the front page (here's how, 1838 Georgetown slave sale), 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.

Alex Shih (talk) 00:02, 24 March 2018 (UTC)

Wikidata weekly summary #305

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.


Courses Modules are being deprecated

Hello,

Your account is currently configured with an education program flag. This system (the Courses system) is being deprecated. As such, your account will soon be updated to remove these no longer supported flags. For details on the changes, and how to migrate to using the replacement system (the Programs and Events Dashboard) please see Wikipedia:Education noticeboard/Archive 18#NOTICE: EducationProgram extension is being deprecated.

Thank you! Sent by: xaosflux 20:28, 8 March 2018 (UTC)

 Done — xaosflux Talk 17:13, 2 April 2018 (UTC)

Wikidata weekly summary #306

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.


Wikidata weekly summary #307

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.


Facto Post – Issue 11 – 9 April 2018

Facto Post – Issue 11 – 9 April 2018

The 100 Skins of the Onion

Open Citations Month, with its eminently guessable hashtag, is upon us. We should be utterly grateful that in the past 12 months, so much data on which papers cite which other papers has been made open, and that Wikidata is playing its part in hosting it as "cites" statements. At the time of writing, there are 15.3M Wikidata items that can do that.

Pulling back to look at open access papers in the large, though, there is is less reason for celebration. Access in theory does not yet equate to practical access. A recent LSE IMPACT blogpost puts that issue down to "heterogeneity". A useful euphemism to save us from thinking that the whole concept doesn't fall into the realm of the oxymoron.

Some home truths: aggregation is not content management, if it falls short on reusability. The PDF file format is wedded to how humans read documents, not how machines ingest them. The salami-slicer is our friend in the current downloading of open access papers, but for a better metaphor, think about skinning an onion, laboriously, 100 times with diminishing returns. There are of the order of 100 major publisher sites hosting open access papers, and the predominant offer there is still a PDF.

Red onion cross section

From the discoverability angle, Wikidata's bibliographic resources combined with the SPARQL query are superior in principle, by far, to existing keyword searches run over papers. Open access content should be managed into consistent HTML, something that is currently strenuous. The good news, such as it is, would be that much of it is already in XML. The organisational problem of removing further skins from the onion, with sensible prioritisation, is certainly not insuperable. The CORE group (the bloggers in the LSE posting) has some answers, but actually not all that is needed for the text and data mining purposes they highlight. The long tail, or in other words the onion heart when it has become fiddly beyond patience to skin, does call for a pis aller. But the real knack is to do more between the XML and the heart.

To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see below.
Editor Charles Matthews, for ContentMine. Please leave feedback for him. Back numbers are here.
Reminder: WikiFactMine pages on Wikidata are at WD:WFM.
If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 16:25, 9 April 2018 (UTC)

This Month in GLAM: March 2018



Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #308

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.


Your draft article, Draft:The Jade Pendant

Hello, Fuzheado. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "The Jade Pendant".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply edit the submission and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.

If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. JMHamo (talk) 20:53, 22 April 2018 (UTC)

Wikidata weekly summary #309

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

Looks like I've connected to what I needed with John Cummings & Jens Ohlig, so I won't bother you with the "further details" I promised when we talked on Sunday. - Jmabel | Talk 19:42, 25 April 2018 (UTC)

Great to hear it. Good meeting you in Berlin! -- Fuzheado | Talk 20:31, 25 April 2018 (UTC)

Wikidata weekly summary #310

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

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.


This Month in GLAM: April 2018



Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #312

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.


Wikidata weekly summary #313

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.


Editor of the Week

Editor of the Week
Your ongoing efforts to improve the encyclopedia have not gone unnoticed: You have been selected as Editor of the Week in recognition of your teamwork. Thank you for the great contributions! (courtesy of the Wikipedia Editor Retention Project)

User:Buster7 submitted the following nomination for Editor of the Week:

Fuzheado, a most interesting User, has been a mentor to over 80 students in his long WP career and teaches the power of collaborative editing. Recently, he was one member of a group of editors that displayed excellent teamwork; all working toward a common goal of managing and manipulating input into an article that was in flux; an article that's "real life history" was developing daily. This team of editors, of which Fuzheado was a part, deserve separate individual recognition as Editors of the Week because they came together and worked on location maps, before and after the event, and they did a fantastic job. One need only look at Talk:March For Our Lives#Maps to see the positive interactions that resulted in a timely and quality addition to the encyclopedia. Fuzheado has been a teacher and leader of the Encyclopedia for many years. This is but a small recognition for all he has done.

You can copy the following text to your user page to display a user box proclaiming your selection as Editor of the Week: 

{{User:UBX/EoTWBox}}

Thanks again for your efforts! ―Buster7 ☎ 14:17, 29 April 2018 (UTC)

Belated congrats! ---Another Believer (Talk) 18:12, 26 May 2018 (UTC)

Facto Post – Issue 12 – 28 May 2018

Facto Post – Issue 12 – 28 May 2018

ScienceSource funded

The Wikimedia Foundation announced full funding of the ScienceSource grant proposal from ContentMine on May 18. See the ScienceSource Twitter announcement and 60 second video.

A medical canon?

The proposal includes downloading 30,000 open access papers, aiming (roughly speaking) to create a baseline for medical referencing on Wikipedia. It leaves open the question of how these are to be chosen.

The basic criteria of WP:MEDRS include a concentration on secondary literature. Attention has to be given to the long tail of diseases that receive less current research. The MEDRS guideline supposes that edge cases will have to be handled, and the premature exclusion of publications that would be in those marginal positions would reduce the value of the collection. Prophylaxis misses the point that gate-keeping will be done by an algorithm.

Two well-known but rather different areas where such considerations apply are tropical diseases and alternative medicine. There are also a number of potential downloading troubles, and these were mentioned in Issue 11. There is likely to be a gap, even with the guideline, between conditions taken to be necessary but not sufficient, and conditions sufficient but not necessary, for candidate papers to be included. With around 10,000 recognised medical conditions in standard lists, being comprehensive is demanding. With all of these aspects of the task, ScienceSource will seek community help.

OpenRefine logo, courtesy of Google
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see below.
Editor Charles Matthews, for ContentMine. Please leave feedback for him. Back numbers are here.
Reminder: WikiFactMine pages on Wikidata are at WD:WFM. ScienceSource pages will be announced there, and in this mass message.
If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 10:16, 28 May 2018 (UTC)

Wikidata weekly summary #314

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.


Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Fuzheado/Archive_8&oldid=1145976071"