This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the
current talk page.
Hi Andy, not sure why you redirected
Template:Holiday abroad when the TfD was closed as no consensus. Or was there another TfD I was not made aware of? I will assume you weren't deliberately implementing your proposed changes because they failed to reach consensus. A courtesy notice would also have been appreciated. No bad faith assumed, rest assured. I do thank you for your efforts to keep the template namespace tidy, but please do bring this one back to TfD if you still feel a redirect is necessary. Hope you are well, and happy holidays :) — MusikAnimaltalk05:57, 24 December 2015 (UTC)
Wikidata weekly summary #190
Wikidata weekly summary #186
Here's your quick overview of what has been happening around Wikidata over the last week.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited
Corporation Street tram stop, you added a link pointing to the disambiguation page
Centro. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the
FAQ • Join us at the
DPL WikiProject.
Hi Andy, I just started a
discussion regarding the parameters for honorifics. Since you initially introduced them to the template I thought this would interest you.
De728631 (
talk)
20:27, 3 January 2016 (UTC)
Invitation to a virtual editathon on Women in Music
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
Wikimedia no longer uses visitor statistics from
comScore.
[1]
Internet Explorer 8 will no longer have
JavaScript support. You will
still be able to browse and edit Wikipedia if you use Internet Explorer 8, but will not be able to use some features. This can be solved by upgrading to a newer version or switching to a different browser.
[6][7]
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on
12 January at 20:00 (UTC). See
how to join.
Future changes
URLs in the recent changes IRC feed will no longer be rewritten to unencrypted HTTP. This could be a breaking change for bots dependent on the IRC feed.
[8]
The edit tabs for the wikitext editor and the visual editor will be combined to one single edit tab. You will be able to choose which one you prefer. If you are not logged in, your choice will be saved as a cookie in your browser. You
can test the single edit tab.
[9][10]
There is a beta feature that
adds links to the subject on other Wikimedia projects. This works much like the links to for example Wikipedia articles in other languages. It will go out of beta testing and be enabled for everyone in January. Wikis that don't want this can decide to have it disabled.
[11][12]
The difference between "alerts" and "messages" notifications is unclear to some. The developers want feedback at
the Phabricator task or
on MediaWiki.org so they can make this better. You can give feedback in your language if you can't write in English.
The Wikimedia Foundation is currently running
a consultation on the value and planning process of Wikimania, and is open until 18 January 2016. The goals are to (1) build a shared understanding of the value of Wikimania to help guide conference planning and evaluation, and (2) gather broad community input on what new form(s) Wikimania could take (starting in 2018).
Hi. Got your message. Let's continue here, as you are closer to the topic.
In the last discussion at
CS1 on the use of ORCID you thought (09:38, 17 April 2014) there were five decisions to make. I think the last two ("4. How to display ORCIDs in citations", and "5. How and to what to link those ORCIDs", are key ("toughest") to the
implementation of ORCID in citations, and need consideration.
So I think the issue here comes down to: is there any single character or symbol or mark (implemented in a standard character set, not as a graphic) that can be used to indicate a link to an ORCID page?
In the absence of any special character dedicated for ORCID (which might raise trademark issues), the question would be what ordinary character we might use for this purpose on Wikipedia? E.g., a raised ("superior") asterisk, such as is used in books to indicate a footnote, might be just the thing.
The small ORCID icon would be more distinctive and less ambiguous. A reduction in size would make it less intrusive. I'll discuss this when I next talk to the folk at ORCID, but I doubt they would expect their preferred style guideline to be binding on Wikipedia. Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits16:22, 8 January 2016 (UTC)
Regarding the ORCID icon, I disagree, but if we're going to move this forward, we shouldn't get hung up on a side issue. The external link icon can be suppressed by using {{Plainlinks}}; or locally in your suer CSS. Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits23:39, 9 January 2016 (UTC)
As a possible partial implementation I have been thinking of a generic "id link" template where we could do {{
idlink|orcid|0000-0002-1825-0097}} or {{
idlink|scopus|7007156898}} to generate the proper links. ~
J. Johnson (JJ) (
talk)
22:50, 11 January 2016 (UTC)
Perhaps but alternatively, or also, that functionality could be included in the Cite... family of templates. If a new template is created, it should include the name: {{idlink|name=Carberry|orcid=0000-0002-1825-0097}}. Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits23:39, 11 January 2016 (UTC)
For a single link it there is little difference between the "|orcid|000..." and "|orcid=000..." forms. But I can see a likely advantage in having a variable number of arguments in the form of "{{idlink |orcid=0000.. |scopus=1111.. |...}}": less typing overall, and more efficient implementation. But I don't see any point in havng a "|name=" parameter. What would it do?
A stand-alone implementation could work in all cases. Implementation in cs1/2 needs more consideration. One straight-forward approach (likely requiring no or no modification of cs) is to use {idlink} directly. E.g. {{citation |last1= Carberry |first1= J.S.{{idlink|orcid=000..}} |...}}. Alternately, we could have a class of |lastN-id= parms, similar to the author-links. These could be either open, taking the idlink template as before (and perhaps other stuff to put in right after the author's name), or dedicated, taking just the arguments and generating the link the directly. In the latter case we might have something like |last1-id= orcid-000.. scopus-111... However, having separate classes of idlink parameters (|lastN-orcid=, |lastN-scopus=, |lastN-resid=, etc.) seems way too heavy, excessively complicating the cs code. ~
J. Johnson (JJ) (
talk)
22:02, 13 January 2016 (UTC)
Monkey selfie
Hi. I've started
a discussion on the article's talk page, so we can talk about the matter. I don't know if you've notice already or not, but either way, can you participate? Thanks.
Nightscream (
talk)
00:25, 15 January 2016 (UTC)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited
John Joseph Mechi, you added a link pointing to the disambiguation page
Cutler. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the
FAQ • Join us at the
DPL WikiProject.
Students worked on new datatype to capture mathematical expressions (
phabricator:T67397)
Updated property suggester data to give you more up-to-date suggestions when adding new statements
Pages in the module namespace now also get interwiki links (
phabricator:T123234)
Reduced number of resource loader modules to improve performance (
phabricator:T123233)
Started experimenting with showing an image in the header area (
phabricator:T119493)
Fixed a bug where the query text would be moved off the screen on the query service website (
phabricator:T120196)
Worked on the remaining blocker for taking the in other projects sidebar out of beta. We need to link to the Commons category and not gallery for articles without frying the servers (
phabricator:T94989)
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
You will be able to find or mark bugs and suggestions in
Phabricator that are specific for your language or wiki.
[13]
Notifications have been upgraded with more detailed and easier-to-access information.
See the documentation. Cross-wiki notifications will be available soon on the two test wikis.
[14]
Changes this week
The visual editor uses the
TemplateData extension to make editing templates easier. You will now get a warning when you edit a TemplateData form and leave it without saving.
[15]
MediaWiki will get a new authentication and authorization system called AuthManager. This is planned to happen in a month or two. Some bots will need to change how they log in. Two new and more stable authentication methods will be available now: Owner-only
OAuth credentials and bot passwords. You can
read more about the change.
[16]
The
new version of MediaWiki will be on test wikis and MediaWiki.org from 19 January. It will be on non-Wikipedia wikis and some Wikipedias from 20 January. It will be on all Wikipedias from 21 January (
calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on
19 January at 20:00 (UTC). See
how to join.
You can join the next meeting with the Architecture committee. The topic this week is governance model. The meeting will be on
20 January at 22:00 (UTC). See
how to join.
...for the linked article you put up on the David Bowie talk page, Religion and spirituality section. You made my day! All the very best to you!
Boscaswell (
talk)
19:35, 16 January 2016 (UTC)
I would very much appreciate any view you would like to add,
Andy Mabbett, to the debate which is going on on the David Bowie talk page, Religion and spirituality section. I competely revamped the section yesterday, as previously it was truly awful, but mentioning Bowie and spirituality in the same breath has I believe got some people upset. I was able to use a few quotes from the interview which you highlighted - thanks again! Anyway, a few hatchets were taken to my revamp, almost immediately. Today I made some minor changes, but edit war has broken out. Thank you.
Boscaswell (
talk)
21:56, 19 January 2016 (UTC)
Hello there! Happy to be writing this newsletter once more. This month:
What comes next
Some good news: the Wikimedia Foundation has renewed WikiProject X. This means we can continue focusing on making WikiProjects better.
During our first round of work, we created a prototype WikiProject based on two ideas: (1) WikiProjects should clearly present things for people to do, and (2) The content of WikiProjects should be automated as much as possible. We launched pilots, and for the most part it works. But this approach will not work for the long term. While it makes certain aspects of running a WikiProject easier, it makes the maintenance aspects harder.
We are working on a major overhaul that will address these issues. New features will include:
Creating WikiProjects by simply filling out a form, choosing which reports you want to generate for your project. This will work with existing bots in addition to the
Reports Bot reports. (Of course, you can also have sections curated by humans.)
One-click button to join a WikiProject, with optional notifications.
Be able to define your WikiProject's scope within the WikiProject itself by listing relevant pages and categories, eliminating the need to tag every talk page with a banner. (You will still be allowed to do that, of course. It just won't be required.)
The end goal is a collaboration tool that can be used by WikiProjects but also by any edit-a-thon or group of people that want to coordinate on improving articles. Though implemented as an extension, the underlying content will be wikitext, meaning that you can continue to use categories, templates, and other features as you normally would.
This will take a lot of work, and we are just getting started. What would you like to see? I invite you to discuss on our
talk page.
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
You can now follow when pages are added or removed from a category on German Wikipedia. The plan is to add it to Wikimedia Commons and other Wikipedias this week.
[17][18]
Administrators can hide individual entries of a page with
RevisionDelete. There is now a button to choose "all", "none" or "inverse" in Special:Log. The article history will get the same buttons soon. Wikis that have done this locally with JavaScript will be able to remove that code.
[19]
Changes this week
You will be able to see the references when you preview a section you are editing. This will happen even if there is no <references /> tag in that section.
[20]
The
new version of MediaWiki will be on test wikis and MediaWiki.org from 26 January. It will be on non-Wikipedia wikis and some Wikipedias from 27 January. It will be on all wikis from 28 January (
calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on
26 January at 20:00 (UTC). See
how to join.
Future changes
There is now an extension called
ArticlePlaceholder. It can automatically generate content on Wikipedia with data from Wikidata if there is no Wikipedia article. It will have a tag to remind the reader it is not an article and ask the reader to create one. The developer is now looking for smaller Wikipedias that want to try the extension.
[21]
The
OTRS system will be upgraded. The plan is to do this on
3 February at 08:00 (UTC). It will probably take 6 to 8 hours. OTRS will be down during the upgrade.
[22]
Users will soon be automatically congratulated when they reach some edit count milestones.
[23]
Changes in how authentication in MediaWiki is handled are being rolled out (and more coming).
[24] Ordinary users and gadgets / user scripts should not be affected but bots may need to be adjusted. pywikibot already supports
[25] OAuth authentication, though bot operators need to set that up for their bot.
Investigated language support in MediaWiki and Wikibase to allow more languages in monolingual text and disallow some non-sense for label/descriptions/aliases (
phabricator:T78006)
Fixed missing license info and broken links for Wikibase libraries on Special:Version
Working on improving scoring of search results on Wikidata, on Special:Search
Preparing to take the "in other projects" sidebar out of beta features, with the Wikimedia Commons link going to the Commons category (
phabricator:T103102,
phabricator:T94989)
Amir and Aaron are turning
ORES into an extension to make it easier for you to spot bad edits \o/
Final touches on putting identifiers into their own section (
phabricator:T117421)
Switching the in other languages box to be expanded by default for new people (
phabricator:T92387)
More experimenting with adding an image to the header area (
phabricator:T119493)
Good day, Andy. Hope you're doing well. While digging through some old stuff in the above template, I have noticed that you were interested in improving the above template. So I thought of letting you know that I'm currently working on a revamped version
here. It's currently in the final stages (I have not yet notified the other editors), but I'd appreciate if you could have a peek and see if there are any bugs and/or any other areas that could be improved. I will be staring work on the compatibility side of the code over the next couple of days... Best wishes,
Rehman08:42, 24 January 2016 (UTC)
@
Rehman: Thank you; I'll take a look shortly. My main concern is to merge in the relevant functionality from {{Geobox}}, in order that the use of Geobox for rivers can be deprecated, and instances replaced with the infobox. Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits12:55, 24 January 2016 (UTC)
Hi Andy. Thanks for the input. I have no issue with retaining native_name_langname_native_lang and progression. But I disagree on adding |etymology= as it doesn't belong in an
infobox and against
H:IB.
Since there will be a bot sweep over articles using this template, it is a very good window for us to tidy-up and stylize the parameters simultaneously, even if the change is trivial. If you look closer at the template skeleton listed on the sandbox-doc page, changes like native_name → name_native and left_tribs → tributaries_left makes the overall skeleton look much neater thanks to the ordered prefix.
Things like |river_name=, |mouth=, and |other_name=, are not removed as such, but instead will be replaced. This is pending a bot scan to see how exactly to go about with it.
Similar cleanups were done at {{Infobox power station}} and {{Infobox dam}}, and the results are quite good. The number of articles using these infoboxes will only increase over time, to an extent where any neatness/cosmetic changes will only be instantly rejected due to the number of articles effected. Hence this is a great oppurtunity to neaten things up... If you compare the current doc page, and the doc at the sandbox, I am sure you would agree that we need to clean/simpify things there. And once this is done, we can then focus on making the Infobox River the primary infobox for river articles (as it should have been), and discontinue the geobox...
Rehman03:37, 25 January 2016 (UTC)
@
Rehman: There is nothing against the use of |etymology= in either MoS or H:IB; it is there now, so I'm not asking for it to be "added"; please don't remove it unless there is consensus to do so. Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits09:35, 25 January 2016 (UTC)
Fair enough. Just FYI, HIB states that an infobox should not contain "Long bodies of text, or very detailed statistics, belong in the article body". Since the content intended for that field cannot be entered in a couple of characters/words, it does not belong in an 'infobox'.
Rehman10:35, 25 January 2016 (UTC)
Maybe; only because all of the examples I came across had at least two sentences in them... Lets discuss about this later, once the cleanup part is complete. No hard feelings. Regards,
Rehman12:18, 25 January 2016 (UTC)
Hi Andy. Based on
this test, native_name_lang doesn't seems to do anything (probably since it was added). Am I missing something? The test is using the current (unaltered) infobox.
Rehman13:08, 26 January 2016 (UTC)