Jump to content

User talk:JarrahTree/Archive 57

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


Wikidata weekly summary #353

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

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

Books & Bytes, Issue 32

[edit]

The Wikipedia Library

Books & Bytes
Issue 32, January – February 2019

  • #1Lib1Ref
  • New and expanded partners
  • Wikimedia and Libraries User Group update
  • Global branches update
  • Bytes in brief

French version of Books & Bytes is now available on meta!

Read the full newsletter

Sent by MediaWiki message delivery on behalf of The Wikipedia Library team --MediaWiki message delivery (talk) 03:30, 26 February 2019 (UTC)[reply]

Facto Post – Issue 21 – 28 February 2019

[edit]
Facto Post – Issue 21 – 28 February 2019
The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Back numbers are here.
What is a systematic review?

Systematic reviews are basic building blocks of evidence-based medicine, surveys of existing literature devoted typically to a definite question that aim to bring out scientific conclusions. They are principled in a way Wikipedians can appreciate, taking a critical view of their sources.

PRISMA flow diagram for a systematic review

Ben Goldacre in 2014 wrote (link below) "[...] : the "information architecture" of evidence based medicine (if you can tolerate such a phrase) is a chaotic, ad hoc, poorly connected ecosystem of legacy projects. In some respects the whole show is still run on paper, like it's the 19th century." Is there a Wikidatan in the house? Wouldn't some machine-readable content that is structured data help?

File:Schittny, Facing East, 2011, Legacy Projects.jpg
2011 photograph by Bernard Schittny of the "Legacy Projects" group

Most likely it would, but the arcana of systematic reviews and how they add value would still need formal handling. The PRISMA standard dates from 2009, with an update started in 2018. The concerns there include the corpus of papers used: how selected and filtered? Now that Wikidata has a 20.9 million item bibliography, one can at least pose questions. Each systematic review is a tagging opportunity for a bibliography. Could that tagging be reproduced by a query, in principle? Can it even be second-guessed by a query (i.e. simulated by a protocol which translates into SPARQL)? Homing in on the arcana, do the inclusion and filtering criteria translate into metadata? At some level they must, but are these metadata explicitly expressed in the articles themselves? The answer to that is surely "no" at this point, but can TDM find them? Again "no", right now. Automatic identification doesn't just happen.

Actually these questions lack originality. It should be noted though that WP:MEDRS, the reliable sources guideline used here for health information, hinges on the assumption that the usefully systematic reviews of biomedical literature can be recognised. Its nutshell summary, normally the part of a guideline with the highest density of common sense, allows literature reviews in general validity, but WP:MEDASSESS qualifies that indication heavily. Process wonkery about systematic reviews definitely has merit.

Links
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:02, 28 February 2019 (UTC)[reply]

The Signpost: 28 February 2019

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 11:16, 28 February 2019 (UTC)[reply]

Wikidata weekly summary #354

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

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


Proposed deletion of Geoff Law

[edit]
Notice

The article Geoff Law has been proposed for deletion because it appears to have no references. Under Wikipedia policy, this biography of a living person will be deleted after seven days unless it has at least one reference to a reliable source that directly supports material in the article.

If you created the article, please don't be offended. Instead, consider improving the article. For help on inserting references, see Referencing for beginners, or ask at the help desk. Once you have provided at least one reliable source, you may remove the {{prod blp/dated}} tag. Please do not remove the tag unless the article is sourced. If you cannot provide such a source within seven days, the article may be deleted, but you can request that it be undeleted when you are ready to add one. Rogermx (talk) 02:48, 5 March 2019 (UTC)[reply]

This Month in GLAM: February 2019

[edit]


Headlines
Read this edition in full • Single-page

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

Original research question

[edit]

Hello, I received your message, but had no context for it. In what area are you concerned that original research is taking place? Nicholas Nastrusnic (talk) 14:11, 9 March 2019 (UTC)Thank you.[reply]

  • Received your message, thank you. That entire article had no inline citations before I placed anything there, and the content you are referring to I literally just added (I am working on uploading a picture from the book currently). In any event, what I wrote also had two wikilinks that go to articles that have a whole host of relecant references associated with them; from my understanding that means one does not have to add an actual source if what is being added is a short statement that includes piped words linkable to other articles. In any event I have added an inline citation (the first of the entire article :) ) Cheers Nicholas Nastrusnic (talk) 14:32, 9 March 2019 (UTC)[reply]

... no further comment - you revert, thats it cheers JarrahTree 14:37, 9 March 2019 (UTC)[reply]

I Corps (Australia)

[edit]

Hi, I've just reverted your move of the I Corps (Australia). The corps is most commonly called I Corps by historians, including in the the post-war official histories and recent works. 1st Corps is sometimes also used, but under western countries' military naming conventions army field corps are typically allocated roman numerals. If you think that this is miss-named, can you please start a requested move discussion? Regards, Nick-D (talk) 06:10, 11 March 2019 (UTC)[reply]

Wikidata weekly summary #355

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

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



NPR Newsletter No.17

[edit]

Hello JarrahTree,

News
Discussions of interest
  • Two elements of CSD G6 have been split into their own criteria: R4 for redirects in the "File:" namespace with the same name as a file or redirect at Wikimedia Commons (Discussion), and G14 for disambiguation pages which disambiguate zero pages, or have "(disambiguation)" in the title but disambiguate a single page (Discussion).
  • {{db-blankdraft}} was merged into G13 (Discussion)
  • A discussion recently closed with no consensus on whether to create a subject-specific notability guideline for theatrical plays.
  • There is an ongoing discussion on a proposal to create subject-specific notability guidelines for chemicals and organism taxa.
Reminders
  • NPR is not a binary keep / delete process. In many cases a redirect may be appropriate. The deletion policy and its associated guideline clearly emphasise that not all unsuitable articles must be deleted. Redirects are not contentious. See a classic example of the templates to use. More templates are listed at the R template index. Reviewers who are not aware, do please take this into consideration before PROD, CSD, and especially AfD because not even all admins are aware of such policies, and many NAC do not have a full knowledge of them.
NPP Tools Report
  • Superlinks – allows you to check an article's history, logs, talk page, NPP flowchart (on unpatrolled pages) and more without navigating away from the article itself.
  • copyvio-check – automatically checks the copyvio percentage of new pages in the background and displays this info with a link to the report in the 'info' panel of the Page curation toolbar.
  • The NPP flowchart now has clickable hyperlinks.

Six Month Queue Data: Today – Low – 2393 High – 4828
Looking for inspiration? There are approximately 1000 female biographies to review.
Stay up to date with even more news – subscribe to The Signpost.

Go here to remove your name if you wish to opt-out of future mailings.

--MediaWiki message delivery (talk) 23:18, 15 March 2019 (UTC)[reply]

Wikipedia:WikiProject Portals update #030, 17 Mar 2019

[edit]

Previous issue:

Single-page portals: 4,704
Total portals: 5,705

This issue:

Single-page portals: 4,562
Total portals: 5,578

The collection of portals has shrunk

[edit]

All Portals closed at WP:MfD during 2019

Grouped Nominations total 127 Portals:

  1. Wikipedia:Miscellany for deletion/US County Portals Deleted 64 portals
  2. Wikipedia:Miscellany for deletion/Districts of India Portals Deleted 30 Portals
  3. Wikipedia:Miscellany for deletion/Portals for Portland, Oregon neighborhoods Deleted 23 Portals
  4. Wikipedia:Miscellany for deletion/Portal:Allen Park, Michigan Deleted 6 Portals
  5. Wikipedia:Miscellany for deletion/Portal:Cryptocurrency Deleted 2 Portals
  6. Wikipedia:Miscellany for deletion/Portal:North Pole Deleted 2 Portals

Individual Nominations:

  1. Wikipedia:Miscellany for deletion/Portal:Circles Deleted
  2. Wikipedia:Miscellany for deletion/Portal:Fruits Deleted
  3. Wikipedia:Miscellany for deletion/Portal:E (mathematical constant) Deleted
  4. Wikipedia:Miscellany for deletion/Portal:Burger King Deleted
  5. Wikipedia:Miscellany for deletion/Portal:Cotingas Deleted
  6. Wikipedia:Miscellany for deletion/Portal:Prostitution in Canada Deleted
  7. Wikipedia:Miscellany for deletion/Portal:Agoura Hills, California Deleted
  8. Wikipedia:Miscellany for deletion/Portal:Urinary system Deleted
  9. Wikipedia:Miscellany for deletion/Portal:You Am I Deleted
  10. Wikipedia:Miscellany for deletion/Portal:Cannabis (2nd nomination) Reverted to non-Automated version
  11. Wikipedia:Miscellany for deletion/Portal:Intermodal containers Deleted
  12. Wikipedia:Miscellany for deletion/Portal:Adventure travel Deleted
  13. Wikipedia:Miscellany for deletion/Portal:Adam Ant Deleted
  14. Wikipedia:Miscellany for deletion/Portal:Benito Juárez, Mexico City Deleted
  15. Wikipedia:Miscellany for deletion/Portal:Spaghetti Deleted
  16. Wikipedia:Miscellany for deletion/Portal:Wikiatlas Deleted
  17. Wikipedia:Miscellany for deletion/Portal:Greek alphabet Deleted
  18. Wikipedia:Miscellany for deletion/Portal:Aleksandr Solzhenitsyn Deleted
  19. Wikipedia:Miscellany for deletion/Portal:Accounting Deleted G7
  20. Wikipedia:Miscellany for deletion/Portal:Lents, Portland, Oregon Deleted P2
  21. Wikipedia:Miscellany for deletion/Portal:Ankaran Deleted
  22. Wikipedia:Miscellany for deletion/Portal:Jiu-jitsu Deleted G8
  23. Portal:University of Nebraska Speedy Deleted P1/A10 exactly the same as Portal:University of Nebraska–Lincoln also created by the TTH

Related WikiProject:

  1. Wikipedia:Miscellany for deletion/Wikipedia:WikiProject Quantum portals Demoted

(Attribution: Copied from Wikipedia:Administrators' noticeboard#Portal MfD Results)

WikiProject Quantum portals

[edit]

This was a spin-off from WikiProject Portals, for the purpose of developing zero-page portals (portals generated on-the-screen at the push of a button, with no stored pages).

It has been merged back into WikiProject Portals. In the MfD the vote was "demote". See Wikipedia:Miscellany for deletion/Wikipedia:WikiProject Quantum portals.

Hiatus on mass creation of Portals

[edit]

At WP:VPR, mass creation of Portals using semi-automated tools has been put on hold until clearer community consensus is established.

See Wikipedia:Village pump (proposals)#Hiatus on mass creation of Portals.

The Transhumanist banned from creating new portals for 3 months

[edit]

See Wikipedia:Administrators' noticeboard#Proposal 1: Interim Topic-Ban on New Portals.

Until next issue...

[edit]

Keep on keepin' on.    — The Transhumanist   10:17, 17 March 2019 (UTC)[reply]

Wikidata weekly summary #356

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

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


Category:Railway accident locations in Western Australia has been nominated for discussion

[edit]

Category:Railway accident locations in Western Australia, which you created, has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Shyamsunder (talk) 10:48, 19 March 2019 (UTC)[reply]

Category:Foundation members of the Tasmanian Wilderness Society has been nominated for discussion

[edit]

Category:Foundation members of the Tasmanian Wilderness Society, which you created, has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Shyamsunder (talk) 10:51, 19 March 2019 (UTC)[reply]

How to create portals

[edit]

The following instructions are not subject-specific...

There are 2 main situations in creating portals:

1) Subjects that have the necessary resources to support instant creation via {{bpsp}}.

2) Subjects that don't.

There are 2 main approaches to building portals:

1) You look around for subjects that fit the support criteria = fast. And you use {{subst:bpsp}} to create them.

2) You select subjects that you want to build portals for = potentially slow. Then you build a {{navbox}} navigation footer for each subject (if they don't already exist), and then use {{subst:bpsp}} to build the portals.

I hope the above instructions make sense.

Good luck.    — The Transhumanist   11:11, 4 February 2019 (UTC)[reply]

Re: wow

[edit]

Yeah, crazy ... but better than no tag at all! Graham87 16:21, 23 March 2019 (UTC)[reply]

Zhivko Sedlarski

[edit]

Hi JarrahTree,

Sorry for my previous message and thank you for your reply.

I was a little bit aggressive in my reply because I've spent time to create a page and the page disappear.

Thank you for adding the points and how I can ask the admin to restore the page. I want to create a biography about my father and his work but I'm novice in Wikipedia. I did it in French.

I hope I will find the way and I will have a page of my father.

Thank you for everything.Nikola-Sedlarski (talk) 09:57, 25 March 2019 (UTC)[reply]

Comment

[edit]

Thanks for your forbearance with this editor. I've posted a warning/guidance on his talk page. I think his dad probably is notable enough, so I've offered to restore as a cleaned-up draft. Jimfbleak - talk to me? 11:24, 25 March 2019 (UTC)[reply]

Wikidata weekly summary #357

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

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


Facto Post – Issue 22 – 28 March 2019

[edit]
Facto Post – Issue 22 – 28 March 2019
The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Back numbers are here.
When in the cloud, do as the APIs do

Half a century ago, it was the era of the mainframe computer, with its air-conditioned room, twitching tape-drives, and appearance in the title of a spy novel Billion-Dollar Brain then made into a Hollywood film. Now we have the cloud, with server farms and the client–server model as quotidian: this text is being typed on a Chromebook.

File:Cloud-API-Logo.svg
Logo of Cloud API on Google Cloud Platform

The term Applications Programming Interface or API is 50 years old, and refers to a type of software library as well as the interface to its use. While a compiler is what you need to get high-level code executed by a mainframe, an API out in the cloud somewhere offers a chance to perform operations on a remote server. For example, the multifarious bots active on Wikipedia have owners who exploit the MediaWiki API.

APIs (called RESTful) that allow for the GET HTTP request are fundamental for what could colloquially be called "moving data around the Web"; from which Wikidata benefits 24/7. So the fact that the Wikidata SPARQL endpoint at query.wikidata.org has a RESTful API means that, in lay terms, Wikidata content can be GOT from it. The programming involved, besides the SPARQL language, could be in Python, younger by a few months than the Web.

Magic words, such as occur in fantasy stories, are wishful (rather than RESTful) solutions to gaining access. You may need to be a linguist to enter Ali Baba's cave or the western door of Moria (French in the case of "Open Sesame", in fact, and Sindarin being the respective languages). Talking to an API requires a bigger toolkit, which first means you have to recognise the tools in terms of what they can do. On the way to the wikt:impactful or polymathic modern handling of facts, one must perhaps take only tactful notice of tech's endemic problem with documentation, and absorb the insightful point that the code in APIs does articulate the customary procedures now in place on the cloud for getting information. As Owl explained to Winnie-the-Pooh, it tells you The Thing to Do.

Links
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:45, 28 March 2019 (UTC)[reply]

Thank you

[edit]
Cookies!

Dr.Bookman has given you some cookies! Cookies promote WikiLove and hopefully this one has made your day better. You can spread the "WikiLove" by giving someone else some cookies, whether it be someone you have had disagreements with in the past or a good friend.

Thank you for showing to me Wikipedia adventure, i learned a lot! Thank you very much again. :)

To spread the goodness of cookies, you can add {{subst:Cookies}} to someone's talk page with a friendly message, or eat this cookie on the giver's talk page with {{subst:munch}}!

hHAhahahahaahah, it is really. I will give my best. :) Thank you man! --Dr.Bookman (talk) 23:44, 28 March 2019 (UTC)[reply]
Is that comment new level in Wikipedia adventure i have just finished? :) --Dr.Bookman (talk) 00:07, 29 March 2019 (UTC)[reply]
I know, i am just kidding because of the planet references from Wikipedia adventure. :) --Dr.Bookman (talk) 00:30, 29 March 2019 (UTC)[reply]

The Signpost: 31 March 2019

[edit]
News, reports and features from the English Wikipedia's weekly journal about Wikipedia and Wikimedia

Wikidata weekly summary #358

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

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


Thank you, JarrahTree

[edit]

Thanks for welcoming me, but I am in the English Wikipedia 2 years now and I don't need to get anymore messages welcoming me, but thanks. If I'll need help I'll tell you. 

And, 
    what's the problem with big lists?

Cow me, please! (talk) 13:09, 3 April 2019 (UTC)[reply]


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

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


Wikidata weekly summary #361

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

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


Do as I say, not as I do?

[edit]

It would be really good if other editors were able to offer their perspectives - indeed it would be, and your perspective on this is ...? Mitch Ames (talk) 01:52, 26 April 2019 (UTC)[reply]

Acacia beadleana

[edit]

Jeez, was just about to do that talk page....Hughesdarren (talk) 13:07, 29 April 2019 (UTC)[reply]

Wikidata weekly summary #362

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

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


Facto Post – Issue 23 – 30 April 2019

[edit]
Facto Post – Issue 23 – 30 April 2019
The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Back numbers are here.
Completely clouded?
Cloud computing logo

Talk of cloud computing draws a veil over hardware, but also, less obviously but more importantly, obscures such intellectual distinction as matters most in its use. Wikidata begins to allow tasks to be undertaken that were out of easy reach. The facility should not be taken as the real point.

Coming in from another angle, the "executive decision" is more glamorous; but the "administrative decision" should be admired for its command of facts. Think of the attitudes ad fontes, so prevalent here on Wikipedia as "can you give me a source for that?", and being prepared to deal with complicated analyses into specified subcases. Impatience expressed as a disdain for such pedantry is quite understandable, but neither dirty data nor false dichotomies are at all good to have around.

Issue 13 and Issue 21, respectively on WP:MEDRS and systematic reviews, talk about biomedical literature and computing tasks that would be of higher quality if they could be made more "administrative". For example, it is desirable that the decisions involved be consistent, explicable, and reproducible by non-experts from specified inputs.

What gets clouded out is not impossibly hard to understand. You do need to put together the insights of functional programming, which is a doctrinaire and purist but clearcut approach, with the practicality of office software. Loopless computation can be conceived of as a seamless forward march of spreadsheet columns, each determined by the content of previous ones. Very well: to do a backward audit, when now we are talking about Wikidata, we rely on integrity of data and its scrupulous sourcing: and clearcut case analyses. The MEDRS example forces attention on purge attempts such as Beall's list.

Links
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:27, 30 April 2019 (UTC)[reply]

Wikipedia:WikiProject Portals update #031, 01 May 2019

[edit]

Back to the drawing board

[edit]

Implementation of the new portal design has been culled back almost completely, and the cull is still ongoing. The cull has also affected portals that existed before the development of the automated design.

Some of the reasons for the purge are:

  • Portals receive insufficient traffic, making it a waste of editor resources to maintain them, especially for narrow-scope or "micro" portals
  • The default {{bpsp}} portals are redundant with the corresponding articles, being based primarily on the corresponding navigation footer displayed on each of those articles, and therefore not worth separate pages to do so
  • They were mass created

Most of the deletions have been made without prejudice to recreation of curated portals, so that approval does not need to be sought at Deletion Review in those cases.

In addition to new portals being deleted, most of the portals that were converted to an automated design have been reverted.

Which puts us back to portals with manually selected content, that need to be maintained by hand, for the most part, for the time being, and back facing some of the same problems we had when we were at this crossroads before:

  • Manually maintained portals are not scalable (they are labor intensive, and there aren't very many editors available to maintain them)
  • The builders/maintainers tend to eventually abandon them
  • Untended handcrafted portals go stale and fall into disrepair over time

These and other concepts require further discussion. See you at WT:POG.

However, after the purge/reversion is completed, some of the single-page portals might be left, due to having acceptable characteristics (their design varied some). If so, then those could possibly be used as a model to convert and/or build more, after the discussions on portal creation and design guidelines have reached a community consensus on what is and is not acceptable for a portal.

See you at WT:POG.

Curation

[edit]

A major theme in the deletion discussions was the need for portals to be curated, that is, each one having a dedicated maintainer.

There are currently around 100 curated portals. Based on the predominant reasoning at MfD, it seems likely that all the other portals may be subject to deletion.

See you at WT:POG.

Traffic

[edit]

An observation and argument that arose again and again during the WP:ENDPORTALS RfC and the ongoing deletion drive of {{bpsp}} default portals, was that portals simply do not get much traffic. Typically, they get a tiny fraction of what the corresponding like-titled articles get.

And while this isn't generally considered a good rationale for creation or deletion of articles, portals are not articles, and portal critics insist that traffic is a key factor in the utility of portals.

The implication is that portals won't be seen much, so wouldn't it be better to develop pages that are?

And since such development isn't limited to editing, almost anything is possible. If we can't bring readers to portals, we could bring portal features, or even better features, to the readers (i.e., to articles)...

Some potential future directions of development

[edit]

Quantum portals?

[edit]

An approach that has received some brainstorming is "quantum portals", meaning portals generated on-the-fly and presented directly on the view screen without any saved portal pages. This could be done by script or as a MediaWiki program feature, but would initially be done by script. The main benefits of this is that it would be opt-in (only those who wanted it would install it), and the resultant generated pages wouldn't be saved, so that there wouldn't be anything to maintain except the script itself.

Non-portal integrated components

[edit]

Another approach would be to focus on implementing specific features independently, and provide them somewhere highly visible in a non-portal presentation context (that is, on a page that wasn't a portal that has lots of traffic, i.e., articles). Such as inserted directly into an article's HTML, as a pop-up there, or as a temporary page. There are scripts that use these approaches (providing unrelated features), and so these approaches have been proven to be feasible.

What kind of features could this be done with?

The various components of the automated portal design are transcluded excerpts, news, did you know, image slideshows, excerpt slideshows, and so on.

Some of the features, such as navigation footers and links to sister projects are already included on article pages. And some already have interface counterparts (such as image slideshows). Some of the rest may be able to be integrated directly via script, but may need further development before they are perfected. Fortunately, scripts are used on an opt-in basis, and therefore wouldn't affect readers-in-general and editors-at-large during the development process (except for those who wanted to be beta testers and installed the scripts).

The development of such scripts falls under the scope of the Javascript-WikiProject/Userscript-department, and will likely be listed on Wikipedia:User scripts/List when completed enough for beta-testing. Be sure to watchlist that page.

Where would that leave curated portals?

[edit]

Being curated. At least for the time being.

New encyclopedia program features will likely eventually render most portals obsolete. For example, the pop-up feature of MediaWiki provides much the same functionality as excerpts in portals already, and there is also a slideshow feature to view all the images on the current page (just click on any image, and that activates the slideshow). Future features could also overlap portal features, until there is nothing that portals provide that isn't provided elsewhere or as part of Wikipedia's interface.

But, that may be a ways off. Perhaps months or years. It depends on how rapidly programmers develop them.

Keep on keepin' on

[edit]

The features of Wikipedia and its articles will continue to evolve, even if Portals go by the wayside. Most, if not all of portals' functionality, or functions very similar, will likely be made available in some form or other.

And who knows what else?

No worries.

Until next issue...    — The Transhumanist   01:17, 2 May 2019 (UTC)[reply]

May 2019

[edit]

Warning removed, with apologies Mvcg66b3r (talk) 11:37, 2 May 2019 (UTC)[reply]

  • @Mvcg66b3r: A self revert is not edit warring, there was two editors fixing sock puppets they over lapped, JT noticed this had happened and reverted. I recommend you apologise and remove this warning Gnangarra 11:04, 2 May 2019 (UTC)[reply]
First, after having passed 199k edits, to be warned for edit warring with myself... sigh JarrahTree 02:44, 3 May 2019 (UTC)[reply]


New Flora of Australia site

[edit]

Hi. I should have discovered this site long ago and I suspect many of us have not done so I am hoping you might pop it into an appropriate place. I have already proposed it as a wikidata item. I suspect that all the taxa that are not in flora of Australia online are those that are first going up to this site. Certainly, taxa which I cannot find on foao I now can find here. I think it needs to be drawn to the attention of the wikipedia Australian biota community. An example: Flora of Australia: Acacia abbreviata Maslin, and the search part is: https://profiles.ala.org.au/opus/foa/search I am hoping you will know where to put the info so that the site starts to become more widely used... Cheers, MargaretRDonald (talk) 19:07, 17 April 2019 (UTC)[reply]

Wikidata weekly summary #363

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: BRPever, welcome on board!

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


Poundofdonuts

[edit]

Dear Jarrah Tree,

I have seen you have advised Poundofdonuts (who`s profile exists since a day) not to move pages without a discussion. He kept moving pages without encouraging a discussion. He also moved articles with sensitive themes. As an experienced editor, you might know the tools how to fix this. Thank you. Best, Lean Anael (talk) 16:40, 6 May 2019 (UTC) He has not stopped yet with his sensitive editing and does not answer on his discussion page.Lean Anael (talk) 21:13, 12 May 2019 (UTC)[reply]

WP:Plants assessments

[edit]

The articles on Australian plant species you have been assessing are not High-importance or even Mid-importance. Being endangered is not an assessment criterion. Thanks. Abductive (reasoning) 04:50, 7 May 2019 (UTC)[reply]


Christian Smith (DJ) at AfD

[edit]

I notice you did some work on the article.

A discussion is taking place as to whether the article Christian Smith (DJ) is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/Christian Smith (DJ) until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.HouseOfChange (talk) 20:27, 8 May 2019 (UTC)[reply]

Category:Minerals named after locations in Western Australia has been nominated for discussion

[edit]

Category:Minerals named after locations in Western Australia, which you created, has been nominated for deletion. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. RevelationDirect (talk) 00:28, 9 May 2019 (UTC)[reply]

In case you want to start a list article, here are the current articles:
  • Western Australia
  • Tasmania
RevelationDirect (talk) 15:31, 9 May 2019 (UTC)[reply]

This Month in GLAM: April 2019

[edit]


Headlines
Read this edition in full • Single-page

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

One Cat, Two Cats, Red Cats, Blue Cats

[edit]

Re: this - Are you going to create Category:Wikimedia meetups in May 2019? Perhaps rename Category:Wikipedia meetups in May 2019? Create a whole new category tree, to be more inclusive of our Commons and Data collaborators? Mitch Ames (talk) 07:33, 11 May 2019 (UTC)[reply]

Wikidata weekly summary #364

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

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


Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:JarrahTree/Archive_57&oldid=998918716"