Hey, I know I reverted your edits, but would like to extend an offer to work with you to get the statements correct. I've been working on Wikidata Every Politician which has similar succession and office holder boundaries.
For positions like the judges replacing another - on the position's talk page (or page of your own) you can create tables from the format I suggested with Template:PositionHolderHistory on Wikidata. Which Talk:Q5589680https://www.wikidata.org/wiki/Talk:Q5589680 is a good example of the extra help it creates to check consistency of start/end and persons replaced or replaced by, but this may not work if there are more than one office holders for the Q (which might be split to seat if able to be distinguished by some differentiation consistently). If you have other questions if your format is correct, I encourage to ping me and/or post to Wikidata:Project_chat. Wolfgang8741 says: If not you, then who? (talk) 14:52, 17 March 2022 (UTC)[reply]
@Wolfgang8741: I ran the edits from OpenRefine, and I still have the files on PAWS (here, if you can view them). I'm not entirely sure what format you want the data in, but from your example at BOTREQ, it appears it needs data other than the successor and judge. By the way, please just ask me to revert my edits, because now I have about 500 notifications. Thanks for taking the time to clean up my mess! ― Qwerfjkltalk 18:25, 17 March 2022 (UTC)[reply]
@Qwerfjkl: Apologies for the excessive notices from the reverts, my first time catching something like this at scale. I do not have permission to view your openrefine, but an example schema config for a position would look more like the following screenshots from openrefine and based on creating this demo you may also need to create some of the positions and clean up some existing Qs for the judge positions. Yes, you probably need to create a few more columns to make a statement that fits both the established practice. I think most positions require a start time which if they were confirmed, but never started the start time would be no value I guess unless the start is at the point of appointment. That is not a nuance I know the answer. It may be that confirmation date needs a new property to represent given the difference between appointed, confirmed, and starting in the role.
A quick look for Judge of the United States District Court for the Eastern District of Michigan (or similar) didn't exist - now Q111274584 and Q23933765 wasn't linked to the court - checked by viewing What links here.
You can create the position name in plain text in a new column from the table to try to mach what the position should be called and if they don't resolve, create new positions which would be another schema to configure. I'd look to Q20706330 to know what should be added when creating any new instances of judge positions related to a court listed in the table. Ideally the death date column wouldn't include the age as it makes matching less effective.
The new position schema would be a different statement you can export together or do this in two rounds. The first round to create all missing positions then second to add all the statements for persons holding those positions. For each position adding their respective qualifier of "start time" and "end time" as well as "replaces" and "replaced by" qualifiers for the position, the confirmation date (which I don't know a good property to use as a qualifier so you might ask on wikidata project chat) and "appointed by" property also would be a qualifier for the position.
Two more columns are needed on to the table which would include the person the judge replaces for bidirectional movement through the statement and the position that they will hold which is part of the "Court" that you currently have in the table as mentioned above. I hope this helps to clarify a little? Wolfgang8741 says: If not you, then who? (talk) 19:32, 17 March 2022 (UTC)[reply]
@Wolfgang8741: clean up some existing Qs for the judge positions - What exactly do you mean by this? I used {{Get QID}}, which follows redirects, so might be inaccurate. I could ignore redirects if that would help. I think most positions require a start time which if they were confirmed, but never started the start time would be no value I guess unless the start is at the point of appointment. - I have additional data where I initially got the data from, mentioned in the BOTREQ. Ideally the death date column wouldn't include the age as it makes matching less effective. - I can easily use some regex to remove the template that gives the age (or just subst it and remove the age). Two more columns are needed on to the table which would include the person the judge replaces for bidirectional movement - harder to do automatically, though maybe possible in OpenRefine? ― Qwerfjkltalk 20:42, 17 March 2022 (UTC)[reply]
clean up some existing Qs for the judge positions - not all existing positions link to their respective court Qid so to get the most out of the linked data, you may need to verify positions link to courts, have applies to jurisdiction values and other cleanup tasks to have consistent statements across the positions. I'm not aware of a model existing for judge positions, but basing off the example cited above it should be a good template of what statements should be on the judge's position.
I think most positions require a start time which if they were confirmed, but never started the start time would be no value I guess unless the start is at the point of appointment. - One the postion held statements require a start time for context of period of time the person was in the role. Though start time is subjective possibly to different interpretation based on the job. Defining what is the start time for a judge and if it is the same or different from when they are confirmed. I'm talking more about how to represent the data. Without a start time the position statement is flagged as missing that qualifier unless the value is set to unknown or no value.
Ideally the death date column wouldn't include the age as it makes matching less effective. - This is more of a comment of table and data design than something hard to cleanup with regex or openrefine split column.
Two more columns are needed on to the table which would include the person the judge replaces for bidirectional movement The infoboxes (if accuracte) could be one source to extract the value or if you have another source at your disposal with this information. This was more of a comment comparing the table to what might be needed to make a more useful statement for the position. Really its not critical, but the more complete the statement the easier it is to query, walk through the links in either direction, visualize, etc. Wolfgang8741 says: If not you, then who? (talk) 20:57, 17 March 2022 (UTC)[reply]
@Wolfgang8741: I think I'm going to re-generate the table, using updated data, so all rows have a successor. Then, I can get the predecessor, which is typically just above it in the infobox. I think I've created most of the positions needed. Can you see any that are missing? (I wrote a QuickStatements batch to create a few.) ― Qwerfjkltalk 21:12, 22 March 2022 (UTC)[reply]
It would help to provide to link(s) to resources you want me to review. I believe you wanted me to look at batch 79292? I don't have anything to compare to for a complete list off hand and courts are not my area of expertise. Format wise for the positions, it would be useful given the defined boundaries to add the position's the jurisdiction with P1001 as well as which court the position is affiliated via P361 of which court ie Q111295760 is part of Q7889771. A query for the list of courts to be part of: https://w.wiki/4yjB When you have the position statements ready, I'll check them out too. — Preceding unsigned comment added by Wolfgang8741 (talk • contribs) 21:43, 22 March 2022 (UTC)[reply]
@Wolfgang8741: Am I right in saying that P1001 should always be Q30? If not, can you give an example of what it should be? ― Qwerfjkltalk 20:59, 23 March 2022 (UTC)[reply]
No, the US is too broad for jurisdiction as these courts either have jurisdiction of an entire state's geographic area or sub region of a state's geographic area. An example would be the Q111295760 the first sentence states the jurisdiction to the entire state of Delaware https://en.wikipedia.org/wiki/United_States_District_Court_for_the_District_of_Delaware and appeals to the 3rd circuit as this map shows (not sure if this is most current, but it would be a guide on what Qids might be named or need to be created). While in this case I think the jurisdiction and state area are the same it probably requires a separate Qid to represent the jurisdiction that is equivalent in area to the state of Delaware as it is instance of a jurisdiction rather than instance of a state (so the concepts are similar, but different on type). An example of a jurisdiction only of a portion of a state is the Western District of Washington Q111295799 which would be a part of the state of Washington and a second Qid would represent the Eastern District of Washington. The development of the model for representing the jurisdictions may be better suited for the Wikidata Project Chat discussion.
There would be a relation between the jurisdiction and the state as part of the state of Delaware with different Qids, instance of, and description similar to how electoral districts are sub components of the state, but part of the state. This is where creating new positions have a lot of inter dependencies and deciding how to model can enable teasing out the differences between concepts with the same name, but in doing so allows for much richer queries once the Qids exist. New Qid for the district jurisdictions would probably be an instance of Q5982983 or a subclass of this to specify US district jurisdictional areas as a group or something like this. You might query the instances of this Qid to find what jurisdictions exist and for those that do not, create the Qid for each of the district areas as Q5982983 named the same as Q7889771 (United States District Court for the District of Delaware), but has an instance of Q5982983 or a subclass of Q5982983 being "United States District Court Jurisdiction" which would allow for alternative naming of the jurisdictions as "District of Delaware" with description "jurisdiction of the District Court. I was thinking of the jurisdictions to be modeled similarly to how electoral districts ie Q192611 and modeled, but it may be this concept needs more eyes and would benefit from a modeling discussion on the Wikidata project chat or related Wikidata project. This all said, if this is getting too complex, the jurisdiction can be left off for a later person to complete or put on hold to further discuss how to model them. — Preceding unsigned comment added by Wolfgang8741 (talk • contribs) 01:32, 24 March 2022 (UTC)[reply]
Great, just some cleanup of the duplicates created like Q106071810 and you should be good to add these to the people holding the position with the qualifiers you wanted to add for replaced and replaced by, etc.Wolfgang8741 says: If not you, then who? (talk) 18:25, 24 March 2022 (UTC)[reply]
Wait, are the judges you want to create District Court Judges or Court of Appeals Judges? I think the subclass is incorrect. The name of the position d:Q106071810 aka Judge of the United States District Court for the Southern District of New York would imply this is a district court judge ie subclass of d:Q58412318 not d:Q58412251. Wolfgang8741 says: If not you, then who? (talk) 18:32, 24 March 2022 (UTC)[reply]
@Wolfgang8741: Do you know how to replace the property using QuickStatements? I keep on getting errors, and I can't check them as I'm on a mobile device. (List at User:Qwerfjkl/sandbox). ― Qwerfjkltalk 19:44, 26 March 2022 (UTC)[reply]
Hello Qwerfjkl, I wanted to ask you a question regarding my bot request for the removal of an undue weight statement form around 3,000 Poland related articles. At this point I'm not seeing that it's being picked up by any of the bot editors, thus can you advise if the reason for it is that this is not the correct venue for such a request or perhaps that I'm missing certain steps in the request process? --E-960 (talk) 22:34, 19 March 2022 (UTC)[reply]
Ok, I see, thank you for the clarification. --E-960 (talk) 16:18, 20 March 2022 (UTC)[reply]
Many thanks for the ping on the BRFA. --E-960 (talk) 15:52, 3 April 2022 (UTC)[reply]
Hello again Qwerfjkl, I just had a quick look on the bot request [1] page and it looks like the final approval was granted following the test run, so things should be good to go. --E-960 (talk) 11:22, 14 April 2022 (UTC)[reply]
E-960, Yes, I know (I was notified below). Unfortunately, I've been busy lately, and unable to complete the bot task. All the statements have.been removed now. Qwerfjkltalk 16:01, 14 April 2022 (UTC)[reply]
That is now very outragous.. There were multiple discussions about that, and there was no consensus (especially because there is nothing wrong about that correct sentence).. And now I see DESPITE ALL THIS E-960 still tries to erase this sentence, he willfully just ignored all this and waited some time and now he's doing the same even with a bot.. E-960 is obviously trying to vandalize Wikipedia long time and now he is doing it with the support of bots.. after he failed multiple times to try it manually. Besides that, some accounts got blocked for erasing that from many articles. This should stop right away. --Jonny84 (talk) 19:39, 14 April 2022 (UTC)[reply]
Jonny84, You are the only user who has objected, with no clear reason (several editors supported). That does not constitute no consensus. In addition, you did not object to the BRFA, even after I linked to it in the discussion. There was also a week left after the trial for any objections, yet there were none. Whilst there is indeed nothing wrong about that correct sentence, it has undue weight. You make a serious claim that @E-960 has been trying to vandalize Wikipedia for a long time. Could you please give any other cases/examples, or explain why you have not taken this to WP:ANI (although I don't recommend you do)? You say some accounts got blocked for erasing that from many articles - which accounts? Please try to remain civil and assume good faith. Qwerfjkltalk 20:04, 14 April 2022 (UTC)[reply]
Qwerfjkl, sounds good, thanks. Btw, I noticed that on some articles such as this on Mokre, Goleniów County, the phrase is still there, perhaps there is a punctuation variation or something that threw off the bot criteria. --E-960 (talk) 20:55, 14 April 2022 (UTC)[reply]
I'm just a human and I'm just occasionally here and I'm not contributing often here, so I can't observe every edit in here.. Also I'm not following every single edit by E-960.. I just realised today, that some pages on my watchlist got changed by bots. 1) There was also a bot or an author who put this information in before, so somebody thought this is important to the history and the articles. 2) Nobody had a problem with that for over 15 years besides some already blocked accounts and besides them only E-960.. So there was a consensus with that.. 3) There was also no Poland from 1795 till 1918... So missing this information, brings also a big undue weight to Wikipedia articles.. So I'm wishing there would be a mention of that fact to be put in. If we start with argumenting about undue weight, then we should go further and not just pick some selected passages. Erasing the mention of Germany, to places which belonged for centuries to Germany, brings also an even bigger undue weight to this articles, for me it's even faking history. 4) This discussions were just in March: [2]... Other users suggested to expand the articles for example. He didn't accepted the advice and didn't even tried to expand any of this articles.. He just did, what he tried before, to erase it, just on another wikipedia page. So how could there be a consensus? Also I'm related with the German minority of Poland, I'm still remembering how he tried to erase data about them once, so this current actions also have a very bad taste to me.. --Jonny84 (talk) 20:58, 14 April 2022 (UTC)[reply]
I'd like to point out, that here was no "Germany" before 1871. Pls see German Reich and Legal status of Germany articles, when German actually became a nation state. Also, Pomerania was Polish, Danish and Swedish, before becoming Prussian and subsequently "German". So, please stop with the one-sided claims about eternal German lands. --E-960 (talk) 21:09, 14 April 2022 (UTC)[reply]
(edit conflict) @E-960, I'll finish this tomorrow (I missed insource:/Before 1945 the area was part of \[\[Germany/). @Jonny84, this has already been discussed in the previous discussion. While, yes, expanding the articles would be preferable, it would take a while to do to over 5000 articles. As other users have said, the statement on its own is WP:UNDUE. I don't think further argument is productive or helpful. ― Qwerfjkltalk 21:11, 14 April 2022 (UTC)[reply]
It's a fact, that Silesia, East Prussia and Pomerania were part of the German Empire from 1871 till 1945, so erasing this sentence is just simple POV-pushing, which isn't wanted on Wikipedia. So this actions are just against Wikipedia policies. BTW. before 1871 there was the North German Confederation and the German Confederation. You can ignore that, but then this is just POV-pushing. With the same argument, there was also no Poland before 1918.. --Jonny84 (talk) 21:21, 14 April 2022 (UTC)[reply]
The next Wikidata+Wikibase office hours will take place on Wednesday, April 20th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
April 22nd - 24th, from Wiki Mentor Africa, A three days workshop on Linking biodiversity data through wikidata using Webaps and jupyter notebooks to attend, register here
May 5th: Wikidata Bug Triage Hour, open discussion. Come with your favorite Phabricator task and we will improve its description together.
DigAMus goes Wikidata workshop: make digital projects in museums visible and findable. April 29, 3-5 p.m. TIB Open Science Lab. Register here.
Live Coding - PyORCIDAtor, integrating ORCID with Wikidata - YouTube
How to add location coordinates to Wikidata Items (in Dagbani) - YouTube
Bundestag + Wikidata = Open Parliament TV (in German) - YouTube
Tool of the week
Glitter another R package to write SPARQL queries and query Wikidata and other SPARQL endpoints. This package provides a domain specific language to write queries directly from R.
Conzept is a topic-exploration tool based on Wikidata and other information sources.
Other Noteworthy Stuff
The Wikidata MOOC (online course) has been developed by Wikimedia France, involving several French-speaking Wikidata editors. The first version of the course will start on April 26 (in French only - registration here)
Wikibase cloud update (April): the closed beta of Wikibase.cloud is planned to start in mid-April. If you want to apply for closed beta access, please register with this form.
Lexicographical data: Continued work on the new Special:NewLexeme page. We worked on displaying error messages and inferring the spelling variant from the language. We also looked into the non-JavaScript version of the page.
REST API: Worked on conditional requests (do not return data the client already has) and authorization.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
There is a new public status page at www.wikimediastatus.net. This site shows five automated high-level metrics where you can see the overall health and performance of our wikis' technical environment. It also contains manually-written updates for widespread incidents, which are written as quickly as the engineers are able to do so while also fixing the actual problem. The site is separated from our production infrastructure and hosted by an external service, so that it can be accessed even if the wikis are briefly unavailable. You can read more about this project.
On Wiktionary wikis, the software to play videos and audio files on pages has now changed. The old player has been removed. Some audio players will become wider after this change. The new player has been a beta feature for over four years. [3][4]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 April. It will be on non-Wikipedia wikis and some Wikipedias from 13 April. It will be on all wikis from 14 April (calendar).
Tol, sorry! I don't normally use JWB for bot editing, and forgot its generator isn't restricted to mainspace. The bot task is now complete, so should be fine now. (I did notice a discussion from ~12 years ago at Talk:Wielbark, Warmian-Masurian Voivodeship#History, however.) Happy editing! Qwerfjkltalk 15:18, 15 April 2022 (UTC)[reply]
Hello and welcome to the April newsletter, a brief update of Guild activities since December 2021.
Election results: Jonesey95 retired as lead coordinator. Reidgreg was approved to fill this role after an 18-month absence from the coordinator team, and Baffle gab1978 was chosen as an assistant coordinator following a one-year break. Dhtwiki, Miniapolis and Tenryuu continued on as long-standing assistant coordinators.
January Drive: Of the 22 editors who signed up, 16 editors claimed 146 copy edits including 45 requests. (details)
February Blitz: This one-week effort focused on requests and a theme of Africa and African diaspora history. Of the 12 editors who signed up, 6 editors recorded 21 copy edits, including 4 requests. (details)
March Drive: Of the 28 editors who signed up, 18 claimed 116 copy edits including 25 requests. (details)
April Blitz: This one-week copy editing event has been scheduled for 17–23 April, sign up now!
Progress report: As of 11 April, copy editors have removed approximately 500 articles from the backlog and completed 127 copy-editing requests during 2022. The backlog has been hovering at about 1,100 tagged articles for the past six months.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Reidgreg, Baffle gab1978, Dhtwiki, Miniapolis and Tenryuu
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
Question from Scranley (19:04, 15 April 2022)[edit]
Conflict of interest when edited my own page? --Scranley (talk) 19:04, 15 April 2022 (UTC)[reply]
Scranley, you have declared a COI with Seamus Cranley (game designer) - a page that does not exist. If you plan to make a draft of this, that's fine, but there's no COI if the page doesn't exist. Do you have a specific question (or could you phrase it more clearly)? Qwerfjkltalk 20:11, 15 April 2022 (UTC)[reply]
User talk:Qwerfjkl, Thank you, I thought it was an error and realized the page edit worked.. I am now creating the draft page.. Seamus Cranley (game designer). — Preceding unsigned comment added by Scranley (talk • contribs) 20:17, 15 April 2022 (UTC)[reply]
Feedback request: WikiProjects and collaborations request for comment[edit]
Speedy deletion nomination of ISO 639 talk:xghu[edit]
Hello, Qwerfjkl,
Welcome to Wikipedia! I edit here too, under the username Yeeno, and I thank you for your contributions.
I wanted to let you know, however, that I have tagged ISO 639 talk:xghu for deletion, because it doesn't appear to contain any encyclopedic content. You may find our guide for writing quality articles to be extremely informative. Also, you may want to consider working on future articles in draft space first, where they cannot be deleted for lacking content.
If you feel that the article shouldn't be deleted and want more time to work on it, you can contest this deletion but please don't remove the speedy deletion tag from the top. If the page is already deleted by the time you come across this message and you wish to retrieve the deleted material, please contact the deleting administrator.
For any further query, please leave a comment here and prepend it with {{Re|Yeeno}}. And, don't forget to sign your reply with ~~~~ . Thanks!
Message delivered via the Page Curation tool, on behalf of the reviewer.
Speedy deletion nomination of ISO 639-6 talk:xghu[edit]
Hello, Qwerfjkl,
Welcome to Wikipedia! I edit here too, under the username Yeeno, and I thank you for your contributions.
I wanted to let you know, however, that I have tagged ISO 639-6 talk:xghu for deletion, because it doesn't appear to contain any encyclopedic content. You may find our guide for writing quality articles to be extremely informative. Also, you may want to consider working on future articles in draft space first, where they cannot be deleted for lacking content.
If you feel that the article shouldn't be deleted and want more time to work on it, you can contest this deletion but please don't remove the speedy deletion tag from the top. If the page is already deleted by the time you come across this message and you wish to retrieve the deleted material, please contact the deleting administrator.
For any further query, please leave a comment here and prepend it with {{Re|Yeeno}}. And, don't forget to sign your reply with ~~~~ . Thanks!
Message delivered via the Page Curation tool, on behalf of the reviewer.
(talk page watcher) Looks like this and the above were a glitch in User:Enterprisey/AFCRHS.js. I've moved the pages to the correct locations without redirect. @Enterprisey: I think the issue is with L658; there should be a check in there as to whether the colon delineates a real namespace. -- Tamzin[cetacean needed] (she/they) 23:56, 16 April 2022 (UTC)[reply]
The next Wikidata+Wikibase office hours will take place on Wednesday, April 20th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
LD4 Wikibase Working Hour: Learn about Wikibase system exploration, data model development, and the road ahead for Digital Scriptorium. When: Thurs. 21 April 2022, 3PM Eastern US (time zone converter). Where: Registration Link
WeDigBio Transcription workflow "...blogpost...showing how I go from finding the name of a collector when transcribing labels to adding them to Wikidata & then linking them to their collections via Bionomia."
Bird O'Clock! is a tool based on Wikidata and other data sources that shows pictures and numbers from actual people counting actual birds in the actual world!
Tiago's Coin Herbarium is a coin collection depicting different plant information displayed via Wikidata SPARQL queries.
Lexicographical data: Worked on inferring the spelling variant from the language's Item on the new Special:NewLexeme page and started building a little help box on the special page to explain what lex. data is.
REST API: Getting closer to having a first version of the REST API that returns Item data.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 April. It will be on non-Wikipedia wikis and some Wikipedias from 20 April. It will be on all wikis from 21 April (calendar).
Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 19 April at 07:00 UTC (targeted wikis) and on 21 April at 7:00 UTC (targeted wikis).
On selected wikis, 50% of logged-in users will see the new table of contents. When scrolling up and down the page, the table of contents will stay in the same place on the screen. This is part of the Desktop Improvements project. [5]
Message boxes produced by MediaWiki code will no longer have these CSS classes: successbox, errorbox, warningbox. The styles for those classes and messagebox will be removed from MediaWiki core. This only affects wikis that use these classes in wikitext, or change their appearance within site-wide CSS. Please review any local usage and definitions for these classes you may have. This was previously announced in the 28 February issue of Tech News.
@Johnbaxter329, you can add [[File: + the file name + ]], with the file being from either the file nanespace, or from Commons. Qwerfjkltalk 06:22, 19 April 2022 (UTC)[reply]
Visible anchor removal blowing away large portions of articles[edit]
Hello, good day to you. I’m an artist and am trying to create a a Wikipedia page profile for myself. How do I do that ? --Justbizzsisko (talk) 05:46, 21 April 2022 (UTC)[reply]
@Justbizzsisko, Welcome! Creating a new article from scratch is extremely challenging, and new editors are strongly recommended to spend a few months learning how Wikipedia works, by making improvements to some of our existing six million articles before trying it. When you do decide to have a go at a new article, you are highly encouraged to read WP:Your first article. If you haven't already also check out WP:TUTORIAL; it's a lot of fun! See WP:AUTOBIO as well. Happy editing! Qwerfjkltalk 06:04, 21 April 2022 (UTC)[reply]
Wikipedia:RedWarn is left at its current location since it is the name of the legacy script. It is also used by the current RedWarn script for default data. Do NOT move any more pages. Chlod (say hi!) 13:35, 22 April 2022 (UTC)[reply]
@Chlod: Sorry, that was an accident, my bad. I think I've reverted all the moves. Qwerfjkltalk 13:39, 22 April 2022 (UTC)[reply]
disambiguates only one extant Wikipedia page and whose title ends in "(disambiguation)" (i.e., there is a primary topic);
disambiguates zero extant Wikipedia pages, regardless of its title; or
is an orphaned redirect with a title ending in "(disambiguation)" that does not target a disambiguation page or page that has a disambiguation-like function.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator. Shhhnotsoloud (talk) 08:32, 24 April 2022 (UTC)[reply]
I see you are doing some closures at CFD and that area could really use some extra help. There are some very experienced non-admin closers at CFD so if you have questions, I'm sure they could be of some assistance to you. Nice to run into your work again! Hope you are well. LizRead!Talk! 23:30, 24 April 2022 (UTC)[reply]
It can be a little tricky getting the CSD tags correct but everything looks fine. I think we have more non-admins closing CFD discussions than admins right now. We can always use more admins though, maybe a thought you can keep in the back of your mind for the future. LizRead!Talk! 22:36, 26 April 2022 (UTC)[reply]
Actually, there is a problem with Category:Fishing in the European Union. Categories need to be emptied before they can be deleted or else we end up with red link categories on pages which, according to WP:REDNO, must be avoided. So this one isn't ready for deletion yet. LizRead!Talk! 22:39, 26 April 2022 (UTC)[reply]
Liz, thanks, I must have been tired when I closed that one. Emptied now. ― Qwerfjkltalk 06:07, 27 April 2022 (UTC)[reply]
The next Wikibase live session is 15:00 UTC on Thursday 28th April 2022 (17:00 Berlin time). What are you working on around Wikibase? You're welcome to come and share your project with the community.
Cultural Venues Datathon: April 25 - May 2, 2022. The aim of this online editing event is to increase the quantity and quality of performing arts building/venue items.
Daily guided editing sessions will be facilitated in English and in French between April 25 and April 29.
Wikidata Coffee Breaks From April 25 - April 29, 2022 to fill in missing information on Swiss Performing Arts Institutions and venues.
From May 4 to 18 there will be the International Museum Day - Wikidata competition. The aim is to improve data about museums in the countries and regions participating. Contributors from anywhere can take part.
The Wikimedia Hackathon will take place online on May 20–22, 2022. If you’re interested in presenting something around Wikidata and Wikibase during the hackathon, don’t wait too long to book a slot: Wikimedia Hackathon 2022/Schedule#The Wikidata and Wikibase Room.
Lexicographical data: Worked on showing the name of language variants in the language variant selector and added the new information box to help people get a better understanding of lex. data.
REST API: Finished the initial implementation of the endpoint for getting data for a full Item and discussed feedback, testing and roll-out plans.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
On many wikis (group 1), the software to play videos and audio files on pages has now changed. The old player has been removed. Some audio players will become wider after this change. The new player has been a beta feature for over four years. [10][11]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 April. It will be on non-Wikipedia wikis and some Wikipedias from 27 April. It will be on all wikis from 28 April (calendar).
Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 26 April at 07:00 UTC (targeted wikis).
Some very old browsers and operating systems are no longer supported. Some things on the wikis might look weird or not work in very old browsers like Internet Explorer 9 or 10, Android 4, or Firefox 38 or older. [12]
Did you mean to tag this category for deletion? I noticed that it was empty and then saw the CFD had been closed but I wanted to confirm it with you before deleting the page. Take care. LizRead!Talk! 17:41, 28 April 2022 (UTC)[reply]
Hi, I meant to tag it for deletion. Thanks for checking, Liz. ― Qwerfjkltalk 19:32, 28 April 2022 (UTC)[reply]
This also happened with Category:Wikipedia extended confirmed users. There is not point in closing a deletion discussion if you don't follow through and take action on the consensus decision. Do you know what to do if the decision is to merge or rename categories? LizRead!Talk! 23:42, 28 April 2022 (UTC)[reply]
Liz, sorry, I'm not sure what happened. I'm sure I tagged that category; I'll try to double-check. I think this was caused by inputting the link (in Twinkle) to the CfD with [[...]], and then clicking off the message warning against this. Regarding renaming categories, I can't move category pages. If the decision is merge, then all of the pages in the merged category should be moved into the category.being merged into. ― Qwerfjkltalk 06:09, 29 April 2022 (UTC)[reply]
Wikidata Bug Triage Hour on May 5th at 16:00 UTC, online. Open discussion - you can bring a Phabricator ticket that you care about or that needs to be improved.
May 3rd. Next Linked Data for Libraries LD4 Wikidata Affinity Group call: The call will include presentations on two projects using Wikidata to enhance discoverability of archival and museum collections. Sharon Garewal (JSTOR) will present “Adding Wikidata QIDs to JSTOR Images,” and Daniela Rovida and Jennifer Brcka (University of Notre Dame) will present “‘Archives At’: An opportunity to leverage MARC to create Linked Open Data.” [13]
Workshop "Wikidata, Zotero and Cita": tools to understand the construction of knowledge (in Spanish) - YouTube
Georeferencing cultural heritage on Wikidata - YouTube
Theory of Machine Learning on Open Data: The Wikidata Case by Goran S. Milovanovic - YouTube
Introduction to SPARQL (Wikidata Query Service (in Czech) - YouTube
Wikidata: A Knowledge Graph for the Earth Sciences - YouTube
Tool of the week
User:Nikki/LowercaseLabels.js - is a userscript that adds a button when editing labels to change the text to lowercase.
EqualStreetNames - is a tool that maps the inequality of name attributions.
Other Noteworthy Stuff
OpenRefine is running its two-yearly user survey! Do you use OpenRefine? Then fill in the survey to tell us how and why you use OpenRefine. Results and outcomes will inform future decisions about the tool.
The April update for the Wikidata Query Service scaling project is now available.
Lexicographical data: We are finishing up the information box that should help new users understand quickly what lexicographical data is. We also added the help text to encourage people to check if the Lexeme already exists before creating one.
REST API: We started working on the REST routes to get all statements of an Item and retrieve a single statement from an Item.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
On all remaining wikis (group 2), the software to play videos and audio files on pages has now changed. The old player has been removed. Some audio players will become wider after this change. The new player has been a beta feature for over four years. [14][15]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 3 May. It will be on non-Wikipedia wikis and some Wikipedias from 4 May. It will be on all wikis from 5 May (calendar).
Future changes
The developers are working on talk pages in the Wikipedia app for iOS. You can give feedback. You can take the survey in English, German, Hebrew or Chinese.
Several CSS IDs related to MediaWiki interface messages will be removed. Technical editors should please review the list of IDs and links to their existing uses. These include #mw-anon-edit-warning, #mw-undelete-revision and 3 others.
Hi Qwerfjkl, I'm having issues adding templates to redirect's with twinkle. Can you help? Maybe with some screenshots or photos. Comr Melody Idoghor(talk) 21:44, 3 May 2022 (UTC)[reply]
@Idoghor Melody, To use rcats with Twinkle, when on a redirect, select TW → Tag, and then select any rcats to tag the redirect with. ― Qwerfjkltalk 06:05, 4 May 2022 (UTC)[reply]
Thanks again for helping erase the tens of thousands of "Wiki(p/m)edia list article" descriptions. I think it was such a success that we should expand the bot's scope to remaining articles not beginning with "List", and maybe even expand the strings it searches for (looking at you, "Aspect of history"). And I'm sure you noticed that there's a steady flow of editors adding back the removed descriptions. What do you think? Thrakkx (talk) 01:56, 6 May 2022 (UTC)[reply]
@Thrakkx, to expand the bot's scope, there first needs to be a discussion (probably at WT:SD) in support of the idea. As for editors adding back these short descriptions, it would be simple to just run the bot again on the pages. ― Qwerfjkltalk 06:05, 6 May 2022 (UTC)[reply]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Last week, there was a problem with Wikidata's search autocomplete. This has now been fixed. [20]
Last week, all wikis had slow access or no access for 20 minutes, for logged-in users and non-cached pages. This was caused by a problem with a database change. [21]
The Vector (2022) skin will be set as the default on several more wikis, including Arabic and Catalan Wikipedias. Logged-in users will be able to switch back to the old Vector (2010). See the latest update about Vector (2022).
Future meetings
The next open meeting with the Web team about Vector (2022) will take place on 17 May. The following meetings are currently planned for: 7 June, 21 June, 5 July, 19 July.
The Wikimedia Hackathon will take place online on May 20–22, 2022. If you’re interested in presenting something around Wikidata and Wikibase during the hackathon, don’t wait too long to book a slot: Wikimedia Hackathon 2022/Schedule.
MapComplete is an OpenStreetMap viewer and editor that searches Wikidata for species - which means that it is super-easy to link the Wikidata item to a tree one sees!
REST API: We are continuing to implement the REST routes to get all statements of an Item and retrieve a single statement from an Item (phab:T305988, phab:T307087, phab:T307088)
Lexicographical data: We are finishing the version of the page for browsers without JavaScript support (phab:T298160). We started working on the feature to pre-fill the input fields by URL parameter (phab:T298154). And we started working on better suggestions for lexical categories so commonly-used ones can more easily be added to avoid mistakes (phab:T298150).
We fixed an issue with recently added new language codes not being usable for Lexemes and not being sorted correctly on Special:NewItem (phab:T277836).
Following an RfC, a change has been made to the administrators inactivity policy. Under the new policy, if an administrator has not made at least 100 edits over a period of 5 years they may be desysopped for inactivity.
A public status system for WMF wikis has been created. It is located at https://www.wikimediastatus.net/ and is hosted separately to WMF wikis so in the case of an outage it will remain viewable.
Arbitration
Remedy 2 of the St Christopher case has been rescinded following a motion. The remedy previously authorised administrators to place a ban on single-purpose accounts who were disruptively editing on the article St Christopher Iba Mar Diop College of Medicine or related pages from those pages.
The 
--
Message boxes produced by MediaWiki code will no longer have these CSS classes: 
